date:20060903

Re: [vdr] lost comment in runvdr script

2006-09-03 Thread Matthias Becker


Ah, sorry. I was a bit too fast.

Regards,
Matthias

Note to myself: Better look twice next time.

2006/9/2, Klaus Schmidinger <[EMAIL PROTECTED]>:

Matthias Becker wrote:
> Hi,
>
> when reorganizing my runvdr I found some lost comment in the file that
> is delivered with vdr 1.4.2. There is still some comment about the
> variable VDRUSR. It says:
>
> # Set the environment variable VDRUSR to the user id you
> # want VDR to run with. If VDRUSR is not set, VDR will run
> # as user 'vdr'.

I'm afraid I can't find this in the 'runvdr' file that comes
with VDR 1.4.2.

Klaus

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



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

[vdr] [ANNOUNCE] vdr-span-0.0.1

2006-09-03 Thread Christian Leuschen


Hello folks,

with my first post on this ML I'm glad to announce a new plugin called 
span.


I have written a plugin that can receive PCM-data from other plugins 
(e.g. mp3ng)

to compute frequency-data and to provide them to other plugins
to display a 'Sp'ectrum 'An'alyzer. It is meant as a kind of middleware 
between
these providers and clients to be as generic as needed to be able to 
implement
the visualisation on all kinds of output-devices (OSD, lcd, graphlcd, 
framebuffer, etc.).


It is available at http://lcr.vdr-developer.org/

There's a thread also at 
http://www.vdr-portal.de/board/thread.php?postid=513343#post513343

providing the latest information.

@Klaus: Is there an obstacle to get all plugins that support some kind 
of service?

s.th like

static cPlugin **CallAllServicePlugins(const char *Id, void *Data = NULL);

that returns a list of all plugins supporting the requested service. I 
would like to
use it to collect the names of all data-providers and all 
visualization-clients.


Kindly yours
Christian Leuschen




Abstract from the plugins's README:

This is a 'Sp'ectrum 'An'alyzer Plugin for the Video Disk Recorder (VDR).

Requirements:

VDR & (lib)fftw3

Description:

A plugin that can receive PCM-data from other plugins (e.g. mp3ng)
to compute frequency-data and to provide them to other plugins
to display a 'Sp'ectrum 'An'alyzer.
It is meant as a kind of middleware between
these providers and clients to be as generic as needed to be able to 
implement
the visualisation on all kinds of output-devices (OSD, lcd, graphlcd, 
framebuffer, etc.).

Sketch of the architecture:
| Data-provider sends PCM-data ---> | SpAn-plugin | >--- 
Visualization-clients
  request the spectrum-data "making s.th. handsome out of 
it" |



Installation:

cd /put/your/path/here/VDR/PLUGINS/src
tar -xzf /put/your/path/here/vdr-span-X.Y.Z.tar.bz2
ln -s span-X.Y.Z span
cd /put/your/path/here/VDR
make
make plugins
./vdr -P span


Setup:

Activate spectrum analyzer?yes/no
De-(Activates) the plugin.
yes: The plugin receives data (only if clients also request data) and
on request hands the results over to clients.
no: In this case all data provider- and visualization-plugins are
rejected when trying to hand over data or to request results.

Use logarithmic diagramyes/no
A (yet naive) try to equalize the heights of the bars a bit.
Lower frequencies are prevailing which results in an "high dynamic
range of the heights of the bars" (= mostly few extremely high bars on
the left, further right more decreasing or even no bars at all).
yes: Suspends a "no" at "Use pure (unequalized) data". Scaling of the 
heights

of the bars is done logarithmically.
no: No logarithmic scaling is done.
Tips to improve this way of equalizing are warmly welcome!

Hide mainmenu entryyes/no
Should be self-explanatory.
At the moment there is no use of displaying the plugin's entry in the
main menu. See ToDo (way below) for the reason.

Use pure (unequalized) datayes/no
yes: Really compute the pure data without equalizing anyhow.
no: Values of higher frequencies are emphasized resulting in a "bit 
nicer way

of displaying the frequencies" than with pure data.


Notes:
- Tested on VDR-1.4.0 with a FF-DVB-s 2MB (CPU = PIII 1,2GHz) with 
mp3ng-plugin

