Well this is ridiculous. You are already adapting to the tedious ARA nightmare. If you have to bounce first, where is the improvement? This is an improvement for the worse. With VST3, all this wasnt needed.
I want official support for VST3 back. Yes you have to transfer first but can rely on.
I’m personally not adapting, as it’s how I work with everything. I just prefer raw audio files as it makes recalling and archiving so much easier the less dynamic assets you have. Even VST Instruments I put to audio.
I’ve not worked the other way around to know the problems reported here. If it’s as bad as people are saying (i.e. save a project, re-open it and edits gone) - then yes that’s incredibly bad.
I wish someone could post the steps to reproduce this, really.
Bottom line is that I have zero trust in any plugin, which is sad in itself really. But what I’ve learnt in the years of opening up older projects in past years.
If lots of say it is happening (and it IS) and we also say that it’s impossible to reproduce to order because it happens randomly, why do people have trouble understanding that? I’ve done experiments where I had a single audio track in a project and it failed to load correctly. On the other hand I have had it work fine in projects with hundreds of audio tracks (not all Melodyned of course). I have tried the recommended 1024 sample buffer and smaller and larger. It’s not my hardware. It’s a flaw in the programming of Steinberg or Celemony or both. My money is on Steinberg because ARA works in Presonus Studio One (which I also own).
I don’t think anyone has a problem understanding it, it would be nice to be able to reproduce it to demonstrate the issue and would ensure that a fix could be made.
There’s a few actions that could be carried out at project save which could affect linked files.
For example running functions on the pool, ‘saving as’ to different locations/drives, could be backing up the project from a temporary to permanent location, could be related to running the application as an admin, or even using the same audio folder for multiple projects - all are potential pit falls.
I presume none of those apply to anyone having issues?
I don’t do any of these things to the pool. I just use the software the way it’s supposed to be used. If it was easy to reproduce, we would all have posted solutions by now! All we get from people here is “Bounce the audio”. No help at all.
I didn’t mean skijumptones personally!
Yup that’s not quite a solution.
Oh and also those occasional “pak!” high amplitude clicking noises whenever an ara segment begins that only bouncing seems to cure.
Yeah, me also - as the Melodyned part begins, a litle click? Sometimes it’s louder, then maybe a few times softer. Dragging the start point of the part back or forwards just moves the timing of the click. Been happening since I shifted to ARA, and affects Cubase Pro 11 and 12.
Ya it can “click” 7 times strat and the 8th time is click free.
And it is NOT a CPU issue.
I’ve also experienced loosing hours of melodyne work. I’ve now made it a habit to bounce the vocal after editing. Not ideal but it’s currently the only way to not loose my work.
My solution to these ARA issues is simple - I just use Melodyne the old-fashioned way. It worked before ARA, and it still works now without ARA.
Yes, and you have all the old limitations. When ARA is working well you can move parts around on the arrange page and they will follow in Melodyne, you can change volume of parts on arrange page and Melodyne will follow… you can copy things blah blah. You get the point?
‘When ARA is working well’ - You get the point?
Yes. I get the point. Which is why I was one of the first to come here and complain about ARA not working reliably.
Reported fixed in 12.0.20 ? How’s it working?
[EDIT: Typo fixed, “12.0.20”, not “11.0.20”]
No, it’s not fixed in 11 or 12. Ed
I just downloaded 12.0.20 so will give it a try tomorrow when back in studio.
Yup, thats what im doing.
Please let us know what you found.