scook

Ok, just a minute

Great Thanks again

Ok, Google finally refreshed. I believe v2.0.2 addresses the environment and upsampleeditor.ini errors. After recompile, I could not generate the two other iniWrite $tbl errors. They may be related to the environment failure. If they continue, please let me know which tools are throwing them I will take another look. Thanks for the feedback.

The iniWrite failure for the UpsampleEditor happens when no PluginUpsample entry is present in Aud.ini I'll need to add a check for that. That will take a minute. Can you tell me which programs are throwing the other iniWrite errors?

Hmm, that should be a Windows environment variable I will remove the code. It is not needed any more Give me a minute and I will post a new release.

No need to force the import to 24bit. Leave it at the original bit depth. The engine runs at 32 or 64bit based on the Double Precision Engine setting. The other setting to check is Render Bit Depth used for bounce, freeze and export. By default, it is 32bit. Any new recording uses the Record Bit Depth setting on the same page as Render Bit Depth.

Categories are stored in a SQLite database %appdata%\Cakewalk\Library\Library.db in the plugin_properties table There are three sources for tags: The VST3 plug-in manufacturers The user through the plug-in browser Cakewalk when they initially created library.db AFAIK, the only way to reducing the number of tags is directly manipulate Library.db. I like DB Browser for SQLite for SQLite db work. What I find annoying with the category drop down is it mixes FX and synth categories in one big list. User created layouts are not automatically maintained. This is one of the few reasons the plug-in manager still exists as part of CbB.

Try Open both projects "Select All" in project A "Copy Special" deselecting everything except tempo changes Paste into Project B

All new versions of Launchpad, Tools Editor, Upsample Editor and VST Inventory released as CbB Tools. A complete rewrite. All tools have font, style support and improved table displays Delivered as "CbB Tools.zip" containing a readme.pdf and "cbb tools.exe" As noted in the OP the zip is available from my Google page. Existing Launchpad users should copy "CbB Tools.exe" into their existing Launchpad folder. Other may copy "cbb tools.exe" into any folder such as "c:\program files\cbb tools". The readme has a little more info on install. Any questions? Please post them in this thread. thanks Some sample images follow

does for me

Or click-drag with the smart tool in the controller pane like this

Sounds like a question about the browser-based DAW called BandLab. This forum was created for the DAW called Cakewalk by BandLab, a Windows program. There may be a user here with some ideas but you might get faster answers from support@bandlab.com or the BandLab facebook group.

I don't own the hardware but if the DAW is receiving MIDI from it and it works with other plug-ins you are most of the way there. MIDI notes may be mapped manually or using MIDI learn in the plug-in. Sitala looks to be setup for GM by default. If you are not hearing anything after inserting the synth and the AKAI is GM mapped and set as the track input, make sure input echo is enabled on the instrument or MIDI track (of the MIDI+audio pair used by Sitala).

Here are a couple free choices

From the link provided

The good news is guitar is most often recorded in mono. There are a couple of ways to address the image above. My preferred method is select the track then bounce to track(s) (without the FX rack) set the Source Category to Tracks, Channel Format to Split Mono and Dithering to None. After bouncing, throw away the original and silent tracks The center pan the new track made from the right channel.

DP has a few programs that are known to crash. Without the program names, it is hard to say if they are involved here. WRT to CbB crashes in general see

Yes an extra discount applies when buying both SEM and 8 Voice Not when There is no bundle to complete

yeah, often best to consult the current doc regarding questions about the current implementation

When Post FX Rack is checked, the PC follows the FX Rack. When Post FX Rack is not checked, the PC precedes the FX Rack When in doubt, check the documentation

that's the one

The signal paths through the FX Rack and the PC are the same - in at the top, out at the bottom. IIRC, by default the PC is before FX Rack. There is an option in the PC context menu to place it after the FX Rack.

Instead of using the keyboard shortcut, try opening the controller from main menu View > View Controllers With the computer keyboard virtual controller active, keyboard shortcuts like "K" are pre-empted by the controller. The keystroke must go to either the controller or the DAW. It cannot go to both at the same time.

It is the same with all the other modular synth voices . Buy the standalones if preset convenience is important. Of course, the host module in VM (not part of the free version) can load the standalone VST although not as flexible as the SEM