Petri Helin | 1 Aug 2007 23:33

New shutdown procedure not working as expected

Hi,

It seems that the new shutdown procedure introduced for versions 1.5.x 
is (at least for me) not working as expected. The problem is that it 
does not recognize correctly whether VDR was started manually or not. In 
fact it thinks every time that it has been started manually. I traced 
the problem to the SystemExec call in 
cShutdownHandler::CallShutdownCommand where Setup.NextWakeupTime is 
updated only if the SystemExec call returns 0. i changed it to accept 
all values greater or equal to 0 and now Setup.NextWakeupTime gets 
updated properly. Can some explain me why 0 is expected?

Here is the patch that I came up with:

--- shutdown.c.orig     2007-08-02 00:14:49.000000000 +0300
+++ shutdown.c  2007-08-02 00:15:10.000000000 +0300
 <at>  <at>  -126,7 +126,7  <at>  <at> 
    time_t Delta = WakeupTime ? WakeupTime - time(NULL) : 0;
    cString cmd = cString::sprintf("%s %ld %ld %d \"%s\" %d", 
shutdownCommand, WakeupTime, Delta, Channel, *strescape(File, "\"$"), 
UserShutdown);
    isyslog("executing '%s'", *cmd);
-  if (SystemExec(cmd, true) == 0)
+  if (SystemExec(cmd, true) >= 0)
       Setup.NextWakeupTime = WakeupTime; // Remember this wakeup time 
for comparison on reboot
  }

-Petri

(Continue reading)

Boguslaw Juza | 1 Aug 2007 23:42
Picon

xine-lib 1.1.7, xxmc on nVidia and xine-vdr

     Hi

Have anybody tried xine-lib 1.1.7 with xine-vdr plugin and
xxmc video engine? When I have done it, picture was flashing while
deinterlace was enabled.

I'm affraid, that support for bob deinterlace in xinelib 1.1.7
in xxmc module was changed and now is a little underdone...

                                    Boguslaw Juza

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Udo Richter | 2 Aug 2007 00:07
Picon
Picon

Re: New shutdown procedure not working as expected

Petri Helin wrote:
> I traced the problem to the SystemExec call in 
> cShutdownHandler::CallShutdownCommand where Setup.NextWakeupTime is 
> updated only if the SystemExec call returns 0. i changed it to accept 
> all values greater or equal to 0 and now Setup.NextWakeupTime gets 
> updated properly. Can some explain me why 0 is expected?

SystemExec called with true as second parameter should only return -1 in 
case of an error (logged to syslog) or the status of waitpid() in case 
of success. (see thread.c) Since the direct child instantly does 
exit(0), I assumed that status should also be 0.

On the other hand, the man page of waitpid mentions lots of macros to 
inspect the status return of waitpid. Maybe checking on these helps here.

Cheers,

Udo

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Reinhard Nissl | 2 Aug 2007 12:51
Picon
Picon

Re: xine-lib 1.1.7, xxmc on nVidia and xine-vdr

Hi,

Boguslaw Juza wrote:

> Have anybody tried xine-lib 1.1.7 with xine-vdr plugin and
> xxmc video engine? When I have done it, picture was flashing while
> deinterlace was enabled.
> 
> I'm affraid, that support for bob deinterlace in xinelib 1.1.7
> in xxmc module was changed and now is a little underdone...

One of my patches to xine-lib is to disable bob-deinterlacing on demand
(= per frame) when for example a frame has the "progressive" flag set.
While this feature was planned for DVD playback, I recently discovered
that several broadcasters set this flag too, most likely depending on
the frame's content. But it happens that the flag is set although there
is interlaced content in the image, e. g. some stations have
horizontally scrolling text at the top or bottom of the screen and
though set the flag.

There'll soon be a patch which makes this behaviour configurable at
runtime. But to disable this feature at the moment, have a look into
xine-lib/src/video_out/video_out_xxmc.c and locate the line

    disable_deinterlace = frame->vo_frame.progressive_frame

and change it to

    disable_deinterlace = 0 * frame->vo_frame.progressive_frame

(Continue reading)

Joerg Bornkessel | 2 Aug 2007 18:46
Picon

Re: vdr-mailbox-0.4.0 wont load with vdr-1.5.6


> 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 hints how is this to fix?

> Cannot help much, but c++filt says that the above missing symbol 
> translates to:

>    Ax::VDR::OsdMenuBase<cOsdMenu>::clearStatusMsg()

