Cannot remote play serviio videos to WDTVLive

Cannot play (remote) serviio videos to WDTVLive

On my best days most everything in the home network works except I cannot play videos served by Serviio (1,21) to my WDTVLive (1.15.10) using Android (4.03) BubbleUpnp (402 errors), MediaHouse (Unable to Play -1), and now ArkMC (no message).

Using our program, Servi-go, play via Bubble fails to the WDTVLive, same message, but play via Beam (latest 'Twonky' )to play to the WDTVLive does work, and is the only way I can play videos 'remote' using the tablet off serviio to the WDTVLive.

I can send a serviio video file to the XBMC renderer just about anyhow. I can send a Serviio MP3 file anywhere, including WDTVLive (but sending a flac file won't go to WDTVLive, Flac/Wav etc. does play on Foobar/XBMC). So I wonder how much the problem is a format problem. I've tried disabling mime checks whereever I can and with and without transcoding in the serviio server, no better results.

When a to-fail Serviio video is sent In most cases whatever is playing on the WDTVLive stops, the error message appears on the tablet, then whatever was playing starts playing again.

I'm wondering if others have this problem or it has been solved.

[slyguy42o]

post a copy of your server logs after a play back failiure and we will see if that can tell us why it's failing.

I got through "test run #3" tonight. I'll have to get better at turning off both library updates and, it appears, metadata processing/extraction before I'll do a fourth run. I'm seeing a large number of warnings mostly it seems about having non-dates in year headers, etc, I think, that deserve some investigation later. However, I think I culled the pertinent messages from the log (run #3 and run 2) and await feedback before trying again.

The chosen test movie, it became apparent, is (inadvertant) in a directory that is set for metadata extraction but is one of a few NOT expected to have its own metadata in an online resource. I'd certainly think this would not affect anything. And I am sure, I will have to check, the problem happens for movies metadat'd and with it. I will make a note in passing that I saw some really strange things over a week ago with playing serviio files on the WDTVLive in regards to "playing" metadata instead of the video (they went away) and I have no other feedback on that.

My suspicion is it has something to due with metadata management between Serviio and WD.

Serviio was started. Transcoding was off. WDTVLive was turned off/on again. Basically, vereything I saidin my original post was rerun. The chosen test movie was successfully played on the XBMC renderer or played off other servers to WDTVLive successfully and the only way it was played successfully remotely off of Serviio server was 1) if it was the first media sent to WDTVLive (sometimes) and 2) off Serviio Go by way of BEAM (twonky).








From RUN 3 Serviio log ...

2013-05-05 22:42:43,311 INFO [WebServer] WebServer starting on port 8895
2013-05-05 22:42:43,311 INFO [EventSubscriptionExpirationChecker] Starting EventSubscriptionExpirationChecker
2013-05-05 22:42:43,311 INFO [EventDispatcher] Starting EventDispatcher
2013-05-05 22:42:43,311 INFO [DiscoveryAdvertisementNotifier] Starting DiscoveryAdvertisementNotifier
2013-05-05 22:42:43,384 INFO [DiscoverySSDPMessageListener] Starting DiscoverySSDPMessageListener using interface eth3 (Broadcom NetLink (TM) Gigabit Ethernet) and address 192.168.1.40, timeout = 0
2013-05-05 22:42:43,385 INFO [RendererSearchSender] Searching for Renderer devices
2013-05-05 22:42:43,481 INFO [RendererManager] Stored a new renderer: uuid='3f6005c4-57ef-bd80-9ff9-ac521ec3add2', name = 'XBMC Media Center', ipAddress='192.168.1.40', profile = '1'
2013-05-05 22:42:44,401 INFO [RendererManager] Stored a new renderer: uuid='48e25832-71c7-8395-7e99-5c15c4ff0b06', name = 'foobar2000 Media Renderer', ipAddress='192.168.1.40', profile = '1'
2013-05-05 22:42:45,401 INFO [RendererManager] Stored a new renderer: uuid='3f6005c4-57ef-bd80-9ff9-ac521ec3add2', name = 'XBMC Media Center', ipAddress='192.168.1.40', profile = '1'
2013-05-05 22:42:45,416 INFO [RendererManager] Stored a new renderer: uuid='48e25832-71c7-8395-7e99-5c15c4ff0b06', name = 'foobar2000 Media Renderer', ipAddress='192.168.1.40', profile = '1'
2013-05-05 22:42:45,429 INFO [RendererManager] Stored a new renderer: uuid='3f6005c4-57ef-bd80-9ff9-ac521ec3add2', name = 'XBMC Media Center', ipAddress='192.168.1.40', profile = '1'

MY NOTE HERE IT LOOKS LIKE SERVIIO HAPPENED TO GO BY THE "TEST MOVIE" Santana Diving - Burma Dive Safari.mp4. ("Flash avi was not used at all)

2013-05-05 23:02:14,826 WARN [OnlineVideoSourcesMetadataExtractor] Online metadata search returned no results for file Santana Diving - Burma Dive Safari (Santana 03-2004 - 320 x 240).mp4 [VideoDescription [type=FILM, names=[santana diving burma dive safari (santana 03, burma dive safari], year=2004, season=null, episode=null]]
2013-05-05 23:02:15,392 INFO [LibraryUpdatesCheckerThread] Updated 'Santana Diving - Burma Dive Safari (Santana 03-2004 - 320 x 240)' (\\MYBOOKLIVE\Media\_Movies_SD\Burma Dive Safari (2004 archived)\Santana Diving - Burma Dive Safari (Santana 03-2004 - 320 x 240).mp4) in Library
2013-05-05 23:02:16,604 WARN [OnlineVideoSourcesMetadataExtractor] Online metadata search returned no results for file Santana Diving - Burma Dive Safari.mp4 [VideoDescription [type=FILM, names=[santana diving burma dive safari, burma dive safari], year=2004, season=null, episode=null]]
2013-05-05 23:02:16,702 INFO [LibraryUpdatesCheckerThread] Updated 'Santana Diving - Burma Dive Safari' (\\MYBOOKLIVE\Media\_Movies_SD\Burma Dive Safari (2004 archived)\Santana Diving - Burma Dive Safari.mp4) in Library
2013-05-05 23:02:19,152 WARN [LibraryManager] Extractor ONLINE_VIDEO_SOURCES failed to connect to metadata source for file \\MYBOOKLIVE\Media\_Videos_TV\Flash.Gordon 7.5 Gb\Flash.Gordon.S01E19.DSR.XviD.avi, will try again later: Error connecting to thetvdb.com: http://thetvdb.com/api/235C8CA4529142E9 ... /19/en.xml
2013-05-05 23:02:19,260 INFO [LibraryUpdatesCheckerThread] Updated 'Flash.Gordon.S01E19.DSR.XviD' (\\MYBOOKLIVE\Media\_Videos_TV\Flash.Gordon 7.5 Gb\Flash.Gordon.S01E19.DSR.XviD.avi) in Library
2013-05-05 23:02:21,588 WARN [LibraryManager] Extractor ONLINE_VIDEO_SOURCES failed to connect to metadata source for file \\MYBOOKLIVE\Media\_Videos_TV\Flash.Gordon 7.5 Gb\Flash.Gordon.S01E17.DSR.XviD.avi, will try again later: Error connecting to thetvdb.com: http://thetvdb.com/api/235C8CA4529142E9 ... /17/en.xml
2013-05-05 23:02:21,642 INFO [LibraryUpdatesCheckerThread] Updated 'Flash.Gordon.S01E17.DSR.XviD' (\\MYBOOKLIVE\Media\_Videos_TV\Flash.Gordon 7.5 Gb\Flash.Gordon.S01E17.DSR.XviD.avi) in Library
2013-05-05 23:02:23,566 WARN [LibraryManager] Extractor ONLINE_VIDEO_SOURCES failed to connect to metadata source for file \\MYBOOKLIVE\Media\_Videos_TV\Flash.Gordon 7.5 Gb\Flash.Gordon.S01E03.DSR.XviD.avi, will try again later: Error connecting to thetvdb.com: http://thetvdb.com/api/235C8CA4529142E9 ... 1/3/en.xml
2013-05-05 23:02:23,626 INFO [LibraryUpdatesCheckerThread] Updated 'Flash.Gordon.S01E03.DSR.XviD' (\\MYBOOKLIVE\Media\_Videos_TV\Flash.Gordon 7.5 Gb\Flash.Gordon.S01E03.DSR.XviD.avi) in Library
2013-05-05 23:02:25,698 WARN [LibraryManager] Extractor ONLINE_VIDEO_SOURCES failed to connect to metadata source for file \\MYBOOKLIVE\Media\_Videos_TV\Flash.Gordon 7.5 Gb\Flash.Gordon.S01E02.DSR.XviD.avi, will try again later: Error connecting to thetvdb.com: http://thetvdb.com/api/235C8CA4529142E9 ... 1/2/en.xml
2013-05-05 23:02:25,772 INFO [LibraryUpdatesCheckerThread] Updated 'Flash.Gordon.S01E02.DSR.XviD' (\\MYBOOKLIVE\Media\_Videos_TV\Flash.Gordon 7.5 Gb\Flash.Gordon.S01E02.DSR.XviD.avi) in Library
2013-05-05 23:02:27,613 WARN [LibraryManager] Extractor ONLINE_VIDEO_SOURCES failed to connect to metadata source for file \\MYBOOKLIVE\Media\_Videos_TV\Flash.Gordon 7.5 Gb\Flash.Gordon.S01E04.DSR.XviD.avi, will try again later: Error connecting to thetvdb.com: http://thetvdb.com/api/235C8CA4529142E9 ... 1/4/en.xml
2013-05-05 23:02:27,667 INFO [LibraryUpdatesCheckerThread] Updated 'Flash.Gordon.S01E04.DSR.XviD' (\\MYBOOKLIVE\Media\_Videos_TV\Flash.Gordon 7.5 Gb\Flash.Gordon.S01E04.DSR.XviD.avi) in Library
2013-05-05 23:02:29,453 WARN [LibraryManager] Extractor ONLINE_VIDEO_SOURCES failed to connect to metadata source for file \\MYBOOKLIVE\Media\_Videos_TV\Flash.Gordon 7.5 Gb\Flash.Gordon.S01E15.DSR.XviD.avi, will try again later: Error connecting to thetvdb.com: http://thetvdb.com/api/235C8CA4529142E9 ... /15/en.xml
2013-05-05 23:02:29,580 INFO [LibraryUpdatesCheckerThread] Updated 'Flash.Gordon.S01E15.DSR.XviD' (\\MYBOOKLIVE\Media\_Videos_TV\Flash.Gordon 7.5 Gb\Flash.Gordon.S01E15.DSR.XviD.avi) in Library
2013-05-05 23:02:32,691 WARN [LibraryManager] Extractor ONLINE_VIDEO_SOURCES failed to connect to metadata source for file \\MYBOOKLIVE\Media\_Videos_TV\Flash.Gordon 7.5 Gb\Flash.Gordon.S01E21.DSR.XviD.avi, will try again later: Error connecting to thetvdb.com: http://thetvdb.com/api/235C8CA4529142E9 ... /21/en.xml
2013-05-05 23:02:32,746 INFO [LibraryUpdatesCheckerThread] Updated 'Flash.Gordon.S01E21.DSR.XviD' (\\MYBOOKLIVE\Media\_Videos_TV\Flash.Gordon 7.5 Gb\Flash.Gordon.S01E21.DSR.XviD.avi) in Library
2013-05-05 23:02:34,144 WARN [LibraryAdditionsCheckerThread] Cannot add file 06 - billy's got a gun.mp3 because of an unexpected error. Message: For input string: "Augu"

2013-05-05 23:05:59,802 WARN [ResourceDeliveryProcessor] Invalid request, sending back 400 error
org.serviio.upnp.protocol.http.transport.InvalidResourceRequestException: Invalid incoming request: /resource/149858/MEDIA_ITEM/MPEG4_P2_MP4_ASP_AAC-0
at org.serviio.upnp.protocol.http.transport.RequestedResourceDescriptor.<init>(RequestedResourceDescriptor.java:73)
at org.serviio.upnp.protocol.http.transport.AbstractProtocolHandler.getRequestedResourceDescription(AbstractProtocolHandler.java:35)
at org.serviio.delivery.ResourceDeliveryProcessor.deliverContent(ResourceDeliveryProcessor.java:65)
at org.serviio.upnp.webserver.ResourceTransportRequestHandler.handleRequest(ResourceTransportRequestHandler.java:85)
at org.serviio.upnp.webserver.AbstractRequestHandler.handle(AbstractRequestHandler.java:61)
at org.apache.http.protocol.HttpService.doService(HttpService.java:293)
at org.serviio.upnp.webserver.ServiioHttpService.doService(ServiioHttpService.java:77)
at org.apache.http.protocol.HttpService.handleRequest(HttpService.java:212)
at org.serviio.upnp.webserver.WebServer$WorkerThread.run(WebServer.java:192)
Caused by: java.lang.ArrayIndexOutOfBoundsException: 3
at org.serviio.upnp.protocol.http.transport.RequestedResourceDescriptor.<init>(RequestedResourceDescriptor.java:70)
... 8 more
2013-05-05 23:06:43,388 INFO [DiscoveryAdvertisementNotifier] Leaving DiscoveryAdvertisementNotifier
2013-05-05 23:06:43,388 INFO [DiscoverySSDPMessageListener] Leaving DiscoverySSDPMessageListener
2013-05-05 23:06:43,388 INFO [WebServer] WebServer shutting down
2013-05-05 23:06:43,389 INFO [EventDispatcher] Leaving EventDispatcher
2013-05-05 23:06:43,388 INFO [EventSubscriptionExpirationChecker] Leaving EventSubscriptionExpirationChecker, removing all event subscriptions

From Run 2 Serviio Log

org.serviio.upnp.protocol.http.transport.InvalidResourceRequestException: Invalid incoming request: /resource/149858/MEDIA_ITEM/MPEG4_P2_MP4_ASP_AAC-0
at org.serviio.upnp.protocol.http.transport.RequestedResourceDescriptor.<init>(RequestedResourceDescriptor.java:73)
at org.serviio.upnp.protocol.http.transport.AbstractProtocolHandler.getRequestedResourceDescription(AbstractProtocolHandler.java:35)
at org.serviio.delivery.ResourceDeliveryProcessor.deliverContent(ResourceDeliveryProcessor.java:65)
at org.serviio.upnp.webserver.ResourceTransportRequestHandler.handleRequest(ResourceTransportRequestHandler.java:85)
at org.serviio.upnp.webserver.AbstractRequestHandler.handle(AbstractRequestHandler.java:61)
at org.apache.http.protocol.HttpService.doService(HttpService.java:293)
at org.serviio.upnp.webserver.ServiioHttpService.doService(ServiioHttpService.java:77)
at org.apache.http.protocol.HttpService.handleRequest(HttpService.java:212)
at org.serviio.upnp.webserver.WebServer$WorkerThread.run(WebServer.java:192)
Caused by: java.lang.ArrayIndexOutOfBoundsException: 3
at org.serviio.upnp.protocol.http.transport.RequestedResourceDescriptor.<init>(RequestedResourceDescriptor.java:70)
... 8 more

I turned everything to do with metadata handling and library updates off. I then still got a lot of Playlist messages. I moved playlists out of the library path but I guess I forgot to update the library (so there are still a lot of those mesages to do with something in the attached log).

Anyway, I still had all the problems noted (despite having metadata off)

I did one session where I (with a different mp4 file "secret world.mp4"
1) got the 402 error in BubbleUPnP to the WDTV Live then
2) successfully sent it to the XBMC renderer.

Full session ... hope this helps.

[zip]

Some of the exceptions look like the request made is not valid anymore. I think some clients cache the content, which will not work properly with online content, because the IDs can be reused. try to clean BubbleUPnP cache if thee is one.

I've recently found out the cause of 402 errors with recent firmware of WDTV Live

Recent version of this firmware do very agressive matching of protocolInfo passed to SetAVTransportURI
and will return a 402 "Illegal argument" if the protocolInfo found in the metadata argument doesn't match what it claims to support.
Although I couldn't verify it, I suppose there might the same issue when the WDTV browse dirrctly a media server.

In particular for mp4, the WD TV declare support for http-get:*:video/mp4:*
Theorically it should accept http-get:*:video/mp4:<whatever DLNA fields here>, but it doesn't and return a 402.

So if Serviio is passing to BubbleUPnP anything other than http-get:*:video/mp4:* for mp4 then it will fail.
I have workarounded it in the next version of BubbleUPnP, but this is a good candidate to add in a serviio profile.

[zip]

It should already be supported. Try to add this to the wdtv profile:

  Code:

<ProtocolInfo>simple</ProtocolInfo>

There was a BubbleUpnp udate this morning whose release notes were more device-to specific though seemed to address issues I am having. However, except for possibly getting more success with wmv files (a couple of those only 'got through') there was little success elsewhere.

Thanks. I see some replies that I will investigate and let you know.

I will mention something I should have noticed before it seems artist/album did not still does not get through from Serviio to the BubbleUpnp 'now playing' window. For the same MP4 music video, for instance, from another server the artist and album do get through. Also the codec beneath the scroll bar on the other server comes through as MPD/44.1 Khz while from serviio is 'MP4'.

SOLVED!!!

There was a small BubbleUpnp cache to clear under Android settings. I also cleared the Servii-go cache and, according to popular thought, the WDTVLive cache, by clearing the login info (I guess that makes sense). I did not go as far as a WDTVLive factory reset (which is not a big deal, anyway).

It appears adding that line to the WDTVLive profile:

<Profile id="14" name="WDTV Live" extendsProfileId="1">
<Detection>
<UPnPSearch>
<ModelName>WD TV HD Live</ModelName>
</UPnPSearch>
</Detection>
<ProtocolInfo>simple</ProtocolInfo>

solved the problem. That's great! Everything from Serviio is playing through Bubble (I'll check others later). After two years fiddling with this stuff from the LG that didn't seem to play anything (and where my worst problem was ADSL phone system "drops") EVERYTHING is working perfectly!!! Thank you all.

