Hi Space Boy - I did a quick search but didn't see anyone getting this.
I've been using Reaper 1.28 for a few days with no problems till I copied FreEQ Boy to my VST directory and inserted it in a track in Reaper. The first thing I did was register, the FreEQ Boy and Reaper windows went white and I got a "Reaper not responding" msg box which let me end the apps. I then brought Reaper back up and inserted FreEQ Boy again (it had registered) but the windows went white again after I brought up an IE then went back to Reaper.
Any ideas about that?
Thanks,
Kyle
FreEQ Boy v2.03 and Reaper v1.28 - windows go white
-
- KVRian
- 951 posts since 11 Jan, 2004 from Netherlands
Hi,
There are a few problems with Reaper. I also posted, on the Reaper forum, a strange problem I encountered when using Extra Boy Pro in an earlier version of Reaper.
I am currently working on the next generation of all my plug-ins. I have spent a tremendous effort on compatibility issues (not that I had a lot to do) However, compatibility is at 100% for all other hosts except Reaper - the new kid on the block.
I have found that the problems change from one release of Reaper to the next.
My conclusion - something in Reaper is not quite right/stable.
It is amazing how many times I've made custom fixes in my plug-ins, where the host developer first claims the problem is with my plug-in and then later releases a patch which fixes the problem.
Get in touch with the Reaper developers - they still have some work to do.
There are a few problems with Reaper. I also posted, on the Reaper forum, a strange problem I encountered when using Extra Boy Pro in an earlier version of Reaper.
I am currently working on the next generation of all my plug-ins. I have spent a tremendous effort on compatibility issues (not that I had a lot to do) However, compatibility is at 100% for all other hosts except Reaper - the new kid on the block.
I have found that the problems change from one release of Reaper to the next.
My conclusion - something in Reaper is not quite right/stable.
It is amazing how many times I've made custom fixes in my plug-ins, where the host developer first claims the problem is with my plug-in and then later releases a patch which fixes the problem.
Get in touch with the Reaper developers - they still have some work to do.
-
- KVRAF
- Topic Starter
- 2049 posts since 18 Sep, 2003 from Seattle USA
Yes - I think that's true concerning plugins. It's just a tad early to try and get in heavy production with Reaper just yet.Space Boy wrote: ...Get in touch with the Reaper developers - they still have some work to do.
I plan to switch back and forth between Traction2 and Reaper (when it's ready) kind of like I used to do between Adobe Audition and Sonar. I don't know if that'll pan out but I wanted to try out some newer hosts. Audition especially seems to have a bunch of old code in it that isn't too optimal, Sonar is gettin that way IMO. We'll see if the newer hosts can do the trick...
-
- KVRist
- 101 posts since 18 Mar, 2006
Hi, I'm the developer of REAPER.
I just tested the demo version of FreEQ boy with REAPER 1.40 and it worked fine. Is there another
version I should test with?
Thanks,
Justin
I just tested the demo version of FreEQ boy with REAPER 1.40 and it worked fine. Is there another
version I should test with?
Thanks,
Justin
-
- KVRian
- 951 posts since 11 Jan, 2004 from Netherlands
And when you click on the "Load EQ" button - what happens?deadbeef wrote:Hi, I'm the developer of REAPER.
I just tested the demo version of FreEQ boy with REAPER 1.40 and it worked fine. Is there another
version I should test with?
Thanks,
Justin
P.S. I just tested V1.40, some things have been fixed, but not this one.
-
- KVRAF
- Topic Starter
- 2049 posts since 18 Sep, 2003 from Seattle USA
OK - I had a chance to do some testing. I'll just go ahead and post this here - I assume Reaper and Elevayta are working together on this.
Anyway this example is using FreEQ. I load FreEQ v2.03 into the Reaper v1.42 demo as an insert in the bassd track. Next I start Reaper by hitting Play, the bassd track is now putting out a whopping +23db peak, I hit reset on FreEQ and the track puts out the proper db. Over in Tracktion I have tried the same thing but the test track plays at the normal db level. I export the EQ from FreEQ while in Tracktion with the thought that I'll Import it over in Reaper and try it again. In the FreEQ instance in Reaper I hit the Import EQ button but Reaper loops the cpu at 100% and never comes back till I stop Reaper and Restart.
That's why I made the comment that Reaper isn't 100% ready for production yet - it's because of the varienty of VST plugins that can bring a host down. I've seen this happen in Cool Edit/Audition, Cakewalk, Sound Forge - seems like it's tough to get that interface tweaked so it works in every case. Good luck guys - I have faith in you! -Kyle
Anyway this example is using FreEQ. I load FreEQ v2.03 into the Reaper v1.42 demo as an insert in the bassd track. Next I start Reaper by hitting Play, the bassd track is now putting out a whopping +23db peak, I hit reset on FreEQ and the track puts out the proper db. Over in Tracktion I have tried the same thing but the test track plays at the normal db level. I export the EQ from FreEQ while in Tracktion with the thought that I'll Import it over in Reaper and try it again. In the FreEQ instance in Reaper I hit the Import EQ button but Reaper loops the cpu at 100% and never comes back till I stop Reaper and Restart.
That's why I made the comment that Reaper isn't 100% ready for production yet - it's because of the varienty of VST plugins that can bring a host down. I've seen this happen in Cool Edit/Audition, Cakewalk, Sound Forge - seems like it's tough to get that interface tweaked so it works in every case. Good luck guys - I have faith in you! -Kyle