Forum Replies Created

Page 265 of 428
  • Michael Phillips

    October 29, 2012 at 5:51 pm in reply to: Newsflash

    never heard of Newsflash. Avid has NewsCutter…

    Michael

  • Michael Phillips

    October 29, 2012 at 2:20 pm in reply to: Kinda hijacking the REELS thread from below…

    I just did a session dealing with camera metadata and the importance of consistency and persistence of that metadata throughout post. Not only for picture, but sound, and then double system workflows where a single clip represents two different sources, etc.

    There are formats that have long filenames, but also include a REEL ID in the header of the file which is usually a truncation of the filename to 8 characters; such as ARRI Alexa and Red to some extent. This is due to EDL’s being the sequence translation in many cases (unfortunately) and it’s legacy limitation of only having 8 characters as source. Media Composer offers 16 and 32 versions of the EDL while also removing other CMX limitations such as number of events and number of sources (999 and 254 respectively).

    So some cameras use a shorter REEL ID, some don’t. Some cameras allow you to create very long Camera ID such as the BMCC. I have seen some as long as 51 characters. VFX can create long filenames, and such. So in the end, systems need to be prepared to support any length of filename string supported by the OS as well as any and all metadata in the header to allow full flexibility in post workflows chosen.

    Michael

  • Michael Phillips

    October 28, 2012 at 10:58 pm in reply to: frame to second conversion question

    You can also use the Avid timecode calculator for such conversions.
    (command 2).

    Michael

  • Michael Phillips

    October 28, 2012 at 10:50 pm in reply to: Media Import….ale and .xml

    For others following along – here is what was done in the end to bring in all the metadata from the Alexa:

    1. Fast Import directly original files
    2. After import, add the column “Source File” to the bin (choose columns). It should contain the full name of the file including .mov
    3. Highlight all clips and do an import with the following changes to
    Import options – Merge based on known sources – (last check box)
    4. Select ALE file that matches those clips. All the info should be added.
    5. Highlight the column Reel_Name and do a command-D and select either
    Labroll or Camroll and click OK.

    Michael

  • You should be able to…

    Michael

  • Michael Phillips

    October 28, 2012 at 5:33 pm in reply to: Media Import….ale and .xml

    OK – importing will present you with either preserving as ProRes or transcoding to DNxHD. If on a Mac, and have enough storage, then keeping the Prores file as a Prores file and having the ability to render as ProRes will be your best bet.

    Make sure your import settings are set to Rec 709 and at correct size to be as a fast import. If you don’t see the words “fast import” beneath the progress bar when importing, then you need to verify your settings.

    In this scenario – import the ALE for each folder into a bin, select all clips, do a batch import and select QT from the file that matches. I don’t believe you will need to edit the ALE file beforehand, but I have not seen an Alexa camera generated ALE file in a while. If you don’t mind sending the ALE, I can check. Send to michael[at]24p[dot]com

    Michael

  • Sounds like more if a RedCine X Pro issue than Media Composer. Do the R3D clips in RedCine X Pro still have the reframing metadata applied?

    Michael

  • Michael Phillips

    October 28, 2012 at 5:14 pm in reply to: Media Import….ale and .xml

    Are you looking to do this via AMA (user managed) or Avid managed (fast import) and keep ProRes? Prores can be re-wrapped as MXF/Prores via a fast import and live within the Avid MediaFiles/MXF folder structure.

    I ask because it will change the way you work with the ALE file. As an FYI – Media Composer does not support XML import for log files. But depending on link/import method – it will be a batch import into the ALE or an ALE merge to AMA linked files.

    Michael

  • Michael Phillips

    October 27, 2012 at 3:34 pm in reply to: SCRI – Avid Woes Continue with Q3 Warning

    I agree – and I can’t speak for Adobe, but for Media Composer a “complete rewrite to 64bit” was also been bantered about when v6 came to market. I always like to ask back – “if a complete rewrite of the code, then why would you keep existing limitations such as resolution, bit depth, etc. in the new version?”

    Making sure it runs on 64bit, taking advantage of additional memory where needed, and potentially having a architecture for future development etc. is more like it.

    Michael

  • Michael Phillips

    October 26, 2012 at 3:05 pm in reply to: Avid Audio Workflow – Converting Audio for Edit

    Import does not allow you to choose video, audio, or both, it’s always everything. Couple things to consider:

    AMA to the clips, subclip out audio only, then transcode those to Avid media.

    Use a program like MPEG Streamclip to extract and transcode audio only as a pre-process to an Avid compatible import format such as WAV, AIF, .mov, etc.

    Michael

Page 265 of 428

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy