@Trucky
just a quick detail:
in the red track (store presets) you can still set it to Write by using the mouse in the inspector.
Per the Studio One 7 Reference manual...
Track Presets can be used to store and recall all aspects of a Track: names, instruments, routing, pan, levels, and any variables that can
be set in the Inspector.
Note: Track Presets do not store Note Events, Audio Clips, Event FX, or Automation.
Thanks for the info Trucky
Makes perfect sense a preset doesn't store any of the above but in this case a track preset is not responding to native functions available for tracks
- shortcut for Write
- shortcut for Read
- shortcut for Touch
- shortcut for Latch
- shortcut to Auto Off
which are basic functions available for tracks. But only them. and that's why it sounds like a bug to me.
But I've got a theory:
f.e. in this picture the same track responds to native shortcut for Solo per example but in the same track if I press T (Write) it doesn't respond
So if I open the Shortcuts page I can see:
You'd expect both to work but the latter doesen't in this case.
But, my game dev buggo tracker mindset, made me discover another variable:
if you load a track preset as mentioned they don't work and I'd bet 20 quids that
1- the track preset saves the automation tracks (as shown here)
2- the automation section in the inspector is not aware of them at first
considering automation options become available only if there is an automation track
Moving forward:
Then I tried activating them by mouse clicking in the inspector and eventually re-try the shortcuts and
they worked for the track presets.
But the plot thickened when I tried to replicate it again in a new session:
it didn't work no more.
Then I added a new track, created a new automation track, and shortcuts
began working on the preset track again.
Tried again doing the same on a new session, but this time
didn't work.
As you can see behavior seems to be quite unpredictable and, given my experience in game dev, I'd say something is underspecified somewhere.
More specifically, if automation tracks are stored within the preset (to be clear, empty automation tracks
without any automation data and storing automation tracks within a preset is allowed by S1) appear to be undetected within the preset bundle.
- track preset allows to store them
but
- once preset is loaded, they're not detected by the automation system and the discrepancy is that
- the automation options are available (S1 is aware there are automation tracks in this instance)
But if I press the shortcut for "write"
it doesn't get detected.
My guess is that there's something underspecified between the automation tracks embedded in a preset and the automation options panel.
I other words they're not talking to each other when the track preset is loaded for the first time.
But as mentioned in the
red &
green tests above, results seem to be inconsistent anyway.
My DIY programmer's head makes me think what the code could be missing is something along these lines:
If a track preset is loaded (Instrument & VST)
- a check if there's any automation track stored in the preset (code allows you to do so)
- a "
true" or "1" state variable that would activate the automation modes panel in the inspector (and as a consequence the automation shortcuts will start working)
But that's just my speculation.
Is there a place in the Stuio One + where I can submit this for further investigation from the dev team?
