Malfunction of track Solo when using MIDI remote control

[GraemeSPa]

Hi All , I can't find anything similar to my problem, so I am starting anew.   I have been using Cakewalk since it was a DOS program and Greg Hendershot answered emails.  I lost my Sonar Platinum after Gibson had a brainstorm,  but I have been a CW Bandlab user and a Gibson ex-customer ever since. 

I use templates for my project files and use an external MIDI controller to send control messages to channel faders and buttons to set/reset  ARM Record,  Mute and Solo for up to ten channels.    Everything worked fine until I installed 2024 12  build 125.   Now my external controller buttons will toggle the track Solo button ON and OFF   (i.e.  it  turns green or not green)  but the actual Solo function on the track doesn't work - the track will not go Solo.    The track  WILL go Solo with a mouse click. 

This error occurs with the track Solo Remote control assigned to any MIDI cc .  The remote control of ARM and MUTE buttons still function normally.   

Any remote MIDI code assigned to a track Solo button has the same effect - the remote control of the Track Solo button for this build does not work.    Any help will be appreciated, 

 

[David Baay]

I recalled this issue having come up in the past and found mentions on the old forum going back to at least 2012. Here's one from 2017 before the Gibson shutdown:

http://forum.cakewalk.com/SONAR-Track-Soloing-Remote-Control-not-working-m3561832.aspx

If it was working more recently, it may have regressed, but possibly there's some other contributing factor that can make it fail. The first thread I saw suggested that it could be intermittent and work for a time after re-learning.

[User 905133]

FWIW, I don't generally use controllers (e.g. CCs) as control surfaces for the DAW's functions. For the most part I use buttons, knobs, sliders, etc. to control synths (including soft synths w/in my DAW. However, earlier today I confirmed this [remote control CCs change the Solo on/off display but not the function itself] with my keyboard using CbB build 125. I just did another test (and confirmation) with a nanokontrol. 

I am reminded of a similar issue I had a few years ago with the inspector-based arpeggiator's Latch display v. the Latch function. IIRC there were other anomalies like that--CCs made the button's display toggle on and off, but not the button's function. 

[msmcleod]

Is this on a pure MIDI track, or on an instrument track?

Generally the MIDI part of instrument tracks ignore solo/mute,  with it only applying to the audio part of an instrument track. 

The reason for this is that MIDI data needs to be cooked in advance,  so un-muting a MIDI track will result in a delay before you start hearing the notes again. The audio track however is almost instant (depending on your ASIO buffer size).

Solo works in a similar way, as it's basically muting other tracks behind the scenes.

Pure MIDI tracks should be respond as you'd expect - i.e. Solo / Mute apply directly to the track.

AFAIK this behaviour is not new.