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

Pull List

MichaelP said:
I hope to have engineering parsing examples in 2-3 weeks. Send me PM for beta.
Click to expand...

Awesome.

Everyone should understand the scope of what Michael is saying MichaelP is Michael Phillips. He is one of Avid's principal product designers and is one of the chief brains behind almost everything Avid has done in the past 10 years relating to the comprehension of film and video-related metadata. He's easily one of the brightest dudes I know in the industry.

The fact that Filmscribe will be able to output REDCINE XML means that there will be a fully manufacturer-supported metadata workflow from Avid offline to REDCINE for generating a pull list that can then generate high-end DPX/TIFF output.

This is huge.

Lucas
-----
ASSIMILATE, Inc.
LA, CA, USA
 
I am setting a Mark by finding a frame and hitting "I" go forward 10 frames then hit "O". from there I save the project out and name it "project".xml. I can see in your file where to find the offsets, once I get mine to work, then it is repeatable for me to give to engineering to ensure a proper ALE translation.

Michael
 
MichaelP said:
I am setting a Mark by finding a frame and hitting "I" go forward 10 frames then hit "O".
Click to expand...

That is setting timeline in and out, not clip in/out. Clip in/out is in the "shot" tab.

Note: this is from memory, as I am not in front of Redcine right now.
 
I am doing this in the shot tab. As there is only one clip in the construct, the marks are the same in both, but I am setting them while in the shot tab.

I just found a bug - I reset the metadata overlay to a 50 point font and moved the band to the bottom of the frame - the first frame of the rendered QT wrapped DNxHD is corrupt, render for about 4 frames, then the frame sticks for the remaining 6. Also, the timecode frame count in the overlay is all pixelated. I will email to Lucas.

Michael
 
MichaelP said:
I am setting a Mark by finding a frame and hitting "I" go forward 10 frames then hit "O". from there I save the project out and name it "project".xml. I can see in your file where to find the offsets, once I get mine to work, then it is repeatable for me to give to engineering to ensure a proper ALE translation.

Michael
Click to expand...

What Nick said...

The place to set In and Out for individual clips is in the numeric In/Out in the Shot section.

Lucas
 
Thanks guys. This is an amazing community and I have no doubt that there will be a workable solution soon. Hopefully soon means in a couple weeks since we have a fairly lengthy project shooting next week :-)
 
Sorry, can't get it to work... I'll keep trying.

Michael
 
luki said:
The fact that Filmscribe will be able to output REDCINE XML means that there will be a fully manufacturer-supported metadata workflow from Avid offline to REDCINE for generating a pull list that can then generate high-end DPX/TIFF output.

This is huge.
Click to expand...

It would be much more huge if Redcine was also capable of generating truncated R3d files based on the pull list.
 
MichaelP said:
Sorry, can't get it to work... I'll keep trying.

Michael
Click to expand...

Michael,

Steps:

1) Click "New" in Player -> Project just to start with a blank slate.
2) Load a single R3D file

Let's say the length of the R3D file is 622 frames. In that case, in Player -> Shot, you will see In = 1, and Out = 622.

See attached file "NoHandles.jpg." The XML output for this Library is the attached "NoHandles.xml" in the ZIP.

3) Edit so that In = 50, and Out = 300.

See attached file "Handles.jpg" The XML output for the edited file is the attached "Handles.xml" in the ZIP.

Download the ZIP and the 2 JPEGs.

Does that help?

Lucas
 
MichaelP said:
Sorry, can't get it to work... I'll keep trying.

Michael
Click to expand...

Lucas has already "sort of" described this, but....

You have to use the entry fields themselves. If you drag the sliders in them, you'll see how it works.
 
OK, I got it to work. My error. It was the values in the fields below the timeline... duh! Now that I see it work, this brings up another feature request; can the frame counter burn-in keep the count from the original master r3d file? since this is only a pointer to a subset (or subclip in Avid parlance) keeping metadata consistent would help.

