Re: [vdr] [ANNOUNCE] VideoCD Plugin 0.9

[Stone]

On Jan 21, 2008 8:31 PM, Thomas Heiligenmann <[EMAIL PROTECTED]>
wrote:

> A new version of the plugin is available:
>
> Download: http://www.heiligenmann.de/vdr/download/
> Filename: vdr-vcd-0.9.tgz
> Filesize: 33687
>
> See HISTORY and README for details. Thanks to all, who have provided
> ideas and patches.
> 


Hello,

Thanks for the update.  I had a small issue with the changes to the Makefile
in 0.9 though.  Here is what I had to do to get it working.. (I am prettry
sure its DVBDIR that was supposed to be removed, not VDRINC).

--- vcd-0.9/Makefile2008-01-16 07:29:39.0 -0800
+++ vcd-0.9/Makefile2008-01-22 01:04:55.0 -0800
@@ -21,6 +21,7 @@
 ### The directory environment:

 VDRDIR = ../../..
+VDRINC = $(VDRDIR)/include
 LIBDIR = ../../lib
 TMPDIR = /tmp

@@ -47,7 +48,7 @@

 ### Includes and Defines (add further entries here):

-INCLUDES = -I$(VDRINC) -I$(DVBDIR)
+INCLUDES = -I$(VDRINC)

 DEFINES += -DPLUGIN_NAME_I18N='"$(PLUGIN)"' -D_GNU_SOURCE
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [ANNOUNCE] AudioIndexer.patch for VDR-1.5.10 provides correct length for new radio recordings

[Stone]

When I apply this patch to vdr-1.5.10, VDR no longer starts.  Could this new
Audio Indexer patch be conflicting with the dynamc ringbuffer patch?

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Not good behaviour from vdr

[Stone]

On 10/9/07, VDR User <[EMAIL PROTECTED]> wrote:

I was hoping some of these ideas would have made it into the next release.
But, since it didnt, does anyone have a patch put together?

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Not good behaviour from vdr

[Stone]

>
> >
>
> Maybe a solution for all the ideas in here ? Let vdr call a command and
> decide based on exit status ? This could be simply set to /bin/false for
> never restart or any sophisticated logic for everything else ?



The main problem for me is that my reception is not that great.  During bad
weather, I often lose signal.  Now, if vdr happens to be recording when that
signal is lost, it will do an emergency exit.  Restarting isnt going to make
the weather get any better.  It will just keep restarting, over and over.
As soon as the rain stops, the signal comes back and vdr is fine.  Perhaps
having to reload the drivers is only a problem for people using old
kernels.  I just want to know if my recordings are corrupted or not w/o
having to watch them first. If I am not home when the problem occurs, I want
to be able to tell which ones are bad w/o having to watch it and notice the
end of the show is missing.  Marking the recording in the Recordings Menu
with any symbol you want is good enough for me, but forcing vdr reload the
drivers over and over during every storm doesnt seem like the right thing to
do either.  When the reception comes back, vdr works just fine.

Best Regards.

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Not good behaviour from vdr

[Stone]

On 9/30/07, VDR User <[EMAIL PROTECTED]> wrote:
>
> I like these ideas...  NO SIGNAL image in recording during no signal.
> Or that if no signal then no writing to disk.  And a warning in the
> log about a possible incomplete recording cuz of lost signal +
> identified in recordings menu by a special char like ? maybe.



I like the idea of appending the "?" symbol to every recording that triggers
the "no signal" flag.

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Not good behaviour from vdr

[Stone]

On 9/30/07, JJussi <[EMAIL PROTECTED]> wrote:
>
> On Sunday, 30. Septemberta 2007 10:35:07 Stone wrote:
> > Since the recording is scheduled, I would assume the user has room on
> the
> > disk (so disk space usage is not really the problem).  The only problem
> I
> > can see is that you might get a blank recording if the signal goes out
> (and
> > you think its recorded but its not).  So, perhaps vdr should NOT do a
> > emergency exit, but instead, just mark the recording as possible
> > incomplete?
>
> How about, when there is no stream - no writing to HD.. OK, if there is 15
> minutes break middle of stream, then recording "jump" those 15 minutes
> during
> playback.
> OR when no stream, in a recording there is recorded (in a picture) word
> "no
> stream", static picture takes little space and who is watching knows that
> what has happend!



I think most importantly that we know that there is a possible problem with
the recording because a flag got set that the signal was lost. But, I
understand what you are saying... perhaps VDR should be integrated with
femon :)

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Not good behaviour from vdr

[Stone]

Since the recording is scheduled, I would assume the user has room on the
disk (so disk space usage is not really the problem).  The only problem I
can see is that you might get a blank recording if the signal goes out (and
you think its recorded but its not).  So, perhaps vdr should NOT do a
emergency exit, but instead, just mark the recording as possible incomplete?

Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Prefermenu plugin ERROR: cOsd::SetAreas

[Stone]

On 9/23/07, Thomas Günther <[EMAIL PROTECTED]> wrote:
>
> Stone wrote:
> >
> > You dont think it has something to do with the changes in vdr-1.5.9?
> > Prefermenu uses the CreateOsd without the new "Level" attribute.
>
> No, this is not the problem but the now adjustable font size. The error
> occurs if the font height is an even number.
>
> Her is a fixed version of the patch:


Thanks, that was it.

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Prefermenu plugin ERROR: cOsd::SetAreas

[Stone]

On 9/22/07, Udo Richter <[EMAIL PROTECTED]> wrote:
>
> Stone wrote:
> > vdr: [4922] ERROR: cOsd::SetAreas returned 5
>
> This is oeWrongAlignment, and is returned if an OSD area has negative
> size, is outside of the screen, or does not byte-align.
>
> The latter is triggered if a 1-bit OSD has a width that is not multiple
> of 8, a 2-bit OSD has a width not multiple of 4, or a 4-bit OSD has a
> width not multiple of 2.
>
> You may want to check the settings for any width options, and set it to
> something multiple of 8.



Odd, because OSDWidth = 600 on my machine.  You dont think it has something
to do with the changes in vdr-1.5.9?  Prefermenu uses the CreateOsd without
the new "Level" attribute.  Can anyone verify prefermenu works with the
latest vdr release?

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Exist: windows media player that plays unaltered vdr files?

[Stone]

On 9/16/07, VDR User <[EMAIL PROTECTED]> wrote:
>
> On 9/16/07, Steffen Barszus <[EMAIL PROTECTED]> wrote:
> > Torgeir Veimo schrieb:
> > > Subject says it all. It's just way too much work to transcode files if
> > > I want to send a clip to friends.
> > VLC and mpui can do that. Also some direct show filter exist that make
> > it possible to play unaltered files.
>
> I dream of the day vdr recordings are something more supported then
> the current mpeg-pes format!



WMP may not work, but mplayer does. You can get that for windows.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Gentoo, vdr and extra plugins

[Stone]

On 9/14/07, JJussi <[EMAIL PROTECTED]> wrote:
>
> Hi!
>
> Have anybody knowledge how I can bring/use vdr-pluging what don't exists
> at
> gentoo..
>
> At other worlds, how I can install transfron  (what uses transcode) vdr
> pluging because it don't exists at gentoo repository.
>
>
> OR, is there easy way to convert VDR recordings to DivX (XDiV?), mpeg-4...
> And am I gonna loose subtitles during that process...



Transfron is pretty antique.  I suggest you give vdrconvert a try.

cvs -d :pserver:anoncvs:@ddimi.homeip.net:/cvs co vdrconvert

BR.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] vdr-pin-0.1.9 not locking menu

[Stone]

Hi,

I decided to try the pin plugin (0.1.9) with vdr-1.5.9 today.  I noticed
that the patch that came with the pin plugin was only for vdr-1.4.x, but the
merges seemed trivial and it appears to work fine.  The plugin does seem to
have a few minor problems.  It appears that when I associate "Recordings" or
"Timers" to a keymacro or separate key on the remote, vdr still allows me to
access them even when the childlock is enabled.  Also, I would like to
prevent someone from being able to push the "recording" button on the remote
when the childlocks are enabled, but this also still seems to work.  It
appears that really only the main menu is locked when the childlock is
enabled.  I would like to have most of the keys on the remote locked as well
(and not just have the menu options locked).

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] Prefermenu plugin ERROR: cOsd::SetAreas

[Stone]

Hello,

I am using prefermenu-0.6.6 along with prefermenu-0.6.6-1.5.3.diff that was
posted a while back on this list.  When I try to use prefermenu with
vdr-1.5.9, I get the following error:

vdr: [4922] ERROR: cOsd::SetAreas returned 5

Would anyone know how to fix this?

Thank you.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] EPG charset

[Stone]

On 9/1/07, Boguslaw Juza <[EMAIL PROTECTED]> wrote:
>
> On Sat, 1 Sep 2007, Stone wrote:
>
> > On 9/1/07, Boguslaw Juza <[EMAIL PROTECTED]> wrote:
> >> On Sat, 1 Sep 2007, Klaus Schmidinger wrote:
> >>> The character set is defined in the first byte(s) of the data that
> >>> is broadcast for each string. VDR uses that information to convert
> >>> that string to the character set used on your system.
> >> Which function do this conversion and where?
> >
> > Why not just  "export LANG="  at the beginning of your startup script to
> set
> > the locale?
>
> I have set it to pl_PL.ISO-8859-2 . If I'll set it to pl_PL.UTF-8,
> characters are not displayed correctly. But are not converted to '?' :).


