IPTV - channels.conf problem

Having problems with adding channels to channels.conf file.
Some channels work, others don't.
The HELP file isn't very helpful for a beginner:

TV4;IPTV:40:S=1|P=0|F=EXT|U=iptvstream.sh|A=0:I:0:0:680:0:0:4:0:0:0
  TV3;IPTV:30:S=0|P=1|F=FILE|U=/video/stream.ts|A=5:I:0:514:670:2321:0:3:0:0:0
  TV2;IPTV:20:S=0|P=1|F=HTTP|U=127.0.0.1/TS/2|A=3000:I:0:513:660:2321:0:2:0:0:0
  TV1;IPTV:10:S=1|P=0|F=UDP|U=127.0.0.1|A=1234:I:0:512:650:2321:0:1:0:0:0
           ^  ^   ^   ^     ^           ^    ^
           |  |   |   |     |           |    Source type ("I")
           |  |   |   |     |           Stream parameter (multicast port
           |  |   |   |     |           number, HTTP port number, file delay
           |  |   |   |     |           (ms), script parameter)
           |  |   |   |     Stream address (multicast address, URL, file
           |  |   |   |     location, script location)
           |  |   |   Stream protocol ("UDP", "HTTP", "FILE", "EXT")
           |  |   PID Scan ("0" disable, "1" enable)
           |  SID Scan ("0" disable, "1" enable)
           Unique enumeration

This is what my channels.conf looks like (manual testing):

RTV SLO 1;IPTV:1:S=1|P=0|F=UDP|U=239.1.1.115|A=5000:I:0:300=2:301:400:0:1:0:0:0
POP TV;IPTV:2:S=1|P=0|F=UDP|U=239.1.1.9|A=5000:I:0:121=2:123:124:0:4:0:0:0

It seems that some channels don't like the last part of the string. How can I enter the info correctly? Is there some 'detect' tool for IPTV channels?

Using the latest v0.4.1.

Zitat

Originally posted by rofafor
The entries looks fine, although you really should use bigger "frequency" values: 1->10, 2->20, etc. Otherwise you might encounter some minor problems as

Hmm, saw that somewhere mentioned, but didn't change it. Now I'm going to.

Zitat

Any error messages in syslog? What do mean exactly with the last part: the parameter part only or the whole string? Does the vdr accept the channels.conf? Does any of the channels work? ...

Some channels work, some don't. The one that I pasted in the previous post work. If I add a few with the same params (excluding the name, 'frequency' and IP) they don't work.
I'm sure the problem is in the params .. somewhere. I'm having problems with exact definition of the params.

When to use "S=1" or "S=0" or "P .." and all the params behind the port.

I only know Name, IP and Port of a certain channel from my provider. OK, frequency, "IPTV", and stream protocol are sort of obvious, but that's about it.

Zitat

Originally posted by rofafor
If you don't know the service id of your input stream, you should set "S=1" that enables the SID scanner and the plugin tries to guess the service id value by itself and update the configuration. Service id is required i.e. for EPG data. If your stream is missing the PMT table, VDR cannot find any pids for the channel. Then you can enable the PID scanner by setting "P=1" and the plugin tries to guess a video pid and (only) a first audio pid automatically and update the configuration. If some channel doesn't work, make sure it isn't encrypted: use the VLC for viewing or redirect plugins' output stream into a file (requires a fifo as mentioned in README). You could also check the stream information menu found in plugin's setup and see if there's any pid activity.

Thanks for the info.
I'm still not sure about these PID&SIDs tasks in a UDP stream, but I'll manage. I'm also boggled by the last 10 or so params. Are they supposed to be edited manually or are they updated by the system as you mentioned?

BTW There is no EPG data in the streams. Channels are not encrypted - I can play all the channels with VLC.

Will check the "plugins' setup" ... Let's see if I can find it.

Thanks for explaining it to me.

After some experimentation I found out that each channel has it's own S and P preferences - if I don't change it to exactly right combination it does't work. There were also some problems based on buffer sizes (iptv plugin).
Now it sort of works in xine, but I still have problems with XMBC - crashes a lot (this is probably the VNSI's fault, being in an early stage of development and all).