Also, per mmost's request to create new r3d file would be handy, but you need to ensure that you keep a parent/child relationship going because the file name will look the same and the _001 extension is being used for shots longer than 2GB in size. And if someone makes multiple subclips that span each other and each one has a different color treatment and or reframe to it... well you see where I am going with all this...

Michael
 
MichaelP said:
OK, I got it to work. My error. It was the values in the fields below the timeline... duh! Now that I see it work, this brings up another feature request; can the frame counter burn-in keep the count from the original master r3d file? since this is only a pointer to a subset (or subclip in Avid parlance) keeping metadata consistent would help.

Also, per mmost's request to create new r3d file would be handy, but you need to ensure that you keep a parent/child relationship going because the file name will look the same and the _001 extension is being used for shots longer than 2GB in size. And if someone makes multiple subclips that span each other and each one has a different color treatment and or reframe to it... well you see where I am going with all this...

Michael
Click to expand...

Cool - glad you got it to work. Frame counter burn-in - good idea.

The new internal builds of REDCINE automatically concatenate the _001, _002 clips into one clip in the library, so I don't think the whole subclip thing will be an issue going forward.

Lucas
 
MichaelP said:
Also, per mmost's request to create new r3d file would be handy, but you need to ensure that you keep a parent/child relationship going because the file name will look the same and the _001 extension is being used for shots longer than 2GB in size. And if someone makes multiple subclips that span each other and each one has a different color treatment and or reframe to it... well you see where I am going with all this...
Click to expand...

I can. However, the request was made from the point of view of using Scratch for conform and finishing. In that scenario, the file relationships are not all that relevant as long as the truncated file carries the original metadata, since Scratch references that directly. Color treatments are also not relevant as this would likely not be done in Redcine, but in Scratch - and since the color space would likely not be the same as the offline clips, well, you get the picture.

To tell you the truth, my biggest gripe with the current release of Redcine is that it seems to always refer to the "edge code" rather than the time of day time code in its exports. This is not the case in the most recent versions of Scratch, in which you can select which time code you want to use.
 
Offhollywood said:
Ian, do you really think that list is done ... :devil:

What you should post is a list of what YOU want it to parse.
Click to expand...

I think I want to parse everything. In all seriousness. And it won't be a big deal to add new tags as things develop.

Lucas is right, once you have a framework setup properly parsing from FCP to Redcine is looking to be pretty easy, I'm still assembling the right set of tools, but I'm looking at maybe a day of actual coding if you are using the right tools, and so are automating some of the tools in Redcine with FCP tags, such as shot reframing.

It's taking you work back into FCP though that takes some heavy lifting Mark. i.e. you've got a pull list in Redcine, and pulled footage... now what.

No wait, don't tell me.... buy Scratch. :wink:

Ian
 
ibloom said:
It's taking you work back into FCP though that takes some heavy lifting Mark. i.e. you've got a pull list in Redcine, and pulled footage... now what.
Ian
Click to expand...
Yes, but I don't think that lifting is actually that heavy. If you reprocessed your final media (your "on line") with your re-framing - you can just use the EDL from the project and conform in FCP or Premiere or Scratch or even Fusion ...
 
I agree that for final conform the pull list generating new r3d files will not have the same issues as pulling dailies for editorial, but all the same, any subset of an original r3d file should maintain the same metadata and not start counting over - right now it appears as the frame counter and the individual clip timecode both start at 0 and 00:00:00:00 respectively.

A question I have on the spanned 2GB files is when referencing a source in an EDL or XML, should it always refer to the original file and let the timecode determine whether it jumps to the second file (assuming 2 files of 2GB each)? Or should a single take refer to the original file name with _001 and _002 when referencing back to the original r3d? It's a matter of retaining history of the file through all its permutations that I am trying to anticipate.

Michael
 
You must log in or register to reply here.
Back
Top