When you do export LANG to pl_PL.ISO-8859-2, does VDR say the locale is
recognized on startup?

Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] EPG charset

[Stone]

On 9/1/07, Boguslaw Juza <[EMAIL PROTECTED]> wrote:
>
> On Sat, 1 Sep 2007, Klaus Schmidinger wrote:
>
> > The character set is defined in the first byte(s) of the data that
> > is broadcast for each string. VDR uses that information to convert
> > that string to the character set used on your system.
>
> Which function do this conversion and where?


Why not just  "export LANG="  at the beginning of your startup script to set
the locale?

BR.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] vdr-1.5.9 plugin patches

[Stone]

On 8/27/07, Stone <[EMAIL PROTECTED]> wrote:
>
> It seems the new "Level" parameter in cOsd has caused xine and softdevice
> to fail in compile with vdr-1.5.9.  Does anyone know how to fix these?



This seems to build now with these changes.  I didnt add backwards
compatibility for < 1.5.9 though.  Please let me know if this is the correct
way.

Best Regards.
diff -ru softdevice.cvs.orig/softdevice.c softdevice.cvs/softdevice.c
--- softdevice.cvs.orig/softdevice.c	2007-07-24 04:10:13.0 -0700
+++ softdevice.cvs/softdevice.c	2007-08-26 18:06:33.0 -0700
@@ -119,7 +119,7 @@
 static cOsd *osd;
 public:
 cSoftOsdProvider(cVideoOut *VideoOut);
-virtual cOsd *CreateOsd(int Left, int Top);
+virtual cOsd *CreateOsd(int Left, int Top, uint Level);
 static cOsd *GetOsd();
 };
 
@@ -130,9 +130,9 @@
 videoOut = VideoOut;
 }
 
-cOsd * cSoftOsdProvider::CreateOsd(int Left, int Top)
+cOsd * cSoftOsdProvider::CreateOsd(int Left, int Top, uint Level)
 {
-osd = new cSoftOsd(videoOut, Left, Top);
+osd = new cSoftOsd(videoOut, Left, Top, Level);
 return osd;
 }
 
diff -ru softdevice.cvs.orig/SoftOsd.c softdevice.cvs/SoftOsd.c
--- softdevice.cvs.orig/SoftOsd.c	2007-07-24 04:10:11.0 -0700
+++ softdevice.cvs/SoftOsd.c	2007-08-26 18:14:57.0 -0700
@@ -46,8 +46,8 @@
 /* ---
  */
 
-cSoftOsd::cSoftOsd(cVideoOut *VideoOut, int X, int Y)
-: cOsd(X, Y),active(false),close(false) {
+cSoftOsd::cSoftOsd(cVideoOut *VideoOut, int X, int Y, uint level)
+: cOsd(X, Y, 0),active(false),close(false) {
 OSDDEB("cSoftOsd constructor\n");
 OutputConvert=&cSoftOsd::ARGB_to_ARGB32;
 bitmap_Format=PF_None; // forces a clear after first SetMode
diff -ru softdevice.cvs.orig/SoftOsd.h softdevice.cvs/SoftOsd.h
--- softdevice.cvs.orig/SoftOsd.h	2007-07-24 04:10:11.0 -0700
+++ softdevice.cvs/SoftOsd.h	2007-08-26 18:13:17.0 -0700
@@ -91,7 +91,7 @@
 int ScreenOsdWidth;
 int ScreenOsdHeight;
 public:
-cSoftOsd(cVideoOut *VideoOut, int XOfs, int XOfs);
+cSoftOsd(cVideoOut *VideoOut, int XOfs, int XOfs, uint level);
 virtual ~cSoftOsd();
 virtual void Flush(void);
 
--- xine-0.7.10/xineDevice.c.orig	2006-11-21 12:44:48.0 -0800
+++ xine-0.7.10/xineDevice.c	2007-08-26 17:52:52.0 -0700
@@ -3426,7 +3426,7 @@
 #if APIVERSNUM < 10307
   cOsdBase *cXineDevice::NewOsd(int x, int y)
 #else
-  cOsd *cXineDevice::NewOsd(int x, int y)
+  cOsd *cXineDevice::NewOsd(int x, int y, uint level)
 #endif
   {
 //::fprintf(stderr, "NewOsd ---: %s\n", ::ctime(&(const time_t &)::time(0)));
--- xine-0.7.10/xineDevice.h.orig	2006-04-17 09:33:18.0 -0700
+++ xine-0.7.10/xineDevice.h	2007-08-26 17:51:03.0 -0700
@@ -120,7 +120,7 @@
 #if APIVERSNUM < 10307
 virtual cOsdBase *NewOsd(int x, int y);
 #else
-virtual cOsd *NewOsd(int x, int y);
+virtual cOsd *NewOsd(int x, int y, uint level);
 #endif
 
 cXineDevice(cPlugin *const plugin, cXineSettings &settings, cXineRemote *remote);
--- xine-0.7.10/xineOsd.c.orig	2006-04-17 09:35:17.0 -0700
+++ xine-0.7.10/xineOsd.c	2007-08-26 17:47:20.0 -0700
@@ -144,7 +144,7 @@
 #if APIVERSNUM < 10307
 : cOsdBase(x, y)
 #else
-: cOsd(x, y)
+: cOsd(x, y, 0)
 #endif
 , m_xineDevice(xineDevice)
 , m_xineLib(xineDevice.m_xineLib)
@@ -366,9 +366,9 @@
   {
   }
   
-  cOsd *cXineOsdProvider::CreateOsd(int Left, int Top)
+  cOsd *cXineOsdProvider::CreateOsd(int Left, int Top, uint Level)
   {
-return m_xineDevice.NewOsd(Left, Top);
+return m_xineDevice.NewOsd(Left, Top, Level);
   }
   
 #endif
--- xine-0.7.10/xineOsd.h.orig	2006-04-17 09:37:32.0 -0700
+++ xine-0.7.10/xineOsd.h	2007-08-26 17:42:17.0 -0700
@@ -81,7 +81,7 @@
 
   public:
 cXineOsdProvider(cXineDevice &xineDevice);
-virtual cOsd *CreateOsd(int Left, int Top);
+virtual cOsd *CreateOsd(int Left, int Top, uint Level);
   };
 
 #endif
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] vdr-1.5.9 plugin patches

[Stone]

It seems the new "Level" parameter in cOsd has caused xine and softdevice to
fail in compile with vdr-1.5.9.  Does anyone know how to fix these?

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] List of failed plugins for vdr-1.5.7

[Stone]

>
> I think I have also fixed text2skin to atleast compile with vdr-1.5.7.
> The new "gettext" language still needs to be implemented, but I think
> text2skin should work with the previous i18n method.  Please let me know if
> it works ok.



Best Regars.


text2skin-1.1-cvs_ext-0.10-20070620.3-vdr-1.5.7-1.diff
Description: Binary data
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] List of failed plugins for vdr-1.5.7

[Stone]

On 8/13/07, VDR User <[EMAIL PROTECTED]> wrote:
>
> Could someone post the link to the dvd cvs real quick?  I was under
> the impression it hasn't been maintained in a long time so I've been
> using dvd-0.3.6-b03.



cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/dvdplugin
co -P dvd
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] List of failed plugins for vdr-1.5.7

[Stone]

On 8/13/07, Stone <[EMAIL PROTECTED]> wrote:
>
> I must have had an older cvs link for the dvd plugin.  The Dvd plugin
> works now, thanks.
>
> Epgsearch now also builds with beta 13, thanks.
>
> Out of the rest, there are only two more that I really care about to fix
> for testing: text2skin and undelete.  Anyone have those patched up for the
> new i18n stuff?



I think I fixed undelete-0.0.6 with the following patch.  I hope I did that
right.. :)  So, the only thing I think I need help with is text2skin.
Thanks.
--- undelete-0.0.6/undelete.c.orig	2007-08-13 06:46:16.0 -0700
+++ undelete-0.0.6/undelete.c	2007-08-13 06:59:10.0 -0700
@@ -198,7 +198,11 @@
 private:
   // Add any member variables or functions you may need here.
   void FreeKeyNames(void);
+#if VDRVERSNUM >= 10507
+  char* OSDLanguage;
+#else
   int OSDLanguage;
+#endif
   void TestAndSetOSDLanguage(void);
   bool ProcessArg(int argc, char *argv[]);
 #ifdef UND_Debug
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] List of failed plugins for vdr-1.5.7

[Stone]

I must have had an older cvs link for the dvd plugin.  The Dvd plugin works
now, thanks.

Epgsearch now also builds with beta 13, thanks.

Out of the rest, there are only two more that I really care about to fix for
testing: text2skin and undelete.  Anyone have those patched up for the new
i18n stuff?

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] List of failed plugins for vdr-1.5.7

[Stone]

Hello,

As you all might have guessed, we have some more broken plugins (mainly due
to the i18n changes and some from OSDLanguage being changed from an integer
to a string).

*** failed plugins: autotimeredit burn dvd epgsearch skinenigmang text2skin
undelete

Can anyone help resolve these?

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Make.config options for vdr-1.5.7

[Stone]

On 8/13/07, Stone <[EMAIL PROTECTED]> wrote:
>
> Actually, I dont have to edit the default Make.config at all to make it
> fail.  If I copy Make.config.template to Make.config and use the default,
> it still fails.



