scook

The reset could have been performed after the re-install. A reset is a scan except it clears the VST Inventory and scans all plug-ins as if they were just installed. So, what is the status now? Is the plug-in available?

The Cakewalk documentation includes a section from the old SONAR documentation for an alternate method, however; the only method currently available for CbB is BandLab Assistant.

Try the Split At Selection option in the Split Clips dialog.

The log indicates a regular scan not a reset. No plug-ins were actually scanned according to the log. From the bottom of the log Instead of clicking the Scan button, click Reset

The scan log indicates the plug-in was skipped because it was previously scanned. Try running a VST reset with "Generate Scan Log" enabled. This will force a scan of all plug-ins including SSD5.

Might help to explain what the difficulty is. Here are the instructions. Use the "If you are installing from BandLab Assistant" method.

By default duplicate step sequencer clips are link, there is an option to unlink a step sequencer clip on the tack view clips menu http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x1875B To create a new step sequencer clip either close the existing step sequencer view, move the cursor to an empty spot on the MIDI track and open a new step sequencer view or right-click the step sequencer tab and lock its contents then open another step sequencer view.

my mistake

Right-click the body of the PC module for the about screen option or open C:\Program Files\Cakewalk\Shared Utilities\Internal\ProChannelConcreteLimiter and right-click on ProChannelConcreteLimiter_64.dll to open the context menu, select Properties and check out the details tab for file/product version info and modified date.

AFAIK, there was only one CCC compatible installer made for the Concrete Limiter - ProChannelConcreteLimiterSetup_1.0.2.18.exe It is the most recent version of the plug-in.

Noel's reply

Does this mean 64bit X2 is installed on the same PC now and the limiter is available in X2 but unavailable in CbB?

Yes, the plug-in predates CCC but it is one that was one of the few plug-ins that was updated to use the tool. Loaded up CCC to verify the installer is there. Usually when an installer is CCC complaint, best results are had using the tool.

The Concrete Limiter installer was updated for the Cakewalk Command Center. May want to use the CCC to install the limiter.

Would still need additional action to update CbB. In Preferences, where the current ASIO button is located, the Close and Apply buttons perform this task. I think the best one could hope for is a function to open the Preferences > Driver Settings screen which could be mapped to a shortcut. In the interim, autohotkey may be a viable solution. In fact, the entire round trip from CbB to ASIO client and back begs for a scripted solution.

Chances are the files are imported but are far to the right on the timeline. If this is the case, uncheck Always Import Broadcast Waves at Their Timestamp

Not sure I follow the request Here is an example of moving the audio from a frozen instrument track and frozen audio+MIDI tracks that point to a synth, thawing the frozen tracks then starting the transport. Notice all tracks play OK.

This would be nice but it is not possible. Their is no provision in the ASIO spec for a DAW to send buffer size change request to the interface or its software.

There are few plug-in specifically written for the ProChannel and there has not been a new PC module created in some time. Just like the FX Rack and any plug-in may be added to the ProChannel. When added to the ProChannel regular plug-ins are automatically hosted in FX chains. It is possible to create a custom UI with up to 6 buttons and 6 knobs to control plug-in parameters in an FX chain, plug-in UIs may be opened from the FX chain and all plug-in parameters are available for automation.

If the layouts predate SONAR Platinum, it may be better/faster to build fresh files. A combination of the plug-in browser and plug-in manager works pretty well. Start by using the default "Sort by Category" layout then modify the layout to suit keep in mind these folders and their content represent the lowest folders in the final layout tree. Once all named properly and places in the correct folders, organize the folders using the plug-in manager. The plug-in manager is needed only to nest folders otherwise everything is possible with the plug-in browser and the "Sort by Category" layout. The help for the plug-in browser layout edits starts around here. Once this is done, maintenance depends on whether folders are nested or not. Nested folders used the plug-in manager otherwise use the plug-in browser set to "Sort by Category." This does not address the FXs plug-in in the synth list. The only time I have seen this was when the plug-ins were manually changed from effects to synths in their plug-in properties. Starting with X3, this is not necessary the MIDI I/O properties for plug-ins is now on the plug-in standard header. For any FX plug-in currently residing in the synth Sort by Category layout, double check the plug-in properties and make sure the plug-in is not configured as a synth. Probably want to do this before building the custom effects and synth layouts.

And all this time CbB has been running as administrator? If not, the run the VST reset again with CbB running as administrator and continue running CbB as administrator. If CbB has been explicitly running as administrator, I am out of ideas.

By default CbB writes audio into per-project audio folders. Usually the per-project audio folder is created in the folder where the project is saved. If a project is created and not named, CbB uses the global audio folder in preferences.

If a Log is created, the path is in the toast when the scan completes. Like this That said, since this is a platform change, the log is a secondary issue. There is no reason to remove the old 32bit X3. In fact, it is a good idea to leave it as moving the CbB is likely the first 64bit transition. Along with anything from X3 that may be needed, all of need their 64bit versions installed. It is not a good idea to use 32bit plug-ins when a 64bit version is available.

32bit makes a big difference. Some 32bit DX plug-ins bundled with X3 were never ported to 64bit, Make sure 64bit plug-ins are installed when possible. This means it is necessary to run the 64bit X3 installer to get all the 64bit version of plug-ins bundled with X3 installed. It is not necessary to install X3 though. Choose the advanced install option and install the plug-ins only. Avoid using 32bit plug-ins when a manufacturer also supplies a 64bit version. If X3 was running as administrator, chances are CbB will need to run as administrator.