Created attachment 128940 [details] Screenshot of inserted tracks SUMMARY Inserting a track, never goes where it supposed to and it creates a gap in between an existing Video and Audio belonging to the same clip. I have 12 videos in the project and need to insert a video track between V1 and V2. I select track V1, right click, Insert Track. ____________________________________________ The result is this: V1 and A1 remain the same. A2 is an empty track above V1. V2 shows audio track of what was A2. A3 is an empty track above V2 V3 shows what was V2 and this is expected as V2 would shift upwards to make space for the inserted tracks. But the corresponded Audio is not adjacent to it and I can only move it downwards, when it needs to be upwards. So, basically when it inserts a track above or below, instead of cutting between 2 fields, it skip one, hence splitting a pair of Video and Audio from the same clip. Hopefully this can be resolved quickly as I have a video mosaic to finish but I need to be able to insert tracks correctly. STEPS TO REPRODUCE I select track V1, right click, Insert AV Track, above V1. OBSERVED RESULT V1 and A1 remain the same. A2 is an now an empty track above V1. V2 shows audio track of what was A2. A3 is an empty track above V2 V3 shows what was V2 and this is expected as V2 would shift upwards to make space for the inserted tracks. But the corresponded Audio is not adjacent to it and I can only move it downwards, when it needs to be placed upwards. So, basically when it inserts a track above or below, instead of cutting between 2 fields, it skip one, hence splitting a pair of Video and Audio from the same clip. EXPECTED RESULT It is normally expected that any clips containing AV would be still be together after the tracks insertion. SOFTWARE/OS VERSIONS Windows: WINDOWS 10 ADDITIONAL INFORMATION Hopefully this can be resolved quickly as I have a video mosaic to finish but I need to be able to insert tracks correctly. This is a basic requirement.
Is it the same as bug #403443?
(In reply to emohr from comment #1) > Is it the same as bug #403443? Yes its the same in Windows 10.
Thank you for the feedback. So I close this issue as a dublicate. *** This bug has been marked as a duplicate of bug 403443 ***