There was a BubbleUpnp udate this morning whose release notes were more device-to specific though seemed to address issues I am having. However, except for possibly getting more success with wmv files (a couple of those only 'got through') there was little success elsewhere.

Thanks. I see some replies that I will investigate and let you know.

These WDTV Live with newer firmware are a real pain to make working with a Control Point.
Normally, BubbleUPnP pass the unmodified protocolInfo returned by the Media Server (Serviio and others) but if the protocolInfo does not exactly match a protocolInfo from the WDTV live supported list, it will fail miserably with an error 402. For reference here's the list of protocolInfo that can help building profiles.
If you can get Serviio to return to BubbleUPnP one of these protocolInfo for a given file type (the ones that you want to play), it should work.
I added a specific workaround for the WDTV Live in the newer version of BubbleUPnP but it doesn't work in all cases.

http-get:*:audio/L16;rate=44100;channels=1:DLNA.ORG_PN=LPCM,http-get:*:audio/L16;rate=44100;channels=2:DLNA.ORG_PN=LPCM,http-get:*:audio/L16;rate=48000;channels=1:DLNA.ORG_PN=LPCM,http-get:*:audio/L16;rate=48000;channels=2:DLNA.ORG_PN=LPCM,http-get:*:audio/mpeg:DLNA.ORG_PN=MP3,http-get:*:audio/x-ms-wma:DLNA.ORG_PN=WMAFULL,http-get:*:audio/x-ms-wma:DLNA.ORG_PN=WMABASE,http-get:*:video/mpeg:DLNA.ORG_PN=MPEG_PS_PAL,http-get:*:video/mpeg:DLNA.ORG_PN=MPEG_PS_NTSC,http-get:*:video/vnd.dlna.mpeg-tts:DLNA.ORG_PN=MPEG_TS_SD_NA,http-get:*:video/vnd.dlna.mpeg-tts:DLNA.ORG_PN=MPEG_TS_SD_NA_T,http-get:*:video/mpeg:DLNA.ORG_PN=MPEG_TS_SD_NA_ISO,http-get:*:video/vnd.dlna.mpeg-tts:DLNA.ORG_PN=MPEG_TS_SD_EU,http-get:*:video/vnd.dlna.mpeg-tts:DLNA.ORG_PN=MPEG_TS_SD_EU_T,http-get:*:video/mpeg:DLNA.ORG_PN=MPEG_TS_SD_EU_ISO,http-get:*:video/vnd.dlna.mpeg-tts:DLNA.ORG_PN=MPEG_TS_SD_KO,http-get:*:video/vnd.dlna.mpeg-tts:DLNA.ORG_PN=MPEG_TS_SD_KO_T,http-get:*:video/mpeg:DLNA.ORG_PN=MPEG_TS_SD_KO_ISO,http-get:*:video/x-ms-wmv:DLNA.ORG_PN=WMVMED_PRO,http-get:*:video/x-ms-wmv:DLNA.ORG_PN=WMVMED_BASE,http-get:*:video/x-ms-wmv:DLNA.ORG_PN=WMVMED_FULL,http-get:*:video/x-ms-wmv:DLNA.ORG_PN=WMVHIGH_FULL,http-get:*:video/x-ms-wmv:DLNA.ORG_PN=WMVHIGH_PRO,http-get:*:video/x-ms-wmv:DLNA.ORG_PN=WMVHM_BASE,http-get:*:video/x-ms-wmv:DLNA.ORG_PN=WMVSPLL_BASE,http-get:*:video/x-ms-wmv:DLNA.ORG_PN=WMVSPML_BASE,http-get:*:image/jpeg:DLNA.ORG_PN=JPEG_SM,http-get:*:image/jpeg:DLNA.ORG_PN=JPEG_MED,http-get:*:image/jpeg:DLNA.ORG_PN=JPEG_LRG,http-get:*:image/jpeg:DLNA.ORG_PN=JPEG_TN,http-get:*:image/png:DLNA.ORG_PN=PNG_SM_ICO,http-get:*:image/png:DLNA.ORG_PN=PNG_TN,http-get:*:audio/x-aiff:*,http-get:*:audio/aiff:*,http-get:*:audio/x-wav:*,http-get:*:audio/lpcm:*,http-get:*:audio/x-mpegurl:*,http-get:*:audio/x-scpls:*,http-get:*:audio/x-ms-asx:*,http-get:*:audio/rmp:*,http-get:*:video/mpeg:*,http-get:*:video/mpeg2:*,http-get:*:video/dvd:*,http-get:*:video/x-msvideo:*,http-get:*:video/avi:*,http-get:*:video/mp4:*,http-get:*:video/MP4V-ES:*,http-get:*:video/MP4V:*,http-get:*:video/x-mpegurl:*,http-get:*:video/x-scpls:*,http-get:*:video/x-ms-asx:*,http-get:*:video/rmp:*,http-get:*:image/tiff:*,http-get:*:image/jpeg:*,http-get:*:image/jpeg2000:*,http-get:*:image/png:*,http-get:*:image/bmp:*,http-get:*:image/gif:*,http-get:*:image/x-mpegurl:*,http-get:*:image/x-scpls:*,http-get:*:image/x-ms-asx:*,http-get:*:image/rmp:*,http-get:*:application/ogg:*,file:*:audio/x-ms-wma:*,file:*:audio/x-aiff:*,file:*:audio/aiff:*,file:*:audio/mpeg:*,file:*:audio/x-wav:*,file:*:audio/lpcm:*,file:*:audio/x-mpegurl:*,file:*:audio/x-scpls:*,file:*:audio/x-ms-asx:*,file:*:audio/rmp:*,file:*:video/mpeg:*,file:*:video/mpeg2:*,file:*:video/dvd:*,file:*:video/x-msvideo:*,file:*:video/mp4:*,file:*:video/MP4V-ES:*,file:*:video/MP4V:*,file:*:video/x-mpegurl:*,file:*:video/x-scpls:*,file:*:video/x-ms-asx:*,file:*:video/rmp:*,file:*:image/tiff:*,file:*:image/jpeg:*,file:*:image/jpeg2000:*,file:*:image/png:*,file:*:image/bmp:*,file:*:image/gif:*,file:*:image/x-mpegurl:*,file:*:image/x-scpls:*,file:*:image/x-ms-asx:*,file:*:image/rmp:*,file:*:application/ogg:*,rhapsody:*:audio/x-ms-wma:*,rhapsody:*:audio/x-mpegurl:*,rhapsody:*:audio/x-rhap-radio:*,uvox:*:audio/mpeg:*,http-get:*:image/sls:*,http-get:*:application/x-dtcp1;CONTENTFORMAT=image/jpeg:*,unicast:*:video/mpeg2ts:*,multicast:*:video/mpeg2ts:*,rtsp:*:video/mp4:*,rtsp:*:misc/sdp:*,http-get:*:audio/mp4:*,http-get:*:audio/vnd.dlna.adts:*,http-get:*:audio/m4a:*,http-get:*:audio/3gpp:*,http-get:*:video/3gpp:*,http-get:*:video/3gpp2:*,http-get:*:audio/flac:*,http-get:*:audio/x-flac:*,http-get:*:video/x-matroska:*,http-get:*:video/quicktime:*

