I am also seeing the issue, but only with media with a non-integer frame rate such as 23.976, 29.97 and 59.94. Not with 25 or 50 fps. I suspect a rounding error was introduced when the new variable frame rate support was added in build 424.

@NickHope & @xberk - I'm using 29.970 and I can't reproduce this. I've got this setup with with both Single Track and Two Tracks. I've altered the Timeline Scales which would and wouldn't challenge my setup and I can't repro:

Here's my Options Menu too:

How many frames did you delete?

@Marco. - I followed the instructions which called for one.

@xberk - Looking at the COW Forum, try turning on “Snap to Grid”. I notice you haven’t and I have.

@Grazie .. Ok. I reinstalled Build 424. Turned on Snap to Grid. First test did not yield an overlap, the second did. And the third. And fourth .. and so on .. (no matter the length of the deletion) but after a while, no overlap on further tests .. and then, like a bad penny, it appeared again. Bug !! .. Thy name is inconsistency. The OP reports longer overlaps than 1 frame too. I've yet to see that.

I think Nick is right about the rounding error or some kind of math error in the code that under certain circumstances causes the overlap by a miscalculation in Auto Ripple of how far the timeline must move. It's far over my head how that math is done. But Nick's theory about the variable frame rate fix in Build 424 causing the problem, makes sense to me.

But, that still leaves us with --- why would your system not have this problem? What's different? Can we rest easy knowing Grazie is bug free?

Nick .. I tried an interger frame rate. No bug.

From my experience (trying and reporting at CCOW, due to Paul's question), at first I reported I couldn't duplicate and tried many time with several different medias and many different settings.

Then this morning I tried again and the very first cut it happened and after about 50 more attempts, I could not duplicate it. And when checking the first cut overlap, the overlap was gone!

I'm thinking everyone has this issue, but for me at least it is so seldom that I was lead to believe I didn't have the issue.

Our doggedly Testing May flag up an “issue” but now somebody needs to do some Input Algorithm series analyses to “prove” this error lies within the program. The intermittent qualities of bugs are notoriously slippery to catch. Anybody remember the issues I’d had with Media Manager breaking in VP6 but not in AcidPro? That eventually was placed at the feet of Syncfusion.

Am I Bug Free? Now that’s something nobody has asked here on the Forums?

My guess is the cause is hidden somewhere in a strange background process happening within the split process. I'm still investigating, splitting triggers some others strange things in this build which does not happen in other versions. So rippling maybe would work fine if only split would work fine before.

Hah! Reproduced:

@xberk

4. Move the timeline cursor exactly one frame (left or right) and split the event again at that point.
5. This leaves a one frame event on the timeline.

Wishing to be exact, I concentrated on selecting EXACTLY ONE Frame, I did this by using the KeyBoard Command to select ONE Frame and NOT moving the Cursor Manually, and then Splitting the END of the Selection - this is EXACTLY ONE Frame. This way no reproduction. So, inadvertently, I've flagged-up convergence.

Now this IS interesting. It would appear that KB Strokes work. Could THIS mean that accuracy is down to using KB Strokes and that Manual Manipulation can't be relied upon?

"Could THIS mean that accuracy is down to using KB Strokes and that Manual Manipulation can't be relied upon?"

I'd say in a certain manner this deeply depends on the personal tremor-factor. 😁

I'd say in a certain manner this deeply depends on the personal tremor-factor. 😁

Well, @Marco. , joking aside, using StoGrid SHOULD overcome that.

Does it make a difference if your timeline starts at a timecode other than 00:00:00?

Not here. But it makes a difference where in the timeline the event is placed. If I can repro the issue moving the event 1 frame back or forth can make it work again. And same is for the frames of the event where the splitting happens. Shifting the splits 1 frame back or forth makes a difference.

It sounds like it could be a Drop Frame vs. Non-Drop frame math error.

Yes.

This issue has been prioritized for fixing. See my comment here and the one below it.