jefftravilla

I'm interested in ideas here too. I used to use Audreio for this purpose, and it was fantastic. It even worked remotely (not on a local network). I think you had to pay for credits for the remote access. I went to use it today to make a tweak to a mix from a remote computer, but Audreio doesn't exist any more. Bummer. For the local network thing, I think I'll explore some of the Airplay ideas. I also enjoy monitoring on an iPhone speaker to test the mix. I like ensuring that you can hear at least a little of the kick drum on a tinny iPhone speaker and then adjusting via better monitors to taste. To solve my remote access issue today, I logged into the mix computer with Chrome Remote Desktop. Then I used a loopback audio router from a screencasting app I use called Screenflix. I chose that as my Logic Output. Then chose the same as my mic input on a Google Meet and joined the same Google Meet from my remote computer. The audio was complete garbage but it was passable enough to hear levels and make guesses at EQ.

While the VCA faders are really helpful for this functionality, they are more useful for controlling groups. To use them for controlling the relative volume of each track makes for too many faders. The relative automation lane is very helpful, but I don’t believe it quite has maximized the expected behavior user experience. Here’s what I would expect. Feel free to disagree. The default volume lane is where people are going to set their rough mix levels and begin writing their automation. Once they are happy with that automation, they are going to want to “lock it in” and control/audition the overall volume without committing to additional written automation. When I am in “read” mode and click the “relative” option from the automation modes, I expect the relative lane to open up, locking the first lanes automation greyed out behind it - the way it does in relative latch mode, for example. From here, still in read mode, I would expect to be able to control the fader without drawing automation in the same way that the default volume fader works in read mode when no automation is written. This would create a more cohesive user experience across the different methods of automation and intentions for adjusting track volume. Lately I’ve been using the trim window to accomplish this, but their isn’t a way for me to grab that from my hardware controller.