• SONAR
  • ACT question re: bus output settings (p.2)
2013/11/24 18:12:42
Blades
This is an OLD post - but I resurrecting it because this is STILL a problem.  I would have thought that somewhere in the last 6 years this would have been addressed, but it still has the exact issue as before.
 
So here's a summary:  I have a midi remote control on the enable of a bus send.  I press the button on my keyboard and the send turns on as expected (visually), but nothing happens to the audio.  If I click the same button, it does just what I'd expect it to.
 
Bummed that this bug has existed for this long and in as many updates as there have been to the audio engine and so many other things, this has gotten bypassed.
 
It would be really handy to be able to have a one button press to switch from monitors to headphones rather than having to expose the master bus and switch which soundcard output it uses every time.  Certainly not a show-stopper, but annoying nonetheless.
 
Thoughts from anyone on this?
2013/11/28 18:00:41
Blades
So I guess since 5 out of the 8 posts in this thread are my own, no one else really has an issue with this?  It this the only place where the midi remote control doesn't work right?  or is it just the only place the doesn't work and I happened only to need the one part that fails?
 
Do you understand what I'm trying to do here?  I have two outs on my Layla 3g.  The headphones are out #1, the monitors are attached to out #2.  So I switch the main out to point to the two different outs on the sound card.  But to do this requires that I pull up the master bus and make the change.  It would be nice to be able to do this with a button on my controller.
 
This "switch on and off" the bus sends seemed like a perfect way to do it, but it just doesn't work when triggered from an external button - fine from the mouse, and from an external button, looks right, just DOES nothing.
 
Thoughts?
2014/06/22 23:09:05
Blades
I am bumping this post again to see if anyone has any idea how this might be addressed in X3.  I don't think it has had anything done to it, and as I have mentioned above, it's been an issue for a number of years - and something that seems like it should work - such a simple thing, but doesn't do anything with the midi remote where the literal click of the onscreen GUI control DOES work.
 
I started this thread almost 7 years ago.  Cakewalk team?  Craig Anderton?  Anyone?
2014/06/22 23:13:57
scook
I don't use ACT and not many of the X series posters visit this forum. This forum is for older pre-X series versions of SONAR. Maybe re-posting in the X forum would generate a reply or two.
2014/06/23 07:34:47
Blades
Good point scook - didn't even realize that the age of this planted it in an old version of the product.  I will put it over there and see if I get any traction.
2014/06/23 13:06:48
azslow3
Several observations:
  1. Switching on/off sends reset my audio engine, if done too fast, SONAR freeze...
  2. Doing so using CS API (I use my "AZ Controller" plug-in) works (while "Remote control" not, as you have discovered). So, the API is not broken in that respect. I do not know other plug-ins which can be configured such way, so that is not your way (till you want test AZC...)
  3. But toggling "Mute" on masters works as expected in AZC and with "Remote control"! I set "Master" (Bus) output to 1/2 and one send from it to 3/4. Then I have muted 3/4. "Remote control..." one button for all 4 mutes. Then it toggles all 4 correctly. Also "Mute" does not reset the engine in my case and I had no freezes in my short test (even toggling many times per second).
 
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account