ozemari berneta philothea
Tina Popielarczyk
You could try a factory reset of the box just select the option to keep your recordings, (you will need to sign in again to your apps), some user's have had a problem with the match frame rate try turning it off if set to on.
Hi @walneyhammer Thanks for reaching out to us and a warm welcome to the Virgin Media Community Forums.
I'm sorry to hear about the issues with the Netflix services you are having.
May I ask if the advice on the forums thread has assisted you or are you still experiencing the same issue?
Let us know and we can go on from there.
Kind regards.
Nothing I have tried has helped unfortunately. It happens every single time now. If I open Netflix then the screen freezes on the netflix logo. Once I power the box down and back up again then I can get into Netflix, but the next time I try it freezes again.
In any case, I have been isolate 1 of the problems and I can crash all the yamaha
receivers every time without fail. I mean every time. I think there are more problems with the IP stack on the receivers.
I have taken everything off my network except the yamaha , my pc and my
ipad.
I use wireshark to trace the network traffic.
I can turn the yamaha on and just do a ping from my PC. No streaming, no nothing. Just a simple ping.
I then go to my ipad and launch netflix. The first thing that Netflix does
is an MDNS broadcast message
to 224.0.0.251 and on the ipv6 stack to ff02::fb
After that the the yamaha receiver network stops responding to ping. You
can't ping it. The only
way to get it alive again is to power cycle this.
I can do this over and over again.
Don't hold your breath. I've been waiting for a response from Yamaha and C4 for months. There are (at least) two problems. There is a logic problem in the C4 driver and (I'm almost certain) a problem with the Yamaha firmware/hardware.
I have a Yamaha RX-v673 (firmware 1.91) that had been working fine for as long as I know, but recently (not sure exactly when - perhaps a few months ago?), I discovered that whenever I stream Netflix from an iOS device (iPhone or iPad - happens to be running iOS 9.3 now) through an Apple Airport Extreme, I am seeing my RX-v673 completely drop off the network (which I can observe by watching the Network Information screen). It's not like it just loses its IP address (as if the network cable was unplugged), but seems to lose the network interface completely, with the connection status changing to "Please Wait..." and the MAC address and network name not even being displayed (unlike when the network cable is removed). As soon as I terminate the Netflix app on the iOS device, the network functionality returns.
Thinking that the Netflix app was impacting my wired router (connected to my cable modem) in some way, I even swapped the router out, with no change. I have pulled off every other network device from my network except the RX-v673, and an Apple Airport Extreme (to serve as a wireless access point for the iOS device), and can still reproduce. This doesn't happen with any other device (e.g., PC, Android tablet) or with any other streaming media app (e.g., amazon video, YouTube, etc) - just Netflix running on an iOS device. I have had no issues with any other devices (C4, apple airport extreme, my netgear router, etc.) until I encountered and narrowed down this issue. The one thing that I have yet to try is to swap out the airport extreme, but it's next on my list to do (probably can test on Monday)...
I can reproduce this 100% of the time, and happens within 10-20 seconds consistently.
Repro steps are really easy:
- display the Network Information screen from the onscreen GUI
- start the latest Netflix app on an iPad (for example)
- stream any show
- observe that the RX-V673 loses network functionality
- quit/close the Netflix app on the iPad
- observe that the network functionality returns
I have observed that the RX-V673 has the network issue even by just launching the Netflix app, but it seems to happen quicker if streaming is started.
Yamaha had never heard of this, and Netflix had no clue. I did hear from another RX-V673 owner, and he didn't see the same issue, so it's not generic to just the Yamaha and/or netflix.
Of course, when the above happens, C4 can't see the Yamaha receiver, so can't control it (as has been reported in this thread).
So, for those that are experience an issue with C4 not being able to communicate with the Yamaha receiver at times, try pulling up the Network Information Screen GUI on your Yamaha receiver - what it shows/does when connectivity is lost? I did not see any owners reference this screen in any posts on this thread (unless I missed them). This will also tell you whether it's C4 that is having a problem, or whether the Yamaha receiver is getting into a weird state...
I'm glad to hear this, but it also pisses me off. I wrote the Yamaha person in charge with detailed info in December. My dealer opened up s problem with C4 in January after dragging their feet by saying my dealer had to be on site before they would do anything. I had weeks of logging info - C4 didn't want any of it and blew off the problem. I haven't heard anything from anyone in three months - nothing from Yamaha, my dealer or C4. I spent considerable time (and bought new C4 equipment) to work around this problem and had to pay my dealer for his time involved in doing all the stuff C4 said we had to do (swapping a bunch of drivers, coming to my house, changing ports etc. - all things I explained would have NO impact)) and got NOTHING for it other than the privilege of spending hundreds of dollars for nothing.
Matt, please tell Yamaha and C4 it's more than a Yamaha firmware issue. There is also a logic bug in the Yamaha drivers that results in C4 endlessly looping to the point it will bring the controller (or at least an HC-800) to the its knees, requiring a reboot to recover and, depending on timing, the driver will see the receiver offline even after the receiver is back online.
I just checked in with the AMX dealer that was having the same issue with two Yamaha receivers I mentioned in a previous post. He said the system would work fine for awhile then the entire network would experience issues. He would see all the failed devices with Greenlight, but got tired of rebooting the receivers every 2-3 days via GL. He told me that he changed control from IP to 232 a month ago and there has been no issues whatsoever. I am going to agree with everyone that said its a Yamaha issue and they need to address it. This has to be affecting thousands of people and I can't believe it hasn't been addressed.
The network develops problems because of the Yamaha driver bug(s) not as a direct result of the Yamaha firmware issue. This problem will exist in some form until the underlying issues are fixed in both the firmware and drivers.
I believe fixing the cause of the network port shutting down will significantly reduce the issue, but until the driver can deal with (or even report) an unexpected connection state, there is a potential for the driver to bog the controller down to the point of failure. In that event, the only way to recover is to reboot the receivers and then reboot the controller.
As an update, I have been in touch with both Netflix and Yamaha. Netflix is looking into the issue, and I should hear back by end of week about eta for a fix. I found that the Netflix app sends out more than one SSDP M-SEARCH request, and the second form of the request is correctly formed, so doesn't affect the Yamaha receiver. However, if I modify the second SSDP request to match the "bad" form that the Netflix iOS app uses, then the Yamaha receiver will drop off the network. The Yamaha receiver actually sends out an SSDP M-SEARCH request itself, but it is formed correctly (so no issue).
- Because of the type of bug (just a syntax issue for a parameter), it would not surprise me in the least if other apps may have a similar bug, or other network devices themselves may send out a malformed SSDP M-SEARCH requests that could cause the Yamaha receiver to encounter the same issue (for customers not using Netflix, this may be what is happening on their network). It's very easy to identify this case if you are able to capture packet traffic on your network (I can describe if anyone cares).
So, hopefully Yamaha will step up and more gracefully handle the bad packet case on their end, solving this problem once and for all on their side. Will see what they say when they review the info that I sent them. I'll also report back when i hear that Netflix fixed the bug on their end.
UPDATE: Sure enough... The Yamaha RX-V673 receiver uses a BridgeCo DM860A Networked Media Processor chip (refered to as a JukeBlox) manufactured by MicrochipTechnology, Inc., and the Marantz AV7702mkii uses a Microchip Technology CY920 module - both modules provide network functionality along with multimedia capability. So, it makes sense that these devices have the same problem...
I'm wondering if Pioneer can be affected by the same issue. I have multiple Pioneer AVRs and they have been pretty solid on IP control for years--until the past few months. Now I have to reboot one quite frequently (it was daily for a while), and others less often.
It would not surprise me at all. Do you use netflix on an ios device? If so, then yep. What i am curious about is what other apps have a similiar bug for those thst don't use netflix, but are having a similar problem? I have been having network flakiness with a projector, snd it eould not surprise me that if it was affected as well.
90f70e40cf