Add Across Tracks - incorrect alignment

Greg N wrote on 12/20/2024, 5:09 AM

I recently upgraded from Vegas Pro 20 to 22 and am seeing some bad behavior in v22 build 194.

I use multi-track audio with my productions, so I frequently drop 12 to 32 audio track *.wav files onto the timeline. The way I do this is by dragging the files into Project Media, selecting them all and then using right-click to drag them down to the timeline. This gives me the option for "Add Across Tracks" as shown here:

In version 20, when I did this the 12 tracks would be aligned in time. Now, with version 22, they end up sequential in time, as shown here:

While not the worst problem, it sure is a pain to have to drag each one of these newly-added events to the left to align them all to the same time. I should not have to do that.

I have looked through Options -> Preferences to see if I have something set incorrectly but found nothing. I have found a clunky workaround to this issue by using "Add as Takes" instead of "Add Across Tracks" and then doing Tools -> Multicamera -> Expand to Multiple Tracks, but I really shouldn't have to do that. So, it would be great to see this issue fixed.

While I am on this topic, let me mention one other related issue. Way back in version 18, when I dragged multiple files into the Project Media window, those files would stay highlighted. That made it very easy for me to right click the group and then drag them down to the timeline. However, when I upgraded to version 20 the files no longer stayed highlighted after dragging them into Project Media. As a workaround for larger projects, I ended using Custom Bins in Project Media so that I could use Ctrl-A to select the group of newly-added files to drag them down onto the timeline, but I still do miss that nice feature back in version 18 where the files that had just been dragged into Project Media would stay highlighted. It would be nice to see that behavior brought back!

Comments

3POINT wrote on 12/20/2024, 5:19 AM

@Greg N That's a known bug, hopefully fixed in next build.