vdr May 2005

vdr@linuxtv.org

154 participants
186 discussions

mounting smb drive to play recordings on remote server
by C.Y.M 19 May '05

19 May '05

I have setup a vdr client using streamdev client/server and xine. I would like to be able to play the recordings that are stored on the main server on the client. The client has a /video0 directory for its own recordings and I tried to mount /video1 as a smb drive. Unfortunately, no matter what I try, I can not get the /video1 directory to show in vdr. I have tried just making two directories on the local machine (not using smb) named /video0 and /video1 but still the second directory does not show up. I am starting vdr with "vdr -l 3 -v /video0 -c /etc/vdr -E /etc/vdr -P'xine -r'" Is there something Im missing? Best Regards,

3 4

VDR+DXR3 - stability problems
by Mikolaj Tutak 19 May '05

19 May '05

Hi! I use Creative DXR3 decoder and SkyStar2, a have folowing software versions: VDR 1.3.24/1.3.23 DXR3 Plugin (snapshot 0.2.3-cvs20050501, latest CVS does not support OSD) DXR3 Driver (latest CVS) Linux 2.6.11 SkyStar2 - b2c2_flexcop_pci (latest drivers from CVS linuxtv.org) sometimes VDR output hangs, and syslog comes like this: vdr[9688]: playing '/home/.other/video/....vdr' kernel: Fifo still full, trying stop cd9343e0 kernel: em8300.o: FIFO sync timeout during blocking write, n = 3414, copy_size = 0, total = 2048, free slots = 0 kernel: Fifo still full, trying stop cd9343e0 vdr[9688]: cDxr3Interface::Resuscitation Device failure detected kernel: em8300.o: FIFO sync timeout during blocking write, n = 5462, copy_size = 0, total = 0, free slots = 0 kernel: bt865.o: Configuring for PAL kernel: em8300_audio.o: Analog audio enabled vdr[9688]: cDxr3Interface::Resuscitation Microcode upload successful vdr[9688]: cDxr3Interface::Resuscitation Reopening devices took 1 kernel: em8300: Microcode version 0x29 loaded kernel: bt865.o: Configuring for PAL But the only solution is to stop VDR (sometimes it requires kill -9) and load it again. Dou you know any solution/workaround for this? Maybe other combination of DXR3 plugin/driver versions? -- Mikolaj Tutak

7 21

vdr: no primary device found - using first device!
by mauro.folcarelli＠sistinf.it 19 May '05

19 May '05

