Someone from here sends me MXF files to look at their problem.
Oh oh, they will not open in V8.0b. I open them in V9.0a but other Vegas user doesn't have V9 so project file not much use to them.
OK, so I go back to those MXF files. Here's a thing, they also open in Ppro CS3 and VLC. Anyways need to move this forward to help a fellow Vegas user so I take the problem MXF files into V9 and render them out as um, MXF files, supposedly XDCAM EX compliant 4:2:0 HQ 29.970p.
Still no joy opening the files in V8.0b. Of course V8.0b quite happily opens all MY MXF files from the Clipbrowser??
So now I'm having one of those 'WTF gives here' moments with Vegas. Only logical conclusion I can reach is Vegas has been playing fast and loose with Sony's own MXF specification. It's a pretty poor show when Sony's own software company that must have access to the actual Sony specs gets it mixed up and yet Adobe can seemingly get it right. What's further confounding is all Vegas really does is read the mpeg-2 stream from the MXF/mp4 container, it does nothing with the essence metadata etc, it should be easily able to read the video regardless.
To distill the above into it's essence. The MXF files that V9 is creating are not exactly the same as the ones Sony's Clipbrowser is creating. At the very least this is a minor issue that's annoying to me, at the very worst it's a potential disaster if other apps such as FCP etc cannot read them.
Bob.
Oh oh, they will not open in V8.0b. I open them in V9.0a but other Vegas user doesn't have V9 so project file not much use to them.
OK, so I go back to those MXF files. Here's a thing, they also open in Ppro CS3 and VLC. Anyways need to move this forward to help a fellow Vegas user so I take the problem MXF files into V9 and render them out as um, MXF files, supposedly XDCAM EX compliant 4:2:0 HQ 29.970p.
Still no joy opening the files in V8.0b. Of course V8.0b quite happily opens all MY MXF files from the Clipbrowser??
So now I'm having one of those 'WTF gives here' moments with Vegas. Only logical conclusion I can reach is Vegas has been playing fast and loose with Sony's own MXF specification. It's a pretty poor show when Sony's own software company that must have access to the actual Sony specs gets it mixed up and yet Adobe can seemingly get it right. What's further confounding is all Vegas really does is read the mpeg-2 stream from the MXF/mp4 container, it does nothing with the essence metadata etc, it should be easily able to read the video regardless.
To distill the above into it's essence. The MXF files that V9 is creating are not exactly the same as the ones Sony's Clipbrowser is creating. At the very least this is a minor issue that's annoying to me, at the very worst it's a potential disaster if other apps such as FCP etc cannot read them.
Bob.