aMUSEd's Forum Page

OK we are post 2.09 so is this on the roadmap for a fix yet? I’m sorry to have to keep bringing this up but please understand that the current implementation basically makes recording synths with automation unworkable for me at present and I see this as a very serious issue – to show how serious I took this screenshot which I hope demonstrates the extent of the problem

here I think it is plain to see in this relatively simple sequence example every time I adjust the cutoff and then switch to the res knob, the cutoff drops to zero and every time I adjust the res and then switch back to cutoff it does the same – all the time having the cutoff at zero makes the sound silent so I would hastily adjust it back only to then have the res drop down and have to be corrected. It’s like I was fighting the host all the way and this is just a simple example.

This is not a bug with this particular VSTi (Korg Legacy Cell) – I have encountered similar behaviour with every synth and effect I have tried to automate and I chose LC as the example as it is widely known to be a stable and well established “classic VSTi. No host should do this – it takes away control from the musician – not one of those drops to zero in either param was intentional and even if I could edit them out afterwards the whole flow of the track and of my playing was ruined.

@H-man wrote:

Sounds to me like this is drifting a little 😕

Isn’t this FR basically as follows:

Change “New Uniquie copy” to “Save Unique Copy”, add the option for timestamp, rename or sticknote and make it available from the arrangement window?

I’d be pretty happy with that.

Well yes instead of “save as” it could be “save unique copy as” and I would be happy. The point is I would like to be able to do it as I go along and cumulatively, not in advance. I don’t really see the problem with this in itself.

Yes I know I can do that (in fact that’s what I am doing) but it’s back-to-front compared to being able to save copies along the way at key points as I make changes. At least it ensures I always have a pristine versions but it doesn’t flow as easily for me as being able to “save as”. Maybe I’ll just have to do as you said and have one arrangement per project and ditch the whole arrangement concept.

I’m sorry but maybe I’m not being clear enough. If I save a phantom copy or a unique copy it is an exact replica of the current state of the arrangement I am working on. That is fine in itself. However in order not to lose that copy I have to then save the whole project which means it also fixes the original arrangement in that same state when I would like that one to remain unchanged. That to me is the point of a “save as” command – it makes it possible have multiple snapshots of the arrangement while at the same time avoiding overwriting my original arrangement (or any of the snapshots) so can always trace my steps backwards

Like I said Tracktion manages this very well – you also have Projects in Tracktion but they are more like folders and you can save multiple variations in the same project.

I’ve tried that now but it doesn’t work how I need it to at all. The first time I created a new arrangement and laid down a couple of tracks of midi. Then I wanted to save that version. If I had a “save as” for arrangements I would be able to save that iteration without it affecting the previous (blank) version which is what I need from this function, so I can cumulatively add different versions but still go back to my starting point if I need to. So I saved a Phantom copy as you suggested but then when I reopened Podium I found it had vanished. I realised I had not saved the project the new copy was in!! (in Tracktion this would not have happened – a saved copy is a saved copy).

Anyway I started again and laid down some midi, made a phantom copy and this time saved the project as well. However the next time I opened it I found that both versions were identical – in other words saving the project (as I had suspected actually) saved both versions but in the last state of the first version. A “Save as” would not do that if I chose to save the second version as a new iteration and left the first version unsaved.

It seems there is stuff to iron out with the current project/arrangement model. A proper “save as” for arrangements would help, and maybe also something like Tracktion’s project management which is similar in it’s logic but does not require one to save twice.