VP17b321 bug: Media FX don't show FX's controls in preview window

Comments

Sylk wrote on 9/28/2019, 9:47 PM

No bug for me.

Software:
[OS]  : Windows 10 Ent. x64 v1903 (18362.535)
[NLE] : Vegas Pro 17.0 (Build 321) // (Build 284 if posted before 9/24/19)
[DRV] : Studio 536.23 (Display, PhysX, HD Audio) // (Game Ready 436.15 if posted before 9/24/19)
Hardware:
[GPU] : Gainward RTX 4090 Phantom / GTX 1080 Phoenix GLH
[CPU] : Intel Core i7-2600K @3.4GHz OC@4.5GHz (HyperThreaded) | AirCooling: Noctua NH-D14
[RAM] : 16GB (4x 4GB GSkill Ripjaws X DDR3 1600MHz 9-9-9-24) @1333MHz
[SSD] : Samsung 860 Pro 1TB
[MOB] : Asus P8P67 Deluxe (Rev.1), No iGPU support
[SND] : Asus Xonar Essence STX
[PSU] : Corsair HX750
Devices:
[DSP1]: 30" DELL UltraSharp U3011 @2560x1600
[DSP2]: 28" Samsung U28D590 @3840x2160

[UPS] : Eaton 5PX 2200i RT

[CAM] : GoPro Hero8/4/3 Black. Apple iPhone 11Pro/6S.
[REC] : Zoom Handy Recorder H4.
Sylk wrote on 9/28/2019, 11:37 PM

Ok same. Occurs from MediaFX only. TrackFX and EventFX are ok.

Software:
[OS]  : Windows 10 Ent. x64 v1903 (18362.535)
[NLE] : Vegas Pro 17.0 (Build 321) // (Build 284 if posted before 9/24/19)
[DRV] : Studio 536.23 (Display, PhysX, HD Audio) // (Game Ready 436.15 if posted before 9/24/19)
Hardware:
[GPU] : Gainward RTX 4090 Phantom / GTX 1080 Phoenix GLH
[CPU] : Intel Core i7-2600K @3.4GHz OC@4.5GHz (HyperThreaded) | AirCooling: Noctua NH-D14
[RAM] : 16GB (4x 4GB GSkill Ripjaws X DDR3 1600MHz 9-9-9-24) @1333MHz
[SSD] : Samsung 860 Pro 1TB
[MOB] : Asus P8P67 Deluxe (Rev.1), No iGPU support
[SND] : Asus Xonar Essence STX
[PSU] : Corsair HX750
Devices:
[DSP1]: 30" DELL UltraSharp U3011 @2560x1600
[DSP2]: 28" Samsung U28D590 @3840x2160

[UPS] : Eaton 5PX 2200i RT

[CAM] : GoPro Hero8/4/3 Black. Apple iPhone 11Pro/6S.
[REC] : Zoom Handy Recorder H4.
Former user wrote on 9/29/2019, 1:29 AM

Confirmed. I also have this bug here.

matthias-krutz wrote on 9/29/2019, 2:43 AM

It's not a bug for me, it's like Vegas works. The preview window does not automatically sync to the keyframes of the Media FX. If I need it, I used HOS to find the keyframe positions in preview and then apply it to the Media FX. I do it so in the video stabilization, if I use it at the media level.

Desktop: Ryzen R7 2700, RAM 32 GB, X470 Aorus Ultra Gaming, Radeon RX 5700 8GB, Win10 2004

Laptop: T420, W10, i5-2520M 4GB, SSD, HD Graphics 3000

VEGAS Pro 14-18, Movie Studio 12 Platinum, Vegasaur, HOS, HitfilmPro

fr0sty wrote on 9/29/2019, 8:18 AM

Just a guess, but it could be because media effects are able to be applied to the clip while still in the project media pool, before it is on the timeline and therefore before where it is or if it is on the timeline is considered. That may be why it does not allow for auto-sync to where it is on the timeline. Event level and beyond effects must be on the timeline to be applied, so syncing it to a position on the timeline doesn't cause a conflict when it doesn't find a timeline to sync it to.

Last changed by fr0sty on 9/29/2019, 8:19 AM, changed a total of 1 times.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

Former user wrote on 9/30/2019, 5:52 PM

For information only, a temporary workaround until this bug is fixed: You can see the FX's controls in preview window by clicking on an empty area of the timeline.

NickHope wrote on 12/26/2019, 1:13 AM

This issue dates back at least to VP12. I tested with the Cookie Cutter FX etc..

I believe the VEGAS team use the term "video preview interacts" for these on-screen controls.

I see no fundamental reason that the video preview interacts should not display for media FX. As demonstrated above, they display for media FX when the cursor is over an empty area of the timeline, so why not when it is over the event?

I added it to the Known Issues post.

joelsonforte.br wrote on 2/23/2020, 11:11 PM

@NickHope

This bug no longer occurs in Vegas Pro 17 Build 421.

NickHope wrote on 2/27/2020, 2:54 AM

@joelsonforte.br Thanks. Verified it here. I've removed it from the Known Issues post. It appears in the release notes as "Overlays will now show up properly for Media effects".