Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by Teegarden

  1. Well, I think your review goes way beyond mine! Very informative👍
  2. 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...
  3. 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)
  4. 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 .
  5. 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???
  6. 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?
  7. 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.
  8. 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😃
  9. 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)
  10. Nice first two suggestions. Regarding the stability: For me at least CbB has be come much more stable with better workflow and the bakers do nothing but continuously improving stability and fixing bugs each day (that doesn't mean that it is bugfree, of course). I've got the impression that many others feel the same when reading forum topics. Would you mind sharing which problems you have encountered? In many cases with some forum help problems can be solved! Often it is not the DAW but a pc setting or a plugin or another piece of software/hardware/driver that leads to problems. In case it is the DAW itself the bakers usually respond well and manage to fix the bug if you provide enough information (hardware and software versions incl. drivers, crash dump, observed actions that lead to the problem, etc.)
  11. Just a few years ago when Cakewalk by Bandlab was still Sonar the reviews were raving, see Sonar reviews, for example. At that time the cost for the DAW were comparable to the other top paid DAWs like Cubase and Pro Tools. CbB is leaning on decades of professional development. There was a delay in development when Gibson ended Sonar, before CbB was well established, but ever since the development has been going really well, ironing out old bugs and introducing new highly desired features. Any DAW has its own advantages as well as bugs, so having a particular bug in CbB does not mean that switching to another DAW will relieve you from all bugs, just look at other forums and you'll see many bug or other problems all over the place. It is just very hard to make a program that is compatible with a virtually unlimited number of hardware and software configurations and on top of that comforts everyone's personal workflow and options wishes. I would say today it is one of the best DAWs compared to all other DAWS (both paid and free). This year CbB was again ranked in the top ten best DAWS with as main downside just that it is Windows only... In the mean time many other new features and bug fixes have been introduced, so the future just looks good! When you notice the feedback from the bakers, who in general listen and respond quite well on this forum (as well as the often excellent feedback from users when you have a problem, which has helped me out many times) it just seems like CbB is thriving. Regarding professionality and options you can't go wrong with CbB. You get at top priced DAW for free (why that is possible is covered elsewhere on this forum) However, like Lord Tim said the best DAW is the one that works best for you.
  12. I have no clue what could be the cause. However, once in a while my pc shows this kind of behaviour and in those cases so far it appeared to be a new Windows update that was waiting for a restart. Once restarted the problem is gone. Maybe this helps. BTW did you check that all your drivers are the latest versions? More info about the hardware and software and the kind of project might also give more clues
  13. If your graphics card with the latest Geforce driver supports the WDDM graphics driver and you have installed the latest Windows 2004 update you can switch on "Hardware Accelerated GPU Scheduling". It is turned off by default, so in order to make use of it you need to switch it on. This feature is introduced in order for Windows to be able to offload most of GPU scheduling to a dedicated GPU-based scheduling processor. It can be enabled on the Advanced Graphics Settings page. The settings page can be accessed via Settings -> System -> Display -> Graphics settings. I just installed both latest updates and my already fast system feels much snappier😃. The way I understand how it works it must free some CPU capacity which now can be used for other tasks like your DAW.
  14. Hillmy, you're right, let's try to help more😉 Oscar, I would not expect too much from your system as far as can be concluded from the information you provided so far. However, its a nice challenge to see if it can be improved. Could you give a list of your hardware and software. It would help figuring out where the main bottlenecks are and what can or cannot be done about it. Do you have any budget? (I understood 100 USD is too much) On Ebay you can find FOCUSRITE Scarlett 2i2 Audio Interfaces in the 40-50 USD range. These are quite good. There are plenty of other options and second hand sites as well. On a slow PC all tuning might make a difference. So I advice you to also have a look at this thread with pc optimisation software links. Some handy free tools to check your PC harware and software status: HWinfo, gives full details on your hardware DUMo, gives a list of installed hardware device drivers, and of the available updates. Don't use this program to update, just use the info to find the driver on the manufacturer's site if it needs to be updated SUMo, gives a list of installed software incl. version and what updates are available You might find some other free utilities on the same KC Softwares website that could be usefull, like HDD/SSD status, RAM status + upgrade capability indication, based on motherboard empty slots, etc. ProcessKO, I use it to make a list of background processes like the ones from adobe, printer etc. Whenever I want maximum power I can quickly stop these processes from running in the background. You can also easily restart them with it.
  15. The question was if a geforce gtx 960 could help render audio in cakewalk or help improve the program in some way. Your answer was: "You want a "graphics" card to render audio? o_O" I tried to point out that the question of OP was a logical and very valid one while your reaction seemed to suggest the opposite. Did you even read the hyperlinks in my post? Here's another one: Why The Future Of Real-time Audio Processing Could Be In Graphics Cards (article on Pro Tools Expert). To get back to your last reaction: if you look at the forum you'll find plenty of questions about performance issues, latency and how to get a project run smoother, so apparently that "very capable sound card" is not enough in many cases (and yes, many other factors like CPU, settings in CbB like thread scheduling etc. could be the culprit, but my own machine which is fast with RME PCIe sound card (low latency), 32 GB RAM and fast SSDs also regularly runs into problems with bigger CbB projects with many FX plugins). Great if your sound card is all you need, but others have different projects and needs. The point is that it doesn't matter that a sound card is made to process sound. Of course it is. The point is that performance is depending on several different hardware components and that in this example a GPU might eventually help projects run better. Ergo, the sound card alone is not always sufficient and any help from other hardware is welcome if that would make projects run smoother. Unfortunately the CUDA development is not there yet, but there are several indications that in the (near?) future GPUs might play a role in audio processing. I would love to have it and would make good use of it.
  16. It is certainly possible to render audio on a GPU. Cuda cores are being used for many different computing tasks and there were already a long time ago initiatives to use GPUs to offset the CPU: using-your-graphics-card-process-plug-ins (published 2008) Have You Heard What a GPU Can Do? - A Revolution in Audio Processing (published 2009) GPU DSP — When You Can’t Have Enough Cores (published 2019) I'm surprised no one referred to this, maybe its not so well known. Still hope that (especially now that PCIe busses and other communication parts are getting much faster) in the near future it will be possible to use CUDA cores in CbB.
  17. Isn't this a nice case where you could use Arranger track? Selected the whole song, allocate it to one section and move that section one measure?
  18. If you play keyboard (or guitar probably also, maybe to a bit lesser extent), you might be able to do whatever you want with the TEControl MIDI Breath and Bite Controller 2. I think it comes the closest to what you can achieve regarding realistic virtual instruments. All imaginable controllers van be allocated the way you want (as far as I understood) and it sounds highly expressive. Ramiro Gómez Massetti has a YouTube channel with many examples on how to use this controller to create string ensembles for example. There are also other YouTube channels with videos where this controller is linked to an electrical guitar to play sax or trumpet for instance. Probably best results with virtual instruments like the ones from Audio Modeling or Sample Modeling.
  19. Good idea, it could be an option where you can make them taller or shorter, just like you can make them narrow and wide. Maybe another option is that you could (user selectable) have the fader pop out when selected or when hovering over the meter. What I really like is the lay-out of Sonalksis FreeG (a free plugin!) which I started using for mastering/gain staging thanks to one of the excellent tutorials CbB Gain Staging of Creative Sauce. I would love to see a similar functional fader build in into CbB.
  20. I get the problem with muscle memory. However, by sticking to the original functions you also block an entire group of new users from quickly getting used to navigating CbB. My personal experience is that if you get a clear list of changes for a keyboard/mouse (you could attach a pdf to each new update with all shortcuts and an annex with changes from the old shortcuts, or put between brackets an old shortcut after the new one) it is not that hard to get used to the new functions and develop new muscle memory. Especially not in the case of "old" users that are already used to standard Windows functions for other purposes. My main problem with CbB is also the not always intuitive way functions work, which costs me more time than expected.
  21. I fully agree. CCleaner is in that respect very transparent (in contrast to many other tools like that). The good thing of CCleaner is that everything you do you can fully tailor to your needs so you can be sure nothing that you want to keep will be deleted. CCleaner is handy to switch of processes that otherwise automatically start with Windows, but that you don't need in the background. Next to that CCleaner can take away a lot of junk files and you can tell it where it has to look for junk and check what will be deleted and what not (see it as a significantly enhanced Recycle Bin). My experience with very slow running older computers from others that regularly ask for PC help is that after some Windows tweaking and especially running several tasks of CCleaner these systems were suddenly usable again. There appeared to be many files spread over the HD that could have been deleted a long time ago. I guess with the latest Windows and new PCs these problems will be much less thanks to improved software and hardware developments. However, I personally do use it for many years also for cleaning the registry. Many unused items are left behind that have no function so I like to get rid of them. You can see exactly what will be deleted before you execute CCleaner, so its easy to see what you want to keep and what is absolutely safe to delete. I do however understand that many people are afraid that registry cleaners might do more harm than good. I know what I'm doing and have never had any problem that I could somehow relate to deleted registry entries, but others might want to stay away from that.. Good advice bitflipper, everyone interested in doing something with the registry and in tuning his PC should certainly try to understand it first by doing his homework. Nice to see you also have good experience with those. I also always use Blackviper's advice and settings en CCEnhancer makes CCleaner's Recycle Bin function even better. I'm going to check out Tweakhound, never used that one before.
  22. Hi Neil, ShutUp10 is not supposed to have any effect on the DAW or plugin functionality. For an older system it might just make the difference you need. It is a long list of options that can be deactivated so I guess it's certainly worth using ShutUp10. It does not run in the background, it just deactivates many options and when you close ShutUp10, it does not stay in the background. Al it does is take just over 1 MB of disk space. I understand you can't upgrade much more, but if you have the possibility try to get the maximum amount of RAM.
  23. I would never use bloatware (if you refer to pre-installed software that comes from third parties without you asking for it). According to Computerworld (article is from 2015 so slightly dated), Signature PCs from Microsoft are free of third-party software and supposedly start up 104% faster, shut down 35% faster and have 28 minutes more battery life than the same laptops with bloatware. Computerworld also gives directions how to get rid of bloatware. Logically every additional process that runs on your computer will consume a tiny bit or more of your processing power. Today's PCs are fast enough to handle many background processes, so I wonder if stopping them makes a lot of difference (never took the time to measure possible differences). However, I like to have as much power available for my DAW so I eliminate every possible process that I don't really need. O&O ShutUp10 is a program that I use to stop as many MS processes as possible the only things I leave are the Windows Update settings where they state Recommended: "limited"or "no" If your serious using this program you will need to check for updates after each windows update and run that latest version again: Windows regularly switches back on settings that were switched of and keeps adding new features that run in the background. Another program useful for eliminating background tasks and processes (and also for deleting junk files etc.) that I run regularly is CCleaner: under Tools-> startup you can find several tabs with options to prevent software from running automatically in the background. Cheers
  24. Hi, I always build my own DAW systems, keeping in mind that I also want to be able to work on them and do photo/video editing. Always a large quality desktop case with good airflow and place for everything I might want to build in. Checking a few websites with the most recent info helps a lot. If you search for custom DAW or build your own pc you'll find plenty of information. Hardware site forums also usually have dedicated threats. Here are some sites: https://www.logicalincrements.com/articles/build-pc-music-production-audio-daw https://www.tomshardware.com/topics/pc-builds https://www.scanproaudio.info/2020/02/27/2020-q1-cpus-in-the-studio-overview/ Having had Intel for years, AMD is currently my favorite for several reasons. With most configurations you'll get more for your money and they have PCIe 4.0 on board, which gives you a much higher data transfer rate with SSDs (and your video card). Yes, Intel has in some cases higher single core speed, but with my 1950X Threadripper (which is already a few generations old) I've never experienced any problems in that respect with large demanding audio projects in CbB. The benefit of having many cores at relatively high speed is not neglectable. Windows 10 keeps also improving multi-core support under the hood, so that will probably only become better. If you go for such a system make sure you've got high speed quality RAM (minimum 3200 MHz, the best for AMD seems to be somewhere around 3600 MHz, but that could change with newer systems) and if the price is not too much try to get at least 32 or 64 GB of it. These systems are also relatively easy to overclock, but I would not start with that. Basic configurations are fast enough these days. Try to have a fast PCIe SSD as startup disk (0,5 to 2 TB) on which you also have your CbB projects. Next to that a large PCIe SSD with your audio libraries and if needed a normal 8 or 10 TB HD for backups etc. Of course everything depends on your budget and storage needs. Since larger SSDs are finally slowly entering the market that might be the ultimate way to go. You can scale down on all these components and still have a nice working DAW PC. There are people around that have 8 or 10 your old configurations and are still productive with it. For the rest I fully agree with Colin Nicholls. You can do it yourself, or go to dedicated PC builders and ask them to put your favorite components together. Don't forget to optimise the BIOS and Windows settings for DAW use (like switching off power management in USB ports , set Windows to high performance etc.). There are many sites including this one where you'll find how to do that. If needed, I could compile a full list with all the information that I've gathered over time about DAW optimisation. Good luck!
  25. Thanks, I don't have this library but I'm going to study it and see how you've constructed an orchestral template. Very useful as a start for other orchestras as well I hope!
  • Create New...