when moving tracks and groups inside a folder, only the automation on audio and instrument tracks gets moved but not automation of group tacks.
the bug was also reproduced here by Greg at 1:53:58 during live stream.
why is it still not fixed ?
Steinberg, please fix this ASAP
Steinberg got many bugs which was not fixed by years… it’s the pain…
Its not a bug !
It is a part of the program that hasn’t been optimized for a certain behaviour, not a bug.
The Folder Data is not an event, Cubendo has the option of moving Automation with Event, there is no event on the folder track.
Steinberg have not implemented the Folder Track to recognise events within itself, it should be a simple code update, but it isn’t a bug.
Behaviour should be:
- Data on the Folder Track is a sum of all Events within the Folder Track.
- Data on the Folder Track is recognized by the program as an Event itself.
The workaround is simple, just select everything in the folder including automation and move it.
I mean not this bug, but several bugs like VCA, many visual bugs etc…
I think the VCA one isnt a bug either, if you mean where VCA acts funny regarding its position.
I think the VCA issue again is Steinberg never implemented the VCA system to recognize an official starting volume for the VCA, so you have to manually create a start point on the Automation.
Why they haven’t made it so it automatically does this who knows ?
There’s many things that appear to be missing something regarding implementing it, is it done on purpose ? to keep people on there toes, could be, because in every other DAW (inferior to Cubendo) these little issues are not present.
Not the only bug with VCAs.
The implications logic is faulty, making them unusable…
Explain the issue with them ? what scenario introduces the bug, ill test it my end see if i can replicate it.
The problem with Cubase’s VCA implimentation is that the programmers assumed that the automation of the VCA should be assimilated into the fader(s) that it is controlling.
The automation on a VCA track should be and STAY SEPARATE from the controlled fader(s) automation, and only calculated to produce a final value.
At NO POINT should the vca value be amalgamated with the controlled fader!
It should be separate and calculated on the fly.
Consider this case that happened to me today:
I have a simple VCA controlling two guitars that I simply want to lower during the solo.
I make the move on the VCA - so far so good.
Now a bit later on, I decide that my guitar levels (the faders controlling them have no automation yet, just the VCA) are incorrect and I want to write them in.
I place these faders into write with complete to front and end enabled - but now I see that automation has appeared on these two faders, to make them the same level all the way though and negating the vca move by inserting the opposite move…
That is simply wrong.
I am not sure where whoever programmed this got the information, but it is simply wrong.
The vca channel and automation should remain separate- NEVER amalgamate the automation into the target faders!! EVER!
PLEASE rewrite the code for the VCAs.
As ANY Cubase user will tell you - they are unusable.
Please consult a recording engineer like me if you need an explaination of how VCAs should work.
This implementation is horrible, broken and senseless!
Nuendo is no better!
Cmon guys - this has been broken for 12 freaking years…
A good workaround:
Try Grouping the event(s) with the automation in that section, then the automation from the Groups will move with the events.
Edit > Key Commands > Edit > Group & Ungroup
They temporarily allow grouping of events, parts, automation etc…
Group > move > ungroup
This is very big issue when working on big projects. This must be fixed ASAP.