scook

Given the PRV operates at the track level, one way to "hide" data from the PRV and still have it play is move the clip to edit to a new track and edit it from there. This may be done by: Create a new MIDI track with its output set to the master track's synth SHIFT-drag the clip from the master track to the new MIDI track, Edit the clip in the PRV SHIFT-drag the clip back to the master track Holding down SHIFT while dragging the clip insures it does not move to the left or right on the timeline.

The PRV works at the track level. The control what is visible in a track, mute the clips to hide and enable Hide Muted Clips in the PRV View menu

For products that appear in Cakewalk Command Center, install them using Cakewalk Command Center and they will be activated automatically. For the rest, run the installer. Use the serial number and registration code provided when the product was originally registered. If you created an accounted between 2014 and 2017, the installers, serial numbers and registration codes are in your old Cakewalk account. If you do not recall your account password contact support@cakewalk.com for password reset.

Cakewalk must be activated at least every 6 months. Activation is automatic as long as the PC has an internet connection and an active login to a BandLab account.

That is why it does not appear in the edit filter. It was associated to a parameter no longer in the track probably from a plug-in that was removed. Orphaned envelopes used to be more common. CbB does a pretty good job of removing automation when plug-ins are deleted.

This is almost always the result of unexpected data shutting down the sfz engine in the synth.

SHIFT-click on the envelope to bring it into focus Right-click on the envelope for the context menu Select Delete Envelope from the context menu

A better discussion for but double-click in instrument/MIDI whitespace follows the click behavior setting as long as snap is off or when clicking in an area outside of the snap setting as noted in It appears Now messes with double-click.

Given the plug-in cannot handle fast bounce, there may be other buffer issues. Try increasing the Prepare Using nnn Millisecond Buffers setting in preferences.

Fails when snap is off or when clicking at a location where Now will snap with snap enabled.

Starting with 2020.09 CbB has in-app updating. No need to run BA.

It looks like all the Valhalla plug-ins were updated in Oct 2020. Did not get the memo. Downloading now.

The reverbs are nice but the Valhalla plug-in I have used most is UberMod.

To my knowledge Valhalla does not discount there products...ever. Their prices are set upon release and that is it.

Not as of Nov 2. It appears to be up to Steinberg.

When exporting multiple audio clips with the intent of loading them into another piece of software it is best to export as broadcast waves. Broadcast wave files have their position on the timeline written into the files. By default, CbB imports broadcast waves using their timestamp. If the source cannot export broadcast waves, the next best option is export all the tracks starting at 0 on the timeline. If neither of these are possible consider saving as a MIDI file and use File > Open to bring the file into CbB. With no MIDI output device specified in preferences, CbB opens MIDI files ready to play with TTS-1. Then add additional synths to replace TTS-1 if desired.

From http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x20091 Keep in mind, when set to DirectShow, if a video fails to load, the DAW will try the MF engine. This may result in the Render Quality tab going missing even though the default is set to DirectShow.

Good news. It is a good idea to stay current. Starting several released back, when a new version is released a rollback installer is also released to revert back to the previous version if necessary.

The last image indicates BandLab Assistant does not recognize Cakewalk is installed. The fact BA does not have a record of the install leads me to believe more than a simple uninstall and reinstall of BA occurred. When BA and CbB are installed properly the Install button shows either Open or Update if an update is available. You can try running just running Refresh Activation from the menu next to the Install button but since BA does not see the installation, it may try to download and install Cakewalk by BandLab 2020.09. This should take care of activation too. If this does not work consider sending email to support@cakewalk.com Reactivation happens automatically every update. If you prefer not to update the software, you will have to manually re-activate every 6 months.

Everything except the CbB documentation on the old site is the old Cakewalk company. The old site is useful to gain access to your old purchases, documentation, knowledge base and forum history. The support page is old, do not use it. The email above is the new support link The new support web page is https://help.cakewalk.com/hc/en-us The forum you figured out.

Great, CbB was activated by BA. If you blew up access to your old Cakewalk account send email to support at the link above. They will reset the password.

The url is the old Cakewalk site. You will need access to your old account for old products but not for anything to do with Cakewalk by BandLab. Email service for the old Cakewalk site was turned off when Gibson shut down the company. Fortunately support@cakewalk.com the new BandLab support email site for Cakewalk by BandLab can restore access to your old Cakewalk account. Initial activation for Cakewalk by BandLab should happen through BandLab Assistant. It uses the same password as your BandLab account and this forum.

As far as disk usage, the audio driver and engine settings do not matter. Record, render and import bit depths along with project sample rate affect file size. It is pretty easy to get a lot of extra files in the audio folder. Bounced and frozen tracks create copies of clips at the render bit depth. Deleted audio clips may no longer be referenced in the project but still exist on disk. The extra audio files should not affect wave drawing though.

VCV Bridge was part of VCV Rack 0.6. Pretty sure it was installed along with the synth so that it could be used in DAWs. AFAIK, it is not included with VCV 1 and is not being developed as VCV 2 will have a paid VST plug-in version. If you are not using VCV modular inside a DAW (the bridge does work with VCV 0.6 and 1) consider removing the the VCV bridge dlls from the scan path. May also want to rebuild the Cakewalk plug-in inventory registry. To do this run a VST reset from preferences. This clears and rebuilds the Cakewalk VST Inventory in the registry. No need to directly edit the registry.

Sorry, I was going by the documentation I should have looked data in detail. I scanned the cache for the clip names but forgot there were two attempts at creating the project and two clip in each project (original and processed). This resulted in 4 cache entries totaling 115 MB. The 2 audio clips in the final project were actually 48 kHz @ 16 bit or ~1.85 GB each. The individual wov files for the final project were 29.6 MB each. So the expected cache size corresponds to ~1.57% of the original clip size. A value I just learned about, thanks.