Hi Roger thanks for your reply. I've uploaded the clip. If you can let me know how you go that would be much appreciated.

To add to that, the program is freezing on playback. And I need to use task manager to shut it down, and it's indicating "very high" power usage. Whatever that means. I've never had this issue, completely at a loss right now.

@gmtmtfilms I can't even play your file with VP19 532, It crashes with default settings. It will work with Legacy AVC decoder, or by changing the hardware decoding setting in FILE IO to OFF, so try that with build 636

@Former user thank you for checking it out. By switching the hardware decoding to OFF as you suggested I was able to create the video proxy (it also played back without crashing) so now I have enabled the hardware decoding again and it appears I no longer have that problem. Thank you very much. Fingers crossed!

@gmtmtfilms @Former user @RogerS 

Hi, just for the sake of sharing, the only way i could get that file to play without crashing Vegas was with File I/O Decoder OFF. It didn't seem to make a difference Legacy AVC on or off, it did also need to play through once before it ran smoothly at full fps.

PS, just to piss off those who hate it being mentioned, that file plays absolutely no problem, very smoothly first go around in MEP Premium, Vegas Effects & Hitfilm Pro 😛 I didn't try it in Resolve but that plays pretty much any file i've thrown at it so far.

& in Boris's Mocha Pro standalone & in Silhouette standalone,

@Former user Looks like a fairly basic file . Short GOP (14) which Vegas likes. Maybe it's the leading quadruple B frames that it doesn't like. Vegas does great without B frames, even HEVC 4K without B frames, but B frames is a standard reality

@Former user

I'm not seeing four leading B-frames. I see two before the first IDR.

@john_dennis I think ffprobe is agreeing with you. Need a more dependable free GUI app that shows the order of GOP frames correctly. Is this actually the problem then, the way this file was cut by OP? It should start with an I frame, and Vegas doesn't like it?

@Former user

"Need a more dependable free GUI app that shows the order of GOP frames correctly."

VideoReDo TV Suite is perfect for this task. I find it well worth the upgrade price since I've owned versions 2-6. It's not free. I just asked the developer to consider moving the IPB indicator closer to the frame counter.

I'm uncertain about leading B-frames. I can look though my camera files to see if any of them ever start on anything but an I-frame.

@Former user

I did a quick survey of the files from my Sony RX10-IV. All the files I sampled started with the pattern B-B-IDR.

Hi Roger thanks for your reply. I've uploaded the clip. If you can let me know how you go that would be much appreciated.

I was able to open and play the file with 19.636 just fine. I right-clicked and created a video proxy without problem and it works fine for playback (preview/full). In case it makes a difference I am using an Intel iGPU for decoding (see signature). I have the regular decoders in use for AVC (legacy off and hardware set to auto/Intel).

Here's MediaInfo for the file:

General
Complete name                  : PROXY FAIL01.mp4
Format                         : XAVC
Codec ID                       : XAVC (XAVC/mp42/iso2)
File size                      : 108 MiB
Duration                       : 14 s 200 ms
Overall bit rate mode          : Variable
Overall bit rate               : 63.7 Mb/s
Encoded date                   : UTC 2022-06-06 23:28:18
Tagged date                    : UTC 2022-06-06 23:28:18

Video
ID                             : 1
Format                         : AVC
Format/Info                    : Advanced Video Codec
Format profile                 : High@L5.1
Format settings                : CABAC / 2 Ref Frames
Format settings, CABAC         : Yes
Format settings, Reference fra : 2 frames
Format settings, GOP           : M=3, N=12
Codec ID                       : avc1
Codec ID/Info                  : Advanced Video Coding
Duration                       : 14 s 200 ms
Bit rate mode                  : Variable
Bit rate                       : 62.2 Mb/s
Maximum bit rate               : 100.0 Mb/s
Width                          : 3 840 pixels
Height                         : 2 160 pixels
Display aspect ratio           : 16:9
Frame rate mode                : Constant
Frame rate                     : 25.000 FPS
Standard                       : Component
Color space                    : YUV
Chroma subsampling             : 4:2:0
Bit depth                      : 8 bits
Scan type                      : Progressive
Bits/(Pixel*Frame)             : 0.300
Stream size                    : 105 MiB (98%)
Language                       : English
Encoded date                   : UTC 2022-06-06 23:28:18
Tagged date                    : UTC 2022-06-06 23:28:18
Color range                    : Limited
Color primaries                : BT.709
Transfer characteristics       : BT.709
Matrix coefficients            : BT.709
Codec configuration box        : avcC

