scook

It could be updating the OS is the cause IDK. I stopped using Win7 in 2014.

I have no recent experience with 32bit DAWs either migrating to 64bit X1 in 2011.

I do not use V-Vocal but keep it installed for testing purposes. For this thread,

• I created a region FX clip using V-Vocal
• manipulated the clip in V-Vocal
• floated the V-Vocal window
• docked the V-Vocal window
• saved the project while shutting down CbB
• restarted CbB and loaded the project
• rendered the V-Vocal clip

There were some issues: 

• V-Vocal would not maximize in the mutlidock. It may be trapping the keystrokes. I could resize with the mouse though.
• once undocked, the only way to get the plug-in back into the multidock was using the menu

Granted the tests were not exhaustive and V-Vocal was never noted for being extremely stable in either 32 or 64bit hosts.

I was writing a reply to the OP while the second message was posting.

Plug-in layouts are different than plug-in categories.

• Plug-in layouts used to display plug-ins for use in a project.
• Category tags are a VST3 feature. CbB has the ability to associate category tags with any plug-in DX, VST2 and VST3. These tags are used to create the "Sort by Category" layout.

It is hard to imagine an update resulting in lost plug-in layouts. AFAIK no update has ever messed with the plug-in layout folder or its content. That said backing up user data is a good idea.

The path to the plug-ins layouts folder is maintained in preferences.

I have never read of plug-in categories being lost either. IIRC, there have been a couple of threads on the old forum regarding errors trying to load the database. The fix usually involved initializing the database which loses any user mods to the database.

The category database Library.db is stored in %appdata%\Cakewalk\Library

Bus automation works the same as track automation

That said, one must have a master bus setup.

All the templates provided with CbB have a master bus defined.

Did you use a template provided with CbB or did you start with your own template or blank project?

A couple of things this support person got right are V-Vocal is a DX plug-in and 32bit VST plug-ins while supported with BitBridge may have reliability problems. Given that the support person should know that

• 32bit DX plug-ins cannot load into a 64bit host
• Bitdrige does not work with DX plug-ins

I can assure you the V-Vocal running in your 64bit DAWs is 64bit.

Cronus is excluded by design in the plug-in manager because V-Vocal is not intended to show up as a regular plug-in. Changing the excluded flag for this plug-in is not the right thing to do.

Pretty sure someone with more experience may have handled this differently. Maybe @Mike B can review this.

FYI

13 hours ago, sdwest said:

If I am working on a 32 bit file, with SPLAT X1 or X2, V-Vocal seems to work fine for me.

The data files are the same whether working in 32bit SONAR or 64bit SONAR/CbB. The difference is the software. V-Vocal is a DX plug-in. The 32bit X1 and X2 are loading a different plug-in from the 64bit DAWs. X1, X2 and V-Vocal were all developed and tested on Win 7. CbB is developed and tested on Win10 along with the later versions of Platinum.

I cannot say if any of this matters but these are some of the differences between the software mention in this thread.

6 hours ago, wunderbier said:

Is there a technical reason why those plugins should go in different places? I typically only install one version (starting with VST3 and working backwards if there are problems), but I put everything into the same C:\Program Files\VstPlugIns folder. I haven't encountered a problem so far (I think) regardless of plugin type.

The VST3 spec calls for

• 64bit VST3 plug-ins to go in  C:\Program Files\Common Files\VST3 and
• 32bit VST3 plug-ins to  go in C:\Program Files (x86)\Common Files\VST3

While CbB will use VST3 plug-ins installed elsewhere some DAWs do not. Most manufacturers follow the VST3 and do not give the user an option for an alternate install path. It is a bad idea to install VST3 plug-ins outside of the specified path.

The VST2 spec is silent about where plug-ins should be installed. This lead to manufacturers using a variety of "default" locations. In general, VST2 plug-ins may be installed anywhere EXCEPT in the VST3 folders mentioned above.

Dimension Pro LE, the synth included in the package to play the Garritan Pocket Orchestra

I am guessing this is SONAR Home Studio 7 XL the last version of this product.

It is a 32bit DAW so any plug-ins bundled with the product are 32bit too.

64bit versions of Boost11 and Studio Instruments are bundled with CbB.

CbB also has an integrated step sequencer.

It includes a 64bit version of TH3 Cakewalk amp sim.

The only unique bits of the XL pack are the 32bit DP LE and the bundled content. While the content may be useful, you may be better off using a 64bit sfz player like sforzando instead of 32bit DP LE.

14 minutes ago, sdwest said:

I was not aware that V Vocal was also a 64 bit plug-in as well as 32 bit, I'll look into that further.

DX plug-ins are host bitness specific. 32bit DX plug-ins are not visible in 64bit DX hosts and 64bit DX plug-ins are not visible in 32bit DX hosts. IOW, when running a 64bit DAW only 64bit DX plug-ins are available.

6 minutes ago, Sunset Recording said:

Am I just asking to much of my wimpy laptop? My latest project is larger then my average. 57 tracks, no virtual instruments and plenty of automation. Dell lap, i5 7200 U, 16 GB ram. Trust me, I'm saving my $$ for more PC.

Could be. If the laptop does not have an SSD, the drive may be a limiting factor.

Adjusting the ASIO and playback buffers may help

The software is mentioned on page 9 of the users manual

http://download.steinberg.net/downloads_hardware/UR-RT2/Manuals/UR-RT2_UR-RT4_Operation_Manual_en.pdf

The ability to use the buffer slider depends on the driver mode and the driver in use.

Some ASIO drivers do not respond to the slider. In those cases, the slider is disabled and manufacturer supplied software must be used to adjust the buffer.

WASAPI Shared buffer size is fixed and cannot be adjust so the slider is disabled for this driver mode.

AFAIK the rest of the driver modes can use the slider.

16 minutes ago, Sunset Recording said:

Steinberg Ur-RT2 and  Focusrite Scarlett interfaces

I assume you are not trying to use both interfaces at the same time.

Look in the FX browser in the MIDI tab, the plug-in list for FX Racks on MIDI tracks or the MIDI tab in the Inspector for instrument tracks.

Make sure to run the scanner from preferences with "Scan in Sandbox" enabled. Avoid running the scanner from the Plug-in Manager.

might be a question for support@cakewalk.com

Include OS info in the report

I believe the SD80 is in the Roland.ins

By default this file is in "C:\Cakewalk Content\Cakewalk Core\Instruments"

Working in CAL I have Emacs in Lisp mode so formatting happens automatically.

V-Vocal shipped as a 32 and 64bit DX plug-in. It was developed by Roland and not part of the sale to Gibson so, starting with X3, the plug-in could no longer be bundled with SONAR. Since Gibson did not own the product, it was not part of the IP purchased by BandLab.

The plug-in was last updated in 2011. Software does not age well. Regardless of its utility, relying on old, unmaintained, unsupported software is unwise.

That said, I just loaded up the plug-in into a new project in CbB and messed around with a clip without crashing the DAW. I am running Win10 though.

Providing the crash information to BandLab as suggested in the thread below may help the developers address the problem

It is not clear what you moved.

It is unlikely anything in appdata is part of the plug-in unless you inadvertently forced the plug-in to be installed under appdata.

The installer available at https://www.orchestraltools.com/store/get-sine provides an option to install the plug-in. I believe this tries to install in a VST plug-ins folder somewhere in "Program Data" by default. This should be installed in the existing VST scan path.

Rather than try to sling files around by hand, it may be more productive to uninstall and re-run the SINE_Player_1.0.2.436.exe and install the plug-in correctly.

If a plug-in has "Enable MIDI Output" disabled it means the VST scanner determined the plug-in does not support the feature. Not all plug-ins echo or generate MIDI data.

It sound like you are pointing the scanner to where the sample library is stored.

This library uses the Orchestral Tools Sines player. This player should be installed in the VST scan path not the sample library.

This thread may be useful

Of course any plug-in with a side chain input may be used. The routing for regular plug-ins is the same as the PC modules in CbB.

Open the Melodyne plug-in or a clip as a Region FX and check the algorithm default.

Can't help you with this plug-in other than to mention, from the description on their website, it appears the plug-in should show up as an FX plug-in. After adding the plug-in to an audio FX rack "Enable MIDI Input" should be set in the VST2/3 drop down in the standard header above the plug-in. This procedure was added starting with SONAR X3 eliminating the need to configure FX plug-ins as synths.

all three lines should be in the do block like this

(do
    (dword takt)
    (= takt Now)
    (insert takt 1 NOTE 60 100 240)
)

or use a one liner

(insert Now 1 NOTE 60 100 240)

BTW

39 minutes ago, Heinz Hupfer said:

 (== takt Now)

Is not an assignment statement. This is

(= takt Now)

Here are a few randomizers

A CAL script called HUMANIZE.CAL

The Velocity MFX has a Randomize section. Press F1 over the plug-in UI for its help.

An MFX created by @Variorum called CSHumanize