Since upgrading to Studio One 4.6 my Track Automation is behaving inconsistently. It reads correctly if the tracks are Audio but NOT if Midi.
Example – I recorded a virtual instrument track and when mixing decided to pan the chords hard Left followed by hard Right, from bar to bar. I created a Pan automation by touching Pan slider in Console and dragging ‘hand’ onto track, then plotted the points to suit. On playback the automation didn’t respond continuously – it recognised the first instruction to Pan hard Left but stayed there, ignoring the following hard Right pan. The corresponding Pan slider in the Console will MOVE accordingly as Automation written BUT IT DOESN’T PLAYBACK AS WRITTEN. But if I just play the track and manually move the Pan slider with mouse, the playback responds to my movements.
To complicate things, when I saved the song last night and opened again today the Pan automation that wasn’t working last night DID RESPOND as written – so I thought that’s strange, and continued to write further instructions. When I then played back from beginning of track the Automation refused to respond, contradicting what it just did moments earlier. And from that point I was back to square one from last night’s session.
I have 3rd party instruments running through Kontakt and other independent Host engines and none of them respond to Track Automation when Added from the Audio folder. However, creating Automation from a CC number assigned to the Pan Slider within a virtual instrument interface and added to Track WILL READ FINE.
So I can temporarily solve the issue by converting Midi to Audio or through CC# but I’d prefer to use my normal method that’s worked fine for last 5 years.
Anyone else with this issue..?
I have volume automation on for one MIDI track in a song that randomly stops working. If I move the playback cursor before the automation point and play it again it's fine.
I tested on a 8 bar with Waves Element synth - and cannot reproduce.
So I continued and added Cakewalk Dimension Pro and redirected midi out to that.
So no response to pan automation - and this is because redirecting midi out does not redirect that audio track automation - so no longer valid.
So had to copy first automation onto new pan automation for Dimension.
Further I figured if something to do with conflict - both CC#10(pan) and track pan - so added that on midi track and assigned that to pan inside Dimension.
All that happend is that audio out from Dimension was panned as CC#10, and the track automation for pan were working on what it got. If that was panned all left - there was nothing for track automation to work with.
A couple of thoughts
- is there any CC#10 at beginning of track - since when you start playback from start it suddenly stops working? It could fit that - but then you also see nothing on meters if that is panned, as I discovered. Pan is done after meters on track automation. So adding a bus in between and looking at meters there is should say what you hear.
Note: once entered a midi CC in StudioOne you cannot remove it - it stays even showing no nodes.
- anything that midi was redirected - but since track automation does not follow target of midi, but what was target when created - something strange here?
I so it all seems to work as expected here - but also had strange things happening in one session which are gone next time opening song.
- so see if it matters - closing song and then reopening again?
Just a few ideas....
kingzo1 wroteThe corresponding Pan slider in the Console will MOVE accordingly as Automation written BUT IT DOESN’T PLAYBACK AS WRITTEN.Do you have dropout protection set to anything else but Minimum? If yes, disable monitoring on the track or channel to hear the channel automation or set dropout protection to Minimum.
Thanks for all the responses to my Automation issue.
Nile’s suggestion has worked fine, i.e. setting the Dropout Protection to Minimum. Mine was on Medium as I found it helped solve a problem I encountered when recently mixing down songs for mastering and finding that the mix imported into Project wasn’t faithful. So thank you very much Niles.
The ‘Low’ dropout protection also works – in both Minimum and Low settings I don’t have the Green ‘Z’ latency setting appear – only with Medium and settings above.
I created a Support Ticket with Presonus but I am yet to see their response. But I think if having different Dropout Protection settings can affect the way Studio One operates, they should perhaps make a warning list..?
Thanks for your response. You lost me a little with the CC10# explanation. The parameter that was giving me issue is the ‘Pan’ setting located in the Audio folder when you go to Add/Remove when in Automation mode. So I deleted that and applied a ‘Learn CC’ to the VI interface which controls panning and used that in the Automation to write my intentions – that works fine. There was no other CC# at the beginning of the track to counter my co-ordinates. Closing and re-opening also didn’t work.
Niles has solved my issue by directing me to set Dropout Protection to Minimum (mine was on Medium) and all working well now. Seems Dropout Protection affects certain Parameters within Studio One – perhaps Presonus should issue a list of potential issues when choosing different Dropout settings..?
Users browsing this forum: No registered users and 12 guests