MetaFuze 1.2 files do not work

[Chris Burg]

Hi..

For an upcoming RED edit job I gave MetaFuze 1,2 today a try…. I had no Luck..

…


What I get when I import the ALE is just “Media offline” – Relink does not work nor the import with the MEDIA TOOL” Basically I made the same experience as richards has described here…

http://www.reduser.net/forum/showpost.php?p=386938&postcount=24

Even so I tried it with 24p R3D files



We are working on a MC 3,5 / VISTA 64 Ultimate PC.

What can I do? -

Will MetaFuze 1,3 solve this problems? Where can I get it….

When I do the job with REDrushes – I would need a MAC – and do I understand it right that the QuickTime-files form REDrushes have to be once more transcoded by the Avid importer to a mxf file?

thanks for answers...

 

[MichaelP]

Copy the MXF files from MetaFuze into the Avid MediaFiles/MXF/1 folder. Open MediaTool and drag clips to bin. Edit from there. ALE is not a requirement.

Michael

 

[Chris Burg]

Copy the MXF files from MetaFuze into the Avid MediaFiles/MXF/1 folder. Open MediaTool and drag clips to bin. Edit from there. ALE is not a requirement.

Michael

Thanks for the response…

But MediaTool does not like to open the mxf file I coded with MetaFuze. So just dragging the clip to the bin does not work at all on my computer ….:yikes:

 

[richards]

Hi Chris,

I could never get the "drag the clip to the bin" to work (Vista 32), but after unchecking some boxes in the Relink tool, I was able to use the ALE.

I think either "Match case when comparing tape names" or "Allow relinking to source tapes with compatible rates", I can't recall.

 

[MichaelP]

Direct drag of MXF file to the bin is not supported (I know, I know, it should be). You need to drag the clip to the MiedaFile folder first before launching the app, then go to the mediatool and drag to bin from there.

Michael

 

[richards]

Unless I am misunderstanding something, I already have the MXF files in the "1" folder on the media storage.

I then open the media tool, locate these files and attempt to drag them into the bin from the media tool - nothing happens.

 

[Chris Burg]

You need to drag the clip to the MiedaFile folder first before launching the app, then go to the mediatool and drag to bin from there.

Michael

That is exactly what I did... You saying it should work… but on my computer it does not…

I could never get the "drag the clip to the bin" to work (Vista 32), but after unchecking some boxes in the Relink tool, I was able to use the ALE.

I think either "Match case when comparing tape names" or "Allow relinking to source tapes with compatible rates", I can't recall.

Thanks for the hint… but does not work for me,, just tried it…


I got the feeling that coding the file on VISTA does something to the mxf
Here you find my mxf file:

http://rapidshare.com/files/229200669/red-test.zip.html - 30MB -

could you try if the import works on your machine?
Thanks a lot

 

[richards]

Hi Chris,

I (and the Avid suites are pretty tied up at the moment. I'll see what I can do, but it may be a day or two.

 

[Chris Burg]

thanks richards


Hi Michael

What do you say to the mxl file I posted… Does it work for you…
Do you have a idea what I could do now… ????

 

[MichaelP]

If it's a shot of a blurry lookng something (rock outside a dirty window?), then it works fine for me on Mac running v3.5.

Michael

 

[Chris Burg]

Thanks Michael…


I Just got it work as well….

“Relink only media from the current project” has to be unchecked in the Relink Tool/

- or in MediaTool the button “All Projects” has to be activated.. then all works perfect…

Michael you maybe want to ad this detail in your guide… I blockheads like me needs same time to figure it out…

All the best

 

[MichaelP]

Good point. I don't use the ALE method. I go to the MediaTool, sort by date, and drag clips to bin. I will update the ALE method for the next round when we get all the metadata into the ALE. If you give your MXF files a project name in MetaFuze, then you will have an easier time with the relink.

Michael

 

[jolifilm]

Tks for that post, I got the same problem
Can't wait for the V2, hope it will be fixed