DustyStorm

Q: Netflix quality HORRID after update

I made the mistake of updating to latest firmware, 6.0.2. Ever since, Netflix quality *****. SuperHD used to be so sharp and crisp. Now it's pixelated and NOT hd in the least bit!

 

How can I undo the software change? Has anyone else had this issue?

Posted on Nov 15, 2013 7:17 PM

Close

Q: Netflix quality HORRID after update

  • All replies
  • Helpful answers

first Previous Page 31 of 91 last Next
  • by boylan,

    boylan boylan Dec 9, 2013 9:28 AM in response to Markus Wernig
    Level 1 (0 points)
    Dec 9, 2013 9:28 AM in response to Markus Wernig

    My problem turns out is the comcast-netflix conflict as I'm getting the same 235kbps garbage on any device and computer and have been since around 11/11 which I believe is the date of the Netflix OpenConnect roll-out.

     

    Of course, I can stream everything else from Amazon to PBS at HD.

  • by dvanhou,

    dvanhou dvanhou Dec 9, 2013 9:46 AM in response to Hankfromnh
    Level 1 (0 points)
    Dec 9, 2013 9:46 AM in response to Hankfromnh

    Don't bother.  It didn't work.  Back to it's old tricks by noon.  Calling Netflix again.  Apple insists they know nothing about this being a problem. 

  • by Dave_K.,

    Dave_K. Dave_K. Dec 9, 2013 9:53 AM in response to jimpal
    Level 3 (609 points)
    Desktops
    Dec 9, 2013 9:53 AM in response to jimpal

    jimpal wrote:

     

    dvanhou wrote:

     

    With both devices off, unplug the HDMI cable from your ATV and TV, turn the cable around and plug it back in (so the end that was in the ATV is now in your TV and vice versa).

    Thanks for sharing this. Perhaps it gives us all some insight into how seriously Netflix reps view this problem.

     

    Does this mean after I do this to see Netflix properly, I have to reverse the cable again to receive all the other stuff on my Apple TV I've been watching for the last three years with beautiful results? Are you sure there wasn't some hee-heeing going on at the Netflix end of the line when they told you to do this?

     

     

    Oh dear I agree- I fear the Netflix rep was having some fun at Dvanhou's expense.   Probably the guy in the cube next to him said "20 bucks says I can get the next caller to unplug an HDMI cable and reverse it".   Sorry it came to that.

     

    Dave

  • by boylan,

    boylan boylan Dec 9, 2013 9:58 AM in response to Dave_K.
    Level 1 (0 points)
    Dec 9, 2013 9:58 AM in response to Dave_K.

    I'm sure the person at Netflix wasn't deliberately winding up Dvanhou - they probably just

    didn't know what they were talking about and may have previously solved something like a loose

    cable or damaged cable problem by reversing it.

  • by dvanhou,

    dvanhou dvanhou Dec 9, 2013 10:12 AM in response to Dave_K.
    Level 1 (0 points)
    Dec 9, 2013 10:12 AM in response to Dave_K.

    Tough crowd.  If the caustic ones want more food for fodder, I called Netflix again and they were sent me the boilerplate email "Troubleshoot Network Connection Issues."  If you want me to include it here I can. 

     

    They also it's either an ATV issue or Comcast.  Finger pointing all around. 

     

    Have a great day despite it all.

  • by Vandergraff,

    Vandergraff Vandergraff Dec 9, 2013 10:32 AM in response to boylan
    Level 1 (15 points)
    Dec 9, 2013 10:32 AM in response to boylan

    boylan wrote:


    and have been since around 11/11 which I believe is the date of the Netflix OpenConnect roll-out.

     

    Netflix opened up Super HD for non Open Connect ISPs 26th September

     

    http://www.theverge.com/2013/9/26/4774732/netflix-super-hd-1080p-now-available-o n-all-isp

  • by J.N.L,

    J.N.L J.N.L Dec 9, 2013 10:46 AM in response to DustyStorm
    Level 1 (0 points)
    Dec 9, 2013 10:46 AM in response to DustyStorm

    I doubt its Comcast, I am an upstate NY Time Warner Road Runner Cable ISP subscriber with roughly 20/2 mbit. I have QOS set up with highest priority to my Apple TV 3.

     

    Ever since the last update Netflix runs poorly as described, at ALL times of day. Starts in HD, and drops to awful, blurry within seconds. So bad I cant read license plates or signs on Wilfred etc. Occasionally bumps up to decent compressed SD, and then back to the dumps.

     

    I have reset my network settings, reset the router, reconfigured DNS, and even did a total "factory" reset. The problems persist. I even put it into DFU mode and reset it via USB via iTunes. (it wouldnt let me revert to a previous ipsw obviously, but had to try). No luck.

     

    HOPEFULLY someone at Apple/Netflix fixes this soon.

     

    Considering trying to exchange it at Target with receipt, I bet the one on the shelf has fw version 5 or 6.0.1 or something.

     

    Also I would like to see that Time Warner app soon to replace the cable box, like your competitors have, between that and netflix.... getting tempted to go R0ku....

  • by boylan,

    boylan boylan Dec 9, 2013 11:00 AM in response to Vandergraff
    Level 1 (0 points)
    Dec 9, 2013 11:00 AM in response to Vandergraff

    Vandergraff wrote:

     

    boylan wrote:


    and have been since around 11/11 which I believe is the date of the Netflix OpenConnect roll-out.

     

    Netflix opened up Super HD for non Open Connect ISPs 26th September

     

    http://www.theverge.com/2013/9/26/4774732/netflix-super-hd-1080p-now-available-o n-all-isp

    Definitely appeared roughly around the 11th.  For a few days we were successful switching to a mac mini

    for streaming and then that too started yielding super low res - 235kbps stream using their example 23.xxx

    video.

     

    So the only announced change on the 11th was their new UI?  Obviously not directly related to that.

    Maybe it just got cold :-)

     

    Normally when this happens we can bypass the problem using a computer, mac mini, switching to a

    Roku which performs better with marginal bandwidth, but this time everything is impacted.

     

    Again, running Comcast who is an OpenConnect hold-out according to what I've read.

  • by boylan,

    boylan boylan Dec 9, 2013 11:09 AM in response to boylan
    Level 1 (0 points)
    Dec 9, 2013 11:09 AM in response to boylan

    Hey, has anyone tried testing a VPN service like "Hide My A...", to see if that defeats this problem?  Particularly those that are seeing this on Comcast?  I just dropped my subscription and would have to renew just for a test.

  • by J.N.L,

    J.N.L J.N.L Dec 9, 2013 11:22 AM in response to boylan
    Level 1 (0 points)
    Dec 9, 2013 11:22 AM in response to boylan

    RESOLVED!

     

    I was thinking this may have started after the "Super HD" rollout, and I wondered if Netflix is having a hard time determining what the end device is capable of displaying. I checked Netflix_com and under Playback Settings Data Usage was set to Auto. I changed it to High (HD video quality...) and voila! Now the default stream is HD.

    netflix.jpg

    For all my testing I watched a "Super HD" episode of Wilfred.I am getting a good 720p picture now, albeit with some compression. I still feel the quality was better before the issue started, I will update with any other results.

  • by Tony Ramirez,

    Tony Ramirez Tony Ramirez Dec 9, 2013 11:12 AM in response to boylan
    Level 1 (5 points)
    Dec 9, 2013 11:12 AM in response to boylan

    My problems started on November 9th.  Tried to watch Eureka the other night and it would not go to HD no matter how many times I restarted it.  On my PS3 and Roku 3 I do sometimes have to restart the stream a few times when it won't get HD and plays at that godawful worthless 240p junk but then it does lock in around 30 seconds.

     

    I know a simple fix for Netflix.  Get rid of those worthless trash 240p, 288p and 384p encodes that are only worth watching on 1/2 inch wrist watch screen.

     

    Also I have mine set to High.  It does not make a difference.

  • by Vandergraff,

    Vandergraff Vandergraff Dec 9, 2013 11:20 AM in response to boylan
    Level 1 (15 points)
    Dec 9, 2013 11:20 AM in response to boylan

    boylan wrote:

     

    Definitely appeared roughly around the 11th.  For a few days we were successful switching to a mac mini

    for streaming and then that too started yielding super low res - 235kbps stream using their example 23.xxx

    video.

     

    It started on November 11th for me as well.

  • by boylan,

    boylan boylan Dec 9, 2013 11:40 AM in response to Tony Ramirez
    Level 1 (0 points)
    Dec 9, 2013 11:40 AM in response to Tony Ramirez

    Tony Ramirez wrote:

     

    My problems started on November 9th.  Tried to watch Eureka the other night and it would not go to HD no matter how many times I restarted it.  On my PS3 and Roku 3 I do sometimes have to restart the stream a few times when it won't get HD and plays at that godawful worthless 240p junk but then it does lock in around 30 seconds.

     

    I know a simple fix for Netflix.  Get rid of those worthless trash 240p, 288p and 384p encodes that are only worth watching on 1/2 inch wrist watch screen.

     

    Also I have mine set to High.  It does not make a difference.

     

    I completely agree.  There is no reason to support these low res encodings.  Realistically, how many people are really using 480p?  The Wii users should upgrade.

     

    I'd rather have my streaming locked to a resolution and if I have to wait 10-20 minutes while it buffers so what.

     

    I've been unable to find anything definitive with Google but clearly there are a lot of forums filled with PO'ed users starting about the 10th or so.

  • by Markus Wernig,

    Markus Wernig Markus Wernig Dec 9, 2013 11:51 AM in response to boylan
    Level 1 (20 points)
    Dec 9, 2013 11:51 AM in response to boylan

    boylan wrote:


    I completely agree.  There is no reason to support these low res encodings.  Realistically, how many people are really using 480p?  The Wii users should upgrade.

     

    I'd rather have my streaming locked to a resolution and if I have to wait 10-20 minutes while it buffers so what.

     

    Netflix needs these low resolutions because their streaming technology doesn't work like YouTube, where you pick a resolution and you just have to wait until most of the video has been downloaded.

     

    Netflix only buffers a short amount and relies on "adaptive streaming" to deliver a constant signal. Waiting for 10-20 minutes wouldn't solve anything. If there is a congestion somewhere in your delivery line (ISP / Netflix side) and they didn't have these lower resolutions to fall back on, you'd be spinning every few seconds and never get to watch anything.

     

    Again - these super low resolutions (240p for example) are not normal on a device like the Apple TV with a fast Internet connection. They'll fix this hopefully sooner than later.

     

    At this point, calling Apple and demanding to speak to a level 2 customer service rep seems to make the most sense.

  • by boylan,

    boylan boylan Dec 9, 2013 12:02 PM in response to Markus Wernig
    Level 1 (0 points)
    Dec 9, 2013 12:02 PM in response to Markus Wernig

    Markus Wernig wrote:

     

    boylan wrote:


    I completely agree.  There is no reason to support these low res encodings.  Realistically, how many people are really using 480p?  The Wii users should upgrade.

     

    I'd rather have my streaming locked to a resolution and if I have to wait 10-20 minutes while it buffers so what.

     

    Netflix needs these low resolutions because their streaming technology doesn't work like YouTube, where you pick a resolution and you just have to wait until most of the video has been downloaded.

     

    Netflix only buffers a short amount and relies on "adaptive streaming" to deliver a constant signal. Waiting for 10-20 minutes wouldn't solve anything. If there is a congestion somewhere in your delivery line (ISP / Netflix side) and they didn't have these lower resolutions to fall back on, you'd be spinning every few seconds and never get to watch anything.

     

     

    I'm aware.

     

    Netflix made a design decision about people's preference of waiting vs. reduced quality that I don't agree with.

    We've quit streaming while this problem is on-going.  I'm starting to think about paying the extra money to watch things off of iTunes.

first Previous Page 31 of 91 last Next