Reaper crashes (was: Took a Reaper Track to Nashville)
in [Cakewalk]
|
Prev: Asus Eee PC
Next: Drive Benchmarks
From: Sue Morton on 22 Apr 2008 08:07 Odd stuff. Actually I haven't experienced too many actual 'crashes'. (I wish it would, then I could get a debug log.) Reaper just locks the machine up hard, big red switch is needed to get it going again. In the beginning this was when I tried to manipulate my Lynx ASIO driver settings, but not consistent. I might go in and out of that panel without changing anything a dozen times, then it would lock up. Or lock up while playing audio (only). My Lynx ASIO drivers need a higher latency in Reaper than they do in Sonar. Also in Sonar, the Lynx MME drivers perform equally well as the ASIO, however they do not work well at all in Reaper (my Lynx does not have WDM drivers). I think I have sorted out most of the ASIO driver issues by playing with some of the different options in Reaper. However it still locks up the machine at random times. Then I still have the workflow issues with it I've mentioned before... When I have more time, I plan to get some information to the Reaper folk on these things. -- Sue Morton Glennbo wrote: > In news:X20Pj.5020$iK6.1583(a)nlpi069.nbdc.sbc.com the killer robot "Sue > Morton" <867-5309(a)domain.invalid> grabbed the controls of the > spaceship cakewalk.audio and pressed these buttons... > >> I hear ya on that one. I'm so tired of fighting the software. >> Unfortunately Reaper is in that same boat for me, I still have >> crashes and performance problems in areas where they don't exist >> with Sonar :-( > > What kind of crashes? The only crashes I've had so far with Reaper > were from trying to use old plugins that were possibly VSTs wrapped > by Cake's VST wrapper. I just created myself a favorites folder with > the plugins I know I can trust, and stay away from the older stuff. > I am however able to use all the Timeworks stuff, all the DB-Audio > stuff, TTS-1, PerfectSpace, and some other plugs that came with Cake. > The DSP factory plugs or whatever they were called that came with > Sonar 1 or 2, will *every* time crash Reaper. Those even say as they > are detected that they aren't licensed to use with anything else > though.
From: malachi on 22 Apr 2008 08:24 "Sue Morton" <867-5309(a)domain.invalid> wrote in message news:9ykPj.8275$GE1.4293(a)nlpi061.nbdc.sbc.com... > Odd stuff. Actually I haven't experienced too many actual 'crashes'. (I > wish it would, then I could get a debug log.) Reaper just locks the > machine up hard, big red switch is needed to get it going again. > > In the beginning this was when I tried to manipulate my Lynx ASIO driver > settings, but not consistent. I might go in and out of that panel without > changing anything a dozen times, then it would lock up. Or lock up while > playing audio (only). My Lynx ASIO drivers need a higher latency in > Reaper than they do in Sonar. Also in Sonar, the Lynx MME drivers perform > equally well as the ASIO, however they do not work well at all in Reaper > (my Lynx does not have WDM drivers). > > I think I have sorted out most of the ASIO driver issues by playing with > some of the different options in Reaper. However it still locks up the > machine at random times. > > Then I still have the workflow issues with it I've mentioned before... > > When I have more time, I plan to get some information to the Reaper folk > on these things. What kind of hardware are you running it on? My system is an Intel 975 series motherboard with a Core 2 Duo processor. The only glitches I've encountered were due to incompatible plugins (ok, one strike against Reaper, some plugs don't digest well, but most do). I'm also running it on my Lenovo dual pentium laptop without a hitch. malachi
From: Sue Morton on 22 Apr 2008 09:36 ASUS P5K3-Deluxe WiFi Core2 Duo E6850's (3ghz each) on 1333 FSB, two matched 1GIG DDR3 1333 memory (2 GIG total), SATA 3Gs in AHCI mode on the intel chipset, Intel P35/ICHR9 chipset with Fast Memory Access technology. I am having no lockups with anything on this system except Reaper. Sonar experiences various crashes from bugs that have been reported and confirmed, so I know that's not my system. Adobe Audition is more stable but doesn't have the features I need. Reaper has mega workflow problems for me, most are not glitches (though some are, like frequently not chasing MIDI controllers from the begining, if I stop and restart MIDI playback), they're just not programmed in, like me saving my project then importing audio from somewhere else, when I go to do a "save as" I am pointed at the import directory and not the audio projects directory. Reaper leaving *.rea* files in any directories I have imported from, even though I have selected the option to save imported audio in the project directory. Things that like drive me crazy in workflow situations. -- Sue Morton malachi wrote: > "Sue Morton" <867-5309(a)domain.invalid> wrote in message > news:9ykPj.8275$GE1.4293(a)nlpi061.nbdc.sbc.com... >> Odd stuff. Actually I haven't experienced too many actual >> 'crashes'. (I wish it would, then I could get a debug log.) Reaper >> just locks the machine up hard, big red switch is needed to get it >> going again. In the beginning this was when I tried to manipulate my Lynx >> ASIO >> driver settings, but not consistent. I might go in and out of that >> panel without changing anything a dozen times, then it would lock >> up. Or lock up while playing audio (only). My Lynx ASIO drivers >> need a higher latency in Reaper than they do in Sonar. Also in >> Sonar, the Lynx MME drivers perform equally well as the ASIO, >> however they do not work well at all in Reaper (my Lynx does not >> have WDM drivers). I think I have sorted out most of the ASIO driver >> issues by playing >> with some of the different options in Reaper. However it still >> locks up the machine at random times. >> >> Then I still have the workflow issues with it I've mentioned >> before... When I have more time, I plan to get some information to the >> Reaper >> folk on these things. > > What kind of hardware are you running it on? My system is an Intel > 975 series motherboard with a Core 2 Duo processor. The only > glitches I've encountered were due to incompatible plugins (ok, one > strike against Reaper, some plugs don't digest well, but most do). > > I'm also running it on my Lenovo dual pentium laptop without a hitch. > > malachi
From: Sue Morton on 22 Apr 2008 09:44 I haven't tried any plugs in Reaper yet, whether external or Reaper's. For MIDI playback, I'm using SFZ free player for my testing. I also tried the TTS-1 but haven't yet tried the multi-routing you posted a short while ago. -- Sue Morton Glennbo wrote: > I've only had problems with old DX plugins. I think all of them were > wrapped with Cake's VST wrapper too. I've put the ones I use and > know I can trust into my favorites folder, and haven't had any > problems since.
From: malachi on 22 Apr 2008 13:12
"Sue Morton" <867-5309(a)domain.invalid> wrote in message news:gRlPj.2594$I55.2155(a)newssvr22.news.prodigy.net... > ASUS P5K3-Deluxe WiFi Core2 Duo E6850's (3ghz each) on 1333 FSB, two > matched 1GIG DDR3 1333 memory (2 GIG total), SATA 3Gs in AHCI mode on the > intel chipset, Intel P35/ICHR9 chipset with Fast Memory Access > technology. > > I am having no lockups with anything on this system except Reaper. > Sonar experiences various crashes from bugs that have been reported and > confirmed, so I know that's not my system. Adobe Audition is more stable > but doesn't have the features I need. > > Reaper has mega workflow problems for me, most are not glitches (though > some are, like frequently not chasing MIDI controllers from the begining, > if I stop and restart MIDI playback), they're just not programmed in, like > me saving my project then importing audio from somewhere else, when I go > to do a "save as" I am pointed at the import directory and not the audio > projects directory. Reaper leaving *.rea* files in any directories I have > imported from, even though I have selected the option to save imported > audio in the project directory. Things that like drive me crazy in > workflow situations. > -- > Sue Morton > What I'm getting more and more is that if you are primarily audio-centric in your work, Reaper is mighty nice, but if you are MIDI-centric, best to stick with something else. I don't use MIDI except for drums and an occasional keyboard part, and for what I do it seems to fill the bill. But I guess if you need sophisticated MIDI functions, use what works for you. I'll bet that Justin will greatly expand the MIDI capabilities sooner or later, tho. As far as your Reaper glitches, maybe something in the code doesn't play well with your chipset. I'm experiencing pretty stable performance from it, so maybe it's a compabibility issue specific to Reaper and your mobo. I dunno. malachi |