| Friday, January 16th, 2015, 10:16 UTC | ||
| [10:16:00] | warpme: | Morning all! |
| [10:16:53] | warpme: | Just quick Q: is current master UPNP suppoused to work with VLC 2.3 on IOS? |
| [10:19:24] | len_ (len_!~quassel@75-168-45-25.mpls.qwest.net) has quit (Remote host closed the connection) | |
| [10:25:21] | stuartm: | warpme: no idea, it's more the other way around, MythTV exposes a standards compliant server, so the question is whether upnp is working in VLC 2.3 on iOS |
| [10:25:58] | map7 (map7!~map7@2001:44b8:4192:2a00:7110:d28c:f369:57a5) has joined #mythtv | |
| [10:26:26] | stuartm: | I think someone, de-karl? mentioned that VLC on iOS was recently patched to fix some upnp bugs |
| [10:28:16] | warpme: | stuartm: sure. Just asking as on 0.27 it was working quite well – but with current master mythtv server is seen as upnp server – but when selected – only search field is displayed. Is there resonable upnp app worth to try? |
| [10:28:45] | stuartm: | is bubbleupnp available for iOS? Found it to be the best app on Android |
| [10:29:21] | stuartm: | warpme: ironically master is more upnp/dlna compliant than 0.27 was |
| [10:30:53] | warpme: | yeah. I believe so. For sure it should be considered as most advanced FOSS upnp server. Sad that this standard has so poor state of implementation :-( |
| [10:31:37] | stuartm: | I think I can guess why vlc might be broken as I've discovered other upnp apps which broke when we started advertising that we supported MediaServer > 1, and ContentDirectory > 1 |
| [10:31:45] | dekarl-work: | warpme are you taking part in the testflight? |
| [10:32:41] | warpme: | dekarl-work: ?? |
| [10:33:05] | dekarl-work: | warpme: https://forum.videolan.org/viewtopic.php?f=36&t=123435 |
| [10:33:47] | dekarl-work: | Might suggest the devs to install a master backend to see the greatness of UPNP (and keep compatible) but ENOTIME and its "yet another forum registration" |
| [10:34:03] | warpme: | stuartm: so is it possible that my WiFi access point (which advertizing also UPNP) interferes with mythtv UPNP server? |
| [10:35:18] | stuartm: | some apps are incorrectly coded to ignore servers which offer versions of the API greater than version 1 (2002) – the correct upnp compliant behaviour is to interoperate with those services using only parts of the API that they understand – upnp is fully backwards compatible |
| [10:35:24] | stuartm: | warpme: no |
| [10:35:37] | warpme: | dekarl-work: ah I see. Thx. I'll try beta :-) |
| [10:37:03] | stuartm: | it's worth asking the VLC iOS devs whether their upnp client will talk to servers supporting MediaServer and ContentDirectory version 4 (2014) even though their app only supports version 1 (2002) |
| [10:44:13] | stuartm: | I'm trying to re-find the relevant line from the spec about how clients must support servers which expose a newer version than they understand |
| [10:47:31] | dekarl-work: | referring to the spec would be good, they (vlc devs) also asked for the spec wrt sharing of PIDs between services in MPTS. (e.g. when regional variants show all the same main content and share all pids or euronews sharing the video pid across all services) |
| [10:47:45] | dekarl-work: | still need to look that one up :/ |
| [10:49:47] | stuartm: | ah, had it bookmarked, Section 1.1.2 of "UPnP Device Architecture 1.0" |
| [10:50:07] | stuartm: | that's Section 1.2.2 in Device Architecture 1.1 |
| [10:50:55] | stuartm: | <quote>Updated UPnP device and service types are required to be fully backward compatible with previous versions of the same type.Devices must advertise the highest supported version of each supported type. For example, if a device supports version 2 of the “Audio†service, it would advertise only version 2, even though it also supports version 1. Control points that support a given version of a device or service are able to also interact |
| [10:50:56] | stuartm: | with higher versions because of this backward compatibility requirement, but only using the functionality that was defined in the lower version. For example, if a control point supports only version “1†of |
| [10:50:58] | stuartm: | the “Audio†service, and a device advertises that it supports version “2†of the “Audio†service, the control point should |
| [10:50:59] | stuartm: | recognize and be able to use the device.</quote> |
| [10:51:31] | warpme: | dekarl-work, stuartm: already sent mail do vlc devs with proposal to to be 'testing-bridge' between MythTV and iOS8 VLC. Lets see whats happen... |
| [10:51:52] | stuartm: | dekarl-work: can't argue when presented with the specs |
| [10:52:00] | dekarl-work: | looking forward to have a nice UPNP server (ours) and client (theirs) |
| [10:52:54] | stuartm: | of course I don't know whether that's the reason they are unable to interoperate, could be something else entirely, but it's a reasonable theory as it's tripped up other upnp client developers in the past |
| [10:53:19] | warpme: | exactly. Keeping in mind hell of work You already devoted to this area it will be really good to achive "MythTV as most advanced & complete UPNP server in FOSS" |
| [10:59:40] | stuartm: | warpme: if you're interested in experimenting you could patch the version numbers back to 1, see whether VLC is then able to see the server |
| [11:01:42] | stuartm: | programs/mythbackend/devicemaster.xml – change MediaServer:4 to MediaServer:1 |
| [11:01:59] | warpme: | stuartm: good idea. I'll look on this when back to home... |
| [11:02:42] | stuartm: | libs/libmythupnp/upnpcds.h – change ContentDirectory:4 to ContentDirectory:1 |
| [11:04:12] | stuartm: | libs/libmythupnp/upnpcmgr.h – change ConnectionManager:3 to ConnectionManager:1 |
| [11:08:10] | stuartm: | warpme: patch to make that easier – http://pastebin.com/XagC8zKw |
| [11:09:01] | stuartm: | anyone who has access to vlc on iOS is welcome to try that patch and let me know if it helps |
IRC Logs collected by
BeirdoBot.
Please use the above link to report any bugs.