When you apply an ARA process (such as Spectralayers) to an audio event, moving the event in the timeline or changing its duration is updated in the ARA Editor. So far, so good.
However, if I move an event (i.e., position it earlier or later on the same track in the timeline) and undo that move (Ctrl+Z), the undo is not reflected in the ARA Editor. It remains in the old position in the ARA editor and can no longer be played at all. It remains silent, both at the correct timeline position and at the “ghost position” in the ARA Editor. Strangely enough, however, length changes are indeed transferred correctly to the ARA Editor when I press Ctrl+Z.
This isn’t a Spectralayers issue either; I have the same problem with AutoAlignPost, for example.
Can someone confirm this issue? Has been like that in N14 and still is the same in N15 for me.
Not trying to justify this at all, but I’ve learned that when using ARA the less you do with the clips while extensions are active, the better.
Don’t move, duplicate, split, extend, nothing. You do all that before, use ARA, make it permanent, and then you can do all that again.
This way I find it manageable to use. Anything else is asking for problems.
okay yeah that’s a workaround but it should’t be like that, doesn’t it? Isn’t ARA meant as a non destructive clipbased processing workflow? At least it would be awesome if it would work like that and we could keep the flexibility of going back into the ARA editor and change things at any given time.
Yeah, ARA’s promise is that it should work like you said, but unfortunately that is not the case. I believe it is something inherent to the current state of the protocol, cause every single account I’ve read about ARA tells the same problems.
For me it is still worth it, though. Now that I’m used to working around its shortcomings I feel it is just another workflow. At least it is predictable, albeit very quirky. (I much prefer it over my days of RX Connect, and there’s nothing else that comes close to AAP2 anyways). But it would be great if it really worked as advertised, no doubt!
I tried with all 10 of my ARA plugins and all of them show the same misbehaviour in Nuendo.
However with all 10 of them there is no problem when using ARA in Studio Pro 8 (former Studio One) and applying undo after moving an event.
So it seems to be an error of how Steinberg implements ARA into Nuendo
okay thanks for your answers! I think I’m going to report it in the bug/issue collection thread for N15, maybe we are lucky and it is going to be improved.
Isn’t ARA meant as a non destructive clipbased processing workflow? At least it would be awesome if it would work like that and we could keep the flexibility of going back into the ARA editor and change things at any given time.