VP21 b300 - VP22. Still unresolved bugs with 4K MXF and HEVC files

pierre-k wrote on 4/8/2024, 10:16 AM

I have a big problem with MXF files.
Vegas uses mxcompoundplug.dll

Although the videos play amazingly smoothly now, there are major problems.

1. For some interviews, the image is delayed by about a second. There are often artifacts in the video and flickering of images from another part of the file.

2. MXFs are imported as multichannel audio even if this option is not enabled.

3. If I open multiple MXF files, they look like this in the timeline:

I don't have time for more experiments. I am reverting back to a lower version.

Format                                   : MXF
Format version                           : 1.3
Format profile                           : OP-1a
Format settings                          : Closed / Complete
File size                                : 147 MiB
Duration                                 : 24 s 0 ms
Overall bit rate mode                    : Variable
Overall bit rate                         : 51.5 Mb/s
Frame rate                               : 50.000 FPS
Encoded date                             : 2023-06-07 09:46:50.000
Writing application                      : Sony Mem 2.00

Video
ID                                       : 2
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : High 4:2:2@L4.2
Format settings                          : CABAC / 2 Ref Frames
Format settings, CABAC                   : Yes
Format settings, Reference frames        : 2 frames
Format settings, GOP                     : M=3, N=12
Format settings, wrapping mode           : Frame
Codec ID                                 : 0D01030102106001-0401020201316001
Duration                                 : 24 s 0 ms
Bit rate mode                            : Variable
Bit rate                                 : 46.8 Mb/s
Maximum bit rate                         : 50.0 Mb/s
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate                               : 50.000 FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:2
Bit depth                                : 10 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.452
Stream size                              : 134 MiB (91%)
Color range                              : Limited
Color primaries                          : BT.709
Transfer characteristics                 : BT.709
transfer_characteristics_Original        : xvYCC
Matrix coefficients                      : BT.709
Delay_SDTI                               : 54494840

Audio #1
ID                                       : 3
Format                                   : PCM
Format settings                          : Little
Format settings, wrapping mode           : Frame (AES)
Codec ID                                 : 0D01030102060300-0402020101000000
Duration                                 : 24 s 0 ms
Bit rate mode                            : Constant
Bit rate                                 : 1 152 kb/s
Channel(s)                               : 1 channel
Sampling rate                            : 48.0 kHz
Frame rate                               : 50.000 FPS (960 SPF)
Bit depth                                : 24 bits
Stream size                              : 3.30 MiB (2%)
Delay_SDTI                               : 54494840
Locked                                   : Yes

Audio #2
ID                                       : 4
Format                                   : PCM
Format settings                          : Little
Format settings, wrapping mode           : Frame (AES)
Codec ID                                 : 0D01030102060300-0402020101000000
Duration                                 : 24 s 0 ms
Bit rate mode                            : Constant
Bit rate                                 : 1 152 kb/s
Channel(s)                               : 1 channel
Sampling rate                            : 48.0 kHz
Frame rate                               : 50.000 FPS (960 SPF)
Bit depth                                : 24 bits
Stream size                              : 3.30 MiB (2%)
Delay_SDTI                               : 54494840
Locked                                   : Yes

Audio #3
ID                                       : 5
Format                                   : PCM
Format settings                          : Little
Format settings, wrapping mode           : Frame (AES)
Codec ID                                 : 0D01030102060300-0402020101000000
Duration                                 : 24 s 0 ms
Bit rate mode                            : Constant
Bit rate                                 : 1 152 kb/s
Channel(s)                               : 1 channel
Sampling rate                            : 48.0 kHz
Frame rate                               : 50.000 FPS (960 SPF)
Bit depth                                : 24 bits
Stream size                              : 3.30 MiB (2%)
Delay_SDTI                               : 54494840
Locked                                   : Yes

Audio #4
ID                                       : 6
Format                                   : PCM
Format settings                          : Little
Format settings, wrapping mode           : Frame (AES)
Codec ID                                 : 0D01030102060300-0402020101000000
Duration                                 : 24 s 0 ms
Bit rate mode                            : Constant
Bit rate                                 : 1 152 kb/s
Channel(s)                               : 1 channel
Sampling rate                            : 48.0 kHz
Frame rate                               : 50.000 FPS (960 SPF)
Bit depth                                : 24 bits
Stream size                              : 3.30 MiB (2%)
Delay_SDTI                               : 54494840
Locked                                   : Yes

Other #1
ID                                       : 1-Material
Type                                     : Time code
Format                                   : MXF TC
Frame rate                               : 50.000 FPS
Time code of first frame                 : 15:08:14:42
Time code of last frame                  : 15:08:38:41
Time code settings                       : Material Package
Time code, stripped                      : Yes

