I added another file from the same day with same Nano settings but different Sony EX1 microphone configuration (microphone in both XLR inputs). VLC allows viewing the codec information and shows that all of these MXF files have different audio Stream orders. The MXF files, both Eseals_01189001.MXF with VLC sound and Rays_01134001.MXF with no VLC sound, have the same Stream ordering as show in in VLC's Codec Information.

Eseals_01189001.MXF Nano file, microphone in both XLR inputs, LongGOP 100 MBps

Rays_00001135_01.MP4 SxS file, microphone in right XLR input, LongGOP 100 MBps

Rays_01134001.MXF Nano file, microphone in right XLR input, LongGOP 100 MBps

Rays_00001135_01_mxf_SonyClipBrowserExportMXFforNLE.mxf : SxS MP4 file exported from Sony ClipBrowser 2.6 under "Export MXF for NLEs"

Rays_00001135_01_mxf_SonyClipBrowserExportforXDCAM422.mxf : SxS MP4 file exported from Sony Clip Browser under "Export for XDCAM HD422

My nanofile opened in VLC shows two audio tracks, one mono, the other 1-channel (not sure what the difference is, but that is how VLC reports it). VLC plays the sound the same regardless of which audio track I choose.

Vegas says there is one audio track and it is stereo but does not play the sound.

The .wav file created by SUPER® has one mono track according to both VLC and Vegas.

At any rate, if VLC sees two mono channels and Vegas sees one stereo channel, that shows some kind of format incompatibility somewhere. The original that was recorded by the nano had stereo sound, so it is strange that it looks like two mono tracks to VLC (and apparently to SUPER®).

The Sony XDCAM Viewer plays both the audio and video and says the audio is in the AES-3 format with 2 channels

Of course, the Viewer is a 32-bit app, while Vegas is a 64-bit app, so it is an unfair comparison.

Dear Adam,

It could be that a file recorded with 1.6.29, our latest release may work for you.

I believe that we had some problems in this area, last December.

I do not know of any similiar problems reported with 1.6.29.

This is all strange... I never had any problem with audio channel mapping in Vegas. The original SxS mxf files are read as 4-channel (with only channel 1 and 2 actually containing audio), while those from the nanoFlash - as 2 channel. In both cases, the 2 channels that contain the audio are arranged as a single, stereo track...

Piotr, where do you get SxS MXF files? Aren't they MP4 ?

ClipBrowser MXF and Nanoflash MXF appear to have a different MXF structure, at least from viewing them from VLC. Check the PNG files in my link above that show the Codec Details from VLC. Nano's MXF uses 24 bits/sample and two Streams, one Channels=1 and Channels=Mono . ClipBrowser exports 16 bits/sample with four Streams, three with Channels=1 and Channels=Mono . Though, I'm reporting MXF files that play in Vegas and are silent in VLC.

Gints,

You're right - the native format of SxS files is mp4 (mpeg-2 in the mp4 wrapper, to be exact), and you can read them directly by Vegas.

However in my workflow, I always preferred to re-wrap from mp4 container to the mxf (ClipBrowser does it on the fly using the "Export for NLE" option). This way, I'm always working with mxf regardless of whether the clips come from the SxS or the nanoFlash.

Again: both SxS and nano mxf audio is OK here (in VLC as well as Sony MXF Player, or NLEs such as Vegas and Edius).