> This is at least not part of standard VDR, except for the cOsdMenu part,
> so its probably the mailbox plugin. Did you try a clean recompile of VDR
> and plugins?

> Cheers,

> Udo

Thanks, Udo

Damnd, my fault, short before i'll go crazy !!

I have on my system a local patch for more user keys in VDR,
there comes the conflikt from.
(Continue reading)

mike lewis | 3 Aug 2007 04:34
Picon

1.4.7 and xineliboutput issues

Hi Team.

Just would like to start this post with a big thankyou to everyone who
contributes to VDR.  It's a great piece of software and I have really
enjoyed toying with it over the past 6 months or so.

I've recently started using xinelibout plugin.  I have a vanilla vdr
1.4.7 apprat from the xinelibout plugin.

I've recently found that sometimes when watching a stream that is
currently recording, not sure why (could be load, disk speed etc) I
will see some on-screen stutering.  The scenario that happened last
night was as follows.

Recording a 2.5hr show / stream.  The recording was about 1hr 20 or so
mins through.  I had been watching the stream for about 30 minutes but
was up to about 40minutes in the stream, when I saw some "digital"
noise on the screen.  Like when you have a mild scratch on a dvd.
blocking etc.  I  happened maybe twice or three times over about 10 to
15 seconds and then went away..

Then, when I got to about 1hr20 minutes through watching the stream; I
get the "no signal" screen.  I tried "stopping" playback (so go back
to live tv) and no signal doesn't get replaced by the live tv.  I then
tried to watch some other recordings.. and the same thing happens
(that is, nothing.. the display shows like it's watching a show, but
the clock is stoped and ff/ww/jump don't change the clock value..).

So..  What can I do to debug whats going on and why??

(Continue reading)

Petri Helin | 3 Aug 2007 12:55

Re: 1.4.7 and xineliboutput issues

On 8/3/07, mike lewis <lachlanlewis <at> gmail.com> wrote:
>
> So..  What can I do to debug whats going on and why??
>

First of all you'd need to tell us the version of xineliboutput you
are using and the way you use/start xineliboutput. Which frontend do
you use (remote or local), what parameters do you give to
xineliboutput, what settings have you set and so on. Also information
about cpu load and used hardware could be useful.

I use remote frontend (vdr-sxfe) and start it like this in a script:

STARTTIME=`date +%Y%m%d_%H%M`
vdr-sxfe --reconnect --fullscreen --audio=alsa --video=xv
--display=0.0 --verbose xvdr://127.0.0.1 2>
/var/log/vdr/vdr-sxfe_err_${STARTTIME}.log 1>
/var/log/vdr/vdr-sxfe_${STARTTIME}.log &

That way I have always a log of what's happened.

-Petri

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Igor | 4 Aug 2007 15:25
Picon

Extension HD PCI from ReelMultimedia in August ?

Hello

here http://www.reel-multimedia.de/shop/product_info.php?products_id=223
there's info about of selling this hardware h264 decoder in August. 

and here there's first test's result
http://www.vdr-portal.de/board/thread.php?postid=631271#post631271

Igor

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Udo Richter | 4 Aug 2007 16:17
Picon
Picon

[ANNOUNCE] Hard link cutter patch 0.1.4

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 
possible to speed up editing recordings noticeably.

The new feature of this release is dynamic increase of recording file 
size before VDR runs out of xxx.vdr files. That way, for example, VDR 
will use 30Mb for 001.vdr - 206.vdr and 2000Mb for 207.vdr - 255.vdr.

For a complete list of changes, see web page. Don't miss the 
README-HLCUTTER included in the patch.

http://www.udo-richter.de/vdr/patches.html#hlcutter
http://www.udo-richter.de/vdr/patches.en.html#hlcutter

Cheers,

Udo

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

(Continue reading)

Gavin Hamill | 5 Aug 2007 17:37
Picon

[ANNOUNCE] Frontend for VDR/mplayer on Nokia 770/800

Just some Python I knocked together - don't expect the world. It reads a
channel list via SVDRP, shows the list, and launches mplayer with the
appropriate arguments.

Requires python and mplayer on the Nokia, VDR with streamdev-server and
a machine (perhaps the VDR machine) with a CGI-capable webserver  (I use
thttpd) to transcode from MPEG2 -> low bitrate MPEG4 so the 770 can play
it.

There's no easy .deb to install - just a tarball, I dunno how to make
packages for Maemo yet. Good luck.

http://bum.net/vdrview.tar.gz

Cheers,
Gavin.

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Gmane