DVB-C Streaming

[adam2009]

Hello, been trying to stream DVBC via VLC but can't get it working. I've put in the freqency and symbol rate, is there anything else I need to do?

[Jean-Baptiste Kempf]

Try to play and see if you can play it. Then, you can stream

[adam2009]

It's a hybrid card with both analogue and digital. Vlc is only decting the analogue part of the card.

[VLC_help]

And your card has BDA drivers? (e.g. ProgDVB works with it)

[adam2009]

Yes, it has BDA drivers. Works with dvbviewer and dvbdream. Haven't tried progdvb.

http://www.terratec.net/en/products/tec ... 57350.html

[VLC_help]

Then VLC should detect it. What does Tools -> Messages... (set Verbosity to 2) display when you try open DVB? (open messages before you try to open DVB)

[adam2009]

It says this.

qt4 warning: Input option: dvb-srate=6887
main debug: adding item `dvb-c://frequency=570000000' ( dvb-c://frequency=570000000 )
qt4 debug: Adding a new MRL to recent ones: dvb-c://frequency=570000000
main debug: rebuilding array of current - root Playlist
main debug: rebuild done - 2 items, index 0
main debug: processing request item dvb-c://frequency=570000000 node null skip 0
main debug: resyncing on dvb-c://frequency=570000000
main debug: dvb-c://frequency=570000000 is at 1
main debug: starting new item
main debug: creating new input thread
main debug: Creating an input for 'dvb-c://frequency=570000000'
main debug: thread (input) created at priority 1 (../.././src/input/input.c:230)
main debug: thread started
main debug: using timeshift granularity of 50 MBytes
main debug: using timeshift path 'E:\Users\Len\AppData\Local\Temp'
main debug: `dvb-c://frequency=570000000' gives access `dvb-c' demux `' path `frequency=570000000'
main debug: creating demux: access='dvb-c' demux='' path='frequency=570000000'
main debug: looking for access_demux module: 0 candidates
main debug: no access_demux module matched "dvb-c"
main debug: TIMER module_need() : 1.000 ms - Total 1.000 ms / 1 intvls (Avg 1.000 ms)
main debug: creating access 'dvb-c' path='frequency=570000000'
main debug: looking for access module: 1 candidate
bda debug: CreateTuneRequest: Using Tuning Space: DD2 DVB-C
qt4 debug: IM: Setting an input
bda debug: Build: Using Tuning Space ID 6
qt4 debug: Updating the geometry
qt4 debug: Updating the geometry
bda debug: FindFilter: Connected Cinergy HTC USB XS DVB-C Tuner
bda debug: BDAGraph: Using adapter 1
bda debug: FindFilter: Connected Cinergy HTC USB XS Digital Capture
bda debug: Build: Trying connecting with subtype MEDIASUBTYPE_MPEG2_TRANSPORT
bda warning: Build: Cannot connect Sample Grabber to Capture device: hr=0x80004005 (try 1/2)
bda debug: Build: Trying connecting with subtype KSDATAFORMAT_SUBTYPE_BDA_MPEG2_TRANSPORT
bda debug: FindFilter: Connected BDA MPEG2 Transport Information Filter
bda debug: Graph started hr=0x8007001f
bda warning: Start: Graph not started: 0
bda warning: Start: Cannot stop Graph after Run failed: hr=0x8007001f
bda debug: Build: Using Tuning Space ID 6
bda warning: FindFilter: No filter connected: hr=0x80004005
bda warning: Build: Cannot load tuner device and connect network provider: hr=0x80004005
bda warning: SubmitDVBCTuneRequest: Cannot Build the Graph: hr=0x80004005
bda warning: DVB_Open: Unsupported Network dvb-c
main warning: no access module matching "dvb-c" could be loaded
main debug: TIMER module_need() : 322.000 ms - Total 322.000 ms / 1 intvls (Avg 322.000 ms)
main error: open of `dvb-c://frequency=570000000' failed: (null)
main debug: thread ended
main debug: dead input
main debug: thread times: real 0m0.328018s, kernel 0m0.109200s, user 0m0.000000s
main debug: changing item without a request (current 1/2)
main debug: nothing to play
qt4 debug: IM: Deleting the input
qt4 debug: Updating the geometry
qt4 debug: Updating the geometry
main debug: TIMER input launching for 'dvb-c://frequency=570000000' : 381.000 ms - Total 381.000 ms / 1 intvls (Avg 381.000 ms)

[KenS]

The good news is that its finding the right device the first time but appears to be not receiving a signal.
Error 0x8007001f apparently means "A device attached to the system is not functioning" and some devices apparently return that code when they are not receiving.
I say apparently because the error code is poorly documented.

I suspect srate. My memory is poor but 6887 does not look right. I would have thought something more like 6887000
This thread may offer some clues