Media Browser Integration

[Svekke]

There are two

/live?channel=##&client=uniqueid
/live?channeloid=##&client=uniqueid

You are responsible for the uniqueid if &client is not provided only one stream is available via the API.

Martin

So could can't stream 2 channels?
I have u card with 2 tuners. So MB3 can stream 2 channels (different people).

But you tell me that it's not possible?

[mvallevand]

But you tell me that it's not possible?

No I am telling it is possible but only f you provide two different unique ids of your choice.

Martin

[sub]

There are two

/live?channel=##&client=uniqueid
/live?channeloid=##&client=uniqueid

You are responsible for the uniqueid if &client is not provided only one stream is available via the API.

That's not quite correct. You can use those URLs without client identifier to view multiple streams at the same time. Specifying the client identifier just helps the server keep track of which client is which. This is used to help the server know which old streams it can discard when a client askes for a new channel, without having to rely on socket disconnection timing etc.

[sub]

So could can't stream 2 channels?
I have u card with 2 tuners. So MB3 can stream 2 channels (different people).

But you tell me that it's not possible?

Yes, of course you can do multiple streams.

In fact, unlike your WMC plugin, it'll be able to do multiple streams from the same tuner simultaneously, with the same or other channels carried on the same frequencies. so you might be watching, for example, 8 different channels with one DVB-T tuner.

[mvallevand]

That's not quite correct. You can use those URLs without client identifier to view multiple streams at the same time. Specifying the client identifier just helps the server keep track of which client is which. This is used to help the server know which old streams it can discard when a client askes for a new channel, without having to rely on socket disconnection timing etc.

Sorry my understanding was that without the client parameter you would kill each other off in round robin format. I know vlc users have complained about this and I didn't know you adapted things to be IP aware.

Martin

[sub]

Sorry my understanding was that without the client parameter you would kill each other off in round robin format. I know vlc users have complained about this and I didn't know you adapted things to be IP aware.

Yeah, that's not correct. When you don't specify the client identifier, it's not done on IP address, instead it just frees up a stream when the client connection goes away. This generally works, but for the occasional user the connection would be slow to close, causing the next channel request to fail because the tuner was still in use (on another frequency), since the connection had not yet closed. The "client" identifier works around this issue.

[mvallevand]

Reading the explanation I will stick with my original suggestion. It would be insane for any reasonably designe app that used this method of streaming to not avoid using unique client id, since it defines both the stream start and the stream stop.

Martin

[sub]

True - you definitely want to specify a client identifier if you can

[UncleJohnsBand]

If you can give both, that would be great.

New version on the FTP server - 20140120-1

New UtilService API to support calls such as these.

[KRA]

slap me for beeing lazy and not reading 20 pages, but can I test MediaBrowser with NPVR now ?