The source files are nothing special, the majority are simply H264/AAC/MP4. I have encountered some files which are causing encoding problems, but I'll raise this in a different post after we get XDCAM output working.
We tried different output processors (h264/aac/mp4, DNxHD/MXF and XDCAM/MOV) without issue.
I built the simplest workflow I could, for testing source and compatibility with our playout system.
Folder -> AV/Media -> XDCAM -> Folder
this is the command I see is running;
Code: Select all
C:\WINDOWS\system32\cmd.exe /c ""C:\Users\mheath\Downloads\FFAStrans0.7.6_Win32\Processors\mxf_tools\bmxtranswrap.exe" -o "c:\.ffastrans_work_root\20160922150016\20160923-172741-495-70B7DB8CB4F1\~20160923-172744-902-958CA338DC54.mxf.mxf" "c:\.ffastrans_work_root\20160922150016\20160923-172741-495-70B7DB8CB4F1\~20160923-172744-902-958CA338DC54.mxf"
bmxtranswrap defaults to type as02 (I thought we want op1a) as02 produces a directory (which it calls a bundle) with the double .mxf extension containing demuxed mxf streams. This does not look right to me.
section from bmxtranswrap help
Code: Select all
-t <type> Clip type: as02, as11op1a, as11d10, op1a, avid, d10, wave. Default is as02
* -o <name> as02: <name> is a bundle name
as11op1a/as11d10/op1a/d10/wave: <name> is a filename
avid: <name> is a filename prefix
which is producing, the bundle
Code: Select all
Directory of C:\.ffastrans_work_root\20160922150016\20160923-144925-392-687F09DE227C\~20160923-144934-852-6B32C1F283CF.mxf.mxf
23/09/2016 02:49 PM <DIR> .
23/09/2016 02:49 PM <DIR> ..
23/09/2016 02:49 PM 2,608 manifest.xml
23/09/2016 02:49 PM <DIR> media
23/09/2016 02:49 PM 246 shim.xml
23/09/2016 02:49 PM 18,706 ~20160923-144934-852-6B32C1F283CF.mxf.mxf.mxf
3 File(s) 21,560 bytes
Directory of C:\.ffastrans_work_root\20160922150016\20160923-144925-392-687F09DE227C\~20160923-144934-852-6B32C1F283CF.mxf.mxf\media
23/09/2016 02:49 PM <DIR> .
23/09/2016 02:49 PM <DIR> ..
23/09/2016 02:49 PM 1,948,471 ~20160923-144934-852-6B32C1F283CF.mxf.mxf_a0.mxf
23/09/2016 02:49 PM 1,948,471 ~20160923-144934-852-6B32C1F283CF.mxf.mxf_a1.mxf
23/09/2016 02:49 PM 1,948,471 ~20160923-144934-852-6B32C1F283CF.mxf.mxf_a2.mxf
23/09/2016 02:49 PM 1,948,471 ~20160923-144934-852-6B32C1F283CF.mxf.mxf_a3.mxf
23/09/2016 02:49 PM 27,844,006 ~20160923-144934-852-6B32C1F283CF.mxf.mxf_v0.mxf
5 File(s) 35,637,890 bytes
Total Files Listed:
8 File(s) 35,659,450 bytes
5 Dir(s) 296,711,540,736 bytes free
I would expect these files to be remux-ed back together but instead it just appears to try and copy the directory.
I now get the error
Code: Select all
Getting error code 3 - the system cannot find the path specified, when trying to deliver "\\server\path\m-mh-dachsunddash-24-d.mxf\media"
At first I only see these files delivered in the output directory
Code: Select all
24/09/2016 01:39 PM 18,706 m-mh-dachsunddash-24-d.mxf
24/09/2016 01:39 PM 2,609 m-mh-dachsunddash-24-d.xml
But when the deliveries processor has counted down from 50 to 0, I see these files (do have unique file ticked in the processor)
The _5 version of the media appears to be correct.
Code: Select all
24/09/2016 01:39 PM 2,960,471 m-mh-dachsunddash-24-d_2.mxf
24/09/2016 01:39 PM 246 m-mh-dachsunddash-24-d_1.xml
24/09/2016 01:39 PM 135,798,699 m-mh-dachsunddash-24-d_5.mxf
24/09/2016 01:39 PM 2,960,471 m-mh-dachsunddash-24-d_3.mxf
24/09/2016 01:39 PM 18,706 m-mh-dachsunddash-24-d.mxf
24/09/2016 01:39 PM 2,609 m-mh-dachsunddash-24-d.xml
24/09/2016 01:39 PM 2,960,471 m-mh-dachsunddash-24-d_4.mxf
24/09/2016 01:39 PM 2,960,471 m-mh-dachsunddash-24-d_1.mxf
8 File(s) 147,662,144 bytes
0 Dir(s) 10,850,709,252,096 bytes free
I got a bit fooled when I saw the error code 3 and manually aborted the job. I can see that the correct file does eventually appear, but it's named incorrectly and other files are also delivered. It doesn't appear to be working as expected.