Could you share MediaInfo for the main media you use? https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

If you have a sample file you could share via Google Drive, etc. users with similar systems could test it.

The legacy decoder will eventually go away; if you'd like to use the new decoder and not disable your GPU it would bw great to get more info about the media so team VEGAS can fix this problem.

The legacy decoder will eventually go away; if you'd like to use the new decoder and not disable your GPU it would bw great to get more info about the media so team VEGAS can fix this problem.

Sure! Here is the link with some clips where I've encountered issues. I only work with Fuji cameras, and this problem happens with all the clips I've mentioned. I've included some 4K clips and others in FHD.

Link: https://smile-art-studio.filemail.com/d/cmirnecsvtqvksa

There are also some clips that Vegas Pro 22 simply doesn't read; when dragging them to the timeline, I only get audio.

Link: https://smile-art-studio.filemail.com/d/jgcxenyxzxwvgke

I hope the developers can resolve this.

I don't have any excess memory problems with just playing the clips, and I don't see the problem with some clips only loading audio without the video. I am using Nvidia GPU, this may be an AMD GPU problem.

"There are also some clips that Vegas Pro 22 simply doesn't read; when dragging them to the timeline, I only get audio.

Link: https://smile-art-studio.filemail.com/d/jgcxenyxzxwvgke"

I have no problem with these clips in V22 (194) I get video and sound. They play perfectly on the timeline.

I don't have any excess memory problems with just playing the clips, and I don't see the problem with some clips only loading audio without the video. I am using Nvidia GPU, this may be an AMD GPU problem.

It's really very strange. I don't understand why these bugs are happening then.

I was only able to get everything working with the settings I mentioned above. I don’t understand.

Thank you very much for the feedback.

"There are also some clips that Vegas Pro 22 simply doesn't read; when dragging them to the timeline, I only get audio.

Link: https://smile-art-studio.filemail.com/d/jgcxenyxzxwvgke"

I have no problem with these clips in V22 (194) I get video and sound. They play perfectly on the timeline.

Thank you for the feedback. I'll wait then for some feedback from AMD users. I also had this issue with Vegas Pro 21.

I can only play the file smoothly with the Vegas settings I mentioned above.

Thanks.

For the second set of clips I had no issue opening and playing them in VP 22 on my laptop (RTX 4060 doing decoding).

They seem to be 8-bit AVC from an XT-4:

General
Complete name                  : Filemail.com files 11_5_2024 jgcxenyxzxwvgke\1PNM2253.MP4
Format                         : MPEG-4
Format profile                 : Base Media / Version 2
Codec ID                       : mp42 (mp42)
File size                      : 46.6 MiB
Duration                       : 3 s 0 ms
Overall bit rate mode          : Variable
Overall bit rate               : 130 Mb/s
Frame rate                     : 50.000 FPS
Movie_More                     : FUJIFILM DIGITAL CAMERA X-T4
Encoded date                   : 2024-06-09 17:10:03 UTC
Tagged date                    : 2024-06-09 17:10:03 UTC
Origin                         : Digital Camera

Video
ID                             : 1
Format                         : AVC
Format/Info                    : Advanced Video Codec
Format profile                 : High@L5
Format settings                : CABAC / 1 Ref Frames
Format settings, CABAC         : Yes
Format settings, Reference fra : 1 frame
Format settings, GOP           : M=1, N=25
Codec ID                       : avc1
Codec ID/Info                  : Advanced Video Coding
Duration                       : 3 s 0 ms
Bit rate                       : 105 Mb/s
Width                          : 1 920 pixels
Height                         : 1 080 pixels
Display aspect ratio           : 16:9
Frame rate mode                : Constant
Frame rate                     : 50.000 FPS
Color space                    : YUV
Chroma subsampling             : 4:2:0
Bit depth                      : 8 bits
Scan type                      : Progressive
Bits/(Pixel*Frame)             : 1.011
Stream size                    : 37.5 MiB (80%)
Language                       : English
Encoded date                   : 2024-06-09 17:10:03 UTC
Tagged date                    : 2024-06-09 17:10:03 UTC
Color range                    : Full
Color primaries                : BT.709
Transfer characteristics       : BT.601
Matrix coefficients            : BT.601
Codec configuration box        : avcC

Audio
ID                             : 2
Format                         : AAC LC
Format/Info                    : Advanced Audio Codec Low Complexity
Codec ID                       : mp4a-40-2
Duration                       : 3 s 0 ms
Source duration                : 3 s 8 ms
Bit rate mode                  : Variable
Bit rate                       : 128 kb/s
Maximum bit rate               : 192 kb/s
Channel(s)                     : 2 channels
Channel layout                 : L R
Sampling rate                  : 48.0 kHz
Frame rate                     : 46.875 FPS (1024 SPF)
Compression mode               : Lossy
Stream size                    : 47.1 KiB (0%)
Source stream size             : 47.1 KiB (0%)
Language                       : English
Encoded date                   : 2024-06-09 17:10:03 UTC
Tagged date                    : 2024-06-09 17:10:03 UTC
mdhd_Duration                  : 3000

Other
ID                             : 3
Type                           : Time code
Format                         : QuickTime TC
Duration                       : 3 s 0 ms
Bit rate mode                  : Constant
Frame rate                     : 50.000 FPS
Time code of first frame       : 00:22:57:08
Time code of last frame        : 00:23:00:07
Time code, stripped            : No
Language                       : English
Encoded date                   : 2024-06-09 17:10:03 UTC
Tagged date                    : 2024-06-09 17:10:03 UTC

As it's Rec601 they may benefit from a channel blend Rec601 to Rec709 preset

@RogerS What is this: "channel blend Rec601 to Rec709 preset"

Jøran

@J-Toresen Channel blend is a Fx and you should have a preset like this (or can make one) to fix the REC 601 colors from older Canon and current Fuji cameras.

@Nuno-Fernandes I was just able to download the first set up clips (took about 8 hours here). In VP 22.194 I didn't notice any increase in memory use while just playing them back. Are there any Fx that caused particular trouble? Happy to test those, too.

I think you may need someone with an AMD GPU to replicate this issue.

@RogerS Thank you. Jøran

 

 

As it's Rec601 they may benefit from a channel blend Rec601 to Rec709 preset

Hello, I've already tried using "Rec601 to Rec709 preset", but it still doesn't work.

The preview remains black, and I only have audio.

This is probably an AMD bug because if I disable "hardware decoder to use," everything works perfectly.

Strange.

That just fixes the colors, it won't do anything if the preview is black. Hopefully other AMD users can test the footage.

@Nuno-Fernandes I did try the files that you mention that will not play back in VP22 B194, and you are correct. I only get audio playback while the preview is black. I am using AMD latest drivers 24.10.1.

Your FHD files played back fine.

Your FHD files played back fine.

 

Hello.

It seems to be an issue with AMD graphics cards. I have a laptop with an i7 and an Nvidia 1050, and when I installed VP22 to test, Vegas immediately asked to download the codec and worked perfectly. On the desktop with AMD, however, the only way to get it to work is by disabling the GPU.

I also discovered what causes my memory usage to spike to 99%.

Simply disabling the "Enable GPU Import Path" option solves the problem.

@Nuno-Fernandes yes, it seems to plague us AMD GPU users. I wonder if it is a driver issue. It's sort of late here, and I have a funeral tomorrow. So maybe Saturday I will try different driver versions to be sure.

In the mean time, as you've discovered, disabling the GPU is a workaround for the moment. Hope this gets fixed soon!