"apply fx to items as new take" with PLParEQ3

politcat · 11-13-2006, 08:26 PM

trying to do this crashes reaper. ??

i have this eq on every track so at some point i have to apply fx...

olzzon · 11-13-2006, 11:45 PM

Quote:

Originally Posted by politcat

trying to do this crashes reaper. ??

i have this eq on every track so at some point i have to apply fx...

Not to say, it couldn´t be Reaper, but in my experience,this is one of the more chrash prone plugs, in most hosts.
I haven´t tested in cubase though, have you used it in other hosts?
Just to find out whether its reaper or PLParEq

politcat · 11-14-2006, 03:59 AM

Quote:

Originally Posted by olzzon

have you used it in other hosts?
Just to find out whether its reaper or PLParEq

plpareq works fine in sonar and energyxt.

i have it on over 20 tracks in reaper running just fine. what happens when applying fx is you see the update bar thing go across but when it's done reaper freezes.

Dstruct · 11-14-2006, 05:00 AM

yeah, maybe it's something in reaper. does it crash always? yesterday i had a crash while rendering too. but it didn't happen on the next try ...

politcat · 11-14-2006, 08:25 AM

dandruff,
i tried it several times on different tracks, crashed every time.

how about "apply fx..." does that work for you?

are there option settings somewhere related to apply fx?

Dstruct · 11-14-2006, 09:35 AM

Quote:

Originally Posted by politcat

how about "apply fx..." does that work for you?

didn't really need/tried it yet. need some more midi functionality first ;-)

i also don't use this eq. the only fx i'm using are from voxengo and ohmforce ...

politcat · 11-14-2006, 10:15 AM

ok.

well i can render tracks with plpareq on them but not apply fx. so it must a reaper thing. justin??

i would really like to be able to apply fx since that is essentially the "freeze" function in reaper. argh!

pipelineaudio · 11-14-2006, 10:16 AM

Quote:

Originally Posted by politcat

dandruff,
i tried it several times on different tracks, crashed every time.

how about "apply fx..." does that work for you?

are there option settings somewhere related to apply fx?

check that in prefs\audio the rendering block size is the same as the latency you are using on your soundcard

politcat · 11-14-2006, 05:05 PM

they're the same

politcat · 11-14-2006, 08:09 PM

i contacted the plpareq dev to see if he could help. i got this response, which seemed fair:

--------------------
Judging from the comments on the forum for Reaper, this is not unique to PLParEQ.

http://www.cockos.com/forum/showthread.php?t=800

Since PLParEQ is compatible with every other known commercial DAW, including Receptor, and since Reaper appears to be a beta, or just released, version, I suspect that the problem lies with their implementation of the VST host protocol. Our list of tested and compatible DAW's is:

Fruity Loops, Sonar 5, Cubase VST, Wavelab, Samplitude 7+, Tracktion, Live 5, Receptor, Audition, others?

If PLParEQ were the only plugin not working properly, I would be more inclined to dig into why that is the case. But it appears that we are in good company. Hence, we will leave it to the developers of Reaper, for now, to try to track down why these plugins fail.

Cheers,

David McClain
Chief Technical Officer
Refined Audiometrics Laboratory
----------------------

it would be cool if justin or someone from reaper could chime in here.

Rednroll · 11-14-2006, 08:25 PM

What version of PLPar3 EQ are you using? I'm guessing, but are you using the FREE version of PLPAR3 EQ? I think the last free version was v1.96. At least that's what I have as my latest version....but they are currently not installed. From the v1.96 release David McClain made 2 versions. One was a Pentium 4 optimized version and the other was a Non P4 version. I could never get the Pentium4 optimized version to work on an Athlon processor machine and I would get similar crashes. I reported this to David and he made 2 versions for users who where running PCs with non P4 compatible processors. I don't know if he still does this for the latest pay versions.

Anyways, I have both FREE v1.96 versions available. It might be worth a shot to try the non-P4 version if you have it available. If you don't have it then I could probably upload it for you.

David McClain is great. He reminds me a lot of Justin in the great support and the speed he gets things done. If there's a bug between PLPar3 and Reaper, I think you are in the best hands around to get things fixed, having Justin/Christopher on one end and David on the other.

politcat · 11-15-2006, 03:58 AM

i have the last 3 versions, 2.19, 2.20, 2.21. the last 2 just involve a simple protection scheme so 2.19 was the last update function-wise. iirc they are the same otherwise. his response indicates they should work regardless of cpu.

david mcclain has always been responsive, like ralph zauni at rayzoon who goes way out of his way to help too. i only started hanging around here more in the last month but i hope justin shows up for this one. will turning this into a bug thread help?

pipelineaudio · 11-15-2006, 04:07 AM

I wonder if this is similar to the waves problem. RALabs is another fine Arizona company, though a little to the south. Im sure this will be worked out

pipelineaudio · 11-15-2006, 04:17 AM

Alright I tried a mess of diffewrent settings too, getting the same sort of crash

Strangely, looking in the folder, it had rendered the track fine with the fx...the file it rendered works perfectly., it just seems to crash as its adding the new take back to the project!

politcat · 11-15-2006, 04:27 AM

well...that IS good to know. so it's just a minor? bug. thx for checking pipe!

Rednroll · 11-15-2006, 09:42 AM

FYI, I think Justin is on vacation right now. This is the one time of year we let him do that after working 200 hours per weak on Reaper the rest of the year. So hold tight.

Justin · 11-15-2006, 06:41 PM

Quote:

Originally Posted by politcat

it would be cool if justin or someone from reaper could chime in here.

Just did some quick testing (I'm a touch ill here at the moment so I can't spend too much more time on it). Seems the versions of PLParEQ3 on the web site work fine. An older version did exhibit the crash, but it appeared to be caused by memory corruption from the plug-in. The reason it works for audio playback, I assume, is that it is being called from a different thread.

-Justin

politcat · 11-15-2006, 07:36 PM

thx justin. it must be me and the dll i have then.

hope you get better soon!

Rednroll · 11-15-2006, 09:31 PM

Quote:

Originally Posted by Justin

(I'm a touch ill here at the moment so I can't spend too much more time on it).
-Justin

You see what a vacation away from Reaper can do to ya? LOL!!! Hopefully, this is one of those contageous illnesses, that we have to put a warning disclaimer on the Reaper license agreement.

Warning: Too much time away from Reaper has been proven to have severe illness side effects.

Prescription: Create 2 new songs in Reaper and call me in the morning
Get well soon Justin!!!!

politcat · 11-17-2006, 07:18 PM

probably won't matter to anyone but for future reference...i'm now using plpareq3 version 2.21 and it works without a flaw in reaper. this eq is awesome, i can't do without it.

i really like the apply fx feature and being able to go back to a previous "take" if necessary. as good as freeze or better imo.

now i just have to figure out where to change settings, to render in mono instead of the apparent stereo default, for instance.