Previous 1 2 3 4 5 Next 250 Replies Latest reply: Jan 27, 2015 7:09 AM by gmarinov Go to original post Branched to a new discussion.
  • garyfromking's lynn Level 1 Level 1

    Also, why do files play perfectly through quick look but not when opened via the QuickTime player? The correct playback codecs are in there somewhere!


    I can open the quick look to full screen and watch my movies and shows with no problem.



  • miguel165 Level 1 Level 1

    The problems with QuickTime and Quicklook after installing Mavericks are clearly something Apple must repaired. They are major issues and it should not be for users to find workarounds.


    Sticking to QuickTime 7 may not be a solution in the long term. Rather, improvements must made made in the new QuickTime versions. The same as for Quicklook.


    In order for Apple to take appropriate steps, I would recommend to write them at


    The issues discussed here are most disappointing and a solution should be provided soon.

  • Deborah Terreson Level 4 Level 4

    Gary, I honestly do not know what Apple's plans WRT the QuickTime updates are, or even whether they'll address these issues anytime soon. I have been reading up on their longterm plans and it seems that *everyone* is migrating towards cloud-based computing. At that point the security concerns will over-ride considerations for the older file formats OR the applications that run them.



    As of last night's install of Mavericks, I have had to put in three security exemptions for older apps that I use that predate the App Store.

  • scoobyclub Level 1 Level 1

    I am not really knowledgeable enough to know the ins and outs of QT codecs and strategy.


    BUT, the videos I have problems with are youtube videos in HTML5. So if they have decided to degrade, to the point of unuseable, the youtube user experience then I can only give out a big ***!!.


    This seems to be an out and out Mavericks bug to me and it should be fixed PDQ. As pointed out above the correct software is in there ( Quick Preview, Playing in Finder etc prove that ) it is only the Quicktime Player and Quicktime web browser component that have a problem playing one video at a time ( the sound, as previously stated, is fine of more than one video is playing ).


    I shall add this problem/ thread to the Mavericks feedback link.

  • Deborah Terreson Level 4 Level 4

    Oddly enough last night one of the first things I did was to hit youtube and the first three videos I viewed played but only after the 'missing plug-in' message popped up for a few seconds before each.


    After the third video NONE of the movies I tried to view played until I hit Adobe's site and downloaded the Flash player.


    Weird, huh?

  • scoobyclub Level 1 Level 1

    It is weird, especially as I can't find much uproar on the web about it. Is it only a select few that have this problem or are most people still using the Flash option and are therefore blissfully unaffected?


    I have gone back to the Flash setting and hope in time this will be fixed.

  • Deborah Terreson Level 4 Level 4

    I'm thinking that it may be as MOST everyone *seems* to have upgraded from Mountain Lion, Lion or Snow Leopard.. ALL 3 of the OSes I have on my machines reported "Migration Assistant to Mavericks" downloads available in the System Updates.


    Since I've had *horrible* experiences with using the Assistant to migrate settings and data info in the past, I didn't take the update and instead erased my unused Leopard partition and installed Mavericks to that. I have a pure vanilla install on a cleaned, empty partition, and all the tweaks and add-ons aren't there.


    I noticed that there are a whole bunch of Utilities that didn't make the cut to Mavericks and oh-ho! they work *just* fine if I copy them out of the Snow Leopard Utilities folder.. Which is interesting, as MOST of the older version Apple apps have the prohibited circle/bar slapped on the icon and they will NOT run. Hmmm.


    So it leads me to believe that this is more a throwback to the old 'Archive and Install' upgrade that Jaguar, Panther and Tiger did, where only the new code and kernel was updated and the stuff that wasn't, was brought up from the prior install.


    I'm thinking that if you did a install ON TOP of the prior OS, it took the settings you already had resident and just upgraded them - which would go along way to explaining why so few have actually had issues like this.

  • scoobyclub Level 1 Level 1

    Well I had a problem installing directly from the App Store ( the App Store install script crashed and burned ) so had to install from the file that it downloaded which went smoothly. I installed it straight over the top of the existing OS ( fed up having to re-register/license everything etc ) so it may not be a factor.

  • yeeeoww Level 1 Level 1

    I'll throw in my 2 cents worth just for the heck of it... I'm unable to see Quicktime movies with the Avid Codec in QuickLook. I reinstalled the codec but no go. It converts the file in QT Player 10 as everyone else has been reporting.

  • PTO214 Level 1 Level 1

    This is my main issue as well.

  • Deborah Terreson Level 4 Level 4

    @yeeeoww and PT - From what I can work out there is NO way to get around that re-conversion if you use QuickTime Player X for your playback. The only way to avoid that is to set the file properties to playback with the QuickTime 7.6.6.


    Let me clarify: NONE of the codecs will work with QuickTime Player X - it only accepts the 64-bit code now, and few, if any, of the current codecs are that.


    QT 7.6.6 is a 32-bit player as are the codecs. THOSE will work without issue and your older files will play.


    What is happening is that the older formats are being deprecated and will eventually be abandoned as the newer 64-bit processors and codecs are designed to be more energy efficient for the mobile platforms that the ENTIRE computer industry - not just Apple - is moving towards.


    The fact that Apple is holding their new AV core rendering close - where the QTX is 'nested' into the system, whereas QT 7 is not - and not letting third-party developers in on it also speaks to security issues for the mobile 'always-on' future that is coming.


    If you aren't willing to slog through a reconversion on every video and just want to enjoy what you already have, and NOT have to wait, open a Get Info window on the file you want, set the Open With to be QT 7 so your system will default to the older QuickTime and use that. You can set it for one file or ALL of the same type.


    With the codecs in the list I put up and Perian installed in your System Preferences with the sound output set correctly, you shouldn't have any issues.


    Thing is, it seems to be a gamble on which files wortk in QuickLook and which ones do not. So far on my system with QuickTime 7 with the Pro key installed, NONE of my video works in QuickLook - which is fine as I never used it to begin with!


    The thing to consider is that QT 7 and those older formats are on borrowed time, (as they ARE 32-bit and we're into 64-bit now) eventually the nature of the mobile processing and newer codecs will mean many videos will cease to work unless you have reconverted the files.


    I think that forcing everyone to do this ALL at once with the new upgrade is a bit pushy on Apple's part.


    Let's face it, not every video you or I may have will be worth converting and to force this automatically, when in many instances it may *double* the file size is a bit heavyhanded and unnecessary.


    At least with the QT 7 in, you DO have the option to just watch the videos you want without having to jump through any hoops and if you use the QT X it will convert them at that time..

  • yeeeoww Level 1 Level 1

    Thanks for the info. I use After Effects and output Avid codec files for my Avid freinds in the bays. It certainly is nice to be able to proof the avid files coming to me with Quicklook.


    Is the idea if Avid rewrites their drivers in 64 bit it would work in QuickLook? Or is there more to this whole AV Core thingy?

  • miguel165 Level 1 Level 1

    Thanks for the info as well, it is most useful. However, as far as I see it, forcing in this way the conversion to new 64-bit codecs (if that is why all of a sudden so many files cannot be previewed nor played) is totally inappropriate.


    Moving to 64-bit should take place (in fact is taking place) gradually with the increasing use of 64-bit compatible (rather than exclusive) programs and equipments. Placing users overnight against all the problems arising from no longer being able to normally process a huge amount of files, is at the very least pretty surprising. To me, it looks like a bug, and it should be fixed.


    Imagine we no longer could handle DV files because the industry standard is HD and beyond. It would certainly make no sense. The transition to HD took place in a totally different way. Similarly, moving to 64 bits (if that is the case) should and is taking place because users and industry understand it is for the better, not because all of a sudden there is a blackout of all or many 32-bit files.

  • Deborah Terreson Level 4 Level 4

    Oh, there's probably more. I roam through the Apple developers library (A good thing to peruse if you are at all a bit interested in keeping up on current changes) and although I really do NOT understand the major aspects of coding, I can muddle my way through the release notes to *sort of* work out where they are headed.



    I imagine that as now the major emphasis is on the mobile platforms it may be a while before Apple comes up with a solution. They open only certain parts of their API's and of course once a service is into the low-level of the OS, it gets tighter controls on it for security reasons, of course.


    The AV kit seems to be fairly low-level, perhaps *just* above the machine code, certainly there are some aspects that ARE working directly with the hardware and not the OS. (I think the security protocols of Flash was one such process that went below Apple's directly to the graphics cards and was as buggy as all get out conflicting with the OS and why Apple and Adobe got stroppy with each other a few years ago.)


    I suppose I should just jump at this and learn the blasted stuff, but I really can't be bothered, when working on the actual hardware is far more satisfying for me..


    Regardless, it may be time, to start looking to third-party developers that ARE willing to tangle with the 64-bit AV core stuff.. At this point, I'm still on the fence with Mavericks and I still maintain Snow Leopard on my MacPro for the bulk of my work - I'm using it right now.


    Early Apple adopters ALWAYS are the guinea pigs.

  • Zenobius Level 1 Level 1

    "Same problem here. Crackling audio when playing MP4 through Quicktime. If I watch a music video in iTunes withn the iTunes Window it's fine but as soon as I click fullscreen the audio starts crackling. I can't Fix needed ASAP"


    I have been searching for days trying to figure this out.. And a completely different issue gave me an idea.


    APP NAP....


    Go to Applications folder, Right click on iTunes "get Info", check the box for "Prevent App Nap"

    Go back to iTunes, start video.. go fullscreen. Audio stuttering gone.


    This worked for me, hopefully it works for everyone else as well. Like I said I was searching for something else, and saw an article on App Nap... Gave it a try. boom, problem fixed with the stuttering.

Previous 1 2 3 4 5 Next