Hardware Output Left Fader Reverts on Stop

[scoco]

Today, out of the blue, I noticed that Sonar's output level to my MOTU 8Pre ES was lower on left. In the MOTU's interface I could see the difference on the meter coming "from computer." But in Sonar the levels were equal on my master bus. I usually hide the hardware outputs in my console view. It wasn't until I looked at my hardware outputs that I saw that the left fader was set at -8.7. I right-clicked on the fader and saw a line that said "Revert to -8.7." But I can find no way to remove that setting. So, with any Sonar project loaded, I can set the fader to 0 before I hit play but it jumps back to -8.7 when I stop playback.

How can I eliminate that "Revert to -8.7" setting or otherwise fix this problem?

[Chaps]

Never seen that before, though that covers a lot of ground. Try this: Set the faders to 0.0 (or wherever you want them), right-click the one that changes, or each one, and select Value>Set Snap-To = Current. This seems to work for me. There is more about this function on page 1491 of the reference manual.  The unwanted change in fader position may be caused by the Set End = Current command, on page 1491 of the manual.

"Set Snap-to = Current
This command, which you find by right-clicking a fader or knob in the Console or Track views, sets the snap-to position of that fader
or knob to its current value. When you double-click a fader or knob, it jumps to its snap-to position.
For more information about the Console view, see “Preparing to mix” on page 912."

Also, make sure those faders are not part of a custom group.

[Bristol_Jonesey]

All that means is you could, if you wish, revert the value of the fader to its previous setting, which in this case is -8.7

• Double click it to set to 0.0
• Click the padlock icon to lock L + R together

[Noel Borthwick]

If you send the project file I can take a look at why it's resetting.

[User 905133]

post withdrawn 

   

Edited Wednesday at 11:46 AM by User 905133

[scoco]

Thanks to all for your replies. Here an update:

It looks like I was able to resolve the problem. I got to thinking about what was different in my setup and remembered I recently had set up a Mackie ACT control surface and connected it through rptMIDI to my Android tablet. TouchDAW is installed on the tablet. When I deleted that entry from the list of control surfaces in Preferences, the problem stopped happening in all the projects I opened and tested. It might be worth looking into on Bandlab's end, but I'm good to go at this point (with this particular issue - there are many more).

[User 905133]

Thanks for the update! Good to know what solved it for  you.

[msmcleod]

1 hour ago, scoco said:

Thanks to all for your replies. Here an update:

It looks like I was able to resolve the problem. I got to thinking about what was different in my setup and remembered I recently had set up a Mackie ACT control surface and connected it through rptMIDI to my Android tablet. TouchDAW is installed on the tablet. When I deleted that entry from the list of control surfaces in Preferences, the problem stopped happening in all the projects I opened and tested. It might be worth looking into on Bandlab's end, but I'm good to go at this point (with this particular issue - there are many more).

If you've got a Mackie Control Master fader assigned to the hardware out, the master fader on the Mackie will just control one side  - the solution here is either:

1.  Click the "lock" on the hardware output fader, so they always move together.

2. Re-assign the Mackie's Master fader to your Master bus in Sonar's Mackie Control dialog (under the utilities menu).

Personally, I prefer option 2 as having the hardware output fader at unity gain is pretty much essential in order to get your audio exports at the same volume as your mix.

[scoco]

msmcleod - thanks for the insights. Yes, if I had known about that and assigned the the TouchDAW Master fader to Sonar master faders, I would have seen the problem much sooner.

I really would like to be able to use TouchDAW with Sonar because I record a lot of tracks alone (and it usually takes me a bunch of takes to get what I want). But since I posted about this problem I have had constant problems with Sonar locking up or stuttering or audio completely dropping out. After my initial discovery, I deleted and added a new Control Surface instance for TouchDAW. When I deleted that new one, Sonar started behaving again.

Do you have any ideas about other settings that might be tripping up Sonar, even when the Android device is turned off?

[msmcleod]

6 hours ago, scoco said:

msmcleod - thanks for the insights. Yes, if I had known about that and assigned the the TouchDAW Master fader to Sonar master faders, I would have seen the problem much sooner.

I really would like to be able to use TouchDAW with Sonar because I record a lot of tracks alone (and it usually takes me a bunch of takes to get what I want). But since I posted about this problem I have had constant problems with Sonar locking up or stuttering or audio completely dropping out. After my initial discovery, I deleted and added a new Control Surface instance for TouchDAW. When I deleted that new one, Sonar started behaving again.

Do you have any ideas about other settings that might be tripping up Sonar, even when the Android device is turned off?

I've only used TouchDAW briefly myself, but abandoned it due to the whole Bonjour / MIDI network setup thing which I found I constantly had to reconfigure. 

I suspect this is your issue - i.e. when the android is turned off, it's wasting resources trying to look for it.   When it's on, delays in the network due to the high CPU usage could be causing the issue.

Microsoft are currently working on a native MIDI over network solution that will be built into Windows, so hopefully that will be far more reliable.

Another thing it could be... I'm not sure about your machine specs, but many people (mainly laptop users) have major audio issues when the network is busy, and end up disabling it (albeit temporarily) when using their DAW.  The issue there is that the network and USB ports used for the audio device are tied to the same resources on the motherboard.

Personally, I'd recommend looking at a different control surface solution.   If you don't mind not having motorized faders, the Korg nanoKONTROL Studio is fantastic.  The nanoKONTROL 2 is pretty good too... I've got one stuck to the wall next to my vocal mic!