Copy > Paste Velocity Keyframes vanishing

AVsupport wrote on 11/14/2018, 11:46 PM

It seems that the 'Copy / Paste Event Attributes' fails to remember the exact position of the Velocity Keyframes in the pasted clip. I think I can see them 'squshed up' at the start of the clip...

Anyone else notice this? [VP16.307]

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

16GB (2x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

Comments

klt wrote on 11/15/2018, 12:19 AM

Confirmed... The same here.

Also with V15 387.

Last changed by klt on 11/15/2018, 12:22 AM, changed a total of 1 times.

Camera: JVC GY-HM600

Desktop: AMD Ryzen 5 1600, 16GB RAM (dual channel 2400 MHz) - Videocard: Radeon R9 380 2GB

Laptop: i5 5200u, 8GB RAM (1600MHz single channel) Videocard: integrated HD5500

AVsupport wrote on 11/15/2018, 12:22 AM

@NickHope is this a known issue?

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

16GB (2x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

AVsupport wrote on 11/15/2018, 1:50 AM

this might work once once rebooted etc, but not repeatedly, in the long run..just sayin'..

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

16GB (2x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

NickHope wrote on 11/15/2018, 6:02 AM

@NickHope is this a known issue?

No, and a very brief test here has it working OK for me. Can you come up with a repeatable process to demonstrate, or even a demo project?

klt wrote on 11/15/2018, 6:50 AM

Seems, that the original has to be out of view somehow. On different track, far away in time.

Then pasting attributes with velocity envelope fails. However, touching event trim, heals it instantly...

Looking at it a bit closer it seems, that the velocity is working, just the envelope is not displayed correctly.

Last changed by klt on 11/15/2018, 6:55 AM, changed a total of 1 times.

Camera: JVC GY-HM600

Desktop: AMD Ryzen 5 1600, 16GB RAM (dual channel 2400 MHz) - Videocard: Radeon R9 380 2GB

Laptop: i5 5200u, 8GB RAM (1600MHz single channel) Videocard: integrated HD5500

AVsupport wrote on 11/15/2018, 4:29 PM

@klt In my scenario it also happens when I copy>paste to the adjacent clip. And Yes, as you say, it is only the envelope that's not displayed properly, which can be 'healed' by trim the header forward/backward a frame!!

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

16GB (2x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

NickHope wrote on 11/15/2018, 9:00 PM

I still can't make this happen.

klt wrote on 11/16/2018, 1:18 AM

Seems I could reproduce. The event you paste the attributes to has to be untouched since you opened the project. So my steps to reproduce:

-start a new project.

-add 2 events to timeline

-edit one event, so that it will have event velocity

-save the project, close Vegas

-now start Vegas again, open that project

-copy the edited event

-paste attributes to the other event: for me the velocity envelope is garbled now.

IF I trim the event (end or start) BEFORE I paste attributes, the velocity will show up correctly at first.

IF I do the trim AFTER pasting the attributes, the messed envelope will be healed.

Because of my curiosity, I tried to save the project with the messed (still working) pasted velocity.

Whenever I open this project, the envelope still shows up badly. I have to make a trim to make it look right...

Last changed by klt on 11/16/2018, 1:19 AM, changed a total of 2 times.

Camera: JVC GY-HM600

Desktop: AMD Ryzen 5 1600, 16GB RAM (dual channel 2400 MHz) - Videocard: Radeon R9 380 2GB

Laptop: i5 5200u, 8GB RAM (1600MHz single channel) Videocard: integrated HD5500

NickHope wrote on 11/16/2018, 8:36 PM

Thank you kit. I've reproduced this now and it goes right back to VP10 (the oldest version on my machine).

If Paste Event Attributes or Selectively Paste Event Attributes is used to paste a velocity envelope onto an event that existed on the timeline before the last time a project was opened, any keyframes in the pasted envelope all appear to be on the first frame. They cannot be dragged to the right and new keyframes cannot be added. However the keyframes affect the event's velocity correctly, and are displayed correctly if the event's length is subsequently adjusted.

I bet this old comment from 2010 refers to exactly the same bug.

I reported with a support request [Ticket#2018111717000624].

AVsupport wrote on 11/16/2018, 8:44 PM

Thank you @klt thank you @NickHope excellent bug smashing ;-)

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

16GB (2x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

NickHope wrote on 11/19/2018, 8:53 PM

I had a reply from Support that the issue has been reported and "PEFed" ("PEF" means escalating the issue to the development and QA team).

Edit: Still not fixed in VP17 build 421.