DLNA & DIAL detection #34
Comments
|
OK, I'll check this. |
|
@se-bastiaan In my case I am able to discover both services DLNA & DIAL. Can you check the same with ConnectSDK Sampler app and send logs? |
|
Situation 1 Situation 2 Pluto: Raspberry Pi running XBMC |
|
@se-bastiaan The strange thing that there is a Netcast service on your Saturnus TV instead of DIAL in second situation. Can you log entire SSDP packages? |
|
@frolov-alexey Sure. I'll do that once I'm near my TV again. Not only the television is detected as Netcast TV, but the XBMC instance is too. But they're also both detected as DLNA. |
I hope this is what you wanted. |
|
The problem is Currently, we're using uuid as a key, that's why you can only see one of them. |
|
That confirms what I thought. I was looking through the code, but I wasn't sure. Maybe that I'll take a look and try to change it. Or I just disable the DIAL service. |
|
Maybe you can add extra exceptional case for sony bravia tv. (To add this, our team (with iOS) needs to discuss first, it may need sometime). In the meantime, if you want to change it by yourself, please check |
|
I decided to disable DIAL for now, since I don't need it. I'll only be beaming video's and that works great without it. Tight schedule etc. If your team wants to solve this and it needs testing: give me a shout. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My Sony Bravia television has support for DIAL and DLNA. But I suspect only one of these services is detected. If DIAL is discovered first, then DLNA is unavailable. If DLNA is discovered first, then DIAL is not available. Can that be the case?
The text was updated successfully, but these errors were encountered: