DR18.6 ripple delete unusable

I know there are already another threads about this bug, but on the real day-to-day work, this is something unbelievable.
For everyone who hasn't read about it yet, when you ripple delete something, the clips forward in your timeline get out of sync!
Will this been taken care of on 18.6.1?
Hope so, as it's crazy to work selecting all tracks forward and moving them, instead of doing a simple ripple delete.
@Peter Chamberlain looking forward to reading your input on this.

For me, 18.6 is unusable for this reason (MacBook in my signature). Roll back to 18.5.1 to get any work done.

Surprise 18.6.1 hasn't been released by now to correct this.

I know there are already another threads about this bug, but on the real day-to-day work, this is something unbelievable.
For everyone who hasn't read about it yet, when you ripple delete something, the clips forward in your timeline get out of sync!
Will this been taken care of on 18.6.1?
Hope so, as it's crazy to work selecting all tracks forward and moving them, instead of doing a simple ripple delete.
@Peter Chamberlain looking forward to reading your input on this.

Unless I am missing something, I don't have this problem with ripple delete!

I know there are already another threads about this bug, but on the real day-to-day work, this is something unbelievable.
For everyone who hasn't read about it yet, when you ripple delete something, the clips forward in your timeline get out of sync!
Will this been taken care of on 18.6.1?
Hope so, as it's crazy to work selecting all tracks forward and moving them, instead of doing a simple ripple delete.
@Peter Chamberlain looking forward to reading your input on this.

Unless I am missing something, I don't have this problem with ripple delete!

Win or Mac? Simple or long, complex timeline?
There are reports of this not happening in simple projects…

I don't have this problem with ripple delete!

I couldn't trigger it either, even on a 7 hr timeline.

No probs seen here Windows 11 18.6 Studio

I don't have this problem with ripple delete!

I couldn't trigger it either, even on a 7 hr timeline.

How many clips on your timeline on a single track, Jim?

No probs seen here Windows 11 18.6 Studio

Yes have this problem on Windows 11 18.6 Studio - basically makes it unusable.

[Peter Chamberlain]

While many don't see this issue for those that do, please go back to 18.5.1 until we release an update.

While many don't see this issue for those that do, please go back to 18.5.1 until we release an update.

Thanks Peter. Expected timeframe for the update?

I went back to 18.5.1 it was just unusable on a very simple timeline.

How many clips on your timeline on a single track, Jim?

About 30 half hour clips cut into about 400 segments.

While many don't see this issue for those that do, please go back to 18.5.1 until we release an update.

Thanks Peter. Expected timeframe for the update?

Having spent many decades writing/maintaining software I doubt that BMD will be drawn on a timeframe and the industry-standard response is "how long is a piece of string".

