Auto-Stretch Bug

[muorsic]

Hello Reaper family!
Auto-stretch timebase is a really cool feature that was introduced few versions ago. The problem is - when I undo a tempo change I made, the stretch markers that were created on Auto-stretch timebased items get displaced
https://drive.google.com/file/d/1qPM...JrLZTD-87/view
This is a link to a video that describe this issue, what I basically did was:
1. Created a click source
2. Glued it as audio
3. Changed timebase to auto-stretch
4. Made tempo changes
Works great so far!
5. Glued it again
6. Changed timebase to auto-stretch (item is already mapped to tempo map)
7. Changing tempos and auto-stretch works great! until...
8. I undo a tempo change and try to make any new adjustments.

Here is a link to the a session file, before I set the item to auto-stretch.
***Same problem appears when saving the file after setting the item to auto-stretch mode and clicking "yes" in the project tempo dialogue box.
https://drive.google.com/file/d/1Ift...M14qq3IGF/view

Problem appears both on Mac and Windows, and I noticed it since the feature was added (v6.0 - December 3 2019) and tried it on the latest pre-release as well.
Only workaround I found is to save and undo the tempo change manually..
Any idea what is causing it?

[gkurtenbach]

Originally Posted by muorsic

Hello Reaper family!
Auto-stretch timebase is a really cool feature that was introduced few versions ago. The problem is - when I undo a tempo change I made, the stretch markers that were created on Auto-stretch timebased items get displaced
https://drive.google.com/file/d/1qPM...JrLZTD-87/view
This is a link to a video that describe this issue, what I basically did was:
1. Created a click source
2. Glued it as audio
3. Changed timebase to auto-stretch
4. Made tempo changes
Works great so far!
5. Glued it again
6. Changed timebase to auto-stretch (item is already mapped to tempo map)
7. Changing tempos and auto-stretch works great! until...
8. I undo a tempo change and try to make any new adjustments.

Here is a link to the a session file, before I set the item to auto-stretch.
***Same problem appears when saving the file after setting the item to auto-stretch mode and clicking "yes" in the project tempo dialogue box.
https://drive.google.com/file/d/1Ift...M14qq3IGF/view

Problem appears both on Mac and Windows, and I noticed it since the feature was added (v6.0 - December 3 2019) and tried it on the latest pre-release as well.
Only workaround I found is to save and undo the tempo change manually..
Any idea what is causing it?

This bug is still in 6.47, easily reproducible, and has trashed several of my big projects. It really needs to be fixed.

I regularly get big projects corrupted by it: it results in the tempo map and items stretching getting badly corrupted so your project timing gets all messed up.

Also, the problem is that corruption can go unnoticed because its screws up the timing of items *before* the tempo change you are modifying. So I have ended up unknowingly saving the corruption to the file.

It also seems to happen to me without the "second gluing" described by muorsic, although I not able to reproduce that in simple a case.

Please fix: I love auto-stretch!!!!

Thanks!

[schwa]

Looking into this. The same problem occurs if *adding* tempo changes within the bounds of an item that is set to auto-stretch, right?

[schwa]

The latest development builds may have a fix for this. It would help us out if you could try it and give feedback in the prerelease forum!

https://forum.cockos.com/forumdisplay.php?f=37

[schwa]

With the fixes in 6.49, I'm no longer able to reproduce the bug in post #1.

This issue however remains:
https://forum.cockos.com/showpost.ph...9&postcount=17

What I find with that project is that opening it and immediately running the action "Media item: Clear and recalculate auto-stretch at project tempo changes" causes the markers to move. In other words, I think that project was saved in an inconsistent state. So the underlying problem is whatever sequence resulted in the project being in that state.

gkurtenbach it may not be possible, but if you are able to provide steps that can result in a project that then changes when the "clear and recalculate" action is run, please let us know.

[muorsic]

Originally Posted by schwa

The latest development builds may have a fix for this. It would help us out if you could try it and give feedback in the prerelease forum!

https://forum.cockos.com/forumdisplay.php?f=37

Hi! thank you so much, yes tested this again and it got fixed.
Sorry for the super delayed response.