Movies keep on playing when paused/stopped

[Bellxpvu]

Let me know if you find a solution, I too am having the same problem as you.  Would be nice to not have to reset everytime we press stop. 

http://community.wdc.com/t5/General-Discussions/Can-t-play-any-videos-after-pressing-stop-on-remote/...

[MacFr]

The problem still occurs. I might give WDC a call today.

Here's also a thread:

http://forum.qnap.com/viewtopic.php?f=160&t=41697&p=201455#p201455

Keep in touch!

[TonyPh12345]

MacFr:  I think the link in your QNAP post that goes to the WDLXTV forum is the most telling.

In that thread, there was a process running on the network SOMEWHERE that caused the DMAOSD to lose contact with the RENDERER.  

On the WDTVs, DMAOSD is the "User Interface" process.   The RENDERER process is what actually processes and displays media.

When DMAOSD invokes the renderer to play a movie (regardless of where it comes from), DMAOSD basically "clears the screen" of all UI elements and gets out of the way, and let's the renderer run the show.  DMAOSD normally only gets involved with the screen during playback if the user brings up the OPTIONS menu or the status bar or whatever.

In the post you linked, DMAOSD threw out an error saying it had lost contact with the renderer.  If that happens, it has no longer has any way of knowing what the renderer is doing.   If you then press STOP, the normal menu UI will be brought back up because DMAOSD has to assume that the media DID stop.   But since it can't talk to the renderer, it cannot actually tell the RENDERER to terminate the playback. 

Therefore you get both the movie and its audio on the screen underneath the regular user interface. 

So whose fault is it?   Well, I believe it's ultimately WD's issue for two reasons:

   1- The DMAOSD process losing contact with the renderer process should be handled more gracefully.  If it needs to, it should just terminate the renderer and restart the process to restore communication.  That would not ultimately fix your problem, because you'd suffer from aborted playback all the time.   But at least your box would remain "communicative" and functional. 

   2- WHATEVER it is on your network that's CAUSING that broken process should be handled gracefully.

So, you're pretty much stuck at this point with two options as far as using the WD is concerned

   1-  Wait for a fix.   It might be a LONG TIME, if ever, because it appears to be a rather rare issue.

   2-  Track down what's happening on your network and eliminate the root cause.

My guess is you have a process running SOMEWHERE that's sending broadcasts or bad packets to the WD using the same network ports the renderer is using.

[Bellxpvu]

Thanks TonyPH12345, your help is very much appreciated.

I will try a different router and just have the media player connected to it and see if that does anything.

[MacFr]

Thanks for the response,

Maybe I should do a factory reset to clear all settings and try again. So you don't have any of these issues? And what kind of processes could disturb it? 

[imageofyou]

MacFr,

in my case there was IGMP routing enabled on the router which caused WDTV to behave erroneously. Just try to minimize the number of network active services on your network to see which one is the reason (torrents, IMs, etc)

[MacFr]

A solution has been provided by

quote:

Thanks heaven for finding this thread! I thought I had cooked my WD TV Live somehow, but I solved my problem.

I had the same symptoms as dsenseb.
First avi or mkv plays until the end, but after about 5-10 minutes, the progess bar and time indication stop working.

After that 5-10 minute point, I still can navigate file structure but a second file does not play ("unable to play the selected file").

Also, the first file (sound) plays in the background and i can go back playing it but now with blue rotating circle showing.
All this happens also on USB drives, not only on network shares.

Tried reburn Firmware 1.05.04_V, tried 1.03.49_V, tried ice packs, all to no avail...
But having read this thread, I swithed off my QNAP (TS 219, 3.4.3 Build 0520T) and after it I could play fine from USB!
So TonyPh12345 was right ("NAS is ... locking up the players because of some sort of packets it's sending on the network").

With QNAP on again, I started disabling various services and found that "UPnP Port Forwarding" is the culprit.
(MyCloudNAS Service - Auto Router Configuration - Enable UPnP Port Forwarding; uncheck this option to disable)

So anybody with similar problems, check your NAS and possibly other equipment that are trying to program your UPnP router.

[MacFr]

Thanks heaven for finding this thread! I thought I had cooked my WD TV Live somehow, but I solved my problem.

I had the same symptoms as dsenseb.
First avi or mkv plays until the end, but after about 5-10 minutes, the progess bar and time indication stop working.

After that 5-10 minute point, I still can navigate file structure but a second file does not play ("unable to play the selected file").

Also, the first file (sound) plays in the background and i can go back playing it but now with blue rotating circle showing.
All this happens also on USB drives, not only on network shares.

Tried reburn Firmware 1.05.04_V, tried 1.03.49_V, tried ice packs, all to no avail...
But having read this thread, I swithed off my QNAP (TS 219, 3.4.3 Build 0520T) and after it I could play fine from USB!
So TonyPh12345 was right ("NAS is ... locking up the players because of some sort of packets it's sending on the network").

With QNAP on again, I started disabling various services and found that "UPnP Port Forwarding" is the culprit.
(MyCloudNAS Service - Auto Router Configuration - Enable UPnP Port Forwarding; uncheck this option to disable)

So anybody with similar problems, check your NAS and possibly other equipment that are trying to program your UPnP router.

[BBBBBrandon]

---

chriswadurand wrote:

I have the BlackArmor 400 NAS and have the same problem using both File Share and DNLA access.

How do we raise this as a bug and request it to be fixed?

Thanks

Chris

---

Have you updated your Black Armor to the latest firmware update?  We cannot reproduce this problem any further with the latest Black Armor update.