Found the problem.. its a broken template.


--- Make.config.template.orig   2007-08-12 16:50:32.0 -0700
+++ Make.config.template2007-08-12 16:51:25.0 -0700
@@ -26,7 +26,8 @@
 #DVBDIR   = /usr/src/v4l-dvb/linux
 MANDIR   = /usr/local/man
 BINDIR   = /usr/local/bin
-LOCDIR   = /usr/share/vdr/locale  # set to ./locale to run VDR from within
its source directory
+# Set LOCDIR to ./locale to run VDR from within its source directory
+LOCDIR   = /usr/share/vdr/locale

 PLUGINDIR= ./PLUGINS
 PLUGINLIBDIR= $(PLUGINDIR)/lib

Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Make.config options for vdr-1.5.7

[Stone]

Actually, I dont have to edit the default Make.config at all to make it
fail.  If I copy Make.config.template to Make.config and use the default, it
still fails.

Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Make.config options for vdr-1.5.7

[Stone]

On 8/13/07, Stone <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> When I edit my Make.config and tell it to use CC=gcc-3.4 and CXX=g++-3.4,
> I get the following error:
>
> g++-3.4: ": No such file or directory
> make: *** Deleting file `.dependencies'
> ccache g++- 3.4 -g -O2 -Wall -Woverloaded-virtual -c -DREMOTE_KBD
> -DLIRC_DEVICE=\"/dev/lircd\" -DRCU_DEVICE=\"/dev/ttyS1\" -D_GNU_SOURCE
> -DVIDEODIR=\"/video/recordings\" -DPLUGINDIR=\"./PLUGINS/lib\"
> -DLOCDIR=\"/usr/share/vdr/locale  \" -DVFAT -I/usr/include/freetype2
> -I/usr/src/DVB/linux/include audio.c
> g++-3.4: ": No such file or directory
> make: *** [audio.o] Error 1
> make: *** Deleting file `audio.o'
>
> Anyone know whats wrong?



Ahh, I see a space in the middle of  g++-3.4.  How does that keep getting in
there?

Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] Make.config options for vdr-1.5.7

[Stone]

Hi,

When I edit my Make.config and tell it to use CC=gcc-3.4 and CXX=g++-3.4, I
get the following error:

g++-3.4: ": No such file or directory
make: *** Deleting file `.dependencies'
ccache g++-3.4 -g -O2 -Wall -Woverloaded-virtual -c -DREMOTE_KBD
-DLIRC_DEVICE=\"/dev/lircd\" -DRCU_DEVICE=\"/dev/ttyS1\" -D_GNU_SOURCE
-DVIDEODIR=\"/video/recordings\" -DPLUGINDIR=\"./PLUGINS/lib\"
-DLOCDIR=\"/usr/share/vdr/locale  \" -DVFAT -I/usr/include/freetype2
-I/usr/src/DVB/linux/include audio.c
g++-3.4: ": No such file or directory
make: *** [audio.o] Error 1
make: *** Deleting file `audio.o'

Anyone know whats wrong?
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [ANNOUNCE] VDR developer version 1.5.7

[Stone]

On 8/12/07, Klaus Schmidinger <[EMAIL PROTECTED]> wrote:
>
> VDR developer version 1.5.7 is now available at
>
>ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.5.7.tar.bz2
>
> A 'diff' against the previous developer version is available at
>
>ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.5.6-1.5.7.diff



Thanks Klaus.  Since i18n.c has changed in this new version of vdr, a few
common patches I have been using have broke.

1) jumpplay-0.9.diff
2) liemikuutio-1.13.diff
3) timercmd-0.1.diff (comes from epgsearch)

Can someone explain to me the proper way to fix these rejects with i18n.c?

Groeten.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] New shutdown procedure not working as expected

[Stone]

On 8/10/07, Udo Richter <[EMAIL PROTECTED]> wrote:
>
> Stone wrote:
> > I noticed my vdr-1.5.6 did an emergency shutdown when I had poor signal
> > reception during a recording, which in itself is a fine thing to do...
> > but my "runvdr" script didn't seem to catch the bad exit code (exit 1)
> > when vdr did that, so VDR never restarted.
> >
> > Does this have to do with the children spawning the exit code?
>
> No, the exit code of VDR is independent of what the script returns.
> You're sure that it did not exit with 0 or 2? Maybe some other problem
> prevented the next restart?


It is possible there was something else going on. I will investigate
further, but thanks for the  info.  Perhaps I will skip my runvdr script and
just use your "extreme" runvdr version instead :)

Groeten.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] New shutdown procedure not working as expected

[Stone]

On 8/9/07, Udo Richter <[EMAIL PROTECTED]> wrote:
>
> 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 use version 1.5.6. I tested with my normal shutdown script and with a
> > script that just does an "exit 0". No difference there. Can the script
> > itself have any influence on the return value?
>
> Since 1.5.4, VDR forks into a child that does nothing but fork off a
> second child, and do an exit(0). The second child exec's the shutdown
> script:
>
> VDR
>   +-- Child 1 -> exits
> +-- Child 2 -> runs shutdown
>
> That way the waitpid quickly returns, the second child becomes orphaned,
> and no process ends up being a zombie.
>
> Since the shutdown script runs orphaned, the return value of the script
> is not evaluated, nor does anyone wait for the script to terminate.



I noticed my vdr-1.5.6 did an emergency shutdown when I had poor signal
reception during a recording, which in itself is a fine thing to do... but
my "runvdr" script didn't seem to catch the bad exit code (exit 1) when vdr
did that, so VDR never restarted.   This code snippet used to work for me,
but doesn't now:

  eval "screen -D -m -S vdr $VDRCMD &"
  # Remember PID of VDR process
  PID=$!
  # Wait for VDR to end or signal to arrive
  wait $PID
  # Remember return value of VDR
  RET=$?
  if test $RET -eq 0 -o $RET -eq 2; then exit; fi
  TIMEOFDEATH=$(date +%s)

so, something is wrong with RET.  Does this have to do with the children
spawning the exit code?

Groeten.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] Warning fix for softdevice

[Stone]

Hello,

 Here is a patch to fix a compile warning in the latest softdevice plugin.

Best Regards..


softdevice.cvs-warning-20070411.diff
Description: Binary data
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] no sound on output of TT-premium C-2300

[Stone]

On 7/15/07, Chris F <[EMAIL PROTECTED]> wrote:


Hi everyone,

I've got a problem setting up a vdr system.

I installed Debian Etch with a vanilla 2.6.21 kernel and vdr using the
e-tobi packages.
I used the development firmware (f12623) and also tried the firmware from
linuxtv.org

Apart from the DVB-C FF card there is a WinTV PCI analogue TV-Card in that
I want to use to record analogue TV channels that are not broadcasted in
DVB-C.

The system works so far, however the analogue sound output of the card
doesn't work and I have ne idea why. I hope someone who uses the same card
can help me out on that.




This might be too obvious, but do you have "capture" enabled on the device
in the alsamixer settings?


My second problem is getting the analogue card to work. I installed the

analogue-tv plugin and using scantv I can find some channels, however if I
set up the channels.conf vdr doesn't add the channels to its list (i
stopped vdr before editing the channels.conf)
Whe can help me out on that ?

Thanks in advance for any help you can give me.


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] cdfs patches for mp3 plugin

[Stone]

On 7/10/07, Malte Schröder <[EMAIL PROTECTED]> wrote:


On Tue, 10 Jul 2007 12:30:45 +0200
Stone <[EMAIL PROTECTED]> wrote:

> Hi,
>
>   Today I tried to build the new 2.6.22 kernel but my external "cdfs"
module
> (which is used by the mp3 plugin) failed to compile with the following:

> --snip--

> Would anyone happen to know how to fix this?  Is the "cdfs" project
> currently maintained? I had found patches on vdrportal to fix cdfs for
> linux-2.6.21, but I cant seem to find anything for this new problem.

You could take a look at http://fuse.sourceforge.net/, more
specifically
http://fuse.sourceforge.net/wiki/index.php/FileSystems#Cddfs.
I haven't tried it myself, but sounds interesting I think.




I found a patch that seems to work...

Best Regards.


cdfs-2.6.19-linux-2.6.22.diff
Description: Binary data
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] cdfs patches for mp3 plugin

[Stone]

Hi,

 Today I tried to build the new 2.6.22 kernel but my external "cdfs" module
(which is used by the mp3 plugin) failed to compile with the following:

--snip--

