Petri Helin wrote:
Udo Richter wrote:
In any case, try dumping the return value to syslog, I would really like
to know what additional flag is set on the return value.
I got 6, 9 and 11 when I did some debugging earlier.
I *think* that these are kill signals received by the child process
Petri Helin wrote:
Udo Richter wrote:
I *think* that these are kill signals received by the child process.
Which is strange, as the child does an exit immediately. (Unless you're
somewhere between 1.5.1 and 1.5.3 - this changed in 1.5.4)
6 is SIGABRT, 11 is SIGSEGV and 9 is SIGKILL.
I
Petri Helin wrote:
It seems to me that VDR still fails writing the NextWakeupTime every now
and then, even after I made the change described earlier. Do you have
suggestions on how to shutdown properly in order to get the
NextWakeupTime written to setup.conf? I run VDR as a daemon and shut
Hi list,
The original hard link cutter patch has received a few bug fixes and an
enhancement, so its time to release an updated version.
Quick info:
The hard link cutter patch changes the recording editing algorithms of
VDR to use file system hard links to 'copy' recording files whenever
Joerg Bornkessel wrote:
On try to load the plugin on vdr start, i get following ERROR in
syslog:
Jul 30 22:27:23 vdr1 vdr: [9428] ERROR:
/usr/lib/vdr/plugins/libvdr-mailbox.so.1.5.6: \
undefined symbol: _ZN2Ax3VDR11OsdMenuBaseI8cOsdMenuE14clearStatusMsgEv
Is there a workaround or any
Martin Prochnow wrote:
I call in my plugin in a loop (in a thread) cCutter::Active() every
second. If I stop an editing process over the main menu entry, VDR
crashes from time to time:
cCutter::Active is more than a simple query function. It also does the
cleanup of the thread, the error
Hi,
I've published version 0.0.2 of the OSDServer plugin.
OSDServer is a plugin that allows external programs to use the OSD and
the menu system of VDR. Access is done via TCP/IP and a simple script
language that is primarily designed to be handled by perl programs and
shell scripts. Until
Norbert Goebel wrote:
Why is this done in this order and not like this:
a) check the shutdown-hooks and if those exit with exitcode=0 do b) else
abort the shutdown sequence without a message (exception: the script
wants to be verbose and does it itself)
b) display shutdown abort message
Norbert Goebel wrote:
does vdr (especially version 1.4.7 as I am using this right now) tell
the shutdownscript in any way what caused the shutdown-request (pressing
the poweroff button on fb or the idle timer)?
See the INSTALL file of VDR. The 5'th parameter of the shutdown script
is 0 for
Gregoire Favre wrote:
I use Min. event timeout/user inactivity of 60 minutes but when my
computer poweron vdr only seems to wait for about 5 minutes before
shuting down my computer if a timer isn't programmed which is quiete bad
if I power it by hand and don't come after it directly.
This is
Torgeir Veimo wrote:
Bummer! I was hoping it could be used to detect ads during live TV and
reduce the volume. Ads always have louder sound, which is extremely
annoying.
Noad needs some time to find the most probable start/end point of
commercials, so its generally not able to do it live.
Brendon Higgins wrote:
Jun 30 21:12:55 phi vdr: [3452] frontend 0 timed out while tuning to channel
0, tp 536
I'm a bit confused that it's
trying to access channel 0, since AFAICT there is *no* channel 0.
'Channel 0' is usually the scan for new channels on currently unused
transponders.
Hi Klaus,
Found a bug in VDR-1.5.5 in non-UTF8 mode. In any text field, when the
cursor is on an uppercase non-ASCII character like ÄÖÜ, the up/down key
jumps directly to A.
The core problem is that the non-UTF8 version of Utf8ToArray
sign-extends chars to uints, turning the ä of the
Adrian C. wrote:
Anything I record get's splited into numerous
pieces (like VDR is recording every frame into diffrent file)... so when
I try to playback a recording I don't get smooth playback but something
like slow motion.
VDR does split files, but usually after 2gb, or at least 100mb.
Petri Hintukainen wrote:
It might be even some plugin. All timeouts (cTimeMs, cCondVar,
cCondWait) use current wall clock time to set the timeout.
Thats not even all: There are 140 references to time(NULL) in VDR, and
most of them are used for timeouts between a few seconds and some hours.
Andrew Herron wrote:
If I have some existing vdr recordings on another partition is there a
way to include these so that they are visible inside vdr's recording's
menu?
You can symlink the partition into the first partition as directory. Not
very clean, but should work for playback.
(but
Josce Unknown wrote:
I am sure this would fix the problem. However, is this really the way it
should work?
The clock is four minutes off, let's PANIC?
VDR still defaults to start recordings three minutes before scheduled
time, right? I wouldn't want to rely my recordings on a clock that is
Unknown Unknown wrote:
May 31 20:23:38 localhost vdr: [3413] Local Time = Thu May 31 20:19:37 2007
(1180631977)
May 31 20:21:01 localhost vdr: [3405] PANIC: watchdog timer expired -
exiting!
Could vdr turn off the watchdog before it sets the system time, if that is
the problem?
IMHO
Pasi Juppo wrote:
For some reason VDR has decided to remove recordings. I've been
suspecting this for some time but now I'm sure. I've been recording Tomi
Traktori (a serie for kids) and there used to way more recordings that
single page. Now only single page and all recordings in 2007 have
Chris wrote:
If I use an 'empty' shutdown script that just starts with #!/bin/sh or
bash or whatever, the script itself becomes a zombie. And if I use a script
with just an empty line, sh becomes the zombie. So in either way,
something is wrong and it can not be the script's fault.
I've
Olaf Titz wrote:
After that, some existing cut marks are not on a GOP
boundary any more (looks like genindex really has fixed something). I
can't edit these cut marks any more.
[...]
Proposed fix: on the 7 and 9 keys, look if the mark is really on a GOP
boundary, and if not, scan for the next
Olaf Titz wrote:
The only quick solution I can think of is to turn off Use episode name
in Setup/Recording.
It would be nice to have a flag in the individual timer for this.
There are a lot of shows where you want episode subdirs and a lot of
others where the EPG is so broken you're better off
VDR User wrote:
This patch just changes charset querying to not only look at environment
variable LANG, but respect all in correct order. So now I can overwrite
charset setting with LC_CTYPE and LC_ALL.
Just curious, why would you need to query anything other than the
environment LANG
Stefan Huelswitt wrote:
The current code segfaults on the first terminal access (e.g.
printf), if the effective vdr user doesn't have sufficient
rights.
Just a thought, would it work to open the terminal before switching the
user? Or is the access rights status checked again later on?
(/me
Guido Fiala wrote:
Maybe you should mount reiserfs with the notail option for video-partitions,
which should kill most of the overhead. I run reiserfs with vdr since 10
years or so, no problems at all even when running in 100% used diskspace
often.
AFAIK notail disables reiser's ability to
Sven Schwyn wrote:
After some research on Reiser4 and the surprising twist in Hans Reiser's
personal fate (he was arrested with murder charges last October), I'm
having my doubts as far as further development/bugfixing is concerned
and therefore decided to switch back to ext3 before playing
Anssi Hannula wrote:
However, the usual use-already-tuned-devices check in GetDevice() only
checks for device-Receiving(), which does not report transfer-moded
device, resulting in the new receiver being started on second device,
thus both devices being reserved for receiving data from the same
Hans-Peter Jansen wrote:
Hi,
we're suffering from continuous vdr restarts every few minutes during
recording of certain programs, while this is spat into syslog:
[...]
The signal quality looks fine.
Did you check the signal quality of the second card, or just the first
card? The femon
ShorTie wrote:
I understand the need for a rewrite of the shutdown sequence for vdr
when using timers and stuff.
But I was wondering if the good old crtl/c was going to make it’s way
back in?
The signal handler for SIGINT (aka. Ctrl+C) should work as before. Do
you have any problems with
Andreas Brachold wrote:
i like your patch, but its work only on some recordings.
Its failed with a segmentation fault, on cutting.
The only differ are unbalanced marks (out missed)
Confirmed, the patch doesn't handle the case that the last mark is a
cut-in mark, not a cut-out. In that case
Richard Lithvall wrote:
Why not just change the naming of video files to four, five or even
eight digits?
The real limit is that the file format and the VDR API uses byte sized
integers to represent this. (cIndexFile::Get uses an uchar *FileNumber.)
This could be extended, even with moderate
Heikki Manninen wrote:
On su, 2007-03-18 at 15:46 +0100, Klaus Schmidinger wrote:
You can disable all the cThread::EmergencyExit() calls if you don't want
this. Maybe I should disable this by default in a future version - and wait
until people start complaining because recordings are broken...
Jürgen Schilling wrote:
I've the same problem with VDR 1.5.1... The VDR does not shutdown
after a recording.
It looks like VDR assumed the start to be manually, not automatically.
Same for you: Check the logs for assuming manual start of VDR, next
timer event at and next plugin wakeup at
Rolf Ahrenberg wrote:
No assuming manual start of VDR entry found on my logs, so this really
was on automatic wakeup for the timer.
If VDR did detect it as manual start, then something else must have
caused VDR to believe that there's an interactive user. Something
triggers the activity,
Rolf Ahrenberg wrote:
On Sun, 4 Mar 2007, Udo Richter wrote:
Mar 4 18:31:14 xxx vdr: [6740] LastActivity: Never
Mar 4 18:31:14 xxx vdr: [6740] ActiveTimeout: 2104
Mar 4 18:31:14 xxx vdr: [6740] Retry: Never
... goes on and on and no shutdown attempts...
Found it! And, more important
Hi list,
In the 'final' 1.0 version of the shutdown patch, and in VDR 1.5.1, a
small bug slipped through that prevented automatic shutdown after VDR
started for a recording only.
I've uploaded a new 1.1 version of the patches for VDR 1.4.5, VDR 1.5.0
and VDR 1.5.1 to my web page:
Rolf Ahrenberg wrote:
I've noticed some shutdown problems with vdr-1.5.1 in my setup: when my
vdr wakes up for a timed recording, it doesn't automatically shutdown
itself anymore after the recording is done. The MinEventTimeout is set
to 15 minutes and MinUserInactivity to 600 minutes, but in
Hi list,
Now that VDR 1.5.1 was published, I've also published the final 1.0
version of the shutdown rewrite. The changes since 0.4 are mainly by Klaus.
http://www.udo-richter.de/vdr/patches.html#shutdown
http://www.udo-richter.de/vdr/patches.en.html#shutdown
The patch is identical to the
Frank Schmirler wrote:
this patch allows plugins to replace the VDR mainmenus Schedule, Channels,
Timers and Recordings by a different implementation.
There are already a few plugins around which do something like that, using
their own idea of a patch. So Tobias Grimm, Martin Prochnow,
Udo Richter wrote:
I've finished a fourth version of the shutdown rewrite. Again there are
two patches available, one for VDR 1.5.0, and one with slight changes
for 1.4.x.
Changes:
- Handle setup menu restart questions in cShutdown::ConfirmRestart()
- Act differently on SIGHUP:
Restart VDR
Simon Baxter wrote:
Anyone know a good reference on how to write VDR plugins?
There's not much available, sorry.
You can start by taking a look at the PLUGINS.html, then just start with
a test plugin. The newplugin script will generate one for you.
From there, its a matter of trying. For
Hi list,
I've finished a fourth version of the shutdown rewrite. Again there are
two patches available, one for VDR 1.5.0, and one with slight changes
for 1.4.x.
http://www.udo-richter.de/vdr/patches.html#shutdown
http://www.udo-richter.de/vdr/patches.en.html#shutdown
Changes:
- Renamed
Hi list,
I've updated the runvdr extreme script to version 0.2.
runvdr extreme is a runvdr script, just like the runvdr script included
in the VDR distribution. Additionally, it supports configuration files,
lots of command line options and more features.
-
Darren Salt wrote:
We re-define SIGHUP, so that it doesn't terminate VDR instantly, but
instead checks for activity. If user and vdr is inactive, act just like
sigterm, if there's some activity, ignore the signal.
An external script could then repeat sending the SIGHUP periodically until
Simon Baxter wrote:
I'm looking for a way to execute a command whenever a channel change is
selected. I think part of the 'sky' plugin is close to what I want -
without the stream type changing part.
Has anyone done anything like this?
Not as far as I know, but it should be possible with a
Darren Salt wrote:
I guess the only situation that may cause a problem is if the VDR never
shuts down, eg. has no shutdown script at all. It must have some Min User
Inactivity setting, or else live viewing could be interrupted by the
automatic update.
The user inactivity setting isn't relevant
Darren Salt wrote:
Then there's the upgrade restart, which should be available via a signal. The
actual restart should be deferred if VDR is currently busy. (It is *possible*
to implement this via runvdr, but it's a lot easier to handle if VDR can
re-exec itself.)
H. Some kind of
VDR User wrote:
Also, the user inactivity stuff is again, a bad idea. Vdr should not
assume anything or take action just because the user hasn't interacted
with it in a while. This type of behavior is simply not consistent with
other devices and not a behavior the user would expect. My tv
VDR User wrote:
There is no reason to behave otherwise unless
it's done thru some kind of auto-shutoff? [y/n] setting.
As said above, its called Min User Inactivity and can be set to 0.
Also, a coffee-maker is not a device used for entertainment purposes.
Nobody turns their coffee-maker on
Marko Mäkelä wrote:
However, you're right about breaking that feature: if PlayVideo() and
PlayAudio() start refusing data when Shutdown.IsUserInactive() holds,
the playback will never end, and VDR would probably wait
MinUserInactivity (3 hours by default) until shutdown.
While playback, the
Peter Dittmann wrote:
How about a new two level inactivity timeout ?
After VDR starts the inactivity timeout uses a first short timeout (e.g.
5min) assuming that VDR has automaticly being started.
Actually, even in worst case you'll see the 5-minute-countdown, so you
already have enough time
Jere Malila wrote:
Is it online somewhere? Udo's site seemed to be down / reinstalled?
Dammed, they've busted the server.
I've put up a temporary mirror here:
http://www.mathematik.uni-kassel.de/~urichter/temp/mirror/vdr/
Cheers,
Udo
___
vdr
Marko Mäkelä wrote:
Actually I would press the pause button, as I usually don't want to miss
anything. And then the playback should be halted anyway, no matter if
display is on or off.
But you surely would power the display off, to avoid burning the still
image on the CRT or plasma screen or
Marko Mäkelä wrote:
First, and more important: Can you please suspend the playback of
recordings when Shutdown.IsUserInactive() holds? Here is the relevant
hunk from my vdr-suspend patch:
This would break the other interesting feature, shut down VDR as soon as
the playback ends. Also, this
Kartsa wrote:
burn.c:32: error: conflicting return type specified for â
../../../include/vdr/plugin.h:43: error: overriding â
The original plugin.h of VDR has this in line 43:
virtual cString Active(void);
This was introduced on VDR 1.3.47, and conflicts with earlier patches
that had
Marko Mäkelä wrote:
On Tue, Jan 23, 2007 at 10:19:57PM +0100, Udo Richter wrote:
Since the shutdown script runs in the background, the stdin could
probably be closed. After all, VDR should continue to 'own' stdin, and
running in the background would probably cause a conflict. However,
running
Marko Mäkelä wrote:
The problem seems to lie in shutdown.c, in SystemExecSession().
It won't close file descriptor 0, but it will close anything above
STDERR_FILENO (which is normally 2). This function appears to show
up in strace output as clone(). Adding close(0) to the function
fixes the
mailto:[EMAIL PROTECTED] wrote:
Werner fixed the A/V sync problem. Please test firmware f12623.
See
http://www.vdr-portal.de/board/thread.php?postid=566692#post566692
I can confirm that the two known issues ('Lost' on ATV and 'Lost' sample
by Tero) both play smooth and properly synced for
Marko Mäkelä wrote:
Right, becoming inactive is not that time-critical. I will give your
suggestion a try: in the MainThreadHook of each plugin, poll
Shutdown.IsUserInactive().
It should work, though the first key press may trigger some longer work,
and the MainThreadHook will be called at
Marko Mäkelä wrote:
A minor cosmetic thing: the '#' of pre-processor directives should always
be located at the first column of the line.
The only indented directives are for the debug output I think, and this
will probably be removed before the final integration anyway.
A more important
Hi list,
I've finished a second version of the shutdown rewrite. This time, there
are two patches available, one for VDR 1.5.0, and one with slight
changes for 1.4.x.
http://www.udo-richter.de/vdr/patches.html#shutdown
http://www.udo-richter.de/vdr/patches.en.html#shutdown
- Fixed negative
Klaus Schmidinger wrote:
However, (don't know exactly if this has already been suggested as such)
maybe a simple feature in the new shutdown code could be to allow the
user to specify *one* time at which VDR shall be guaranteed to be up,
along with a time period for which it shall stay up. That
Klaus Schmidinger wrote:
Udo Richter wrote:
The downside of this would be that again several external tasks would
fight for one resource: the time set in VDR.
I don't see why several external tasks would fight for that time.
This is something the user would set up the way he wants it. If he
Lars Fredriksson wrote:
I'm trying to use VLC to stream an mms:// as MPGA to my VDR-box where I
have installed the streamplayer plugin, but I get no sound!
Streamplyer says it's receiving a stream and the bitrate show, the
buffering value goes up to the value a specify and the starts over from
Pjotr Kourzanov wrote:
I am experiencing VDR errors when loading EPG via SVDRP. If the EPG
data to
be loaded is larger that 3 MB then VDR silently drops the SVDR connection.
Everything is fine if the data is truncated to fit 3 megs.
There is an issue if the EPG download is too slow. In
[EMAIL PROTECTED] wrote:
The alternative would be to implement a generic task scheduler and make
timers one special type of schedule. This would get REALLY big.
Yes, but it will be the much better design.
It will open the option to do VDR related timed and maintainance tasks.
There must be
Matthias Schwarzott wrote:
I think a much easier solution (implementable in runvdr/vdr-initscript) is:
Write down wakeup-time when shutting down and comparing that to time when
system/vdr starts (with some margin).
That would be the way I would do it. Reconstructing the reason for
shutdown
Matthias Schwarzott wrote:
In gentoo vdr package we added a small hack (attached), which implements a
svdrp call down to tell vdr it is inactive and will shutdown in X minutes.
We call this from shutdown-scripts to let vdr retry shutdown in 5 min (or
other value if needed).
Question is: Is
Hi list,
The program code for automatic and manual shut down and for automatic
restarts for timer recordings is in VDR 1.4.x very complex and
error-prone, and behaves strange in some situations. With Klaus'
permission I am working on a re-implementation for the upcoming 1.5.x
developer
Christian Wieninger wrote:
for a new feature of epgsearch, I'd like to do a continuous check (in a
separate thread) if any timer was deleted via OSD or SVDRP since the
last check.
The only thing I found so far is to build a timer array and compare it
at each check with the current timer list.
Thiemo wrote:
Plus, effectively, while
you currently confirm shutdown with power, ok, you now confirm with
power, power. And together with the other numerous reasons for not
shutting down, this gets confusing: Use power button to override running
timers, and use ok button to override timers in
Marko Mäkelä wrote:
I have written a patch for making the Power key suspend the output.
Some softdevice users have found it useful, but I've been told that
the patch does not stop playback on full-featured cards. You can
access the patch here: http://www.iki.fi/~msmakela/software/vdr/#suspend
Thiemo wrote:
So here is my solution:
- if a recording is running and User presses Power tell him the box will
shutdown after the current recording
- If he presses Power a second time, ask if he realy wants to do this (like
before) *and* stop any running recordings (i reused the code from Udo
Klaus Schmidinger wrote:
Matthias Schwarzott wrote:
Why not just keep it away. I think it is not too hard to replace that
in the plugins.
You're probably right.
By the time I'll release the next maintenance patch I guess
all plugins will have been updated, anyway.
This strikes on the
Klaus Schmidinger wrote:
The attached patch makes it call cPluginManager::Active() only
if it really wants to shut down, and if there is actually an option
for plugins to delay the shutdown (i.e. this is not a forced shutdown).
If cPluginManager::Active() returns 'true' once, it waits for
Klaus Schmidinger wrote:
For VDR, the two if's in the inactivity shutdown should be swappable
with no serious side effects, see attached diff. All the calls do
noting important, except the cCutter::Active() call, and this one is
called often enough in other situations. But even with this
Klaus Schmidinger wrote:
Are you sure?
ACTIVITYTIMEOUT is 60 seconds, so wouldn't your change just
avoid the calls until 60 seconds after the last user activity?
Hmm, you're right. Its not a test on Setup.MinUserInactivity * 60. My
patch would just avoid these calls the usual 60 seconds after
Hi Klaus,
I've isolated an null pointer dereferencing bug in cSkins::Message():
In the very rare case that a message is displayed using a
cSkinDisplayMessage object, and the message is not removed before
another cSkinDisplay object takes control, the next attempt to display a
message while
Hi list,
the attached patch fixes compile issues with pre-4.x GCC compilers.
Cheers,
Udo
Index: osdobjects.h
===
--- osdobjects.h(Revision 812)
+++ osdobjects.h(Arbeitskopie)
@@ -214,6 +214,7 @@
virtual
BRUNETON Béranger wrote:
Is there a way, from a plugin, to save immediately the setup.conf
instead of waiting a proper VDR shutdown?
I a word how to call Setup.Save() from a plugin method ?
Calling Setup.Save() should be fine, unless you do it from a background
thread. VDR does call it too
Jörg Wendel wrote:
For plugin developers, I suggest to keep it simple in there. Its
probably a good idea to tr() the string just once and cache it afterwards.
this would be a nice change in the streamdev plugin.
The attached patch does it.
This patch has one side effect: The message wont be
Simon Baxter wrote:
I'm trying to get my PAL PVR-500 working in a non-PAL country. May
sound weird, but I'm preparing to move back to New Zealand.
Correct me if I'm wrong, but isn't NZ a PAL country? At least from what
I know the Australian area is mostly using PAL.
Cheers,
Udo
Jörg Wendel wrote:
a question about the 'new' vdr shutdown handling implemented a few versions ago.
[..]
But why vdr call this so often, isn't it only required if the vdr is going to
shutdown?
Even without the log message, at first view it looks like unnecessary load?
VDR calls this function
Udo Richter wrote:
Udo Richter wrote:
Tero Siironen wrote:
Here is a 3 minute clip from the episode of Lost I told earlier.
http://kotisivu.suomi.net/izero/lost.tar
80MB file and played ok at least with VLC v 0.8.5. and MPlayer on OS X
The only disturbance I've noticed is a slight jitter
VDR User wrote:
about this... Copy the mplayer code that does the PES layer and slap it
into vdr just to test if the problem persists?
I don't think that it is that easy. Its just educated guessing, but I
assume that the mpeg data is going a long way through the mplayer core,
through
whoMAN wrote:
mplayer uses either LAVC or FAME [depending on how mplayer was
compiled/configured] to convert EVERYTHING to MPEG1 before it is sent to
the DVB Device. In essence, it transcodes in realtime.
Not too efficient, but since transcoding to MPEG 1 takes little
resources, most people
Tony Houghton wrote:
If you want to rely on existing stuff, maybe you can use the remote
plugin from Oliver Endriss for your needs - it supports tty control and
telnet control.
That sounds like the best idea. If I wrote my own plugin I'd probably
just be effectively duplicating the telnet
Tony Houghton wrote:
[When playing a recording]
I've since noticed that when SVDRP freezes while the progress bar is on
screen the clock of the current time shown under the bar stops counting,
although playback continues. Perhaps the OSD is freezing as well as
SVDRP?
Its possible that the VDR
C.Y.M wrote:
mplayer -vo mpegpes -ao mpegpes -framedrop -cache 4096 -slave -nolirc -quiet
001.vdr
Notice that -framedrop is added to the command line. I wonder if that is the
reason why mplayer is immune to the a/v desync problem.
Definitely not just that. My playback issue already
Morfsta wrote:
Certainly I think the problem is that VDR is not properly doing sync,
In a way, I agree. VDR does not sync at all. Never.
Simplified, here's what the VDR playback really does:
- Read data from file in frame-sized chunks into read buffers
- If the DVB driver accepts data, read
C.Y.M wrote:
If the answer to this question could be discovered, then problem solved. So,
what you are suggesting is VDR is not doing something that mplayer is doing that
fixes the problem. Hmm... so then it is not a driver or firmware issue
after all?? Could we agree that much? :)
I
Glyn Edwards wrote:
I've got VDR (1.4.3) running on a machine by my TV and have just been
playing with the xineliboutput plugin to stream vdr over the network.
Everything works well on its own but I'd like to be able to have someone
watching TV on one channel via the dxr3 and someone else
martin wrote:
So, as far as i can read with my basic knowledge: if there is a difference
of more then 2 (don't know the unit, but I think it must be seconds), there
is a step in time.
If SAT time and internal clock differ by more than 2 seconds, and this
time offset is reported twice in a
C.Y.M wrote:
Utilizing mpegpes is really the best of
both worlds. We would still be using the video output on the FF card but having
software to process the actual mpeg decoding. There would be no transcoding
involved because obviously the recording would already be in a DVB resolution
format.
Harald Milz wrote:
I'm trying to compile osdpip-0.0.8 in vdr-1.4.1, and I get
osd_info.c:233: error: ‘cDevice’ has not been declared
Anybody managed to port it to 1.4? 0.0.8 is from May 2005...
osdpip requires a patch since 1.3.31. See wiki:
Reinhard Walter Buchner wrote:
I have the same problem (still using an older version of VDR, tho).
VDR does delete the contents of the directory, but it doesn't
always delete the primary directory below 'video'. In your example
you (or in my case me ;o)) still have
Andreas Mair wrote:
that's a known issue with Internet Explorer. I don't know how to fix this
correctly. Other browsers (FireFox, Opera, Konqueror) do fine.
You can take a look at contrib/user.css_example to find a workaround or use
another browser ;)
Thats one of the flaws of the IE layout
Rene Bartsch wrote:
But the remote plugin doesn't have OSD, does it?
It has. Its a really good replacement for the buggy control plugin. The
only thing I miss is the possibility to end a session with Ctrl+C, you
have to terminate the telnet program side.
Cheers,
Udo
C.Y.M wrote:
Thanks for your replay, but I was looking for a switch that would make vdr run a
script right after vdr starts up.
If you want to start a program together with VDR, why don't you put it
into your runvdr script?
Cheers,
Udo
___
C.Y.M wrote:
Yes, I like the idea of backgrounding VDR using and then using 'wait $PID'.
Is that the method you use? I've been trying to find the best way to do this.
Could you give me an example? :)
Something like that. This is a snippet of my overgrown runvdr script:
# Run VDR
eval
301 - 400 of 414 matches
Mail list logo
