Participant

Answered

32-Bit QuickTime Support Ending - Premiere v12.0.0

Forum|Forum|8 years ago
October 18, 2017
13 replies
59242 views

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 has been closed for replies.

Correct answer SteveHoeg

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

L

larrye20612251

Participating Frequently

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

Mad Pierre

Participating Frequently

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?!

Mad Pierre

Participating Frequently

larrye20612251 wrote
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?

At least one file in your project needs to be converted in order to be used in the latest update to PR and AE.

If you enable "Video Codec" under the Premiere Pro Project Metadata options in the Metadata Display dialog box, you can then scan the Video Codec column while in List View.

Or, if you know the name of the offending CODEC, you can create a new Search Bin from query with the option set to Video Codec.

-Warren

Thanks Warren. That does 'work' but I'd not really say that it is the best way for Adobe to provide help/user feedback. I have a RAID drive sat on my desk with dozens of projects and hundreds, if not thousands, of files - stretching back a few years. Mostly, I don't need these unless a client wants a change to a project. So, I'd have to open and convert every project and look at the meta data for every single file. Since Premier knows that there's an offending file when it opens a project, it would be really helpful if it would highlight that file in a clear and easy way. Then a right-click to render and replace please. I totally get why Adobe is discontinuing support for this codec, fine, the world moves on - but how about a real-world easy solution to getting rid of potential problems coming back to haunt us? Or am I missing something?

Mad Pierre

Participating Frequently

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

Warren Heaton

Community Expert

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

N

not_Aaron

Participant

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....

A

afearisthis

Participating Frequently

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!"

Mad Pierre

Participating Frequently

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.

R

razvang87726906

Participating Frequently

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?

tadeu_segundo

Participant

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.

R

razvang87726906

Participating Frequently

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

K

Keith_Clark

Inspiring

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

SteveHoeg

Adobe Employee

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

M

markschlicher

Known Participant

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?

J

j_davis63

Participant

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.

SteveHoeg

Adobe Employee

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

C

compgeek07

Participant

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.

Ann Bens

Community Expert

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.

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded