[dvblast-devel] DVB-T2 support
Otto Kellerman
wildiness at gmail.com
Fri Feb 10 05:45:42 CET 2017
VLC requires stream information. Check the dvblast --help (I think it is
-e, or -C) . Or switch to some other player like media player classic.
Den 10 feb. 2017 01:07 skrev "peet freud" <peetfreud at gmail.com>:
Thx Christophe!
Now the dvblast behavior looks much better - it streams "something",
I can see the traffic with tcpdump on interface (also it is possible to
"save"
it with dumprtp). Problem is that VLC is not able to play it.
I have one another debug output from tvheadend:
http://pastebin.com/b54Sfimq
Any idea?
On Thu, Feb 9, 2017 at 2:04 PM, Christophe Massiot <cmassiot at upipe.org>
wrote:
> You may want to use --dvb-plp-id -1 to match tvheadend setting.
>
> On 9 Feb 2017, at 08:43, peet freud <peetfreud at gmail.com> wrote:
>
>
> Thx Christophe.
>
> Now the output looks:
>
> DVBlast 3.1 (git-3.1)
> warning: restarting
> debug: compiled with DVB API version 5.10
> debug: using DVB API version 5.10
> debug: Frontend "TurboSight TBS 6205 DVB-T/T2/C " supports:
> debug: frequency min: 42000000, max: 870000000, stepsize: 0, tolerance: 0
> debug: symbolrate min: 1000000, max: 7200000, tolerance: 0
> debug: capabilities:
> debug: INVERSION_AUTO
> debug: FEC_1_2
> debug: FEC_2_3
> debug: FEC_3_4
> debug: FEC_5_6
> debug: FEC_7_8
> debug: FEC_AUTO
> debug: QPSK
> debug: QAM_16
> debug: QAM_32
> debug: QAM_64
> debug: QAM_128
> debug: QAM_256
> debug: QAM_AUTO
> debug: TRANSMISSION_MODE_AUTO
> debug: GUARD_INTERVAL_AUTO
> debug: HIERARCHY_AUTO
> debug: 2G_MODULATION
> debug: MULTISTREAM
> debug: FE_CAN_MUTE_TS
> debug: delivery systems:
> debug: DVBT
> debug: DVBT2
> debug: DVBC_ANNEX_A
> debug: DVBC_ANNEX_B
> debug: tuning DVB-T2 frontend to f=706000000 bandwidth=8 inversion=-1
> fec_hp=999 fec_lp=999 hierarchy=-1 modulation=qam_256 guard=-1
> transmission=-1 PLP_ID=0
> warning: failed opening CAM device /dev/dvb/adapter0/ca0 (No such file or
> directory)
> debug: setting filter on PID 0
> debug: setting filter on PID 16
> debug: setting filter on PID 17
> debug: setting filter on PID 18
> debug: setting filter on PID 19
> debug: setting filter on PID 20
> debug: conf: 239.255.1.1:1234/tsid=1793 config=0x1 sid=1003 pids[0]
> debug: change sid tsid network
> debug: frontend has acquired signal
> debug: frontend has acquired carrier
>
> But no data are send out. :(
>
>
>
>
> On Thu, Feb 9, 2017 at 12:09 AM, Christophe Massiot <cmassiot at upipe.org>
> wrote:
>
>> You need to specify that you want DVB-T2 with -5 DVBT2.
>>
>> On 9 Feb 2017, at 00:00, peet freud <peetfreud at gmail.com> wrote:
>>
>>
>> The w_scan output is here:
>> http://pastebin.com/CFwQwC35
>>
>> In our country the DVB-T2 multiplex is on the frequency 706000 KHz.
>> As I have written in the first email - tvheadend can tune (on this
>> machine and with this card)
>> this multiplex and find the TV channels without problems.
>>
>> BTW Tvheadend working configuration:
>> {
>> "delsys": "DVBT2",
>> "frequency": 706000000,
>> "bandwidth": "8MHz",
>> "constellation": "QAM/256",
>> "transmission_mode": "AUTO",
>> "guard_interval": "AUTO",
>> "hierarchy": "AUTO",
>> "fec_hi": "AUTO",
>> "fec_lo": "AUTO",
>> "plp_id": -1,
>> "enabled": true,
>> "epg": 1,
>> "onid": 8395,
>> "tsid": 1793,
>> "scan_result": 1,
>> "pmt_06_ac3": 0
>> }
>>
>>
>> I have used for dvblast the configuration parameters working
>> for tvheadend, but dvblast is not working with them.
>>
>> There are 4 TV programs available with PIDs 1000,1003,1004,1005 in the
>> multiplex.
>>
>> I have tried this:
>>
>> cat ./dvblast.cfg
>> 239.255.1.1:1234/tsid=1793 1 1005
>>
>>
>> ./dvblast -c dvblast.cfg -a 1 -f 706000000 -b 8 -m qam_256
>> DVBlast 3.1 (git-3.1)
>> warning: restarting
>> debug: compiled with DVB API version 5.10
>> debug: using DVB API version 5.10
>> debug: Frontend "TurboSight TBS 6205 DVB-T/T2/C " supports:
>> debug: frequency min: 42000000, max: 870000000, stepsize: 0, tolerance: 0
>> debug: symbolrate min: 1000000, max: 7200000, tolerance: 0
>> debug: capabilities:
>> debug: INVERSION_AUTO
>> debug: FEC_1_2
>> debug: FEC_2_3
>> debug: FEC_3_4
>> debug: FEC_5_6
>> debug: FEC_7_8
>> debug: FEC_AUTO
>> debug: QPSK
>> debug: QAM_16
>> debug: QAM_32
>> debug: QAM_64
>> debug: QAM_128
>> debug: QAM_256
>> debug: QAM_AUTO
>> debug: TRANSMISSION_MODE_AUTO
>> debug: GUARD_INTERVAL_AUTO
>> debug: HIERARCHY_AUTO
>> debug: 2G_MODULATION
>> debug: MULTISTREAM
>> debug: FE_CAN_MUTE_TS
>> debug: delivery systems:
>> debug: DVBT
>> debug: DVBT2
>> debug: DVBC_ANNEX_A
>> debug: DVBC_ANNEX_B
>> debug: tuning DVB-T frontend to f=706000000 bandwidth=8 inversion=-1
>> fec_hp=999 fec_lp=999 hierarchy=-1 modulation=qam_256 guard=-1
>> transmission=-1
>> warning: failed opening CAM device /dev/dvb/adapter1/ca0 (No such file or
>> directory)
>> debug: setting filter on PID 0
>> debug: setting filter on PID 16
>> debug: setting filter on PID 17
>> debug: setting filter on PID 18
>> debug: setting filter on PID 19
>> debug: setting filter on PID 20
>> debug: conf: 239.255.1.1:1234/tsid=1793 config=0x1 sid=1005 pids[0]
>> debug: change sid tsid network
>>
>>
>> Thx.
>>
>> On Tue, Feb 7, 2017 at 8:02 PM, Otto Kellerman <wildiness at gmail.com>
>> wrote:
>>
>>> Alright. I used a DVB-T/T2/C+SDR device for DVB-C and there was 2
>>> frontends. One RTL for DVB-T and SDR and a Panasonic MN88473 for DVB-C and
>>> i think DVB-T2. Now to use DVB-C i had to force it to switch from DVB-T to
>>> DVB-C using w_scan -f c . I'm thinking you also have to force it over to
>>> DVB-T2. But i don't know how.
>>> Can you provide the output of w_scan?
>>>
>>> 2017-02-07 19:55 GMT+01:00 peet freud <peetfreud at gmail.com>:
>>>
>>>>
>>>> There are no more frontends :(
>>>>
>>>> ls /dev/dvb/adapter*
>>>> /dev/dvb/adapter0:
>>>> demux0 dvr0 frontend0 net0
>>>> /dev/dvb/adapter1:
>>>> demux0 dvr0 frontend0 net0
>>>> /dev/dvb/adapter2:
>>>> demux0 dvr0 frontend0 net0
>>>> /dev/dvb/adapter3:
>>>> demux0 dvr0 frontend0 net0
>>>>
>>>> Thx.
>>>> Peet
>>>>
>>>>
>>>> On Tue, Feb 7, 2017 at 7:27 PM, Otto Kellerman <wildiness at gmail.com>
>>>> wrote:
>>>>
>>>>> I'm thinking it might be on another frontend. Look in /dev/dvb/adapter0
>>>>> Also run w_scan and see what adapters it finds.
>>>>>
>>>>>
>>>>> Den 7 feb. 2017 19:14 skrev "peet freud" <peetfreud at gmail.com>:
>>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>> I have question about dvblast and DVB-T2 support.
>>>>>
>>>>> I would like to stream DVB-T2 with dvblast but it is not working.
>>>>> The DVB-T streaming works fine.
>>>>>
>>>>> Maybe it has something common that the utilities like tzap, wscan,
>>>>> dvbv5-scan/dvbv5-zap etc. are also not able to tune the multiplex.
>>>>>
>>>>> The only working program is tvheadend.
>>>>>
>>>>>
>>>>> I am using TBS6205 card, debian Jessie with backports
>>>>> - kernel 4.8.0-0
>>>>> - TBS drivers from git
>>>>> - compiled the latest version of dvblast
>>>>>
>>>>> Supports dvblast the dvb-t2 for streaming?
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Peet
>>>>>
>>>>> _______________________________________________
>>>>> dvblast-devel mailing list
>>>>> dvblast-devel at videolan.org
>>>>> https://mailman.videolan.org/listinfo/dvblast-devel
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> dvblast-devel mailing list
>>>>> dvblast-devel at videolan.org
>>>>> https://mailman.videolan.org/listinfo/dvblast-devel
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> dvblast-devel mailing list
>>>> dvblast-devel at videolan.org
>>>> https://mailman.videolan.org/listinfo/dvblast-devel
>>>>
>>>>
>>>
>>> _______________________________________________
>>> dvblast-devel mailing list
>>> dvblast-devel at videolan.org
>>> https://mailman.videolan.org/listinfo/dvblast-devel
>>>
>>>
>> _______________________________________________
>> dvblast-devel mailing list
>> dvblast-devel at videolan.org
>> https://mailman.videolan.org/listinfo/dvblast-devel
>>
>>
>>
>> _______________________________________________
>> dvblast-devel mailing list
>> dvblast-devel at videolan.org
>> https://mailman.videolan.org/listinfo/dvblast-devel
>>
>>
> _______________________________________________
> dvblast-devel mailing list
> dvblast-devel at videolan.org
> https://mailman.videolan.org/listinfo/dvblast-devel
>
>
>
> _______________________________________________
> dvblast-devel mailing list
> dvblast-devel at videolan.org
> https://mailman.videolan.org/listinfo/dvblast-devel
>
>
_______________________________________________
dvblast-devel mailing list
dvblast-devel at videolan.org
https://mailman.videolan.org/listinfo/dvblast-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/dvblast-devel/attachments/20170210/7b3c8478/attachment-0001.html>
More information about the dvblast-devel
mailing list