Home » The PARIS Forums » PARIS: Main » Reaper + Paris + Adat Sync -> what to expect?
Reaper + Paris + Adat Sync -> what to expect? [message #105751] |
Mon, 25 October 2010 10:06 |
drfrankencopter
Messages: 137 Registered: July 2009
|
Senior Member |
|
|
Okay, so I took the plunge, and got myself an RME 9652 and a second Adat card for my MEC, and plan to sync Paris and Reaper.
I'm new to reaper, and picked up Kenny Gioia's video tutorial to get up to speed. I think I'm going to like it, and can imagine using Reaper for the bulk of my mix/edit requirements. But, I still want to use Paris as a control surface, submixer, and for IO. I will likely migrate to a fully native setup eventually, but it looks like the Reaper + Paris combo will let me do that gradually.
As I wait for my RME card to cross the ocean I can't help but wonder about how the sync between the two applications will work. Assuming I get the ADAT positioning protocol working. Here are my questions:
1) How fast does Reaper slave to Paris? Will it add significant latency to the transport buttons?
2) When the transport is stopped in Paris does moving the jog wheel still send ADAT position protocol information over to Reaper? Does the Reaper 'now line' and time display move in sync with the Paris one while the transport is stopped, or does this only work while in 'Play'?
3) Since Reaper has plug in delay compensation, when I connect my Reaper subgroups out via ADAT to my MEC, will there be a delay, or does reaper compensate for this by buffering ahead? Or do you have to disable delay compensation to run as a slave to sync in?
4) Can Reaper read 24 Bit PAF files? How about write?
I've got a few other questions that I can't quite remember right now...I'll add them later.
Cheers
Kris
|
|
|
Re: Reaper + Paris + Adat Sync -> what to expect? [message #105752 is a reply to message #105751] |
Mon, 25 October 2010 11:20 |
|
yep, Reaper is a definite "win", I have now left Logic completely behind and I'm doing full album production on Reaper.
I doubt you'll have much trouble with APP, it "just worked" for me after about fifteen minutes of searching out settings.
1) The sync is fast over here - less than a second. I'm pretty sure I could tweak it lower if I felt the need.
2) Can't recall about it tracking the jog/shuttle wheel, I'll have to check it out when I'm in the studio
3) IIRC I believe Reaper buffers ahead.
4) As soon as you install the Xenakios libsndfile wrapper extension, Reaper will read 16 and 24 bit PAF files directly just as if they were WAV files.
[One exception/caveat - libsndfile still contains a crippling bug that affects Mac-generated versions of 24 bit PAF only, currently they just produce noise until someone takes on the job of fixing the bug and submitting a patch to libsndfile. PARIS PC-generated PAFs work perfectly.]
As to Reaper writing PAF - the wrapper doesn't yet support this but Xenakios said it could certainly be made to do it. Xenakios, not being a PARIS user himself and having a lot of other demands on his time, took it as far as what we asked for - import capability - but opened up the source code to the wrapper so we'd be free to finish it off ourselves if we wished. The developers have left Reaper beautifully extensible.
As far as the scope of that job, Xenakios reckons he made the wrapper from scratch in "a couple of hours"; he reckons coding in the writing functionality to be a somewhat longer undertaking but I'd still guess it to be a pretty approachable project. Also on the "to do" list is porting the extension so it works with Reaper OSX as well.
"... being bitter is like swallowing poison and waiting for the other guy to die..." - anon
[Updated on: Mon, 25 October 2010 11:26] Report message to a moderator
|
|
|
|
Re: Reaper + Paris + Adat Sync -> what to expect? [message #105754 is a reply to message #105753] |
Mon, 25 October 2010 12:30 |
|
Yes, absolutely - libsndfile allows reading and writing, it's just the code hasn't yet been written in the wrapper to take advantage of all the possibilities. I'd guess he's just being specific about what the wrapper can do as it currently exists.
I know little about coding but it's my understanding that aside from the myriad apps on all platforms that rely on libsndfile for the conversion of many file types - PAF being only one of many - it's also what the entire Linux OS relies on.
In Reaper you bring PAFS in as PAFs and work directly with them on the edit screen without conversion. Of course if you "glue" two PAFs the resulting file will have to be whatever output format you've specified in "Project Settings" as your default file type, which won't yet include PAF.
But we're darned close to that day
"... being bitter is like swallowing poison and waiting for the other guy to die..." - anon
[Updated on: Mon, 25 October 2010 12:34] Report message to a moderator
|
|
|
|
Re: Reaper + Paris + Adat Sync -> what to expect? [message #105765 is a reply to message #105755] |
Wed, 27 October 2010 10:30 |
|
Hey Kris, have you checked to see how much of ReaRoute (Reaper's own kind of ReWire equivalent) is exposed in the Reaper SDK here? I might be talking out my butt here but at first glance I wonder if Senderella plus ReaRoute might give you everything you need to bolt PARIS and Reaper together in a kind of "ReWire Lite" way - particularly if you ask Mike to expose any useful info from the drivers, I know he'd be more than happy to do that.
Man, it's refreshing to look at PARIS in 2010 and actually see more fun possibilities and open doors ahead than there were just a few years ago. Granted the work to implement the ideas now has to come primarily from us in the community - but it seems there are less things today that are automatically closed doors.
"... being bitter is like swallowing poison and waiting for the other guy to die..." - anon
[Updated on: Wed, 27 October 2010 10:34] Report message to a moderator
|
|
|
|
|
Re: Reaper + Paris + Adat Sync -> what to expect? [message #105789 is a reply to message #105788] |
Mon, 01 November 2010 02:20 |
|
Sounds like you've already got a handle on the best way to keep 16 individual tracks "live" through PARIS. Besides individual tracks you can also take advantage of Reaper's routing flexibility to quickly assemble submixes and bus them from Reaper - save routings you like as Reaper templates.
Bussing Reaper tracks into PARIS for mixing:
- in Reaper, create a new track and name it eg. "Drum Bus"
- shift or alt-select the Reaper tracks you want bussed together into PARIS, and drag them onto the "Drum Bus" track (they're now "foldered" under it, so to speak)
- click the "I/O" icon on the "Drum Bus" track
- uncheck "Master/Parent Send" to take them out of the "master outs" and click "add new hardware send" to send them to an appropriate ADAT out
- if you want FX in the bus drag the FX track in too; if not, drag it out
If you use AATranslator of course there's another method of getting PARIS tracks into Reaper for further work:
- In PARIS, render an OMF and use AATranslator to turn it into a new Reaper RPP
- in your current Reaper session choose "insert > tracks from template"
- once you're in the "insert" dialogue, switch the "files of type" to "RPP"
- find your converted PARIS session and insert it into your Reaper session (it adds the tracks below whatever track you have selected)
ADAT sync and PARIS OMFs both use "samples from session start" as their timeline so this ought to give sample lock (I haven't verified this through testing but I haven't noticed any timing differences).
You've probably already noticed that the "synchronization settings" dialogue (rightclick bar/time counter in the transport) gives access to detailed sync settings - if you've got a modern PC, try tweaking the sync to get faster lock. Can't remember how much I messed with settings myself, the lock between the two never bothered me on my box.
"... being bitter is like swallowing poison and waiting for the other guy to die..." - anon
[Updated on: Mon, 01 November 2010 02:21] Report message to a moderator
|
|
|
Re: Reaper + Paris + Adat Sync -> what to expect? [message #105790 is a reply to message #105787] |
Mon, 01 November 2010 02:25 |
|
I'm not using a control surface with Reaper yet, although I'm mulling using an iPad to get some remote functions. Mike's discussed making a MIDI driver for the C16 to allow it to show up under Win7 as a control surface. A Reaper extension's comparatively easy after that.
"... being bitter is like swallowing poison and waiting for the other guy to die..." - anon
|
|
|
Goto Forum:
Current Time: Sun Dec 29 03:50:18 PST 2024
Total time taken to generate the page: 0.01254 seconds
|