VLC and dvb-t not working in Ubuntu 11.10

[jlanza]

Hi all,

As I said, everything was working fine till I upgraded to Ubuntu 11.10. Right now I'm not able to view DVB-T channels. This is using VLC 1.1.12 UBuntu.
The issue is that using the scan application I'm able to generate the channels.conf file. However when running vlc channels.conf I get the following error:

main stream error: cannot pre fill buffer

I then start me-TV thinking that it will fail too, but to my surprise it worked fine.

Could you point me to some solution? I've been reading on forums and web and people points the problem is because of kernel 3.0 and vl4 driver, but I don't understand why is it working correctly with Me-TV.

Any help is more than welcome.

[Rémi Denis-Courmont]

Did you select a channel or does it fail to open the playlist?

[jlanza]

This message is the output when selecting channels. The playlist have all the channels, but it seems that it is not tuning or something. The issue is that I haven't touch anything neither in my vlc configuration nor in the channels.conf. What is more it is working with Me-TV.

[dbrb2]

Was a solution ever found for this? I can generate my scan file fine, play in me-tv fine, but on loading channels.conf into VLC I get "cannot pre fill buffer" when selection a channel (WinTV-Duet, VLC Luggage)

[dbrb2]

...I have now run VLC from the command line with the vvv flag. I get:

[0x8f123cc] dvb access debug: Opening device /dev/dvb/adapter2/frontend0
[0x8f123cc] dvb access debug: Frontend Info:
[0x8f123cc] dvb access debug: name = DiBcom 7000PC
[0x8f123cc] dvb access debug: type = OFDM (DVB-T)
[0x8f123cc] dvb access debug: frequency_min = 45000000 (kHz)
[0x8f123cc] dvb access debug: frequency_max = 860000000 (kHz)
[0x8f123cc] dvb access debug: frequency_stepsize = 62500
[0x8f123cc] dvb access debug: frequency_tolerance = 0
[0x8f123cc] dvb access debug: symbol_rate_min = 0 (kHz)
[0x8f123cc] dvb access debug: symbol_rate_max = 0 (kHz)
[0x8f123cc] dvb access debug: symbol_rate_tolerance (ppm) = 0
[0x8f123cc] dvb access debug: notifier_delay (ms) = 0
[0x8f123cc] dvb access debug: Frontend Info capability list:
[0x8f123cc] dvb access debug: inversion auto
[0x8f123cc] dvb access debug: forward error correction 1/2
[0x8f123cc] dvb access debug: forward error correction 2/3
[0x8f123cc] dvb access debug: forward error correction 3/4
[0x8f123cc] dvb access debug: forward error correction 5/6
[0x8f123cc] dvb access debug: forward error correction 7/8
[0x8f123cc] dvb access debug: forward error correction auto
[0x8f123cc] dvb access debug: card can do QPSK
[0x8f123cc] dvb access debug: card can do QAM 16
[0x8f123cc] dvb access debug: card can do QAM 64
[0x8f123cc] dvb access debug: card can do QAM auto
[0x8f123cc] dvb access debug: transmission mode auto
[0x8f123cc] dvb access debug: guard interval mode auto
[0x8f123cc] dvb access debug: hierarchy mode auto
[0x8f123cc] dvb access debug: card can recover from a cable unplug
[0x8f123cc] dvb access debug: End of capability list
[0x8f123cc] dvb access debug: trying to tune the frontend...
[0x8f123cc] dvb access debug: using inversion=2
[0x8f123cc] dvb access debug: using bandwidth=8
[0x8f123cc] dvb access debug: using fec=9
[0x8f123cc] dvb access debug: using fec=9
[0x8f123cc] dvb access debug: using transmission=8
[0x8f123cc] dvb access debug: using guard=32
[0x8f123cc] dvb access debug: using hierarchy=-1
[0x8f123cc] dvb access debug: Opening device /dev/dvb/adapter2/dvr0
[0x9053b24] main input debug: TIMER input launching for '5 USA' : 23006.206 ms - Total 23006.206 ms / 1 intvls (Avg 23006.205 ms)
[0x8f123cc] dvb access debug: setting filter on PAT
[0x8f123cc] dvb access debug: Opening device /dev/dvb/adapter2/demux0
[0x8f123cc] dvb access debug: DMXSetFilter: DMX_PES_OTHER for PID 0
[0x8f123cc] dvb access debug: Opening device /dev/dvb/adapter2/ca0
[0x8f123cc] dvb access warning: CAMInit: opening CAM device failed (No such file or directory)
[0x8f123cc] main access debug: using access module "dvb"
[0x8f123cc] main access debug: TIMER module_need() : 6.304 ms - Total 6.304 ms / 1 intvls (Avg 6.304 ms)
[0x8d54964] main stream debug: Using AStream*Block
[0x8d54964] main stream debug: pre buffering
[0x8d1568c] qt4 interface debug: IM: Setting an input
[0x8f123cc] dvb access debug: frontend has acquired signal
[0x8f123cc] dvb access debug: frontend has acquired carrier
[0x8f123cc] dvb access debug: frontend has acquired stable FEC
[0x8f123cc] dvb access debug: frontend has acquired sync
[0x8f123cc] dvb access debug: frontend has acquired lock
[0x8f123cc] dvb access debug: - Bit error rate: 0
[0x8f123cc] dvb access debug: - Signal strength: 39285
[0x8f123cc] dvb access debug: - SNR: 232


Which as far as I can tell is all fine...except that I see no actual video...Ideas?

[dbrb2]

...updating from luggage to twoflower seems to have solved this problem...but does anyone have any ideas what the root cause might have been? Whatever it is seems to affect dvBlast as well...