Other #2
ID                                       : 1-Source
Type                                     : Time code
Format                                   : MXF TC
Frame rate                               : 50.000 FPS
Time code of first frame                 : 15:08:14:42
Time code of last frame                  : 15:08:38:41
Time code settings                       : Source Package
Time code, stripped                      : Yes

Other #3
ID                                       : 7
Format                                   : Acquisition Metadata
Muxing mode                              : Ancillary data / RDD 18
Duration                                 : 24 s 0 ms
Frame rate                               : 50.000 FPS
Delay_SDTI                               : 54494840
IrisFNumber_FirstFrame                   : 5.600182
FocusPositionFromImagePlane_FirstFrame   : 9.400 m
AutoExposureMode_FirstFrame              : Full Auto
AutoFocusSensingAreaSetting_FirstFrame   : Manual
CaptureFrameRate_FirstFrame              : 50.000 fps
ShutterSpeed_Time_FirstFrame             : 1/50 s
CameraMasterGainAdjustment_FirstFrame    : 0.00 dB
ElectricalExtenderMagnification_FirstFra : 100%
AutoWhiteBalanceMode_FirstFrame          : Automatic

Other #4
Type                                     : Time code
Format                                   : SMPTE TC
Muxing mode                              : SDTI
Frame rate                               : 50.000 FPS
Time code of first frame                 : 15:08:14:42

Back to post

Comments

VEGASSteve wrote on 11/1/2024, 6:55 AM

Hello @pierre-k I kindly asked @VEGASMichael to have a look on the NVIDIA artifact problem. I could not reproduce this on my machine so far..

VEGASSteve wrote on 11/1/2024, 7:11 AM

Hello @pierre-k I also tried to reproduce the problem with the delays between the media events while playback. I got this file: "Clip0174.MXF" from a former link in this thread (sports event). I did copy it four times and placed them all in a time line. My playback runs smooth without delays.

Can you please check again these points: GPU setup for "video" and "file i/o" correct? Maybe remove side car files in folder to force recreation. Also adjusting the RAM preview setting will strongly influence the number of buffers hold in (video) RAM, so it makes sense to try this. I have a default value of 5%. If you don't rely on too many of them - it should be also worth to reset the preferences of the app by starting with Ctrl+Shift and confirm with "yes".

These steps may sound a bit arbitrary, but first step would be to adjust your machine to the developers machines to make it able to reproduce the problem. Otherwise there is no good chance to fix this..

Also one more test would be great - if you try my test with only four copies of one and the same file - do you still experience the delays between the clips?

pierre-k wrote on 11/1/2024, 7:34 AM

@VEGASSteve

Hi Steve.
I have a better suggestion for you. The whole project. It's 5GB.
But I don't want to publish it here. Please, I can send you the link in a message. But I don't see you in my contacts.

You can test the problem with stopping between cuts in it.

Procedure:
1. Open the project in VP22. (If something is missing, ignore it).
2. Start playback and see if the events stop at the end.
(If you play the project a second time, the problem will disappear. But if you then extend the events and play them again, the stop will remain there)

I've tried absolutely everything. I/O, reset, Internal settings.
Nothing helped. The only solution for me is VP21 b208 and older.

Please try it on more machines and let me know how the testing went.
I need feedback.

pierre-k wrote on 11/1/2024, 7:38 AM

@VEGASSteve

There must be a lot of files. You won't recognize anything on one file that you repeat several times.

RAM settings only make sense in VP21 b208. In VP22, RAM settings don't seem to work at all.

VEGASMichael wrote on 11/1/2024, 8:57 AM

