scook

I believe the BandLab support person got this wrong. Cakewalk never had the source code for V-Vocal (and several other plug-ins that were made by Roland). They were completely dependent on the Roland software development for this product. This was one of the reasons for the push to develop VST3 and ARA support for X3. Cakewalk lost the ability to include V-Vocal starting with X3 the first Gibson release. Also the mention of DP in the email does not make any sense. DP was replaced in the Cakewalk product line by Rapture Pro. The last time DP was updated (not including the installer) was in 2010. The synth was bundled with SONAR but was a legacy product before the sale to BandLab. It is likely Rapture Pro will be ported to BandLab and maybe Z3ta+ 2.

V-Vocal was a product made in Japan by Roland. It was not part of Roland's sale of Cakewalk to Gibson or the IP purchased by BandLab. It would be up to Roload to release V-Vocal.

By default F11 is full screen mode, keyboard shortcut "M" brings up the marker dialog. The default shortcuts are documented here. The link is also available in the CbB Help menu.

I am sure there are a few permutations. It all seems to revolve around the edit filter being set to clip automation when bouncing the clip. For now, to avoid the bug, make sure the edit filter is set to clips, select the clip(s) then bounce.

Looks like a bug to me. The mono clip on bounce should not happen. This video shows the mono clip bounce bug using CbB 2019-03 build 20 (make to include which version of CbB is in use when experiencing a bug).

Maybe the plug-ins are installed in a folder not in the VST scan path. If the plug-ins are in the VST scan path there may be a problem scanning the plug-ins. The link above also shows the option to generate a scan log. There should be some information about the plug-in in the log. If plug-ins in the scan path failed to scan, they may get added to the exclude list. To see the excluded VST instruments, open the Plug-in Manager click on "VST Instruments" in Plug-in Categories click on the "Show Excluded" radio button If the synth is in the exclude list, using the preference screen in the link referenced above, temporarily set the scan drop down to Manual Scan enable "Rescan Failed Plugins" click the Scan button after the scan disable "Rescan Failed Plugins" and reset the scan drop down

Looks like a version of the VST Inventory I wrote

Toggling the FX button in the Mix module will set the state of all FX racks. However, It is possible to individually change the state of FX racks regardless of the state of the FX button. Also, the state of the FX button determines the state of the FX rack when adding a track. The "silent buses detected" warning advises the user that some send/output goes nowhere. This may be what the user wants. The warning may be suppressed by setting WarnSilentBuses to 0 in preferences.

In CbB, 32bit plug-ins are often in a different color and always have (32-bit) after their name in plug-in lists. Most installers provide an option to skip installing 32bit plug-ins. This is a good idea if they are not needed for another program. If there is a need to include certain 32bit plug-ins in CbB consider having more than one install location for 32bit plug-ins. This way one path may be used for CbB and another for other programs. This is a way to restrict the number of 32bit plug-ins visible to CbB while allowing other programs access to the full complement of 32bit plug-ins installed on the PC.

Often this is the result of too small a Prepare Using nnn Milliseconds Buffer value. The current default is 250 but many get better results when the value is set to 500 or 750. Some use values over 1000.

Not using the built-in metronome.

The metronome is turned off during export. In order to have the metronome exported, it will have to be recorded. Enable the metronome playback while recording and record the metronome audio track. Once recorded, it will export like any other audio track.

The plug-in reports I know of do not scan disks, they read the registry and report what has been scanned. Bitflipper's program should be available from the link provided in this thread. Unfortunately, he lost the source code when his studio was robbed so, it was not updated for CbB. I wrote a similar program that supports SONAR and CbB. Like the rest of my tools it is available on my google page.

Read up on the transfer function in the Melodyne help. When added to an FX rack, Melodyne has a transfer button on the plug-in UI. The transfer function reads the clip data and performs analysis needed for Melodyne.

I see a pitch, formant and volume automation when Melodyne Studio v4.2 is loaded in an FX rack. Have not played with it though.

AFAIK, nothing has changed on this subject since this thread

Can't see a reason in this case to suggest using a different value.

Usually record bit depth should be set to driver bit depth. The default settings for render bit depth (32) and import bit depth (Original) are fine. Projects can operate with clips at different bit depths. Imported clips follow the import bit depth setting. Import bit depth set to "Original" means the clip bit depth is unchanged on import. In short, use the ASIO driver set record bit depth to 24 leave render bit depth at 32 leave import bit depth at Original These setting will work fine for your existing projects recorded at 16bit and going forward. The only difference is new clips will be recorded at 24bit.

Often ASIO drivers operate at a single bit depth. This may be why driver bit depth is grayed out. The transport module shows record bit depth not driver bit depth. Record bit depth is set elsewhere in preferences. Follow the links for more information.

This was my solution when working

Could this be the Generic Low Latency Driver installed with Cubase? It is a problem. Try renaming the dll and use the ASIO driver for your interface.

maybe by running an advanced install of a pre-X series version of 64bit SONAR.

The package is for Rapture and Rapture Pro. Unlike Rapture Pro, Rapture does not support flac.

Thinking about Plasma FXPad being free for SONAR 2 and after a little more research I found a thread about SpectraFX and SONAR 3 from early 2004. Pretty sure that must have been the first release including SpectraFX. It would have been 32bit at the time. The plug-in was ported to 64bit at a later date (maybe SONAR 5). The version I have installed likely came from X2, the oldest full install on the machine.