/usr/src/modules/cdfs/2.6/root.c: In function 'cdfs_init':
/usr/src/modules/cdfs/2.6/root.c:598: error: 'CLONE_FS' undeclared (first
use in this function)
/usr/src/modules/cdfs/2.6/root.c:598: error: (Each undeclared identifier is
reported only once
/usr/src/modules/cdfs/2.6/root.c:598: error: for each function it appears
in.)
/usr/src/modules/cdfs/2.6/root.c:598: error: 'CLONE_FILES' undeclared (first
use in this function)
/usr/src/modules/cdfs/2.6/root.c:598: error: 'CLONE_SIGHAND' undeclared
(first use in this function)
make[5]: *** [/usr/src/modules/cdfs/2.6/root.o] Error 1
make[4]: *** [_module_/usr/src/modules/cdfs/2.6] Error 2
make[4]: Leaving directory `/var/local/kernel-src/linux-2.6.22.0'
make[3]: *** [all] Error 2

--snip

Would anyone happen to know how to fix this?  Is the "cdfs" project
currently maintained? I had found patches on vdrportal to fix cdfs for
linux-2.6.21, but I cant seem to find anything for this new problem.

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] mplayer & mode for nonstop play

[Stone]

On 7/2/07, Igor <[EMAIL PROTECTED]> wrote:


Hello

I have on my vdr-harddisc several video-files with video-clips.
Is it possible to command to MPlayer-plugin to play these files without
stop - one behind another (By
turns) ?




You might be able to make a playlist for mplayer, although I have never
tried.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] changing default font

[Stone]

> I just explicitly tested this and after a restart VDR did use
> the selected font.
>
> So I'm afraid I can't reproduce what you are experiencing.
>
I experienced the same bug!
It seems related to the loaded plugins.
Disabling these 3 Plugins for me cured the problem:
cpumon
pilotskin
skinelchi



Yes, this does appear to be "plugin" related.  It turns out the "sysinfo"
plugin is the cause of the problem.  Would anyone know how to solve it?  The
sysinfo plugin must be initializing something over...

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] setting tv standard in /dev/video0

[Stone]

On 7/1/07, Stone <[EMAIL PROTECTED]> wrote:




On 7/1/07, VDR User <[EMAIL PROTECTED]> wrote:
>
> Unfortunately I don't have a patch to vdr to handle this but it's
> better then having to install X and all the other unnecessary
> packages...  You can compile and use v4l2-ctl from the current
> mercurial v4l drivers located in the v4l-dvb/v4l2-apps/util dir.
>
> command is:  v4l2-ctl -s ntsc
>
> Tested and works.  v4l2-ctl is meant to be a standalone app.



Thanks for this.  I think the Makefile needs another dependency added to
it:

L../../lib -lqt-mt -lXext -lX11 -lm -lpthread
/usr/bin/ld: cannot find -lv4l2
collect2: ld returned 1 exit status




Sorry, my bad.  I just need to start building one directory higher.  Thanks
again.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] setting tv standard in /dev/video0

[Stone]

On 7/1/07, VDR User <[EMAIL PROTECTED]> wrote:


Unfortunately I don't have a patch to vdr to handle this but it's
better then having to install X and all the other unnecessary
packages...  You can compile and use v4l2-ctl from the current
mercurial v4l drivers located in the v4l-dvb/v4l2-apps/util dir.

command is:  v4l2-ctl -s ntsc

Tested and works.  v4l2-ctl is meant to be a standalone app.




Thanks for this.  I think the Makefile needs another dependency added to it:

L../../lib -lqt-mt -lXext -lX11 -lm -lpthread
/usr/bin/ld: cannot find -lv4l2
collect2: ld returned 1 exit status

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] setting tv standard in /dev/video0

[Stone]

AFAIK:

The TV-out connectors in the dvb-ttpci board output automatically NTSC
if the stream is NTSC. They output automatically PAL when the stream is
PAL.

When there is no stream (channel switch or the like), they output PAL by
default, or NTSC if the tv_standard kernel option is used to select that.

The output from /dev/video0 file is PAL all the time, unless it is
changed by the proper V4L ioctl, which is done by VLC and v4lctl.




This is exactly what I have observed as well.  Is there any way VDR could
perform this V4L ioctl without the need for external applications such as
VLC and v4lctl?

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] setting tv standard in /dev/video0

[Stone]

On 6/30/07, Stone <[EMAIL PROTECTED]> wrote:



> > vdr: [7841] connect from 127.0.0.1, port 49972 - accepted
> > vdr: [7841] grabbing to JPEG 70 384 288
> >
> > Can I hardcode the default resolution from within VDR or the kernel
> driver?
> > Best Regards.
>
> Does it work if you use the v4lctl method?
>
> Are there any FTA NTSC transmissions on Astra 19.2°
> or Eutelsat 13°? I'd like to do some tests...



I have not been able to test the v4lctl method since I do not have X on
the machine. Does v4lctl require xawtv?  I suppose I could try and install X
but I would rather not if possible.  Also, I'm not sure about Astra or
Eutelsat since my dish is in America.





I just went ahead and installed X and xawtv.  It appears the "v4lctl" method
does work and the kernel option does not.  I wonder what the difference is
between the two.

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] setting tv standard in /dev/video0

[Stone]

> vdr: [7841] connect from 127.0.0.1, port 49972 - accepted
> vdr: [7841] grabbing to JPEG 70 384 288
>
> Can I hardcode the default resolution from within VDR or the kernel
driver?
> Best Regards.

Does it work if you use the v4lctl method?

Are there any FTA NTSC transmissions on Astra 19.2°
or Eutelsat 13°? I'd like to do some tests...




I have not been able to test the v4lctl method since I do not have X on the
machine. Does v4lctl require xawtv?  I suppose I could try and install X but
I would rather not if possible.  Also, I'm not sure about Astra or Eutelsat
since my dish is in America.

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] setting tv standard in /dev/video0

[Stone]

Basically there are two ways to select NTSC mode:
- v4lctl setnorm NTSC
- module parameter 'tv_standard' for dvb-ttpci

modinfo dvb-ttpci:
...
parmtype:   tv_standard:int
parm:   tv_standard:TV standard: 0 PAL (default), 1 NTSC
...



When tv_standard=1 is used, why does VDR still startup with these PAL
resolutions:

vdr: [7841] starting plugin: screenshot
vdr: [7841] grabbing to PNM 100 768 576
vdr: [7841] grabbed image to /dev/null

And after I run VLC, I get these new resolutions:

vdr: [7841] connect from 127.0.0.1, port 49972 - accepted
vdr: [7841] grabbing to JPEG 70 384 288

Can I hardcode the default resolution from within VDR or the kernel driver?
Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] changing default font

[Stone]

When I select a different default font for vdr to use (other than San
Serif), and save it to setup.conf, vdr does not use the newly selected
default font upon startup.  It seems vdr keeps defaulting back to the
original default font.  Has anyone noticed this too?

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] updated text2skin for vdr-1.5.3 and enigma?

[Stone]

On 6/19/07, Klaus Schmidinger <[EMAIL PROTECTED]> wrote:


On 06/19/07 06:53, Stone wrote:
>
> For vdr-1.5.4 (fix for removal of FONTDIR):

Why patch VDR/font.[hc] and not just call cFont::CreateFont()
which was introduced in version 1.5.4 for this?




Thanks Klaus.  I should have read the HISTORY better. :)  Attached is a
corrected patch for text2skin that does not require any additional changes
to VDR/font.[ch].

Best Regards.


text2skin-1.1-cvs_ext-0.10-vdr-1.5.4.diff
Description: Binary data
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] updated text2skin for vdr-1.5.3 and enigma?

[Stone]

For vdr-1.5.4 (fix for removal of FONTDIR):

Regards


vdr-1.5.4-t2s.diff
Description: Binary data
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] VDR 1.5.3: UTF-8 vs. ExchangeChars()

[Stone]

On 6/13/07, Pertti Kosunen <[EMAIL PROTECTED]> wrote:


Oleg Roitburd wrote:
> As maintainer of ArVDR ( VDR distribution for Russian user) I would say,
that
> in 1.5 years as we use UTF-8 patch without VFAT part, I havn't heard any
> complaints about this issue.

touch 'foo:bar'

And dir in Windows shows:
13.06.2007  14:24 0 FF4GBY~Q

You can 'del "FF4GBY~Q"' though.




The problem is not being able to share the linux directory over the network
to a windows box, it is trying to open a file with invalid chars.  When a
file contains invalid DOS chars, it will display incorrectly and windows
will not be able to play it.

Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] VDR 1.5.3: UTF-8 vs. ExchangeChars()

[Stone]

On 6/12/07, Klaus Schmidinger <[EMAIL PROTECTED]> wrote:


The function ExchangeChars() in VDR/recording.c converts characters
that can't be used in file names on Windows to "#XX", where XX is
the hex code of the character.

This was simple when VDR only worked with single byte character sets,
but now that it can handle UTF-8 this needs to be changed, too.

Currently it has a list of characters that can be used "as is",
and converts everything else to "#XX". I guess it is better
to convert any "disturbing" characters to "#XX" and leave the
rest untouched. However, this requires that we know exactly
which characters can't be used with Windows.

Does anybody have that kind of information?
Or should this be done completely different?

Note that I don't use this feature myself, so unless there
is some input from others, I won't be changing anything here.




I use this FAT feature so I can mount my linux drive on windows and stream
movies with vdradmin to my windows machine.  I have noticed that VDR might
currently be renaming a little more than is required.  Invalid characters
include:

. " / \ [ ] : ; = ,

http://support.microsoft.com/kb/142982

Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Plugin patches for vdr-1.5.3

[Stone]

On 6/12/07, Stone <[EMAIL PROTECTED]> wrote:


Hi,

Attached is a patch for vdr-1.5.3 and the timeline-1.0.141 plugin.  Please
let me know if this patch is incorrect.  Also, I am currently looking for
patches to fix epgsearch-0.9.22, tvonscreen-0.7.0, and liemikuutio.





Here is also a fix for yaepg and vdr-1.5.3.

Regards.


vdr-1.5.3-core-yaepg.diff
Description: Binary data


yaepg-0.0.2.1-vdr-1.5.3.diff
Description: Binary data
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] Plugin patches for vdr-1.5.3

[Stone]

Hi,

Attached is a patch for vdr-1.5.3 and the timeline-1.0.141 plugin.  Please
let me know if this patch is incorrect.  Also, I am currently looking for
patches to fix epgsearch-0.9.22, tvonscreen-0.7.0, and liemikuutio.


timeline-1.0.141-vdr-1.5.3.diff
Description: Binary data
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] updated text2skin for vdr-1.5.3 and enigma?

[Stone]

On 6/10/07, Stone <[EMAIL PROTECTED]> wrote:


Hello,

I am currently using vdr-text2skin-1.1-cvs_ext-0.10.tgz with
Enigma-0.4pre9 from vdrportal.  Is there an updated version of text2skin
for vdr-1.5.3 (or perhaps even better, a patch against current text2skin
cvs)?





Answering my own question, here is a patch to fix
vdr-text2skin-1.1-cvs_ext-0.10 for use with vdr-1.5.3 and Enigma-0.4pre9.
Please let me know if you spot any problems.
Regards.


vdr-1.5.3-t2s.diff
Description: Binary data


text2skin-1.1-cvs_ext-0.10-vdr-1.5.3.diff
Description: Binary data
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] updated text2skin for vdr-1.5.3 and enigma?

[Stone]

Hello,

I am currently using vdr-text2skin-1.1-cvs_ext-0.10.tgz with
Enigma-0.4pre9from vdrportal.  Is there an updated version of
text2skin for
vdr-1.5.3 (or perhaps even better, a patch against current text2skin cvs)?

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] VDRAdmin behind Apache2

[Stone]

I'm using apache2.2 as shipped with Debian/etch and have the following
in my config:

   ProxyRequests Off
   
   Order deny,allow
   Allow from all
   

   ProxyPass / http://localhost:40404/
   ProxyPassReverse / http://localhost:40404/




Thanks for the help.  I just realized that I am using mod-auth-security on
my apache2 server and it appears the following line in my apache2.conf is
the problem:

# Prevent XSS atacks (HTML/Javascript injection)
SecFilter "<(.|n)+>"

After commenting out this filter, it all seems to work now.

Thanks.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] VDRAdmin behind Apache2

[Stone]

Hi,

   I am using VDRAdmin 3.5.3 behind Apache2 over HTTPS.  Everything seems
to work fine, but when I try to edit a timer, I get an error stating "method
not allowed".  Has anyone seen this problem?  It does not happen if I use
VDRAdmin from the localhost on the default port.  Also, as of now, when
connecting to VDRAdmin through apache2, I can create "one-shot" timers, but
not recurring timers.  If this was a permission issue, I would think that I
would not be able to create any timers at all.

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] setting tv standard in /dev/video0

[Stone]

But, this seems to make no difference when VDRAdmin tells VDR to "grab"
the picture.




To summarize, when I stream /dev/video0 with VLC, it seems like VLC's v4l
module is setting the resolution in the driver to something other than PAL
because now for the first time ever, I can use VDR's grab command with a FF
card, in NTSC mode, and not have the picture look like the horizontal is all
offset. The image does not have horizontal lines in it now.  This has always
been a problem with FF cards, NTSC, and VDR's grab command.

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] setting tv standard in /dev/video0

[Stone]

On 6/7/07, Oliver Endriss <[EMAIL PROTECTED]> wrote:


Stone wrote:
> Hi,
>
> I am currently using VDR with a Nexus-S FF card in an NTSC environment.
For
> a long time, I could never get the correct tv standard (NTSC) while
trying
> to watch television via VDRAdmin. I recently noticed that once I stream
VDR
> using VLC and its v4l interface, something in /dev/video0 gets set to
NTSC,
> because from then on, the video is correctly set to NTSC mode and I can
> watch television via the VDRAdmin television interface.

Basically there are two ways to select NTSC mode:
- v4lctl setnorm NTSC
- module parameter 'tv_standard' for dvb-ttpci

modinfo dvb-ttpci:
...
parmtype:   tv_standard:int
parm:   tv_standard:TV standard: 0 PAL (default), 1 NTSC



Yes, I use the tv_standard option when modprobing the drivers as follows:

alias /dev/dvb/* /dev/dvb
alias char-major-212-* dvb-ttpci
options dvb-core dvb_shutdown_timeout=0
options dvb-ttpci tv_standard=1

But, this seems to make no difference when VDRAdmin tells VDR to "grab" the
picture.  Basically VDRAdmin uses VDR's SVDRP interface to "grab" a frame
and send it over http.  Prior to streaming VDR with VLC, VDR's grab still
gets the frames in PAL mode for some reason.  VLC's v4l module is doing
something in addition to switching the driver in NTSC mode with modprobe
options.  Also, this is only a problem with FF ttpci cards.

Best Regards.

R
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] setting tv standard in /dev/video0

[Stone]

Hi,

I am currently using VDR with a Nexus-S FF card in an NTSC environment. For
a long time, I could never get the correct tv standard (NTSC) while trying
to watch television via VDRAdmin. I recently noticed that once I stream VDR
using VLC and its v4l interface, something in /dev/video0 gets set to NTSC,
because from then on, the video is correctly set to NTSC mode and I can
watch television via the VDRAdmin television interface.  Here is the VLC
command I'm using:

vlc -vvv v4l:/dev/video0:adev=/dev/dsp:audio=1:norm=ntsc:size=352x240 --sout
'#transcode{vcodec=DIV3,vb=64,acodec=mp3,ab=48,deinterlace}:std{access=http,mux=asf,dst=:6789}'

Notice how VLC is directly interacting with the video from /dev/video0 (this
method only works with FF cards).  Somehow, the v4l interface from VLC is
setting the tv standard properly for /dev/video0 and fixing VDRAdmin for
NTSC.  Anyone have an idea whats going on? The firmware is set to NTSC as
soon as the card tunes to a NTSC channel.  Why would /dev/video0 not be set
to NTSC until I stream it with VLC?

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [ANNOUNCE] VDR sync early patch

[Stone]

 >
> the motivation for this patch was to speed up zapping channels when
> using vdr-xine, i. e. to shorten the time from pressing the remote
> button till audio and video appear.
>
> FF card users may only see the effect of this patch when the FF card is
> running in transfer mode.
>



Could this patch cause problems if vdr triggers a retune some time after the
initial channel change?  Perhaps this has to do with what UpdateChannels is
set to at the time.

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] what are section filters?

[Stone]

On 5/26/07, Clemens Kirchgatterer <[EMAIL PROTECTED]> wrote:


hi.

since i get many lines of

read incomplete section - len = 1127, r = 334

when my machine is recording and under heavy CPU load, i was curios what
this means. i had a look at the vdr source and saw that there is nearly
no code to recover from short reads from the corresponding
filedescriptor. my guess is, that this data is not important enougth to
be handled more carfully. but what is it for? i searched the web for
EIT DVB section filters a.s.o. but couldn't find any useful
information. can anybody give me some hints or point me in the right
direction regarding section filters?




I'm no expert on section filters, but there is definitely a difference
between the ability to properly parse them and the type of dvb card you
have.  It seems that full featured cards are much more limited in this
aspect.

Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [ANNOUNCE] Cut-a-Lot 0.0.3

[Stone]

So you may want to use uint64_t.




Thanks again.  This works:


--- cutalot-0.0.3/cal-mpeg.h.orig   2007-05-18 06:20:53.0 -0700
+++ cutalot-0.0.3/cal-mpeg.h2007-05-18 06:22:08.0 -0700
@@ -8,7 +8,7 @@

#include 

-typedef uint64 pts_t;
+typedef uint64_t pts_t;

#define MAX_PTS 8589934591LL
#define NO_PTS  8589934592LL
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [ANNOUNCE] Cut-a-Lot 0.0.3

[Stone]

On 5/18/07, Stone <[EMAIL PROTECTED]> wrote:



>
> If you take 30 frames per sec for NTSC-recordings, you will have 1 / 30
> *
> 9 = 3000 PTS-ticks. So you should try 3005 for the PTS-threshold. Am
> I
> right, that you talk about the gap finder? Please let me know, if that
> threshold worked.



Thank you.  Yes, the gap finder is what I am interested in. Previously, if
i had several cuts in some recordings, the PTS would become desynced in the
final cut and Vdrsync would no longer be able to demux the recordings
without having to drop many frames.





Sorry, I forgot to ask one more thing.  Do you have a patch for vdr-1.5.x?

ccache g++-3.4 -g -O2 -Wall -Woverloaded-virtual -fPIC -c -D_GNU_SOURCE
-DPLUGIN_NAME_I18N='"cutalot"' -I/usr/src/DVB/linux/include
-I../../../include cutalot.c
ccache g++-3.4 -g -O2 -Wall -Woverloaded-virtual -fPIC -c -D_GNU_SOURCE
-DPLUGIN_NAME_I18N='"cutalot"' -I/usr/src/DVB/linux/include
-I../../../include cal-cutter.c
In file included from cal-cutter.c:11:
cal-mpeg.h:11: error: `uint64' does not name a type
cal-mpeg.h:35: error: `pts_t' does not name a type
cal-mpeg.h:36: error: `pts_t' does not name a type
cal-mpeg.h:38: error: `pts_t' has not been declared
cal-mpeg.h:38: error: ISO C++ forbids declaration of `Pts' with no type
cal-mpeg.h:44: error: `pts_t' was not declared in this scope
cal-mpeg.h:44: error: expected primary-expression before "bool"
cal-mpeg.h:45: error: `pts_t' was not declared in this scope
cal-mpeg.h:45: error: expected primary-expression before "bool"
cal-cutter.c: In member function `virtual void cCalCuttingThread::Action()':
cal-cutter.c:184: error: `pts_t' was not declared in this scope
cal-cutter.c:184: error: expected `;' before "iFramePts"
cal-cutter.c:221: error: `iFramePts' was not declared in this scope
cal-cutter.c:221: error: 'class cCalPES' has no member named 'GetPTS'
cal-cutter.c:222: error: `newIFramePts' was not declared in this scope
cal-cutter.c:222: warning: unused variable 'newIFramePts'
cal-cutter.c:223: error: `newIFramePts' was not declared in this scope
cal-cutter.c:231: error: 'class cCalPES' has no member named 'GetPTS'
cal-cutter.c:231: error: `iFramePts' was not declared in this scope
cal-cutter.c:234: error: `newIFramePts' was not declared in this scope
cal-cutter.c:237: error: `newPts' was not declared in this scope
cal-cutter.c:237: warning: unused variable 'newPts'
cal-cutter.c:239: error: `newPts' was not declared in this scope
cal-cutter.c:239: warning: unused variable 'newPts'
cal-cutter.c:241: error: `newPts' was not declared in this scope
cal-cutter.c:241: warning: unused variable 'newPts'
cal-cutter.c:244: error: `newPts' was not declared in this scope
cal-cutter.c:231: warning: unused variable 'iFramePts'
cal-cutter.c:244: warning: unused variable 'newPts'
cal-cutter.c:184: warning: unused variable 'pts_t'
make[1]: *** [cal-cutter.o] Error 1


Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [ANNOUNCE] Cut-a-Lot 0.0.3

[Stone]

If you take 30 frames per sec for NTSC-recordings, you will have 1 / 30 *
9 = 3000 PTS-ticks. So you should try 3005 for the PTS-threshold. Am I
right, that you talk about the gap finder? Please let me know, if that
threshold worked.




Thank you.  Yes, the gap finder is what I am interested in. Previously, if i
had several cuts in some recordings, the PTS would become desynced in the
final cut and Vdrsync would no longer be able to demux the recordings
without having to drop many frames.

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [ANNOUNCE] Cut-a-Lot 0.0.3

[Stone]

On 5/17/07, Marius Heidenstecker <[EMAIL PROTECTED]> wrote:


Hi everybody,

I'm pleased to announce version 0.0.3 of my cut-a-lot-plugin.




I really like the idea behind this.  Can you tell me what the recommended
PTS threshhold should be for NTSC recordings? It seems like this will only
work with PAL.

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Bug/SegFault in vdr-1.4.6

[Stone]

Very, very strange.  The problem certainly exists using vdr-1.5.2,
mplayer-nogui 1:1.0-rc1svn20070501-0.1, mp3/mplayer plugin version
0.9.15, and mplayer.sh version 0.8.7..  The problem has always existed
here and I've used every version of all those starting nearly 4 years
ago.  Patrick's explanation makes sense to me and I don't see how the
problem could be resolved otherwise...?




