Ingex - video capture and transcoding / Discussion / Developers: XDCAMHD422@50Mbps support for writeavidmxf

Rens Dijkshoorn - 2010-12-09

l.s,

we would like to extend writeavidmxf to support XDCAMHD422@50Mbps.
Are there any plans to implement this in the near future? We would like
to support the development of this feature, is there a way we can contribute
to get this implemented.

Regards Rens Dijkshoorn

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Marc Struminki - 2011-07-04

Hello,
I am also interested for support XDCamHD422 in writeavidmxf.
There are plans to implement the codec?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Philip de Nier - 2011-07-13

We have support for XDCAM HD and AVC-Intra codecs in new media i/o library, but will need to decide whether to open-source that library and/or port the code back to writeavidmxf.

Philip

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Marc Struminki - 2012-01-13

Happy new year.
There are some new news about the new media i/o library and xdcamhd support in writeavidmxf?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Philip de Nier - 2012-01-13

The new media i/o library is called 'bmx' and is available here:
http://sourceforge.net/p/bmxlib/
The restructured libMXF and libMXF++ libraries are available there as well.
The file release is now rather old so I'd suggest using the git repository.

The raw2bmx or bmxtranswrap utilities in the bmx library can be used to generate or transwrap to Avid MXF files.

Philip

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Marc Struminki - 2012-01-17

Hi philipn,
thanks for the link to the bmxlib.
are the sources compatible to Windows?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Philip de Nier - 2012-01-17

Yes, the sources are compatible to Windows.

I happen to have made some updates yesterday to the git repository to support cross-compiling to mingw.

The other option is Visual C++. I've compiled libMXF and libMXF++ 3 months ago using Visual C++ 2010 using the project files. I've tested building parts of bmx but haven't got any project files that would work today. I'll probably take another look in the next couple of weeks as I need a Windows build for a project and mingw might not be whats wanted.

Philip

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Marc Struminki - 2012-01-17

So, I have a problem to convert an XDCamHD422 to avidMXF.

1. I convert an MXF-file to raw "mxf2raw -p C0001 C0001.MXF"
After the conversion to raw, I get some raw files e,g.: C0001_v0.raw C0001_a0.raw etc.

2. Then I use "raw2avidmxf -project test-project -clip C0001 -tape 0301111010142148 -y 21:48:04:24 -p C0001 -mpeg2lg_422p_hl C0001_v0.raw -pcm C0001_a0.raw -pcm C0001_a1.raw -pcm C0001_a2.raw -pcm C0001_a3.raw -pcm C0001_a4.raw -pcm C0001_a5.raw -pcm C0001_a6.raw -pcm C0001_a7.raw"

When this command finished, I get Avid compatible MXF Files, but the sound is defect.
Question: What am I doing wrong?

Marc

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Marc Struminki - 2012-01-17

Compiled is it with following configure options: ./configure -disable-shared

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Philip de Nier - 2012-01-17

Please use the latest code in the git repository. The raw2avidmxf command is no more.

In what way is the sound defected? Is the frame rate 25Hz? Does it sound like very loud noise? If so, then it could be 24-bit and the -q command-line option should be used if I remember correctly.

The latest code includes the bmxtranswrap command which will allows you to do the transwrap using a single step:

bmxtranswrap -t avid -o C0001 --clip --project test-project --clip C0001 --tape 0301111010142148 C0001.MXF

Philip
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Philip de Nier - 2012-01-17

Copy paste error… bmxtranswrap command should be:

bmxtranswrap -t avid -o C0001 --clip C0001 --project test-project --tape 0301111010142148 C0001.MXF

Philip
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Marc Struminki - 2012-01-17

OK. With bmxtranswrap it is all fine. :-))))))))
Thanks.

Marc

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Marc Struminki - 2012-01-24

Hey Guys,
bmxtranswrap is great to to convert XDCAMHD to AvidMXF.
I have a question to this tool. Do you plan to support XDCam SD with this tool?

Marc

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Philip de Nier - 2012-01-24

Sony MPEG IMX is supported (just pushed an update to fix bmxtranswrap to create an AS-11 sample file).
All DV formats, including DVCam, should be supported, but I haven't actually tried a Sony DVCam file.

Philip

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Hi Philip,
with your command line:

bmxtranswrap -t avid -o C0001 --clip C0001 --project test-project --tape 0301111010142148 C0001.MXF

comes a warning:

Warning: Track 1 has unknown essence type
Warning: Ignoring unsupported track 1 (essence type 'sound essence')

The PCM-Audio track have the problem. 8 Channels in one pcm track.

 ffmpeg -i C0001.MXF
FFmpeg version SVN-r13582, Copyright (c) 2000-2008 Fabrice Bellard, et al.
  configuration: --prefix=/usr --libdir=${prefix}/lib --shlibdir=${prefix}/lib --bindir=${prefix}/bin --incdir=${prefix}/include/ffmpeg --enable-shared --enable-libmp3lame --enable-gpl --enable-libfaad --mandir=${prefix}/share/man --enable-libvorbis --enable-pthreads --enable-libfaac --enable-libxvid --enable-postproc --enable-libamr-nb --enable-libamr-wb --enable-x11grab --enable-libgsm --enable-libx264 --enable-liba52 --enable-libtheora --extra-cflags=-Wall -g -fPIC -DPIC --cc=ccache cc --enable-swscale --enable-libdc1394 --enable-nonfree --disable-mmx --disable-stripping --enable-avfilter --enable-libdirac --disable-decoder=libdirac --enable-libschroedinger --disable-encoder=libschroedinger --disable-altivec --disable-armv5te --disable-armv6 --disable-vis
  libavutil version: 49.7.0
  libavcodec version: 51.58.0
  libavformat version: 52.16.0
  libavdevice version: 52.0.0
  libavfilter version: 0.0.0
  built on Oct  4 2010 18:36:29, gcc: 4.3.2
Input #0, mxf, from 'C0001.MXF':
  Duration: 00:00:29.40, start: 0.000000, bitrate: 62569 kb/s
    Stream #0.0: Video: mpeg2video, yuv422p, 720x608 [PAR 608:405 DAR 16:9], 50000 kb/s, 25.00 tb(r)
    Stream #0.1: Audio: pcm_s16le, 48000 Hz, 8 channels, 6144 kb/s
Must supply at least one output file

Wraping of the IMX-Codec is no problem.

Marc

Philip de Nier - 2012-01-27

There was a fix for reading Sony MPEG IMX files on January 24th:

commit db765659bc367a9c9f1df163eb062f63735f291c
Author: Philip de Nier <philipn@users.sourceforge.net>
Date: Tue Jan 24 12:24:34 2012 +0000

bmxtranswrap: fix d10 audio detection and track creation

Philip

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Marc Struminki - 2012-02-01

Hi Philip,
I checked out the new version of bmx library. The conversion from XDCamSD to AvidMXF is functional.
Thanks.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Philip de Nier - 2012-02-01

Good to hear - thanks.

Philip

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Marc Struminki - 2012-02-09

Hi,
when we want to play codolitdated MXF-Files, that are generated with mxftranswrap, we get this Message/Error:

Exception: MXF_DIDMapper::ReadRange - End Sample Index exceeds on-disk Index Entry Count.

Marc
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Philip de Nier - 2012-02-09

Could you send me the output of "MXFDump -no-limit-entries -show-dark <filename>" for the video file? (MXFDump is in the libMXF/tools/MXFDump directory).

Philip

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Marc Struminki - 2012-02-09

When I get the file, I make the Dump.
The original or consolidated file?

Marc

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Philip de Nier - 2012-02-09

Both if possible please.

I assume the consolidated file equals bmxtranswrap generated file?

I did some quick tests with Media Composer 5.0.3 and found that it behaved differently (played black) if the file had rollout. You can check for rollout in your file by running "mxf2raw -i" and looking for a non-zero Rollout property.
My assumption that Avid supports rollout was therefore wrong.

Maybe different versions of Avid react differently to rollout. Which product and version of Avid are you using?

Philip

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Marc Struminki - 2012-02-13

Hi Philip,
I need an email-address, where I can mail the log-files.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Philip de Nier - 2012-02-13

Try philipn@users.sourceforge.net

Philip

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Philip de Nier - 2012-02-14

Thanks for the log files.

I confirmed that the consolidated MXF files have issues and that the Avid error

Exception: MXF_DIDMapper::ReadRange - End Sample Index exceeds on-disk Index Entry Count.

is understandable given those issues.

The consolidated MXF file had these values:
* duration = 0x0484
* (Material Package) start position = 0x16fa
* index duration = 0x1b7e
* Index entry count = 0x0486
* index duration - start position = duration
The index duration is therefore wrong (> index entry count) and the large start position is also a bit surprising.

The question I have is what edit sequence resulted in Avid producing this broken consolidated MXF file?

I tried replicating it here with some XDCAM content but couldn't get the same error. I have Media Composer 5.0 whilst you have 5.5.

I had the same results for both the bmxtranswrap files as well as XDCAM imported files.

I'm thinking that there is an issue with Avid rather than an issue with the bmxtranswrap MXF files.

Could you try consolidating the same edit sequence, but using the original XDCAM MXF file imported into Avid (e.g. drag and dropped into a bin)? Or, could you explain how I could reproduce the error?

Philip

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

XDCAMHD422@50Mbps support for writeavidmxf

Forums

Help

XDCAMHD422@50Mbps support for writeavidmxf

XDCAMHD422@50Mbps support for writeavidmxf

Forums

Help

XDCAMHD422@50Mbps support for writeavidmxf document.SUBSCRIPTION_OPTIONS = { "thing": "topic", "subscribed": false, "url": "subscribe", "icon": { "css": "fa fa-envelope-o" } };

XDCAMHD422@50Mbps support for writeavidmxf