Jump to content

gstring

Members
  • Posts

    13
  • Joined

  • Last visited

Reputation

1 Neutral
  1. Thanks Promidi for the link to report the issue. I'll see they follow through with a fix for this.
  2. Seems like a new bug in CbB. The Midi SELECT and SMART tools stop working after about an hour of edits in PRV requiring the program to be re-booted. Any one else seeing this?
  3. Thanks scook. You cleared that up better for me, as I wasn't sure where the actual data folders would be situated. That seems straightforward enough.
  4. Thanks Scook for taking your time to help me with this. I've been struggling with my CW setup for years after doing so many upgrades. Fortunately, this is a new pc platform for me and I've only just started rebuilding my DAW, so I don't have too much to lose at this point. The link you provided to do a clean install looks like the best approach for me to take. I really don't understand how to use directory junctions, but it gives me something else to look into for future consideration.
  5. How can I clear historical file folder paths before doing a fresh install of CW by Bandlab and Sonar? I've just completely uninstalled CbB and Sonar Platinum after inadvertently removing and renaming some plugin folders.... big mistake. Nothing was working right after the changes so I'm starting over. The problem is that the CbB installation will not let me browse to select different storage locations than what I had before and I'd like to set things up a little differently this time. I'd like to install my OS and program files on a 465 GB NVME M.2 SSD, and place all VST plugins, VSTi stuff and sample files on a separate 1.92 GB SSD, but Bandlab is forcing me to put some of this on a magnetic HDD, which I want to reserve strictly for my music projects. Sooooo.....Is there some way to clear out the historical file location paths and start over from scratch? Can I just delete the Users\me\AppData\Roaming\Cakewalk\ folder and all of its contents, or will this invoke a major registry edit, which I'm prepared to do if that's what it'll take to get this working right. I also have several other VST plugins and VSTis that were bundled with older versions of Sonar PE that I wish to keep using; hence, I will have to install the core parts of Sonar 4 (maybe not), 7, 8, 8.5, X1, X2, X3 and Platinum in order to register those plugins. I also still use Project5 and have a lot of iK Multimedia, Native Instruments and other 3rd party plugins. I doubt that I have room enough on drive C to KISS and just put everything there; that's why I am planning to install all of the VST and VSTI stuff on another 1.92 TB SSD.
  6. I think I have the hang of it now. I didn't even have the comping tool selected. So with the tool selected, I now see how I can promote selected areas of each lane. Thanks David for pointing me in the right direction. I haven't tried this yet with midi lanes of a track. I'd still like to know how midi notes can be moved from one lane to another.
  7. Some lanes were grayed out but definitely not muted. I found that the same problem happens with audio take lanes that are recorded in Comping Mode. In Sound on Sound mode all lanes are still accessible whether soloed or not. I opened another project and the problem did not show up when recording new midi lanes to a single track in comping or sound on sound mode, but the problem still occurs when trying to record an audio track using comping mode. I was unable to highlight parts of clips in different lanes to select the best take. Take Lane 3 was the only one that stuck to the track, even though the other lanes could be heard when soloed. This appears to be a bug in Comping Mode.
  8. I have a drum track with the snare, bass drum, cymbals, etc. in different lanes of a midi track. It seems impossible to move data from one lane to another. Also some of the lanes are silent unless I solo the lane. If I un-solo the track, only the bass drum lane sounds, but the other lanes will sound if I solo their respective lane. Copying a "silent" lane to it's own track does not solve the problem; it is still silent unless soloed. If I try bouncing all lanes to a clip, then only the bass drum survives.
  9. Thank you so much scook. I finally found that setting in your link, and indeed the record bit depth was somehow set to 16. I changed it to 24 and now all is good. You da man!!!
  10. My audio interface does record at 24-bit depth in other DAWs, but my tracks in CBL are being recorded at 16-bit depth. This is my problem.
  11. The Audio Driver Bit Depth setting displays 24, but my recorded tracks are 16-bit resolution in CBL. I get 24-bit recordings in all other programs with the same audio interface. I've tried 3 different audio interfaces now with the same result. The problem seems to be in CBL.
  12. My audio interface does record at 24-bit depth in other DAWs, but my tracks in CBL are being recorded at 16-bit depth. This is my problem.
  13. I'm running Cakewalk Bandlab. My audio interface (NI Komplete Audio 2) is set at 24-bit 48KHz sample rate, but all audio records in CBL at 16-bit depth, yet when I record in Studio Lab or Project 5, the audio always records at 24-bit depth. The Audio Driver Bit Depth setting is grayed out in CBL Audio Driver Settings so I can't make any change there to the setting, but it displays as being 24. I'm using NI's ASIO drivers. Native Instrument's Komplete Audio Control Panel allows me to set the buffer size and sample rate, but there is nothing to set the bit depth. Windows 10 Sound Control panel has the interface set to play and record at 24-bit 48 KHz. I've tried deleting the aud.ini file and resetting to default values, but to no avail. This problem has only developed recently; when I open older projects, I see that all audio files are 24-bit. I'm stumped. Any ideas?
×
×
  • Create New...