Jump to content

Teegarden

Members
  • Content Count

    8
  • Joined

  • Last visited

Community Reputation

6 Neutral

Recent Profile Visitors

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

  1. 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!
  2. 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!
  3. Thanks. It could be that I've updated the plugins and it happened afterwards, I also organised the plugins in different directories. I would expect CbB to be able to keep referring to the right plugin when moved or updated (in case of small updates). Maybe something that can be improved?
  4. It was a wild guess, sometimes I accidentally (de)activate a certain function which leads to unforeseen issues (although in my example I had those tracks hidden once on purpose and forgotten about it). Anyway, I meant anything that can be hidden/out of sight, including take lanes Regarding take lanes: maybe experimenting with Recording Mode settings in Preferences. I use Sound on Sound instead of Comping. Maybe that would fit your workflow better if you had comping mode selected so far (Btw, I just noticed that this selection is saved per project, not as standard setting in CbB: preferences without my standard project template loaded showed Comping selected)
  5. Hi, This was my first post, put in in Q&A but I suddenly remembered that the problem described below also happened a few weeks ago (I forgot with which plugins) after I had CbB 2020.04 installed. Before that update I never had this kind of problem, so maybe it is related to the last official release. I made a standard project template with many plugins pre-inserted (all deactivated, not consuming CPU at the start) and busses. So far, each time I opened the template all worked well. Since I've updated CbB the template worked well most of the time except for the following error that I got after a few days and also again last week: The following plugins are referred to by this project but could not be found: FabFilter Pro-R (Bus: 'R-ambie') FabFilter Pro-R (Bus: 'R-plate') FabFilter Pro-R (Bus: 'R-hall') Expurgate (Bus: 'FX-gate') FabFilter Pro-C 2 (Bus: 'DR-SQSH') The plugins are greyed out and when clicked upon I get the following text: Cakewalk Missing Plug-In Stand-In This plug-in is missing or improperly installed on your system. The original plug-in state is saved by this stand-in, and will be restored if you save the project and subsequently load it on a system where the plug-in is properly installed. Plug-In data (bytes): 456 However,...I can find the Fabfilter plugins in the plug-in manager and in the Audio FX menu and insert them on the same bus where the greyed out instance of the same plugin sits. That works well, but then I've got one not working instance greyed out (with my favorite plugin settings...) and a new one working but without my predefined favorite start settings... The Expurgate plugin seems to have vanished? So, I guess I'll need to reinstall. For the rest all seems to work as expected. I have the following questions: Does anybody have an idea what happened, is this possibly related to the latest CbB update or is there another idea what could be at the root of this problem? Is there a way to redirect the new instance of the same plugin to the settings of the greyed out plugin? Is there a way to backup plugin settings in a template (or project file) so that I don't have to redo the settings each time this kind of problem happens I also noticed in the past that when you update certain plugins, they are not always recognised as an update of an existing plugin that is used in a project, so all settings are lost. Is there a way to prevent this? Can I move a topic posted in the wrong place from one forum part e.g. Q&A to another e.g. Feedback? I tried to find guide lines how the forum works but didn't find it (probably overlooked) For the rest, it's impressive how CbB has improved over time, I hope that the audio magazines and websites will start including it in tests with the main paid DAWs like Pro Tools and Cubase. I'm convinced it should come out at least as good... Thanks for developing such great flexible, professional and free DAW! System specs: Windows 10 64bit with all latest updates (incl. runtime redistributables etc.) except for the big Win 10 May 2020 update (according to Will_Kaydo that seems to introduce new problems) AMD Threadripper 1950X 32Gb 3200 MHz RME HDSPe AIO GeForce GTX 1050 Ti (audio, telemetry etc disabled) Separate SSDs for programs and sound libraries Thread scheduling model 2 Optimised all possible audio workstation settings I could find (processor throttling and dynamic frequency scaling, high performance, wireless connections, wake up timers and so on) All software and drivers up to date
  6. Did you check if there are no hidden tracks? I once had a similar situation with a track that was hidden and I tried all kinds of things, deleting tracks etc. It made me crazy. In the end I used the "Show all tracks" option and found the problem. In the reference guide you can find different options to hide/show tracks, busses etc. Just another wild guess: maybe the project somehow triggers Melodyne externally if you also have a stand alone version installed next to the Sonar integration, or Melodyne is triggered by another plugin or track through routing?
  7. You can also download the installer of All in One Runtimes at sereby.org: https://sereby.org/download/All%20in%20One%20Runtimes It contains the following (each item can be selected/deselected before install and is regularly updated): .NET Framework 4.8 + Updates Java Runtime Environment 8 DirectX 9.0c Extra files General runtime files 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 (Internet Explorer Plugin)
  8. I made a standard project template with many plugins and busses . So far, each time I opened the template all worked well. I'm not sure if it is related to the latest CbB 2020.04 update, but since I've updated the template worked well a few times but today suddenly I got the following error: The following plugins are referred to by this project but could not be found: FabFilter Pro-R (Bus: 'R-ambie') FabFilter Pro-R (Bus: 'R-plate') FabFilter Pro-R (Bus: 'R-hall') Expurgate (Bus: 'FX-gate') FabFilter Pro-C 2 (Bus: 'DR-SQSH') The plugins are greyed out and when clicked upon I get the following text: Cakewalk Missing Plug-In Stand-In This plug-in is missing or improperly installed on your system. The original plug-in state is saved by this stand-in, and will be restored if you save the project and subsequently load it on a system where the plug-in is properly installed. Plug-In data (bytes): 456 However,...I can find the Fabfilter plugins in the plug-in manager and in the Audio FX menu and insert them on the same bus where the greyed out instance of the same plugin sits. That works well, but then I've got one not working instance greyed out (with my favorite plugin settings...) and a new one working but without my predefined favorite start settings... The Expurgate plugin seems to have vanished? So, I guess i'll need to reinstall. For the rest all seems to work as expected. I have the following questions: 1. Does anybody have an idea what happened, is this possibly related to the latest CbB update or is there another idea what could be at the root of this problem? 2. Is there a way to redirect the new instance of the same plugin to the settings of the greyed out plugin? 3. Is there a way to backup plugin settings in a template (or project file) so that I don't have to redo the settings each time this kind of problem happens 4. I also noticed in the past that when you update certain plugins, they are not always recognised as an update of an existing plugin that is used in a project, so all settings are lost. Is there a way to prevent this? For the rest, it's impressive how CbB has improved over time, I hope that the audio magazines and websites will start giving it an honest comparison with the main paid DAWs like Pro Tools and Cubase. I'm convinced it should come out at least just as good... Bakers, thanks for developing such great flexible, professional and free DAW! System specs: Windows 10 64bit with all latest updates (incl. runtime redistributables etc.) except for the big May 2020 update (according to Will_Kaydo that seems to introduce new problems) AMD Threadripper 1950X 32Gb 3200 MHz RME HDSPe AIO GeForce GTX 1050 Ti (audio, telemetry etc disabled) Separate SSDs for programs and sound libraries Thread scheduling model 2 Optimised all possible audio workstation settings I could find (processor throttling and dynamic frequency scaling, high performance, wireless connections and so on) All software and drivers up to date
×
×
  • Create New...