Is DNxHD out of RedCine working yet?

[brandon thomas]

Haven't looked into the avid stuff for awhile.. but can anyone tell me if you can export DNxHD out of RedCine yet?

thanks so much!

[MichaelP]

REDCINE has always been able to export DNxHD 175x since it defaults to the first codec it sees in the stack. The issue has been that the Avid DNxHD codec had a bug that was returning noise rather than picture. That was fixed with a release of the v1.10 QT codec available from the Avid Knowledge-base or from www.avid.com/red pages. Click on the Avid Resources Tab.

Meanwhile, REDrushes has added the ability to transcode to all DNxHD flavors with its latest release. That implementation has not yet been shared or implemented that I know of with REDCINE at this time.

Michael

[brandon thomas]

awesome thanks

[Bruce Allen]

Meanwhile, REDrushes has added the ability to transcode to all DNxHD flavors with its latest release. That implementation has not yet been shared or implemented that I know of with REDCINE at this time.


I emailed REDCINE developers recently about this, asking what was up. They claim Avid wants to charge a license fee - that's why it hasn't been implemented.

Can you confirm if this is correct? Maybe things have gotten a bit confused. Thanks Michael.

MC 3.0.5 is solid as anything by the way and super-fast. Zero crashes or issues. Same project works flawlessly on both Mac Laptop and my cheap PC desktop. Love it. That's how software should be.

Bruce Allen
www.boacinema.com

[Michael Lindsay]

MichaelP may correct me but I believe:

Avid does not charge for quicktime wrapped files. MXF is another thing..

Michael Lindsay

[MichaelP]

Correct. There are different levels of DNxHD licensing. In order to create optimized native MXF wrapped DNxHD directly, that is a license fee. If they were to create QT wrapped DNxHD like REDrushes, then it using the DNxHD QT codec which is free.

MetaFuze is coming soon...

Michael

[Bruce Allen]

Okay great. Ball back in REDCINE developers' court.

Hey, just noticed that even Blender (free open-source 3D app) can make DNxHD36 quicktimes.

Bruce Allen
www.boacinema.com

[Henrik Cednert]

MetaFuze is coming soon...

Michael

How soon is soon man (like 1-2 days, 1-2 months, 1-2 years)? :construction: Can you say anything how it will change the current Avid/RED workflow? Will we go from R3D directly to MXF with it? :detective2:

[MichaelP]

I want to be more realistic with product release dates.... ;)

My guess, barring any unknown issues is that we should see something usable in 4-6 weeks. Although users should be aware that the SDK does not support audio so neither will MetaFuze in this version. And yes, it will change the way you work on a PC since it creates native MXF wrapped DNxHD directly with burn-in, aspect ratio control, 1D and 3D LUT import, as well as support for RLX, 4K, 2K, 1K extraction, etc... This is a dailies creation tool. Information on the current version can be found at www.avid.com/metafuze. This is a free application so I can give more details about it over quarter boundaries without breaking any laws for public companies... ;)

Michael

[Henrik Cednert]

This is brilliant news for us! :love:

But the version available on the website, is it like daily builds or is that the old old version that Vincent demoed here on location back in February...?


I want to be more realistic with product release dates.... ;)

My guess, barring any unknown issues is that we should see something usable in 4-6 weeks. Although users should be aware that the SDK does not support audio so neither will MetaFuze in this version. And yes, it will change the way you work on a PC since it creates native MXF wrapped DNxHD directly with burn-in, aspect ratio control, 1D and 3D LUT import, as well as support for RLX, 4K, 2K, 1K extraction, etc... This is a dailies creation tool. Information on the current version can be found at www.avid.com/metafuze. This is a free application so I can give more details about it over quarter boundaries without breaking any laws for public companies... ;)

Michael

[Henrik Cednert]

mmmkay... I couldn't resist... I installed the version on the webpage, 1.0. Does not to be any RED support in that. But I must say that I like what I see. It have grown a lot since we got it demoed in February! :w00t:

Will try to pull some strings and see if there's a beta one could test. :shiftyph34r:

[MichaelP]

No RED support in the current shipping version. I will let people know when there is something. Please sign up for the update email we have on avid.com/red if you haven't already.

I am working with Assimilate to see if there is a better way to work between REDCINE and Avid via MetaFuze which would solve a lot of problems and potentially get to a solution faster than dealing with a QuickTime interim format.

Michael

