Gentlemen - I have confirmed with 360 Systems that their server does indeed process the dv25 content wrapped in a type 1 avi wrapper - only type 1 - our non-linear editor creates dv25 content with a type 2 avi wrapper according to the openDML spec (this allows them to put timecode et. in the file). The server should say "no I'm sorry I can't possibly ingest this avi type 2 file" but it doesn't - it starts to tranfer then dumps you out - making it appear as if it's the FTP clients fault.
The reason that they process the file is because they change the wrapper to an MXF file which is the "new standard" making all these diverse devices all talk the same language. The issue is that it's a standard that everyone hasn't adopted yet.
Thanks again.
|
Hybrid Mode
