hi there, some information on my current setup:
ubuntu kernel 3.2.0-52-generic
tvh 3.5.243~g2b64995
dvb-s card tbs6991 dual tuner and dual ci with latest drivers: v130802 - my card supports dvb-s and dvb-s2 (I have other mux's with 8PSK that do work)
2 dishes facing astra 19.2, hotbird and Turksat
Astra and Hotbird seem to work fine in every aspect. Seems the trouble I have is on some of the stations on Turksat.
I have issues with some of the multiplexes, although they are working (I can open it via the 'play' button from the multiplex tab in the browser and watch it, as well as e.g. in mplayer with the channels.conf I created with w_scan) they are not showing up in the services tab and thus they can't get mapped to channels.
Below one example of the several muxes i have problems with. I removed the mux and it got re-added and this is what is in the logs:
Aug 31 12:24:19 SAT tvheadend[990]: dvb: New mux "TURKSAT: 11,964,000 kHz Horizontal (Turksat (Port 2, Universal LNB))" created by automatic mux discovery
Aug 31 12:24:58 SAT kernel: [ 829.863846] TurboSight TBS 6991 Frontend:
Aug 31 12:24:58 SAT kernel: [ 829.863848] tbs6991fe - modulation 9 is not supported
I checked on modulation 9, according to the info I found it relates to 8PSK settings, but this (and others with the same problem) station is not 8PSK but QPSK, and as stated earlier it does work via webinterface 'play' button on mux tab and in mplayer.
Deleting the mux, disabling the auto-detection of muxes and adding the mux manually with correct settings (QPSK), results in exactly the same (as well as same log entries).
tvh must somehow pass on wrong information I suppose, don't know...
the entry created for the mux looks correct:
{
"quality": 100,
"enabled": 1,
"status": "OK",
"transportstreamid": 302,
"originalnetworkid": 42,
"network": "TURKSAT",
"frequency": 11964000,
"initialscan": 0,
"symbol_rate": 5925000,
"fec": "3/4",
"polarisation": "Horizontal",
"modulation": "QPSK",
"delivery_system": "SYS_DVBS",
"rolloff": "ROLLOFF_35",
"satconf": "1"
}
but there is no service entry in the directory where it should be.
I did some more testing and playing around, as I said earlier when using the 'play' button from the multiplex tab from the web interface I can watch that station on the local machine. So I took those links for channels that somehow are not being added as services in tvh and put them in text files as streams, so e.g. I called the file ShowTV.strm with only the link below as content:
http://10.0.0.96:9981/stream/mux/_dev_dvb_adapter0_TurboSight_TBS_6991_DVBS_S2_frontend11964000_H_satconf_1
When using the xbmc install on the local machine where tvh is installed as well it works fine and plays great. Accessing the file via a xbmc install on the local network (100Mb) on another machine (via share in xbmc) it plays as well but a lot of buffering occurs.
For testing purposes I did the same with a station that did get added to services but used the 'play' button link from the services tab, so the *.strm file content was:
http://10.0.0.96:9981/stream/service/_dev_dvb_adapter0_TurboSight_TBS_6991_DVBS_S2_frontend11938000_H_satconf_1_0728
Plays perfectly locally as well as over network on another machine without any buffering.
Checking xbmc log files I see that the mux link-stream sends over all the stations that are actually on that mux so several at the same time, which is too much for the lan to handle and thus buffering occurs, whilst when using the service play link only that particular station is being sent over lan, obviously resulting in less bandwidth requirements and thus no buffering occurs.
Upgrading to Gb-lan might be another dirty work around but as I want to use the raspberry pi as front-end not really an option (it only has 100Mb lan and using e.g. a usb lan interface will also not work).
I wonder if I can somehow add the service myself in tvh to at least be able to stream only one channel. First let's stop the tvh service. Then let's look at mux that does work also as service, 11984 is a mux on Turksat that does work, doing a locate on that frequency (locate 11981) on the cmd line yields this:
/home/hts/.hts/tvheadend/dvbmuxes/_dev_dvb_adapter0_TurboSight_TBS_6991_DVBS_S2_frontend/_dev_dvb_adapter0_TurboSight_TBS_6991_DVBS_S2_frontend11981000_H_satconf_1
/home/hts/.hts/tvheadend/dvbtransports/_dev_dvb_adapter0_TurboSight_TBS_6991_DVBS_S2_frontend11981000_H_satconf_1
/home/hts/.hts/tvheadend/dvbtransports/_dev_dvb_adapter0_TurboSight_TBS_6991_DVBS_S2_frontend11981000_H_satconf_1/_dev_dvb_adapter0_TurboSight_TBS_6991_DVBS_S2_frontend11981000_H_satconf_1_0001
/home/hts/.hts/tvheadend/dvbtransports/_dev_dvb_adapter0_TurboSight_TBS_6991_DVBS_S2_frontend11981000_H_satconf_1/_dev_dvb_adapter0_TurboSight_TBS_6991_DVBS_S2_frontend11981000_H_satconf_1_0002
/home/hts/.hts/tvheadend/dvbtransports/_dev_dvb_adapter0_TurboSight_TBS_6991_DVBS_S2_frontend11981000_H_satconf_1/_dev_dvb_adapter0_TurboSight_TBS_6991_DVBS_S2_frontend11981000_H_satconf_1_0003
/home/hts/.hts/tvheadend/dvbtransports/_dev_dvb_adapter0_TurboSight_TBS_6991_DVBS_S2_frontend11981000_H_satconf_1/_dev_dvb_adapter0_TurboSight_TBS_6991_DVBS_S2_frontend11981000_H_satconf_1_0005
First one is the Mux itself and the latter four indicate that there are 4 stations/channels on that mux, having a look on lyngsat confirms this.
Let's first have look into the mux file:
cat /home/hts/.hts/tvheadend/dvbmuxes/_dev_dvb_adapter0_TurboSight_TBS_6991_DVBS_S2_frontend/_dev_dvb_adapter0_TurboSight_TBS_6991_DVBS_S2_frontend11981000_H_satconf_1
{
"quality": 100,
"enabled": 1,
"status": "OK",
"transportstreamid": 1,
"originalnetworkid": 65535,
"network": "TGRT",
"frequency": 11981000,
"initialscan": 0,
"symbol_rate": 5200000,
"fec": "5/6",
"polarisation": "Horizontal",
"modulation": "QPSK",
"delivery_system": "SYS_DVBS",
"rolloff": "ROLLOFF_35",
"satconf": "1"
}
Looks pretty much like the mux file from the sample station that does not work (see at the top). Now let's look at the service files for that mux:
cat /home/hts/.hts/tvheadend/dvbtransports/_dev_dvb_adapter0_TurboSight_TBS_6991_DVBS_S2_frontend11981000_H_satconf_1/_dev_dvb_adapter0_TurboSight_TBS_6991_DVBS_S2_frontend11981000_H_satconf_1_000*
{
"service_id": 1,
"pmt": 32,
"stype": 1,
"scrambled": 0,
"channel": 0,
"provider": "www.tgrt.com.tr",
"servicename": "TGRT BELGESEL",
"channelname": "TGRT BELGESEL",
"mapped": 1,
"dvb_eit_enable": 1,
"pcr": 308,
"disabled": 0,
"stream": {
"pid": 308,
"type": "MPEG2VIDEO",
"position": 0,
"width": 480,
"height": 576,
"duration": 3600
},
"stream": {
"pid": 256,
"type": "MPEG2AUDIO",
"position": 1,
"language": "eng",
"audio_type": 0
}
}
{
"service_id": 2,
"pmt": 48,
"stype": 1,
"scrambled": 0,
"channel": 0,
"provider": "",
"servicename": "TGRT HABER",
"channelname": "TGRT HABER",
"mapped": 1,
"dvb_eit_enable": 1,
"pcr": 309,
"disabled": 0,
"stream": {
"pid": 309,
"type": "MPEG2VIDEO",
"position": 0,
"width": 720,
"height": 576,
"duration": 3600
},
"stream": {
"pid": 257,
"type": "MPEG2AUDIO",
"position": 1,
"language": "eng",
"audio_type": 0
}
}
{
"service_id": 3,
"pmt": 64,
"stype": 2,
"scrambled": 0,
"channel": 0,
"provider": "",
"servicename": "TGRT FM",
"channelname": "TGRT FM",
"mapped": 1,
"dvb_eit_enable": 1,
"pcr": 8191,
"disabled": 0,
"stream": {
"pid": 259,
"type": "MPEG2AUDIO",
"position": 0,
"language": "fre",
"audio_type": 0
}
}
{
"service_id": 5,
"pmt": 40,
"stype": 2,
"scrambled": 0,
"channel": 0,
"provider": "",
"servicename": "noname-sid-0x5",
"channelname": "noname-sid-0x5",
"mapped": 1,
"dvb_eit_enable": 1,
"pcr": 8191,
"disabled": 0,
"stream": {
"pid": 265,
"type": "MPEG2AUDIO",
"position": 0,
"language": "eng",
"audio_type": 0
}
}
Now let's look only at one station from that mux to get an idea what information would be needed:
{
"service_id": 1,
"pmt": 32,
"stype": 1,
"scrambled": 0,
"channel": 0,
"provider": "www.tgrt.com.tr",
"servicename": "TGRT BELGESEL",
"channelname": "TGRT BELGESEL",
"mapped": 1,
"dvb_eit_enable": 1,
"pcr": 308,
"disabled": 0,
"stream": {
"pid": 308,
"type": "MPEG2VIDEO",
"position": 0,
"width": 480,
"height": 576,
"duration": 3600
},
"stream": {
"pid": 256,
"type": "MPEG2AUDIO",
"position": 1,
"language": "eng",
"audio_type": 0
}
}
service_id, pmt, scrambled, pcr, pid-video and pid-audio information can be obtained from w_scan output or from sites like kingofsat or lyngsat.
mapped: i suppose that is tvh internal and means if the service is mapped to channel on the web interface where 1=map;0=don't map
dvb_eit_enable: internal to tvh and means if epg info is turned on for that channel or not 1=enabled;0=disabled
disabled: internal to tvh is that channel is enabled or not 1=disabled;0=enabled
provider, servicename, channelname, type (video/mostly "MPEG2VIDEO" when SD, HD is mostly "H264"), width, height, type (audio/mostly "MPEG2AUDIO" unless dolby, then "AC3"): these entries i got from the logs of xbmc when i played the mux stream
I don't know yet where to get the info or if it is internal to tvh for the following entries:
stype
channel
position
duration
position
language
audio_type
I'm sure that instead getting this info from xbmc log there should be a command line tool maybe within the dvb-tools that will provide that info as well, maybe even the currently missing info, need to look into that.
Now let's try to create the file on the system, first we need to create the directory for the service, a working service directory looked like this:
/home/hts/.hts/tvheadend/dvbtransports/_dev_dvb_adapter0_TurboSight_TBS_6991_DVBS_S2_frontend11981000_H_satconf_1/
so i create for my not working frequency 11964:
mkdir /home/hts/.hts/tvheadend/dvbtransports/_dev_dvb_adapter0_TurboSight_TBS_6991_DVBS_S2_frontend11964000_H_satconf_1/
then we need to create the service file, for the working service on service ID the service file is called:
/home/hts/.hts/tvheadend/dvbtransports/_dev_dvb_adapter0_TurboSight_TBS_6991_DVBS_S2_frontend11981000_H_satconf_1/_dev_dvb_adapter0_TurboSight_TBS_6991_DVBS_S2_frontend11981000_H_satconf_1_0001
thus I call mine for the not working service:
touch /home/hts/.hts/tvheadend/dvbtransports/_dev_dvb_adapter0_TurboSight_TBS_6991_DVBS_S2_frontend11964000_H_satconf_1/_dev_dvb_adapter0_TurboSight_TBS_6991_DVBS_S2_frontend11964000_H_satconf_1_0001
Now we need to edit the content, we had the content of a working service file displayed above, we start with that and edit the information as much as we have according to the sources described above, resulting for my currently not working mux/service in:
{
"service_id": 1,
"pmt": 32,
"stype": 1,
"scrambled": 0,
"channel": 0,
"provider": "SHOW TV",
"servicename": "SHOW TV",
"channelname": "SHOW TV",
"mapped": 1,
"dvb_eit_enable": 1,
"pcr": 8190,
"disabled": 0,
"stream": {
"pid": 308,
"type": "MPEG2VIDEO",
"position": 0,
"width": 720,
"height": 576,
"duration": 3600
},
"stream": {
"pid": 256,
"type": "MPEG2AUDIO",
"position": 1,
"language": "tur",
"audio_type": 0
}
}
As I have been working as root, I need to change the ownership of files to hts:video like all the other files/folders:
chown -R hts:video /home/hts/.hts/tvheadend/dvbtransports/_dev_dvb_adapter0_TurboSight_TBS_6991_DVBS_S2_frontend11964000_H_satconf_1/
Now restart the tvh service and indeed the mux appears in the service tab and is mapped as channel. It works, yeah!!!
if someone has some comments or other tips, e.g. on the missing information or if someone could fix tvh to work out of the box for this, that would be great!! :)
thank you in advance.