[dvblast-devel] Can dvblast stream to a file?

Doychin Dokov dokov at silistra.tv
Sun Dec 29 16:13:56 CET 2013


TBS hardware?

On Sunday, December 29, 2013, cedric.dewijs at telfort.nl wrote:

> Le 29 déc. 2013 à 14:51, cedric.dewijs at telfort.nl a écrit :
>
> > I have an USB DVB-T receiver. Also I have a digitenne smartcard with a smargo cardreader. This is everything I need to capture, decrypt, and store a TV show. This works fine on a normal PC.
>
> > I would like to record my shows on a D-link DNS-323 NAS. The ARM CPU on this device is very slow, so it cannot decode multiple TV shows in realtime.
>
> >
> > I would like to get the datastream from the receiver, and then store it in encrypted form on the hard drive. The CPU is fast enough to do this for multiple channels at the same time in realtime.
>
> > Next I would launch a low-priority task to decrypt the file, and store the result into a new file. When completed, this decrypted file can then be made accessible via samba.
>
> >
> > Can dvblast stream to a file? Is there a utility that can take the network stream from dvblast, and place it into a file?
>
>
> > Yes, what you are looking for is multicat.
>
> I am trying to stream 'Nederland 1' to a file. It's a free to air channel
> with the following parameters:
> 474000000 Hz
> Video PID = 1B63
> Audio PID = 1B64
>
> I have edited dvblast.conf:
> 127.0.0.1:9999
>
> I have then started multicat:
> # multicat 127.0.0.1:9999 test.ts
>
> Then I've started dvblast:
> # dvblast -a 1 -f 474000000 -c ~/dvblast.conf
>
> Now I get the message: "warning: no DVR output, resetting"
> The file test.ts is 0 bytes.
>
> Full output:
> # dvblast -a 1 -f 474000000 -c ~/dvblast.conf
> DVBlast 2.2 (release)
> warning: restarting
> debug: using linux-dvb API version 5
> debug: Frontend "DiBcom 7000PC" type "OFDM (DVB-T)" supports:
> debug:  frequency min: 45000000, max: 860000000, stepsize: 62500,
> tolerance: 0
> debug:  symbolrate min: 0, max: 0, 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_64
> debug:   QAM_AUTO
> debug:   TRANSMISSION_MODE_AUTO
> debug:   GUARD_INTERVAL_AUTO
> debug:   HIERARCHY_AUTO
> debug:   FE_CAN_RECOVER
> debug: tuning OFDM frontend to f=474000000 bandwidth=8 inversion=-1
> fec_hp=999 fec_lp=999 hierarchy=-1 modulation=qam_auto 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: frontend has acquired signal
> debug: frontend has acquired carrier
> debug: frontend has acquired sync
> info: frontend has acquired lock
> frontend has acquired lock
> debug: - Bit error rate: 2097151
> debug: - Signal strength: 2056282
> debug: - SNR: 2031650
> warning: no DVR output, resetting
> debug: tuning OFDM frontend to f=474000000 bandwidth=8 inversion=-1
> fec_hp=999 fec_lp=999 hierarchy=-1 modulation=qam_auto guard=-1
> transmission=-1
> debug: frontend has acquired signal
> debug: frontend has acquired carrier
> debug: frontend has acquired sync
> info: frontend has acquired lock
> frontend has acquired lock
> debug: - Bit error rate: 2097151
> debug: - Signal strength: 2056058
> debug: - SNR: 2031649
> warning: no DVR output, resetting
> debug: tuning OFDM frontend to f=474000000 bandwidth=8 inversion=-1
> fec_hp=999 fec_lp=999 hierarchy=-1 modulation=qam_auto guard=-1
> transmission=-1
> debug: frontend has acquired signal
> debug: frontend has acquired carrier
> debug: frontend has acquired sync
> info: frontend has acquired lock
> frontend has acquired lock
> debug: - Bit error rate: 2097151
> debug: - Signal strength: 2055994
> debug: - SNR: 2031652
> ^Cinfo: Shutdown was requested.
>
> Best regards,
> Cedric
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/dvblast-devel/attachments/20131229/8f00136d/attachment-0001.html>


More information about the dvblast-devel mailing list