Problem reported as solved is back !

As I recall everything:

1) there was a BubbleUPnP update 1.6.9 yesterday morning (SE Asia) for which after noticing I went through my 'cases' noted in the first couple posts of this thread and saw little difference in the problem noted. The issues noted in the Bubble update changelog were not specific to the problem, anyway.

2) I came here to this forum to find some useful suggestions and added the directive suggested by one of our forum masters to my serviio configuration and adding that directive solved the problem.

3) aftewards a BubbleUpnp update 1.6.9.1 came along. Item one in the changelog was: "Fixed 402 playing some files to the WDTV Live"

4) My 'feeding files from serviio to the WDTVlive streamer via the BubbleUpNp facilty is again ridden with '402' errors. NOT WORKING.. To be sure I tried both with the directive and without it in the configuration.

So my problem is back. I presume there was some minor oversight or something in the 1.6.9.1 update and it will be reported elsewhere too and fixed. I suppose it could possibly be a strange internal problem. My network is working pretty much perfectly, I believe, finally. I can't see what it could be. I will sit back and hope someone else cares enough to report it here as well. Also, I'll be happy to try something or provide further data if requested.

And anyway, what the problem is has been investigated and reported. It's good that news is out. Someone with my level of experience might mistake where the error message is coming from ...

I guess what's happening is coders are finding the latest WDTVLive streamer too restrictive on the media types handled for files 'pushed' (as opposed to files requested directly - I have no problems requesting serviio files from the WDTVLive menus). I can't see that there should be a difference. I appreciate the proactive response and enthusiasm of the BubbleUpnp rep but I don't think he should be patching his code. The WDTVLive should see the file as it is and handle it appropriately. The situation at "UpNp" could get quite complicated and its better the serviio code or user handles it for serviio.

