scook

No need to export; copy and paste tracks. Open the bun and the target project. Select and copy the tracks from the bun project to the target project, Make sure to have a good backup of the target project, just in case.

No need to convert the files before importing into CbB. During import, CbB converts the files as needed for the project. All the clips in a project must be the same sample rate but bit depth may vary. Sample rate conversion in CbB is pretty good. The actual bit depth used for import is controlled by the Import Bit Depth setting in Preferences > File > Audio Data The default Import Bit Depth is Original meaning the bit depth will not change during import.

Did you try the safe mode suggested by the message?

Or get the lot for $49 https://www.pluginboutique.com/product/2-Effects/39-FX-Bundle/8656-Plugin-Boutique-s-10th-Anniversary-iZotope-Bundle-Exclusive-?nosto=frontpage-nosto-cherrypicked

Master.ins is a text file in "%appdata%\Cakewalk\Cakewalk Core" for bulk changes, I use a text editor

Before that was and after

keep it simple If "C:\Cakewalk Content" is a directory junction, remove it. if "C:\Cakewalk Content" is a directory leave it If the rollback instructions do not work in this link chances are the installation is too damaged. If this is the case, perform step 5 of the clean install instructions Download and the Cakewalk Installer from this page and reinstall everything you installed previously.

no

Cakewalk by BandLab is a Windows only program. BandLab, a web browser-based DAW, not sure which browsers work on a Mac, originally BandLab required Chrome. Questions about BandLab, the DAW, are best posed to support@BandLab.com , the support page or Facebook group.

"Enable MIDI Output" is in the Insert Soft Synth Options dialog too. FYI, by default "Enable MIDI Output" is automatically turned on for synths but not for effects and not all plug-ins can send MIDI data. "Enable MIDI Output" is considered a per-instance setting so is not located in plug-in properties. Plug-ins incapable of sending MIDI data will have "Enable MIDI Output" disabled. You are welcome. Please edit the OP and add [Solved] to the subject. thanks

Which reply?

It is possible if the plug-in is capable of sending MIDI data and "Enable MIDI Output" is checked in the VST drop down in the standard header of the plug-in and the plug-in has the option enabled, if necessary. Some plug-ins have a separate MIDI send setting. Here is an image showing Track 1, a MIDI track with its output routed to VCV Rack 2 Pro (in this case I specifically used the synth plug-in but the FX version works just as well) in Track 2's audio FX rack configured to receive and send the MIDI data and Track 3, an instrument track setup to use TTS-1, with its input set to VCV Rack and echo input enabled. and an animated gif showing the MIDI track playing and TTS-1 playing the data received from VCV Rack Plug-ins in FX racks only send audio data down through the FX rack. There are other ways to route audio and MIDI using 3rd party plug-ins but will leave that for another time. While setting up this example, I noticed plug-ins in bus FX racks do not send MIDI data so for this case use aux tracks or audio tracks with patch points instead of buses. FWIW, I agree data routing in CbB could be improved but want to make clear what is possible today.

Please return when possible and post your findings thanks

Instrument tracks are a special presentation of autio+MIDI track pairs. If a plug-in has multiple outputs, it is possible to add addition instrument tracks to the plug-in, one for each plug-in stereo output. It is also possible to add as many MIDI and audio tracks to a plug-in as desired. MIDI data cannot be routed track-to-track regardless of the track type. MIDI data is routed to and from plug-ins. Any plug-in capable of sending MIDI data may send the data to any number of instrument and MIDI tracks. An instrument track has a MIDI input and an audio output so there is no way to route audio to an instrument track. To route audio to a synth. the synth must be placed in an audio track FX rack. The audio in that track will be processed by the synth. MIDI data may be routed to the plug-in using any number of MIDI tracks.

It was early access only until a few days ago. Noel posted when it went official The documentation still needs updating. When it comes to activation Noel's FAQ might be a useful link

There can only be one entry on the disk for "C:\Cakewalk Content" if it is a regular directory or a directory junction and it can be written to, the installer will write to it. If "C:\Cakewalk Content" currently is a directory junction, you should be able to enter the folder and end up wherever the junction points copy files into "C:\Cakewalk Content" and the files should be wherever the junction points add files to the physical location where the junction points and see those files in "C:\Cakewalk Content" IOW, a directory junction works just like a regular directory except the data is physically located somewhere else and data may be added to the physical location and that data will appear where the directory junction was defined. If all of that works, the install should be able to work with the directory junction. If any of that does not work, delete the directory junction and either try to create a working directory junction or forget about it for now, delete the directory junction and create a regular "C:\Cakewalk Content" directory

I have no idea what your backups look like. That said, it is pretty easy to get the factory "Cakewalk Content" using a full Cakewalk installer. Here is a post I made to a user that inadvertently deleting part of the Cakewalk core installer (Cakewalk Content is part of this too). It explains how to use rollback and update to get everything back Should you choose to attempt directory junctions again (this is the first time in my memory someone has actually lost data) instead of moving "C:\Cakewalk Content" to another drive, copy it to the other drive then rename "C:\Cakewalk Content" something else then create the directory junction. This way if you mess up, the original Cakewalk Content folder is still there albeit under a different name. Once the directory junction is verified as working (IOW, the DAW loads and can access Cakewalk Content), the renamed Cakewalk Content on the system driver may be deleted, backed up off the drive or whatever.

Depends on what is meant by "system restore." If "Cakewalk Content" is now empty and there is no backup of the directory somewhere, it will need to be reinstalled. Is this just a CbB install or are legacy Cakewalk DAWs involved?

This is great. Maybe this http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Introduction.30.html could use a little rewrite.

Looks good BTW, there are two different installers on the official Cakewalk website

Here is a similar thread

I believe what you are asking about is the GeneralMidiSMFs setting in TTSSEQ.ini. It defaults to 0 but in this case, it should be 1 so the setup events are visible in the Event List view. Edit "%appdata%/Cakewalk/Cakewalk Core/TTSSEQ.ini" to make the change.

Maybe but you can skip the bundling step and use "Save As" or "Save Copy As" to rewrite a project to a new location if this is an issue. Just make sure to enable "Copy all audio with project" so all the audio referenced in the original project is placed in the new project folder. IIRC, the one thing bundling does that the save functions do not is re-write the project file. Of course, whether bounced or copied there is no guarantee that the new files will not be fragmented. That mostly depends on how much space is available and how continuous space is on the hard drive. Disk fragmentation is not much of a problem with SSDs. Dropouts generate a message with a code and a link to the help with information about the dropout code.

Sounds like

The Realtek ASIO driver is broken. Use the WASAPI modes in Cakewalk when using the Realtek chip. ASIO4All is not a good choice, uninstall it. For the mixer, did you try the latest driver from Soundcraft https://www.soundcraft.com/en/products/signature-12#downloads_and_docs?