Preview Video Playback doesn't work (and failed video proxy creation!)

alberto-p wrote on 1/3/2019, 4:14 AM

Hello everyone,
i've been using Vegas 16 till a few hours ago, when all of a sudden I could not see any video clip running in the video preview anymore.
The audio goes on but no video is shown, and even on the timeline the clip is blank.
Also, when i try to create a video proxy i get an error message (see screenshot attached).
I've tried unistalling, rebooting, cleaning temporary files and registry, reinstalling still nothing changed, no matter the video type/format I use.
I can only see the clips being played on preview (and their thumbnail on the timeline) when I'm working on a previous project in which I had already created video proxies before this problem showed up.
Other than that, complete blackout.
Video drivers are up to date.
Anyone has a clue of what is happening? 
thank you very much!

Alberto

 

Comments

john_dennis wrote on 1/3/2019, 3:16 PM

https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/

alberto-p wrote on 1/4/2019, 8:54 AM

Further informations:
Vegas pro 16 Build 248
Win 10.0 64 bit
Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
NVIDIA GEForce gtx 1050 driver 25.21.14.1735
GPU acceleration on Vegas either on/off doesn't change the result.
As mentioned in my first post, no matter what footage i'm using, or what kind of project i'm working on. It's always happening for 3 days now.

The only clips that i can preview are those from the project in which I had already created the video proxy (still event thumbnails on the timeline are blank though).

j-v wrote on 1/4/2019, 9:03 AM

Try first the latest build of VPro 16 you will find in your Magix account

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver 566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

alberto-p wrote on 1/5/2019, 6:18 AM

Thank you j-v fr your message.
I tried updating to the 352 build and rolling back to a previous gpu driver but still got the problem...
Anybody has other suggestions?

3POINT wrote on 1/5/2019, 7:35 AM

Creating proxies from 720p30 footage makes no sense ( proxies will be 1080p24). Also trying to create proxies from footage that's not being recognized by Vegas makes no sense and gives probably the unrecognized error message. What is the source of your footage?

Marco. wrote on 1/5/2019, 7:43 AM

Vegas internal proxies are 1280x720 with no frame rate meta data used but frame rate automatically adopted to the source media. It makes sense using them if the source media is encoded in a way Vegas Pro would need much resources to decode.

3POINT wrote on 1/5/2019, 8:28 AM

Vegas internal proxies are 1280x720 with no frame rate meta data used but frame rate automatically adopted to the source media.

Marco, you're right. Proxies are 720p (XDCAM mpeg2), but my experience is that they are always 24p, nevertheless the framerate of the source media. Proxies are only shown when previewmode is draft or preview. The original media is always shown in previewmode good or best.

alberto-p wrote on 1/5/2019, 9:21 AM

The point is not the proxy, this is just another thing that is not working at the moment when it comes to deal with heavy footage. As I explained, the problem is the videos don't play in the preview but just the audio.

3POINT wrote on 1/5/2019, 10:08 AM

Therefore I asked, what is the source of your media files?

alberto-p wrote on 1/5/2019, 10:10 AM

Any source, from GoPro to Nikon to Sony mirrorless to mobile phone's mp4 etc etc

3POINT wrote on 1/5/2019, 10:40 AM

When it has worked before and the problem suddenly appeared, maybe a reinstallation could help.

3POINT wrote on 1/5/2019, 10:44 AM

Also it looks strange to me that in your screenshot a thumbnail of VLC player is shown and not a thumbnail of the first frame of the media.

alberto-p wrote on 1/5/2019, 10:48 AM

I've already written all these things in my first post: I've already done multiple clean uninstallings. The thumbnails are blank because there is a problem recognizing the footage and that's also why creating video proxys fails

vkmast wrote on 1/5/2019, 11:24 AM

If VEGAS Pro has worked before but now is behaving strangely, it is often recommended to try resetting it to default settings. Your first post does imply that you may have tried that as well, but if not, please try.

alberto-p wrote on 1/5/2019, 11:43 AM

Thank you for your suggestion, yes I've done it already.

3POINT wrote on 1/5/2019, 11:50 AM

Did you maybe install a 3rd party codec pack?

Marco. wrote on 1/5/2019, 12:02 PM

"[...] my experience is that they are always 24p"

Don't want to protract that off topic but this is something which is misunderstood very often.

Definitely, Vegas Pro internal proxy workflow does not use the fps meta data of the proxy file itself but reads the source meta data to get the correct (source) fps. You could use 120 fps source video or you could use 2 fps source video. When using the proxy workflow 120 fps will still be 120 fps and 2 fps will still be 2 fps. No frames doubled, no frames skipped.

The confusion once arose when people checked the meta data of the SFVP0 proxy files which isn't valid for the use of meta data.

3POINT wrote on 1/5/2019, 12:26 PM

Also Vegas interprets the Proxy as being 720p24 when re-imported into the media folder. But I don't want to start a discussion about this here, because I also assume that your knowledge about Vegas is larger than mine.

Marco. wrote on 1/5/2019, 1:23 PM

That's what I mean: You cannot and should not use the SFVP0 file itself. It's totally misleading. Vegas proxies should be used solely within the given proxy workflow (by switching the preview settings while touching the source files only in the project). Any use of separated SFVP0 files breaks the proxy functionality because the wrong use of meta data.

The equitation is not:
Proxy = SFVP0 file

The equitation is:
Proxy = source file's audio stream + SFVP0 file's video stream + source file's frame rate meta data

3POINT wrote on 1/5/2019, 2:40 PM

Marco, thanks for this detailed explanation about proxies.

mark003 wrote on 2/4/2019, 4:12 PM

alberto-p, did you ever solve this? I'm having the same issue with 4K .mov files.

alberto-p wrote on 2/5/2019, 12:55 AM

Hello Mark, I made it to solve it by adopting this changes I was suggested on CreativeCow.net:
Clean unistall of Vegas;
I rolled back to a previous version on Vegas and to a previos version of gpu driver;
I disabled the so4compoundplug;