Until the cause of the problem is identified (and that can take the most time, especially when it's something that affects only *some* users) then the time-to-fix can't be calculated.

The *great* thing is that BMD have (finally) acknowledged the problem, offered a mitigation (downgrade to 18.5.1), and confirmed they're working on a fix. The only additional thing they could/should do is post an advisory on the 18.6 download page warning that users of this version may encounter performance issues.

I can recreate this bug easily with a single source file on a very short timeline with just a few cuts. All it takes is add audio transition to an edit point and perform a ripple trim.
Win 10.

I can recreate this bug easily with a single source file on a very short timeline with just a few cuts. All it takes is add audio transition to an edit point and perform a ripple trim.
Win 10.

I tried replicating it like the way you did and still did not happen. Clearly this bug does not happen with everybody.

I can recreate this bug easily with a single source file on a very short timeline with just a few cuts. All it takes is add audio transition to an edit point and perform a ripple trim.
Win 10.

Can you create a .dra to rule out something funny for the people who does not have the problem?

Having spent many decades writing/maintaining software I doubt that BMD will be drawn on a timeframe and the industry-standard response is "how long is a piece of string".

For a mild bug, I'd agree.
For something which makes the software unusable, I can't

I'm still puzzled on how some don't seem to have this issue. It's immediately obvious so it's not that it takes anything special to trigger it.

When I tested 18.6 I fiddled with my PC for a whole morning until I gave up and downgrade, I also created a new timeline and added some simple content to test.

The *great* thing is that BMD have (finally) acknowledged the problem, offered a mitigation (downgrade to 18.5.1), and confirmed they're working on a fix. The only additional thing they could/should do is post an advisory on the 18.6 download page warning that users of this version may encounter performance issues.

I'd like to stress out the "finally". I'm disappointed by how BMD is handling this severe (for some) issue.

Also, the ripple delete was just number one of the bugs, the whole Resolve had become sluggish as hell. Hopefully it's the same bug.

I'm experiencing a bug that's likely connected to this. Whilst my clips don't go out of sync, every ripple delete attracts a hanging of the timeline for around 4-6 seconds. This includes ripple deleting of entire clips and ripple trims at header or footer. Also undoing those actions also attracts the same 4-6 second delay.

My computer is pretty high-end with an RTX 4900 and Intel 13900X 16C/32T running off fast nvme drives.

This fault didn't occur with any previous versions of Resolve Studio.

I'm still puzzled on how some don't seem to have this issue. It's immediately obvious so it's not that it takes anything special to trigger it.

There are so many variables that could trigger this problem with some users, however is it possible that the type of media used has to do with this?

I'm still puzzled on how some don't seem to have this issue.

I have the opposite puzzlement - how do you trigger it?

If we can narrow down the variables, it might help BMD.

I'm experiencing a bug that's likely connected to this. Whilst my clips don't go out of sync, every ripple delete attracts a hanging of the timeline for around 4-6 seconds.

I wasn't seeing such a delay but definitely a much slower interface. Others have reported similar delays if not mistaken.

Code: Select all

I have the opposite puzzlement - how do you trigger it?
If we can narrow down the variables, it might help BMD.

Why do I feel they know exactly what's going on? A bit more dialogue with the users might stop my pessimism!
If they didn't know what's going on they would ask for more details. Instead so far all we've got is "we're looking into that".

I removed 18.6 so I cannot test anymore. I just upgraded from 18.5.1, started working and at the first ripple delete (start to playhead or end to playhead which I mapped with Q and W) the sound would be messed up/out of sync. I tried with Razor tool and DELETE and it was the same. Switching to another timeline and back would fix the sound.

My footage is H264 from iPhone, iPad and OBS.

<<
Switching to another timeline and back would fix the sound.
>>

I found that I had to quit and re-restart. I didn't think of switching to another timeline and back.

Is there a known issues list somewhere that I could refer to?

Getting back to my first post, I decided not to roll back to 18.5.1
I can't afford the risk of something unforeseen ruin a very complicated project I'm working on. Delivery deadlines don't help as well.
Instead, I forced myself to work as if ripple delete didn't exist at all. Feel free to call me crazy... it's not an impossible task.
That said, all we can do is ask for 18.6.1 asap.
And that new upgrades don't mess up with the basics of the tool.

On my Mac I can't replicate this issue. Ripple delete working fine.

To those that can't replicate it, can you try my .dra?
viewtopic.php?f=21&t=188357#p982140

Does that slow down (Reminder: Delete the first clip in the timeline)?

To those that can't replicate it, can you try my .dra?
viewtopic.php?f=21&t=188357#p982140

Does that slow down (Reminder: Delete the first clip in the timeline)?

No, deleting first clip happens immediately

I can recreate this bug easily with a single source file on a very short timeline with just a few cuts. All it takes is add audio transition to an edit point and perform a ripple trim.
Win 10.

Can you create a .dra to rule out something funny for the people who does not have the problem?

Sure, here it is:

Ripple_BUG_18.6.dra.zip

(205.74 KiB) Downloaded 39 times

Unfortunately, after reimporting dra back the "bad transition" on the clip is gone. But as soon as I perform a ripple trim - it reappares again.

image_2023-10-03_095319793.png (51.52 KiB) Viewed 1981 times

And one more update:
Closing Resolve and reopening project clears "bad transitions" ...

I can recreate this bug easily with a single source file on a very short timeline with just a few cuts. All it takes is add audio transition to an edit point and perform a ripple trim.
Win 10.

Can you create a .dra to rule out something funny for the people who does not have the problem?

Sure, here it is:

Ripple_BUG_18.6.dra.zip

Unfortunately, after reimporting dra back the "bad transition" on the clip is gone. But as soon as I perform a ripple trim - it reappares again.

image_2023-10-03_095319793.png

And one more update:
Closing Resolve and reopening project clears "bad transitions" ...

I tried and deleting the first clip happens instantly.

Getting back to my first post, I decided not to roll back to 18.5.1
I can't afford the risk of something unforeseen ruin a very complicated project I'm working on. Delivery deadlines don't help as well.
Instead, I forced myself to work as if ripple delete didn't exist at all. Feel free to call me crazy... it's not an impossible task.
That said, all we can do is ask for 18.6.1 asap.
And that new upgrades don't mess up with the basics of the tool.

You can backup your database to be sure but it's a straight forward process, you uninstall and resinstall the older version: your database will be there, your preset, plugins, power bins with you assets all is going to be there

I have this problem as well on Windows 10.
I have a pretty complex project where I am using compound clips to keep the multiple audio tracks from my rushes in order.
Workflow is Rushes in. Edit sync pulls of Rushes with upto 5 audio tracks.
Edit from the sync pulls as compound clips so the audio all goes into 1 track.

Doing ripple cuts on these Edits either puts the audio out of sync or plays the wrong bit of audio for the first half a second. Doesn't always happen but most often. If I decompose in place the audio then everything goes back to how it should be.

I too am avoiding ripple edits for now.

Nick

Also having this problem and other similar audio issues. Windows 11. And this is on top of 18.6 crashing so often I had to make sure I wasn't running Premiere.

Just installed 18.6.1 and did the first tests.
Now ripple delete happens instantly, unlike on 18.6 where it took some moments to execute.
And there's no de-syncing anymore.
Problem solved.
I suggest getting back to work and stop all the non-constructive criticism. Do you see any advantage for BMD on these issues? I don't, so I assume they're as interested in solving them as we are.

Great. yes 18.6.1 fixed the issue and pretty quickly too. You wouldn't get this kind of service from AVID.
Very pleased with the fix.