@jeremyscottproductions thank you for the sample file. Since the file is AVC (as found by @RogerS) the fix will also apply to this camera model. I tried local and it looks fully correct now. Please check announcements of @VEGASDerek when an update will be available (will be soon).

I installed the latest build and also have glitches with my MXF files (8bit 1920x1080 50P) files from my sony pxw-z280. Even in a test render this was still an issue the glitches. I thought it was only the preview in the timeline. I went back to the previous build 208. So I will wait for a fix.

@VEGASSteve, @VEGASDerek

Hi Steve.
I found out today that the MXF editing problems returned in VP 21 b315. Everything is ok in the b314 version.

I remind you that the non-functional option "open MXF as multichannel audio" is still not resolved. Even if this option is not enabled, MXF files are opened as multichannel.

I also noticed that the MXF events in the timeline stop for half a second when cut.

Instructions on how to replicate the bug:

1. sequence several short moving MXF video clips in a row.

2. Save the project. Close it. And open it again.

3. start playback and watch the flow between the slices of events.

Everything is fine with AVC and HEVC. The problem is only with MXF.

https://www.vegascreativesoftware.info/us/forum/vp-21-b315-mxf-events-always-stop-at-the-end-when-editing--146216/

@pierre-k With what MXF footage exactly? Please share MediaInfo and preferably a test file.

The MXF multichannel issue is true of 300+.

@pierre-k With what MXF footage exactly? Please share MediaInfo and preferably a test file.

The MXF multichannel issue is true of 300+.

I have already posted everything here in this thread.

@pierre-k

I used the 50p MXF source files that I downloaded in the past and never got around to using. I had no problem at all with Vegas Pro 21-315 on the machine in my signature. My project frame rate was set to 50P. The project settings in your original demo were 29.97P?

I don't have any issues with your C70 media in Vegas Pro 21-315 with the machine in my signature...

...even across a 10Gb network. (Not my normal work arrangement.)

I'm deferring my plug-in GPU purchase until Vegas Pro 35-759.

@VEGASSteve, @VEGASDerek

Hi Steve.
I found out today that the MXF editing problems returned in VP 21 b315. Everything is ok in the b314 version.

You're a Nvidia GPU user, shouldn't b314 and b315 operate identically?

I thought the only difference in 315 was a patch for AMD GPU's, and nothing else,

If that is not true, I'd like to know the details of what has changed.

@pierre-k

I used the 50p MXF source files that I downloaded in the past and never got around to using. I had no problem at all with Vegas Pro 21-315 on the machine in my signature. My project frame rate was set to 50P. The project settings in your original demo were 29.97P?

@john_dennis You spent too much time messing about after loading the project, he wants you to load project and immediately press play. I believe he's trying to avoid the Vegas VRAM caching which obscuring his alleged problem.

@Todd-AO Sorry. I've cut it off six times and it's still too short.

@john_dennis go frame by frame in your screen capture of the soccer players around your first edit point, there are duplicate frames before the edit point. Because it's of a mostly static man it's hard to see, but look at waveform to confirm. For a 1080P file and your 13900K processor that's unusual. It's where the frame counter is stuck on frame 295. Is that Vegas or your screen capture, because it's right at the edit point I'd think It's Vegas

@pierre-k With what MXF footage exactly? Please share MediaInfo and preferably a test file.

The MXF multichannel issue is true of 300+.

I have already posted everything here in this thread.

It wasn't clear if these were the same files.

So the problems you see with 315 are with the same Sony MXF 1080p 50fps 10-bit 422 AVC that you used before.

General
Format                         : MXF
Format version                 : 1.3
Format profile                 : OP-1a
Format settings                : Closed / Complete
File size                      : 52.3 MiB
Duration                       : 8 s 160 ms
Overall bit rate mode          : Variable
Overall bit rate               : 53.8 Mb/s
Frame rate                     : 50.000 FPS
Encoded date                   : 2023-06-22 15:15:39.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 fra : 2 frames
Format settings, GOP           : M=3, N=12
Format settings, wrapping mode : Frame
Format settings, Slice count   : 4 slices per frame
Codec ID                       : 0D01030102106001-0401020201316001
Duration                       : 8 s 160 ms
Bit rate mode                  : Variable
Bit rate                       : 49.2 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.474
Stream size                    : 47.8 MiB (91%)
Color range                    : Limited
Color primaries                : BT.709
Transfer characteristics       : BT.709
transfer_characteristics_Origi : xvYCC
Matrix coefficients            : BT.709

