Exchange/replace bug??

jeffjn wrote on 6/29/2013, 9:21 AM

I’m trying to understand behaviour in MEP 2013 and VEP X5. It involves the use of Exchange/Replace. Below is a simple demonstration but it affects many exchange operations.

Place a video clip on track 1, and follow it with a second clip.

On track 2, add a title and trim it so that it is slightly shorter than the first clip on track 1

Find a 3rd clip in the Media pool that is longer than the first clip. Use the Exchange mode to replace clip 1 on track 1 with the longer clip. The new clip is longer, and the second clip on track 1 is moved to the right.

Now restore the project to how it was before the Exchange operation and trim the title so that it has the same duration as the first clip on track 1. Repeat the Exchange operation.

Now, a gap has been placed between clips 1 and 2 on track 2.

Why? I don’t understand the reason for the gap being introduced. If there isn’t an object on track two, no gap is added.

Can anyone explain this, because it appears to be a bug to me.

Comments

jeffjn wrote on 6/29/2013, 10:14 AM

Added - here is a screen capture of what I mean...

[[VIDEO:cloud://]]

johnebaker wrote on 6/30/2013, 3:15 PM

Hi

This not only happens in VPX 5 but also VPX 4 and it occurs if the title is placed on a non adjacent track.

AFAICS no one has ever reported this as an issue in VPX 4

John

Last changed by johnebaker on 6/30/2013, 3:15 PM, changed a total of 1 times.

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 23H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

jeffjn wrote on 7/1/2013, 6:29 AM

Thanks - yes there are a number of ways to induce this behavior. Can anyone think why it might be deliberate?

I've put in a support request asking for an explaination.

jeffjn wrote on 7/1/2013, 8:20 AM

Swift response from support, forwarding a bug report to the developers -)

jeffjn wrote on 9/12/2013, 8:41 AM

...and it has been fixed in the 2014 version :-)

Pleased seeing bugs fixed when reported, even if I did have to wait (obviously 2014 was already in dev when I posted the bug)