I get this message (vdr: no primary device found - using first device!) when I run vdr on my Linux box. Can anyone help me get the vdr software work? I apologies for the long message following, but I want to supply all information needed ... ============================================================================ Linux Kernel: 2.6.10-1.771_FC2 PC: i686 AMD Duron 600MHz Card: Hauppauge/TT WinTV Nexus-S Rev 2.3 dvb driver: dvb-1.1.0-35 ============================================================================ # lspci -vv 00:09.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) Subsystem: Technotrend Systemtechnik GmbH: Unknown device 000e Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 32 (3750ns min, 9500ns max) Interrupt: pin A routed to IRQ 11 Region 0: Memory at e3001000 (32-bit, non-prefetchable) ============================================================================ Modules loaded: Module Size Used by sr_mod 16548 0 ipt_LOG 6144 0 ipt_limit 2432 0 ipt_state 2048 0 iptable_mangle 2944 0 iptable_nat 23752 0 iptable_filter 3712 1 ip_conntrack_ftp 72240 0 ip_conntrack 40724 3 ipt_state,iptable_nat,ip_conntrack_ftp ip_tables 16512 6 ipt_LOG,ipt_limit,ipt_state,iptable_mangle,iptable_nat,iptable_filter nvidia 3919868 10 md5 4224 1 ipv6 215808 19 snd_mixer_oss 16512 1 snd_ens1371 21088 2 snd_rawmidi 22176 1 snd_ens1371 snd_seq_device 8204 1 snd_rawmidi snd_ac97_codec 63456 1 snd_ens1371 snd_pcm 81800 2 snd_ens1371,snd_ac97_codec snd_timer 21636 1 snd_pcm snd 48612 9 snd_mixer_oss,snd_ens1371,snd_rawmidi,snd_seq_device,snd_ac97_codec,snd_pcm,snd_timer soundcore 8800 2 snd snd_page_alloc 9476 1 snd_pcm gameport 4480 1 snd_ens1371 n_hdlc 8580 0 pppoatm 6016 0 ppp_generic 21780 1 pppoatm slhc 7168 1 ppp_generic bttv 139472 0 i2c_algo_bit 8456 1 bttv btcx_risc 4616 1 bttv dvb_ttpci 75180 0 ves1820 5636 1 dvb_ttpci stv0299 9220 1 dvb_ttpci tda8083 5636 1 dvb_ttpci stv0297 7944 1 dvb_ttpci sp8870 6796 1 dvb_ttpci ves1x93 6276 1 dvb_ttpci ttpci_eeprom 2560 1 dvb_ttpci i2c_core 20368 10 bttv,i2c_algo_bit,dvb_ttpci,ves1820,stv0299,tda8083,stv0297,sp8870,ves1x93,ttpci_eeprom dvb_core 71720 1 dvb_ttpci saa7146_vv 42752 1 dvb_ttpci video_buf 19716 2 bttv,saa7146_vv v4l1_compat 12292 1 saa7146_vv saa7146 17188 2 dvb_ttpci,saa7146_vv v4l2_common 5888 2 bttv,saa7146_vv videodev 9216 2 bttv,saa7146_vv usb_storage 59464 0 parport_pc 25284 1 lp 11180 0 parport 32456 2 parport_pc,lp 8139too 22400 0 mii 4736 1 8139too floppy 51920 0 sg 33312 0 scsi_mod 110464 3 sr_mod,usb_storage,sg vfat 12544 1 fat 36640 1 vfat dm_mod 52476 0 speedtch 12552 0 usb_atm 14128 1 speedtch atm 36824 2 pppoatm,usb_atm uhci_hcd 28824 0 ext3 115336 3 jbd 47640 1 ext3 ============================================================================ dvb devices: # ls -la /dev/dvb/adapter0 drwxrwxrwx 2 root root 4096 11 mag 18:56 . drwxr-xr-x 3 root root 4096 11 mag 18:56 .. crw-rw-rw- 1 root video 212, 1 11 mag 18:56 audio0 crw-rw-rw- 1 root video 212, 6 11 mag 18:56 ca0 crw-rw-rw- 1 root video 212, 4 11 mag 18:56 demux0 crw-rw-rw- 1 root video 212, 5 11 mag 18:56 dvr0 crw-rw-rw- 1 root video 212, 3 11 mag 18:56 frontend0 crw-rw-rw- 1 root video 212, 7 11 mag 18:56 net0 crw-rw-rw- 1 root video 212, 8 11 mag 18:56 osd0 crw-rw-rw- 1 root video 212, 0 11 mag 18:56 video0 ============================================================================ Other video devices: # ls -la /dev/video* crw-rw-rw- 1 root root 81, 0 23 feb 2004 /dev/video0 crw-rw-rw- 1 root root 81, 1 23 feb 2004 /dev/video1 crw-rw-rw- 1 root root 81, 2 23 feb 2004 /dev/video2 crw-rw-rw- 1 root root 81, 3 23 feb 2004 /dev/video3 /dev/video: totale 132 drwxrwxrwx 3 root root 4096 9 mag 20:34 . drwxr-xr-x 24 root root 118784 14 mag 10:44 .. crw-rw-rw- 1 root root 10, 204 23 feb 2004 em8300 crw-rw-rw- 1 root root 10, 206 23 feb 2004 em8300_ma crw-rw-rw- 1 root root 10, 205 23 feb 2004 em8300_mv crw-rw-rw- 1 root root 10, 207 23 feb 2004 em8300_sp -rw-rw-rw- 1 root root 1033 9 mag 20:34 setup.conf drwxrwxrwx 2 root root 4096 9 mag 20:34 themes /dev/video1394: totale 124 drwxrwxrwx 2 root root 4096 3 set 2004 . drwxr-xr-x 24 root root 118784 14 mag 10:44 .. crwxrwxrwx 1 root root 171, 16 23 feb 2004 0 crwxrwxrwx 1 root root 171, 17 23 feb 2004 1 crwxrwxrwx 1 root root 171, 18 23 feb 2004 2 crwxrwxrwx 1 root root 171, 19 23 feb 2004 3 ============================================================================ script used to run vdr: #!/bin/bash # export LD_ASSUME_KERNEL=2.4.1 export LANG=it_IT /usr/sbin/vdr --video=/mnt/spazio/spoolvideo --epgfile=/mnt/spazio/spoolepg \ --config=/etc/vdr --lib=/etc/vdr/plugins.d --device=0 \ --terminal=/dev/tty8 exit 0 ============================================================================ vdr versions tested: vdr-1.3.24-0.1.i386.rpm and vdr-1.2.6.tar.bz2 (with the same result) Thank you! Mauro Folcarelli

8 13

How often should epg.data update
by Kartsa 18 May '05

18 May '05

