Forum Replies Created

Page 47 of 428
  • What are there plans after you conform? Being RED, it makes more sense to conform in the color correction application being used so they have control over the RAW image if and when needed.

    If you do conform, what do they want from you as you cannot deliver a conformed RED file, and Media Composer does not yet consolidate R3D. You can create a project that matches the source XY resolution, AMA link the R3D files, do a a relink to selected from your locked picture sequence, transcode to DNxHR, most likely 444, in a filmLOG color space and give them that. But you want to conform that with whomever is doing the color correction.

    Michael

  • Michael Phillips

    June 15, 2016 at 3:27 am in reply to: Non drop frame rushes modified to drop frame

    Yes – the conform for the clips you changed will be off by 2 frames after the first minutes, etc. due to the different counting schemes. I haven’t tried it, but can’t you create a common timecode in one of the AuxTC columns and group based on that?

    Michael

  • Michael Phillips

    June 15, 2016 at 3:23 am in reply to: Undo fish eye lens

    There is nothing native to Media Composer, but I believe Boris has a effect that can. Also, depending on what you used to shoot with, the camera supplier sometimes provides tools to work with that footage – for example, GoPro.

    Michael

  • Michael Phillips

    June 13, 2016 at 12:04 am in reply to: Fusion Connect for Avid

    The announcement has caused a lot of confusion, as there was not a whole lot of specifics when first released. I “believe” the news was really about a new version of Avid Connect that also included OS X as it as Windows up to this release. But there is no new behavior as far as working with Media Composer and Fusion without an Avid DNxIO box. As far as Avid Product Management finally got around to saying, is that it was still needed unless you purchase Fusion Studio.

    But you can find it on Blackmagicdesign.com/support.

    I wish there were official Avid announcements when these things are released so that users know right off the bat what is available, and what works seeing as Avid supports the Avid branded Blackmagic IO box (DNxIO) and having the OS X version would be good to hear from Avid.

    In the meantime, I blogged about using Resolve as an “Avid Connect” between MC and Fusion:

    https://24p.com/wordpress/?p=291

    Michael

  • Are you on a later version of MC with 64 tracks of support?

    Michael

  • Depending on how media was accessed or created it will either be in one of these two columns:

    Tape
    Source File

    I usually create a bin view called Source that has these two columns, image size, codec, etc. that I can switch to when needed.

    The “Tape” field gets populated when:

  • Media is captured from a tape source, live video signal, etc.
  • Media is created in a third party application like Resolve and other “dailies” products
  • Source File gets populated:

  • Media is imported to accessed via an AMA plug-in via the Link process
  • The above is true for all video based workflows. Note that AMA always uses the filename and does not support any embedded REEL IDs

    When working with WAV from production audio, production can assign a “Tape” into the files (legacy) and when linking to WAV, those clips will have both Source File and Tape as well as TapeID. Typically I duplicate the TapeID into the SoundRoll column.

    Michael

  • Some workflows and applications may not support AAF. EDL Manager allows you to use different columns as source – they are Labroll, Camroll, and SoundRoll. Or you need to create a pull list, etc.

    In this scenario, dailies being done in Resolve, you have the option of either embedded to file name to be designated as REEL which then becomes TAPE in Avid media. So your original source can be tracked via that column regardless of what NAME column is changed to. As Pat points out, if this is the case, the Timecode Generator should be able to display that column as well.

    Michael

  • My thoughts for future use:

    1. Remember to rename prefix in the camera to something more useful than: “Blackmagic Pocket Cinema Camera_” That’s a lot of characters wasting space adding no value. Even just the letter “A_” (for A camera) or A_Camera_ would work just as well.
    2. Consider renaming the files before you do any work at all in Resolve or Media Composer. Any file renaming program can do a text replace of “Blackmagic Pocket Cinema Camera” to something more useful.
    3. In Media Composer, duplicate the original DNG file name to the Camroll or Labroll as those work very well, can be re-purposed in an EDL if needed, and are east to select for the TC Generator to use.

    Michael

  • Michael Phillips

    June 2, 2016 at 10:53 pm in reply to: Avid EDL Mono and Stereo

    You should be able to, but there is a limit to the number of tracks supported. I brought this up in beta to match the 64 now available, but it is on the backlog. If you want to send me a bin to try on my end to see what up I will. michael[at]24p[dot]com

    Michael

  • Michael Phillips

    June 2, 2016 at 7:16 pm in reply to: Footage shot on FS7

    I looked at a set of XML files from a clip recorded on the FS7, and while I did see a lot of location data recorded, I did not see any lens metadata. I did a quick search of the user manual, and nothing was obvious there to enable if available.

    Michael

  • Page 47 of 428

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