Forum Replies Created

Page 36 of 132
  • Job Ter burg

    November 4, 2012 at 5:40 pm in reply to: Avid Xpress Pro 4.64 project to latest AMC

    – You should be able to use the same project, but creating a fresh one and copying across the bins is a somewhat safer way

    – You should not have any issues with footage not linking; you could delete the msm.pmr and msm.db files from the mediafiles folders if only to force the Avid to rebuild these databases. It’s safe, but not required.

    – Mac-PC should not matter at all, just beware that you should not use HFS+ formatted drives as media drives on a PC, nor should you use NTFS formatted drives as media drives on a Mac. You’re better off copying the media to a properly formatted drive.

  • Job Ter burg

    November 3, 2012 at 1:48 pm in reply to: Avid Xpress Pro 4.64 project to latest AMC

    Just hook up the mediafiles, and open up the project on any MC or Symphony. No pitfalls. If they haven’t stored the mediafiles, you’ll need to batch capture or batch import the original footage. Other than that, the media and the project files will travel to any modern version of MC/SY without any issue, other than that opening up sequences with certain effects are likely to need to be promoted to the current version of the effect, which will happen automatically.

    You can go with 6 or 6.5 depending on your preference.

  • Audio has no frame rate, only a sample rate.

  • Job Ter burg

    October 16, 2012 at 5:54 am in reply to: 24P to 29.97 pulldown question

    I think 15:1s (which is half raster, 48 mins/GB)) is a lot smaller than 14:1p (which is progressive, 14.6 mins/GB). But 35:1p (36.4 mins/GB) or 28:1p (29.1 mins/GB) will definitely give you an easier workflow, and will likely look much better.

    If you can spare the bandwidth, go for 14:1p. If you really need to save on bandwidth, I’d sooner choose 35:1p @23.976p than 15:1s @29.97i, as it allows you to post in native 23.976p.

  • Job Ter burg

    October 15, 2012 at 5:04 pm in reply to: r3d raw question for avid mc6 workflow

    Avid will work at 1920×1080 max. anyway.

  • Job Ter burg

    October 15, 2012 at 6:01 am in reply to: r3d raw question for avid mc6 workflow

    AMA-linking and transcoding will generate a Source File name, RedCine-X will generate a Tape Name. Used to be that you could not cross-link between these two methods, but that may have changed in v6.

  • Job Ter burg

    October 14, 2012 at 6:27 am in reply to: r3d raw question for avid mc6 workflow

    The Clip name is not used for relinking later. You can rename the clip at will. The Source File name will be stored in the Source File column.
    Since you are syncing up with sound, and you will thereby create sync clips, you may just as well rename those, while having the master clips retain their name. But it is not required.

    The AutoSynced clips will not make relinking later any different.

  • Job Ter burg

    October 6, 2012 at 8:34 pm in reply to: Transcoding 23.98 from AMA is changing DF to NDF

    AFAIK, there is no such thing as 23.976 DF. 23.976 has a TC24.

  • Job Ter burg

    September 29, 2012 at 8:33 am in reply to: Prores exports

    I’d always try to avoid using the Quicktime encoders for codecs like ProRes and H264. x264 and Main Concept H264 seem to suffer less from gamma shifts than Apple’s H264.

  • Job Ter burg

    September 29, 2012 at 7:02 am in reply to: rendering in avid

    It will render during export.

Page 36 of 132

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