Hi All!
Sorry my English.
Probably many already faced a problem of simultaneous display of various
international letters in vdr.
For example it is impossible to use simultaneously both Russian and
German letters.
I recently have put myself vdr and it at once was not pleasant to me.
So i have changed all this.
As all fonts of the different sizes and styles was necessary at the same
time and freetype2 library to vdr to fasten.
These Patchs are made for vdr version 1.3.24
one with vanilla vdr-…
[View More]1.3.24 and with enAIO vdr-1.3.24.
Please set locale for correct work at UTF8.
to enAIO users: Please test enAIO functionality with this patch.
I also have a little improved Easyinput patch. Now for each language
there is a character set.
Please change these character sets for your language in file i18n.c .
In setup.conf added some parameters for definition of fonts.
For example:
FontFix = courbd.ttf
FontFixSize = 16
FontOsd = arialbd.ttf
FontOsdSize = 16
FontSml = verdana.ttf
FontSmlSize = 12
By default fonts are
as FontOsd arialbd.ttf size 16,
FontSml arial.ttf size 12
und FontFix courbd.ttf size 15
These files at least for the first start should lay in config directories.
For each channel in channels.conf it is possible to establish the
character coding, the field is added in the end every line.
For example:
Das
Erste;ARD:198500000:I0C34D12M16B7T8G4Y0:T:27500:101:102=deu:104:0:1:8468:9985:0:ISO8859-15
By default is ISO8859-15.
Possible variants are listed in: iconv --list
EPG data at reception are converted in UTF-8. So on a disk all (again
created) files and descriptions will be already in UTF-8. I recommend
to remove a file epg.data that data were already normally filled in
UTF8.
You should also convert names of channels in channels.conf in UTF-8.
Pleasant viewings!!!
Changelog:
o You can use fixed size fonts. All freetype2 supported fonts.
o Small bug fixes.
o version with enAIO patch is also providet.
o some cosmetic changes
--
Alexander Riedel
[View Less]
Hi,
I'm facing the problem that every time I'm on some plugin's screen in
VDR (for example, the burn plugin, which has "Commands" mapped on the
red remote control button), if I'm pressing the red button on my remote,
instead of doing what the red button should do in that specific plugin,
VDR always pauses live video. The other coloured buttons seem to work
(for example when showing recording details, now/next in the schedule
menu, or such things). This happens regardless of the VDR …
[View More]version (now
I'm using 1.3.24).
VDR learned my remote control's keys (LIRC) once, although it keeps
asking me to learn them at every start, and after waiting those few
seconds it asks for the KBD keys (I'd love to have some keys learned
from the IR, but PS/2-attached keyboard+trackball of my htpc, but it
never recognizes a keyboard key, maybe somone can give ahint on this
one, too), and after VDR finally starts, I can use my LIRC remote
control normally (well, if this red button issue wouldn't be).
Maybe it's worth mentioning that I have a single budget card setup,
therefore I do the decoding with softdevice/DirectFB, or xine/df_xine,
but this behaviour is all the same.
Any clues where to look for what I'm doing wrong?
Lucian.
P.S. I'd like to sort this kind of things out, to be able to use cutting
of the recordings and archiving with the burn plugin, all from the LIRC
remote (or even from the IR keyboard).
[View Less]
Hello everybody.
I had a problem with burning dvd's from my recordings on my
system. The system is a FC3 based, and VDR and DVB packages are
installed from cachalot repository.
Some version information of conversion software:
mjpegtools-1.6.3-0.lvn.0.1.rc1
y4mscaler-0.6.2-0.lvn.1
ImageMagick-6.2.2.0-2.fc3
vdr-burn-0.0.6g-0.6.pre3
The problem occured when the burn script started making menu,
failing the mpeg2enc-command.
I managed to burn DVD's changin one (actually two lines) line
in the …
[View More]script. Here is the patch:
--- /usr/lib/vdr/bin/vdrburn.sh.orig 2005-06-13 22:54:02.000000000 +0300
+++ /usr/lib/vdr/bin/vdrburn.sh 2005-06-13 22:54:38.000000000 +0300
@@ -85,14 +85,14 @@
MKMENU)
if [ "$USE_TCMPLEX" == "yes" ]; then
convert "$2/menu-bg-$3.png" pnm:- |
- ppmtoy4m -n 1 -F25:1 -A 59:54 -I t -L -r -v 0 |
+ ppmtoy4m -n 1 -F25:1 -A 59:54 -I t -L -r -v 0 -S 420mpeg2 |
y4mscaler -O chromass=420_MPEG2 |
mpeg2enc -q 2 -a 2 -n p -f 8 -v 0 -o "$2/menu-bg-$3.m2v" &&
$TCMPLEX -i "$2/menu-bg-$3.m2v" -p
"$4/menu-silence.mp2" -m d -o /dev/stdout |
spumux -v 2 "$2/menu-$3.xml" > "$2/menu-bg-$3.mpg"
else
convert "$2/menu-bg-$3.png" pnm:- |
- ppmtoy4m -n 1 -F25:1 -A 59:54 -I t -L -r -v 0 |
+ ppmtoy4m -n 1 -F25:1 -A 59:54 -I t -L -r -v 0 -S 420mpeg2 |
y4mscaler -O chromass=420_MPEG2 |
mpeg2enc -q 2 -a 2 -n p -f 8 -v 0 -o "$2/menu-bg-$3.m2v" &&
mplex -f 8 -vbr -v 1 -o /dev/stdout "$2/menu-bg-$3.m2v"
"$4/menu-silence.mp2" |
Hope this helps.
Cheers,
Jani Frilander
[View Less]
This is the 'official' vdr-mailing-list-etiquette-reminder.
Please take this as a serious advise. The VDR mailinglist is
getting quite large and it shouldn't become a pain in the ass to follow.
Take the time to read it, especially if you are new to mailinglists in
general.
E-mail formatting
=================
Mailing list email should fit the following criteria:
DO
--
* Trim quoted material to the minimum needed to clarify what you're
talking about.
* Add a blank line _before_ and _after_ …
[View More]each quote for better
readability.
* Make sure you are attributing material to the correct person
(i.e. make sure the "On 19/07/2002, Joe Bloggs said:" is correct)
* Write your responses _after_ the quoted text, not before. If your
mail client makes it difficult to do this, get a new one.
* Make sure lines are wrapped at maximum 76 characters (to fit an 80
character wide screen), even if the text had been quotet several
times.
* Use ">" at start of line to mark quoted text.
* Set your mail client to "english headers" to avoid subjects like:
"AW: Antwort: Re: AW: AW: AW: Re: Some Topic allready trunkated"
If you see one, don't just add another "Re:" but remove
all "AW:" and other chained "Re:".
* Use a descriptive subject! A message titled "A small wish"
doesn't tell what it is about. Better use something like
"should do xyz" or "crashes when doing xyz".
* Always write one separate message per topic. some people (especially
those who matter) might not read mixed-up and lengthy threads.
* Start a new thread when posting a new subject.
* Make emails as short as possible whilst keeping them comprehensible.
Don't
-----
* Don't post in either HTML-only or in Text and HTML. If your mail
client doesn't support this, change it.
* Don't top post.
* Don't give a one line answer having quoted the whole post.
* Don't use a too long signature.
* Don't reply where you should have started a new thread.
* Don't break threads by sending a new mail, where you should have
replied.
* Don't test post. Send your test posts to "echo(a)fu-berlin.de" or
similar reply machines.
* Don't use lengthly disclaimers. If not possible, use a freemail
account.
* Don't quote disclaimers and other footers.
General Etiquette
=================
This can really be summed up in one phrase - 'be polite'.
Allways use your 'Real Name' when posting to mailinglists or newsgroups.
If you think something is off-topic, don't reply to the list although
you may want to send a short and *polite* note to the person privately
telling them which list would be more appropriate; don't just say -
"that is OT here".
Before asking a question, please Have a look at the mailing list
archives at http://www.linuxtv.org/pipermail/vdr/
If someone flames or trolls the list, don't reply - it wastes everyones
bandwidth and time.
Don't reply to spam which gets through to the list - just ignore it when
it does.
Resources
=========
* The ultimate guide to most matters to do with email etiquette is
RFC-2822 which can be found at:
ftp://ftp.isi.edu/in-notes/rfc2822.txt
* A german site set up by some usenet-people, who take it even more
serious with netiquette.
http://learn.to/quote
[View Less]
Hello,
there is a new version of the pvrinput plugin available:
http://home.arcor.de/andreas.regel/files/vdr-pvrinput-0.0.2.tgz
Changes since 0.0.1:
- The tuner input is now auto-detected (I hope this works for non
PVR-250 cards).
- Added support for other inputs than the tuner, using the "C" parameter
of the channel entry. I did not test this here, it should work.
- Fixed VIDIOC_G_FMT ioctl.
- Added support for the video norms NTSC, SECAM and PAL, using the "I"
parameter of the …
[View More]channel entry.
- Added support for radio channels, the video PID must be set to zero.
I can't test this here, I hope it works.
- Added setup menu for setting up encoding parameters.
- Added videodev2.h file from the ivtv driver archive.
Andreas
[View Less]
Hello,
I have some problems with creating ISO-images and burnig to DVD:
mkisofs stops with the following message:
STAT: fixed 1 VOBUS
++ started: sh -c 'vdrburn.sh MKISO_BURN '/data/video0/.vdr-burn.FEDTMs' '/dev/dvd' '/mnt/hda5/iso' 'National Geographic ' '/data/video0/.vdr-burn.FEDTMs/fifo''
root: <MKISO_BURN /data/video0/.vdr-burn.FEDTMs /dev/dvd /mnt/hda5/iso National Geographic /data/video0/.vdr-burn.FEDTMs/fifo>
root: Starting <nice -n 19 growisofs -use-the-force-luke=tty …
[View More]-dvd-compat -Z /dev/dvd=/data/video0/.vdr-burn.FEDTMs/fifo>
mkisofs: Unable to make a DVD-Video image.
But there is a file in the folder /mnt/hda5/iso with a length of 0.
When I try without creating an iso file before burning:
++ started: sh -c 'vdrburn.sh BURN '/data/video0/.vdr-burn.F76WkU' '/dev/dvd' 'National Geographic ''
root: <BURN /data/video0/.vdr-burn.F76WkU /dev/dvd National Geographic >
root: Starting <nice -n 19 growisofs -use-the-force-luke=tty -dvd-compat -Z /dev/dvd -V National Geographic -dvd-video /data/video0/.vdr-burn.F76WkU/DVDAUTHOR>
Executing 'mkisofs -V National Geographic -dvd-video /data/video0/.vdr-burn.F76WkU/DVDAUTHOR | builtin_dd of=/dev/dvd obs=32k seek=0'
mkisofs: Unable to make a DVD-Video image.
:-( write failed: Input/output error
++ executing: sh -c 'eject /dev/dvd'
after some time the DVD-tray moves in and the same repeats endless.
Plugin version is burn-0.0.6f with the newest version of vdrsync
(http://vdrsync.vdr-portal.de/releases/vdrsync-050322.tgz), vdr-1.3.24,
all included in the mld 0.3.0-Distribution.
My system is setup on VFAT partitions, it is possible that mkisofs has problems
writing on VFAT (maybe it is formatted with an unusual big sectorsize)?
Jörg.
[View Less]
Hello.
I'm trying to get nvram-wakeup working. My motherboard is supported with
the latest CVS
nvram-wakeup: Following DMI entries found:
nvram-wakeup: - Mainboard vendor: "SHUTTLE INC"
nvram-wakeup: - Mainboard type: "FX43"
nvram-wakeup: - Mainboard revision: ""
nvram-wakeup: - BIOS vendor: "Phoenix Technologies, LTD"
nvram-wakeup: - BIOS version: "6.00 PG"
nvram-wakeup: - BIOS release: "12/30/2003"
nvram-wakeup: Using infowriter "shuttle_sk43g" (automatically …
[View More]detected)
nvram-wakeup: Using following bios info:
but the clock seems to be set to hour (0xFF) and can't be set from
nvram-wakeup :
[root@media nvram-wakeup]# nvram-wakeup --directisa
<snip>
nvram-wakeup: Opening /dev/rtc in O_RDONLY mode...
nvram-wakeup: Hardware clock: 2005-06-10 14:19:05
nvram-wakeup: rtc.tm_isdst : 1
nvram-wakeup: rtc.tm_gmtoff: 3600
nvram-wakeup: diff : 3600
nvram-wakeup: RTC is running in UTC/GMT!
nvram-wakeup: Test (this should be the current time of the hardware clock):
Fri Jun 10 14:19:05 2005
<snip>
nvram-wakeup: value of the addr_stat byte is: 0x9F.
nvram-wakeup: value of the addr_day byte is: 0xFF.
nvram-wakeup: value of the addr_hour byte is: 0xFF.
nvram-wakeup: value of the addr_min byte is: 0xFF.
nvram-wakeup: value of the addr_sec byte is: 0xFF.
nvram-wakeup: value of the addr_chk_h byte is: 0x1A.
nvram-wakeup: value of the addr_chk_l byte is: 0x74.
nvram-wakeup: Checksum is: 0x1A74.
nvram-wakeup: WakeUp Hour value (31) not correct.
[root@media nvram-wakeup]# nvram-wakeup --directisa -s $((`date +%s` + 20 *
60))
nvram-wakeup: WakeUp Hour value (31) not correct.
Any ideas?
[View Less]
----- original Nachricht --------
Betreff: Re: [vdr] Request: Change Dolby Digital handling
Gesendet: Fr 10 Jun 2005 17:21:03 CEST
Von: "Sergei Haller"<Sergei.Haller(a)math.uni-giessen.de>
> On Fri, 10 Jun 2005, Anssi Hannula (AH) wrote:
>
> AH>
> AH> I would also like to be able to record DD streams. But if I enable the
> AH> useDolbyDigital, the VDR might try to use DD for playing also and I do
> not
> AH> have the DD equipment. Yes, I could change …
[View More]the audio stream with the
> audio
> AH> button, but I don't like that I would have to change audio of every
> channel.
>
> you don't have to do that. Once you choose to a non-DD audio stream, VDR
> remembers that setting for all channels. and will not automatically select
> DD. (except you have a channel, which has _only_ DD)
>
> Oh, and don't forget that you can select preferred tracks in the setup
> menu.
>
> AH> Also, when the DVD plugin implements correct "useDolbyDigital" usage
> AH> (correct me if I'm wrong, but that means to offer the audio tracks in
> the
> AH> VDR Audio menu), I would have to switch every DVD to non-DD track also.
>
> same as VDR: the last choosen track should be remembered globally.
Unfortunely not.
I have bad experience with the dvd-plugin. The last 3..4 vdr versions seemed to have small differences that broke the audio.
Id seemed also to be quite driver dependend.
So in total, not usable for beginners ;-)
> AH> I'd like a separate option for playing and recording.
>
> since this question seems to be asked _very_frequently_, maybe having two
> separete options:
>
> "Record DD" and "Offer DD in the Audio Menu"
>
> would make it more clear to the user and stop this questions. ;-)
>
> Klaus?
Then please remember the question if this should not be rather a timer option.
There are only a few (<10) channels with DD. >95% of their program is 2.0.
So there is no reason to record DD always.
It may also being a good oportunity to implement selectively record alternative language tracks (e.g. ARTE) only on request in the timer.
regard Peter
P.S. Ok DD is only 384kb/s in a total 1,5..5Mb stream, so space saving is minimal.
[View Less]
Hello
Yesterday i set EGP timeout to 1 in the hope the LNBsharing
patch will prevent the usual deadlocks. It does not
need to do anything.
It happens too that the box ran that hour without any recordings
instead of being powered off as usual, so EPG scan could really start.
(Hm, why 1h as minimum?)
As you may se below,
"Starting EPG scan" starts at channel 0 (zero? What is channel 0?),
switches to channel 1, that's Ok...
got new transponders/programs, that's OK. (so many new to day?)
…
[View More]then VDR switches to channel 279!
Why 279 and not 2? What's that?
The next timer event would be a timer to record channel 27 at 10:52
but the switch attempt occurs at 10:42:18
and obviuosly leads VDR into a deep endless loop.
channel 279 is
OLD GOLD;PREMIERE:11720:hC34:S19.2E:27500:0:336=deu:0:1801,1722,1702:167:133:3:0
Never ever tuned to 279 (encrypted) channel, no timer except
the one in approx 10 minutes at channel 27 ( an ASCII buffer Bug? *27*9?)
09:09:08 [8593]: info: Channel locked by LNB!
09:09:58 [8600]: changing name of channel 312 from 'D 4 - 07:45,;' to 'D 4 - 09:30,;'
09:09:58 [8600]: linking channel 118 from 305 308 304 415 310 313 312 311 309 to 305 308 304 415 310 313 311 312 309
...
09:40:48 [8593]: Power button pressed
09:40:48 [8593]: next timer event at Mon Jun 6 10:52:00 2005
09:40:48 [8593]: confirm: Press any key to cancel shutdown
09:40:54 [8593]: confirmed
...
10:00:57 [8593]: next timer event at Mon Jun 6 10:52:00 2005
...
10:40:37 [8597]: changing pids of channel 160 from 901+901:902:204 to 701+701:702:204
10:41:34 [8593]: info: Starting EPG scan
10:41:36 [8593]: switching to channel 0
10:41:36 [22711]: TS buffer on device 1 thread ended (pid=22711, tid=2752525)
10:41:36 [22710]: buffer stats: 4136 (0%) used
10:41:36 [22710]: receiver on device 1 thread ended (pid=22710, tid=2736140)
10:41:36 [8593]: buffer stats: 0 (0%) used
10:41:37 [8603]: changing pids of channel 636 from 0+0:0:0 to 32+32:33:0
10:41:37 [8603]: changing pids of channel 637 from 0+0:0:0 to 70+70:71:54
10:41:38 [8603]: changing pids of channel 638 from 0+0:0:0 to 0+0:73:0
10:41:38 [8603]: changing pids of channel 639 from 0+0:0:0 to 61+61:62:0
10:41:41 [8603]: changing pids of channel 646 from 0+0:0:0 to 41+41:40:0
10:41:42 [8603]: changing pids of channel 647 from 0+0:0:0 to 0+0:58=eng:0
10:41:42 [8603]: changing pids of channel 648 from 0+0:0:0 to 0+0:59:0
10:42:00 [8600]: creating new channel 'TVP Kultura,;TVP' on S19.2E transponder 110861 with id 1-1059-7101-0
10:42:00 [8600]: creating new channel 'TV Polonia,;TVP Service' on S19.2E transponder 110861 with id 1-1059-7100-0
10:42:00 [8600]: changing pids of channel 814 from 0+0:0:0 to 516+8190:690=pol:580
10:42:00 [8600]: changing pids of channel 815 from 0+0:0:0 to 514+8190:670=pol:578
10:42:02 [8603]: creating new channel 'Cartoon Network/TCM,Cartoon Network/TCM;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20341-0
10:42:02 [8603]: creating new channel 'Boomerang,Boomerang;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20343-0
10:42:02 [8603]: creating new channel 'Viasat Explorer,Viasat Explorer;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20344-0
10:42:02 [8603]: creating new channel 'Viasat History,Viasat History;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20345-0
10:42:02 [8603]: creating new channel 'AXN,AXN;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20346-0
10:42:02 [8603]: creating new channel 'Cinemax,Cinemax;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20347-0
10:42:02 [8603]: creating new channel 'Minimax/A+,Minimax/A+;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20348-0
10:42:02 [8603]: creating new channel 'CT1,CT1;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20342-0
10:42:02 [8603]: creating new channel 'CT2,CT2;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20350-0
10:42:02 [8603]: creating new channel 'Film+,Film+;UPC Direct' on S19.2E transponder 110920 with id 1-1063-20349-0
10:42:02 [8603]: changing pids of channel 818 from 0+0:0:0 to 251+251:260=hun,261=cze:270
10:42:02 [8603]: changing caids of channel 818 from 0 to D02
10:42:02 [8603]: changing pids of channel 819 from 0+0:0:0 to 301+301:310=hun,311=cze:320
10:42:02 [8603]: changing caids of channel 819 from 0 to D02
10:42:02 [8603]: changing pids of channel 820 from 0+0:0:0 to 351+351:360=hun,361=cze,362=eng:370
10:42:02 [8603]: changing caids of channel 820 from 0 to D02
10:42:03 [8603]: changing pids of channel 821 from 0+0:0:0 to 401+401:410=hun,411=cze,412=eng:0
10:42:03 [8603]: changing caids of channel 821 from 0 to D02
10:42:03 [8603]: changing caids of channel 821 from 0 to D02
10:42:03 [8603]: changing pids of channel 822 from 0+0:0:0 to 451+451:460=hun:0
10:42:03 [8603]: changing caids of channel 822 from 0 to D02
10:42:03 [8603]: changing pids of channel 825 from 0+0:0:0 to 501+501:511=cze:0
10:42:03 [8603]: changing caids of channel 825 from 0 to D02
10:42:03 [8603]: changing pids of channel 824 from 0+0:0:0 to 551+551:561=cze:570
10:42:03 [8603]: changing caids of channel 824 from 0 to D02
10:42:04 [8603]: changing pids of channel 816 from 0+0:0:0 to 101+101:110=hun,112=eng:120
10:42:04 [8603]: changing caids of channel 816 from 0 to D02
10:42:04 [8603]: changing pids of channel 823 from 0+0:0:0 to 151+151:161=cze:170
10:42:04 [8603]: changing caids of channel 823 from 0 to D02
10:42:04 [8603]: changing pids of channel 817 from 0+0:0:0 to 201+201:210=hun,212=eng,213=pol:0
10:42:04 [8603]: changing caids of channel 817 from 0 to D02
10:42:18 [8593]: switching to channel 279
10:42:18 [8593]: info: Channel not available!
10:42:20 [8593]: switching to channel 279
10:44:20 [8593]: info: Channel not available!
10:44:22 [8593]: switching to channel 279
10:44:22 [8593]: info: Channel not available!
10:44:24 [8593]: switching to channel 279
10:44:24 [8593]: info: Channel not available!
10:44:26 [8593]: switching to channel 279
10:44:26 [8593]: info: Channel not available!
10:44:28 [8593]: switching to channel 279
10:44:28 [8593]: info: Channel not available!
10:44:30 [8593]: switching to channel 279
10:44:30 [8593]: info: Channel not available!
10:44:32 [8593]: switching to channel 279
10:44:32 [8593]: info: Channel not available!
10:44:34 [8593]: switching to channel 279
10:51:56 [8593]: switching to channel 279
10:51:56 [8593]: info: Channel not available!
10:51:58 [8593]: switching to channel 279
10:51:58 [8593]: info: Channel not available!
10:52:00 [8593]: switching to channel 279
10:52:00 [8593]: info: Channel not available!
10:52:02 [8593]: switching to channel 279
10:52:02 [8593]: info: Channel not available!
10:52:04 [8593]: switching to channel 279
10:52:04 [8593]: info: Channel not available!
10:52:06 [8593]: switching to channel 279
10:52:06 [8593]: info: Channel not available!
10:52:08 [8593]: switching to channel 279
10:52:08 [8593]: info: Channel not available!
msi:~# ps fax | grep vdr
29410 pts/1 S+ 0:00 \_ grep vdr
8593 ? S 5:46 ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/
8595 ? S 0:00 \_ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/
8596 ? S 0:00 \_ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/
8597 ? RN 34:45 \_ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/
8599 ? S 0:00 \_ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/
8600 ? SN 30:26 \_ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/
8602 ? S 0:00 \_ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/
8603 ? SN 31:34 \_ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/
8605 ? S 0:00 \_ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/
8606 ? SN 9:03 \_ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/
8607 ? S 0:00 \_ ./vdr -v /video0 -P osdteletext -P femon -l 3 -w 60 -s /video0/pwroff /root/video/VDR/
msi:~# kill 8593
msi:~# kill 8593
a kill -9 was required...
vdr 1.3.25 only patch LNBsharing.
Rainer---<=====> Vertraulich
//
//
<=====>--------------ocholl, Kiel, Germany ------------
[View Less]