Audio
ID                             : 2
Format                         : PCM
Format settings                : Big / Signed
Codec ID                       : twos
Duration                       : 14 s 200 ms
Bit rate mode                  : Constant
Bit rate                       : 1 536 kb/s
Channel(s)                     : 2 channels
Sampling rate                  : 48.0 kHz
Bit depth                      : 16 bits
Stream size                    : 2.60 MiB (2%)
Language                       : English
Encoded date                   : UTC 2022-06-06 23:28:18
Tagged date                    : UTC 2022-06-06 23:28:18

@Former user

I did a quick survey of the files from my Sony RX10-IV. All the files I sampled started with the pattern B-B-IDR.

@john_dennis Apparently it's normal

@RogerS So another broken Vegas GPU decoder problem with any GPU but Intel. I'm used to seeing the green flashes

Yes Todd, that's what it seems like.

Is @gmtmtfilms using the NVIDIA decoder? If so, highly recommend getting the Intel UHD Graphics 630 to work instead within Vegas for decoding.

Morning guys, thank you for the insight. This tech is beyond my skill level! I appreciate your input very much.

I've talked to my second who rough cuts my footage, and he said that particular piece of footage was stabilised using Sony Catalyst. This software is amazing at using the gyro stabilisation data that the Sony a7s3 contains. Even though the file output was matched to the original media. So, I'm wondering if that has made a difference? It's worth noting this is new to my workflow but used sparingly over the past few edits.

If you have time then maybe you could test this original footage in the link, shot on the same camera, settings etc.. and see if it makes a difference to your readings? I'd be extremely grateful as the Catalyst render might be what's causing the software to freeze.

https://u.pcloud.link/publink/show?code=XZY47RVZYyaIYQFzmzkjQiJwhRUS0b8c8Aok

Also, this project was started using the previous VP build, would that cause problems since I migrated to the latest build? I've overwritten the project to the latest build.

@RogerS to answer your question, yes, I'm using my RTX3070 as my hardware decoder. I've used that for more than a year now without any problem, it's only since the update I'm having the problem. But it may be due to using the Sony Catalyst software to stabilize the clip.

Thanks again guys.

Generally speaking you're better off with the Intel decoder if you can use it as it works with more types of media. I doubt this new version changed decoding based on the release notes.

I didn't have issues playing back or creating a proxy file for this clip either. Added color grading to the track and faded between two of the same event and no issues.

Here's the MediaInfo though you might need a more sophisticated analyses like what Todd and John have done above to really see what is different.

General
Complete name                  : 5.FILMSHOOT (8).MP4
Format                         : XAVC
Codec ID                       : XAVC (XAVC/mp42/iso2)
File size                      : 96.1 MiB
Duration                       : 6 s 240 ms
Overall bit rate mode          : Variable
Overall bit rate               : 129 Mb/s
Encoded date                   : UTC 2022-01-19 05:55:12
Tagged date                    : UTC 2022-01-19 05:55:12

