huge metafuze render time

[Bogdan Dumitru]

Hi all,

I'm transcoding in metafuze 4k r3d in 1920x1080 MXF DNxHD 40, with the timecode burned in the picture and I have a ratio of 20:1.

In task manager, all 4 cores (from my 8-core macpro) are at 30-40%.

Am I doing something wrong, because these are huge times.....

thanks,

[MichaelP]

What debayer setting are you using?

[Bogdan Dumitru]

I'm using quarter good.
the thing is that windows xp is 32 bits.
would be faster on 64 bits windows so I can increase the memory of virtual machine to 4 gb (half of entire memory) ?

in the same time, windows it seems to move slow....sometimes stucks for few seconds in metafuze.

[Job ter Burg]

I have occasionally done some MetaFuze work on a 2.4GHz iMac under Parallels with XP32. That worked, but a bit slow (around 15-20:1 at Half Good, IIRC). On my MBP, under BootCamp and Vista 64, I got reasonable transcode times (around 8-10:1 at Half Good).

Which version of MetaFuze are you using? A new one is just out (2.2.5, supports the MX color space).

If you're on a Mac, you could also use RedCine-X, or Media Composer v5 rather than MetaFuze.

[Bogdan Dumitru]

what are the rendering times you have with redcine-x ?
I'v tried with recine-x but it doesn't keep the same filename of the original r3d files (even if I select "output with clip filename"). after date it puts some random characters and it's with 2 characters longer than original.

what about MC5 ? how does it renders ?

thanks,

[Job ter Burg]

what are the rendering times you have with redcine-x ?
what about MC5 ? how does it renders ?



http://community.avid.com/forums/t/85371.aspx

I don't think that MXF filename has any relevance. Don't worry about that. You need the correct metadata at Avid bin/clip/timeline level.

[Bogdan Dumitru]

I need to finish the project in Baselight 4 by a conform from an EDL from editing in AVID.
If I don't have the same filename in MXF, RED and also in ALE I won't be able to do that.

the redcine-x seems to make the proper ALE files (I have the red filename, without extension of course) but renames the MXF files.

so ? how did you guys worked on this workflow... ?

thanks,

[Job ter Burg]

I've done that route.

The MXF filename is irrelevant, as MC makes its EDL based on the metadata, not the MXF filename.

So, whenever you bring footage into MC, with RedCine-X or MetaFuze or AMA, the resulting master clips will have a tapename of filename in their metadata (visible in MC's bin columns/headings). It will look like "A001_C001_0717XY". When you make an EDL, the combination of tapename (or filename) and Start TC is what gives you an EDL that references the original R3D file. BaseLight can handle that.

In EDL Manager, you will need to use the File16 template or the Red16 template. This is an EDL template that will allow 16-character source names (classic EDL's maxed out at 8 characters). Even if the filename/tapename is venig extended at any point, you can set the EDL Manager to truncate the tapenames at the end. So you will end up with the first 16 characters, which are what you need.

This will result in an EDL that will refer to exactly those 16 characters that are needed to refer to the original R3D's.