I also have a single FF card setup and know about the problem you speak of
with mplayer causing VDR to crash when a timers goes off while mplayer is in
use.  Could you try building current svn of mplayer with current HG dvb
drivers and let us know if you still have the problem?  This problem seems
to have disappeared for me after updating mplayer a few weeks ago.  It is
not reproducable for me every time.. only sometimes.

Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [PATCH] dynamically sized ringbuffers v2

[Stone]

On 5/10/07, Artur Skawina <[EMAIL PROTECTED]> wrote:


Auto sized ringbuffers, changes since v1:

- increased maximum sizes for a few rb users. Most of the time just a
small part will be used, but there will be more room for times when
more is required.
- a little smarter cRingBufferLinear::Read(), handles the TS buffer
better.
- faster buffer growth. Also makes it less likely that there won't be
an opportunity to resize before an overflow.
- a potentially sleeping cRecorder:Receive(). Mostly to find out how
much more buffer/time would have been needed, ie debugging.
- more verbose logging.

It still wouldn't surprise me if this version caused a few overflows,
but hopefully these will be very rare.




I'm curious how streamdev will function with these buffer changes.

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] backports from 1.4.6-1 to dev

[Stone]

I want to first implement something

really new before releasing a new dev version.




Now thats a teaser! Any hints? :)
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] backports from 1.4.6-1 to dev

[Stone]

Hi,

Klaus, I wasnt sure if you were going to release another version of 1.5.x,
so I just wanted to toss these out there for testing.  The NIT fixes in
vdr-1.4.6-1 are not attached to this mail because they have already been
posted to the list.

Best Regards
--- vdr-1.5.2/dvbplayer.c.orig	2007-05-01 05:03:13.0 -0700
+++ vdr-1.5.2/dvbplayer.c	2007-05-01 05:05:40.0 -0700
@@ -617,8 +617,10 @@
bool TimeShiftMode = index->IsStillRecording();
int Index = index->GetNextIFrame(readIndex, playDir == pdForward, &FileNumber, &FileOffset, &Length, TimeShiftMode);
if (Index >= 0) {
-  if (!NextFile(FileNumber, FileOffset))
+  if (!NextFile(FileNumber, FileOffset)) {
+ readIndex = Index;
  continue;
+ }
   Length += IPACKS; // fixIFrame needs next video packet
   }
else {
--- vdr-1.5.2/vdr.c.orig	2007-05-01 05:07:23.0 -0700
+++ vdr-1.5.2/vdr.c	2007-05-01 05:09:00.0 -0700
@@ -965,7 +965,7 @@
   case kChanDn:
if (!Interact)
   Menu = new cDisplayChannel(NORMALKEY(key));
-   else if (cDisplayChannel::IsOpen()) {
+   else if (cDisplayChannel::IsOpen() || cControl::Control()) {
   Interact->ProcessKey(key);
   continue;
   }
--- vdr-1.5.2/ci.c.orig	2007-05-01 05:00:23.0 -0700
+++ vdr-1.5.2/ci.c	2007-05-01 05:01:44.0 -0700
@@ -643,7 +643,7 @@
 
 // --- cCiConditionalAccessSupport ---
 
-#define MAXCASYSTEMIDS 16
+#define MAXCASYSTEMIDS 64 
 
 // CA Enable Ids:
 
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [Announce] epgsearch-0.9.21

[Stone]

By setup, one can add up to 4 additional times to extend the green
button, e.g. 'afternoon', 'prime time', 'late night'. Times, that are
already passed, are skipped (you will not get 'afternoon' at evening)
with the exception that a time will be displayed for the next day, if it
is less then 20h in the future.


Are you sure, you get both times if 'use favorites' is disabled? If so,
please give me your setup times and the time when you tested it. Also
the setup of the favorites 'before or after user-def. times' would be
interesting. I just did a quick check and it worked on my setup.




Thanks, Christian.  I understand why it did not display both times now.  It
works as designed.  It was the 20 hours in the future that lost me.

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [Announce] epgsearch-0.9.21

[Stone]

On 4/29/07, Christian Wieninger <[EMAIL PROTECTED]> wrote:


Hi,

here's the next release of epgsearch.




I have two user-defined EPG times setup, but when I enable "favorites", only
the second user-defined time is displayed after the favorites is displayed.
Anyone notice that?

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [PATCH] re-use devices in transfer mode

[Stone]

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
> transponder.



Can this patch also be applied to vdr-1.5.1 with a little manual fixing?
Thanks.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [PATCH] limit streamdev client's ringbuffer timeouts to more sane values

[Stone]

> Is this patch for streamdev a direct result from selecting the new
> "Tickless System (Dynamic Ticks)" option in kernel 2.6.21?  If yes, then

CONFIG_HIGH_RES_TIMERS "High Resolution Timer Support". Whether NO_HZ
makes
a difference I'm not sure, i ran into this w/ both options on.
(launching "nice --15 vdr" w/streamdev+softdevice caused X to become
unresponsive; i had to reset the machine. X was barely usable even with
the
vdr client niced)

> does the new "dynamic" timer effect vdr's performance as well?

After increasing that streamdev 1us usleep I don't see much difference in
vdr (+streamdev+softdevice) performance. Haven't updated to highres timers
on the vdr server yet, but i doubt it will change much. (iirc vdr itself
limits the delays to >=3ms).




I just enabled high res timers on my system and the timer accuracy is much
higher.  The response time is very accurate with this new option enabled.
But, the cpu temp seems to have increased by about 4 degrees.  I have now
enabled the associated option to high res timers (tickless system).  With
tickless enabled, the system seems to be just as responsive as before but
the cpu temp is back to normal.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [PATCH] limit streamdev client's ringbuffer timeouts to more sane values

[Stone]

I tried the 1us -> (1000|1)us sleep approach first, before using the
ringbuffer timeouts -- saw no noticeable difference wrt performance.
10ms timeouts seemed to be enough (it's the resolution of a HZ==100
kernel)
and gave similar interrupt and cs numbers as w/ low-res timers.




Is this patch for streamdev a direct result from selecting the new "Tickless
System (Dynamic Ticks)" option in kernel 2.6.21?  If yes, then does the new
"dynamic" timer effect vdr's performance as well?

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [PATCH] limit streamdev client's ringbuffer timeouts to more sane values

[Stone]

sure, just changing it to 'usleep(1)' works too. Is there a reason to
avoid
the ringbuffer infrastructure?




No reason in particular, I just wanted to test which one worked best with
performance.  Thanks for the patch. :)
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [PATCH] limit streamdev client's ringbuffer timeouts to more sane values

[Stone]

On 4/5/07, Artur Skawina <[EMAIL PROTECTED]> wrote:


Well, the streamdev-client reads data from a ringbuffer and when there
isn't anything
to read it tries to sleep for 1us and loops. This wasn't a problem when
the timer
resolution was in the 1000..1us range (1000..100Hz); the usleep(1)
call slept
for one or more milliseconds.
With the high-res timers in kernel 2.6.21+ usleep(1) is no longer treated
as
usleep(1) and the streamdev client is almost unusable; it uses most of
the cpu
and causes hundreds of thousands context switches per second.
This gets rid of the almost-busy-loop.




How about his approach?

--- streamdev/client/filter.c.orig  2007-04-05 20:45:04.0 -0700
+++ streamdev/client/filter.c   2007-04-05 20:45:44.0 -0700
@@ -135,7 +135,7 @@
   }
   m_RingBuffer->Del(TS_SIZE);
   } else
