scook

If the V-Vocal clip was not rendered both the pitch corrected and original clips are available to the project. You may be able to simply roll back to the original by using the Remove Region FX option in the V-Vocal Region FX menu. If not, you can use the method I described above to force CbB to load the original clip.

Until V-Vocal is rendered, it uses a copy of the clip. Should be able to remove the region FX and the original clip should be restored. If that does not happen both should be in the project audio folder (you are using per-project audio folders, right). If the project cannot find the V-Vocal clip it will give you an opportunity to load it. Instead use the original clip and remove the V-Vocal Region. This should restore the original clip. Try it on a copy of the project.

If there are dmp files associated with the crashes, they should be in %appdata%\Cakewalk\Cakewalk Core\MiniDumps Zip up one or two and send to support with a description of the problem, include CbB version, OS and PC hardware details. Crashes are a support issue. They are a "technical problem." Examples of things that are not technical issues and not support issues are "how do I record audio" and "what is MIDI." The problem may be related to the offline render algorithm selected in preferences.

V-Vocal is a special DX format plug-in. It is special because it does not work in the FX Rack like regular plug-ins. Instead, it is a Region FX. The Cronus.dll is V-Vocal and is excluded by design in the plug-in manager. Since V-Vocal is DX format, only the 64bit version is seen and loaded by 64bit DAWs. As far as 64bit hosts are concerned, it does not matter if the 32bit version is installed. Does V-Vocal work in a new project? If so, the old projects which were opened in safe mode and saved without V-Vocal may need to have the V-Vocal clips deleted, the original clips unmuted and V-Vocal reapplied. Don't suppose there are copies of the project prior to opening in safe mode.

Groove clips will play to tempo but you may need to do is check the time base in Clip Properties for the clips.

MIDI follow tempo but regular audio clips do not. Groove clips will follow tempo.

References to controls by color is useless unless they have a theme to put them in context. Even then, it is more helpful to refer to controls by name. Don't know the name and don't want to look it up....post an image.

Try toggling the 64bit Double Precision Engine in preferences If that does not make a difference, bypass all plug-ins either with the FX button in the mix module or the shortcut "E" If the problem goes away, it is related to one or more plug-ins. To narrow it down, enable all plug-ins using the FX button or "E" and bypass individual FX Racks.

Two possible causes - waiting for the audio interface or waiting for a plug-in to shutdown, often a 32bit plug-in running in Bitbridge.

By default, Cakewalk installs audio loops in folders under C:\Cakewalk Content\Audio Library but third party loops may not follow the Cakewalk default. It really does not matter where they are installed.

Could use the Matrix View to loop the original 8 bar clip then while the Matrix View is playing the original clip record on another track. Here is one way to do it... Assume the original 8 bar clip is on track one. Make sure CbB will loop the clip as expected. To do this, turn the clip into a groove clip by selecting it and typing CTRL+L. The clip should completely fill all 8 bars. If it does not, open the clip into the Loop Construction View and adjust the beat count until the clip fills all 8 bars. May want to rename the clip in clip properties and drag it to the browser saving it for future use. Create a new audio track (track two) Open the Matrix View Drag the clip from track one into cell(1,1) in the Matrix View, set the row to play on track two and set Follow Transport on. Click on the clip in the cell. The clip should be flashing. Archive track one Create a new audio track for the new solo and set the track up for recording Start recording The 8 bar clip in the Matrix View should play as long as the transport is running.

Have to go back to the last SONAR documentation for this info

This message is displayed when opening a project created with a version of SONAR prior to X1 that offered per track EQ. The EQ used to implement per track EQ prior to X1 was the Sonitus EQ. The message is displayed in order to provide an opportunity to replace the per track EQ in the project with the ProChannel Quad Curve EQ.

R-Mix is not a Region FX, it is a regular VST2 plug-ins. Maybe you are confusing it with V-Vocal which does appear in Region FX. If R-Mix installed in the 32bit plug-in path, you may have installed the 32bit version. Feel free to uninstall X2 and re-install the 64bit version. By default, 64bit R-Mix installs in C:\Program Files\Cakewalk\Vstplugins\R-Mix SONAR Edition

When making an announcement like this please include the name of the software and the release. AFAIK, the current version are: BA - 5.0.4 from Jan 25 CbB - 2019.01 (25.01.0.27) from Jan 23

no Use "Replace Synth" after the MIDI file is loaded. The Replace Synth function is on the track header context menu and the synth rack synth settings menu.

This depends on the Stop At Project End setting. Because I often need to run the transport without any clips in a project, I leave this option unchecked.

According to the details for C:\Program Files\Cakewalk\Shared DXi\Pentagon I\Pentagon I.dll, version 1.5.0.0 was bundled with X3. Not sure what was bundled with SONAR 8. Version 1.5.0.0 loads OK in CbB 2019.01 on my Win10 PC.

If installed following the instructions above, V-Vocal should appear as a Region FX in CbB. Pentagon I is the only plug-in bundled with SONAR X series requiring administrator access to the registry. This may be done by either running the DAW as administrator or modifying the registry as shown in this post. Allowing for the permissions issue should Pentagon fail to load the problem is system specific.

https://www.cakewalk.com/Support/Knowledge-Base/2007013086/Using-Pentagon-I-as-a-Vocoder Usually Pentagon I requires the DAW to be run as administrator unless the registry has been modified. See this post for details. Pentagon I is a 64bit DXi plug-in (of course, there is a 32bit version too). Pentagon I was bundled with SONAR Producer 5 through X3.

Set this drop down to All Keyboard shortcuts are SHIFT+left and right arrow keys

Note the dates on the assets files. These files are part of Gobbler integration in X3. There is a preference setting to suppress creating them in X3. The feature was only in X3. Since Gobbler changed it service years ago, the assets files serve no purpose and may be deleted.

The two programs look similar. That familiarity is a good thing when trying to learn a new version. That said, there have been quite a few bug fixes, enhancements and new features in the years since X3. Whether they are meaningful to you depends on your workflow and if you choose to take advantage of the changes since X3. Here are the SONAR and CbB update notifications. For the most part, it is possible to ignore all the changes since X3 and use CbB just like the 6 year old SONAR X3.

Which version of CbB are you using? Do you use lenses?