jcsteh
Automation Items and Envelope Points
Hi,
As requested, I'm breaking the automation item issues down into separate ones. Sorry it's taken me a while to do.
The most urgent one, as far as I can see, is that there appears to be a disconnect between the automation items and the way Osara reads envelope points.
For example, I create an automation item with an lfo on the volume envelope.
If I start at the beginning of the time line and navigate right through the envelope points, it only registers that there are two - one at the start of the project and one at the start of the automation item.
If, however, I go to the end of the project and try to navigate backwards, it puts me at point 82 but won't let me go back any further than that.
There are related points to this that I definitely think could be part of the same issue.
When copying and pasting automation items, Osara's feedback says that an increasing number of envelope points are being added, i.e. every time you paste a fresh automation item, the number of points it says you're adding increases where the number should surely be the same
Also, when running the action that deletes an automation item but leaves the underlying envelope points, the envelope points aren't exposed even then.
There needs to be some way for us to tweek the points encapsulated within an automation item and to navigate between them.
Also, and I think this is related so am leaving it here, navigating between multiple automation items often gets stuck, i.e. you can go so far in one direction and no further, much in the same way as described above with the envelope points. I think this used to be an issue with envelope points, particularly when selecting multiple envelope points, when Osara envelope point navigation was just getting started so maybe the fix will be similar.
Thanks,
Justin
@Justinmac84 commented on Jan 7, 2018, 3:40 PM GMT+10:
For example, I create an automation item with an lfo on the volume envelope. If I start at the beginning of the time line and navigate right through the envelope points, it only registers that there are two - one at the start of the project and one at the start of the automation item.
You navigate envelope points within an automation item by first selecting that automation item. Once an automation item is selected, the envelope point navigation commands start moving through points within that item. Otherwise, you'd end up having to navigate through potentially thousands of points with no knowledge of what item they were associated with. Note that REAPER sometimes seems to also insert a point just before (but outside of) an automation item.
When copying and pasting automation items, Osara's feedback says that an increasing number of envelope points are being added, i.e. every time you paste a fresh automation item, the number of points it says you're adding increases where the number should surely be the same
I can't reproduce this. I had an automation item with 2 points. Pasting the item consistently reported 2 points added. Note that REAPER may insert additional points itself in some cases as I noted above. I guess it might do this if it must in order to obey the curve outside of the automation item or similar.
If, however, I go to the end of the project and try to navigate backwards, it puts me at point 82 but won't let me go back any further than that.
I wasn't able to reproduce that either. It might be good if you can create a sample project which reproduces this, but keep it as simple as possible. It should only contain what is absolutely necessary to reproduce the issue and no more. This will help to isolate the cause. Otherwise, it's kinda like finding a needle in a haystack. You should be able to do this even without any audio in the project.
Also, and I think this is related so am leaving it here, navigating between multiple automation items often gets stuck, i.e. you can go so far in one direction and no further, much in the same way as described above with the envelope points.
Please file a separate issue for that one. Thanks.
@Justinmac84, given the recent work in this area, are all the issues covered here resolved? If not, can you please outline the outstanding issues? Thanks.