-   usleep(1);
+   cCondWait::SleepMs(1);
   }
}
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Is GrabImage only for PAL resolution when using FF cards?

[Stone]

On 3/18/07, VDR User <[EMAIL PROTECTED]> wrote:


Grab screenshots are unfortunately screwed up for NTSC.  I asked Klaus
about this a long time ago and he suggested the problem was
driver/firmware related.  When I inquired I was told it's a software
problem.  Rather than continuing to go in cricles I just forgot the
idea of getting a good screenshot.




Grab works perfect for NTSC if I use my FF card with xine in softmode.  It
appears that VDR is just calling the dvb driver and getting the resolution
from that.  Somewhere in the ttpci code, it is hardcoded to PAL... Hmmm
where to find it.  This is only an issue with FF cards in NTSC.

Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] Is GrabImage only for PAL resolution when using FF cards?

[Stone]

I noticed that when the screenshot plugin starts, it grabs a PNM image to
/dev/null, but the resolution is not right.  Fory my system, everything
should be in NTSC resolution.  How is vdr getting 768x576 for the capture
screen resolution?  I would like this to be 720x480 instead.

Mar 18 21:04:26 sid vdr: [4336] starting plugin: screenshot
Mar 18 21:04:26 sid vdr: [4336] grabbing to PNM 100 768 576
Mar 18 21:04:26 sid vdr: [4336] grabbed image to /dev/null


Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] TV Standards option for vdr-1.5.x

[Stone]

You may want to try the attached patch. It determines FramesPerSec by
having a look at the first picture of the recording and falls back to
the FRAMESPERSEC macro otherwise.

The current implementation requires that the recording was taken with
cVideoRepacker enabled. Furthermore it must be MPEG2.

The file marks.vdr still uses FRAMEPERSEC for compatibility. Plugins
like dvd, burn, mp3, mplayer, etc. still use FRAMESPERSEC.

Although this patch is against VDR-1.4.6, it applies with some offset
also against VDR-1.5.1.




Thanks! Im using this patch with vdr-1.5.1 and it has fixed my problems with
the incorrect time of recordings for NTSC.  Before I had hardcoded it to 30,
but this is much more accurate.  Good job.  I think this should be
integrated into vdr along with a switch to set the default tv standard to
25/30.

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] TV Standards option for vdr-1.5.x

[Stone]

On 3/13/07, VDR User <[EMAIL PROTECTED]> wrote:


I think I'll stick to what I said earlier in that support for NTSC should
really be a core feature of VDR.  I have no interest in running a plugin
like this and would rather just stick to patching VDR if Klaus doesn't
intend to address this issue.  :\




That plugin is only beneficial if you have a dual PAL/NTSC environment.  It
does not help with the frames per second calculatons at all.

Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] TV Standards option for vdr-1.5.x

[Stone]

I do appreciate the suggestion and I will take a better look at it.  I was
just trying to conceptually understand whats going on.  All I was trying to
say is that I dont think the plugin can generate valid NTSC values from
invalid PAL settings.  I'll post my results.

Best Regards.




Ok, I have looked at the code and here is what I had to do to make it work.
The OSDHeight value that I need to have for NTSC is 425 (what I am currently
using).  Therefore, I had to reverse the calulation in the videosystem
plugin to make that equivalent to the PAL value.

Pal.height = (425 * 576) / 480 = 510

So, after reversing the my current NTSC patch (except for the FRAMESPERSEC
part), and putting 510 into VDR's OSDHeight, the videosystem plugin
now reads the value of 510 (that is PAL) and converts it to 425 (which is
the correct value I need for NTSC).  That is what I meant when I said I
would have to convert my NTSC settings to PAL so the plugin could read them
and convert it back to NTSC (since the plugin assumes that PAL is the
default).

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] TV Standards option for vdr-1.5.x

[Stone]

This makes absolutely no sense to me.

Why don't you simply grab a plain VDR 1.4.6 without any patches and try
the plugin out? It only takes 3-4 minutes to set it up and you'll see
whether or not it will work correctly.

Using the plugin was only a suggestion for the time being. I thought you
might want to use it until things might be changed in some future
version of VDR. I thought of it as an easy to use option instead of
patching the VDR every time a new version comes out. That's it...



I do appreciate the suggestion and I will take a better look at it.  I was
just trying to conceptually understand whats going on.  All I was trying to
say is that I dont think the plugin can generate valid NTSC values from
invalid PAL settings.  I'll post my results.

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] TV Standards option for vdr-1.5.x

[Stone]

On 3/13/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:


Stone wrote:

> It seems this plugin assumes I am currently using PAL. The plugin takes
> the OSD-Settings from VDR as PAL-settings and calculates the
> corresponding NTSC-settings.  But, my television does not do both PAL
> and NTSC, so if this plugin assumes that I currently have PAL setup
> properly, wouldnt it calculate improper values for NTSC?  I dont
> understand how it can generate proper NTSC values from PAL settings that
> I am not using.

My TV can handle both PAL and NTSC. Nevertheless, the OSD is resized and
everything is displayed correctly when playing NTSC content.

I might be way off here..., but I assume that since all TV-standard
values in VDR are hardcoded to PAL, it is safe to use those values to
calculate the correct OSD size for NTSC material.




It just seems like I would have to translate my NTSC values into PAL, and
then put those PAL  values into VDR so that the plugin will read them as PAL
and translate them back again to NTSC.  Right now they are PAL settings with
NTSC values.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] TV Standards option for vdr-1.5.x

[Stone]

For VDR > 1.4.4 You need a patch to make it compile without errors. This
one can be found here:
http://www.linuxtv.org/pipermail/vdr/2006-December/011336.html
Simply save the: vdr-videosystem-0.0.1-uint64-0001.bin.

Let us know how if it worked and how well.




It seems this plugin assumes I am currently using PAL. The plugin takes the
OSD-Settings from VDR as PAL-settings and calculates the corresponding
NTSC-settings.  But, my television does not do both PAL and NTSC, so if this
plugin assumes that I currently have PAL setup properly, wouldnt it
calculate improper values for NTSC?  I dont understand how it can generate
proper NTSC values from PAL settings that I am not using.

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] TV Standards option for vdr-1.5.x

[Stone]

I never had to patch my VDR to make it play NTSC properly. Have you ever
tried the videosystem plugin? I have been using it for quite some time
and it always worked flawlessly. It can be found here:
http://www.vdr-portal.de/board/thread.php?threadid=43516




VDR will play video fine w/o patching the code. But, the improper framerate
will calculate incorrect times on the video.  Also, the OSD will be sized
differently when 720x480 is used instead of the hardcoded value of 720x576.

Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] TV Standards option for vdr-1.5.x

[Stone]

Hi,

In all the prevous versions of VDR, I have had to patch the FRAMESPERSECOND
and change the rest of the hardcoded PAL values in VDR for my NTSC
television.  Is making this an option in VDR on the TODO list?

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] Understanding how vdr's tuning algo works.

[Stone]

Hello All,

  I am curious how vdr's tuning algorithm, in general, works. With all the
refactoring that has gone on with how vdr tunes, locks, retunes, and
otherwise tries to anticipate various forms of interference, storms, or
other activities that could hinder vdr from performing its job adequitely,
please describe, in pseudocode, how the tuning algorythm actually works.

Some of my questions are:

1) What do all the tuning timers mean? There are some constants in vdr
code,  what are the meanings of each tuning state? (i.e. the switch
statement in dvbdevice.c.
2) Given that we understand what all the timers do, which ones depend on
eachother? What are safe limits for each timer? For example, one timer is
the DVBS_TUNE_TIMEOUT that traditionally is set to 9000 (miliseconds) but at
times it takes my dvb card upwards of 18 seconds to actually tune the
channel (so I might wish to set this to 19000 instead of 9000). What other
timers need to be adjusted if any to account for this?
3) Does vdr care or know anything about a rotor setup where the channel
isn't always present the moment the diseqc commands are sent?
4) There has been some talk in the past about refactoring this process some,
do we think the current approach is the best approach? Does vdr-1.5.x plan
to offer new and improved tuning algos?

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [ANNOUNCE] VDR version 1.4.6 released

[Stone]

On 3/3/07, Klaus Schmidinger <[EMAIL PROTECTED]> wrote:


VDR version 1.4.6 is now available at