@pierre-k: You could click at @VEGASSteve here in the message and should see his profile with the option to send a message. So you could post your link to him (and a copy to me if you don't mind... :))

pierre-k wrote on 11/1/2024, 9:09 AM

@VEGASMichael

Hi. I'd love to, but you also have to write to me first because I don't see you in my contacts. Thanks a lot.

RogerS wrote on 11/1/2024, 9:47 AM

I don't think general forum users are allowed to write to staff and must be contacted first.

pierre-k wrote on 11/1/2024, 10:02 AM

I don't think general forum users are allowed to write to staff and must be contacted first.

Yes. Michael has to write to me first.

vkmast wrote on 11/1/2024, 10:29 AM

Not only Michael, but Steve as well as per RogerS' comment.

VEGASSteve wrote on 11/19/2024, 4:19 AM

Finally the former described second issue with NVIDIA driver and artifacts / green frames while accessing two tracks containing parts of the same file could be located and (hopefully) fixed. Please check for announcements of @VEGASDerek on the next version.

pierre-k wrote on 1/22/2025, 4:45 AM

@VEGASSteve, @VEGASMichael, @RogerS, @VEGASDerek

Hi.
Today I tried the VP22 b237 version
and both problems are still not resolved.

1. stopping events between cuts using 4k MXF
2. pixelation of 4k HEVC and 4k MXF during editing

I remind you that the errors already occurred in VP 21 b300.
You already have all the materials for reproduction and you have confirmed the errors.
I would appreciate your feedback on whether a fix is coming.

I still have to use VP 21 b208.

pierre-k wrote on 1/24/2025, 6:09 AM

@VEGASSteve, @RogerS, @VEGASDerek, @VEGASMichael

Hi.
Today I tried the VP22 b239 version
and both problems are still not resolved.

1. stopping events between cuts using 4k MXF
2. pixelation of 4k HEVC and 4k MXF during editing

I remind you that the bugs already occurred in VP 21 b300.
You already have all the materials for reproduction and you have confirmed the bugs.

3. This is New Bug - audio desynchronization with MXF

Please download this test project.

https://drive.google.com/file/d/1UfhBs3_nkoJaZ64_JgnX-HcL9dBV9yvx/view?usp=drive_link

There are two events in the project.
The one on the left has bad audio synchronization.
The one on the right needs to be shifted by 0.04 to be synchronized with the video.

I would appreciate your feedback on whether a fix is coming.

I still have to use VP 21 b208.

set wrote on 1/24/2025, 7:10 AM

Mod note: change title of this thread as per request by OP from

'VP21 b300 and big problem with MXF'

"VP21 b300 - VP22. Still unresolved bugs with 4K MXF and HEVC files"

johnny-s wrote on 1/24/2025, 9:11 AM

I previously posted within the main thread for vp22 239 that if other users now found everything aok in b239 (re: AV sync) that I would leave as is. My reason is that I wasn’t using typical SOOC material and so the material wouldn’t be that relevant to most users.

FWIW the mp4 ffmpeg generated (from .ts) vfr 8 bit 420 sample I tested is still out of sync with latest build when viewed in vp and when rendered out from vp. It plays in sync with vlc/Mpc. If I extract ( not using vp) a small piece, no transcoding, its also ok, not out of sync.

VEGASSteve wrote on 1/28/2025, 7:04 AM

Hello @pierre-k tried your sample MXF project with LEFT(WRONG) and RIGHT, I don't see any sync issue on my machine. I opened the .veg project and playback different locations left/right. Did you try anything else? I'm working on a Nvidia, the GPU shall however play no role here.. We recently fixed some positioning details, but they should differ at maximum by 2 frames (40ms here).

VEGASSteve wrote on 1/28/2025, 7:15 AM

Hello @pierre-k the pixelation should also be fixed in the lastest beta, can you please post a screen shot with the output and the project? This was fixed at least for some cases with NVIDIA reading.

VEGASSteve wrote on 1/28/2025, 7:22 AM

Hello @pierre-k - and for the third problem - delays between the events - I tried to check the delta between VP 21 b208 and VP 21 b300, but this is almost half a year, there are too many differences. Could you please check the event properties, if there is a different plugin used for reading the material in the two VP21 versions? (event > properties > common > Plug-In) Maybe the switch from the mxfavcplug to mxcompoundplug happened in this period.

If this is the case, I could add the MXF case to the list of legacy switching, in result you would be able to set a legacy option which would enable the usage of the alternative plugin for reading MXF.

@VEGASDerek FYI

pierre-k wrote on 1/28/2025, 9:46 AM

@VEGASSteve, @VEGASDerek, @RogerS

1. 4K HEVC - a way to easily reproduce bugs in video using reversion

2. Stopping 4k MXF between cuts and pixelation.

In VP21 b208 the mxfavcplug plugin is active for MXF. Newer versions use the mxcompoundplug plugin. Please try changing the plugin to mxfavcplug in your beta version and tell me if it works. Thanks. Maybe this will solve the problems with occasional pixelation of the video when editing.

3. I confirm the MXF audio delay of 0.04 in VP22 b239.

You have all the files and projects from me.
Good luck with your testing.

pierre-k wrote on 1/28/2025, 10:05 AM

@VEGASSteve, @VEGASDerek

Question:

If I enable the old mxfavcplug in VP22, will the acceleration and smooth playback of 4k MXF video be maintained? I don't want the Legacy option for MXF to be a throwback to the dinosaur era. That wouldn't be the solution I want. Thanks for the clarification.

1 … 3 4 5 6

of 6