Solved Ripple Edit Gone Mad? Can anyone confirm?

[Vocalpoint]

All

Just wrapped a VO session and when I went to edit a take - I see this:



1 - Ripple Edit = on
2 - Range Defined - roughly a 7 sec slice to be "rippled" out.

Press Delete and....

3 - Instead of "ripple" editing and removing the selected range - S1v7.1 drives a 20 sec hole into the file and shoves the second piece -20 secs down the line



Is this just me - or what is happening?

Would appreciate any quick checks from the field.

This session is using my standard VO template which has been in play for years.

ADDITONAL INFO: Just pulled up a session from a day ago - and copied a section down the timeline to the 2:00 mark. Made a 3 sec selection and hit Delete - S1 v7.1 moved the right slice down the timeline a FULL 2:00. Wow - there is something major - way out of control here.

Should also note - in this session - done on Monday - the day v7.1 was released - I never needed to use Ripple Edit - so no discovery. But the bug is out of hiding now.

VP

 

[Trucky]

Confirmed!

Thanks VP! I'll submit a bug report to the developers for it.

 

[Vocalpoint]

Confirmed!

Thanks VP! I'll submit a bug report to the developers for it.

Whew! Thanks Trucky! Thought it might just be me.

Looks like I am going to have to revert back to 6.6.4 for the time being. This is a major issue for my work

VP

 

[Trucky]

@Vocalpoint - A Ripple Edit (only when "Follow" enabled) bug was reported earlier and fixed but I'm seeing the issue you're having when "Don't Follow" is enabled.



Please confirm if the issue you're having with Ripple Edit is only when "Don't Follow" is enabled...

 

[OutrageProductions]

Confirmed here as well.

 

[Vocalpoint]

@Vocalpoint - A Ripple Edit (only when "Follow" enabled) bug was reported earlier and fixed but I'm seeing the issue you're having when "Don't Follow" is enabled. Please confirm...

Trucky - Don't follow?

Assume this is a setting? If so - where to check. Do not recall changing this if I don't know even what it is

VP

 

[Trucky]

Open Inspector and check Tempo setting...

 

[Vocalpoint]

Trucky - can confirm I am on Don't Follow

VP

 

[Trucky]

@Vocalpoint - Thanks for confirming specific Tempo setting set to "Don't Follow" causes the Ripple Edit bug.

 

[Vocalpoint]

Heard from a couple other users that RE works fine when the track is set to Follow OR Timestretch.

Also noted that S1 defaults to Timestretch when adding a new audio track to either a new empty session OR an existing session. So I tested this and it works great.

So I figured - why not just change my template to use Timestretch - like S1 would in a new default state. I thought I would just "update" my VO template and change the single mono track in it to be Tempo = Timestretch and Type = Sound

BUT - S1 simply does not recognize this change? I open my template - update just these two parameters and resave As Template - overwriting my existing template - which seems to be fine. Then I start a new session based on this change and the tempo settings were not saved?

Is this another bug or what am I missing?

VP

 

[Trucky]

Heard from a couple other users that RE works fine when the track is set to Follow OR Timestretch.

Also noted that S1 defaults to Timestretch when adding a new audio track to either a new empty session OR an existing session. So I tested this and it works great.

So I figured - why not just change my template to use Timestretch - like S1 would in a new default state. I thought I would just "update" my VO template and change the single mono track in it to be Tempo = Timestretch and Type = Sound

BUT - S1 simply does not recognize this change? I open my template - update just these two parameters and resave As Template - overwriting my existing template - which seems to be fine. Then I start a new session based on this change and the tempo settings were not saved?

Is this another bug or what am I missing?

VP

Yes, the Ripple Edit bug report I submitted was specific to Tempo setting = "Don't Follow".

It's working for me when I changed the Tempo setting to "Timestretch" and Type = Sound and saved to a template.
Please post a download link to your template and I'll test it on my system.

 

[Vocalpoint]

Yes, the Ripple Edit bug report I submitted was specific to Tempo setting = "Don't Follow".

It's working for me when I changed the Tempo setting to "Timestretch" and Type = Sound and saved to a template.
Please post a download link to your template and I'll test it on my system.

Trucky

Tried this again - and it appears that if I take my existing template - add the two temp changes and then save as NEW - it works.

But the first pass - I took my existing template, added the two tempo changes and saved as EXISTING - and it did not work.

Probably another minor bug discovered here as well.

VP

 

[John Doesoe]

Open Inspector and check Tempo setting...

View attachment 409

While experiencing the Ripple edit issue previously identified I lost all ability to open the inspector. Had to close s1 and reopen song to be able to display inspector to change timestretch (Mac sequoia latest version v7) anyone else reported this anomaly ?

 

[Trucky]

@John Doesoe - Please update your signature (see link in mine) with your system specs as that helps when responding to issues.

 

[John Doesoe]

While experiencing the Ripple edit issue previously identified I lost all ability to open the inspector. Had to close s1 and reopen song to be able to display inspector to change timestretch (Mac sequoia latest version v7) anyone else reported this anomaly ?

Was impossible to display the inspector. I know where it should be but pressing I displayed markers not the tempo options .

 

[John Doesoe]

@John Doesoe - Please update your signature (see link in mine) with your system specs as that helps when responding to issues.

What do you mean by “update your signature “? I find no link sorry

 

[Trucky]

Click the link below in my signature...

 

[Trucky]

Whew! Thanks Trucky! Thought it might just be me.

Looks like I am going to have to revert back to 6.6.4 for the time being. This is a major issue for my work

VP

This bug is fixed now with the Studio One Pro 7.1.1 release...

Studio One 7.1.1 is online!

Hey everybody, Studio One 7.1.1 is online. Click here for the discussion thread: https://studiooneforum.com/threads/studio-one-7-1-1-discussion-thread.491/ _________________________________________________________________________________________ Version 7.1.1 Released (February 12, 2025)...

studiooneforum.com