The PARIS Forums - RDF feed
type: channel
items: OT for dog lovers (warning, pix):
items: Re: OT for dog lovers (warning, pix):

OT for dog lovers (warning, pix):
type: item
description: /> Open the software and create a session on each computer. On the PARIS computer I called it PARIS rtpMIDI. On the Cubase computer I called it Cubase rtpMIDI. As long as the computers can PING each, rtpMIDI should now show the other computer in the Directory box. Cubase rtpMIDI on the PARIS machine. PARIS rtpMIDI on the Cubase machine. Open PARIS and in the project open the MIDI Devices windows. Set PARIS rtpMIDI to send MTC signals clicking the box on the right. In Cubase, I'm using Version 5, open the Project Synchronisation Setup found in the Transport menu. In the MIDI Timecode Source box select Cubase rtpMIDI as the MTC input. Make sure that Use External Sync is selected. It is also in the Transport Menu. As long as I haven't forgotten anything, Cubase should be synced to PARIS. Not sure if anyone has tried using Ethernet to sync PARIS yet couldn't find anything about it in my searches here. DeanWow - So real time Virtual Instruments via external connection is possible yes? (I know very little about MIDI) Thanks for posting! TedHi Ted, I'm using Cubase to run Superior Drummer mostly. I haven't had time to check latencies yet with the setup. I'm running a Creative X-FI card for sound on the Cubase machine. Coming out of the SPDIF then into the MEC. Using this setup I can sync the transport of each together and record the MIDI into Cubase and also record the output of Superior Drummer, or any another VSTi, into PARIS via the SPDIF. If I need I can then edit the MIDI track or change the drum sounds. Press record on PARIS and Cubase will replay the drums through SPDIF into PARIS. There are other ways to sync PARIS to another DAW which can run VSTi yet I don't have any ADAT which seems the most common way of doing it. Thought I would try connecting using MIDI over Ethernet since I already had a crossover cable not being used. So far I haven't noticed any latency, yet I only got it all synced up this morning. Will do some proper checking in a few days when I'm back …
creator: Kerry Galloway
date: 2008-12-01T17:22:06-00:00

Re: OT for dog lovers (warning, pix):
type: item
description: y New Year. Your system is indeed antiquated. One thing stood out, however. SCSI is absolutely not needed. I too initially used a dedicated SCSI drive, but found I was getting MUCH higher track counts just using the system drive. Try it! Even with your old system, you should get more than ten tracks! As you already have version 3 of Paris, you are well on your way to setting up a very capable system. I'd say there is absolutely nothing worth salvaging from your old system. You could pick up, say, a dual core Intel or AMD computer for literally nothing these days. If going second hand, Check government clearance auctions, or even scour the streets! Make sure the motherboard has no bulging electrolytic capacitors, and has SATA ports, as well as enough of the older PCI slots for your EDS's. You can buy a nice new 500gb drive for around $30. It doesn't have to be anything special. Any modern drive can easily cope with 24 tracks plus. (I have no problem with 64 tracks, albei
creator: Don Nafe
date: 2008-12-01T20:29:10-00:00

Re: OT for dog lovers (warning, pix):
type: item
description: Crap! Not even close...issues running just 10 tracks at this resolution. I stripped everything out of the system and went back to 1 card and an Interface 2. Checked all optimization. Turned everything off that I could in CMOS. I believe my immediate issue to be associated with the SCSI drive/buss/configuration/throughput. So I've been reading and reading. I now have many questions to pose and would really appreciate any and all help/advice you can offer. My questions will be all over the map until I can determine a direction and you can help me solve a few things. Please
creator: Gantt Kushner
date: 2008-12-01T20:33:44-00:00

Re: OT for dog lovers (warning, pix):
type: item
description: consider this fact when responding; Life has dealt me a few difficult hands which have severely limited my finances, therefore money is an issue when deciding how to deal with this situation. And shortage of money is why I need to get this running! My main goal is to be able to do mix sessions with 24 live tracks at 24 48 with a few Direct X and VST plugins. My current Paris hardware: 2 EDS cards 2 black C16s 1 MEC w/ 2 analog input cards (8 ch) and 1 analog output card (8 ch) 1 Interface 2 Running v3.0 and have downloaded the NEW, Pace free v3.01 if needed (AWESOME!!!) My current compute
creator: Deej [5]
date: 2008-12-01T21:04:03-00:00