So the problems you see with 315 are with the same Sony MXF 1080p 50fps 10-bit 422 AVC that you used before.

 

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 fra : 2 frames
Format settings, GOP           : M=3, N=12
Format settings, wrapping mode : Frame
Format settings, Slice count   : 4 slices per frame
Codec ID                       : 0D01030102106001-0401020201316001

@RogerS If you rewrap that to MP4 it behaves the same way, so the Vegas bug is not to do with mxf but the AVC inside the mxf. Both the mxf and rewrapped mp4 playback across edits effortlessly in Resolve but poorly in Vegas.

Earlier I was demonstrating the difference between playback with the original mxf and a re-encoded mp4 to highlight the obvious pauses with the mxf, but later I considered all these bugged out AVC format profiles we've seen in VP21 b3xx and decided this is another

*As mentioned the mp4 shown here is re-encoded, not re-wrapped, re-wrapped it behaves as poorly as the mxf.

I just wish the beta testers showed as much passion in fixing Vegas we we do.

Thanks for testing a rewrap. I did some light testing splitting and rearranging these files on my underpowered GTX 1050 laptop and think caching may be confounding it a bit. I do get 50fps full playback but if I start at certain points it plummets, so I assume the better playback I see in places is thanks to caching and the problem is the inconsistency. 4:2:2 AVC isn't GPU decodable, and my cameras don't shoot it, so I haven't tested it much (but think it's Frosty's main media so he must have tested it a lot.)

I just wish the beta testers showed as much passion in fixing Vegas we we do.

In the spirit of creating a positive, welcoming community I'd ask if you can stop pitting users against each other? Don't we all just want to improve the program and volunteer our time and expertise in different ways? I don't think that issues we still see are due to a lack of effort in testing. There have to be factors like potentially limited engineering resources (didn't this company just go through a restructuring?) and the complexity of the VEGAS codebase.

The problems we unearth on the open forum here are clearly part of an information exchange that makes its way to the developers (and presumably testers and QA staff) and the changelogs show so many issues I see raised here that do get resolved (including the longstanding bug you created an excellent test for with NVENC and QSV bleeding frames between text, video and still images).

@RogerS, @Todd-AO, @john_dennis

Dear colleagues.
Today I tested a lot of MXF files in detail and the problem is more complex.

1. This file shows that MXF does not play smoothly in the Preview window even when the full number of frames is displayed. According to the vertical decay of the image during movement, vertical synchronization is probably not turned on.
If I turn on the full screen preview, the image is fine and does not break up vertically. Was it like this in all versions of Vegas?

2. Note that there was a bug in the image during continuous playback, which was fixed for MXF in version b.314. But if I copy this event and move it to a new VP21 window, the error disappears in the image. So you can't test one file by playing it twice and saying everything is fine.
Image errors occur gradually as you edit and cut MXF clips and stitch them together. The more you play them, the more often errors occur.

for test:

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

Here, see an illustrative example of how new and new errors in the video appear over time during editing and moving clips.

When I copy the error events and move them to a new VP21 window, some errors disappear and some remain.

,............................................................................................................

MXF Problem stopping clips at the end of an event.

There are several MXF events in the project. If you open the project again and start playback, the events at the end freeze for half a second. If you repeat playback, the problem will disappear. However, if you extend the events at the end and play them again, they will stop for a while exactly at the point of the original cut.

Demonstration:

If you play for example 10 events, everything is ok. But if you play 30 or more in a row, the MXF events stop at the end.

 

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

 

Demo clip plays smoothly. What am I doing wrong?

