Bug #5258
closed
getProfiles does not return all profiles (specifically an MPEG-TS Spawn profile)
Added by John Blumpy over 6 years ago.
Updated over 6 years ago.
Found in version:
4.3-1465~g433bcd2e5
Description
I opened a bug with TVHClient because my custom MPEG-TS Spawn profile doesn't appear in that Android app as a selectable profile. The TVHClient developers believe this is a Tvheadend bug, hence I am opening this ticket. I have attached screenshots showing my newly created stream profile and it not appearing in the app.
rsiebert, one of the developers, stated:
When the app has connected to the server it makes a call to get the dvr and playback profiles. According to https://tvheadend.org/projects/tvheadend/wiki/Htsp these are getProfiles and getDvrConfigs. The lists that are returned are then shown in the settings. If the server does not list yours then I don't really know where to look.
For a detailed description of the problem and the conversation between myself and the TVHClient developers, see these threads:
https://github.com/rsiebert/TVHClient/issues/351
https://github.com/rsiebert/TVHClient/issues/361
Files
TVHClient client uses an external media player, right?
Basically, for the HTSP protocol the list of profiles is reduced (only 'htsp' and transcoding profiles), but for HTTP streaming, the list is different (all except 'htsp' profile).
HTSP methods return list of useable profiles for the HTSP protocol (it's expected that the application will get the stream data through this protocol). For HTTP, the HTTP API should be used to get the right list of profiles. The HTSP protocol has a proxy to the HTTP api using "api" method. https://tvheadend.org/projects/tvheadend/wiki/Htsp#api-Added-in-version-24
The right call to get HTTP profiles is:
HTSP "api" method -> path "profile/list", args empty -> response is list
I think that it's missing from TVHClient .
Thanks for the useful info, I will relay this back to the TVHClient developers.
I also noticed this issue on THClient.
As far as I know, THClient does use HTSP protocol for everything except streaming - it can only play channels using an external player (which in turn can only use HTTP streaming).
So, I would tell the THClient developers that they should NOT get any HTSP profile - only get profiles that are usable to do HTTP streaming.
- Status changed from New to Invalid
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