There are a lot of alternatives for me to my favorite combination (Bubble/Serviio/WDTVLive) for now, so I am not in a hurry for anything.

The 1.6.9.1 updates tries to address that 402 issue no matter what the media server is, by sending the WDTV a protocolInfo in the list above.
If you still get a 402 error please email me log file triggering that error (see end of that post for instructions).

That issue cannot be fixed on the Serviio side because modifying the WDTV profile will not have any effect when using BubbleUPnP, because Serviio sees browsing requests
from BubbleUPnP and not the WDTV. The profile system works great as long as the browsing device is also the playing device.
This is true if you browse play from your WDTV. This is not when there is a middle man in bewteen, like a Control Point.
Not unless you make a profile for the Control Point, which doesn't make much sense because a control point by defintiion can control several different devices (unless you ever use it to play to a single device). That's were profile systems commonly found in media servers show their limit.

[zip]

You would have to assign the BubbleUpnp device the wdtv profile to actually use that profile change.

I guess I am still having bad days (nothing with serviio works) and good days and the timing of these days doesn't necessarily seem to be consequential to real situaions, like before/after the effects of software or setup updates.

I will note that at the start of today's surprisingly better day the only change to any of the Bubble related software I have done before is to update Window's BubbleUpnp Server. On the tablet I use the openhome renderers for ''production'(three rooms) and don't need the proxies. For today's better-day test run I switch around between numerous renderers, proxies, actual servers.

