Click here to go to the first RED TEAM post in this thread.   Thread: REDCINE to SCRATCH to Tape....

Reply to Thread
Page 3 of 5 FirstFirst 12345 LastLast
Results 21 to 30 of 41
  1. #21  
    Senior Member MichaelP's Avatar
    Join Date
    Aug 2007
    Location
    Boston
    Posts
    2,318
    You do not want to create a Quicktime with 2:3 pulldown at 29.97 just to remove it again for a 23.976 SD project. The file stays stays native 23.976 as it is now when importing, it is just the metadata that needs to address it as though it did come from 29.97 and had the 2:3 pullldown removed. This is where MetaCheater comes in for creating the metadata before the import. It just needs to updated to reflect the relationships of 24 to 30. I will be finishing a whitepaper that has all of this in it soon, once I get all the information from the different workflows being attempted. Just a bit difficult when working with two beta test files and not having access to a camera.

    The basic mapping is as follows:

    24 30 pulldown
    :00 :00 A
    :01 :01 B
    :02 :03 C
    :03 :04 D
    :04 :05 A
    :05 :06 B
    :06 :08 C
    :07 :09 D
    :08 :10 A
    :09 :11 B
    :10 :13 C
    :11 :14 D
    :12 :15 A
    :13 :16 B
    :14 :18 C
    :15 :19 D
    :16 :20 A
    :17 :21 B
    :18 :23 C
    :19 :24 D
    :20 :25 A
    :21 :26 B
    :22 :28 C
    :23 :29 D


    Michael
    Reply With Quote  
     

  2. #22  
    Senior Member MichaelP's Avatar
    Join Date
    Aug 2007
    Location
    Boston
    Posts
    2,318
    Just a bit of history - MetaCheater was originally developed by Jabez to allow the QT coming from VFX (WETA in NZ) based on the concept that we had discussed that Batch import of files (QT, sequential TIFF, etc.) can have metadata attached to them if an ALE was created beforehand into which the files get merged. During the import, the files inherit all the metadata from the file as well as having the ability to add more as thought it had gotten captured via tape. A ton of metadata can be tracked this way if any of the applications export the metadata in the first place. For an idea of what that can be, check on two whitepapers I have written on Metadata Logging and Tracking as well as ASC EDL support in Avid at: http://www.avid.com/resources/whitepapers/index.asp

    Jabez has been great in extending the tool to work with RED to allow the same basic workflow. There are still some tweaks that need to be done, but it is getting close. A HUGE thanks to Jabez who is currently working on Lovely Bones for Peter Jackson.


    Michael
    Reply With Quote  
     

  3. #23  
    Senior Member
    Join Date
    Feb 2007
    Posts
    254
    aha,
    Ok makes sense Michael so all we need to do to get a working TC 24 is map the end code into a 29.97 space. IE when a 29.97 project is selected instead of mapping the 23.976 end code we need to map the conversion as stated above. Tested it works. So Jabez I guess thats a feature request, in the meantime I'm going to script something of my own.
    Reply With Quote  
     

  4. #24  
    Senior Member MichaelP's Avatar
    Join Date
    Aug 2007
    Location
    Boston
    Posts
    2,318
    Avid is working on the XML to ALE conversion from REDCINE, so we will provide both SD and HD output with all the metadata provide when saving a REDCINE project as .xml. Over time, I would hope to get more metadata out of the process such as color, etc.

    Michael
    Reply With Quote  
     

  5. #25  
    Senior Member
    Join Date
    Feb 2007
    Posts
    254
    Thanks Michael,
    Just got our automated avid transcode system working because of this.
    Reply With Quote  
     

  6. #26  
    Quote Originally Posted by Jeff Brue View Post
    aha,
    Ok makes sense Michael so all we need to do to get a working TC 24 is map the end code into a 29.97 space. IE when a 29.97 project is selected instead of mapping the 23.976 end code we need to map the conversion as stated above. Tested it works. So Jabez I guess thats a feature request, in the meantime I'm going to script something of my own.
    If I find some time I'm happy to do this... but really we should all be cutting in HD with DNxHD36 anyway :)
    Reply With Quote  
     

  7. #27  
    Quote Originally Posted by MichaelP View Post
    Avid is working on the XML to ALE conversion from REDCINE, so we will provide both SD and HD output with all the metadata provide when saving a REDCINE project as .xml. Over time, I would hope to get more metadata out of the process such as color, etc.

    Michael
    Michael -

    Please help me in my crusade for color settings in REDCINE XLM - VERY important to my future pipeline(s) - whatever you can do to encourage the REDCINE team to get color settings in there is greatly appreciated - I think them may be getting tired of all my requests -
    Reply With Quote  
     

  8. #28  
    Quote Originally Posted by MichaelP View Post
    Avid is working on the XML to ALE conversion from REDCINE
    Michael,

    i'm just curious, do you know maybe is avid working ONLY on xml to ale conversion for REDCINE or also on ANY xml conversion to ale (say FCP)?

    thank you,

    filip
    in K I N O veritas!
    Reply With Quote  
     

  9. #29  
    Senior Member
    Join Date
    Apr 2007
    Posts
    3,584
    Quote Originally Posted by cogito View Post
    If I find some time I'm happy to do this... but really we should all be cutting in HD with DNxHD36 anyway :)
    And if there were a way to see that on a client monitor without buying an Adrenaline HD, we might be.
    Reply With Quote  
     

  10. #30  
    Senior Member MichaelP's Avatar
    Join Date
    Aug 2007
    Location
    Boston
    Posts
    2,318
    Use a DVI out full screen. For craft editorial non critical monitoring purposes, it works fine.
    Reply With Quote  
     

Posting Permissions
  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts