- August 29, 2009
- 1,730
- 1,124
- Home Country
- Netherlands
Yes, something like that. I've to think a bit about compatibility though, as the format of the transcoder configuration will probably change with each MPExtended release (i.e. new VLC version requires new parameters, other path, different installation directories).Maybe allow Clients to InitStream with custom profileXmlNode generated by the client. this way no change is required for every new client.
Anyway, for now I'll add your profile to MPExtended 0.5.4. Would it be a problem for you if I changed the target to windows-phone-ts for consistency with the other targets (i.e. can you easily update your app to a new target, or does that require re-approval and delays)?
No, as already mentioned it encodes the video to H.264 and MP3 into an MPEG2 TS container. MP4 doesn't support live streaming at all: that's not a limitation of WP8, it's a limitation of the container.If I read the streaming profile properly, you are using vlc to encode the original file or stream (if tv that would be mpeg2 video codec in .ts container) into an mp4 container with .h264 video codec. I think that is compatible with WP7! (depending on resolution, etc, etc,).
It's quite simple actually: the client sends the supported targets (i.e. what's inside the <Target> tag), and MPExtended sends a list of all compatible streaming profiles. For WebMediaPortal, the supported targets are pc-vlc-video and pc-vlc-audio (always), pc-flash-video and pc-flash-audio (when on a PC) and mobile-hls-video (when on Android, iOS or Mac OS X).What I don't understand is how MPExtended recognizes the client and creates the pick-list of compatible streaming profiles.
Certainly looks like it.I guess that the Plex server must have a smoothstreaming server implementation.