Hey y'all,
I'm trying to implement a batch xml that we can run in version 2.5 of the MetaFuze Console. We've been using version 2.2.5 and the first XML I'm posting is a sample one of what we've been using(I left out everything from the file list and above to save space) :
</FileList> <Transcode> <Version>1.0</Version> <File>//path/to/file/name</File> <ClipName>sample_clipname</ClipName> <ProjectName>project_name</ProjectName> <TapeName>tape_name</TapeName> <TC_Start>00:00:00:00</TC_Start> <DropFrame>false</DropFrame> <EdgeTC>** TimeCode N/A **</EdgeTC> <FilmType>35.4</FilmType> <KN_Start>AAAAAAAA-0000+00</KN_Start> <Frames>47</Frames> <Width>1920</Width> <Height>1080</Height> <PixelRatio>1.0000</PixelRatio> <UseFilmInfo>false</UseFilmInfo> <UseTapeInfo>true</UseTapeInfo> <AudioChannelCount>0</AudioChannelCount> <UseMXFAudio>false</UseMXFAudio> <UseWAVAudio>false</UseWAVAudio> <SrcBitsPerChannel>8</SrcBitsPerChannel> <OutputVideoFormat>1080_23976P</OutputVideoFormat> <OutputConversionMode>ANAMORPHIC</OutputConversionMode> <OutputCompression>DNxHD 175</OutputCompression> <Eye></Eye> <Scene></Scene> <Comment></Comment> </Transcode> </Group></MetaFuze_BatchTranscode>
Now it seems the xml method has changed with version 2.5, so we made a new XML with the GUI, and it works on that machine, but any time we move it to another machine, it seems to be creating the file as uncompressed... Here's a copy of that XML:
</FileList> <Transcode> <Version>1.0</Version> <File>//path/to/file/name</File> <ClipName>sample_clipname</ClipName> <ProjectName>project_name</ProjectName> <TapeName>tape_name</TapeName> <TC_Start>00:00:00:00</TC_Start> <DropFrame>false</DropFrame> <EdgeTC>** TimeCode N/A **</EdgeTC> <FilmType>35.4</FilmType> <KN_Start>AAAAAAAA-0000+00</KN_Start> <Frames>47</Frames> <Width>1920</Width> <Height>1080</Height> <PixelRatio>1.0000</PixelRatio> <UseFilmInfo>false</UseFilmInfo> <UseTapeInfo>true</UseTapeInfo> <AudioChannelCount>0</AudioChannelCount> <UseMXFAudio>false</UseMXFAudio> <UseWAVAudio>false</UseWAVAudio> <SrcBitsPerChannel>8</SrcBitsPerChannel> <OutputPreset>ctest</OutputPreset> <OutputPreset> <Version>2.0</Version> <Name>ctest</Name> <ColorModel>YCC 709</ColorModel> <BitDepth>8</BitDepth> <Format>1080 23.976p</Format> <Compression>DNxHD 175</Compression> <Conversion>Anamorphic</Conversion> <VideoFileType>.mxf</VideoFileType> <IsDefault>false</IsDefault> </OutputPreset> <Eye></Eye> <Scene></Scene> <Comment></Comment> </Transcode> </Group></MetaFuze_BatchTranscode>
If you look in the other machine's <program files>\Avid\MetaFuze\output_presets\all.xml file, is the ctest output preset already existing with an Uncompressed compression?
Etienne AllardEngineer | P&S Creative ProfessionalAvid
I can't seem to find the output_presets folder in \Avid\MetaFuze\
It looks like a bug. A workaround, if you are going to always use the same presets, would be to create those preset on your main machine. Export all of them. Import them all on the remote machines through the MetaFuze UI. Like this, when the batch xml will be read, the MetaFuze on the remote machines will recognize the preset named in the batch.
Hey Etienne,
I hate to drudge up old problems, while the workaround successfully worked for clients that use a GUI, we can't figure out a way to implement this on a system without the GUI... We have a farm that we'd like to handle this, but they don't even have graphics cards. Any ideas how to handle this?
Will the bug ever be fixed? It's been almost a year!
Oh, wow, found something interesting. I just reinstalled MetaFuze, and the \output_presets\ folder was non-exsistent. Then I right-clicked and ran MetaFuze.exe and MetaFuzeApp.exe as Administrator. After that, the \output_presets\ folder AND the all.xml file appeared. This is exciting because it's the first time I've ever successfully seen that folder in 2.5. This still doesn't help with the systems that are command line only....
Just realized it wasn't only that, I also had to save a Column Preset to get this to work. Not sure what's happening exactly, this is a very strange bug!
Moderators! Please help!
Hi Dave!
Development for MetaFuze has slowed down, but a new version should be available soon. I can't guarantee that a fix for this specific bug will be provided with that version, but we're looking into it and are aware of its existance and annoyance it brings to the MetaFuze users. Thanks for reporting the bug as well as the repro-steps.
© Copyright 2011 Avid Technology, Inc. Terms of Use | Privacy Policy | Site Map | Find a Reseller