as self-made data provider as well as visualization-client.
Additionally the lcdproc-plugin was used as visualization-client,
but just as a proof-of-concept. Thus, there were two clients
active simultaneously.
- I would be very glad if the authors of plugins for rendering 
vdr-information
on (external) displays (graphlcd/graphtft/lcdproc/etc.) or the OSD 
(mp3(ng)/

cdda/radio?/muggle?) used the data provided by this plugin to visualize
a spectrum analyzer.


Generic example how to use it:
// Please see the "real" README for the "HowTo".

TODO:
- Test the stuff with cdda-plugin (provider) and graphlcd-plugin 
(visualization)

- Test it on my streaming-client (it's a PIII 450MHz with DXR3 now)
- Implement the output of the names of all data-source- and 
visualization-plugins on

selecting the mainmenu's entry.
A change in the "Plugin-Service-Protocol" could be neccessary to 
support getting ALL

plugins that can handle a service.
- Implement bar-peaks and their fall off


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

Re: [vdr] [ANNOUNCE] vdr-span-0.0.1

2006-09-03 Thread Klaus Schmidinger


Christian Leuschen wrote:

...
@Klaus: Is there an obstacle to get all plugins that support some kind 
of service?

s.th like

static cPlugin **CallAllServicePlugins(const char *Id, void *Data = NULL);

that returns a list of all plugins supporting the requested service. I 
would like to
use it to collect the names of all data-providers and all 
visualization-clients.


You can use cPluginManager::GetPlugin(int Index) to loop through
all plugins, and call each plugin's Service() function without
a 'Data' pointer. If the call returns 'true', the service is supported.

Klaus

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

Re: [vdr] ttxtsubs question

2006-09-03 Thread Luca Olivetti

En/na Jukka Palko ha escrit:
> Now that I've gotten my system running smoothly with my cable
> channels, I have a short question about ttxtsubs.
> 
> Looks like the subtitles get shown when viewing a channel that sends
> them, but they don't either get stored onto the recordings or they
> don't get decoded out on playback.

Both things are working here, but then I have to say that I'm not
keeping up with Rolf's patches and I'm still using a very old one.

The patches I'm using are available at
http://www.ventoso.org/luca/vdr/patches/
specifically for ttxtsubs I'm using
ttxtsubs-0.0.5-patch.gz (to ttxtsubs itself) and
vdr-1.3.39-subtitles-0.3.8-and-ttxtsubs-0.0.5.diff.gz (for vdr).
Additionally I use vdr-1.3.39-fixmenuinrecording.patch to access the
menu during a recording if ttxtsubtitles are active.

Bye

-- 
- Yo también quiero una Europa libre de Patentes de Software  -
- I want a Software Patents Free Europe too! And you? -
---
  EuropeSwPatentFree - http://EuropeSwPatentFree.hispalinux.es



signature.asc
Description: OpenPGP digital signature
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] ttxtsubs question

2006-09-03 Thread Jukka Palko

On 03/09/06, Luca Olivetti <[EMAIL PROTECTED]> wrote:

En/na Jukka Palko ha escrit:
> Now that I've gotten my system running smoothly with my cable
> channels, I have a short question about ttxtsubs.
>
> Looks like the subtitles get shown when viewing a channel that sends
> them, but they don't either get stored onto the recordings or they
> don't get decoded out on playback.

Both things are working here, but then I have to say that I'm not
keeping up with Rolf's patches and I'm still using a very old one.

Gentoo patch seems to be a custom one available here:
http://dev.gentoo.org/~zzam/distfiles/gentoo-vdr-patchset-1.4.1-2.tar.bz2

The patches applied to my install are:
010-vdr-1.4.1-add-svdrp-down-0.1.diff
020-vdr-1.4.1-prepare-collisions.diff
030-vdr-1.4.1-1.diff
040-vdr-1.4.1-continue-plugin-failed.diff
220-vdr-1.4.1-subtitles-0.4.0-and-ttxtsubs-0.0.5.diff
240-vdr-1.4.1-SetGroupSep.diff
250-vdr-1.4.1-4channelscan.diff

The plugin used is vdr-ttxtsubs-0.0.5 and it gets the patch
vdr-ttxtsubs-0.0.5-directors-cut.diff.gz available at e.g
ftp://trumpetti.atm.tut.fi/gentoo/distfiles/vdr-ttxtsubs-0.0.5-directors-cut.diff.gz.