Re: OT for dog lovers (warning, pix):
type: item
description: ut what about recording? Better with a standard SATA HD for my 2nd drive?
creator: John [1]
date: 2008-12-01T22:56:55-00:00

Re: OT for dog lovers (warning, pix):
type: item
description: ; drive. (Drive D Or E: if you had a CD-rom/burner). As far as drives go, I have steered clear of Maxtor and Ibm/Hitachi drives in the distant ppast, and stuck to WD and Seagate. However, I have recently read about WD drives failing, due to poor head parking mechanisms. It seems that hard disks, just like anything these days, are built to a price. Personally, I would go for a Seagate. If you wanted to spend a few extra dollars, maybe one of A/V surveillance drives. (these are designed to be run constantly). You probably don't need too much in the way of capacity. Rotational speed is 5900 rpm, I think. They come in 7200rpm versions as well. Really, it's not the issue it once was. Virtually any drive will do. However, backup your important projects to an external drive, after each session. Drives don't last as long as they used to. That is why you should use one of your SSD drives as your audio drive. These have a MUCH lower failure rate. 120gb should be plenty for you right now. I haven't had a "data streaming error" for about ten years now, due largely to the progressive improvement in bus speeds since the old UDMA days. Long story short... Use whatever you have, and make backups. Kim Oh, and I would resist the temptation to spend lots on a high capacity drive. (I TB and above..)I have had grief from these. Nothing wrong with an "old school" 320gb 7200 Seagate Barracu
creator: Kerry Galloway
date: 2008-12-02T06:52:13-00:00

Re: OT for dog lovers (warning, pix):
type: item
description: ow!) but leave anything alone that you don't have to mess with. The minute you get your .cfg the way you like it, back it up to another drive so you can get back to that setting in a jiffy. Besides crashes, other things can delete your PARIS.cfg - say a reinstall, or changing a setting via the "PARIS Configuration" menu item in the Project Window (if I recall, since this doesn't know about some of the features you can manually edit, this can potentially overwrite your edited .cfg with default values for the things it does
creator: Neil
date: 2008-12-02T09:55:53-00:00

Re: OT for dog lovers (warning, pix):
type: item
description: solved your problem and have any tips, I'd appreciate it. I've tried connecting to my ADAT device using two different DB9 straight through cables. Hey Guys, What version of the driver are you using? I have to admit, I haven't tried to sync an actual ADAT in a while. I have a couple of them beside me. I'll see if they still work. All the best, MikeHi Everyone, It's been tough to make progress this year, but I'm finally getting traction. I've just started testing a version of the PSCL that is designed to work with jBridge. For those who haven't used jBridge, it allows a 32 bit host to connect with 64 bit VST files. I just started testing it with some 64 bit Waves plugins. So far, so good. The updated PSCL has a low priority thread that checks for jBridge processes and moves them off the CPU used by the PARIS application. This way, we can run 64 bit VSTs on all but one available CPU cores, while not running into the thread-safety issues in the PARIS application. jBridge can be found here: https://jstuff.wordpress.com/jbridge/ My next move is to work on the kernel driver (scherzo.sys). I bought a new ASUS motherboard with a PCI slot, and the driver does not work with this new board. The new board uses a I/O MMU, which is a new thing for PCs. I suspect that this is the problem, but I'll know more next week. An I/O MMU puts the PCI bus behind a memory controller that has to be programmed in order to allow PCI cards to access main memory. It's an extra level of indirection put in place for security reasons. The driver was not designed for this kind of thing. I still haven't gotten the EV security certificate. The eventually rejected by documents that were signed by a justice of the peace. It's completely insane. An accountant or a lawyer will do just fine, but a judge can't be trusted. It's nuts. I'm going to go see a notery after I get the kernel driver updated. I only get a year on the certificate, so I think it makes sense to wait until I have this next phase done. That…
creator: Deej [5]
date: 2008-12-04T04:08:26-00:00

Re: OT for dog lovers (warning, pix):
type: item
creator: Rich[4]
date: 2008-12-04T17:25:25-00:00