When trialing vdr-femon-1.1.0 with vdr-xineliboutput-1.0.0_rc1 I receive the following error when trying to view the signal information of my recording server via my streaming only client.
ERROR: cFemonOsd::Show() cannot open frontend device.
Is this a known problem or is there something more I need to configure for my specific setup?
[I need Femon to investigate dvb-t signal issues:- with vdr running the signal to my old freeview settop box is degraded to an unusable level. Signal from common aerial is being split with a "1 in 2 out" signal amplifier. There's a 25m cable to the vdr server and a 12m cable to the set top box.]
Any advice gladly received!
hi,
you could try to use femon (the console application) in the dvb-utils package.
Alasdair Campbell schrieb:
When trialing vdr-femon-1.1.0 with vdr-xineliboutput-1.0.0_rc1 I receive the following error when trying to view the signal information of my recording server via my streaming only client.
ERROR: cFemonOsd::Show() cannot open frontend device.
Is this a known problem or is there something more I need to configure for my specific setup?
[I need Femon to investigate dvb-t signal issues:- with vdr running the signal to my old freeview settop box is degraded to an unusable level. Signal from common aerial is being split with a "1 in 2 out" signal amplifier. There's a 25m cable to the vdr server and a 12m cable to the set top box.]
Any advice gladly received!
Alasdair Campbell wrote:
When trialing vdr-femon-1.1.0 with vdr-xineliboutput-1.0.0_rc1 I ... Any advice gladly received!
Try the current versions?
Femon 1.1.4: http://www.saunalahti.fi/~rahrenbe/vdr/femon/ Xineliboutput 1.0.0rc2: http://phivdr.dyndns.org/vdr/vdr-xineliboutput/
-Petri
On Sun, 20 May 2007, Alasdair Campbell wrote:
Is this a known problem or is there something more I need to configure for my specific setup?
Yes, it's a known problem reported only in xineliboutput setups: somehow "cDevice::ActualDevice()->CardIndex()" returns invalid values. I cannot reproduce this error in my FF card setup, so I'm just blaming xineliboutput for messing up VDR's devices and haven't had any efforts to debug it further. :)
-- rofa
On 20/05/07, Rolf Ahrenberg rahrenbe@cc.hut.fi wrote:
On Sun, 20 May 2007, Alasdair Campbell wrote:
Is this a known problem or is there something more I need to configure for my specific setup?
Yes, it's a known problem reported only in xineliboutput setups: somehow "cDevice::ActualDevice()->CardIndex()" returns invalid values. I cannot reproduce this error in my FF card setup, so I'm just blaming xineliboutput for messing up VDR's devices and haven't had any efforts to debug it further. :)
Thanks for letting me know. The results from femon on the console weren't too enlightening so I'll try the linux-dvb mailing list.