The patches I'm using are available at
http://www.ventoso.org/luca/vdr/patches/
specifically for ttxtsubs I'm using
ttxtsubs-0.0.5-patch.gz (to ttxtsubs itself) and
vdr-1.3.39-subtitles-0.3.8-and-ttxtsubs-0.0.5.diff.gz (for vdr).
Additionally I use vdr-1.3.39-fixmenuinrecording.patch to access the
menu during a recording if ttxtsubtitles are active.

Bye

--
- Yo también quiero una Europa libre de Patentes de Software  -
- I want a Software Patents Free Europe too! And you? -
---
  EuropeSwPatentFree - http://EuropeSwPatentFree.hispalinux.es

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

--
Jukka Palko[EMAIL PROTECTED]
ICQ: 45463432

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

[vdr] [ANNOUNCE] VDR maintenance patch 1.4.2-1

2006-09-03 Thread Klaus Schmidinger


VDR maintenance patch 1.4.2-1 is now available at

ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.2-1.diff

This is a 'diff' against the official version 1.4.2.


Small fixes to the officially released VDR versions will be first
made available as "maintenance patches" in the Developer directory,
so that they can be reviewed and tested before a new official
release is published.

So please apply the above patch and report whether it works (or
if it causes any new problems).


This version is binary compatible to the previous version, so plugins
don't need to be recompiled.


The changes since version 1.4.2:

- Added LC_ALL to the checks for UTF-8 at startup (suggested by Matthias 
Schwarzott).
- Fixed the cTimer::operator=() so that it won't mess up the cListObject's 
pointers
  (reported by Alexander Rieger).
- Fixed a memory leak in the cTimer::operator=() when using the 'aux' string
  (reported by Alexander Rieger).
- Fixed processing the PDCDescriptor in 'libsi' on big endian systems (thanks to
  Martin Ostermann).
- Fixed handling relative volume settings that unmute the audio in the call to
  cStatus::MsgSetVolume() (reported by Oliver Endriss).

Have fun!

Klaus

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

Re: [vdr] xineliboutput: other rtp clients ?

2006-09-03 Thread syrius . ml

Udo Richter <[EMAIL PROTECTED]> writes:

> I've tried, and was successful with udp://@224.0.1.9:37890

oh yes, i don't know what i did before asking here, but now it's
working.


> This is a multicast transmission, so the IP network will take care of
> connecting the client to the server. No need to specify any local IP
> address.
> You may need to initialize the connection with one of the remote
> clients first. Also, see option Remote Clients-> Transmit always on -
> which seems to be buggy though.

Thanks

-- 

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

[vdr] sofdevice and softplay cvs cleanups

2006-09-03 Thread C.Y.M

I have been trying to clean up my builds and when updated softdevice and
softplay via cvs, noticed several warning about unused variables. Also, it
appears that softplay does not have the current Makefile fixes required to build
under the latest VDR.

