Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

42 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi, here are things that I regularly use in order to prevent and solve problems and improve DAW performance: check that all drivers are up to date. For example, use a freeware tool like Dumo. If it finds outdated drivers just go to the hardware manufacturer's site directly and download it from there (in general I find that safer than to use a tool to do it for me) run Windows update to be up to date and to and make sure that no update has been downloaded that is still waiting for install or reboot (this has been a cause of sudden malfunctioning for me several times and is very easy to solve. However, considering your story I assume you've restarted enough and probably are up to date with Windows 10 itself) check that all other software is up to date. For example, use a freeware tool like SUMo. If it identifies outdated software versions, update the software from the software itself, you don't need to use the tool (or support the makers and pay for the function to let it download the software for you) to make sure you've got all the latest runtimes there are two handy downloads: AllinOne Runtimes (contains the following: .NET Framework 4.8 + Updates, Java Runtime Environment 8, DirectX 9.0c Zusatzdateien, Allgemeine Runtime Dateien, Microsoft Visual C++ Runtimes (v2005 - v2019), Microsoft Visual J# 2.0 SE, Microsoft Silverlight 5, Adobe Flash Player (Opera, FireFox, Internet Explorer), Shockwave Player 12. Each can be selected or deselected for installation) and Visual C++ Redistributable Runtimes All-in-One (This last one might be a bit more up to date but has only the C++ updates) run the different windows repair tools (Windows File Protection, Component Store Corruption, System Components, Rebuild WMI Repository, Reset Windows Update, Windows Installer (MSI)): you can find them by searching the web and find explanations for each how to do it or you can see if you can get a free trial of Window 10 Manager which has a very handy repair centre tab where you can execute them with one click use CCleaner to get rid of junk files, clean the registry (you can select what the program will check, will deleted and what not! If you don't understand how to use it don't but it is one of the few really reliable programs that perform this kind of actions so recommended to check it out. It also has many other functions, like startup manager where you can see which programs automatically start with Windows and prevent them from doing so if you don't really need them to start with Windows, etc.) check that PC power is set to maximum: 1. Set your computer's power for high performance - Go to: Control Panel>Power Options - Choose "High Performance" - Then click the "Change plan settings" button. Make sure both power options are set to "Never" check that no USB adapters can switch off power. On the Properties screen, click on Power Management tab and uncheck the option for “Allow the computer to turn off this device to save power” and click on OK. Disable power management for USB root hubs in the Device Manager. Open the Device Manager and expand the Universal Serial Bus controllers category. Right-click each USB Root Hub, click Properties and click the Power Management tab. Uncheck any boxes next to “Allow the computer to turn off this device to save power.” Check this after each big Windows update. Windows has the annoying habit to reset many options after an update... disable network cards, WIFI and Bluetooth if not used (Device Manager => network adapters, right-click and select disable device) check that you your graphics card doesn't install audio and other things than the driver itself. If you have an NVIDIA GeForce you can use NVcleanstall to get the latest driver, do a clean install and deselect everything that is not the main driver (other software, audio driver, telemetry etc.). check in device manager under 1) audio inputs & outputs that only the desired audio controller is being used (e.g. Focusrite) and no other device is being used (like NVIDIA) 2) sound video & game controllers (see 1)) On the same page as DUMo and SUMo you'll find many other tools to find problems (KC softwares). Other sites with many handy tools that might help you are Resplendence (LatencyMon, WhoCrashed, WhysoSlow etc.), Nirsoft and SoftwareOK (I regularly use many of the tools from these websites for different purposes, also to improve my workflow with windows and other programs) To find out what goes wrong on windows: try Control Panel\All Control Panel Items\Security and Maintenance\Reliability Monitor => click on the alarm signs to find out the details try other tools in the same Security and Maintenance directory like Windows Memory Diagnostics try Windows event viewer. Explanations for use are in the hyperlink. This records anything software does on your PC and might pinpoint a problem you have. try What's my computer doing Hope this helps!
  2. Thanks for sorting this out. I didn't know this in Cubase, but it covers for a large part what I had suggested earlier as options that I would like to see in a Chord Track. I would mainly use it in a comparable way: to help me get out of a writers block, boost my creativity and preferably: provide me other than the simple, standard chord progressions that are mostly used suggest other than standard voicings for different instruments Right now I use Toontrack's different options and Scaler and some other software once in a while, but having something build in would speed up things, and I would not be depending on some VSTs and have to exchange parts between VSTs. It might be complicated to implement a Chord Track that meets most of the wishes in this thread, but looking at the recent CbB improvements I think that the bakers are capable of surprising us more and more!
  3. Nice list! I would like to see implemented (partly overlapping with your list): you give in the key (or play the bass note) in which you want to write a song. Then you play a chord (and as option for those who prefer to select chords instead of playing) and a chord track tool gives you a random and/or selectable list with suggestions for different (and more complex) voicings, like for example these "10 Best Neo Soul Chords" you put in a chord progression and get other chord progressions as alternatives for that same part you put in a chord progression and get other chord progressions as suggestion for a next part the option to select the music style and have chords, progressions and timing/rhythm generated accordingly (e.g. like in Superior drummer and EZbass) the option to select the instrument and have chords, progressions and timing/rhythm generated accordingly (e.g. a guitar voicings are not the same as piano voicings) Most preferably the above implemented much more in-depth than common time with just 4 standard chords like you hear these days in most songs...(I long for the sixties and seventies with The Beatles, Jimi Hendrix, The Beach Boys, Chicago, Pink Floyd, psychedelic and symphonic rock,...when music was real music😬🧐)
  4. Hi. I get that it is frustrating if no one answers to you questions. There could several reasons why that happens. Maybe the questions is not clear enough, maybe it concerns something that in the eyes of others has very little priority, or maybe it is because only a limited number of members could answer the question and the have bigger, more urgent fish to fry, other questions draw the attention away, etc.... In this case, however, the problem as you state had already been fixed, which is great. Keep up the good mood and keep posting 😉
  5. Let's stop wasting time and let's make music, each on his preferred DAW 😘
  6. Apart from the possibilities that CbB provides for your problem (as indicated in the post here above which to me seem more quite good and fast), maybe you should try out the new Celemony Melodyne 5, probably the best de-esser around and a huge time saver for professionals😉
  7. Well, I think your review goes way beyond mine! Very informative👍
  8. Nice work! Now that it has been done maybe you could change the title to "Cakewalk and BandLab at KVR - Please vote!" I just wrote a review🧐. Curious to see how the KVR listing will develop...
  9. I'm confused: so the advice from the CbB release is wrong (that leads to 512 KB Playback and 256 KB Record with interface at 256 KB (only one setting possible for both Playback and Record so it can only be in sync with one at a time)? Next to that I thought that for playback during mixing (especially with extensive projects) it's even better to use 1024 KB or higher driver buffer size (meaning that after tracking you always need to increase driver buffer sizes for mixing and vice versa)
  10. My 10 year old RME PCIe at 96kHz, 24bit and 64 sample buffers gives me an effective latency of 0.7 ms and roundtrip of 3.4 ms I always wondered which one is the one you need to look at: roundtrip or effective latency? (I thought the latter when you're recording e.g. a vocal) However, I never felt that CbB was very stable at those settings, to be on the safe side I use 256 sample buffers (effective latency of 2.7 ms and roundtrip of 7.4 ms .
  11. Thanks for all the feedback! I found out that I've changed the setting myself long time ago, when I started to get pops and cracks. It was advised by CbB in the Version 2018-09 release notes: "To optimize playback and reduce the potential for dropouts or audio glitches, we recommend a Playback I/O Buffer Size value of about 512 (KB) if you are experiencing any performance problems. You can change the Playback I/O Buffer Size value in Edit > Preferences > Audio - Sync and Caching." (So you think that both Playback and Record I/O to 256KB is better?) Later on I found out that it was "thread scheduling" value 3 that gave problems. This however seems to have been fixed in the recent CbB releases. Using a simple project (some EQ, compression and two normal reverbs + one convolution) and a few audio tracks + many inactive tracks and inactive busses with preloaded FX from my template) I measured it today against against "thread scheduling" 2 which now shows the following during playing: thread scheduling 3: Audio Processing 6% (Max. 16%, jumps to 21% during pause and jumps to 16 again during play???), 35% (Max. 55%, jumps to 103 during a pause???), Engine Load, 0 Late Buffers thread scheduling 2: Audio Processing 7,5% (Max. 17%, jumps to 22% during pause) Audio Processing, 38% (Max. 54% jumps to 110 during pause), Engine Load, 0 Late Buffers (numbers are rounded averages since they change continuously). So at first sight some small performance improvements. Strangely enough when I stop the project the Max. values jump up and when hitting play again the Max. values drop significantly? I've got the latest RME driver for my AOI PCIe card, so that shouldn't be a problem. I make sure to always have the latest driver and software updates for anything on the PC (has become a bit of an obsession🥴). Things go reasonably well right now. I expected my 16-core Threadripper 1950X with 32 GB RAM and fast PCIe SSD drives to run smooth all the time, even under heavy workload. Still, if you don't pay attention to the many different Windows settings (sleep timers, GPU audio, power settings, wireless connections etc.) and other background processes, such a system can be disappointing. After tweaking it at many sides it's finally becoming nice to work with. Because of the many uncertainties introduced by other software I now use a program (ProcessKO) to disable any background process that is not needed for the system when I run CbB. This also seems to help a bit. System is now running 96kHz, 24bit + 64bit double precision engine (I wonder how useful the latter is and if it uses more resources) with latency of 2,7 ms at 256 (both Playback and Record I/O, according to your advice) samples buffer size. What I don't get is why its still possible to get pops and cracks (which happens rarely at the moment, touch wood...) when you see on the performance monitor that Audio processing and Engine Load are way below 100%? I've never seen one of the cores max out during an audio glitch. And why in some cases late buffers seem to be building up when a song project has been opened but is not playing???
  12. My bad. I wrongly assumed that in order to change the buffer size you needed to enable caching. Clearly you can change the buffer size without that. I noticed that playback was double (512 KB) the size of the record (256 KB) buffer size. Is that standard for CbB? Do you know why making them both the same size has a positive effect on latency or is it just by trial and error that you found it to be better?
  13. I checked this to see if it could be another tweak for my system. The CbB reference guide says: "Enable Read Caching and Enable Write Caching. Choosing either of these options lets Cakewalk use the Windows disk cache while reading or writing audio data. Cakewalk will usually perform best with all caching disabled, which is the default setting. If your computer has an older IDE disk controller, or a disk controller that does not use DMA transfers, enabling caching may improve Cakewalk’s audio performance." It seems to me that it is better to not use this option on a relatively new PC.
  14. In general I agree with you, however, in the case of CbB it is more nuanced. Many users have paid a lot for Sonar, which was rated among the very best of professional DAWs in several reviews (and of course less good in some other reviews, like is the case for other DAWs. "Beauty is in the eye of the beholder"😉), because it was a DAW answering to their high requirements. Since becoming CbB the DAW has quickly gained more options, has gotten a better workflow and has become more stable. Many of the old Sonar users that fit the profile of your description of current customers of high priced DAWs like Cubase (which are supposed to have higher requirements because they paid a lot for it), keep using CbB. I don't think that their requirements have become less just because the once expensive DAW has become free. Fact that they keep using it says a lot about the professional level of CbB. Since everyone can report bugs, complain on the forum or ask questions about anything I don't see why there would be less complaints because CbB is free. With any bug or problem it just makes sense to report it or ask how to get around it on the forum (asking is also free and the high quality of the CbB forum regularly attracts users of other DAWs for specific questions because it is well regarded compared to forums of expensive DAWs). So why would there be less complaints because it is free... You gave me the impression ("Free things usually garner few complaints", etc.) that in expensive DAWs more bugs are ironed out. My bad if misinterpreted your comments. The bugs in free are more acceptable in general, but not if you paid a lot for the DAW like Sonar users that continue to use CbB. And don't forget that there are several professional musicians and studios here on the forum. They can't afford to keep using a DAW that hampers their production... There are several users on the forum that use CbB next to other expensive DAWs. They prefer some things in one DAW and other things in another. I guess if you have Pro Tools, Cubase and are using CbB regularly or (as I understood form several most of the time) next to it it must be of comparable quality See here above. Most Sonar oldies would leave if CbB if it were not up to the task. And people spend many hours to produce a piece of music that they are emotionally attached to. Nothing is more discouraging and frustrating than to see it fall apart because of time consuming bugs along the way or a crash just before finishing the master. Because of that I think that especially with something like a DAW most users will not stick to it if it does not operate well, even when being free You mis the point: I merely pointed out that since CbB is free, the DAW is even much better and better maintained and upgraded than it was at the time of being an expensive DAW, that paying a lot for a DAW can still lead to failure and that (at least in my case) this free DAW is much better than the paid ones in the past. And yes, I'm very critical regarding workflow, options, bugs etc. just like I was when I paid top dollar. If the DAW doesn't fits my needs, I'll leave it for another (paid or free, I don't care as long as it can do what I need it to do) Or maybe they complain more, because they have more problems. Anyway, it is impossible to compare that. I think that the tone on the Sonar and CbB forum is was and is much more positive than usually found on other forums. People treat each other with respect and are very helpful. That might also explain the difference (and language) in forum topics🧐 You miss the point that Bandlab invests a lot continuously. Talking about ROI I assume a corporate point of view, not consumer. I assume you refer to this review Admiral Bumblebee Cakewalk review which is two years old...He doesn't include CbB in his current DAW comparison charts. Many of the issues have been improved since. Anyway, a good list of topics for the bakers to check what still could be improved from that list! Thanks, by the way, for that website! I like the in depth articles😃
  15. Good idea to have a (living, regularly updated) comparison table somewhere with the features that each DAW has. I really would appreciate to have a clear overview to see what each DAW can or cannot do and which one is better for what purpose. I completely disagree: I've never seen nor heard of a complex piece of consumer software (like DAWs, operating systems, video editing etc.) that was completely bug free and did not suffer from flaws that scared some users away Also if you pay less for a DAW you still expect it to work as expected In the past I paid the highest price for Cubase that they ever have put it on the market for to find out that after one traumatic year it never worked well on my pc, so I left for Sonar (and now CbB), which up till today has continuously been improved and become more stable, much to my satisfaction in a way that I've never experienced with Cubase. It seems that CbB is getting more stable and getting more features at a faster pace than in the days that it was priced comparable to the other top DAWs... Suggestion: have a look at the Cubase forum to see what what kind of problems they have with this i.m.o. currently (compared to CbB) overpriced DAW. Some topics form the first page from different users: "Cubase still crash and randomly appear message errors", "Automation Frustration", "Cubase 10.5.20 crashes randomly on Mac", "Cubase crashes every day!", "HANGS, FREEZES, DISAPPEARS, ETC,..." Not saying that Cubase is bad, for many people it does work well and just like with CbB many problems can be solved by pointing users to the right settings, or the problem is related to the operating system or another piece of software/hardware. However, it is not because it is expensive that it is more stable or better in any other sense. And I expect the same stability and functions from CbB as from Cubase. If CbB stops working well I change to another DAW, expensive or free. The thing that matters most for me is usability! ROI on a free product is a standard business model. Free products are often used as marketing tools. Look at websites with adds where you can download something a free tool. The adds pay for the tool. YouTube, where people earn money just by having viewers clicking their content and/or referring to another product, and so on. In the case of CbB it is a way to attract users to Bandlab (as far as I understood)
  • Create New...