Hi all

I'm testing the suggested RED workflow from the Avid/RED PDF.

I went through MetaFuze to export as DNxHD MXF. Loaded in Avid, Opened in film scribe and used the suggested settings to preview my XML. That's when I get this error - ACX_UNEXPECTED_CLASS_ID, expected:Edgecode

I tried to Google it and nothing...

Can anyone please help?

What kind of effects do you have the in the timeline? Any nested type effects? Also, the step by step guide states that MetaFuze is used to finish in DS at this time due to the TAPE based metdata used in the transcode. How are you planning on finishing?

Michael

Hi

I'm now down to one master clip sitting on the timeline. no edits, trims, effects and the such...

I guess it's a bug or an install error. No one else is getting this error?

The error repeats it self with non RED footage as well. But only when using the XML template. Other templates work fine. I tried to edit the XML file given by Avid on the RED page, but only got more errors.

My goal is to go back to RedCine through XTrance and export DPX sequence for my grading session.

Thanks

Hi again

The error went away when I replaced the XML posted on the Avid site with the original XML template file that comes with version 25.0.1. But now XTrance doesn't translate the file correctly and I end up with a useless RedCine project file.

I tried using Avocoda CineXML, but it's only for 32bit systems, mine is XP64.

I thought this workflow is locked by now. Is there no way to create dailies in MetaFuze and still be able to go back to RedCine for DPX/TIFF ???

Tanks

MetaFuze uses the file name inside the R3D as given to us via the SDK. Unfortunately this is not the same ID used at the desktop level (last two characters). So at stated in the guide - MetaFuze v1.2 is really for an Avid MC to Avid DS workflow since DS uses the same implementation of the SDK.

The workaround for v1.2 of MetaFuze is once the files have been opened in Media Composer, to duplicate the NAME column into the Camroll or Labroll column before changing it to something more editor friendly (like scene/take). From there you could create an EDL based on either of those columns.

MetaFuze v2 will add this directly to the camroll column so the workaround is no longer needed. We should also be getting an update to the SDK that persists the directory level name into the header for a future release.

Michael

Thanks for the reply.

From what I understand, with Metafuze 2 we still won't be able to edit MetaFuze generated dailies and send to RedCine.

So if my setup is based on Windows machines, my options will still be very slow or very expensive.

Bummer.

I don't think I said that. I said with MetaFuze v2, the filename is carried in the Camroll column and that can be used in the XSL instead of the Tape source and the workflow would be the same as what you had before.

I also said that I don't think we will see much development on REDCINE as done by Assimilate with RED having announced their own version called REDCINE X which remains to be seen as to what it will support as an input file.

Michael

Hi

Let me explain how I came to those conclusions.
My ideal workflow would be to use MetaFuze for creating dailies as it is much faster then RedCine. And use RedCine for DPX exports for conform and coloring.

The FilmScribe XML template I've downloaded from the Avid site does not work on 3 different machines I've tested. Those were two XP 64 systems and one XP 32, all running Avid 3.5.1 and FilmScibe 25.0.1. They all generated the same error (the title of this thread). So my only option is to use the built in XML template in FilmScribe version 25.0.1, which results in a wrongly formatted RedCine (3.1.8) project file, when going thru XTrance using the FS_RedCine xsl given by Avid.

As of right now, if I choose to create offline media in MetaFuze (including future version 2), there is no way to create an XML that is compatible with RedCine. The only option is to create an EDL, and to take advantage of that EDL I would have to use Scratch or similar products (the expensive way).
I can create the dailies in some other app, RedCine for example, and then round trip to it after the edit is done (the slow way).
But there is no way to enjoy both worlds - dailies in MetaFuze then DPX in RedCine, right?
You're also saying that maybe RedCineX will be able to use that EDL, but that remains to be seen...


Please confirm my assumptions. Also I would like to find the reason and the fix to that FilmScribe error (which accurs in non RED footage as well).


Thanks
O

If you base your assumptions based on what you are experiencing, then you can certainly draw the conclusions that have you reached. But - since it was clear that the v.1.2 version of MetaFuze was released with the caveat that it was to be used for conform in Avid DS, there was no expectation that any of other workflows would be supported.

That does not mean it will stay that way moving forward, features and bugs are addressed and this is one that with the ALE metadata addition in v2 of MetaFuze will give us the grounding to create an XML that uses the file name as the source as expected by these other third party workflows. It will still not address moving the files to a different UNC path but should get you back to parity with previous workflows.

Any changes that may be required of REDCINE is what I was questioning moving forward since the product itself "may" be on hold considering RED's announcement of REDCINE X. And that, as you say, remains to be seen since we won't know what it is till the mass population sees it. We get no early samples, developer insight, or consult on what might be needed. We remain to be delighted with the rest of the world, then will work towards integrating it. The same goes for RED ROCKET.

So stay tuned - we will look to see what the XML issues are and see what can be done sooner than later.

Michael

Thanks

Will stay tuned.

Hi

Any news on that annoying FilmScribe error?

No one else is getting it?

Thanks...

(WinXP x64, Avid 3.5.1, FilmScribe 25.0.1)