Mailing List archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[vdr] Re: newbie lost in space



Hi,

Tony Grant wrote:

Output from system messages :

Mar 20 18:01:46 localhost vdr[9335]: VDR version 1.2.6 started
Mar 20 18:01:46 localhost vdr[9335]: loading plugin:
./PLUGINS/lib/libvdr-xine.so.1.2.6
Mar 20 18:01:46 localhost vdr[9335]: loading /video/sources.conf
Mar 20 18:01:46 localhost vdr[9335]: loading /video/diseqc.conf
Mar 20 18:01:46 localhost vdr[9335]: loading /video/channels.conf
Mar 20 18:01:46 localhost vdr[9335]: loading /video/svdrphosts.conf
Mar 20 18:01:46 localhost vdr[9335]: loading /video/ca.conf
Mar 20 18:01:46 localhost vdr[9335]: loading /video/keymacros.conf
Mar 20 18:01:46 localhost vdr[9335]: found 1 video device
Mar 20 18:01:46 localhost vdr[9335]: initializing plugin: xine (0.1.1):
Software based playback using xine
Mar 20 18:01:46 localhost vdr[9335]: setting primary device to 1
Mar 20 18:01:46 localhost vdr[9335]: device 1 has no MPEG decoder
Mar 20 18:01:46 localhost vdr[9335]: trying device number 2 instead
Mar 20 18:01:46 localhost vdr[9335]: setting primary device to 2
Mar 20 18:01:46 localhost vdr[9335]: SVDRP listening on port 2001
Mar 20 18:01:46 localhost vdr[9335]: starting plugin: xine
Do you find lines like:

Mar 21 20:29:23 video vdr[7050]: switching to channel 7
Mar 21 20:29:23 video vdr[7061]: transfer thread started (pid=7061, tid=131081)
Mar 21 20:29:23 video vdr[7062]: receiver on device 1 thread started (pid=7062, tid=147466)


It looks to me like your channels.conf, diseqc.conf or LNB-Setup in VDR is not totally correct.

Verify, that the tuner has locked to the tuned channel (while VDR is running):

video:/soft/src # linux-dvb.2003-11-08/apps/szap/femon
using '/dev/dvb/adapter0/frontend0'
FE: STV0299/TSA5059/SL1935 based (SAT)
status 1f | signal b542 | snr e75d | ber 0000ff00 | unc 00000000 | FE_HAS_LOCK
status 1f | signal b680 | snr e424 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal b683 | snr e7b4 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal b68a | snr e72a | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal b685 | snr e772 | ber 00000000 | unc 00000000 | FE_HAS_LOCK

How do I get xine to read from the correct device?
xine already does a good job, as you see this "beautiful" NO SIGNAL message. My plugin sends this little stream to have xine display an OSD.

Have you seen the remote teach mode OSD of VDR so far? Maybe you should delete remote.conf to make it appear again. Make shure, to focus the console window where you started vdr from, when you type any keys. You might also use my remote.conf.

From /var/log/messages I assume, that you have a single low budget card (device 1). So my plugin supplies you a further device (device 2) which is used for OSD and replay.

On systems like that, VDR automatically starts a transfer thread that copies the received data from device 1 to device 2 for display. Make shure that the logfile contains a message about buffer usage > 0%, when switching channels. Otherwise you have a tuning issue.

Bye.
--
Dipl.-Inform. (FH) Reinhard Nissl
mailto:rnissl@gmx.de



--
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe vdr" as subject.



Home | Main Index | Thread Index