Welcome to our community

Be a part of something great, join today!

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

Media Composer 2.8 PC Workflow

Carlos Robles

New member
Joined
Dec 11, 2008
Messages
3
Reaction score
0
Points
0
So weve been trying to figure out an efficient workflow for us and have been running into a few walls. First we tried RedCine but the DNxHD quicktimes would either be black or have some sort of digital snow. Then we decided to use RedRushes on a mac to make the ALE and DNxHD files and transfer them over, that worked up to the point where we do the Batch Import, at this point I have to point every clip to its corresponding quicktime manually, it cannot find the files automatically, the clips in my bin have -P infront of all of the clip's names ex. -PA006_C004_080618.mov and after importing them they are not "fast importing" they are capturing like any regular quicktime would.

Is this a 2.8 limitation?
 
Also, after editing, I create an EDL with the Red16 preset, but the Filmscribe version I have is older than what the Workflow PDF indicates. Do I need an EDL AND an XML or will the EDL do? Im going to DS in DPX next.
 
Most of the RED workflow solutions are based on changes in the 3.x world. I believe that the batch import for multiple files was not working in that release.

When ready to do a conform, the EDL 16Char template will work in your version. You would need to go back to the Mac and use Monkey for EDL workflow. If you update to the v.3.1 release, then you can use XML and cineXML as a solution to create DPX files.

Michael
 
do you happen to know what could be causing the black QTs out of RedCine? We've updated our codecs to 1.10. We tried encoding to QT Animation codec and that worked. Right now were making the DNxHDs in Apple, transferring to the PC to edit, then back to the Apple to create the DPXs and then to Flame or DS.
 
I don't know what would cause the black frames if the codecs are loaded. Could be a QT version issue itself.

Michael
 
Hi Carlos

I had the same problems a few days ago.
I just started too look into a workflow for our company.
(big posthouse with: neg lab, telecine, avid, finlalcut, duplication/transmision masters, 3D, web...)
I'm setting up a Digital Lab to provide R3D>QT/MXF for offline, and then the R3D>DPX from a edl.

I found that Monkey is an excelent app. One big problem that I experience from the current DiT-company is that the offline edl's doesn't match in reelname to the DPX's or folder structure I get from them.
Monkey has that great tool that outputs a new edl with propper reelname. Its excelent!

Regarding the black renders:
I had the same problem with rendering out ProRes-files... After a lot of messing about with reinstalations and headake, I realized that I din't have the codec installed.
Probably the same with your problem.

Regarding offline on Avid:
I got the same problem with having to link each file. today actualy.
Found the answer in RedRushes under the "meny" (top or the monitor next to "apple, File, Edit) QT Wrappers/Options/No Resolutions Ext (_F,_H,_M,_P)
check that one. Should fix it.
Make sure to delete the "old" ale. if you just overwrite it it adds this new setting to that file so instead of having 10files with _P... you instead get 10files with _P + 10files without (inthe ale I mean)

You might be able to help me:
I'm trying to import the DNxHD36, that works fine, I first import the ALE into a HD project, change the setting to Pal25p and then do a batch import, select one file and everything gets found.
But!
How do I do to send this project to my client?
Should I do a "Consolidate/Transcode" or can I just export the clips as mxf's and send to my client?
I want to give my client a project in PAL DV 25P 420 MXF (or something els sometimes)
the reason for that is that a lot of clients might prefer to work in a known workflow, being DV, maybe cus they have old hardware or just plain ignorance.

And what if I send a project to a client the first day, what do I send the next day? The same project again with the new footage? or just the new MXF's?
How do a editor import MXF's into a project? Is it enough to just send the MXF's. or should I include something els aswell?

Apreciate any info anyone could give me.
/carl
 
Back
Top