msmcleod

@azslow3 - the saving logic has now changed. The logic is now as follows: On startup, all of the control surfaces are loaded and a backup of the control surface persistence saved. For each control surface, If any of the MIDI ports are unavailable, this control surface is marked as disabled. On close, all of the persistence is saved to ctrlsurface.dat... however: - If the control surface is disabled, the backup of the persistence is used - If the control surface hasn't been altered, the backup of the persistence is used Maybe the last step is the issue... perhaps it should always call the real code if its not disabled.

Yup, I can 100% relate to that!

The Gain knob on MIDI tracks acts as a velocity trim. This isn't a design bug, it was a design decision. Whilst I don't disagree with your suggestion (which is a pretty sensible one to be honest), given that there's no MIDI equivalent of gain, your suggestion is no more valid a solution than what is currently there. In fact you could argue that since gain is applied at the beginning of the chain and volume at the end, velocity actually makes more sense than essentially having two controls over volume. Personally, I would argue that having gain control CC11 (expression) would be more suitable than either velocity or volume, but even then its behaviour is different depending on the instrument being controlled.... just as depending on the patch, velocity doesn't always make a change in timbre - or even in volume as you've pointed out!

Sometimes I really need to get the idea down before I forget it... other times, it makes sense for me to practise it until I get it right, especially when "feel" is a big thing for the part. But either way, I've found actually being able to hear it afterwards makes it WAY easier to play. I'll come back to it a week later (after doing nothing but listening) and play the whole thing without a glitch... very strange how the brain works!

Try uninstalling / re-installing BandLab assistant - and make sure your firewall isn't blocking it else it won't be able to download.

The BT suite doesn't come with Cakewalk - it came with SONAR. Updating Cakewalk would have had no effect on these plugins - the installation process doesn't touch existing plugins. Try doing a plugin scan from within Preferences.

I had a similar issue with downloading BandLab stems - I contacted the team in Singapore and they sorted it out. @Marcelo Arte - you can import blx files using File->Import->BandLab Project... but you need to download the stems first using BandLab Assistant.

Can you post a video of what you're doing? ScreenToGif is good for this: https://www.screentogif.com/

I'll put it to the team tomorrow... I'm pretty sure we've got something similar in the backlog though. In the meantime, checkout the transform tool on the PRV controller. Whilst it isn't quite exactly what you're looking for, it does allow you to alter the angle / shape of the controller data in a much easier way:

Right click on the widget area (where the slider that shows 64 is on your image above), and select "Remote Control". You can either manually select the input on the dialog, or click "Learn" and touch the ribbon. When you write enable the automation lane and start playing, it'll record the automation.

I can't seem to reproduce this - it's working fine for me with instrument tracks. Can you post steps on how to reproduce this? The "(volume)" envelope indicates either a MIDI volume envelope has ended up on an audio track, or an Audio volume envelope has ended up on the MIDI track... I can't get it into this state tho.

At least for the moment, this isn't possible. What you can do is use the inline PRV on the track which would give you the same view except with automation lanes instead of controller lanes. You can also record your controller data directly to the automation track rather than a controller lane.

Instrument tracks are actually two tracks - an Audio track and a MIDI track. The "Volume" automation is the automation for the audio track, and the " Volume (ch 1)" is the volume for the MIDI track. Pan and "Pan (ch 1)" are a similar thing. The "(volume)" automation indicates that somehow these have been mixed up, and it doesn't know which one to choose. In the inspector, when the MIDI tab is selected: Volume controls MIDI volume Pan controls MIDI pan Gain controls velocity trim When the Audio tab is selected in the inspector Volume controls the volume of the Audio track Pan controls the audio track pan Gain controls the audio track gain I'll look into this further to see if this is an issue, or just confusion between the similarly named parameters... but can you try to see if it makes a difference whether the MIDI or Audio tab is selected when you're flipping?

You can do this using existing automation lanes - just add a new lane and assign the automation lane to the CC you want to control.

For those of you who aren't sure how to enable plugins, select "Cakewalk Plugin Manager" from the Utilities menu then: Note that 32 bit DXi plugins will NOT work in CbB... so be careful what you enable.

@jieva - Are you using a template that was created using an older version of SONAR?

Are these existing notes, or notes which you have placed with the snap on? The global snap setting affects the placing of new notes - not what is shown. For that, use the display resolution:

Is this behaviour new to the 2020.08 release, or was it doing this in 2020.05 too ?

Two things to check: 1. The Playback Timing master in Preferences->Audio->Driver Settings is correctly set to your playback device 2. Your ThreadSchedulingModel in Preferences->Audio->Configuration File ... if it's set to 3, set it to 2. ThreadSchedulingModel 3 doesn't work for all users.

BandLab Assistant and Cakewalk are two different apps. If you uninstall Cakewalk, BandLab assistant is still there. So: Uninstall Cakewalk Open up BandLab Assistant's download folder in Windows Explorer Download via BandLab Assistant Cakewalk.exe should appear in the folder - wait until it's fully downloaded (i.e. when the setup starts) Copy / Paste it to another folder

yamaha_syxg50_vsti.7z (3.0MB) — a version with the embedded 4MB wavetable, for general usage. yamaha_syxg50_vsti_ext.7z (4.0MB) — a version with external 2MB and 4MB wavetables, for experiments.

Uncheck "Fast Bounce" in the dialog - it's the same option whether you're doing a "Bounce to Track(s)" or a full Export.

The ext version on that site just provides the XG Lite (2MB) and the standard XG Level 1 (4MB) wavetables as external files. The standard yamaha_syxg50_vsti.7z download has the XG Level 1 (4MB) wavetable embedded - this is the one I use. This is different from the extended XG Level 2 / XG Level 3 sets offered by say, the MU80 / MU100R which is what the asterisk is referring to. I use this VSTi as a stand-in for my MU10 when I'm not in the studio, and it supports the full set of sounds that the MU10 does ( 676 tones compared to the 128 GM tones).

The VST2 API supports sysex, but not sure about VST3 tho - VST3 doesn't really do "MIDI" in the conventional sense. SysEx in VSTi's, until recently, have been extremely rare - it's really only the recent VSTi's that emulate real hardware that support it.

The active synth within the synth rack now uses the same highlight color as the active track in the track view.