Strange behaviour in nested vegs

Cornico wrote on 1/29/2017, 7:38 AM

Trying to edit some parts of my vacation in Vegas Pro 14 build 211, I encountered strange behaviour in the main project as well in the nested vegs.
Placed dissolves do not play in the exported file and do not show in preview.
When I delete that trimmed event always another take (?)is lying underneath.
When I'm able to remove the first one most of the time at the event that stays the dissolve works.
A lot of times by deleting one event both are gone.
Who knows why there is a second "take" and why is the transition not working?

I'm trying to repair everything in Vegas Pro 13, but there also is that behaviour visible.
Repairing in 13 works, in 14 it becomes a greater mudle.

.
 


 

Comments

Former user wrote on 1/29/2017, 9:11 AM

Maybe looking at Expanded track view might give some clues?

Former user wrote on 1/29/2017, 11:30 AM


Another thing not normal in the troubled veg is the dissolve not being expanded at 38 seconds on the timeline. But yeah, it does not give any clues as to why it is a problem.

JackW wrote on 1/29/2017, 1:46 PM

I've had this exact behavior from time to time. It appears to be caused by a duplicate event having been created. I'm never certain what I've done to create it, but the behavior is identical to what you show. Right clicking on the event and deleting solves the problem by removing the offending copy. Doing this has no effect on the structure of the edit.

xberk wrote on 1/29/2017, 3:24 PM

I think you have the answer Jack. Vegas allows an event to be placed on top of another event.  This has always been a part of Vegas to my knowledge. The transition doesn’t work because the take underneath is being revealed. 

If you have two identical events on top and one beneath, a fade will reveal the one underneath.  If the one underneath is identical, it looks like nothing happened.   

How can this happen?  The only way I can reproduce this is by doing it on purpose.  Maybe is has to do with Ctrl drag which will copy an event.  Are you dragging the copy, changing your mind and placing it back where you started?   That’s two events one on top of each other.

I cannot reproduce the deletion of both events (one on top, one under) at the same time.

Paul B .. PCI Express Video Card: EVGA VCX 10G-P5-3885-KL GeForce RTX 3080 XC3 ULTRA ,,  Intel Core i9-11900K Desktop Processor ,,  MSI Z590-A PRO Desktop Motherboard LGA-1200 ,, 64GB (2X32GB) XPG GAMMIX D45 DDR4 3200MHz 288-Pin SDRAM PC4-25600 Memory .. Seasonic Power Supply SSR-1000FX Focus Plus 1000W ,, Arctic Liquid Freezer II – 360MM .. Fractal Design case ,, Samsung Solid State Drive MZ-V8P1T0B/AM 980 PRO 1TB PCI Express 4 NVMe M.2 ,, Wundiws 10 .. Vegas Pro 19 Edit

JackW wrote on 1/29/2017, 4:37 PM

It has happened to me in both Sony Vegas 8 (some time ago) and 13, which I use daily. Now that I think of it I believe xberk has the answer: the accidental Ctrl drag on the event itself, rather than Ctrl drag on the event edge to create slo-motion.