Home » The PARIS Forums » PARIS: Main » REAPER PAF extension ready for download and testing!
() 1 Vote
REAPER PAF extension ready for download and testing! [message #102862] |
Wed, 18 March 2009 17:21 |
|
Hi all. I don't think this was specifically announced, but I'll make it official: Reaper now supports PAF import via an extension coded by developer Xenakios!
It's available right now for download at this link:
http://stash.reaper.fm/v/2421/libsndfilewrapper.zip
This should be considered a beta - it's not complete yet, but even in its present form it will allow the PC version of Reaper to load .paf files generated by the PC version of PARIS without limitation (ie 16 and 24 bit, 44.1 and 48k), and pafs generated by the Mac OS version of PARIS with limits (44.1 and 48 k 16 bit only - still pursuing the 24-bit versions).
Developer Xenakios reckons the problem with the Mac version of paf to merely be a bug in libsndfile (the open-source "library" created by brilliant coder Erik de Castro Lopo that he used to create the paf extension). I contacted Erik right away to ask him to check this over, got an immediate response asking for more specific info, passed the contact over to Xenakios who followed up, and now we wait for a fix. I can't estimate the wait time (it might be today or in two weeks), but don't worry, we're not giving up on it.
This version works for *importing* PAF into Reaper, not exporting PAF *from* Reaper. Exporting to PAF is more work. But it would *definitely* be desirable for those puppies to go back into PARIS as easily as they came out, so let's get this thing downloaded and tested and show our gratitude.
The prevailing ethos at Reaper is to get everything consistent across platforms, so I'd rate the odds that a Mac OSX version of the extension will eventually arrive as being pretty good.
I'm extremely happy with this first interaction with the Reaper coders. We asked for a feature of interest only to our small community of users of a long-discontinued platform; the fact that they built something that works this well for us, within *days*, is pretty exciting (although in fact I'd privately predicted "three days" ).
If you want an idea of "where we go from here", check this thread out (scroll down to post #9): http://forum.cockos.com/showthread.php?t=33427
"... being bitter is like swallowing poison and waiting for the other guy to die..." - anon
[Updated on: Wed, 18 March 2009 17:25] Report message to a moderator
|
|
|
|
|
|
|
|
Re: REAPER PAF extension ready for download and testing! [message #102872 is a reply to message #102863] |
Thu, 19 March 2009 11:08 |
|
Neil wrote on Thu, 19 March 2009 01:02 | Administrator <kg@kerrygalloway.com> wrote:
>the fact that they built something that works this well for
>us, within *days*, is pretty exciting
Within DAYS! Is that anthing like "Soon"?
Fucking amazing... and congrats to the Reaper-heads.
Neil
|
Like I said previously - the intent is to bugfix, reclaim and refurbish the word "soon".
And these are *definitely* the guys who can help us do it.
Check the timestamp on this post:
Quote: | 03-12-2009, 10:04 AM
kerryg
Use of "folder" character in file path causes media import to fail (FIXED)
Perhaps this has been covered before, but in Reaper 2.57 (Mac OSX), naming a folder "Understood ƒ" (option-f) causes the media imported from that folder to fail, with items being imported with zero length and no peak view drawn. Changing the folder name fixes it.
|
http://forum.cockos.com/showthread.php?t=33259
Check out the date of release of the bugfix:
Quote: | News:
March 16 2009 - REAPER v2.58. Fixes OS X filename issue, fixes Win9x compatibility! [download]
|
http://www.reaper.fm/
Aw, *four* days - Justin's slipping
Yeah, we *want* a relationship with these guys, and we want it badly. And as you can tell - there's even hope for the Mac guys if we can get OSX drivers happening for the PARIS hardware some day (not currently in the works, but - volunteers?)
"... being bitter is like swallowing poison and waiting for the other guy to die..." - anon
|
|
|
Re: REAPER PAF extension ready for download and testing! [message #102889 is a reply to message #102862] |
Fri, 20 March 2009 17:33 |
W Mark Wilson
Messages: 8 Registered: February 2009
|
Junior Member |
|
|
Way cool
M-dub
"Administrator" <kg@kerrygalloway.com> wrote in message
news:49c194d5$1@linux...
> Hi all. I don't think this was specifically announced, but I'll make it
> official: Reaper now supports PAF import via an extension coded by
> developer Xenakios!
>
> It's available right now for download at this link:
> http://stash.reaper.fm/v/2421/libsndfilewrapper.zip
>
> This should be considered a beta - it's not complete yet, but even in its
> present form it will allow the PC version of Reaper to load .paf files
> generated by the PC version of PARIS without limitation (ie 16 and 24 bit,
> 44.1 and 48k), and pafs generated by the Mac OS version of PARIS with
> limits (44.1 and 48 k 16 bit only - still pursuing the 24-bit versions).
> Developer Xenakios reckons the problem with the Mac version of paf to
> merely be a bug in libsndfile (the open-source "library" created by
> brilliant coder Erik de Castro Lopo that he used to create the paf
> extension). I contacted Erik right away to ask him to check this over, got
> an immediate response asking for more specific info, passed the contact
> over to Xenakios who followed up, and now we wait for a fix. I can't
> estimate the wait time (it might be today or in two weeks), but don't
> worry, we're not giving up on it.
>
> This version works for *importing* PAF into Reaper, not exporting PAF
> *from* Reaper. Exporting to PAF is more work. But it would *definitely* be
> desirable for those puppies to go back into PARIS as easily as they came
> out, so let's get this thing downloaded and tested and show our gratitude.
>
> The prevailing ethos at Reaper is to get everything consistent across
> platforms, so I'd rate the odds that a Mac OSX version of the extension
> will eventually arrive as being pretty good.
>
> I'm extremely happy with this first interaction with the Reaper coders. We
> asked for a feature of interest only to our small community of users of a
> long-discontinued platform; the fact that they built something that works
> this well for us, within *days*, is pretty exciting (although in fact I'd
> privately predicted "three days" :d).
> If you want an idea of "where we go from here", check this thread out
> (scroll down to post #9): http://forum.cockos.com/showthread.php?t=33427.
>
>
> --------------------------
> :: [ posted via the PARISForums ] ::
> :: kerrygalloway.com/ParisForums/ ::
> --------------------------
|
|
|
Re: REAPER PAF extension ready for download and testing! [message #102895 is a reply to message #102869] |
Sat, 21 March 2009 01:00 |
|
dnafe wrote on Thu, 19 March 2009 07:01 | Awesome news!
Now can anyone explain in layman's terms what the issue is with getting PPJs to open up in Reaper.
D
|
Sure Don, I'll take a layman's stab from my own "picked up as I go along" understanding of the situation.
Like most files, PPJs aren't designed to be human-readable inside; they don't have labelled sections that say, for example, "Fader One data". PPJs aren't encoded or obscured; the organizational system is just unknown to us at the moment.
Under normal circumstances you consult the file documentation (a separate index of what's stored where, what range of values a parameter can have, etc) to figure out where data is. We don't have those docs at the moment, and without info we can't build a translator - it wouldn't know where to look in the file to pull out the info for, say, Fader One.
We have two options open right now. Obviously the first and most preferable would be to get PPJ docs. Failing that, the second option is to figure out what's in our PPJs. Our end of that process is time consuming but not terribly difficult - turn knob, save, turn another knob, save, etc.
After we have that done, we then give them to folks who will take a peek at the changes inside for us. Finally, writing a translator plugin for Reaper is fairly routine work (for those with coding skills).
"... being bitter is like swallowing poison and waiting for the other guy to die..." - anon
|
|
|
|
|
Re: REAPER PAF extension ready for download and testing! [message #103147 is a reply to message #103145] |
Wed, 15 April 2009 17:32 |
|
This is PAF only, although we *definitely* want PPJ support too. This will let Reaper open your 24-bit PAF audio files directly on the edit screen (and naturally PAF is the only format you can work at 24 bits inside PARIS in).
For the uninitiated - PARIS creates two distinct kind of files. One is the project format, PPJ. PPJ is like a Cubase .cpr file or a Logic .lso file; it's basically your "song" or "project" and it contains mix info, the locations of all your audio regions, your FX presets, etc. It was never designed to be readable by another app.
PAF is an audio file format like SD2, AIFF or WAV (it's been characterized as a form of "pure" WAV). PAF is PARIS's native audio file format, and the only format in which PARIS can record at 24 bit resolution. PAF was always intended to be readable by other audio apps (Wavelab on PC and BIAS Peak on Mac have been able to read PAF since PARIS was in production). The only reason more apps don't support it is because PARIS didn't achieve the market penetration needed to convince many other software developers to support the format.
"... being bitter is like swallowing poison and waiting for the other guy to die..." - anon
[Updated on: Wed, 15 April 2009 17:35] Report message to a moderator
|
|
|
|
|
|
|
|
|
|
|
Re: REAPER PAF extension ready for download and testing! [message #108018 is a reply to message #108014] |
Fri, 10 January 2014 13:09 |
|
heya Matt - I have no idea about a 64-bit shim. does the extension not work in 64 bit? Those tasks that remain to be done on that extension are relatively trivial:
1) - write and submit a patch to libsndfile using the documentation we now have on PAF files (I can give directions, but I don't code) to clear up a longstanding "PARIS On Mac OS" bug with 24-bit PAFs, and
2) - write the part of the extension which permits PAF file writing in Reaper (currently it just reads .PAF files).
PPJ is another kettle of fish. Once again, my technical understanding is limited, but I believe they're binaries - they're not encoded, but they are compiled into a non-human-readable form, and we don't have that file documentation. They can be figured out via trial and error, but we haven't invested the considerable time that would be required.
"... being bitter is like swallowing poison and waiting for the other guy to die..." - anon
[Updated on: Fri, 10 January 2014 13:12] Report message to a moderator
|
|
|
|
|
|
|
|
|
Re: REAPER PAF extension ready for download and testing! [message #108827 is a reply to message #108826] |
Sun, 19 July 2015 14:29 |
|
Hi John - are they generated by PARIS on the Mac or PC? PC is solid - Mac PAFs have a bug at 24-bit.
1) Yes, that's what this does - lets you import PAF files into Reaper
2) You can bring them all in at once just as if they were WAV files and once in Reaper you can edit/add tracks etc.
3) They will not be time-aligned unless you exported them all from zero. However AATranslator can do that perfectly via the mechanism of OMF.
4) Yes. Reaper can't export PAF yet though - you'll have to render the edited tracks out as WAV files and re-import them into PARIS. We're working on getting PAF export ability to make this seamless, but AATranslator is a great alternative in the mean time.
"... being bitter is like swallowing poison and waiting for the other guy to die..." - anon
[Updated on: Sun, 19 July 2015 14:30] Report message to a moderator
|
|
|
|
|
|
|
|
|
Re: REAPER PAF extension ready for download and testing! [message #108860 is a reply to message #108832] |
Sun, 02 August 2015 14:48 |
JohnG
Messages: 57 Registered: April 2013 Location: Twin Cities, MN
|
Member |
|
|
Hi Kerry,
What I think are a few simple follow up questions regarding moving a project to reaper for mixing:
1) Pardon my ignorance, but how do you "render from zero"? Is there any quality loss from rendering?
2) If all the tracks started at zero, would I have to render from zero before importing them to reaper?
If they didn't all start from zero, is that the reason I would want to render from zero?
3) When I go into a paris project folder, there seem to be 2 types of files (other than PPJ, which I know reaper cannot use). Some that are paf and others that are OVW.
Do I need the OVW files imported into reaper as well and what are they for?
Thanks for your help. It is greatly appreciated.
John
John, Twin Cities, MN
|
|
|
|
|
|
|
Re: REAPER PAF extension ready for download and testing! [message #108865 is a reply to message #108864] |
Tue, 04 August 2015 17:35 |
|
There's a bug in 24-bit files generated by the Mac version of Paris. They weren't exported from PARIS Mac OS9 in that bit depth, by any chance?'
(never mond, I just reread your earlier post; they're PC, huh? try copying them onto your drive rather than reading them off the USB stick in case it's just not fast enough for realtime audio)
(another question that comes to mind - is your version of Reaper the 64-bit or 32-bit? and are you running Reaper on your PC? or on a Mac?)
"... being bitter is like swallowing poison and waiting for the other guy to die..." - anon
[Updated on: Tue, 04 August 2015 18:26] Report message to a moderator
|
|
|
Goto Forum:
Current Time: Sat Dec 28 23:07:42 PST 2024
Total time taken to generate the page: 0.02367 seconds
|