Hi,
I started to play with "vdr" now. my system is FC5 w/ Twinhan-1025A budget card. After I use linux-dvb-apps-1.0.0's scan and szap program, I can use xine to view satellite dvb TV program now (only unencrypted channel :( ).
So now I downloaded vdr-1.4.0.tar.bz2, and uncompressed it as vdr-1.4.0, in that directory, I type make, and got an excutable vdr, but when I run it, I get the following error: --------------------------------------------- [zhuhx@pc1 vdr-1.4.0]$ ./vdr vdr: can't access video directory /video ---------------------------------------------
I only have /dev/dvb/adaptor0 with "demux0 dvr0 frontend0 net0" subdirectory.
I notice in Makefile these is "VIDEODIR=/video", how can I change it? looks like I have to do something, but in INSTALL, I didn't find the instructions.
Do I need other software packages?
one more question: each time I start my FC5, I have to do the following ---------------------- $modprobe bttv i2c_hw=1 card=0x71 $modprobe dvb_bt8xx $modprobe dst dst_algo=0 ---------------------- How can I let the PC to do these automatically?
Thanks, Paul
Paul ZHU schrieb:
Hi,
I started to play with "vdr" now.
Welcome on board. :)
I notice in Makefile these is "VIDEODIR=/video", how can I change it? looks like I have to do something, but in INSTALL, I didn't find the instructions.
Please try "vdr --help". VDR will then tell you all commandline switches. There is also the option -v <videodir> mentioned. This directory is not related to any tv card in your computer but used by vdr to store the recordings.
Best regards, Lutz
Paul ZHU wrote:
Hi,
I started to play with "vdr" now. my system is FC5 w/ Twinhan-1025A budget card. After I use linux-dvb-apps-1.0.0's scan and szap program,
Did you install this package from source? A newer version (1.1.0) is available in Fedora Extras, the package is named dvb-apps.
I can use xine to view satellite dvb TV program now (only unencrypted channel :( ).
So now I downloaded vdr-1.4.0.tar.bz2, and uncompressed it as vdr-1.4.0, in that directory, I type make, and got an excutable vdr,
There are rpms of vdr and several plugins available at rpm.livna.org. For instructions on how to set up this repository to use it with yum please have a look at http://rpm.livna.org/configuration.html
After installing the package you can just start vdr with "service vdr start" (as root and without the quotes, of course). The video directory used in this package is /srv/vdr, it will be setup with the correct permissions automatically.
Regards, Andreas.
On Wed, 2006-05-03 at 13:54 +0200, Andreas Mueller wrote:
There are rpms of vdr and several plugins available at rpm.livna.org. For instructions on how to set up this repository to use it with yum please have a look at http://rpm.livna.org/configuration.html
After installing the package you can just start vdr with "service vdr start" (as root and without the quotes, of course). The video directory used in this package is /srv/vdr, it will be setup with the correct permissions automatically.
Regards, Andreas.
I don't want to use rpm packages because I am interested in playing with the source code.
now when I run "vdr",I get the following error: ----------------------------------- [zhuhx@pc1 vdr-1.4.0]$ vdr vdr: no primary device found - using first device! [zhuhx@pc1 vdr-1.4.0]$ -----------------------------------
any ideas? Thanks, Paul
Paul ZHU schrieb:
now when I run "vdr",I get the following error:
[zhuhx@pc1 vdr-1.4.0]$ vdr vdr: no primary device found - using first device! [zhuhx@pc1 vdr-1.4.0]$
This error indicates, that you only have a budget card installed. VDR does not know where to display the video. If you don't want to buy a card with playback capabilities, you have to use some plugin that implements a device for output in software. Maybe via xine or framebuffer. Please have a look at the plugins mentioned on the vdr website.
Hi
On 4:01:17 pm 03/05/2006 Lutz Bender l.bender@hagener-feinstahl.de wrote:
card with playback capabilities, you have to use some plugin that implements a device for output in software. Maybe via xine or
On this subject - I've been using the xine plugin for a while, but I've noticed that there do seem to be others (notably softdevice/streamdev). Is there a guide somewhere to how these differ? I guess my ideal solution would be to access VDR through gstreamer/totem, but some googling suggests that that isn't possible at the moment, so I'm just looking for something a bit simpler than the xine plugin (if only so I can avoid recompiling xine).
Cheers, --- Chris Jones cmsj@tenshu.net www.tenshu.net
在 2006-05-03三的 16:32 +0100，Chris Jones写道：
Hi
On 4:01:17 pm 03/05/2006 Lutz Bender l.bender@hagener-feinstahl.de wrote:
card with playback capabilities, you have to use some plugin that implements a device for output in software. Maybe via xine or
On this subject - I've been using the xine plugin for a while, but I've noticed that there do seem to be others (notably softdevice/streamdev). Is there a guide somewhere to how these differ? I guess my ideal solution would be to access VDR through gstreamer/totem, but some googling suggests that that isn't possible at the moment, so I'm just looking for something a bit simpler than the xine plugin (if only so I can avoid recompiling xine).
Yes, I have a budget card twinhan VP-1025A which comes no mpeg2 decoder. I don't mind buy a full-featured card later. but right now I also want to play with this economical card with plugins.
BTW, when using "root", it has no such messages like "vdr: no primary device found - using first device!", but just sits there do nothing. syslog indicates OSD error, lkie these:
-------------------------- [root@pc1 zhuhx]# tail /var/log/messages May 3 23:39:38 pc1 vdr: [4037] found 1 video device May 3 23:39:38 pc1 vdr: [4037] setting primary device to 1 May 3 23:39:38 pc1 vdr: [4037] device 1 has no MPEG decoder May 3 23:39:38 pc1 vdr: [4037] SVDRP listening on port 2001 May 3 23:39:38 pc1 vdr: [4037] loading /video/themes/sttng-default.theme May 3 23:39:38 pc1 vdr: [4037] loading /video/themes/sttng-default.theme May 3 23:39:38 pc1 vdr: [4037] ERROR: no OSD provider available - using dummy O SD! May 3 23:39:48 pc1 vdr: [4037] switching to channel 1 May 3 23:39:48 pc1 vdr: [4037] info: Channel not available! May 3 23:39:48 pc1 vdr: [4037] ERROR: no OSD provider available - using dummy O SD! [root@pc1 zhuhx]# ----------------------------
So I have to use some plugins for vdr? I will research a bit on these tomorrow.
But wait, wait, I know a package vdr-xine-0.7.9.tgz is for vdr as a plugin for xine, now you told me I also need xine to be a plugin for vdr, I got confused!!! could you please explain more on these plugin thing?
Best regards, Paul ZHU
On Wed, 03 May 2006 16:32:18 +0100 "Chris Jones" cmsj@tenshu.net wrote:
Hi
On 4:01:17 pm 03/05/2006 Lutz Bender l.bender@hagener-feinstahl.de wrote:
card with playback capabilities, you have to use some plugin that implements a device for output in software. Maybe via xine or
On this subject - I've been using the xine plugin for a while, but I've noticed that there do seem to be others (notably softdevice/streamdev). Is there a guide somewhere to how these differ? I guess my ideal solution would be to access VDR through gstreamer/totem, but some googling suggests that that isn't possible at the moment, so I'm just looking for something a bit simpler than the xine plugin (if only so I can avoid recompiling xine).
Check this out: http://users.tkk.fi/~phintuka/vdr/vdr-xineliboutput/ It will need libxine headers, but Xine doesn't need to be patched, so any packaged xine-lib 1.1.1 or newer should be fine.
Niko Mikkilä
Check this out: http://users.tkk.fi/~phintuka/vdr/vdr-xineliboutput/ It will need libxine headers, but Xine doesn't need to be patched, so any packaged xine-lib 1.1.1 or newer should be fine.
Niko:
I downloaded vdr-xineliboutput-0.99rc.tgz and uncompressed it to vdr-1.4.0/PLUGINS/src,and patched it with vdr-xineliboutput-0.99rc-vdr-1.4.0.patch.
Initially, this plugin directory name is "xineliboutput-0.99rc", but when I try to "make plugins", it just ignored this plugin directory, so I renamed it to "xineliboutput", now it can compile the plugins with the following error:
----------------------- gcc -g -shared xine_input_vdr.o -L/usr/lib -lxine -lz -lnsl -lpthread -lrt -o xineplug_inp_xvdr.so make[1]: *** No rule to make target `xine_post_autoscale.c', needed by `xine_post_autoscale.o'. Stop. make[1]: Leaving directory `/home/zhuhx/VDR/myvdr/vdr-1.4.0/PLUGINS/src/xineliboutput' *** failed plugins: xineliboutput [zhuhx@pc1 vdr-1.4.0]$ -----------------------
I checked this plugins's directory, there is no such file "xine_post_autoscale.c"and "xine_post_headphone.c". Where it should be?
previously I downloaded xine-lib-cvs-20060319194500.tar.bz2 xine-ui-cvs-20060319194500.tar.bz2 and patched xine-lib with xine-0.7.9/xine-lib.patch and compiled/installed them in /usr/local/xine/
Please help ! Thanks, Paul ZHU
On Thu, 04 May 2006 10:58:05 +0800 Paul ZHU zhu.blue@gmail.com wrote:
Check this out: http://users.tkk.fi/~phintuka/vdr/vdr-xineliboutput/ It will need libxine headers, but Xine doesn't need to be patched, so any packaged xine-lib 1.1.1 or newer should be fine.
Niko:
I downloaded vdr-xineliboutput-0.99rc.tgz and uncompressed it to vdr-1.4.0/PLUGINS/src,and patched it with vdr-xineliboutput-0.99rc-vdr-1.4.0.patch.
Initially, this plugin directory name is "xineliboutput-0.99rc", but when I try to "make plugins", it just ignored this plugin directory, so I renamed it to "xineliboutput", now it can compile the plugins with the following error:
You could also make a symbolic link so that testing many versions of the same plugin is easier and you know which version you happen to use: ln -s xineliboutput-0.99rc xineliboutput
gcc -g -shared xine_input_vdr.o -L/usr/lib -lxine -lz -lnsl -lpthread -lrt -o xineplug_inp_xvdr.so make[1]: *** No rule to make target `xine_post_autoscale.c', needed by `xine_post_autoscale.o'. Stop. make[1]: Leaving directory `/home/zhuhx/VDR/myvdr/vdr-1.4.0/PLUGINS/src/xineliboutput' *** failed plugins: xineliboutput [zhuhx@pc1 vdr-1.4.0]$
I checked this plugins's directory, there is no such file "xine_post_autoscale.c"and "xine_post_headphone.c". Where it should be?
This just came up on a Finnish VDR forum and Rolf Ahrenberg told that you'll need to comment out "ENABLE_TEST_POSTPLUGINS = 1" from the plugin's Makefile. It gets enabled by vdr-xineliboutput-0.99rc-vdr-1.4.0.patch, but apparently it doesn't work yet.
previously I downloaded xine-lib-cvs-20060319194500.tar.bz2 xine-ui-cvs-20060319194500.tar.bz2 and patched xine-lib with xine-0.7.9/xine-lib.patch and compiled/installed them in /usr/local/xine/
Xineliboutput doesn't need that patch, but it shouldn't be a problem either.
Niko
-
Andreas Mueller -
Chris Jones -
Lutz Bender -
Niko Mikkila -
Paul ZHU