MetaFuze 2.0 23.976 -> 59.94i

[SteveHerring]

Hello all,

I'm wondering what the potential workflow is to take a bunch of .r3d files that were shot 23.976 and get them into a 59.94i (really 29.97) project? It'd be ideal to be able to have an "add pulldown" flag somewhere within MetaFuze to make this happen. Is there another way to accomplish this that I'm missing?

Any idea when 1080/29.97P might be supported?

Also, for conforming/re-linking after editing something compressed with DNxHD-36, is there an equivalent method to Monkey Extract for using MetaFuze with it's current version? I see mentions of there being documentation for working with XML and the command line, but don't find any documentation anywhere. Where should I be looking?

Thanks in advance,
Steve

 

[Igor Ridanovic]

Also, for conforming/re-linking after editing something compressed with DNxHD-36, is there an equivalent method to Monkey Extract for using MetaFuze with it's current version? I see mentions of there being documentation for working with XML and the command line, but don't find any documentation anywhere. Where should I be looking?

Thanks in advance,
Steve

You mean doing a final conform with Media Composer or Symphony? You could delete all your DNxHD 36 media generated by MetaFuze and then reincode at uncompressed setting and relink.

 

[SteveHerring]

You mean doing a final conform with Media Composer or Symphony? You could delete all your DNxHD 36 media generated by MetaFuze and then reincode at uncompressed setting and relink.

Yes, doing a final conform with a Symphony. The challenge I'm trying to resolve: to re-encode a large quantity of material (the original raw material) is both a waste of time and requires a large amount of storage. We'd like to only transcode the selects used in the sequence (ala Monkey Extract - which we also have).

It seems like this is made possible by use of XML and a command-line interface with MetaFuze 2.0, but I can't find any documentation on how to make this work.

Thanks,
Steve

 

[MichaelP]

The XML in MetaFuze at this point is a method by which you can drive settings and line commands to batch processing without the GUI. Remember that XML is only a description language format. What is contains is the important part.

But to answer your question, no. MetaFuze does not take the pull list/scan list as XML or an EDL and do a retranscode of the elements used. It is something we would like to add for a future release.

Michael

 

[SteveHerring]

The XML in MetaFuze at this point is a method by which you can drive settings and line commands to batch processing without the GUI. Remember that XML is only a description language format. What is contains is the important part.

But to answer your question, no. MetaFuze does not take the pull list/scan list as XML or an EDL and do a retranscode of the elements used. It is something we would like to add for a future release.

Michael

That's what I thought at the moment. If we could come up with some glue scripting to deal with the XML from the list to create our own pull lists, it should be possible to use the XML command-line based Metafuze to transcode, correct?

Back to my original two questions, where could/would I find additional documentation for MetaFuze, and what about 30P support?

Thanks again,
Steve

 

[david m friedman]

the only way i can think of to do it would be to use redrushes & metacheater rather than metafuze.

 

[MichaelP]

MetaFuze documentation is with the installer. Look in the application folder once installed. 30p is something we need to add in the next release.

Michael

 

[cls105]

im being told the footage i got was shot at 60 frames a second. when i convert using metafuze everything is in slowmotion. is there anyway to make this footage playback at real life speed before it gets to avid ie without motion effects.