Hi,
there is a new version of the pvrinput plugin available: http://home.arcor.de/andreas.regel/files/pvrinput/vdr-pvrinput-0.1.1.tgz
Changes since 0.1.0: - adapted to vdr 1.4.0. Older versions should still work. - fixed detection of PVR card to work with ivtv version 0.4.1 or later with kernel 2.4.
As I recently switched to satellite reception I don't need the PVR card any longer. So don't expect any further development or new releases from me in the future. If anyone wants to continue development, just do it.
Andreas
Hi,
a new version (0.0.15) of the pin plugin available at www.jwendel.de
General: The pin-plugin is a kind of configurable child protection for channels, broadcasts, recordings and scripts.
From the version history:
* #15 30.04.06, added: french translations (thanks to Pat!) * changed: Makefile due to VDR's new APIVERSION feature * added: Patch for vdr 1.4.0 * #14 08.04.06, added: protection feature for scripting * #13 26.03.06, bugfix: autoProtectionMode now respect start time * of event (needed since channels not * protected every time) * #12 20.03.06, change: now using aux field in timer config * bugfix: autoProtectionMode will now restored from config * (Bug reported by rookie1, thanks!) * bugfix: autoProtectionMode now working even with vdr 1.3.44 * (Bug reported by rookie1, thanks!)
Jörg
Griasde Jörg,
I've tried to use your new version with 1.4.0.
So, what I've done? Let me explain ...
I'm testing your latest pin-plugin from http://www.jwendel.de/vdr/vdr-pin-0.0.15.tgz with a plain vanilla-vdr 1.4.0
I've patched the vdr with the patch, delivered with your plugin "vdr-1.4.0-plain.diff".
Locking a channel is no problem, but if I try to lock a recording, nothing will happens. Syslog said: Apr 30 23:55:58 tecvdr vdr: [7638] executing command '/usr/bin/fskprotect.sh protect "/video/Clips/Tito_&_Tarantula_-_After_Dark/2005-02-04.22.50.99.99.rec"' But wether I activate the pin-protection or not, I can start the recording as well. :(
This few lines in /var/log/messages makes me "stutzig":
Apr 30 23:51:06 tecvdr vdr: [7656] PIN plugin receiver thread started (pid=7656) Apr 30 23:51:06 tecvdr vdr: [7656] Receiving message failed, errno 13 Apr 30 23:51:06 tecvdr last message repeated 10 times
If I deavtivate the pin-plugin, this errormessage won't be seen, so I assume that this line have someting to do with the pin-plugin.
But why won't it work right? What happend wrong? Do you have an idea?
Pfiade, BC
On Montag 01 Mai 2006 00:08, Michael Nausch wrote:
Griasde Jörg,
I've tried to use your new version with 1.4.0.
So, what I've done? Let me explain ...
I'm testing your latest pin-plugin from http://www.jwendel.de/vdr/vdr-pin-0.0.15.tgz with a plain vanilla-vdr 1.4.0
I've patched the vdr with the patch, delivered with your plugin "vdr-1.4.0-plain.diff".
Locking a channel is no problem, but if I try to lock a recording, nothing will happens. Syslog said: Apr 30 23:55:58 tecvdr vdr: [7638] executing command '/usr/bin/fskprotect.sh protect "/video/Clips/Tito_&_Tarantula_-_After_Dark/2005-02-04.22.50.99.99.rec"' But wether I activate the pin-protection or not, I can start the recording as well. :(
please can you check if the file "/video/Clips/Tito_&_Tarantula_-_After_Dark/2005-02-04.22.50.99.99.rec/protection.fsk" was created by the script. Does you have changed the script "/usr/bin/fskprotect.sh" to the new one?
This few lines in /var/log/messages makes me "stutzig":
Apr 30 23:51:06 tecvdr vdr: [7656] PIN plugin receiver thread started (pid=7656) Apr 30 23:51:06 tecvdr vdr: [7656] Receiving message failed, errno 13 Apr 30 23:51:06 tecvdr last message repeated 10 times
If I deavtivate the pin-plugin, this errormessage won't be seen, so I assume that this line have someting to do with the pin-plugin.
errno 13 looks like "Permission denied", is it possible, that you have started the vdr first as 'one' user (e.g. root) and than as an 'other' user? Than it is possible (when the vdr was not ended the normal way) that the system message queue used by the plugin is left over from the first session. In this case you can remove it using the ipcrm command (as the user who owns the queue).
What says "ipcs -q", when vdr (with the plugin) is running, can you post the output please?
To make shure that i have interpreted errno 13 correctly i have posted a version 0.0.15a with an extended error message.
Tanks for testing ;) Jörg
But why won't it work right? What happend wrong? Do you have an idea?
Pfiade, BC
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
HI,
Am Montag, 1. Mai 2006 07:53 schrieb Jörg Wendel:
please can you check if the file
and
What says "ipcs -q", when vdr (with the plugin) is running, can you post the output please?
To make shure that i have interpreted errno 13 correctly i have posted a version 0.0.15a with an extended error message.
Tanks for testing ;)
O.K. I'll do taht, but first I must drive to the hospital ... :(
cul8r!
BC
Griasdebou!
O.K. I'm back from hospital an will play and search, what happens ...
Am Montag, 1. Mai 2006 07:53 schrieb Jörg Wendel:
please can you check if the file "/video/Clips/Tito_&_Tarantula_-_After_Dark/2005-02-04.22.50.99.99.rec/prot ection.fsk" was created by the script.
No, there's no protection.fsk in the subdirectory.
Does you have changed the script "/usr/bin/fskprotect.sh" to the new one?
Jepp, I've made some symlinks to use the right new scripts: tecvdr:/usr/bin # ls -al fs* lrwxrwxrwx 1 root root 43 Apr 30 22:54 fskcheck -> /usr/local/src/VDR/PLUGINS/src/pin/fskcheck lrwxrwxrwx 1 root root 59 Apr 30 22:53 fskcheck-demo.sh -> /usr/local/src/VDR/PLUGINS/src/pin/scripts/fskcheck-demo.sh lrwxrwxrwx 1 root root 56 Apr 30 22:53 fskprotect.sh -> /usr/local/src/VDR/PLUGINS/src/pin/scripts/fskprotect.sh
fsprotect.sh contains: tecvdr:/usr/bin # cat fskprotect.sh
fskcheck check
if [ $? != 1 ]; then fskcheck info "Please enable pin protection first" exit 1 fi
if [ "$1" == "protect" ]; then
if [ -f $2/protection.fsk ]; then fskcheck info "Recording was already protected!" exit 1 fi
touch $2/protection.fsk fskcheck info "Recording now protected!"
fi
if [ "$1" == "unprotect" ]; then
if [ ! -f $2/protection.fsk ]; then echo fskcheck info "Recording was not protected!" exit 1 fi
rm -f $2/protection.fsk fskcheck info "Removed protection of recording!"
fi
exit 0
errno 13 looks like "Permission denied", is it possible, that you have started the vdr first as 'one' user (e.g. root) and than as an 'other' user?
Hmmm, I'm using my own old startupscript:
DVBDIR="/usr/local/src/DVB/driver" DVBREM="/usr/local/src/DVB/apps/av7110_loadkeys" VDRPRG="/usr/local/src/VDR/vdr" PLUGIN="/usr/local/src/VDR/PLUGINS/lib/libvdr" VDRCMD="$VDRPRG -c /etc/vdr -g /video -s /usr/local/bin/vdrshutdown -L /usr/local/src/VDR/PLUGINS/lib $*" VDRUSR=vdr
# DVD Dma Mode: # [ -e /dev/dvd ] && (/sbin/hdparm -u1 /dev/cdrom; /sbin/hdparm -X34 /dev/dvd) /sbin/hdparm -u1 -d1 -X udma2 /dev/hdc #/sbin/hdparm -u0 -d1 /dev/hdc
VDRCOMMAND="$VDRCMD \ -D 1 \ `[ -x $PLUGIN-pin* ] && echo "-P pin"`\ `[ -x $PLUGIN-femon.* ] && echo "-P femon"`\ `[ -x $PLUGIN-burn.* ] && echo "-P 'burn -i /video'"`\ `[ -x $PLUGIN-remote* ] && echo "-P 'remote -i /dev/input/event0'"`\ -w 60"
LSMOD="`/sbin/lsmod | grep -w '^dvb' | wc -l`" KILL="/usr/bin/killall -q -TERM"
# Load driver if it hasn't been loaded already: if [ $LSMOD -eq 0 ] ; then (cd $DVBDIR; make insmod) fi
while (true) do # next line is _not_ required if autodetect mode is used $DVBREM/av7110_loadkeys $DVBREM/tecvdr.rc5 > /proc/av7110_ir su $VDRUSR -c "$VDRCOMMAND" if test $? -eq 0 -o $? -eq 2; then exit; fi date echo "restarting VDR" $KILL $VDRPRG sleep 10 (cd $DVBDIR; make rmmod; make insmod) date done
While vdr is running, top shows me: top: top - 12:44:46 up 10 min, 2 users, load average: 1.69, 1.23, 0.63 Tasks: 73 total, 2 running, 71 sleeping, 0 stopped, 0 zombie Cpu(s): 86.5% user, 13.5% system, 0.0% nice, 0.0% idle Mem: 223292k total, 154928k used, 68364k free, 11304k buffers Swap: 530136k total, 0k used, 530136k free, 64864k cached
USER PID PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND vdr 773 15 0 8692 8692 1824 S 0.0 3.9 0:00.04 vdradmind.pl vdr 1831 18 0 920 920 764 S 0.0 0.4 0:00.02 su vdr 1832 15 0 21560 21m 2760 S 0.0 9.7 0:03.83 vdr vdr 1833 15 0 21560 21m 2760 S 0.0 9.7 0:00.01 vdr vdr 1842 15 0 0 0 0 S 0.0 0.0 0:00.01 kdvb-fe-1:0 vdr 1846 15 0 21560 21m 2760 S 0.0 9.7 0:00.02 vdr vdr 1847 34 19 21560 21m 2760 S 0.0 9.7 0:00.27 vdr vdr 1848 25 0 21560 21m 2760 R 57.8 9.7 2:22.01 vdr vdr 1849 34 19 21560 21m 2760 S 0.0 9.7 0:00.00 vdr vdr 1850 18 0 21560 21m 2760 S 0.0 9.7 0:00.00 vdr
What says "ipcs -q", when vdr (with the plugin) is running, can you post the output please?
ecvdr:/usr/bin # ipcs -q
------ Message Queues -------- key msqid owner perms used-bytes messages 0xd8000000 0 vdr 0 0 0
To make shure that i have interpreted errno 13 correctly i have posted a version 0.0.15a with an extended error message.
O.K. I've build the new 15a version: Plugin pin: make[1]: Entering directory `/usr/local/src/vdr-1.4.0.PIN/PLUGINS/src/pin-0.0.15a' make[1]: Leaving directory `/usr/local/src/vdr-1.4.0.PIN/PLUGINS/src/pin-0.0.15a' make[1]: Entering directory `/usr/local/src/vdr-1.4.0.PIN/PLUGINS/src/pin-0.0.15a' make[2]: Entering directory `/usr/local/src/vdr-1.4.0.PIN/PLUGINS/src/pin-0.0.15a' g++ -O2 -Wall -Woverloaded-virtual -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"pin"' -I../../../include -I../../../../DVB/include fskcheck.c g++ -O2 -Wall -Woverloaded-virtual fskcheck.o -o fskcheck make[2]: Leaving directory `/usr/local/src/vdr-1.4.0.PIN/PLUGINS/src/pin-0.0.15a' make[2]: Entering directory `/usr/local/src/vdr-1.4.0.PIN/PLUGINS/src/pin-0.0.15a' g++ -O2 -Wall -Woverloaded-virtual -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"pin"' -I../../../include -I../../../../DVB/include pin.c g++ -O2 -Wall -Woverloaded-virtual -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"pin"' -I../../../include -I../../../../DVB/include setupmenu.c g++ -O2 -Wall -Woverloaded-virtual -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"pin"' -I../../../include -I../../../../DVB/include menu.c g++ -O2 -Wall -Woverloaded-virtual -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"pin"' -I../../../include -I../../../../DVB/include locks.c g++ -O2 -Wall -Woverloaded-virtual -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"pin"' -I../../../include -I../../../../DVB/include brdclocks.c g++ -O2 -Wall -Woverloaded-virtual -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"pin"' -I../../../include -I../../../../DVB/include brdcmenu.c g++ -O2 -Wall -Woverloaded-virtual -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"pin"' -I../../../include -I../../../../DVB/include i18n.c g++ -O2 -Wall -Woverloaded-virtual -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"pin"' -I../../../include -I../../../../DVB/include rep.c g++ -O2 -Wall -Woverloaded-virtual -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"pin"' -I../../../include -I../../../../DVB/include msgreceiver.c g++ -O2 -Wall -Woverloaded-virtual -shared pin.o setupmenu.o menu.o locks.o brdclocks.o brdcmenu.o i18n.o rep.o msgreceiver.o -o libvdr-pin.so make[2]: Leaving directory `/usr/local/src/vdr-1.4.0.PIN/PLUGINS/src/pin-0.0.15a' make[1]: Leaving directory `/usr/local/src/vdr-1.4.0.PIN/PLUGINS/src/pin-0.0.15a'
I think nothing bad here, isn't ist so?
If I try to protect a recording, now syslog shows:
May 1 12:45:25 tecvdr vdr: [1832] executing command '/usr/bin/fskprotect.sh protect "/video/Willi_wills_wissen/2006-04-04.14.50.99.99.rec"' May 1 12:45:25 tecvdr vdr: [1848] Receiving message failed, errno (13), 'Permission denied'
... and there's no protection.fsk there: ls: drwxr-xr-x 3 vdr vdrdaem 4096 Apr 6 20:31 Willi_wills_wissen drwxr-xr-x 2 vdr vdrdaem 4096 Apr 29 14:08 2006-04-04.14.50.99.99.rec -rw-r--r-- 1 vdr vdrdaem 717096461 Apr 4 21:17 001.vdr -rw-r--r-- 1 vdr vdrdaem 292824 Apr 4 21:17 index.vdr -rw-r--r-- 1 vdr vdrdaem 238 Apr 4 21:16 info.vdr -rw-r--r-- 1 vdr vdrdaem 22 Apr 4 21:17 marks.vdr
Tanks for testing ;)
Null Problemo! ;)
I think, there's a problem with my runvdr, 'cause if I run vdr as user root, there are no errormessages in my syslog!
May 1 13:21:30 tecvdr vdr: [2344] executing command '/usr/bin/fskprotect.sh protect "/video/Willi_wills_wissen/2006-04-04.14.50.99.99.rec"' May 1 13:21:30 tecvdr vdr: [2357] Message (0) from (425985) received [-] May 1 13:21:31 tecvdr vdr: [2357] Message (1) from (458753) received [Recording now protected!] May 1 13:21:31 tecvdr vdr: [2357] Got 'Recording now protected!' May 1 13:21:31 tecvdr vdr: [2344] info: Recording now protected!
May 1 13:22:25 tecvdr vdr: [2344] info: Kinderschutz aktiviert May 1 13:22:34 tecvdr vdr: [2344] checking protection of recording '(null)' May 1 13:22:34 tecvdr vdr: [2344] checking rights, protection file is '/video/Willi_wills_wissen/2006-04-04.14.50.99.99.rec/protection.fsk' May 1 13:22:34 tecvdr vdr: [2344] pin: no translation found for 'Recording protected, enter pin code first' in language 1 (Deutsch) May 1 13:22:34 tecvdr vdr: [2344] ERROR: Recording protected, enter pin code first
Pfiadenachad!
Michael
Hi,
On Montag 01 Mai 2006 13:35, Michael Nausch wrote:
Griasdebou!
O.K. I'm back from hospital an will play and search, what happens ...
Am Montag, 1. Mai 2006 07:53 schrieb Jörg Wendel:
please can you check if the file "/video/Clips/Tito_&_Tarantula_-_After_Dark/2005-02-04.22.50.99.99.rec/pr ot ection.fsk" was created by the script.
No, there's no protection.fsk in the subdirectory.
Does you have changed the script "/usr/bin/fskprotect.sh" to the new one?
Jepp, I've made some symlinks to use the right new scripts: tecvdr:/usr/bin # ls -al fs* lrwxrwxrwx 1 root root 43 Apr 30 22:54 fskcheck -> /usr/local/src/VDR/PLUGINS/src/pin/fskcheck lrwxrwxrwx 1 root root 59 Apr 30 22:53 fskcheck-demo.sh -> /usr/local/src/VDR/PLUGINS/src/pin/scripts/fskcheck-demo.sh lrwxrwxrwx 1 root root 56 Apr 30 22:53 fskprotect.sh -> /usr/local/src/VDR/PLUGINS/src/pin/scripts/fskprotect.sh
fsprotect.sh contains: tecvdr:/usr/bin # cat fskprotect.sh
the links and the script looks good, i think the script exits cause it can't check the protection state of the pin plugin. And the reason for this should be the 'permision denied' problem.
ecvdr:/usr/bin # ipcs -q
------ Message Queues -------- key msqid owner perms used-bytes messages 0xd8000000 0 vdr 0 0 0
Ok, thats it, the perms are 0. Sorry it's my bug, i'am using linvdr where vdr is always running as root. For the root user the perms don't matter.
Pleas apply the attached patch to the plugin. BEFORE starting vdr again make sure no system message queue with the wrong permissions is left. Attention only message queues which key starts with 0xd80000?? are from the pin plugin. Don't delete others of your system ;)
Example:
- first list it: linvdr:/etc/vdr# ipcs -q | grep 0xd80000 0xd8000000 393216 root 666 0 0
- now delete it using the listed key(s) (second column) linvdr:/etc/vdr# ipcrm msg 393216
Greetings Jörg
Griasdebou!
Am Montag, 1. Mai 2006 14:27 schrieb Jörg Wendel:
Ok, thats it, the perms are 0. Sorry it's my bug, i'am using linvdr where vdr is always running as root. For the root user the perms don't matter.
Aha! But you know, every little baby is given with the mother's milk: Don't run a program under the rights of root, if there's no secial necessity! <lol>
Pleas apply the attached patch to the plugin.
I've done this, and now it works a little better, but only a little, cause there's a further problem:
If I try to play a protected recording the following happens: May 1 15:07:45 tecvdr vdr: [768] info: Kinderschutz aktiviert May 1 15:07:55 tecvdr vdr: [768] checking protection of recording '(null)' May 1 15:07:55 tecvdr vdr: [768] checking rights, protection file is '/video/Willi_wills_wissen/2006-04-04.14.50.99.99.rec/protection.fsk' May 1 15:07:55 tecvdr vdr: [768] pin: no translation found for 'Recording protected, enter pin code first' in language 1 (Deutsch) May 1 15:07:55 tecvdr vdr: [768] ERROR: Recording protected, enter pin code first
So far so good! I can play this recording after "opening" the protection with "Gorge Orwells special year-code".
BUT, if I try to protect a recording I've the new old problem: May 1 15:08:45 tecvdr vdr: [768] checking protection of recording 'Clips' May 1 15:08:45 tecvdr vdr: [768] checking rights, protection file is '/video/Clips/protection.fsk' May 1 15:08:51 tecvdr vdr: [768] executing command '/usr/bin/fskprotect.sh protect "/video/Clips/Metallica_-_Hero_of_the_Day/2005-02-02.20.20.99.99.rec"' May 1 15:08:51 tecvdr vdr: [866] Message (0) from (229377) received [-] May 1 15:08:51 tecvdr vdr: [866] Sending message to (229377) failed, errno (13), 'Permission denied' May 1 15:08:51 tecvdr vdr: [866] Message (1) from (262145) received [Please enable pin protection first] May 1 15:08:51 tecvdr vdr: [866] Got 'Please enable pin protection first' May 1 15:08:51 tecvdr vdr: [768] info: Please enable pin protection first
The pin-plugin is active!
tecvdr:~ # ipcs -q
------ Message Queues -------- key msqid owner perms used-bytes messages 0xd8000000 0 vdr 666 0 0
Further I will mak a little wish a improvement-suggestion, if the pin-plugin-menue is displayed on OSD, I'll see: 1 Kanalliste bearbeiten 2 Gesperrte Sendungen bearbeiten 3 Aktuellen Kanal in die Sperrliste aufnehmen 4 Aktuelle Sendung in die Sperrliste aufnehmen 5 Kinderschutz aktivieren
If I try to select menupoint 5 "Kinderschutz aktivieren" an press button 5 nothing happens. I must scroll down and press then the ok-button. Were it possible, to (re)act like VDR in all the other menues?
Have a nice day!
BC
On Montag 01 Mai 2006 15:32, Michael Nausch wrote:
Aha! But you know, every little baby is given with the mother's milk: Don't run a program under the rights of root, if there's no secial necessity! <lol>
You're right, but for my vdr i'am using linvdr with less changes as possible :(
Pleas apply the attached patch to the plugin.
I've done this, and now it works a little better, but only a little, cause there's a further problem:
If I try to play a protected recording the following happens: May 1 15:07:45 tecvdr vdr: [768] info: Kinderschutz aktiviert May 1 15:07:55 tecvdr vdr: [768] checking protection of recording '(null)' May 1 15:07:55 tecvdr vdr: [768] checking rights, protection file is '/video/Willi_wills_wissen/2006-04-04.14.50.99.99.rec/protection.fsk' May 1 15:07:55 tecvdr vdr: [768] pin: no translation found for 'Recording protected, enter pin code first' in language 1 (Deutsch) May 1 15:07:55 tecvdr vdr: [768] ERROR: Recording protected, enter pin code first
Ok, i have now added the missing german translation for 'Recording protected, enter pin code first'.
So far so good! I can play this recording after "opening" the protection with "Gorge Orwells special year-code".
Ok
BUT, if I try to protect a recording I've the new old problem: May 1 15:08:45 tecvdr vdr: [768] checking protection of recording 'Clips' May 1 15:08:45 tecvdr vdr: [768] checking rights, protection file is '/video/Clips/protection.fsk' May 1 15:08:51 tecvdr vdr: [768] executing command '/usr/bin/fskprotect.sh protect "/video/Clips/Metallica_-_Hero_of_the_Day/2005-02-02.20.20.99.99.rec"' May 1 15:08:51 tecvdr vdr: [866] Message (0) from (229377) received [-] May 1 15:08:51 tecvdr vdr: [866] Sending message to (229377) failed, errno (13), 'Permission denied' May 1 15:08:51 tecvdr vdr: [866] Message (1) from (262145) received [Please enable pin protection first] May 1 15:08:51 tecvdr vdr: [866] Got 'Please enable pin protection first' May 1 15:08:51 tecvdr vdr: [768] info: Please enable pin protection first
Hm, this i can't reproduce even if i'am not root. Are the fskcheck tool recompiled after the patch was applied? Was the fskcheck.c changed by the patch? Wat says: #> fskcheck check; echo $? it shoud return 2 when the protection is active and 1 if vdr is currently not protected.
The pin-plugin is active!
tecvdr:~ # ipcs -q
------ Message Queues -------- key msqid owner perms used-bytes messages 0xd8000000 0 vdr 666 0 0
looks good!
If I try to select menupoint 5 "Kinderschutz aktivieren" an press button 5 nothing happens. I must scroll down and press then the ok-button. Were it possible, to (re)act like VDR in all the other menues?
Done.
I release the 2 changes when we have solved the pending problem.
Many thanks for beta testing ;) Greets Jörg
HI Jörg!
Am Montag, 1. Mai 2006 19:42 schrieb Jörg Wendel:
Pleas apply the attached patch to the plugin.
I've done this, ...
But I did'nt it not right, so I think! I've patch the two files fskcheck.c and msgreceiver.c by hand, and what happens. IT WORKS!!!
Hm, this i can't reproduce even if i'am not root.
Forget it! Something went wrong while I've patched the pin-plugin via "cat pin-0.0.15-perm-bug.diff | patch".
I release the 2 changes when we have solved the pending problem.
O.K, I've no more problem! ;) So there isn't a rock on your way to solve my little wishes. ;)
Many thanks for beta testing ;)
No problem, I think this is one of VDRs VIP (Very Importandt Plugins), one new feature for next development-release! <bg>
So, now, I can work with the next plugins ...
Have a nice day! Django
Hi,
O.K, I've no more problem! ;) So there isn't a rock on your way to solve my little wishes. ;)
Version 0.0.16 including the bugfix and the little changes from above is available at www.jwendel.de
A new version with a feature to protect plugins is in work now. For example the dvd plugin can protected so the children can't look dvd's.
Django
Hatte ich doch richtig geraten, aber wer sollte es bei "Griasdebou" sonst sein :))
Grüße Horchi
Hi,
a new version (0.0.3) of the ipod plugin is available at www.jwendel.de
General: The ipod plugin shows titel / gernre / artists / etc. of the ITunesDB on a mounted ipod. The osd structure is most familiar of the ipod's menu. For play back the mp3 plugin is used, therefor you need this plugin too.
Changes: - only the Makefile was changed due to the APIVERSION feature
Greetings Jörg Wendel
On Sunday 30 April 2006 18:15, Andreas Regel wrote:
Hi,
there is a new version of the pvrinput plugin available: http://home.arcor.de/andreas.regel/files/pvrinput/vdr-pvrinput-0.1.1.tgz
Changes since 0.1.0:
- adapted to vdr 1.4.0. Older versions should still work.
- fixed detection of PVR card to work with ivtv version 0.4.1 or later
with kernel 2.4.
As I recently switched to satellite reception I don't need the PVR card any longer. So don't expect any further development or new releases from me in the future. If anyone wants to continue development, just do it.
There is a minor problem which at least occurs on gentoo: The Plugin needs to be compiled with the attached patch which changes the include order of the files videodev.h and videodev2.h
This will prevent the usage of the file videodev2.h (which is in my case too old for the plugin to compile) located under /usr/include/linux/...
Matthias