Going Quad Core
in [Cakewalk]
|
Prev: lame-3.98b7.tar.tar (gz)
Next: DAW and PowerPoint
From: kitekrazy on 14 Apr 2008 21:56 Glennbo wrote: > In news:8b3d7$4801f03c$19774(a)news.teranews.com the killer robot John > Braner <me(a)myhouse.com> grabbed the controls of the spaceship > cakewalk.audio and pressed these buttons... > >>> Noel also just said that plugin processing is done serially for all >>> plugins in a particular FX bin, which means if you have several CPU >>> hungry plugs in a bin together, they will all be assigned to the same >>> core, rather than their load being distributed across the available >>> cores. >>> >> Q6600 quad core works fine here. OK, I have the same comp/eq plug on >> all tracks and then just some other stuff on one or two tracks (or >> busses) - but everything is pretty enely split and I'm running a >> *hell* of a lot more than I could on a single core 3.2 GHz P4. > > I've got some songs that have so many CPU hungry plugs that I can see Sonar > breaking a sweat trying to play them back at 1.5ms latency. I still have > S5, so I don't have the per core meters, but when the counters and VU > meters start becoming visibly laggy, and the CPU meter is dancing into the > upper limits, I can tell it's at the edge. I'm only running a Core 2 Duo > 2.4Ghz machine, but the same kind of project in Reaper purrs like a kitten. > I ran that benchmark test from dawbench.com on this system. Reaper blows away Sonar 7. I could run Reaper with my Terratec EWX at 2.9 ms with AVG and ZAP running in the background. I've never been able to run that low of a latency with a lot of apps running. Reaper is very impressive for the price so I bought. Plus I noticed you can run FX from other networked machines.
From: kitekrazy on 14 Apr 2008 23:05 Glennbo wrote: > In news:xXTMj.4179$iK6.540(a)nlpi069.nbdc.sbc.com the killer robot > kitekrazy <kitekrazy(a)sbcglobal.net> grabbed the controls of the > spaceship cakewalk.audio and pressed these buttons... > >>> I've got some songs that have so many CPU hungry plugs that I can see >>> Sonar breaking a sweat trying to play them back at 1.5ms latency. I >>> still have S5, so I don't have the per core meters, but when the >>> counters and VU meters start becoming visibly laggy, and the CPU >>> meter is dancing into the upper limits, I can tell it's at the edge. >>> I'm only running a Core 2 Duo 2.4Ghz machine, but the same kind of >>> project in Reaper purrs like a kitten. >>> >> I ran that benchmark test from dawbench.com on this system. Reaper >> blows away Sonar 7. I could run Reaper with my Terratec EWX at 2.9 ms >> with AVG and ZAP running in the background. I've never been able to >> run that low of a latency with a lot of apps running. >> >> Reaper is very impressive for the price so I bought. Plus I noticed >> you can run FX from other networked machines. > > Reaper does some way cool things that Cake never thought of, and it's > blazingly fast. I wish the Cake doods would get it together, but unless > they do a complete re-write of their audio engine, I don't see how they'll > ever get Sonar to perform as well. I did this stress test tonight. > > This was playing with 82 plugins, and no glitches at 1.5ms latency. > > http://members.cox.net/vdrums/Troublemaker/Trouble2.jpg > > Plugin list: > > 1 Drumkit From Hell Superior (with a half a gig of drums loaded up) > 1 Yellowtools Independence Free (with about a quarter gig of data) > 1 DVS Saxophone > 1 DSK Brass > 1 TickyClav > 2 SFZ > 25 Sonitus Reverb > 17 Timeworks EQ > 19 CompressorX > 9 PSP Vintage Warmers > 1 ReaComp > 1 Bass Chorus > 1 BJ Tremolo > 1 Sonitus Multiband > 1 db-audio Mastering Limiter > I wanna know where you got that Reaper skin. That's really nice. What sounds were you using in Yellow Tools Free?
From: kitekrazy on 15 Apr 2008 01:41 Glennbo wrote: > In news:xXUMj.8396$V14.7481(a)nlpi070.nbdc.sbc.com the killer robot > kitekrazy <kitekrazy(a)sbcglobal.net> grabbed the controls of the > spaceship cakewalk.audio and pressed these buttons... > >>>>> I've got some songs that have so many CPU hungry plugs that I can >>>>> see Sonar breaking a sweat trying to play them back at 1.5ms >>>>> latency. I still have S5, so I don't have the per core meters, but >>>>> when the counters and VU meters start becoming visibly laggy, and >>>>> the CPU meter is dancing into the upper limits, I can tell it's at >>>>> the edge. I'm only running a Core 2 Duo 2.4Ghz machine, but the >>>>> same kind of project in Reaper purrs like a kitten. >>>>> >>>> I ran that benchmark test from dawbench.com on this system. Reaper >>>> blows away Sonar 7. I could run Reaper with my Terratec EWX at 2.9 >>>> ms with AVG and ZAP running in the background. I've never been able >>>> to run that low of a latency with a lot of apps running. >>>> >>>> Reaper is very impressive for the price so I bought. Plus I >>>> noticed >>>> you can run FX from other networked machines. >>> Reaper does some way cool things that Cake never thought of, and it's >>> blazingly fast. I wish the Cake doods would get it together, but >>> unless they do a complete re-write of their audio engine, I don't see >>> how they'll ever get Sonar to perform as well. I did this stress >>> test tonight. >>> >>> This was playing with 82 plugins, and no glitches at 1.5ms latency. >>> >>> http://members.cox.net/vdrums/Troublemaker/Trouble2.jpg >>> >>> Plugin list: >>> >>> 1 Drumkit From Hell Superior (with a half a gig of drums loaded up) >>> 1 Yellowtools Independence Free (with about a quarter gig of data) >>> 1 DVS Saxophone >>> 1 DSK Brass >>> 1 TickyClav >>> 2 SFZ >>> 25 Sonitus Reverb >>> 17 Timeworks EQ >>> 19 CompressorX >>> 9 PSP Vintage Warmers >>> 1 ReaComp >>> 1 Bass Chorus >>> 1 BJ Tremolo >>> 1 Sonitus Multiband >>> 1 db-audio Mastering Limiter >>> >> I wanna know where you got that Reaper skin. That's really nice. > > It's a skin called "Troublemaker" that I modded. > > You can grab it from here. Put it in the "Color Themes" folder of Reaper. > > http://members.cox.net/vdrums/Troublemaker/TroubleMaker.zip > > Thanks! I like that one. Your screen shot looks brighter. >> What sounds were you using in Yellow Tools Free? > > I used a Rhodes electric piano, tambourine, fuzz guitar, and space echo. >
From: Phoenix on 16 Apr 2008 14:11
I have not yet had a chance to test out my new system as to whether I can get lower latency than before (heck, I just got all the H/W installed and Windows!) but on the system that just died most recently I ran at 5.8 or 11.6--often 11.6. The new m-audio drivers seemed to default back to that even when I reset them to 64, and I got tired of re-adjusting them and having to rerun wave profiler (didn't revert to older drivers cos the new ones did fix some BSODs). I notice the new install also "auto-detects" at 256 samples, but that's without Sonar installed. First I install, then I make TI images, then and only then will I fiddle around with the settings! I went quad-core because I had to upgrade, the price was reasonable (thanx again G'bo for putting me onto mWave), and I figured the apps would catch up with the processors eventually...not using onboard graphics, though, kite--if you're gonna work with any video, I'm not an expert but I'd say get a videocard with it's own memory. Just my 2c USD. "Sue Morton" <867-5309(a)domain.invalid> wrote in message news:9duMj.5725$GE1.1235(a)nlpi061.nbdc.sbc.com... >I haven't found latency to be an issue except when recording live tracking >to playback. Or the case where latency was actually too high and a synth >couldn't handle it. It was Sonar 3 (I think), and the Roland VSC synth (I >think). I had raised the latency for a complex mixing job, and had >forgotten to lower it back down. Midi was a mess with that synth, and it >took me awhile to realize it was the buffering. Dropping latency back down >to 'normal' solved the problem with the synth. > > I generally run everything at 11ms latency unless tracking to playback. I > can run with less, and often do because I forget to raise it after > tracking :-) 11ms seems to keep my Lynx One happy. > -- > Sue Morton > > Organfreak wrote: >> Glennbo <vdrumsYourHeadFromYourAss(a)cox.net> blatted: >>> In news:5fk404tjhrs8adhv5ehdeej2r8n3lfvfg1(a)4ax.com the killer robot >>> Organfreak <plonk(a)plinkety.plunk> grabbed the controls of the >>> spaceship cakewalk.audio and pressed these buttons... >>> >>>>> I would expect that you should be able run all day long at 1.5ms >>>>> just like I do. All but a handful of my projects in Sonar play >>>>> without looking stressed at 1.5ms. That's actually 3.0ms round >>>>> trip through the input and output buffers and running 44.1Khz >>>>> 16bit. In Reaper, I'm running 44.1Khz 32bit using ASIO which is >>>>> set at 1ms, which is 2ms round trip through the input and ouput >>>>> buffers. It displays in the upper right corner of Reaper. >>>>> >>>>> http://members.cox.net/vdrums/Troublemaker/ >>>>> >>>>> I hadn't tried to drop it to 16bit so far, but I can run complex >>>>> projects with tons of effects all day long set like this, and it >>>>> never breaks a sweat. >>>> >>>> Forgot to specify that I am, of course, using ASIO. I can't see >>>> where I could adjust it downwards; the slider is full-left at 5.8 >>>> ms. >>>> >>>> My buffers are both set at only 32, with no read or write ahead >>>> eneabled. >>> >>> In the Delta control panel on the tab labeled "hardware settings" a >>> DMA buffer size of 64 samples should get 1ms @ 44.1Khz. I just set >>> Sonar 5 to ASIO set like that, played my song El-Six-Es and it had >>> pops and clicks several times through the playback. I can run that >>> same latency using WDM in Sonar, but not ASIO. In Reaper, I can run >>> ASIO at 64 samples and never get a pop or click. I haven't bothered >>> trying using WDM in Reaper, since ASIO is working so well. >> >> Thanks. What a dumbass I am; I had forgotten all about that! I had >> the MF set on 256, no wonder! 128 gets me to 2ms, haven't actually >> tried it out yet. > > |