Welcome to our community

Be a part of something great, join today!

  • 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 v2.0 now available!

Color science, 720 25p output, ability to choose redcode raw and redlog instead of just 709 should be on the list for coming update?

Another thing. Metafuze exclude the last letters in the filenames. This screws up the possibility to work offline and then go through cineXML back to redcine.
If metafuze ONLY works for online with DS then it's not a goodworkflow option.
Metafuze must support other offline-online possibilites. Especially keeping the filenames intact so EDL's and XML's show correct info.
 
These are planned. The last two letter issue is one we have been waiting for a change in the SDK that actually persists the same file name inside the file and not just at directory level. When v2 was being done, it was not in the SDK that way. The two unique letters is something being done at at the camera level for the file naming to eliminate the chance of creating same file names. Once that is done, then MetaFuze will inherit it for the naming process. It will also benefit other tools in that you can do a "heal" process in circumstances that the original file name gets renamed.

The latest MetaFuze does put the original filename in the Camroll colun so you can generate lists based on that as source instead of tape to support the other workflows.

Michael
 
Ok, having an annoying workflow issue with Metafuze 2.0.

Offlined RED footage in Media Composer in DV25. Export Master XML and constructed my sequence in REDCine and rendered out 10 DPX Log files and sent that over to a baselight system with a straight CMX 3600 EDL for color grading. Asked them to render me out the color graded footage as a new continuous DPX sequence with metadata embedded. Loaded the DPX sequence into Metafuze 2.0 and started a transcode to DNX 175X (the idea being to conform online and render out a Quicktime file or something for output. Problem is, metafuze gives each transcode event the same clip name because it comes from the same DPX sequence originally, which causes it overwrite the files it creates over and over again. So now I have to go through 200 transcode events and increment a 001, 002, 003 at the end of each so that it works properly. Am I missing something?
 
none yet - making some test material for engineering.

Here is some additional info.
We have a problem doing RED->AVID conversions through MetaFuze.

The problem is that in long length clips, about 6 minutes or longer, there is a noticeable drift in the audio synchronization.

At the beginning of a clip, everything is in sync; by the end it is off by a few frames.

I believe this problem exists as a result of decimal point rounding on the frame rate. Here is how I made that determination.

Step 1: Used Metafuze to generate an ALE and MXFs of a 17 min 47 sec clip shot on the RED camera at the 23.98 frame rate setting.

Step 2: Imported ALE into AVID and relinked footage.

Step 3: Went to 16 min 47 sec of the clip and split video layer. By eye, we slid the video layer back toward the beginning of the timeline until audio appeared to be in sync.

Step 4: Made note of how many frames we had to move the video to restore sync; in this case, 4 frames.

Step 5: Math: 17 min 47 sec = 1,067 Seconds, 1,067 x 23.98 = 25,586 Frames, 1,067 x 23.976 = 25,582 Frames, 25,586 - 25,582 = 4 Frames

make sense?
 
UPDATE to above post:

Just used Clipster to create the MXF's and ALE from same clip and it remains in sync...so the issue seems to be isolated to Metafuze.

my .02-- it looks like Metafuze is interpreting the metadata in the R3d literally as 23.98 instead of 23.976
 
doesn't sound like that since the previous post indicates have to remove frames to keep sync. 23.98 is faster than 23.976 so to keep sync frames would have to be added.

Other than this scenario, I haven't heard of any sync issues - anyone else having problems?

Michael
 
Several people confirmed sync issues earlier in the thread, you said you were working on it. It only happens on long clips. I can duplicate the problem consistently here.

Have you tried any long clips?

UPDATED:
Tested MetaFuze conversion with a longer file.

Audio sync drift becomes noticeable at about 6 minutes; around a frame off at this point.

By 25 min 31 seconds into the file, video is outpacing audio by 8 frames.

Again, this only happens with MetaFuze. I can do the exact same transfers in Clipster w/o any sync issue.
 
Back
Top