Welcome to our community

Be a part of something great, join today!

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 :)

updates for PC workflow?

They will be MXF wrapped DNxHD files where all the pertinent metadata will already be in the MXF. Additional metadata if desired that go beyond what MXF currently described can be exported directly as ALE and merged within the Media Composer. The latter is optional if all you want it timecode, filename, tape, etc. The ALE will have such things as RLX file used, UNC paths, etc.

Michael
 
To me this sounds more and more like the holy grail! I so much hope that it'll be out for tests in a few days. Other wise we'll have to look at another solution. But i still hope and pray. =))))
 
Yes, I agree with Henrik. Being able to batch convert to MXF wrapped DNxHD files (with audio tracks !) would be so practical on the PC side ! Come on Avid guys, hurry up !:usd:
 
Hohohoho! :w00t:

Why don't I throw out some number!

Computer: 8 core Xeon 3.2 Ghz (2x5482)
Source on 2.5TB RAID 0 (8 drives).
A 4k 2:1 R3D @ 00:01:04:23 and 25fps
Transcoded to DNxHD40 (guess they mean 36?)
Debayer Low
Burn in TC and key
Letterbox Center

minutes:seconds (rouded to closest second)

Eight good: 00:49
CPU @ 70-75%

Quarter good: 01:34
CPU @ 70-75%

Half good: 08:51
CPU @ 50-55%

Half premium: 08:55
CPU @ 50-55%

Full premium: 29:24
CPU @ 40-50%

Seems to be something funky about the multithreading. Maybe that limit is in the RED-code? What do you think about the numbers folks?

Have not taken the MXF's into the Avid yet. Will soon. And then edit something and throw out an EDL and network conform it in the eQ. :shiftyph34r:
 
DNxHD 40 is the 25fps data rate of DNxHD 36 @ 24fps.

Michael
 
MichaelP said:
DNxHD 40 is the 25fps data rate of DNxHD 36 @ 24fps.

Michael
Click to expand...

Aaaah! Okay.

You have any insight in MetaFuze and how it works with the threading? I mean why the utilization of the cores go down on some of the conversions...? Have not had the time to look to deep into it yet.
 
I'll ask. What are you transcoding from?

Michael
 
MichaelP said:
I'll ask. What are you transcoding from?

Michael
Click to expand...


You mean what red files or what kid of harddrives?

Computer: 8 core Xeon 3.2 Ghz (2x5482)
Source is on 2.5TB RAID 0 (8 drives).
Sourde red-file is a 4k 2:1 R3D @ 00:01:04:23 and 25fps
Transcoded to DNxHD40 (guess they mean 36?)
Debayer Low
Burn in TC and key
Letterbox Center
 
Might have found a bug or something. Dunno what it is really. But it seems like it cripples all the tape names for REDfiles. It removes the C in the file name so the tape name for A003_C001_071120_0001.R3D becomes A003_001_071120. That's pretty devastating once the EDL from the Avid goes to the eQ since it can't find the tape... Sure, we could manually edit the EDL's but it seems like a bug or something I'm missing out... Any clues? =)
 
How are you making the ALE to start with? Are you using yher Avid RECINE to ALE XSL file? Make sure you have the latest version (for now) on www.avid.com/red

Michael
 
MichaelP said:
How are you making the ALE to start with? Are you using yher Avid RECINE to ALE XSL file? Make sure you have the latest version (for now) on www.avid.com/red

Michael
Click to expand...

ALE? I don't do any ALE's... MetaFuze takes r3d to MXF. MXF goes in the appropriate Avid folder on the media disks and then media tool to import in the Avid. Then cut in the avid, use edl manager and the RED16 template to export to EDL. Then network conform in the eQ. :weight_lift:

Another potential bug I might have stumbled on was that MetaFuze seems to have change the timecode in the MXF's for two clips. That's why they couldn't be conformed in the eQ. And the third last clip was open on another computer and that seemed to have locked it from reading. Still investigating this though.
 
MetaFuze has not been released with native R3D support. Are you using some interim plug-in support with MetaFuze?

Michael
 
MichaelP said:
MetaFuze has not been released with native R3D support. Are you using some interim plug-in support with MetaFuze?

Michael
Click to expand...

I got it from V. After some nagging. =) We did discuss it earlier here in the thread, remember. =) It's 1.2 (Ship). Works like a charm, except the few things I wrote about here. :matrix:
 
I'll stick to my assessment - MetaFuze has not yet shipped for native R3D support for the very reasons you mention and a few more that I have on my list. ;)

Thanks for the early alpha feedback though.

Michael
 
MichaelP said:
I'll stick to my assessment - MetaFuze has not yet shipped for native R3D support for the very reasons you mention and a few more that I have on my list. ;)

Thanks for the early alpha feedback though.

Michael
Click to expand...

Oh... Early alpha. Damn. :wink: Think V also thought it was the finished product I got. If that's the case then I don't know if we dare to use it for the production as we had hoped. I guess I have to take it for a real test drive and see.

I'll send whatever bugs I find to V.
 
MetaFuze takes r3d to MXF. MXF goes in the appropriate Avid folder on the media disks and then media tool to import in the Avid. Then cut in the avid, use edl manager and the RED16 template to export to EDL. Then network conform in the eQ.
Click to expand...

hmm is it out?
are we missing something here?

Keghnan
 
It is not out. Still in development.

Michael
 
keghnan said:
hmm is it out?
are we missing something here?

Keghnan
Click to expand...

It's my bad. I thought that what I got was the final release (...since that was what I was told), but as seen it wasn't. So I might just have pissed of some people even talking about it. :unsure: So my apologies for jumping the boat on this one and talking about stuffs that I might not have been allowed to talk about. :poster_oops: If it's any comfort I can only say that this application will truly roxxor you boxxor and totally streamline the pc workflow! :w00t:

And since it was an alpha I might just chime in with a wish for the final? Would be sweet if the LUT function in metafuze would work in the R3D to MXF transcode to. :tongue:
 
Wooohooo! So the final 1.2 is out! Dunno when it was released but the build date is back in february but the folders in the zip says 2009-03-02. Been nagging on Vincent for it for quite a while but found it on their www today. =)

Some changes from the alpha regarding how it builds up tapename and so. But this new way works for us to. We add the clip name as a comment in the EDL and choose that as clipname in the eQ and choose to limit it to 16 char to get rid of the extra "_" metafuse adds.

Also seems to be some issues with the threading. It does not utilize all 8 cores to 100%. Total CPU usage is around 50-55% (dual Xeon 5482). It also feels a lot slower then the alpha version. Which I find a bit odd.

Will test more! :w00t:
 
Henrik go home have a beer ;-) , I really want to look at the tapename issue because the camroll is what I export EDL's as later in our process. Really dont want to have to change that. Looking forward to seeing results next week...

mahvo (you know who I am :-))
 
You must log in or register to reply here.
Back
Top