Currently Being ModeratedJul 30, 2012 4:39 PM (in response to TStam)
I had flawless streaming in Lion. Now that I have Mountain Lion it's choppy and slow. Netflix needs to either change the plugin they use (HTML 5, please) or Microsoft (Doubtful they'll care at all) needs to upgrade Silverlight. It's peculiar that Netflix even uses Silverlight. Hardly anyone has ever used it or still uses it.
Currently Being ModeratedJul 30, 2012 5:23 PM (in response to mahongue)
I'm also running Silverlight 5.1. It I believe comes down to memory management. Safari and it's associated processes are sucking up nearly 1GB of RAM. Add that to around 250MB's being taken up by the Silverlight plugin. It's too much for the plugin and Safari to work in sync with any kind of fluidity.
Hopefully there'll be an update to Silverlight to bump up the hardware acceleration for new drivers and plugins associated with Mountain Lion.
Currently Being ModeratedAug 17, 2012 8:03 PM (in response to TStam)
I wrestled after updating to mountain lion, and what ailed me seems so oddly simple and preventable.
I went to chrome:plugins and saw that silverlight had been updated but was not enabled! That is why it kept asking.
Thank you for the leads from Tstam and others here. Hope that helps someone.
Currently Being ModeratedAug 26, 2012 12:10 PM (in response to TStam)
TStam - I followed your advice and it worked perfectly.
For any other novices like me, you can do a spotlight search for "Internet Plug-Ins" to find the plug in called silverlight in that folder.
I can't believe Netflix's whole advice was "Don't use HD" and "Call your computer manufacturer". LOL
Currently Being ModeratedSep 12, 2012 4:13 PM (in response to TStam)
Currently Being ModeratedSep 13, 2012 2:35 AM (in response to JustinDuke)
I've found Silverlight to be resource intensive, but version 5 is supposed to be less so than version 4. Is there anything else running in activity monitor, such as the Spotlight Indexing process? I have a 2008 mac pro with 8 cores and 32 gig of ram and while Silverlight doesn't slow it down much, the fan speeds up a bit when displaying HD in a fairly large window.
For what it's worth, Elgato EyeTv HD displaying 720p in a decent sized window does the same thing and has nothing to do with Silverlight. At the end of the day your computer is decompressing a lot of data to display HD video on your screen and it takes some work to do it.
Interested in hearing from others on this.
Currently Being ModeratedSep 13, 2012 6:33 AM (in response to TStam)
Spotlight isn't running. I've gone through all the processes. In Lion (10.7) cpu use by silverlight never went over 60%. I am going to try a reinstall of mountain lion today, let you knwo how that goes.
Currently Being ModeratedSep 30, 2012 1:04 AM (in response to TStam)
Anybody found that MS Silverlight is the culprit for slowing sown Mountain Lion, esp on shutdown? Upgraded to ML no problem and alsoI had a personal policy of no Microsoft software on my mac.(one of the reasons for converting to mac from ms was that I was sick of ms conflicts and endless security updates).
recently decided to upgrade to last version of Flip for mac and the installer for that also had option to install silverlight. Should not have been tempted. Post-silverlight install was when hasd shut down times extended. Didn't immediately twig. Uninstalled silverlight and mac immediately back to previous speeds. Lived without silverlight for 18 months beforehand so cannot see what it adds. Have resumed no MS software on my mac policy.
Currently Being ModeratedNov 10, 2012 3:38 PM (in response to TStam)
What people need to do is make/convert their sites to HTML5 instead of using silverlight or flash.
Also, netflix should create an OS X app so that we can use our Apple Remote as well rather than having to scroll around with the mouse.
Currently Being ModeratedDec 15, 2012 8:01 AM (in response to Dhruv3)
An OS X app would be fantastic, or html5.
It might have taken over an hour to find the right way to uninstall so it would let me reinstall, instead of saying there was a more recent version somewhere and blocking reinstall.
These are the instructions that did it.