A revolution in PARIS-REAPER workflow just happened! [message #109138] |
Sun, 17 April 2016 09:48 |
|
Heya folks - building on Reaper's libsndfile wrapper created by Reaper user Xenakios some years back, coder Matthias Kronlachner has now built libsndfile *export* capabilities into the wrapper. You'll find it, free of charge (donationware), over here at Matthias' site, and I'll link it from the "Useful Third Party Software" page as well.
[If you're going to use this software, please do send Matthias a donation here (right side of page, you'll see the link)!]
Matthias' updates to the wrapper (which as you will recall allows Reaper to read PARIS' .paf audio files directly as a native format as if they were e.g. .wav files) now allows Reaper to *write* .paf files as well. Just drop your PAFs into Reaper, edit/tune/process however you like, render them out and import them directly in PARIS once again.
[Why is working with .paf format important when PARIS can work with .wav files? Because .paf is the only 24-bit file format PARIS fully supports. And you never need to worry about stripping PAF files before flying them back into PARIS like we often have to with WAV files!]
You can now take, say, eight tracks of drums tracked in PARIS as 24 bit .pafs, fly them directly into Reaper, edit them using Reaper's cutting edge tools, render them in place, check they have the same names as the original - and PARIS should simply accept them in place of those originals, all without the tiresome mess of creating intermediary wav files. This will certainly be a game changer for workflow over here!
Installation (Win/Mac OSX) is simple - just follow the included instructions. Let Matthias know via his website if you find any bugs.
[EDIT: The default "consolidate/render tracks" settings in Reaper didn't give me working results, but the following settings worked perfectly:
Consolidate to: libsndfile (.au .avr .caf.... etc)
Format: .paf (PAF (Ensoniq PARIS) )
Encoding: signed 24 bit PCM
Byte Order: Little-Endian (Intel Byte Order)
By the way, Reaper also writes "-consolidated" at the ends of all consolidated (i.e. exported) tracks and with the addition of that text, file names can get too long and awkward for poor ancient ol' PARIS to handle, so I used a free and easy-to-use OSX batch renaming utility called NameChanger to trim off the excess.]
Vive PARIS!
- Kerry
[heads up: I've found that each time I update Reaper I have to reinstall the extension; not a big deal, but if after an update you open a previously working Reaper song and it says "unrecognized file types", just click the installer to reinstall the extension - it takes about three seconds over here]
"... being bitter is like swallowing poison and waiting for the other guy to die..." - anon
[Updated on: Thu, 20 April 2017 15:03] Report message to a moderator
|
|
|
|
|