Video
ID                             : 1
Format                         : AVC
Format/Info                    : Advanced Video Codec
Format profile                 : High@L5.1
Format settings                : CABAC / 2 Ref Frames
Format settings, CABAC         : Yes
Format settings, Reference fra : 2 frames
Codec ID                       : avc1
Codec ID/Info                  : Advanced Video Coding
Duration                       : 6 s 240 ms
Bit rate mode                  : Variable
Bit rate                       : 100.0 Mb/s
Width                          : 3 840 pixels
Height                         : 2 160 pixels
Display aspect ratio           : 16:9
Frame rate mode                : Constant
Frame rate                     : 25.000 FPS
Color space                    : YUV
Chroma subsampling             : 4:2:0
Bit depth                      : 8 bits
Scan type                      : Progressive
Bits/(Pixel*Frame)             : 0.482
Stream size                    : 74.3 MiB (77%)
Encoded date                   : UTC 2022-01-19 05:55:12
Tagged date                    : UTC 2022-01-19 05:55:12
Color range                    : Limited
Color primaries                : BT.709
Transfer characteristics       : BT.709
Matrix coefficients            : BT.709
Metas                          : 3
Codec configuration box        : avcC

Audio
ID                             : 2
Format                         : PCM
Format settings                : Big / Signed
Codec ID                       : twos
Duration                       : 6 s 240 ms
Bit rate mode                  : Constant
Bit rate                       : 1 536 kb/s
Channel(s)                     : 2 channels
Sampling rate                  : 48.0 kHz
Bit depth                      : 16 bits
Stream size                    : 1.14 MiB (1%)
Encoded date                   : UTC 2022-01-19 05:55:12
Tagged date                    : UTC 2022-01-19 05:55:12

@gmtmtfilms

My Results with Vegas Pro 19-636

Dell 5770 Laptop

i7-6850K-Radeon RX480-8GB

My computer specs in my signature below. I just tried the clip with AMD RX480 enabled. Crash. Disabled, the clip plays back flawlessly.

@john_dennis I just retried it with the RX480 enabled in the Video tab, but for the File I/O, instead of

(auto) UVD/VCN on Radeon RX480, I just selected UVC/VCN on Radeon RX480 from the Hardware Decoder To Use menu. The file now plays back fine.

@Reyfox @gmtmtfilms

I updated my video driver for the RX480 using the Pro driver to no avail. I selected the UVC/VCN on Radeon RX480 from the Hardware Decoder as you did, but got no satisfaction.

Here's what does give me a lot of satisfaction, using Shutter Encoder to convert the "problem files" to Apple ProRes LT (use 4444 XQ if you're really paranoid and have lots of disk space). It runs as smooth at 25 FPS at Best / Full on my five year old machine.

If I had to get something out the door, I'd stop shooting Vegas/hardware/media/driver/phase of the moon bugs and move on with my life. Some video formats exist to let cameras cram ten pounds of stuff on to an SD card and some video formats exist to make non-linear editors work smoothly. Pick one for each task.

Some video formats exist to let cameras cram ten pounds of stuff on to an SD card and some video formats exist to make non-linear editors work smoothly. Pick one for each task.

@john_dennis While true, Canon R5/R6 as examples of camera files that many NLE's don't like, but think about this, The default Magix decoder that is able to use GPU decoding works worse then the Sony decoder that is over a decade ago with many file types. It's why you always get people complaining about upgrading from say VP11 or 12 to VP19, and get worse playback. It's hard to make sense of this, so people will always complain looking for fixes.

I made this example, playing back 5 different x264 AVC variants, comparing Magix(new) to Sony(Legacy) decoder. It is sped up 1.5x as overly long, so frame dropping durations are actually worse then seen here.

I uninstalled update 636 for the 4th time today. Once again freezing during rendering. It froze at 9%, 33% and 75+%. I finally got it to render by using an Intel rendering option instead of the NVEC. However, regardless I'm was also having editing playback issues where the playback appears to be dropping frames making playback choppy. I didn't have this issue with update 550. I'm only editing 1080p GoPro footage so the GPU/CPU should easily handle that.

I have the File I/O decoder set to 'none'

I using a GTX 1070 GPU and Windows 11. My signature has other information.

@Hamilton53 how can I go back to 550? I've been unable to find that version ( I don't save the releases ) Is there somewhere I can download it? I have used legit software since VP8.