[mythtv] iptv recorder with enigma2 box

[Karl Dietz]

Hi Torbjorn,

did you open a bug ticket to track these issues?

On 21.02.2016 17:48, Torbjorn Jansson wrote:
> problem 1: url too long
> url got cutoff since it was longer than 128 character limit of
> capturecard.videodevice in the database.

Can you post the playlist and preferably a documentation that can be
used to determite the maximum URL length? (to the ticket)

> problem 2: "#EXTM3U "
> channel scanning didn't work at all, it just complained about the file.
> apparently there is an extra space in the first line of the m3u file
> like this without quotes: "#EXTM3U "

Please post a sample, so our parser can be relaxed to accept more
variants of M3U.

> problem 3: format of #EXTINF:
> next the format of EXTINF: is a bit different, like this:
> #EXTINF:-1,Animal Planet

That's an issue. Our parser is written around the concept of playlists
with channel numbers. Preferably Enigma2 would prepend the channel
number that is used in the other interfaces.
(TV screen / webiste / etc.)

> problem 4: channel.serviceid=0
> field serviceid in channel table is 0, result is that the backend can't
> find the channel once it has successful started receiving data.
> there is errors in the log about not able to find program 0 in PAT
>
> only way to workaround this is specify #EXTVLCOPT:program= in the m3u file.
>
> i assume there is no way of convincing the backend to tune to the only
> working service there is?

This requires a rewrite / redesign. Reading a bit of the stream,
counting PIDs of the packets, then trying to figure out which service
uses these PIDs. With some services sharing PIDs this is going to be a
bit of guessing game.

But if I remember correctly the URLs contains all kinds of tuning
details, like frequency, PIDs, etc. if the program_number/service_id is
also part of the tuning information, then it would be easiest to extend
the playlist generator to just add this information.

Regards,
Karl