Best Regards,
--- softdevice.cvs/video-shm.c.orig	2006-09-03 04:34:56.0 -0700
+++ softdevice.cvs/video-shm.c	2006-09-03 04:41:00.0 -0700
@@ -285,16 +285,16 @@
 };
 
 void cShmVideoOut::YUV(sPicBuffer *buf) {
-uint8_t *Py=buf->pixel[0]+(buf->edge_height)*buf->stride[0]
-+buf->edge_width;
-uint8_t *Pu=buf->pixel[1]+(buf->edge_height/2)*buf->stride[1]
-+buf->edge_width/2;
-uint8_t *Pv=buf->pixel[2]+(buf->edge_height/2)*buf->stride[2]
-+buf->edge_width/2;
-int Ystride=buf->stride[0];
-int UVstride=buf->stride[1];
-int Width=buf->width;
-int Height=buf->height;
+//uint8_t *Py=buf->pixel[0]+(buf->edge_height)*buf->stride[0]
+//+buf->edge_width;
+//uint8_t *Pu=buf->pixel[1]+(buf->edge_height/2)*buf->stride[1]
+//+buf->edge_width/2;
+//uint8_t *Pv=buf->pixel[2]+(buf->edge_height/2)*buf->stride[2]
+//+buf->edge_width/2;
+//int Ystride=buf->stride[0];
+//int UVstride=buf->stride[1];
+//int Width=buf->width;
+//int Height=buf->height;
   
 if (!ctl->attached) {
 setupStore->shouldSuspend=1;
@@ -354,8 +354,8 @@
 return;
 };
   
-int width= ctl->max_width < Width ? ctl->max_width : Width;
-int height= ctl->max_height < Height ? ctl->max_height : Height;
+//int width= ctl->max_width < Width ? ctl->max_width : Width;
+//int height= ctl->max_height < Height ? ctl->max_height : Height;
 
 ctl->width=fwidth;
 ctl->height=fheight;
--- softdevice.cvs/video-xv.c.orig	2006-09-03 04:35:18.0 -0700
+++ softdevice.cvs/video-xv.c	2006-09-03 04:36:34.0 -0700
@@ -1814,10 +1814,10 @@
 +buf->edge_width/2;
   uint8_t *Pv=buf->pixel[2]+(buf->edge_height/2)*buf->stride[2]
 +buf->edge_width/2;
-  int Ystride=buf->stride[0];
-  int UVstride=buf->stride[1];
-  int Width=buf->width;
-  int Height=buf->height;
+//  int Ystride=buf->stride[0];
+//  int UVstride=buf->stride[1];
+//  int Width=buf->width;
+//  int Height=buf->height;
 
   if ( Py && Pu && Pv ) {
 #if VDRVERSNUM >= 10307
--- softplay.cvs/Makefile.orig	2006-05-19 01:04:59.0 -0700
+++ softplay.cvs/Makefile	2006-05-19 01:05:35.0 -0700
@@ -90,4 +90,4 @@
 	@echo Distribution package created as $(PACKAGE).tgz
 
 clean:
-	@-rm -f $(OBJS) $(DEPFILE) *.so *.tgz core* *~
+	@-rm -f $(OBJS) $(DEPFILE) *.so *.tgz core* *~ getFFmpegLibs
diff -ru softplay/Makefile softplay.cvs/Makefile
--- softplay/Makefile.orig	2006-03-20 12:09:20.0 -0800
+++ softplay/Makefile	2006-04-01 18:22:00.0 -0800
@@ -11,7 +11,7 @@
 
 #LIBFFMPEG=/home/martin/vdr/ffmpeg
 #LIBFFMPEG=/home/martin/vdr/ffmpeg-0.4.9-pre1
-LIBFFMPEG=/usr/local/include/ffmpeg/
+LIBFFMPEG=/usr/include/ffmpeg/
 
 ### The version number of this plugin (taken from the main source file):
 
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] sofdevice and softplay cvs cleanups

2006-09-03 Thread C.Y.M

C.Y.M wrote:
> I have been trying to clean up my builds and when updated softdevice and
> softplay via cvs, noticed several warning about unused variables. Also, it
> appears that softplay does not have the current Makefile fixes required to 
> build
> under the latest VDR.
> 

And this one too..

BR.
diff -ru softplay.cvs.orig/Makefile softplay.cvs/Makefile
--- softplay.cvs.orig/Makefile	2006-04-26 00:29:15.0 -0700
+++ softplay.cvs/Makefile	2006-04-26 00:59:27.0 -0700
@@ -24,7 +24,6 @@
 
 ### The directory environment:
 
-DVBDIR = ../../../../DVB
 VDRDIR = ../../..
 LIBDIR = ../../lib
 TMPDIR = /tmp
@@ -35,7 +34,11 @@
 
 ### The version number of VDR (taken from VDR's "config.h"):
 
-VDRVERSION = $(shell grep 'define VDRVERSION ' $(VDRDIR)/config.h | awk '{ print $$3 }' | sed -e 's/"//g')
+VDRVERSION = $(shell sed -ne '/define VDRVERSION/s/^.*"\(.*\)".*$$/\1/p' $(VDRDIR)/config.h)
+APIVERSION = $(shell sed -ne '/define APIVERSION/s/^.*"\(.*\)".*$$/\1/p' $(VDRDIR)/config.h)
+ifeq ($(strip $(APIVERSION)),)
+   APIVERSION = $(VDRVERSION)
+endif
 
 ### The name of the distribution archive:
 
@@ -44,7 +47,7 @@
 
 ### Includes and Defines (add further entries here):
 
-INCLUDES += -I$(VDRDIR)/include -I$(DVBDIR)/include -I$(LIBFFMPEG) -I$(LIBFFMPEG)/libavformat -I$(LIBFFMPEG)/libavcodec -I$(LIBFFMPEG)/libavutil 
+INCLUDES += -I$(VDRDIR)/include -I$(LIBFFMPEG) -I$(LIBFFMPEG)/libavformat -I$(LIBFFMPEG)/libavcodec -I$(LIBFFMPEG)/libavutil 
 
 DEFINES += -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"$(PLUGIN)"'
 
@@ -79,7 +82,7 @@
 
 libvdr-$(PLUGIN).so: $(OBJS)
 	$(CXX) $(CXXFLAGS) -shared $(OBJS) $(LIBS) -o $@
-	@cp $@ $(LIBDIR)/[EMAIL PROTECTED](VDRVERSION)
+	@cp $@ $(LIBDIR)/[EMAIL PROTECTED](APIVERSION)
 
 dist: clean
 	@-rm -rf $(TMPDIR)/$(ARCHIVE)
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] sofdevice cvs unused variables