[Henrik Cednert]

I should be on the beta list by now. :red_bandana: :w00t:

We will do the offline editing in Avid and online in eQ Pablo. So far I've only tested: R3D => RedRushes => DNxHD/ALE => Offline => EDL (Red16 template) => eQ. Had some issues in the eQ and are waiting for some replies from quantel. But it seems like a doable workflow.

But if I understand it correctly we could go: R3D => MetaFuze MXF => Offline => EDL => eQ.

Which sounds even better to me. =)

Not really following on what you mean with working between REDCINE and Avid via MetaFuze. Isn't the idea with metafuze that it would make like redcine a tad obsolete? :umm:

Sorry if I ask stupid things. but I'm at the point where probably most of you guys have been regarding red-workflow... A bit overloaded with info and preeeeeetty lost. :cold:


No RED support in the current shipping version. I will let people know when there is something. Please sign up for the update email we have on avid.com/red if you haven't already.

I am working with Assimilate to see if there is a better way to work between REDCINE and Avid via MetaFuze which would solve a lot of problems and potentially get to a solution faster than dealing with a QuickTime interim format.

Michael

[MichaelP]

Setting up source and target Gamma, one light type color set up, crop, scale, etc, can all be done in REDCINE. MetaFuze is a transcode engine that can take all the information as metadata and create MXF wrapped DNxHD. In some cased, direct transcode via MetaFuze may be great, in others it may not. Having a link is important for some productions.

And we all still need audio to work.


Michael

[Henrik Cednert]

Aaah! Gotcha! :matrix: From what I can make out from the tests I have done in MetaFuze, and kinda assuming that the functions now in MetaFuze will be available in next version, I think the LUT function will fill all our needs for the offline editing. Now we just have to work with quantel to get the conform to work. :ninja:

Do people use MetaFuze for their P2-material to? Or how do people prefer to work with their P2 material when doing offline. Would be sweet to kinda have one workflow that "kinda" works for "it all". But that might be a far distant dream. :umm: But MetaFuze could very well be the dream fulfiller. :biggrin:


Setting up source and target Gamma, one light type color set up, crop, scale, etc, can all be done in REDCINE. MetaFuze is a transcode engine that can take all the information as metadata and create MXF wrapped DNxHD. In some cased, direct transcode via MetaFuze may be great, in others it may not. Having a link is important for some productions.

And we all still need audio to work.


Michael

[Agustin Goya]

Hi Michale! Coud you tell us if Metafuze will be able tu run una a render farm environment?
It would be great to have the ability to set up a render farm for Avid workflow.

[MichaelP]

Two questions:

1. Render Farm. MetaFuze can have scripts and XML written to send transcode jobs to separate CPU's for rendering.

2. P2. P2 uses the same MXF metadata wrapper as Avid and the products support the AVCI and DVCPRO codecs naively so there is no need for a transcode. For P2 workflows, see www.avid.com/p2

Michael

[Jörgen Persson]

Two questions:

1. Render Farm. MetaFuze can have scripts and XML written to send transcode jobs to separate CPU's for rendering.

2. P2. P2 uses the same MXF metadata wrapper as Avid and the products support the AVCI and DVCPRO codecs naively so there is no need for a transcode. For P2 workflows, see www.avid.com/p2

Michael

Intriguing. This XML you mention – can it be designed as a pull list for generating Avid MXF from R3D for online?
Will an Avid scan list XML automagically be interpreted as a pull list?

If not - consider it a feature request. :)

[MichaelP]

Maybe... looking into it as we dig into the SDK. But shouldn't be that hard to do.

Michael

[Henrik Cednert]

Sweeeeeeeeeet! :w00t: Anything commandlineish can basically be managed with an app like Smedge. :love: Distributed rendering of R3D to MXF! :) On the other hand I guess that's already possible with the current converters that can be controlled from commandline, but now we're talking MXF baby! :w00t:

[criminallawyer]

hi,
REDCINE has always been able to export DNxHD 175x since it defaults to the first codec it sees in the stack. The issue has been that the Avid DNxHD codec had a bug that was returning noise rather than picture. That was fixed with a release of the v1.10 QT codec available from the Avid Knowledge-base or from www.avid.com/red pages. Click on the Avid Resources Tab.
Meanwhile, REDrushes has added the ability to transcode to all DNxHD flavors with its latest release. That implementation has not yet been shared or implemented that I know of with REDCINE at this time.