But luckily I just had a good day which is one where everything to do with serviio through BubbleUpnp STARTS working fine but after a while the 402 errors start to appear. The 402 errors that start are MOSTLY with serviio files and continue consistently. So it looks like maybe some congestion? Cacheing? Network errors? is a particular problem for me. After the first 402 error started I turned on the logging file and emailed per the instructions linked to in the post above. I hope maybe the logging gives a clue as to what is going on.

For my 'network' I have an ISP provided ADSL router (191.168.1.1) which stays connected to the internet (connection doesn't drop) 90% of the time. 1.1 doesn't work well for home internet connections. One of the 1.1 ethernet ports gets input to the more advanced router (192.168.1.2) I bought with advanced features that works very well inside (but drops the internet 90% of the time if it is the modem connecting into the phone system). I can only get the whole thing working with all the home networking (including PC and tablet wireless) in/out of 1.2 and setting DHCP on Windows (defaults IPV4) to 1.1 by disabling DHCP on 1.2. All the devices are manual set to use 1.1 for gateway and DNS. (Thus I'm shielded from the phone system drops which wreaks complete hell on the home network when Windows forces reconnecting (in the just one router scenario.) I can't seem to uncover any network problems using a lot of the fine facilities available to me (FING, Network tester, LanDroid, Network Signal Info ...). I am having no other problems except with 'play to'.

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethernet
Physical Address. . . . . . . . . : 00-26-B9-0D-3B-95
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::3d34:557a:3149:222d%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.40(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, May 13, 2013 1:45:56 AM
Lease Expires . . . . . . . . . . : Thursday, May 23, 2013 1:45:56 AM
Default Gateway . . . . . . . . . : fe80::1%11
192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 268445369
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-12-03-D0-00-26-B9-0D-3B-95

DNS Servers . . . . . . . . . . . : 192.168.1.1
Primary WINS Server . . . . . . . : 192.168.1.1
Secondary WINS Server . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled

I guess I am still having bad days (nothing with serviio works) and good days and the timing of these days doesn't necessarily seem to be consequential to real situaions, like before/after the effects of software or setup updates.

I will note that at the start of today's surprisingly better day the only change to any of the Bubble related software I have done before is to update Window's BubbleUpnp Server. On the tablet I use the openhome renderers for ''production'(three rooms) and don't need the proxies. For today's better-day test run I switch around between numerous renderers, proxies, actual servers.

But luckily I just had a good day which is one where everything to do with serviio through BubbleUpnp STARTS working fine but after a while the 402 errors start to appear. The 402 errors that start are MOSTLY with serviio files and continue consistently. So it looks like maybe some congestion? Cacheing? Network errors? is a particular problem for me. After the first 402 error started I turned on the logging file and emailed per the instructions linked to in the post above. I hope maybe the logging gives a clue as to what is going on.

Beware that using your WDTV as an OpenHome renderer managed BubbleUPnP Server may give you 402 errors. That's because BubbleUPnP Server controlling your WDTV has not (yet) the WDTV specific fixes that I put in BubbleUPnP 1.6.9.1. So for now it may be wiser to not use your WDTV as an OpenHome renderer, if you get these errors (I don't think you'll get them for audio, but you never know).

Yes, I get them both using the WDTV live as openhome or not.

Don't use '"openhome" server with WDTVLive!! Still, eventually, 402s show up. There is still something about serviio files versus other servers' elswhere. I'll try to look closer later on - maybe the serviio setup change.

Without the WDTVLive openhome the WDTV gets interrupted going to other rooms.

That's too bad. One might think the streamer wouldn't know whetehr the queue was openhome or not. Openhome works so well with foobar and XBMC renderers. The HDMI cable is back across the floor from the den to the living room to be kicked out by guests, and I'm fixing the XBMC sound bug every time again (it got more bizarre this morning). I'm giving up on replacing XBMC with WDTVLive as the network renderer again despite the improvements with WDTV's latest firmware/Beam with ... . (And I do appreciate other features of WDTVLive).

Send me a BubbleUPNP log file, triggering a 402 error, contolling the standard WDTV (not the OpenHome one, that you should disable in BubbleUPNP Server, the time of this log).

I sort of slithered away in embarrassment after realizing I just wrongly assumed all streamers (like WDTVLive) had defacto support for Openhome. So, above, random failures assuming that may have been common. I am also realizing that for some reason playto the WDTVLive can take longer than you would think and some "failures" may have been impatience.

I'm very successful playing to the WDTVLive (no openhome) through Bubble now. I can finally get down to formats and transcoding. Thank you for that .

I still have problems with Serviio files to going to directly WDTVLive using other DLNA clients (ArkMC, MediaHome), other server files seem to be randomly more successful, but still problematic**. No sense to it. But I have great success using Bubble as the external player in these other clients !!!! <more praise here> And using Bubble external player (with the Renderer already set to WDTVLive (no openhome) ) is a one button press procedure as opposed to the "Beam with Twonky" which takes numerous steps. But in terms of formats the Beam with Twonky is sometimes more (internally, obviously) reliable and I have nothing but praise for Beam wTwonky , too, so useful thx.



** Of course it appears that maybe the other clients haven't integrated the strict 'policies' noted here. I guess I should email the develpers directly. I tried to post some feedback in the Google Play store about it. (i hope our forum master doesn't mind the rant >>> ) It appears that Google is trying to force 'upgrade' me to Google plus in order to provide any feedback now. I considered it. I see that to upgrade to Google Plus I MUST AGREE TO 'UNDERSTAND' THE CHANGES THAT THIS WILL MAKE TO MY PICASA themed web photo album. Well, I did not understand that more than a year ago and did not LIKE having my Picasa site tranformed into a facebook like personal folder back then, and quit G+, AND won't "understand" it now either. I won't be posting feedback for developers in the Google Play store.


I see request above, and will consider it.

Things have been better, less bad days of which I assume have more to do with maybe a modem for instance just now i had troubles getting the Bubble log file I just emailed you across the wifi to my PC ...

This log file is for a example not specifically from servio but I have very similar with .m4v from serviio. this time ...

from a podcast manager
1) via bubble the player window open, something happens on the TV screen from the WD streamer, often just a sharing from windows message,nothing plays;
2) via beam with Twonky it gives an 'unable to play' message, but does play anyway.

Hope his helps.

I know some vid links require Semper. How would I knw?