Otherwise you kinda come off as a bit of a troll (which I'm sure you're not). We're here to help, but at least make a reasonable effort to help us help you before telling us the software we all use is not up to par. Telling us that "as usual" the audio engine is not up to par and then leaving out probably the most important information is just going to rile people up (which I see, it already has). You need to tell us which driver mode (ASIO, WASAPI, etc) and what audio buffer settings you are using before anyone here can help. It could well be that out of the box, CW used more aggressive buffer settings than your other software. You have not told us what buffer settings you have set in CW. Overall thinking is that some default settings in Cakewalk does not make optimal result on your system. in manual mention some special settings that are in plugin manager in how mono is handled. It could be running a mono plugin on stereo interleave track or other way around. Thinking that some special plugin here really raise cpu. This is another setting that may differ between daws what is default.įor me with Cakewalk the default threadscheduling worked the best in that it distribute even on 8 cores(4 physical with hyperthreading give 8 logical).Īnother setting made it use 4 cores only(don't remember which one), so changed it back.Īnd my reasoning with what is the largest project that runs normally? I did not bother with 64-bit engine yet, if that matters. If not related to cpu, something close to what you suggest - something wrong with audio engine - may be relevant. I run 64 samples ASIO buffers, and a 10 year old quadcore i7 (benchmarking at 5000, where modern cpu i9-9900k of today rate about 20 000) so old cpu in this regard. The example I mentioned it was added cpu, and when at 55-60%(task manager) or so, some crackles can appear. (With and without last plugin, and depending on preset you used) Larger latency give more headroom before crackles and pops.ĭid you look in task manager what cpu load is and what is ASIO buffer setting? So many things may differ in what daw have as load. Reaper and StudioOne add processing buffers apart from ASIO buffer setting etc. Again, though, what hits me is that other DAWs have no issue.ĭifferent daws may set different ASIO latency, and some have special features like Cubase/Nuendo ASIO guard or whatever it was. What is it? It's got to be fixed before anyone but hobbyists, if even they, would feel comfortable even starting a project with it. Cakewalk, you must know something about how you are handling audio in detail. I'm quite sure that Reaper and the wonderful Nuendo would have smiled through this, too. Please consider that asking me for specifics on my resources and all misses the comparison point. Went back to Cake and added VocSyn to guitar track - immediate audio dropuout upon hitting play. Added VocSyn to the guitar track for fun. Setup same song in Sequoia, same add of VocSyn afterwards. Three minute song, with a TrueVerb bus, Tony Maserati vocal plugin and Ozone 5 in the master bus.Īdded VocalSynth and immediate popping and clicking for three of the five types of effect. Created drum track in Superior 3, guitar raw input from mic'd amp, bass same, then sang a track.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |