14 DAY TRIAL // A number of Mac users writing over at the Apple Support Communities forum are suggesting that OS X 10.10.1 has delivered some bugs along with the promised fixes. Safari users, for instance, can’t seem to be able to play YouTube content properly following the update.
The problem does appear to be widespread, with 4,000 views currently attributed to this post, and 78 replies at the time of writing. Safari has a small market-share, and this is probably not the only place on the web where this issue is being discussed, so these numbers are quite indicative that YouTube, Safari and Yosemite 10.10.1 don’t play well together.
What the users are saying
Most reports sound about the same. Thread starter MoXoM conveys his story to fellow forum users:
“I installed Yosemite on my iMac (20-inch, Mid 2007) when it was first released and I had no issues whatsoever. Last night I updated Yosemite to 10.10.1 and now all of a sudden Safari Version 8.0 (10600.1.25.1) won't play any YouTube videos. All I get is a black screen with a little audio clipping. When using Firefox (v32.1.1) or Chrome (v38.0.2125.122) everything works ok.”
The replies that ensued paint a clear picture about the circumstances in which YouTube no longer works as expected. The cause lies somewhere between the Safari web browser, YouTube’s streaming algorithms, and the latest OS X update from Cupertino.
However, it’s also worth noting that the problems started only recently for these users, and it isn’t clear if they all installed 10.10.1 as late as the thread starter. The update has been available for five days now, so any reports involving crippled YouTube on Safari should have hit the web a lot earlier.
YouTube could be at fault
The natural conclusion here is that YouTube could be just as responsible for the problems, and that Apple might not even have to lift a finger this time around.
Google might be required to do some server-side maintenance to see what’s causing conflicts when Yosemite users are trying to stream video on their newly-updated Macs through Safari.
On the other hand, if Apple discovers that the problem is their responsibility - i.e. inherent to Safari - the Cupertino company could be prompted to update its web browser and release a standalone patch that users can download and apply manually.
Has anyone here had similar issues after updating to 10.10.1? Leave your thoughts in the comments section below.
