Welcome to our community

Be a part of something great, join today!

Register Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Metafuze 1.2 requires MC3.5?

R

richards

Active member
Joined
Mar 12, 2009
Messages
27
Reaction score
0
Points
0
Does Metafuze 1.2 require the use of MC3.5 to recognise exported MXF files?

I have an MC3.1.1 system and have exported both DNxHD40 and DNxHD120 25P clips from Metafuze, dropped them into the "1" folder on the media storage, dropped the ALE file into the bin and all I get is "Media Offline". Avid generates MDB files OK.

Interestingly, the ALE exported from the DNxHD40 clip shows the media as DNxHD120...

Regards,

Richard
 
"After importing the ALE, do you select the clips and relink?"

The relink is not finding the media either.

Anyone succeeded in using 25P clips out of MetaFuze?
 
Yes, select the clips and relink. Have you tried rebuilding the Media Databases. This has happened to me before and I ended up throwing out the MC State and the other database file in with the MXF media.
 
Still no joy after deleting the MDB files

This is just a test with only one single 30sec clip.
 
Where on your drives is the mxf file being sent? Could MetaFuze be transcoding to your C:/ drive? When you set up a transcode, the settings on the top Right allow you to browse to a location for the media to be created. Just check this is the same space that you are telling MC to relink from.
 
Oops, I just noticed your earlier post said you've dropped them into the correct folder. Let me check with the Devs on the 25P setting, I've not had to use that one yet.
 
For what it's worth, the encoding is being done on a different machine to the MC workstation.
 
richards said:
For what it's worth, the encoding is being done on a different machine to the MC workstation.
Click to expand...
That shouldn't matter. Once the files are created, Avid sees them as any other. Unfortunately, I don't have any 25P Red media on hand to test. Let me see if I can grab some off of Redrelay. In the meantime, I've asked the Devs if there are any issues with that framerate. I'll let you know.
 
I can supply you 25P media if required.
 
i don't believe you can drop the files into the media files folder and directly link to them, but need to batch import them using the ALE to basically unwrap and re-wrap them on the move from your orig render directory to the AVID media files folder. what you're trying to do won't be implemented for a while.
 
Forrest: I have emailed you FTP details.

Jason: Taking a slightly alternate route to what I have been trying, I followed the procedure outlined on page 30 of the Metafuze User manual PDF.

At Step 5 I am able to see the mxf media file in the media tool, but it will not drag into a bin.

Regards,

Richard
 
I ran into this problem myself during a test, and finally figured out it was a files ownership problem. For some reason the MXF files that Metafuze creates can't be accessed by Media Composer until you change the ownership properties on the files first.
 
We'll look into this - I have always transcoded on the windows side of my mac - copied to my mac side, dragged them into my mediafiles/mxf/1 folder, opened the mediatool, and dragged them into a bin. Done. Are the issues you are seeing from being on the same system as the Media Composer?

Michael
 
We also use the media tool to import our mxfs. And I can confirm that theres no issues with 25p. Atleast it worked for us. Doublehd red files in 25p via metafuze to mxf. Then import from the correct dir and with the mediatool. Smooth as silk. Other then mfuze not utilzing the CPU fully. =/


MichaelP said:
We'll look into this - I have always transcoded on the windows side of my mac - copied to my mac side, dragged them into my mediafiles/mxf/1 folder, opened the mediatool, and dragged them into a bin. Done. Are the issues you are seeing from being on the same system as the Media Composer?

Michael
Click to expand...
 
Jason Diamond said:
i don't believe you can drop the files into the media files folder and directly link to them, but need to batch import them using the ALE to basically unwrap and re-wrap them on the move from your orig render directory to the AVID media files folder. what you're trying to do won't be implemented for a while.
Click to expand...
This is not correct. You can create or copy the files to your media folder and relink them. There is no Unwrapping/ReWrapping necessary. If you are generating QT from RedRushes, you would Batch Import from the ALE, however, you need to be careful on how this is done if you are going to Online on DS via AFE. The tape name column gets truncated down to the first 4 characters A001. There is a utility that one of the DS guys wrote to change this to the full file name A001_C001etc. I'll ask him if it's cool to post the link here. If you are going RedRushes to MC to any other app using an EDL, you only need the 16 character template from Avid. But then who wants to sit and eyematch effects, when the Avid DS will rebuild them for you.
 
richards said:
Forrest: I have emailed you FTP details.

Jason: Taking a slightly alternate route to what I have been trying, I followed the procedure outlined on page 30 of the Metafuze User manual PDF.

At Step 5 I am able to see the mxf media file in the media tool, but it will not drag into a bin.

Regards,

Richard
Click to expand...
I got the files successfully Richard. I scanned the file in MetaFuze, created DnXHD media at 25P 140DNX to my media folder and an ALE. I imported the ALE and relinked the clip in a 25P project. I then sent the cut to Avid DS via AFE and relinked back to the original .R3D. I used MetaFuze on a PC, the same system the MC was installed on. I have to jump into a session, but later this evening I'll try transcoding on a different station.
 
cmaeditor said:
I ran into this problem myself during a test, and finally figured out it was a files ownership problem. For some reason the MXF files that Metafuze creates can't be accessed by Media Composer until you change the ownership properties on the files first.
Click to expand...
This is possible, although on my end, there is no changing of ownership necessary. I transcode the files, import the ALE and relink.
 
You must log in or register to reply here.
Back
Top