2006-09-03 Thread C.Y.M

I have been trying to clean up my builds and when updated softdevice and
softplay via cvs, noticed several warning about unused variables. Also, it
appears that softplay does not have the current Makefile fixes required to build
under the latest VDR.

Best Regards,
--- softdevice.cvs/video-shm.c.orig	2006-09-03 04:34:56.0 -0700
+++ softdevice.cvs/video-shm.c	2006-09-03 04:41:00.0 -0700
@@ -285,16 +285,16 @@
 };
 
 void cShmVideoOut::YUV(sPicBuffer *buf) {
-uint8_t *Py=buf->pixel[0]+(buf->edge_height)*buf->stride[0]
-+buf->edge_width;
-uint8_t *Pu=buf->pixel[1]+(buf->edge_height/2)*buf->stride[1]
-+buf->edge_width/2;
-uint8_t *Pv=buf->pixel[2]+(buf->edge_height/2)*buf->stride[2]
-+buf->edge_width/2;
-int Ystride=buf->stride[0];
-int UVstride=buf->stride[1];
-int Width=buf->width;
-int Height=buf->height;
+//uint8_t *Py=buf->pixel[0]+(buf->edge_height)*buf->stride[0]
+//+buf->edge_width;
+//uint8_t *Pu=buf->pixel[1]+(buf->edge_height/2)*buf->stride[1]
+//+buf->edge_width/2;
+//uint8_t *Pv=buf->pixel[2]+(buf->edge_height/2)*buf->stride[2]
+//+buf->edge_width/2;
+//int Ystride=buf->stride[0];
+//int UVstride=buf->stride[1];
+//int Width=buf->width;
+//int Height=buf->height;
   
 if (!ctl->attached) {
 setupStore->shouldSuspend=1;
@@ -354,8 +354,8 @@
 return;
 };
   
-int width= ctl->max_width < Width ? ctl->max_width : Width;
-int height= ctl->max_height < Height ? ctl->max_height : Height;
+//int width= ctl->max_width < Width ? ctl->max_width : Width;
+//int height= ctl->max_height < Height ? ctl->max_height : Height;
 
 ctl->width=fwidth;
 ctl->height=fheight;
--- softdevice.cvs/video-xv.c.orig	2006-09-03 04:35:18.0 -0700
+++ softdevice.cvs/video-xv.c	2006-09-03 04:36:34.0 -0700
@@ -1814,10 +1814,10 @@
 +buf->edge_width/2;
   uint8_t *Pv=buf->pixel[2]+(buf->edge_height/2)*buf->stride[2]
 +buf->edge_width/2;
-  int Ystride=buf->stride[0];
-  int UVstride=buf->stride[1];
-  int Width=buf->width;
-  int Height=buf->height;
+//  int Ystride=buf->stride[0];
+//  int UVstride=buf->stride[1];
+//  int Width=buf->width;
+//  int Height=buf->height;
 
   if ( Py && Pu && Pv ) {
 #if VDRVERSNUM >= 10307
--- softplay.cvs/Makefile.orig	2006-05-19 01:04:59.0 -0700
+++ softplay.cvs/Makefile	2006-05-19 01:05:35.0 -0700
@@ -90,4 +90,4 @@
 	@echo Distribution package created as $(PACKAGE).tgz
 
 clean:
-	@-rm -f $(OBJS) $(DEPFILE) *.so *.tgz core* *~
+	@-rm -f $(OBJS) $(DEPFILE) *.so *.tgz core* *~ getFFmpegLibs
diff -ru softplay.cvs.orig/Makefile softplay.cvs/Makefile
--- softplay.cvs.orig/Makefile	2006-04-26 00:29:15.0 -0700
+++ softplay.cvs/Makefile	2006-04-26 00:59:27.0 -0700
@@ -24,7 +24,6 @@
 
 ### The directory environment:
 
-DVBDIR = ../../../../DVB
 VDRDIR = ../../..
 LIBDIR = ../../lib
 TMPDIR = /tmp
@@ -35,7 +34,11 @@
 
 ### The version number of VDR (taken from VDR's "config.h"):
 
-VDRVERSION = $(shell grep 'define VDRVERSION ' $(VDRDIR)/config.h | awk '{ print $$3 }' | sed -e 's/"//g')
+VDRVERSION = $(shell sed -ne '/define VDRVERSION/s/^.*"\(.*\)".*$$/\1/p' $(VDRDIR)/config.h)
+APIVERSION = $(shell sed -ne '/define APIVERSION/s/^.*"\(.*\)".*$$/\1/p' $(VDRDIR)/config.h)
+ifeq ($(strip $(APIVERSION)),)
+   APIVERSION = $(VDRVERSION)
+endif
 
 ### The name of the distribution archive:
 
@@ -44,7 +47,7 @@
 
 ### Includes and Defines (add further entries here):
 
-INCLUDES += -I$(VDRDIR)/include -I$(DVBDIR)/include -I$(LIBFFMPEG) -I$(LIBFFMPEG)/libavformat -I$(LIBFFMPEG)/libavcodec -I$(LIBFFMPEG)/libavutil 
+INCLUDES += -I$(VDRDIR)/include -I$(LIBFFMPEG) -I$(LIBFFMPEG)/libavformat -I$(LIBFFMPEG)/libavcodec -I$(LIBFFMPEG)/libavutil 
 
 DEFINES += -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"$(PLUGIN)"'
 
@@ -79,7 +82,7 @@
 
 libvdr-$(PLUGIN).so: $(OBJS)
 	$(CXX) $(CXXFLAGS) -shared $(OBJS) $(LIBS) -o $@
-	@cp $@ $(LIBDIR)/[EMAIL PROTECTED](VDRVERSION)
+	@cp $@ $(LIBDIR)/[EMAIL PROTECTED](APIVERSION)
 
 dist: clean
 	@-rm -rf $(TMPDIR)/$(ARCHIVE)
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Recording stops and starts again

2006-09-03 Thread Jouni Karvo

hi,

Klaus Schmidinger writes:
 > Lauri Tischler wrote:
 > > I seem to remember that there was a patch to prevent stopping and 
 > > starting recording
 > > if audio-pid changes.
 > > Was there ?

<...>

 > ...but the audio pids are set up at 20:50:18, which is 6 (six!)
 > seconds after the show has begun. I'd say you should contact
 > your broadcaster and complain about this. The audio pids should
 > be set up *before* the show starts.

I remember this discussion before.  Back then, from VDR version 1.3.24
the decision was to not to restart recording if the PIDs do not
change, but only the language codes.  It was like that for some
1.3 versions, but shifted quietly back to the old behaviour a bit
later.

The same arguments here...

http://linvdr.org/mailinglists/vdr/2005/04/msg00070.html

And some more:

>From Teemu Rantanen:

 I wouldn't expect them to change in the middle of a movie, but
 some documentaries may have interviews and actual film footage in
 different languages. I haven't yet recorded any that actually
 change languages in the middle of a show, but just wondering if
 there is a limit what you can and what you cannot change...

...and then for VDR 1.3.24 this was implemented.

yours,
Jouni

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

Re: [vdr] lost comment in runvdr script

[vdr] [ANNOUNCE] vdr-span-0.0.1

Re: [vdr] [ANNOUNCE] vdr-span-0.0.1

Re: [vdr] ttxtsubs question

Re: [vdr] ttxtsubs question

[vdr] [ANNOUNCE] VDR maintenance patch 1.4.2-1

Re: [vdr] xineliboutput: other rtp clients ?

[vdr] sofdevice and softplay cvs cleanups

Re: [vdr] sofdevice and softplay cvs cleanups

[vdr] sofdevice cvs unused variables

Re: [vdr] Recording stops and starts again

11 matches

Site Navigation

Mail list logo

Footer information