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

And speaking of consistency, another area which could be considered a feature request is the age old issue of counting 0 or not as first frame when dealing with whole frame counts. Whatever is chosen as the default should be consistent throughout. Right now setting an IN on the clip is +1 form what is burned-in on the overlay.

Michael
 
MichaelP said:
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
Click to expand...

I would love the answer to that as well. I hope that it always references the original file.

I must assume that based on the GREAT points made here that this is Michael Phillips, principal product designer - Avid?
 
luki said:
Seth,

Filmscribe has been a released tool for quite awhile. I think Michael was the actually the guy who designed pretty much 100% of it. (right, Michael?) But, the XML output specifically for REDCINE has not been released yet.

Lucas
Click to expand...

Thanks Lucas :)

Edit : I actually did know that, as we have it at work. My excuse is I have the flu and not much of my brain makes sense right now :)

Excuses, excuses ..
 
MichaelP is Michael Phillips of Avid... :)
 
MichaelP
Are you able to transcode the native rd3 files to DNxHD 36..if so how do they look..and any curruption issues?...any recommended DNxHD resolution recomendations?

Thanks
DB
 
One of the features still needing to be done via RedCine is having the ability to select which DNxHD codec. Right now it defaults to DNxHD 115 (for 24fps formats).

You can take the QT refs from RedAlert! and import directly into MC as any of the DNxHD codecs with no issues.

Michael
 
MichaelP said:
One of the features still needing to be done via RedCine is having the ability to select which DNxHD codec. Right now it defaults to DNxHD 115 (for 24fps formats).

You can take the QT refs from RedAlert! and import directly into MC as any of the DNxHD codecs with no issues.

Michael
Click to expand...

Thanks Micheal,

Hopefully a Red Team memeber is on this...Having the full range of Avid DNxHD codecs would be huge! O I forgot.....I'm an optomist...Will be Huge!

Best Regards
 
MichaelP said:
You can take the QT refs from RedAlert! and import directly into MC as any of the DNxHD codecs with no issues.

Michael
Click to expand...

I also think it's gonna be very handy to also have the ability to create (and batch output) QT refs FROM Redcine - (a feature request we've made) - although, I assume you couldn't carry re-framing in QT refs -
 
DNxHD export...

DNxHD export...

searching high and low to see where I export DNxHD from REDCINE, am I missing something?

I am not a AVID user but alot of intrested parties are?
 
Yes, it defaults to DNxHD 115 for 24fps formats. DNxHD 120 or for 25fps. Go to the Avid Knowledge base for download of codecs.
 
It does nothing. The choices should be:

DnxHD 36
DNxHD 115
DNxHD 175
DNxHD 175x
1:1
1:1x

Where the number is the data rate, the "x" is 10 bit versus 8 bit, and 1:1 is uncompressed HD.

Michael
 
MichaelP said:
And speaking of consistency, another area which could be considered a feature request is the age old issue of counting 0 or not as first frame when dealing with whole frame counts. Whatever is chosen as the default should be consistent throughout. Right now setting an IN on the clip is +1 form what is burned-in on the overlay.

Michael
Click to expand...

Oh... bitch, bitch... :)

Lucas
-----
ASSIMILATE, Inc.
LA, CA, USA
 
MichaelP said:
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
Click to expand...

Michael,

I'd confirm this w/TonyC and Rob, but I am assuming that this should always refer to the original file, as this is how it will be referenced in REDCINE. Let REDCINE deal with jumping from _001 to _002 based on SourceTC.

Lucas
 
OK - but it might be a nice piece of additinal metadata to indicate whether the file is made up of two or more clips and eventually an indication to the original clip itself should another conform box be used (assuming that other vendors get access to the r3d files...).

Michael
 
MichaelP said:
OK - but it might be a nice piece of additinal metadata to indicate whether the file is made up of two or more clips and eventually an indication to the original clip itself should another conform box be used (assuming that other vendors get access to the r3d files...).

Michael
Click to expand...

I'd like that too - I wonder if there is a flag already hiding in there ... Rob?
 
You must log in or register to reply here.
Back
Top