left-shuffle and ripple editing broken - X9 and 2018

[Davidk]

Elsewhere on the forum there have been posts about improving performance by raising the priority level of VS (from normal to high or realtime) within the operating system. Having experimented and found out how to do that in win7, I used VS2018 (v21.4.0.164, 64bit) to create a short, simple project file for test purposes: 2 clips, and a gallery item, 2 text items for a total of 30 sec play time. I saved that as a 2018 vsp, and an X9 vsp. There were no messages about losing function when saving as an earlier version file - which was expected - it was, after all, a simple file.

The problems came when I opened those files using X9 (v 17.7.0.12) and 2018 for the test, which was intended to be a simple timed render to see what those priority changes actually did.

First I opened the X9 vsp, it opened Ok, but the clips in the timeline were all spaced apart; see this screenshot

When I opened the 2018 vsp using 2018 I got exactly the same result. Moving the 1st clip to eliminate the gap, all the clips moved.
When I experimented with turning ripple editing on, and then moving one clip, I got this message (screenshot)

Clicking Ok moved both clips, not just the one selected, and did not move the associated text files, which is what rippled editing is about. I got the same results when using X9 and opening the x9 vsp.

First time I've seen this weird effect. Has anyone else experienced this?

[Ken Berry]

Did you turn ripple editing on for all tracks? Unfortunately, your second image is cut off at the extreme left hand side, and we can't see what state the ripple editing padlocks are in for each of the tracks.

[Davidk]

Hi Ken,
For the case where I took the screenshot, no, just on for main and title tracks, since those were the only ones that had content. But I've repeated it since reading your post: Open VS, open that vsp, clips still spaced, selected all tracks for ripple editing, and gotten the same result.

[Davidk]

Update
Originally, I created the test vsp in 2018, and then not only saved it, but 'saved as' X9 also.
To localise what may be occurring, I created the same test file - same content, slightly different name - using X9 in the first instance. And just saved it.

Then closed X9, re-opened it, and opened that test vsp. Opened without issues, and I was able to conduct the tests I'd had in mind: several, with close and re-start between them. Closed X9.
Opened 2018, and then opened that X9 test file. It opened without issues, and again I was able to conduct the tests I wanted.

Two conclusions come from this:
1. It is looking like "Saving As" from 2018 did something to the file that produced those timeline spaces between clips reported.
2. Ripple Editing functioned as normal/expected in X9. But when that X9 vsp was opened in 2018, there were no spaces between clips, but ripple editing did not work - moving a clip did NOT move the text associated with it.

So, why?