I noticed that vdradmin showed yesterdays programinfo in "Playing today" page. Took a look in epg.data file and last update is more than 24 hours ago. I've made no changes to vdr and it has been working quite nicely some time now (seems like a bit more than 4 days this time). Timers are still working as they should. Actually everything else but epg.data seems to be working right. First thought that maybe epg has not been updated but that would not seem to be propable for all the channels at the same time would it. No log entrys at the time of the last update of epg.data. Any ideas? vdr 1.2.23 + subtitle 0.3.7 - Kartsa No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.11.10 - Release Date: 13.5.2005

3 4

RE: [vdr] mounting smb drive to play recordings on remote server
by Vladimir Shved 18 May '05

18 May '05

I think so, to update resume file, cut marks, etc. Although I don't know for sure, did not try it. > -----Original Message----- > From: vdr-bounces(a)linuxtv.org [mailto:vdr-bounces@linuxtv.org] On Behalf > Of C.Y.M > Sent: Wednesday, May 18, 2005 12:26 PM > To: Vdr > Subject: Re: [vdr] mounting smb drive to play recordings on remote server > > Vladimir Shved wrote: > > I think you might need the FAT32 support enabled in VDR for this to > work. > > > > > > Does the /video1 directory (smb) need to be writable? I'll recompile with > VFAT=1 > and see.. > > Thanks, > C.Y.M. > > > _______________________________________________ > vdr mailing list > vdr(a)linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

2 1

RE: [vdr] mounting smb drive to play recordings on remote server
by Vladimir Shved 18 May '05

18 May '05

I think you might need the FAT32 support enabled in VDR for this to work. > -----Original Message----- > From: vdr-bounces(a)linuxtv.org [mailto:vdr-bounces@linuxtv.org] On Behalf > Of C.Y.M > Sent: Wednesday, May 18, 2005 12:17 PM > To: Vdr > Subject: [vdr] mounting smb drive to play recordings on remote server > > I have setup a vdr client using streamdev client/server and xine. I would > like > to be able to play the recordings that are stored on the main server on > the > client. The client has a /video0 directory for its own recordings and I > tried > to mount /video1 as a smb drive. Unfortunately, no matter what I try, I > can not > get the /video1 directory to show in vdr. I have tried just making two > directories on the local machine (not using smb) named /video0 and /video1 > but > still the second directory does not show up. I am starting vdr with "vdr > -l 3 > -v /video0 -c /etc/vdr -E /etc/vdr -P'xine -r'" Is there something Im > missing? > > Best Regards, > > _______________________________________________ > vdr mailing list > vdr(a)linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

2 1

[Fwd: [MPlayer-dev-eng] [PATCH] get_time_pos slave commando]
by C.Y.M 18 May '05

18 May '05

Would this new addition to mplayer help show the proper position of native .vdr files in the mplayer plugin? Best Regards,

2 2

Fix for DVB subtitles crash at exit (with plugin primary device)
by Ville Skyttä 18 May '05

18 May '05

Here's a patch for the subtitles plugin that fixes a crash when shutting down VDR. Patch already sent upstream. The crash can probably occur only when the primary device is implemented by a plugin which has already been shut down before the DVB subtitles plugin.

1 0

Error using the scan utility.
by Rudy Sgorlon 18 May '05

18 May '05

Any idea why I have this errors using the scan utility? Thanks, Rudy. May 18 18:28:46 Vdrbox kernel: dvb-ttpci: StartHWFilter error buf 0b07 0010 1206 b96a ret 0 handle ffff May 18 18:28:52 Vdrbox kernel: StopHWFilter tried to stop invalid filter ffff, filter type = 1 May 18 18:28:57 Vdrbox kernel: dvb-ttpci: StartHWFilter error buf 0b07 0010 13ab b96a ret 0 handle ffff May 18 18:28:57 Vdrbox kernel: dvb-ttpci: StartHWFilter error buf 0b07 0010 13ac b96a ret 0 handle ffff May 18 18:28:57 Vdrbox kernel: dvb-ttpci: StartHWFilter error buf 0b07 0010 13ad b96a ret 0 handle ffff May 18 18:28:57 Vdrbox kernel: dvb-ttpci: StartHWFilter error buf 0b07 0010 13ae b96a ret 0 handle ffff May 18 18:29:03 Vdrbox kernel: StopHWFilter tried to stop invalid filter ffff, filter type = 1

1 0

osdteletext page 100-00 not found
by Simon Baxter 18 May '05

18 May '05

Hi. Has anyone got this working on gb Teletext? I get "page 100-00 not found" and the current time (updating). I get the same if I select a different page thanks Simon

4 5

← Newer
1
...
7
8
9
10
11
12
13
...
19
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr May 2005