UPDATE: The original footage of the footballers was shot in FULLHD and seems to have been fixed in b314 and b315. The new problematic shots from the factory that are in the post above are 4k

Format                                   : MXF
Format version                           : 1.3
Format profile                           : OP-1a
Format settings                          : Closed / Complete
File size                                : 49.7 MiB
Duration                                 : 6 s 720 ms
Overall bit rate mode                    : Variable
Overall bit rate                         : 62.0 Mb/s
Frame rate                               : 25.000 FPS
Encoded date                             : 2024-07-03 08:18:47.000
Writing application                      : Sony Mem 2.00

Video
ID                                       : 2
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 frames        : 2 frames
Format settings, GOP                     : M=3, N=6
Format settings, wrapping mode           : Frame
Codec ID                                 : 0D01030102106001-0401020201314001
Duration                                 : 6 s 720 ms
Bit rate mode                            : Variable
Bit rate                                 : 57.4 Mb/s
Maximum bit rate                         : 60.0 Mb/s
Width                                    : 3 840 pixels
Height                                   : 2 160 pixels
Display aspect ratio                     : 16:9
Frame rate                               : 25.000 FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.277
Stream size                              : 46.0 MiB (93%)
Color range                              : Limited
Color primaries                          : BT.709
Transfer characteristics                 : BT.709
transfer_characteristics_Original        : xvYCC
Matrix coefficients                      : BT.709
Delay_SDTI                               : 75637240

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

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

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

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

Other #1
ID                                       : 1-Material
Type                                     : Time code
Format                                   : MXF TC
Frame rate                               : 25.000 FPS
Time code of first frame                 : 21:00:37:06
Time code of last frame                  : 21:00:43:23
Time code settings                       : Material Package
Time code, stripped                      : Yes

Other #2
ID                                       : 1-Source
Type                                     : Time code
Format                                   : MXF TC
Frame rate                               : 25.000 FPS
Time code of first frame                 : 21:00:37:06
Time code of last frame                  : 21:00:43:23
Time code settings                       : Source Package
Time code, stripped                      : Yes

Other #3
ID                                       : 7
Format                                   : Acquisition Metadata
Muxing mode                              : Ancillary data / RDD 18
Duration                                 : 6 s 720 ms
Frame rate                               : 25.000 FPS
Delay_SDTI                               : 75637240
IrisFNumber_FirstFrame                   : 5.600182
FocusPositionFromImagePlane_FirstFrame   : 8.100 m
AutoExposureMode_FirstFrame              : Full Auto
AutoFocusSensingAreaSetting_FirstFrame   : Center Sensitive Auto
CaptureFrameRate_FirstFrame              : 25.000 fps
ShutterSpeed_Time_FirstFrame             : 1/300 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                               : 25.000 FPS
Time code of first frame                 : 21:00:37:06

Thanks for the new file.

One comment is that VEGAS does have a wait for vertical sync function under preferences/ preview device. Looking at this fullscreen it seems to make some difference.

With this clip at the left of the timeline, frame 112-114 just after the panning starts seems to decode out of order giving a stutter-type effect. I don't see that going frame by frame in MPC Black. We saw similar decoding issues with MXF files with build 300. (This is tested with my desktop if it matters.)

Skipping around I was also able to trigger a completely green frame. You're right, the issues with this are complex.

After a few playbacks now I get a black frame where the two events meet. There is no actual black frame of course- this is well within the video.

Thanks for the new file.

One comment is that VEGAS does have a wait for vertical sync function under preferences/ preview device. Looking at this fullscreen it seems to make some difference.

This only applies if the Preview window is in Fullscreen - "Preview on External monitor". This does not apply to the classic small Preview window. Unfortunately.

Yes, that's correct.

Here you can see how 4k MXF does not play smoothly, even though the Preview window shows the full number of frames

https://drive.google.com/file/d/1JaMFSKaz9RqzkOt0nM7YWi8gPFh5sjMg/view?usp=drive_link

Thanks for the file link. I downloaded it and it played back smoothly with settings of Best>Full on my computer spec'ed below. No slight stutter.

I am on B315