V. 6.0+ Auto-Stretch Bug

[muorsic]

Hello Reaper family!
Auto-stretch timebase is a really cool feature, which allows me to take audio stems from another session with complex tempo track and adjust the tempos in reaper. The problem is - when I undo a tempo change I made, the stretch markers get displaced.
https://drive.google.com/open?id=1qP...8bBh8JrLZTD-87
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...ew?usp=sharing

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 (v6.11+dev0526a - May 26 2020)
Only workaround I found is undo to the point before I changed timebase..
Any idea what is causing it?

[Icchan]

Originally Posted by muorsic

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 (v6.11+dev0526a - May 26 2020)
Only workaround I found is undo to the point before I changed timebase..
Any idea what is causing it?

Is this related to a pre-release regression and what specific version?

This area of the forums is not for general bug reporting, but for specifically pre-release regressions/bugs that have been introduced within a specific pre-release so they're easier to stamp out before it's declared stable and pushed out to a release.

Or for testing new features and giving feedback on them so they can be polished to work as they're expected before release.

After it's stable, head to the bug reporting forum for general bug reporting

We need to be careful so that the goal of this forum doesn't change from what it's supposed to be

[muorsic]

Originally Posted by Icchan

Is this related to a pre-release regression and what specific version?

This area of the forums is not for general bug reporting, but for specifically pre-release regressions/bugs that have been introduced within a specific pre-release so they're easier to stamp out before it's declared stable and pushed out to a release.

Or for testing new features and giving feedback on them so they can be polished to work as they're expected before release.

After it's stable, head to the bug reporting forum for general bug reporting

We need to be careful so that the goal of this forum doesn't change from what it's supposed to be

Hi Icchan, still figuring out my way around here, my apologies. I am using only pre-released versions.. I noticed this bug before and didn't know what is causing it. I just wanted to point out its in the most recent pre-released version, and tracked it to the point this feature was added (6.0).
So this post should be in the general bug reporting?
Is it clear enough to describe the bug?
Anyway, thanks for pointing that out.