Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Pr CC 2015.4 Windows reading Apple .mov as AVC-I 100 codec natively

  • Pr CC 2015.4 Windows reading Apple .mov as AVC-I 100 codec natively

    Posted by Sam Lee on October 20, 2016 at 1:58 am

    I’m curious to know whether Adobe CC 2015.4 for Windows can read .mov generated from a Mac OSX using FCP 7 from P2 AVC-I 100 footage? I know that all flavors of Pro Res 422 will be fine. However, last time, the native AVC-I 100 codec rewrapped as a .mov will not work. I don’t have a Win Pr CC to test it out. Native AVC-I 100 is much smaller than Pro Res 422. The rewrap time is also dramatically faster than doing it in Pro Res 422. Quality is literally identical.

    Sam Lee replied 9 years, 6 months ago 3 Members · 8 Replies
  • 8 Replies
  • Alan Lloyd

    October 20, 2016 at 9:59 pm

    Are you talking AVC-Intra camera files? Or have they already been edited or processed in some way?

    AVC-Intra from P2 should load directly into Premiere. There is even a preset for creating a sequence using those settings as a normal preset.

    As Dave said, duplicate a couple files and send them to your editor. See what happens. They should load without any fuss.

  • Sam Lee

    October 21, 2016 at 12:10 am

    There’s an annoying bug or limitation on FCP 10.2.3 where when importing native P2 AVC-I 100 spanned footage, it would not properly reimport after the media has been moved around (changed volume name). Another reason why I use the rewrapped method is the cam’s metadata. In AE CC 2015, it’s not possible to import the .mxf as a clean metadata that was recorded on the field. AE is not smart enough to automatically span volume and retain full clip name metadata. This gets really confusing especially working with Adobe Dynamic Link between Pr & AE on Mac & Windows. Collaborating of editors at different locations also benefitted from a single rewrapped .mov with custom clip metadata name instead of 10-12 P2 spanned P2 cards. And it gets unwieldy when there is multicam involved. Imagine trying to know which camera is which (out of 12 cams) with the system’s default 0041AB.MXF. The custom clip name of “cam09-jib_4.5mmWide_0001.mov” makes a huge difference in media management for example. And that so far worked very well if the P2 media are rewrapped (native AVC-I 100 .mov that so far worked on OSX only) or transcoded to a single .mov
    via Pro Res 422 (Mac&Windows OK) but at a huge transcoding time cost.

    Lastly, FCP X & Pr’s proxy workflows seem to prefer single packaged .mov instead of the camera native .mxf from P2. I had no luck in seamless workflow whenever native camera format are used. This is especially true on AVCHD, Canon XF codec (C100-C300), and so forth.

  • Peter Garaway

    October 21, 2016 at 4:44 am

    Hi Sam,

    I’m not seeing any issues with ACVI.mov files in our upcoming release on windows. I don’t have 2015.4 available at the moment but I’m pretty confident they’d be fine there as well.

    Note that the files were generated in FCP7 and another set from a Grass Valley server. If you want to provide me a small sample file I can take a look at it for you.

    Here’s the file info.

    Best,

    Peter Garaway
    Adobe
    Premiere Pro

  • Sam Lee

    October 21, 2016 at 3:04 pm

    Hello,

    How can I send you a small FCP 7 rewrapped .MOV as AVC-I native codec to check that the latest Pr CC Windows will read it? Perhaps a private link via WeTransfer.com?

    Native AVC-I is so much more efficient over A. Pro Res 422 in terms of file size and rewrap time.

  • Peter Garaway

    October 21, 2016 at 5:42 pm

    Sure. However you want to send it. Creative Cloud, DropBox or WeTransfer.

    Standing by.

    Peter Garaway
    Adobe
    Premiere Pro

  • Sam Lee

    October 21, 2016 at 7:09 pm

    Here’s the WeTransfer link of the AVC-I 100 rewrapped .mov directly fr FCP 7:

    https://we.tl/K7wQ0diiaY

    Media Info report, but better to actually test it with the file:

    Video
    ID : 1
    Format : AVC
    Format/Info : Advanced Video Codec
    Commercial name : AVC-Intra 100
    Format profile : High 4:2:2 Intra@L4.2
    Format settings, CABAC : No
    Format settings, GOP : N=1
    Codec ID : ai13
    Codec ID/Info : Advanced Video Coding
    Duration : 24s 391ms
    Bit rate mode : Constant
    Bit rate : 114 Mbps
    Width : 1 920 pixels
    Clean aperture width : 1 888 pixels
    Height : 1 080 pixels
    Clean aperture height : 1 062 pixels
    Display aspect ratio : 16:9
    Clean aperture display aspect ratio : 16:9
    Frame rate mode : Constant
    Frame rate : 29.970 (29970/1000) fps
    Original frame rate : 59.940 (60000/1001) fps
    Standard : Component
    Color space : YUV
    Chroma subsampling : 4:2:2
    Bit depth : 10 bits
    Scan type : Progressive
    Bits/(Pixel*Frame) : 1.829
    Stream size : 329 MiB (95%)
    Language : English
    Encoded date : UTC 2016-03-07 22:59:03
    Tagged date : UTC 2016-03-07 22:59:03
    Color range : Full
    Color primaries : BT.709
    Transfer characteristics : BT.709
    Matrix coefficients : BT.709

  • Peter Garaway

    October 21, 2016 at 10:11 pm

    Hi Sam,

    No issues with the file you provided on windows using the current shipping version of Premiere. As noted in the previous post, AVCI.mov files are working fine in our upcoming release as well.

    Best,

    Peter Garaway
    Adobe
    Premiere Pro

  • Sam Lee

    October 22, 2016 at 1:50 am

    Splendid news! A right step on Pr CC to be able to do this on the Windows platform. I’ll revert back to my AVC-I rewrap workflow. Huge time saver and disk space as well.

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