Skip to main content
Gonvik
Participant
Oct 18, 2017 4:31 PM UTC
Answered

32-Bit QuickTime Support Ending - Premiere v12.0.0

Hello,

My team is now seeing this warning throughout our projects.  "32-bit QuickTime Support Ending"  -  essentially saying please transcode any media under this legacy format for the future.

What exactly falls under legacy 32-bit quicktime?  Is it certain codecs?  Or all QT MOV files?  If the later, that is kind of huge.

Thank you,

Nick

    This topic is closed to new replies. Start a new post to keep the conversation going.
    SteveHoeg
    SteveHoegCorrect answer
    Adobe Employee
    Nov 8, 2017 7:32 PM UTC

    Here are the .mov formats we support natively -

    Native Video Import:

    * DNxHD/DNxHR

    * JPEG

    * PNG

    * ProRes

    * Cineform

    * DV

    * AVCI

    * h264

    * IMX

    * MPEG2

    * HDV

    * HEVC

    * XDCAM

    * Uncompressed

    * Animation (without delta frames)

    Native Audio Import:

    * Uncompressed

    * AAC

    * AC3

    Native Video Export:

    * Uncompressed

    * DV

    * Cineform

    * DNxHD/DNxHR

    * Animation

    * ProRes (Mac only)

    Native Audio Export:

    * Uncompressed

    View reply

    93 replies

    larrye20612251
    Participating Frequently
    Mar 12, 2018 2:19 PM UTC

    Can someone tell me the best way to analyze a QT file in order to know if it is 32-bit? Thanks!

    Translate
    Mad Pierre
    Mad Pierre
    Participating Frequently
    Mar 12, 2018 2:21 PM UTC

    I've asked this several times. I get one warning on projects with hundreds of media files. OK, so how to track down the offender?!

    Translate
    larrye20612251
    Participating Frequently
    Mar 12, 2018 2:26 PM UTC

    A related question: if I receive this warning in a project, does that mean that I definitely have an offending file or does this waring get pushed out to all projects/users?

    Translate
      Mad Pierre
      Mad Pierre
      Participating Frequently
      Jan 29, 2018 11:21 PM UTC

      I just love the way Adobe is guiding us smoothly through this transition.

      Translate
        Warren Heaton
        Community Expert
        Warren HeatonCommunity Expert
        Community Expert
        Feb 8, 2018 4:45 PM UTC

        Mad Pierre:

        Adobe's handling it rather well all things considered.  It would have been amazing if someone (Apple) had coded a 64-bit system driver that supported everything QuickTime supports (it's an extensive list), but that didn't happen.

        -Warren

        Translate
          not_Aaron
          Participant
          Jan 10, 2018 1:49 PM UTC

          Just received this flag on a .mov file w/h264 video. I suspect because the audio is MP3. Probably not a large market share to record to MP3, but jeez to drop import support for MP3 seems weird....

          Translate
          afearisthis
          Participating Frequently
          Jan 5, 2018 6:22 PM UTC

          The above post from Adobe lists .mov h.264 files as covered, but I get the message every time I export an h.264 .mov.

          Also, does this mean that Apple's finally going to kill Quicktime Player 7? To that I say, "From my cold, dead hands!"

          Translate
            Mad Pierre
            Mad Pierre
            Participating Frequently
            Jan 6, 2018 9:26 AM UTC

            I can't even work out a logic to the message. I assumed it was when there was faulty media in the project, but I've got it randomly on projects where no media is problematic.

            Translate
            razvang87726906
            Participating Frequently
            Nov 28, 2017 7:00 AM UTC

            I'm trying to import a video shot on iPhone 8+ 4k 60FPS and I'm getting this error. The codec is HEVC which according to your list it's a supported codec. But why do I still get this message since HVEC it's fairly new to the market?

            Translate
            tadeu_segundo
            tadeu_segundo
            Participant
            Dec 2, 2017 6:41 PM UTC

            I have the same doubt. I only use iPhone in my filming and the last one is not importing. If it is Apple that will stop the 32-bit support why the new iPhone does not use 64-bit? I tried to go back to the version for CC 2017, but it also did not work. I bought the Adobe system to have more facilities and I think I'm going back to the competition.

            Translate
            razvang87726906
            Participating Frequently
            Dec 2, 2017 8:28 PM UTC

            The way I fixed it, I copied the footage from my iPhone using Image Cature(not Photos app on Mac) and once the files where copied I changed the extension from .mov to .mp4

            Now I can import them to Premier.

            Hopefully this help    

            Translate
              Keith_Clark
              Inspiring
              Nov 2, 2017 12:18 AM UTC

              I saw this message yeaterday too when I imported some AVC-INTRA from work. lol so no Dolby, no avc-intra. Wwooowwwwww

              Translate
              SteveHoeg
              Adobe Employee
              SteveHoeg
              Adobe Employee
              Nov 1, 2017 11:02 PM UTC

              We’re working on a list and should have this ready soon

              Translate
                markschlicher
                Known Participant
                Nov 2, 2017 4:10 AM UTC

                Will you also provide answers to questions such as the ones I posted above?

                Wlll you provide a timetable for incorporating native support for Prores?

                Translate
                j_davis63
                Participant
                Nov 1, 2017 12:51 PM UTC

                I'd like to echo the request for a list of affected codecs. Also, a less ambiguous timeframe would be most helpful.

                I work with a lot of mini-DV footage, captured via Premiere Pro CC (.mov, dvcp). I've got around 150GB of footage spread over 1,500+ clips in this format and intend to continue to shoot and capture this way.

                Is the dvcp codec that Premiere Pro writes to via the capture window reliant on 32-bit Quicktime, or is it natively supported? I'm getting the message pop up, but also have a shed load of archival and library footage of various formats, codecs, etc. in the same project. With no indication given as to which file(s) will need transcoding when support is dropped, I'm at a bit of a loss.

                Translate
                  SteveHoeg
                  Adobe Employee
                  SteveHoeg
                  Adobe Employee
                  Oct 30, 2017 4:19 PM UTC

                  Please see here: https://www.us-cert.gov/ncas/alerts/TA16-105A

                  Translate
                  compgeek07
                  Participant
                  Oct 26, 2017 11:00 PM UTC

                  I'm seeing this warning on a brand new project (in PP 2018) where I'm capturing from DV and HDV over Firewire. Will this change affect capturing over Firewire? I know Firewire is all but dead, but I often help customers digitize their miniDV, DV, and HDV tapes.

                  Translate
                  Ann Bens
                  Community Expert
                  Ann BensCommunity Expert
                  Community Expert
                  Oct 30, 2017 4:28 PM UTC

                  I'm seeing this warning on a brand new project (in PP 2018) where I'm capturing from DV and HDV over Firewire. Will this change affect capturing over Firewire? I know Firewire is all but dead, but I often help customers digitize their miniDV, DV, and HDV tapes.

                  Short answer no.

                  Translate
                  Show more replies
                  Terms & ConditionsAccessibility statement
                  Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices