Project

General

Profile

Bug #5258

getProfiles does not return all profiles (specifically an MPEG-TS Spawn profile)

Added by John Blumpy about 6 years ago. Updated about 6 years ago.

Status:
Invalid
Priority:
Normal
Assignee:
-
Category:
API
Target version:
-
Start date:
2018-10-14
Due date:
% Done:

0%

Estimated time:
Found in version:
4.3-1465~g433bcd2e5
Affected Versions:

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

New Stream Profile.png (59.8 KB) New Stream Profile.png John Blumpy, 2018-10-14 18:49
Allowed Streaming Profiles.png (95.3 KB) Allowed Streaming Profiles.png John Blumpy, 2018-10-14 18:49
App - Missing Profile.png (78.5 KB) App - Missing Profile.png John Blumpy, 2018-10-14 18:49

History

#1

Updated by Jaroslav Kysela about 6 years ago

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 .

#2

Updated by John Blumpy about 6 years ago

Thanks for the useful info, I will relay this back to the TVHClient developers.

#3

Updated by Luis Alves about 6 years ago

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.

#4

Updated by Jaroslav Kysela about 6 years ago

  • Status changed from New to Invalid

Also available in: Atom PDF