Offline/Online on Media composer for HD finish

[nigelsmith]

Hello
I am trying to establish an Avid MC v3.5 workflow that allows for a one light with rushes and then online grading. Projects will [for now] be shot 2K using S16mm glass and mastered for Blu-ray and Digibeta. This is what I've come up with so far.

Use clipfinder and red alert for 'one light' and transcode to DNXHD36 QTs with ALE. Import ALE into a 1080 25p MC project and batch [quick] import QTs.
Offline edit [switching project to Pal 25i and using SDI mojo and SD monitor] and picture lock.

Open final sequence in Film Scribe and export XML using 'scan' as list type.
Use TestXLT to apply FS_Redcine.xls, and save as XML.

Load all project's clips into Redcine, then open XML.
Grade shots, then render to DNXHD185X QTs using the 'hash F' command to generate individual files.

Batch import original ALE clips again, and relink final edit sequence to new hi-res media. Set project back to 1080 25p, then render any effects and send ref QT to Bluray authoring software.
Finally switch project to Pal 25i and digital cut to Digibeta deck.

Simple :laugh:

Would that work ok?

Will Filmscribe ignore titles, time warps and effects, and just list actual clips used across all video tracks? If so this strikes me as a fantastic way of onlining complex sequences at 10bit HD resolution.

Any feedback appreciated.

 

[MichaelP]

This is pretty much described in the step by step guide on www.avid.com/red . Just replace REDrushes with Clipfinder - they both use REDline to make the ALE, so the metadata is the same.

Michael

 

[nigelsmith]

....

 

[nigelsmith]

Ok, so I loaded the XML file using the Redcine's Project Settings' "open" command, but now I get a "failed to load construct" message and nothing happens. :nonod:

 

[MichaelP]

REDcine needs certain metadata to do the loading of the construct. If the path name has changed anytime from the original ALE created from REDcine, then it won't work. cineXML does a re-index and creates a new REDcine XML.

Michael

 

[Christoffer Glans]

REDcine needs certain metadata to do the loading of the construct. If the path name has changed anytime from the original ALE created from REDcine, then it won't work. cineXML does a re-index and creates a new REDcine XML.

Michael

Will there be a possibility to have metafuze exporting an ALE that in the end will make an XML list compatible with RedCine? It would make a powerful workflow with Avid.

As a side note, how's work on the next version of Metafuze going? Have another feature film in talks with me as an editor and I would like to edit in 720p. Also, if an XML to Redcine is possible then it would make me first choice for this job.

 

[MichaelP]

The next version looks like early Jan/10 and does include 720p/25 in it. With more engineering resources being applied to ROCKETCINE-X and REDCINE-X, we will probably focus more effort there for full workflow rather than REDCINE which I don't believe is a priority for RED or Assimilate at this time.

We do want to provide pull list support back into MetaFuze for re-indexing and regenerating native MXF files as well as the same in the new RED tools once that infrastructure is in place.

Michael

 

[Christoffer Glans]

We do want to provide pull list support back into MetaFuze for re-indexing and regenerating native MXF files

Would that be possible with the new Metafuze? I understand the time it takes to implement this in REDCINE-X, but wouldn't it be possible to have it ready for metafuze within it's next release?

 

[MichaelP]

It's not part of the next MetaFuze, but top of the list for the follow on release. The MetaFuze in Jan/10 has RSX support, original filename to Tape, new color space, REDROCKET hardware support, 720p/25 and a few other things I can't think of off the top of my head.

Michel

 

[person]

It's not part of the next MetaFuze, but top of the list for the follow on release. The MetaFuze in Jan/10 has RSX support, original filename to Tape, new color space, REDROCKET hardware support, 720p/25 and a few other things I can't think of off the top of my head.

Michel

And when for the MAC?

 

[Rainer Fritz]

And when for the MAC?

In my opinion we dont need it. IF you have a Rocket. With Rocketcine you can render out in realtime final MXF container.... just relinking then.... with an ALE you get more metadata in....

 

[Christoffer Glans]

It's not part of the next MetaFuze, but top of the list for the follow on release. The MetaFuze in Jan/10 has RSX support, original filename to Tape, new color space, REDROCKET hardware support, 720p/25 and a few other things I can't think of off the top of my head.

Michel

I'm going to begin rendering MXF's and start editing the new feature film very soon. Is there any way to perhaps betatest the new metafuze? I'm in a frustrating situation where I probably need both real filenames and 720 25p support.

How limited am I with the current version of Metafuze? What are the online possibilites? Is it only workable with Avid DS as the online suite?

 

[MichaelP]

email me please a michael (dot) phillips (at) avid...

Michael

 

[nigelsmith]

REDcine needs certain metadata to do the loading of the construct. If the path name has changed anytime from the original ALE created from REDcine, then it won't work. cineXML does a re-index and creates a new REDcine XML.

Michael

I'm pretty certain the path is exactly the same - the original r3d files are still in the same place.
The original ALE was created in Clipfinder - could that be the problem?
nigel

 

[MichaelP]

Yes, the step by step guides says that the ALE needs to be created from REDcine as well for that roundtrip to work. cineXML will be the solution for the re-indexing and XML modification to make it work.

Michael