Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

quicktime plugin missing from Google Chrome

I was not able to watch videos on the Apple website because it said I did not have quicktime installed. However, when I went to "Enable" quicktime in my Google Chrome settings, the quicktime plugin was not even in the plugin list. I have reset my browser settings, cleared my history/cache, uninstalled and reinstalled Google Chrome. I am able to watch the Apple video in Safari, but not in Chrome. When I click on "install quicktime," from the Apple website, it says that Quicktime will be automatically updated with software updates and my computer is up to date. I have also made updated my Chrome browser.

Please advise on how to add the quicktime plugin to chrome.

Thanks.

Posted on Sep 10, 2014 9:13 AM

Reply
Question marked as Best reply

Posted on Nov 24, 2014 10:18 AM

Having the same problem with Chrome, running version 39.0.2171.65 on a Macbook Pro 15" Late 2013. The Quicktime plugin will not appear in chrome://plugins no matter what I've attempted. Seemingly worked fine the other day. Since discovering the problem I've tried the following with no success:


-Full uninstalls (several times) including any Chrome preference files

-Upgrading to latest Chrome Beta

-Using Chromium (same problem in that app)

-Manually placing the quicktime.plugin file into Internet Plugins folder within App Contents


There's no manual override to force the plugin into Chrome, either on Apple's or Google's end. Seems like this should be fixable but I'm stumped. Would really love some fresh ideas to try!

28 replies

Dec 1, 2014 9:41 AM in response to Grant Hutchinson

Grant, thank you for noting that the issue has been posted at https://code.google.com/p/chromium/issues/detail?id=437565


It is currently being flagged as "Status: WontFix" by a Chromium.org worker. That is an unacceptable response. I urge everyone to implore the Chrome team to change "Won't Fix" to "Will Whitelist." QuickTime must not be trashed like this.

Dec 1, 2014 9:48 AM in response to QuickTimeKirk

QuickTimeKirk wrote:


http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html


Deprecating support for a legacy plugin API (such as the Netscape Plug-in API) is different than removing support for all plugins. This still isn’t the issue brought to light by this thread. It remains that the current 32-bit QuickTime plugin doesn’t work in the current 64-bit release of Chrome, regardless of Google’s stand on plugins.

Dec 1, 2014 10:12 AM in response to Grant Hutchinson

First. I don't have a dog in this fight and rarely use the Chrome (Google) browser for anything other than testing and evaluating some of my page code.

All Web pages are moving to http://en.wikipedia.org/wiki/HTML5 and that is where we'll be soon.

Apple released its last version of QuickTime in 2005 and now only develops for QuickTime X and it's OS X only software.

Microsoft has ended support for is "Silverlight" plug-in and web sites that used to use it (Netflix) are changing their pages and updating the code to remove the need for plug-ins.

Adobe Flash isn't in the same game but use of it is also waning at most modern Web pages.

So. Browser plug-ins are dead in Chrome and soon the rest of the Web as page authors change their page code.

If your own page code doesn't work it's up to you to change it. If your browser no longer supports page code that calls a browser plug-in then you'll have to switch to view the content.

Dec 1, 2014 12:22 PM in response to Grant Hutchinson

Grant


Chrome is not alone in its move toward the HTML5 STANDARD - see KT's wikipedia reference - Firefox has also done so by "disabling all 'PLUG-INs' by DEFAULT" - not "Extensions" (AdBlockPlus, QuickTranslate, etc.)


If Chrome still allows Flash, etc., it is merely a matter of time.


It is up to to content providers(websites) to adopt HTML5. The problem is not Safari's, Chrome's, Firefox et al


IMHO, these moves are necessary to make the content creators/providers do what they must eventually do without delay. They have known it was coming for years.


ÇÇÇ

Dec 1, 2014 1:12 PM in response to ChitlinsCC

QuickTimeKirk wrote:


If your own page code doesn't work it's up to you to change it. If your browser no longer supports page code that calls a browser plug-in then you'll have to switch to view the content.

ChitlinsCC wrote:


It is up to to content providers(websites) to adopt HTML5. The problem is not Safari's, Chrome's, Firefox et al.


I completely agree.


In fact, I have been a proponent of HTML5-based media embedding since the beginning. Yes, it is up to content providers (including Apple) to adopt HTML5, but browser developers also have a responsibility to their users to not deliberately break things. I use Chrome because it is stable, fast, and Safari/WebKit is no longer updated by Apple for Snow Leopard. FireFox is just a hot mess in terms of interface and I can’t stand using it.


Fine. Remove support for plugins


However, a little warning before auto-updating everything would have been appreciated.

Dec 1, 2014 1:28 PM in response to Grant Hutchinson

Grant Hutchinson wrote:


SNIP


I completely agree.


SNIP
Fine. Remove support for plugins


However, a little warning before auto-updating everything would have been appreciated.

this is - after all

User uploaded fileNOTUser uploaded file

⇪ just images, not hotlinked ⇪


BUT, if it is any consolation, I think everyone finds out about stuff like this in much the same way. I dont remember getting the MEMO on the change made in Firefox (which I like a LOT more than Chrome or Safari - slick, fast, extensible ad infinitum) - Mozilla is the oldest still cranking out product, after all.


ÇÇÇ

Dec 1, 2014 1:52 PM in response to Richard Schletty

Here is the ticket I submitted to http://itunesaffiliate.phgsupport.com on 11/28/2014. Still no reply yet. I have no control over this Widget code. It is generated by the Widget Builder. I copy and paste the iframe code into my site. What is my workaround? Are all my iTunes Playlists forever dead with 64-bit Chrome?

Request #10232
Google Chrome prompts for QuickTime plugin


When building a new iTunes Playlist Widget, or viewing an existing Widget, Google Chrome prompts for QuickTime plugin in Mac OS X Mavericks. Furthermore, songs do not play. QuickTime is not loading in Chrome.

I tried a fresh install of Chrome Version 39.0.2171.71 (64-bit). That did not fix it.

Feb 28, 2015 3:15 PM in response to QuickTimeKirk

Disagree with you COMPLETELY.


A browser is a program for accessing content via the HTTP/HTTPS protocol.


If a video file (quicktime) is hosted on a server somewhere, I expect that if I access that file directly with browser, it should play it. HTML5 requires there be some webpage hosted to play that file, and that's just dumb. The browser should be able to say ".mov"--- does the OS have something that can read that container / codec? If so.. here you go, playing it...

Mar 17, 2015 6:01 PM in response to Car.

When I updated the QuickTime plugin on my PC, I encountered sound problems on some of the videos I had created years ago; that is, there was video but NO sound. The newer videos on this website were not adversely affected. For those who may want to examine this for themselves, the URLs in question are:

http://visionarypictures.com/fmcommercials.html and http://visionarypictures.com/fmcommercials2.html

A friend of mine who is a retired sound engineer came up with a possible answer. The older videos had a very low sampling rate of 22 hertz. The newer videos had sampling rates of 33 or 44. My friend thinks that the latest version of the QuickTime plugin may simply not recognise the videos with low audio sampling rates. Does this sound plausible?

Mar 18, 2015 9:09 AM in response to Paul Atro

A friend of mine who is a retired sound engineer came up with a possible answer. The older videos had a very low sampling rate of 22 hertz. The newer videos had sampling rates of 33 or 44. My friend thinks that the latest version of the QuickTime plugin may simply not recognise the videos with low audio sampling rates. Does this sound plausible?

Since certain combinations of audio compression, data rate, and sampling rate may create problems, the basic idea does, on the surface, sound very plausible. Unfortunately, when I tested your friend's hypothesis in practice, it didn't "float."


Your audio tracks are IMA 4:1 (PCM) audio having target data rates of 192 Kbps and sampling rates of 22.050 KHz which appear to be fully supported by all media players in which I tested them—to include QT X, QT 7, VLC, MPlayerX, NicePlayer, etc. I then sourced the two sampled files as MP4 files by passing the original video through to MP4 file containers and converted the IMA 4:1 stereo audio converted to AAC audio. In this case I had to lower the target data rate to 64 Kbps since QT does not allow AAC stereo conversion to a 20.050 KHz sampling rate using a target data rate of 192 Kbps. These files where then placed on one of my personal web site pages and re-tested. All 4 files played correctly with audio using browsers forced to play the files using the QT 7 browser plug-in.


Since both your original MOV files and the modified MP4 files play correctly on my web page, I suspect your playback problem is more likely to be a lack of browser playback support for the IMA 4:1 audio compression format due to the manner in which the referenced "VisionaryPictures" web pages are coded for playback. If possible, suggest you replace the MOV files employing the legacy audio compression format with the more modern MP4 H.264/AAC files to see if the audio content is then correctly handled by the page code. All tested files are available for download at http://downloads.walker4.me/Temporary.html


User uploaded file

quicktime plugin missing from Google Chrome

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.