Paste Event Attributes bug - VP13 & VP12 - Fixed in VP14

NickHope wrote on 11/3/2014, 1:40 AM

I am getting a serious bug with "paste event attributes" in VP13 and VP12.

In VP10 and earlier, "paste event attiributes" used to "stack" video event FX on top of the existing FX on the target event. I liked that because I could go into the target event after pasting and selectively delete or edit earlier FX in the chain.

Now in VP12 and VP13, the existing FX on the target event are deleted by the pasting. I preferred the earlier behaviour, and I bet the new behaviour was never planned and intended but slipped through a rewrite of the code.

However, more seriously, I'm getting crashes because the video event FX dialog for the target event does not update automatically after the paste. Most of my testing is with GPU acceleration off, but it also happens with GPU acceleration on.

Here's an example scenario. Please test and reproduce if you can:

1. Put a gray solid color generated media on the timeline
2. Put a 2nd gray solid color generated media on the timeline next to it
3. Put a Color Curves FX on the first event and choose the Warm Colors preset
4. Put a Color Curves FX on the 2nd event and choose the Cool Colors preset
5. Keep the Video Event FX dialog for the 2nd event open
6. Copy the 1st event to clipboard
7. Paste event attributes onto the 2nd event
8. The video preview changes to warm colors, but the Video Event FX dialog wrongly still shows the Cool Colors preset
9. Try to edit the Video Event FX and it crashes

Here's another example:

1. Put a gray solid color generated media on the timeline
2. Put a 2nd gray solid color generated media on the timeline next to it
3. Put a Color Balance FX on the first event and choose the Red Midtones preset
4. Put a Color Balance FX on the 2nd event with no preset
5. Keep the Video Event FX dialog for the 2nd event open
6. Copy the 1st event to clipboard
7. Place the cursor over the 2nd event
8. Paste event attributes onto the 2nd event
9. The video preview changes to red midtones, but the Video Event FX dialog wrongly still shows no preset
10. Move the FX sliders around. It has no effect.
11. Drag the timeline cursor and it crashes

Comments

Arthur.S wrote on 11/3/2014, 4:25 AM
Both options are poo really Nick. An option for what you want to paste (like other NLE software from 10 years ago) would be nice. If Vegasaur can 'partly' do this with cropping, why can't Sony do it? We've all been calling for it for a loooooong time.
NickHope wrote on 11/5/2014, 5:14 AM
Anyone care to try and reproduce this in case it's something specific to my computer? Would only take a few minutes.
Grazie wrote on 11/5/2014, 5:18 AM
I'm running WIN7 not 8. Whould that assist? Or confuse the results?

G

NickHope wrote on 11/5/2014, 5:21 AM
That would certainly assist Grazie. I very much doubt it's dependent on the O/S.
Marco. wrote on 11/5/2014, 5:22 AM
I followed step 1 to 9 of your first example and this way I can always repro the crash you mentioned.
Grazie wrote on 11/5/2014, 5:23 AM
On the case. Give me an hour, I'm running a paid project presently, but I'll go OFF-THE-CLOCK while attempting this.

Grazie



redpaw wrote on 11/5/2014, 5:26 AM
yeap, crashes for me in both instances as well.

v13 b373. win 8.1
Grazie wrote on 11/5/2014, 5:47 AM
Nick, seems like you've got enough feedback now? I'll stand down.

Grazie

diverG wrote on 11/6/2014, 10:31 AM
Not crashing here but would with agree with step 8 in that Fx dialog wrongly
shows color preset as cool.

Can toggle cool to warm within the dialog to match the effect/preview, toggling back
to cool changes to 'cool' in preview.

Geoff

Sys 1 Gig Z370-HD3, i7 8086K @ 5.0 Ghz 16gb ram, 250gb SSD, 2x2Tb hd,  GTX 4060 8Gb, BMIP4k video out. (PS 750W); Vegas 18 & 19 plus Edius 8WG DVResolve18 Studio. Win 10 Pro (22H2) Bld 19045.2311

Sys 2 Gig Z170-HD3, i7 6700K @ 3.8Ghz 16gb ram, 250gb SSD, 2x2Tb, hdd GTX 1060 6Gb, BMIP4k video out. (PS 650W) Vegas 18 plus Edius 8WG DVResolve18 Studio Win 10 Pro (22H2) Bld 19045.2311

Sys 3 Laptop 'Clevo' i7 6700K @ 3.0ghz, 16gb ram, 250gb SSd + 2Tb hdd,   nvidia 940 M graphics. VP17, Plus Edius 8WG Win 10 Pro (20H2) Resolve18

 

OldSmoke wrote on 11/6/2014, 10:33 AM
driverG

Try and make changes to the curve; that is when it crashes.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

kairosmatt wrote on 11/7/2014, 8:36 AM
Unless I missed something (quite possible) neither one crashes my laptop

(Win7, Lenevo T420s with itinel i7, 16 gigs ram)

(vegas 13.0 build 373)

In the first case the FX box does show the wrong preset.

In the Second case after pasting the preset sliders are in the wrong default position. However, when I get to step 10 (move the sliders) the preset display fixes itself, and the sliders all effect the images. Nothing crashing here (from this anyways).

kairosmatt
KelvinWorks wrote on 11/7/2014, 8:54 AM
Last week using VP13, I was doing a bunch of color correcting for an hour long program and having crashes one after another until I realized that it had something to do with when I left the FX dialog box open. Now I see it is not just my system.

I however do like how that it deletes the old FX's vs. stacking the new on top of the old with the pasting event FX. Never liked having to go in and delete the old manually every time when I was pasting over many events.
NickHope wrote on 11/7/2014, 12:22 PM
I got a reply from SCS including this:

"...This is a known issue by our development team and is being considered for a fix in a future update..."
dxdy wrote on 11/7/2014, 2:10 PM
"...being considered..." ?

Their PR team could phrase this in a less callous manner...I guess relative to GPU issues, it is a minor matter. Hmmm......
NickHope wrote on 11/26/2014, 12:08 AM
VP13 build 428 still has this problem.
NickHope wrote on 4/7/2015, 2:20 AM
VP13 build 444 still has this problem.
NickHope wrote on 9/20/2016, 2:53 AM

This bug is fixed in VEGAS Pro 14.0 (Build 161). Thanks!