Should the APIVERSION be incremented to 1.4.6?

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Handling of temporarily encrypted channels

[Stone]

> Is there an easy way to fix this?

Edit the file dvbdevice.c, insert a line "return true;" at the beginning
of the method cDvbDevice::ProvidesCa.
With this modification you can tune to encoded channels, however you'll
never see a "channel not available", you'll just see a black screen.
This, btw, also solves the problem of channels that declare they're
scrambled when they aren't.




With this modification to dvbdevice.c, I wonder if VDR will still crash
when a timer goes off on a channel and all the sudden it becomes encrypted.
This would normally cause a broken data stream and VDR would do an emergency
exit.

Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] updated slavemode patch for mplayer plugin

[Stone]

After building the latest SVN today of the mplayer source, I noticed that
the slavemode patch from the vdr-mp3-plugin did not apply anymore.  Here is
an attached working version of the patch for current SVN of mplayer.

Best Regards.


mplayer-1.0cvs-slavemode-20070302.1.diff
Description: Binary data
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] playing mp3's over smb (lockup)

[Stone]

On 3/2/07, Halim Sahin <[EMAIL PROTECTED]> wrote:


Hi Stefan,
On Fr, Mär 02, 2007 at 07:56:14 +, Stefan Huelswitt wrote:
> On 02 Mar 2007 Stone <[EMAIL PROTECTED]> wrote:
> >
> > I have noticed that when I mount a samba drive on my vdr box and play
mp3's
> > with vdr from it, vdr will often lockup and require a restart.  But,
the
> > strange thing about this is that this only happens when using the mpeg
> > decoder on the FF card.  If I use vdr-xine as the playback method with
my FF
> > card, then vdr never locks up when playing mp3's over the samba drive.
> > Would there happen to be a buffer that needs to be increased?  The
lockup
> > always occurs when a new mp3 is just about to start.
>
> Which background mode does you use?
> If it's "image", try to use "black".
> There is still some bug in firmware which causes the stillpicture
> ioctl to look up.
>
The backgroundmode was the Problem I reported a few days ago.
If I switch to Livemode everything works nearly ok.
Remember:
If I use backgroundmode black, I cannot navigate back in the playlists
and
the first two seconds were skipped of every track .
In livemode the first two seconds were skipped but nothing of the other
tracks.
This Problem did not exist with the previous firmware.




I'm seeing the same thing you are telling me.  Seems like another firmware
bug.

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] playing mp3's over smb (lockup)

[Stone]

On 3/1/07, Stefan Huelswitt <[EMAIL PROTECTED]> wrote:


On 02 Mar 2007 Stone <[EMAIL PROTECTED]> wrote:
>
> I have noticed that when I mount a samba drive on my vdr box and play
mp3's
> with vdr from it, vdr will often lockup and require a restart.  But, the
> strange thing about this is that this only happens when using the mpeg
> decoder on the FF card.  If I use vdr-xine as the playback method with
my FF
> card, then vdr never locks up when playing mp3's over the samba drive.
> Would there happen to be a buffer that needs to be increased?  The
lockup
> always occurs when a new mp3 is just about to start.

Which background mode does you use?
If it's "image", try to use "black".
There is still some bug in firmware which causes the stillpicture
ioctl to look up.




Thanks for the suggestion. So the problem is within the firmware it seems.
I have been using the "image" option as the background to display the album
art.  Lets see what happens when I turn that off.

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] xine-lib patch help

[Stone]

Yes.



Thanks.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] playing mp3's over smb (lockup)

[Stone]

I have noticed that when I mount a samba drive on my vdr box and play mp3's
with vdr from it, vdr will often lockup and require a restart.  But, the
strange thing about this is that this only happens when using the mpeg
decoder on the FF card.  If I use vdr-xine as the playback method with my FF
card, then vdr never locks up when playing mp3's over the samba drive.
Would there happen to be a buffer that needs to be increased?  The lockup
always occurs when a new mp3 is just about to start.

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] xine-lib patch help

[Stone]

Hi,

I was trying to apply the latest xine patches (that come with xine-0.7.10) to
cvs of xine-lib and I have hit a problem.  The patch is looking for this
line to replace:

-dsputil_mmx.o dsputil_mmx.lo: CFLAGS=`echo @CFLAGS@ | sed -e
's/-funroll-loops//g; s/-O[0-9]/-Os/g'`
+dsputil_mmx.o dsputil_mmx.lo: CFLAGS=$(shell echo @CFLAGS@ | sed -e
's/-funroll-loops//g; s/-O([0-9]|s|$)/-Os /g')

But, now the original line looks like this:

dsputil_mmx.o dsputil_mmx.lo: CFLAGS=$(shell echo @CFLAGS@ | sed -e
's/-funroll-loops//g; s/$$/ -Os/')


Should i just leave it as is now?

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [ANNOUNCE] VDRAdmin-AM v3.5.3

[Stone]

On 1/26/07, Christian Wieninger <[EMAIL PROTECTED]> wrote:


Stone wrote:
> Is epgsearch 0.9.20 available or is there an intermediary patch for
0.9.19?

sorry, not yet. I hope to release it within the next days.




Thanks for the updates.

Has anyone noticed that the "timeline" page in vdradmin does not work with
the new IE7?  Anyone know of a workaround?

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] to record or not

[Stone]

On 2/2/07, martin <[EMAIL PROTECTED]> wrote:


You should have a look at the BigPatch. It has some "switch timer"
included.




It sounds like we can just extract this feature out of the "BigPatch".  Has
anyone tried that?  The entire "BigPatch" sounds a little scary, but I too
would like to try the one feature from it. :)

Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] Enigma-0.4pre9 extension patch available?

[Stone]

Hi,

 I just noticed a new version of the Enigma skin available and wanted to
try it out.  But, when I downloaded the required extension patch for the
text2skin plugin, it turned out to be an older version of text2skin that was
prepatched for Enigma.  I was hoping the Enigma extension patch would be
available separately so I can keep using the latest cvs for the text2skin
plugin.  The prepatched version of text2skin is outdated with the Enigma
extensions download.  Perhaps if I could tell when cvs was checked out, I
could pull out the differences... but I was hoping maybe someone already did
it. :)

Best Regards.

http://brougs78.vdr-developer.org/tmp/Enigma-0.4pre9.tar.bz2
http://brougs78.vdr-developer.org/tmp/vdr-text2skin-1.1-cvs_ext-0.10.tgz
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [ANNOUNCE] VDRAdmin-AM v3.5.3

[Stone]

On 1/26/07, Andreas Mair <[EMAIL PROTECTED]> wrote:


Hi!

The new release is available at http://andreas.vdr-developer.org/en

Have fun,
Andreas


*** HISTORY ***
- Fixed: epgsearch's LSTT/DEFT commands need at least epgsearch v0.9.20.




Is epgsearch 0.9.20 available or is there an intermediary patch for 0.9.19?

Best Regards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] How to avoid "cAudioRepacker" messages ?

[Stone]

On 10/15/06, Gregoire Favre <[EMAIL PROTECTED]> wrote:
Hello,sometimes I got cAudioRepacker messages with xxx bytes while syncing onnext audio frame and I would like to know if I could do something inorder to solve this problem ?You can disable the audio and video Repackers (although I dont know if thats really the recommended fix).
Comment out these two lines in remux.c if you want to try w/o the repacker code:#define TEST_cVideoRepacker#define TEST_cAudioRepacker
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] vdr-1.4.3-2.diff compile problem

[Stone]

On 10/15/06, V Live <[EMAIL PROTECTED]> wrote:
Upon patching vdr-1.4.3-2.diff to vdr-1.4.3-1 I first had to manually  patch the vdr.c part of the patch; it did not patch cleanly. Also it  would not compile unless I added an "}"  on the very last line of  "
vdr.c" file.   
		I didnt have any problems.  I think you didnt reverse one of the intermediary patches first. 
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] 451 Grab image failed v4l problem?

[Stone]

On 9/12/06, Leo Márquez <[EMAIL PROTECTED]> wrote:
Hi again,I have installed the last mercurial v4l version and the grab commandstill not working.Anyone knows what could be the problem?Did you specify enabling the grab function in your vdr startup command? For example:
OPTIONS="-l 3 --grab=/tmp"BR.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] ff as budget?

[Stone]

On 8/30/06, Leo Márquez <[EMAIL PROTECTED]> wrote:
Hi,I'm setting my vdr server. Until now I had a vdr box with one fullfeatured dvb-s card (nexus-s).In my server I don't need any vdr output. Now my new server have this ffcard but I think I have to say to vdr that this card acts as budget.
I don't remember where I read it and don't know how can I do this.Anyone can clear my doubt?You can use the xine plugin with a FF card and it will act as a budget.  This is mainly used for HD and preventing the A/V desync during the playback of recordings.
BR.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [ANNOUNCE] VDR maintenance patch 1.4.1-4

[Stone]

On 8/13/06, Stone <[EMAIL PROTECTED]> wrote:
After updating to maintenance 4, I am getting the following error message when starting vdr:Aug 13 04:28:53 sid vdr: [16474] ERROR: plugin '' called cPlugin::ConfigDirectory(), which is not thread safe!
Am I missing something?  Do all of the plugins have to be modified now to not use "cPlugin::ConfigDirectory"?  What is the alternative call?Sorry, I understand now what the problem is.  One of my plugins was calling cPlugin::ConfigDirectory from the same thread.  
Best Regards
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr