Welcome to our community

Be a part of something great, join today!

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

Quick Turnaround PC Only Workflow

F

fiendish

Active member
Joined
Apr 4, 2008
Messages
32
Reaction score
0
Points
0
Hi all,

Have read these forums for some months with great interest but now have to do my first Red job on the Avid. I've read much about the various ways of doing things but in this particular case, I'll have no access to a Mac. I do however have an xw8600 with dual quad 3.0 ghz and 12gb RAM.

To add to the excitement, I'll have just 24 hours to get the footage ready to cut. But on the plus side, they hope to shoot around 30 mins only.

Is Metafuze the way to go? It seems like 1.2 has number of issues. Any opinions would be gratefully appreciated!

Ollie
 
You can also use REDcine. What is your finsihing mastering deliverable going to be in the end?

Michael
 
Hi Michael,

The project in question is a number of sponsorship spots. My final deliverables will be either be 1080 TIFFs or some kind of uncompressed quicktime.

Would Redcine be a faster option than Metafuze? The latter does seem very slow. And it's handy to do a one light in Redcine.

Ollie
 
In my opinion, there is no one "perfect" application yet in the "free to low cost" as everyone on the market today has unique strengths and weaknesses when compared to each other for a particular workflow - even on Mac which as several more options due to the availability of REDline and the R3D QT component. Solutions are improving every day so that is the good news and this part of the process is getting exciting as the solutions become more robust and feature filled.

For PC, as mentioned, it is more limited at this time. In the "free" category you have REDcine or MetaFuze. MetaFuze has its known limitations which are being addressed for the next release where performance is one of them. But Metauze does support an RLX as created by RED Alert should you want to apply a color correct or look to the images beforehand.

REDcine is much more robust for color and image manipulation beforehand as it is a direct descendant of a very well respected DI color solutions; Scratch.

Since it seems your final master is 1920x1080 then creating dailies at that resolution is the way to go - use REDcine to create the QT wrapped DNxHD with all the color manipulation and crop/scale desired for the 1920x1080 frames.

You may also want to look at a straightforward SOURCE of REDspace or RED-RGB with a REC709 out since HD is your final deliverable and you can do all your color correction in Symphony. In this scenario, you are lookng to preserve the full range of what was shot into your destination color space of REC709.

The next version of MetaFuze addresses the performance and batch transcode weaknesses of v1.2.

Michael
 
Very many thanks Michael, that's what I was beginning to think.
I wasn't sure what you meant by your final point though...

You may also want to look at a straightforward SOURCE of REDspace or RED-RGB with a REC709 out since HD is your final deliverable and you can do all your color correction in Symphony.
Click to expand...

Do you mean setting the colour space within Redcine to REC709?

Thanks

Ollie
 
Yes... just a suggestion as to how much color work you wanted to do within REDcine versus a color correction in Symphony.

Michael
 
Yes indeed. So if set my colour space to 709, do my one light, export, and then I can further colour correct within MC. I take it I'm still stuck with DNXHD 185 for export?
 
If using QT for Avid correct. You can always export TIFF and import as uncompressed HD in Symphony. But correct on the REC709 for the output gamma. If going the TIFF route, you could export full RGB range, import as such in Symphony and deal with levels there, or have Symphony do the RGB to 709 upon import. Try a few shots to see which one works the best for you and your images.

Michael
 
DS 10.1.1 would fit the bill nicely.... is the 45 day free fully functional software trial still on offer?

at half premium i see around 18 fps.. so 30 min of footage would take about 40 min to be ready to edit in HD

just a thought ;-)

d.



fiendish said:
Hi all,

Have read these forums for some months with great interest but now have to do my first Red job on the Avid. I've read much about the various ways of doing things but in this particular case, I'll have no access to a Mac. I do however have an xw8600 with dual quad 3.0 ghz and 12gb RAM.

To add to the excitement, I'll have just 24 hours to get the footage ready to cut. But on the plus side, they hope to shoot around 30 mins only.

Is Metafuze the way to go? It seems like 1.2 has number of issues. Any opinions would be gratefully appreciated!

Ollie
Click to expand...
 
I was referring to REDcine exporting TIFF instead of QT wrapped DNxHD. That way you could make uncompressed HD 10 bit when importing.

Michael
 
Thanks Michael, yes I realise that, was referring to Dermot's idea of using DS.

Have been playing with Redcine for the last 24 hours. Blimey, it's buggy as hell! Lots of not saving projects properly, loosing resize attributes and worse crashing just before render, almost all the time! This was on Vista 64 and the Windows 7 RC which I know are totally unsupported but other forum members seem to have it working with them. I've now gone back to testing on good ole XP 32 bit to see how that fares.

Have also had no luck with the demo of CineXML. A very simple sequence, just 3 cuts from 3 clips, either refuses to load constructs or only loads 2 clips! weird.
 
fiendish said:
Have also had no luck with the demo of CineXML. A very simple sequence, just 3 cuts from 3 clips, either refuses to load constructs or only loads 2 clips! weird.
Click to expand...

How did you create the dailies for the offline?
cineXML doesn't support the MetaFuze workflow for the moment because of difference in the tracking of r3d filenames.
REDrushes ALE, Metacheater ALE and Redcine XSL transformed ALE is supported.

Also the Red SDK is 32 bit for Windows so we haven't compiled a 64 bit version of cineXML (yet).
 
Hi Jorgen,

It was a Redcine XSL transformed ALE. But I did run cineXML under Vista 64. I also have Win XP 32 bit at my disposal, should I try it under that?

Ollie
 
fiendish said:
Hi Jorgen,

It was a Redcine XSL transformed ALE. But I did run cineXML under Vista 64. I also have Win XP 32 bit at my disposal, should I try it under that?

Ollie
Click to expand...

Please do.

And feel free to contact me if you run into any problems.
Remember that the new trial version of cineXML needs the latest Redcine (v3.1.8) for the XML to work.
 
So after slow processing through lovely Redcine my 10 sec spots are cut and ready for conform. I created ALEs using the Redcine XLST method and edited using subclips. When I came to using Film Scribe to make an XML for Redcine however, I noticed that it the 'Source' field containing the .R3D path is empty in the resultant XML. Within MC though, the subclip correctly shows the source.

Anyone have any idea why this could be? in this instance the sequences were very simple so matching back to source was straight forward and gave me an XML that worked properly, but it could very tedious in future!
 
Sis you make a SCAN list or an ASSEMBLE list?

Michael
 
What version are you runnning? There was a subclip issue a few versions back.
 
This is the Film Scribe that comes with 3.5.1.
 
You must log in or register to reply here.
Back
Top