Reaper shows lots of promise, but very lacking in documentation, and is not as stable in vst as one might like.
I've not seen any significant projects done with reaper, a couple remixes of stems already done, and it doesn't come with any real quality mastering plugs and eq and such, there's a couple of re plugs that aren't bad, but most folks using reaper seem to be stealing sonar synths and plugs 'grin'.
Ofcourse none of the sonar tools work for reaper that are scripted, because the ui shows up completely different to reaper.
Also re-access interferes with window-eyes keystrokes, you can remap I know, but it's kind of a hassle.
But if you want plane jane recording on a light pc, reaper is good, I checked it out pretty thorougly back a few months ago,
and like I said, good suff, but lots of work needs to be done. What I mean by significant projects is one of us, doing work on it, also, you don't have really good midi editing.Not that I could see anyway, not like it is in sonar, but maybe that's improved.
I found many strange anomalies like trying to export loops that played fine, only to find that the space I'd edited out was still in the exported loops, and of course you've got a million key bindings ancd such, but enough stuff didn't work as expected for me to not give reaper the nod for a professional work a day studio, not yet anyway.
Also radius pitch correction and stretching is much better in protools and sonar, elastique is reasonable, but gives artifacts not as bad as the old soundforge stuff does, but considering the price of reaper, well, as I've always said, you get what you pay for.
But it's another choice, especially for those who like to tinker and play around, but access not withstanding, even taking that out of the equation, reaper is missing a lot of important things to make it a serious daw.
If x1 doesn't get going like we hope it will, my money will be on protools, and on the pc side, probably cubass.
Ross has been using it for years with ahk scripts he hired a programmer such as your self to do for him, and steinberg is a company I have long respected and used their products.
I have no doubt cubass is very stable and full of high end tools.By the way, my friend hasn't spoken up on the list yet, but he still can't install 7.5.2 on his machine, running xp.
Just won't go. Not at all. So he says he's going to write and call gwmicro, but pu that on your list to report, I had installation issues too, but mine finally went in. But I had to do it twice. Something is funky about the install routine. Thanks tom for all you do. We sure appreciate it.As much as i bitch about we, it's another choice, and anything nipping at the heels of the big guys will make thingsw better for all of us.
Make them not get lazy and make the little guy try harder.YOu know jaws better perform right, they got 20 programmers to gwmicro what 2 or 3 now?
Shame on the shark for not doing a whole bunch better and not just a little bit better to stay just far enough ahead to milk that cash crop right? grin'?
At 02:17 PM 11/26/2011, you wrote:
Thanks Jack and Indigo, I'll report the problem to GW.Extra thanks to you, Indigo, for this info. I'll install the 64 bit version just so I can complain from first hand experience. Then I'll try installing the 32 bit version and see if that works. I have a couple XP systems, but really nowhere to set them up for mixing now that my studio is trashed. So I'll first see if I can get this toilet to flush without overflowing and stinking up the house just in case it's one of those needle in a haystack situations.Regards, Tom On 11/26/2011 2:08 PM, Indigo wrote:Hi Tom, Rare that I get a chance to repay you for all the helpyou've provided for me. On win7 64, Wineyes 7.5.1 runs Reaper any version 64, but not while ReaAccess is running. With both running, Reaper freezes as soon as you open it. You need to wait for application manager to come up, close Reaper, and the whole system doesn't collapse if you back out that way. Meantime, NVDA, jaws and system access all run both Reaper 64 and ReaAccess simultaneously. You know, I think one's first and best experience of Reaper should be in XP, with Windoweyes 6.1. I mean true XP, not a virtual XP. The oldest machine you have around the house will probably run Reaper just fine, it was written to run on almost anything, 2 ghz, half a meg of ram, does just fine. You'll totally appreciate what ReaAccess is doing for you, with nice tracks you just arrow to to select, move anywhere along the time line with right left arrow keys, plus page up down for bigger jumps, press R to record, very much reminds me of Sonar 4, only with a million more options. ReaAccess lets you easily route any track to any track, literally anything to anything, press the letter I to enter the IO routing dialog, which is very intuitive. Tab through its settings, just hit escape to return to the tracks, no need to save settings made in the routing dialog.. At your tab keys you find recording options for the track you have arrowed to. After making your selections hit enter to keep them. The only stumbling block is configuring your audio and midi, in Reaper's options, preferences. You can get to the menus with F10, when they're not opening with the alt key. In preferences, you can read all the topics at your number pad, left click any topic to open it, then go to the tab key to move through settings. . All of configuring your audio and midi device speaks, just requires a tiny little extra move to get it done. Audio is the main topic, under that is midi devices, then buffering. When you tab to the edit box to enable your default midi device, you arrow down and it will read, but it will be disabled. To get it enabled, do the pointer routed to cursor command, find the name of your midi device at the number pad, right click it, go back to the arrow keys and check enable, and also enable for midi controller. Those are 2 separate checks to put in. There are 2 separate edit boxes where you need to enable your midi device. Keep on tabbing down until you've enabled both, then do the usual apply and okay. Other than that one little spot where the move over to the number pad is required, all else in Reaper's options preferences seems straight forward and more or less obvious. There are a ton of settings you don't need to change, they are for later use. To enter learning mode, so you can hear what all the keyboard shortcuts do without causing them to act, press F12, press F12 again to exit learning mode. The qwerty keyboard is not quite full of useful commands provided by ReaAccess, and more shortcuts at the number pad with numlock on, and there is a list of hundreds of possible actions not yet assigned to shortcuts, just plug in the shortcut key combination you want. Hope this is enough to get you going, but I'll gladly help up to the limits of my knowledge in Reaper, Indigo L . 11/26/2011 12:27 PM, Tom Kingston wrote:I've been meaning to give Reaper a whirl seeing as I'm not really doing anything in my studio and I don't feel like battling Sonar bloat, complexity, and accessibility. But someone on the GW list said that Reaper 64 wouldn't run on Win 7/64 and blamed it on Window-Eyes. Then one of the guys at GW installed Reaper 64 on Win 7/64 and it ran fine. That is until he installed ReAccess. Then it blew up. And it didn't matter if Window-Eyes was running or not. I'm not sure, but I think he said he even tried it on his laptop at home which doesn't even have Window-Eyes installed and the same thing happened. So, knowing absolutely nothing about Reaper, I'm wondering if installing the 32 bit version will work on Win 7/64, where to get the latest (or best) builds, and any documentation, tutorials, podcasts, etc. And while we're on the subject, has anyone compared Reaper versus Audacity? From what little I've heard I get the impression that Reaper is the better of the two. Any comments? Thanks much, Tom
For all your audio production needs and technology training, visit us at www.affordablestudioservices.com or contact Chris Belle cb1963@xxxxxxxxxxxxx or Stephie Belle stephieb1961@xxxxxxxxxxxxx for customized web design
