Hi :)
I have a FF DVB-C and a budget DVB-C, (they're both ves1820 devices) and the tuner on the FF card is v unreliable - I would like to avoid using it entirely.
Is there a magic one-line hack for VDR to bypass the device-selection logic and always use a specific device, and hence always force transfer mode from the budget card to the MPEG decoder on the FF card?
Cheers, Gavin.
On su, 2005-08-07 at 17:36 +0100, Gavin Hamill wrote:
Hi :)
I have a FF DVB-C and a budget DVB-C, (they're both ves1820 devices) and the tuner on the FF card is v unreliable - I would like to avoid using it entirely.
I'm having the same problem. My Fujitsu-Siemens DVB-C doesn't like the QAM128 signals broadcasted here but my other card, TechnoTrend FF, works fine. I still would like to continue using FuSi as the primary device because of it's RGB output.
Is there a magic one-line hack for VDR to bypass the device-selection logic and always use a specific device, and hence always force transfer mode from the budget card to the MPEG decoder on the FF card?
That would nice to have. I tried to bind all channels to the second card in channels.conf - no luck. The second card tuned correctly to all the channels and services but the primary card showed no picture at all. So something wrong with transfer mode when trying to use it like this.
On Sun, 7 Aug 2005, Gavin Hamill wrote:
Hi :)
I have a FF DVB-C and a budget DVB-C, (they're both ves1820 devices) and the tuner on the FF card is v unreliable - I would like to avoid using it entirely.
Is there a magic one-line hack for VDR to bypass the device-selection logic and always use a specific device, and hence always force transfer mode from the budget card to the MPEG decoder on the FF card?
When had the same problem Klaus suggested me to do the following:
http://www.linuxtv.org/pipermail/vdr/2005-April/001500.html
It worked very well.
regards, Patrick.
Gavin Hamill wrote:
Hi :)
I have a FF DVB-C and a budget DVB-C, (they're both ves1820 devices) and the tuner on the FF card is v unreliable - I would like to avoid using it entirely.
Is there a magic one-line hack for VDR to bypass the device-selection logic and always use a specific device, and hence always force transfer mode from the budget card to the MPEG decoder on the FF card?
The attached oneline patch causes dvb device 0 to look like a card with unknown frontend type, so VDR shouln't know how to use it. Untested.
On Sunday 07 August 2005 18:02, Anssi Hannula wrote:
Gavin Hamill wrote:
The attached oneline patch causes dvb device 0 to look like a card with unknown frontend type, so VDR shouln't know how to use it. Untested.
Perfect - both that and the 'If(PrimaryDevice) hacks pointed to by Patrick work like a charm for FTA chans, so I'm happy until I can get another FF card =)
Cheers, Gavin.
On su, 2005-08-07 at 19:22 +0100, Gavin Hamill wrote:
On Sunday 07 August 2005 18:02, Anssi Hannula wrote:
Gavin Hamill wrote:
The attached oneline patch causes dvb device 0 to look like a card with unknown frontend type, so VDR shouln't know how to use it. Untested.
Perfect - both that and the 'If(PrimaryDevice) hacks pointed to by Patrick work like a charm for FTA chans, so I'm happy until I can get another FF card =)
Like I mentioned befora, I'm having the same kind of problem. My primary card (Fujitsu-Siemens DVB-C) doesn't receive QAM128 channels at particular frequencies very well but I'd like to keep it because of the quality RGB output.
Tried both of these hacks to disable it's use as a receiver but with a disapppointment. Both of them cause ARM crashes/errors on the primary card (otherwise, the funtional part works ok and as expected):
dvb-ttpci: __av7110_send_fw_cmd(): timeout waiting for COMMAND idle dvb-ttpci: av7110_send_fw_cmd(): av7110_send_fw_cmd error -110 dvb-ttpci: av7110_fw_cmd error -110
and so on..
The "dvbdevice-avoid-0.diff" also makes channel changing untolerably slow but then again, it was untested and something like this could be expected.
-
Anssi Hannula -
Gavin Hamill -
Heikki Manninen -
Patrick Boettcher