Re: [vdr] lirc-0.8.6 moved socket to /var/run/lirc/lircd
On Dienstag, 29. September 2009, Helmut Auer wrote: > > Hi list! > > > > lirc starting from version 0.8.6, does use the socket /var/run/lirc/lircd > > instead of /dev/lircd, so all apps not using liblirc_client need to be > > changed. Else IR will not work in VDR. > > > > There are two possibilities: > > 1. Shell code to check which of the two sockets do exist and adding > > relevant command-line-parameter to vdr (--lirc=/var/run/lirc/lircd). > > 2. Patching VDR to check both pathes and using the existing one. > > 3. Change lirc to use /dev/lircd > In gen2vdr ( =gentoo ) I set: > LIRCD_OPTS="-o /dev/lircd" > > in /etc/conf.d/lircd :) Nice to know that it can be changed, but I have a big BUT: Does irw and all other apps using liblirc_client then still work? I doubt, as they have the new name compiled in. And btw. I support the rename, as sockets should not be placed in /dev. Regards Matthias ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] lirc-0.8.6 moved socket to /var/run/lirc/lircd
Hi list! lirc starting from version 0.8.6, does use the socket /var/run/lirc/lircd instead of /dev/lircd, so all apps not using liblirc_client need to be changed. Else IR will not work in VDR. There are two possibilities: 1. Shell code to check which of the two sockets do exist and adding relevant command-line-parameter to vdr (--lirc=/var/run/lirc/lircd). 2. Patching VDR to check both pathes and using the existing one. Regards Matthias ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.9
On Sonntag, 23. August 2009, Goga777 wrote: > > Your headers seem broken. What should happen (i.e. in upstream kernel > > git) is: > > let's have a look on my headers (debian sid kernel 2.6.30 s2-liplianin dvb) Did you look in /usr/include/linux/dvb/... or in /usr/src/linux/... ? For compiling userspace stuff (which vdr for sure is), the versions in /usr/include are used. Regards Matthias ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] small patch to compil vdr-1.7.8 with gcc-4.4.0
On Dienstag, 14. Juli 2009, Gregoire Favre wrote:
> Hello,
>
> today I (finally...) took some time to compil the "new" VDR but it
> failed, with this change it compil :
>
> --- recording.c~ 2009-07-13 21:45:05.0 +0200
> +++ recording.c 2009-07-13 21:51:51.0 +0200
> @@ -1217,7 +1217,8 @@
>if (recording) {
> cThreadLock DeletedRecordingsLock(&DeletedRecordings);
> Del(recording, false);
> - char *ext = strrchr(recording->FileName(), '.');
> + //char *ext = strrchr(recording->FileName(), '.');
> + char *ext = strrchr(const_cast(recording->FileName()), '.');
> if (ext) {
> strncpy(ext, DELEXT, strlen(ext));
> recording->fileSizeMB = DirSizeMB(recording->FileName());
>
> Sorry if I missed something already posted for vdr-1.7.8 here and have a
> great day,
Well, but why not having a look at the other gcc-4.4 patches for different
vdr-versions, and just use the not const recording->fileName member?
This can be done, as cRecordings is a friend of cRecording.
- char *ext = strrchr(recording->FileName(), '.');
+ char *ext = strrchr(recording->fileName, '.');
Regards
Matthias
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] What about vdr-1.6.1?
On Samstag, 27. Juni 2009, Udo Richter wrote: > On 25.06.2009 21:55, Ville Skyttä wrote: > >> Hmmm, this could also be a great opportunity: Why not nominate someone > >> as the official maintainer of the 1.6 stable branch? Someone who > >> collects or back-ports fixes and smaller enhancements to the 1.6 branch, > >> and does minor releases based on community feedback? > > > > Yes, please! Udo, are you volunteering? ;) > > Thanks for the confidence in me, but actually, I would prefer not to. > > I already don't have enough spare time to keep up with my existing > projects. And I wanted to focus on moving towards 1.7.x, which is not > feature-complete from my point of view now. > > This doesn't mean that I wouldn't help out in keeping 1.6.x up to date. > But I simply cannot promise to have the necessary time. > > 1.6.x stable should be maintained by someone who really uses it in the > future, to keep an eye on stability, and who has at least the time to > keep tings from stalling for months. > Well, I am not keen on doing this, but to get some progress I at least did upload my git tree based on vdr-1.6.0-2 version of git://vdr.gekrumbel.de/vdr.git to github: http://github.com/zzam/vdr/tree/stable git://github.com/zzam/vdr.git Branch "stable" It contains up to now only my three patches I already posted in this thread. Regards Matthias ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] What about vdr-1.6.1?
On Dienstag, 16. Juni 2009, VDR User wrote: > The patch vdr-dvb-api-5-is-fine.diff is not a proper "fix" iirc. Ok, so where is the problem, and how should a proper fix look like? Regards Matthias ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] What about vdr-1.6.1?
On Dienstag, 16. Juni 2009, Joachim Welker wrote:
> Hi Klaus,
> I see you are very busy in developing the new vdr-1.7.* (thanks for your
> great work !). But what about stable vdr-1.6.0? You released two patches
> which should result in version vdr-1.6.1. AFAIR there were no complaints
> about these patches, so I think it's save to release vdr-1.6.1 in order to
> rule off the last stable version.
>
Well, if the goal is to release a vdr-1.6.1 version,
I suggest to first collect further patches needed to compile it on recent
systems:
* compiling with gcc-4.4 and glibc-2.10: fixing some variable const issues and
some other warnings
* compiling against linux-headers with s2api (api version 5)
The gentoo versions of these patches are attached.
The gcc-4.4 patch is based on Ludwig Nussels version plus improvments of
Klaus. The last const_cast is replaced by using the fileName member of
cRecording as cRecordings is a friend class.
I don't know if more fixes are floating around that need to be applied.
Regards
Matthias
diff --git a/recording.c b/recording.c
--- a/recording.c
+++ b/recording.c
@@ -509,8 +509,8 @@ cRecording::cRecording(cTimer *Timer, const cEvent *Event)
Utf8Strn0Cpy(SubtitleBuffer, Subtitle, MAX_SUBTITLE_LENGTH);
Subtitle = SubtitleBuffer;
}
- char *macroTITLE = strstr(Timer->File(), TIMERMACRO_TITLE);
- char *macroEPISODE = strstr(Timer->File(), TIMERMACRO_EPISODE);
+ const char *macroTITLE = strstr(Timer->File(), TIMERMACRO_TITLE);
+ const char *macroEPISODE = strstr(Timer->File(), TIMERMACRO_EPISODE);
if (macroTITLE || macroEPISODE) {
name = strdup(Timer->File());
name = strreplace(name, TIMERMACRO_TITLE, Title);
@@ -551,7 +551,7 @@ cRecording::cRecording(const char *FileName)
sortBuffer = NULL;
fileName = strdup(FileName);
FileName += strlen(VideoDirectory) + 1;
- char *p = strrchr(FileName, '/');
+ const char *p = strrchr(FileName, '/');
name = NULL;
info = new cRecordingInfo;
@@ -1022,7 +1022,7 @@ void cRecordings::DelByName(const char *FileName)
if (recording) {
cThreadLock DeletedRecordingsLock(&DeletedRecordings);
Del(recording, false);
- char *ext = strrchr(recording->FileName(), '.');
+ char *ext = strrchr(recording->fileName, '.');
if (ext) {
strncpy(ext, DELEXT, strlen(ext));
recording->fileSizeMB = DirSizeMB(recording->FileName());
diff --git a/svdrp.c b/svdrp.c
--- a/svdrp.c
+++ b/svdrp.c
@@ -736,7 +736,7 @@ void cSVDRP::CmdGRAB(const char *Option)
char *strtok_next;
FileName = strtok_r(p, delim, &strtok_next);
// image type:
- char *Extension = strrchr(FileName, '.');
+ const char *Extension = strrchr(FileName, '.');
if (Extension) {
if (strcasecmp(Extension, ".jpg") == 0 || strcasecmp(Extension, ".jpeg") == 0)
Jpeg = true;
@@ -795,16 +795,17 @@ void cSVDRP::CmdGRAB(const char *Option)
char RealFileName[PATH_MAX];
if (FileName) {
if (grabImageDir) {
- cString s;
- char *slash = strrchr(FileName, '/');
+ cString s(FileName);
+ FileName = s;
+ const char *slash = strrchr(FileName, '/');
if (!slash) {
s = AddDirectory(grabImageDir, FileName);
FileName = s;
}
slash = strrchr(FileName, '/'); // there definitely is one
- *slash = 0;
- char *r = realpath(FileName, RealFileName);
- *slash = '/';
+ cString t(s);
+ t.Truncate(slash - FileName);
+ char *r = realpath(t, RealFileName);
if (!r) {
LOG_ERROR_STR(FileName);
Reply(501, "Invalid file name \"%s\"", FileName);
diff --git a/channels.c b/channels.c
--- a/channels.c
+++ b/channels.c
@@ -574,7 +574,7 @@ void cChannel::SetLinkChannels(cLinkChannels *LinkChannels)
}
else
q += sprintf(q, " none");
- dsyslog(buffer);
+ dsyslog("%s", buffer);
}
void cChannel::SetRefChannel(cChannel *RefChannel)
diff --git a/device.c b/device.c
--- a/device.c
+++ b/device.c
@@ -529,7 +529,7 @@ eVideoSystem cDevice::GetVideoSystem(void)
return vsPAL;
}
-//#define PRINTPIDS(s) { char b[500]; char *q = b; q += sprintf(q, "%d %s ", CardIndex(), s); for (int i = 0; i < MAXPIDHANDLES; i++) q += sprintf(q, " %s%4d %d", i == ptOther ? "* " : "", pidHandles[i].pid, pidHandles[i].used); dsyslog(b); }
+//#define PRINTPIDS(s) { char b[500]; char *q = b; q += sprintf(q, "%d %s ", CardIndex(), s); for (int i = 0; i < MAXPIDHANDLES; i++) q += sprintf(q, " %s%4d %d", i == ptOther ? "* " : "", pidHandles[i].pid, pidHandles[i].used); dsyslog("%s", b); }
#define PRINTPIDS(s)
bool cDevice::HasPid(int Pid) const
diff --git a/pat.c b/pat.c
--- a/pat.c
+++ b/pat.c
@@ -144,7 +144,7 @@ void cCaDescriptors::AddCaDescriptor(SI::CaDescriptor *d, bool Stream)
q += sprintf(q, "CAM: %04X %5d %5d %04X %d -", source, transponder, serviceId, d->getCaType(), Str
Re: [vdr] Can I disable pause live tv altogher?
On Donnerstag, 7. Mai 2009, Frank Scherthan wrote: > Hi Theunis, Hi list, > > Theunis Potgieter schrieb: > > Well honestly I'm confused. I use vdr 1.6 and when I press down or up > > it changes channel only. My vdr never pauses live tv. Mind you I don't > > have a pause key either and neither defined. So perhaps this is the > > way to for him. > > Why didn't you just read the manual? > It is all there! :) It is really great! > > The point is: keys do different things in differnet environments. > > In liveview, the "down"- key decreases channel by 1 > in replay-mode the "down"-key pauses the recording. > > If you define a pause-key, than this key pauses in replay-mode. > In live-view it creates an instant-recording, that is replayed and paused. > > Before anyone posts to this topic, would you please read the manual? > > > I think this whole thread would not exist, if anyone would have read the > manual ;) > > btw. the manual comes with every copy of VDR and can be read via web in > the WIKI: > http://www.linuxtv.org/vdrwiki/index.php/VDR_User's_Manual > Well, I do want the live-pause / instant-recording function, but I can think of a simple way out of this discussion. Why not allow the Pause key to be redefined in keymacros.conf, like the color and User? keys. I have not had a look into the code in vdr.c, but maybe this also requires some non-trivial changes in key processing to stacked event/handler tables with priorities and in such case this is not possible if only needed for this goal. Regards Matthias ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [Fwd: Re: let vdr ignore non vdr directories ?]
On Montag, 20. April 2009, Peter Dittmann wrote: > vdr-boun...@linuxtv.org schrieb am 15.04.2009 08:41:02: > > > vdr is not deleting files it does not know. Its only deleting empty > > > directories in its video directories. > > > > From the VDR/INSTALL file: > > > > Note that you should not copy any non-VDR files into the /videoX > > directories, > > since this might cause a lot of unnecessary disk access when VDR > > cleans up those > > directories and there is a large number of files and/or subdirectories > > in > > > there. > > > > The video directory is VDR's own space, there shall be nothing else > > in there. If the user puts anything non-VDR related into it (even by > > mistake), it's their fault. > > > > Klaus > > A pretty much simplified approach ;-) > > A simple use case: > * standalone settop box with VDR and DVD recording capability > * OS gets a seperate small partition > * /videoX get the big rest > > Now install the usual suspects: > vdr-burn or vdrconvert > > They need a lot of temporary space. > So there are two options: > * blocking ++20GB just for temporary files for burning and greating a > seperate partition > * put the temp files for burning in /videoX ;-) Option 3: Mount your big partition onto /var/vdr (or any other point you choose) and put vdr's video directory into /var/vdr/video, and other vdr-burn temp stuff into /var/vdr/vdr-burn-temp or /var/vdr/temp/burn As I understand it: It is a unix principle to form the directory tree based on logical structure and not on physical disk layout. Regards Matthias ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [Fwd: Re: let vdr ignore non vdr directories ?]
On Mittwoch, 15. April 2009, Steffen Barszus wrote: > Matthias Schwarzott schrieb: > > On Montag, 13. April 2009, Steffen Barszus wrote: > >> Hi all! > > > > Hi! > > > >> is there any way to let vdr ignore any directories which do not belong > >> to it ? > >> > >> What i have seen is that vdr is recursive checking all directories even > >> on second and third video directory. > >> > >> If the logic is that all needs to be in video.0 directory and its > >> subdirectories and symlinks will be required to let vdr find the > >> recordings, it should not check the other video directories. > > > > [deleted some text that did not made sense to me] > > i did a mount --bind /proc proc/ in video.01 resulting in vdr searching > the proc filesystem resulting in plenty of error messages to the log (no > permission etc) which filled up the log, which in turn filled up my root > filesystem with within 15 min or so. > > I have a directory containing a chroot env. not readable by vdr - except > i forgot to unmount the proc in time. > > >> Think there might be others as well that are using the big disks for > >> other space consuming things - nobody else run into this ? > > > > I don't understand why people do put other stuff into vdr video > > directories? If I want to have video directory and a directory containing > > iso images why not do > > > > mkdir video > > mkdir iso > > and put the stuff there? > > That doesn't help. > /dev/hda1 3,4G 1,4G 1,8G 44% / (microdrive which is > containing video.00, with symlinks, index etc) > /dev/sdb1 932G 929G 3,3G 100% /var/lib/video.01 > /dev/sda1 932G 600G 333G 65% /var/lib/video.02 > > bindmount only works properly in newer kernels. Still on 2.6.24. If you > have an idea of how to use the big harddisks for something else without > preallocating space for other tasks (i.e. partitioning), i would be > happy to hear. I'm pretty aware that this might not be good idea to do > things like i did. On the other hand i think what vdr does is a bad idea > and unnecessary. period. > I thought bind mount does work on even older kernels, still shouldn't a symlink work too? So I did setup lvm on my harddisks and made my video partition a logical-volume that can span as many harddisk as I let join the volume group. Still some time ago I had a setup using vdr's own support for multiple disks as you use it. So I suggest you mount your disks somewhere else (like /mnt/large1 /mnt/large2) and then do bind mounts or symlinks from /var/lib # mount /dev/disk1 /mnt/large1 # mount /dev/disk2 /mnt/large2 # mkdir /mnt/large1/video # mkdir /mnt/large1/video # mount --bind /mnt/large1/video /var/lib/video.01 # mount --bind /mnt/large2/video /var/lib/video.02 Regards Matthias ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] let vdr ignore non vdr directories ?
On Montag, 13. April 2009, Steffen Barszus wrote: > Hi all! Hi! > > is there any way to let vdr ignore any directories which do not belong > to it ? > > What i have seen is that vdr is recursive checking all directories even > on second and third video directory. > > If the logic is that all needs to be in video.0 directory and its > subdirectories and symlinks will be required to let vdr find the > recordings, it should not check the other video directories. > [deleted some text that did not made sense to me] > > Think there might be others as well that are using the big disks for > other space consuming things - nobody else run into this ? I don't understand why people do put other stuff into vdr video directories? If I want to have video directory and a directory containing iso images why not do mkdir video mkdir iso and put the stuff there? Still I support the opinion that vdr should not silently delete files it does not know. Regards Matthias ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Unique Timer ID
On Montag, 23. Februar 2009, Matthias Wächter wrote: > Hi, > > just wanted to ask whether someone already thought about the idea to use > unique timer IDs, like autoincrement, for avoiding race conditions > between multiple users or processes adding or removing timers. The > associated renumbering between DELT operations can lead to hitting the > wrong timer. If all timers had unique numbers, the issue would be gone > implicitly, but timers.conf would have to carry the ID requiring a file > layout change. > To me this sounds like a good idea. Even better would be to then properly protect the VDR internal data structures, and finally just allow concurrent access to them. Like multiple svdrp connections etc. Matthias ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] PMT in multiple TS packet bug
On Dienstag, 20. Januar 2009, Klaus Schmidinger wrote: > > VDR uses the (fixed) "pseudo" PMT pid 0x0084, which is 132. > This was taken from some patch that implemented PAT/PMT handling > (don't remember which one it was, maybe it was even the code from > reel multimedia - not sure if I've missed mentioning that in the > CONTRIBUTORS file). > > Anyway, I was already wondering if simply using some fixed PMT > pid was such a good idea. What if some other stream uses exactly > that pid? Apparently this is the case in this example. > > So I guess it will be necessary to first collect all pids and then > check whether the default pseudo PMT pid is still free, and if > not, incresase it until a free one is found... > How about just using the original PMT pid? Matthias ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] OT: local variables limited in size to (8*1024*1024-32*1024) bytes ?
On Samstag, 29. November 2008, Stefan Lucke wrote: > Hi, > Hi Stefan! > the attached program segfaults when using a larger local variable. > > Depending on used value I get segfaulst at different locations. > > //#define BUFSIZE (9*1024*1024-16*1024) // only segfault > #define BUFSIZE (8*1024*1024-16*1024) // hello + segfault > //#define BUFSIZE (8*1024*1024-32*1024) // hello + 2nd line > > When using last definition of BUFSIZE every thing is fine. > I guess linux has some limit on the stack-size. Sounds like 8MB in your case. But why can't you just alloc large data on the heap with malloc as everyone else does? Regards Matthias ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Tuning failures for transponder-locked tuners (VDR 1.4.7)
On Mittwoch, 29. Oktober 2008, Teemu Suikki wrote: > I have a VDR box with three DVB-T tuners.. All cards are > saa7146+tda10045 -based budget cards. > [cut] > > I have tried killing VDR when the tuner is jammed, and then try tuning > with tzap.. Tuning fails for the "already tuned" channel, but if I > simply tune to another transponder and then back, it tunes fine. So > apparently the problem is that VDR doesn't even try re-tuning because > the tuners are "locked" to specific transponders in channels.conf.. 1. So for example using cardX. 2. This card gets tuned to channel C1 by VDR. Once it loses the lock and there is an ongoing recording VDR commits suicide and hopes the problem fixes magically (maybe vdr-launch-script reloads drivers ...) but it does not. 3. You kill VDR and run tzap C1 That also does not lock. But tzap C2 tzap C1 does make it lock. How should VDR know, it need to lock another frequency first to re-get a lock? This clearly is a driver/hw bug. And you can only fix it by modifying the driver. So you best report this to the linuxtv-dvb mailinglist and attach more info: exact used hardware, dmesg logs, ... Regards Matthias ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Improve SVDRP GRAB ...
On Mittwoch, 11. Juni 2008, Herbert Poetzl wrote: > Greetings! > > I would like to 'improve' (or simply extend) > the SVDRP Grab command to allow for grabbing > a picture from a given channel, if possible, > without disturbing normal operations > > basic idea: > > get a device which is capable of tuning > the specified channel (optionally shared > transponder) > > tune to the channel/stream, and wait until > data is available (or some timeout has been > reached) > > grab a screenshot (similar to current grab) > > > now, what I tried so far is the following > (with little success :) > As far as I know, the grab command does grab of the primary device. For a ff card this is done by accessing /dev/video. For what you want you need a different approach - you need to receive some data and run a software mpeg2 decoder over it - then you get a picture without disturbing current operation. Matthias ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-reelchannelscan plugin
On Mittwoch, 7. Mai 2008, lucian orasanu wrote: > Hey. > > 10x for reply and for advices. > > patch is for vdr-reelchannelscan-0.4.1 . > And where is it in a form that can be used without problems? Remember I asked about using diff -r -u. Regards Matthias ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-reelchannelscan plugin.
On Mittwoch, 7. Mai 2008, lucian orasanu wrote: > Hy. > > Attached is an patch for vdr-1.7.0 with h264 and > multiproto support to make plugin work. > > this is my first patch so any sugestions or advices > are welcome. > So here are my suggestions (all formal ones): * Do not rar the file, but just attach it. * use diff -ru This switches to unified diff format which is the one all open source projects (I know of) use. * Tell us what version of reelchannelscan you did modify. Better you even give a download-uri for the original plugin, as there are a lot of different versions/snapshots floating around. Regards Matthias ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] external EPG data & broken encoding (epg4vdr)
On Mittwoch, 16. April 2008, Soeren Sonnenburg wrote: > Dear List, > > I am desperately trying to get the german umlauts going for both vdr > receiving EPG information (out of the air directly from the channels...) > and via epg4vdr 0.5 > http://www.wontorra.net/article.php?story=20050429181815661 > > I've noticed that standard EPG has the correct encoding, but only the > one from epg4vdr has not. However the pulled .xml files still have the > right (i.e. utf-8) encoding. > > Only when this information is transferred to vdr (I guess via SVDRP) > umlauts and everything is distorted. Also then the dumped epgdata file > contains wrongly encoded parts... > > Any ideas what I could do about this? > I guess you need to know the encoding your vdr runs with, and then use this for the SVDRP connection. For future VDR development I still think it could be useful to: 1. Either add a header for epg data (and other places where vdr exchanges texts) telling the encoding. 2. or switch all external interfaces (epg.data, svdrp, channels.conf) to utf8. 3. going even further, switch vdr so that it internally only uses utf8 (or utf16 if one can tell that is easier - I doubt). So all code that does switch/case on the charset can be simplified. Regards Matthias ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] Install headers, add pkgconfig file
On Dienstag, 11. März 2008, clemens kirchgatterer wrote: > On Tue, Mar 11, 2008 at 12:27 AM, Matthias Schwarzott <[EMAIL PROTECTED]> wrote: > > On Montag, 10. März 2008, Ville Skyttä wrote: > > > > So you can install .pc file anywhere you want if you add this location > > to PKG_CONFIG_PATH. > > > > So /usr/bin/pkg-config will always look into /usr/lib/pkgconfig. > > We can either use > > A. $(DESTDIR)/usr/lib/pkgconfig > > or > > B. $(DESTDIR)$(PREFIX)/lib/pkgconfig > > > > For most installations A should be fine. > > definitly B, otherwise it will not work for parallel installs of > different vdr versions in different $PREFIXes. > Ack! BUT: B with default values from Makefile gives /usr/local/lib/pkgconfig that by default is not in pkgconfig search-path. And I wrote: "For most installations ..." Matthias -- Matthias Schwarzott (zzam) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] Install headers, add pkgconfig file
On Montag, 10. März 2008, Ville Skyttä wrote: > Hello, > > As discussed in the freetype/fontconfig pkgconfig thread, here's a combined > patch implementing installation of VDR's headers and generating a pkgconfig > *.pc file. > > This patch is mostly just a discussion draft - I haven't tried installing > the headers and the pkgconfig file isn't installed yet by any "make > install*" (mostly because very ironically, there's no way to query > pkg-config for its default search path, which is something I've intended to > report a bug about since a long time ago, but failed so far - maybe I'll do > it right now :)). > Citing pkg-config manpage: By default, pkg-config looks in the directory prefix/lib/pkgconfig for these files; it will also look in the colon-separated (on Windows, semicolon-separated) list of directories specified by the PKG_CONFIG_PATH environment variable. So you can install .pc file anywhere you want if you add this location to PKG_CONFIG_PATH. So /usr/bin/pkg-config will always look into /usr/lib/pkgconfig. We can either use A. $(DESTDIR)/usr/lib/pkgconfig or B. $(DESTDIR)$(PREFIX)/lib/pkgconfig For most installations A should be fine. Matthias -- Matthias Schwarzott (zzam) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.5.15 and epgsearch-0.9.23
On Mittwoch, 20. Februar 2008, Ville Aakko wrote: > Hi Ludwig and Christian, > > I noticed the betas right after I posted the previous email, and made > a local ebuild for the latest beta (0.9.24.beta19), and it emerges and > runs. Hope the beta doesn't blow up my VDR =) Hi all! I also did an ebuild for that version and added it to the tree. Regards Matthias -- Matthias Schwarzott (zzam) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-sxfe don't start..
On Sonntag, 17. Februar 2008, Ville Skyttä wrote: > On Sunday 17 February 2008, Matthias Schwarzott wrote: > > On Sonntag, 17. Februar 2008, Joerg Bornkessel wrote: > > > We detect this in the vdr-xineliboutput-*.ebuild an let install the > > > xineplug_inp_*.so to the given dir by the headerfile. > > > There is nothing wrong. > > > > > > Jussy, just skip the xine-lib-1.1.10.1 Version, use an older version, > > > or i hope it will fixed by xine team, then the next version. > > > > This is fixed in ebuild vdr-xineliboutput-1.0.0_rc2_p20080120-r1. Now we > > restrict the xine-lib version to 3 components. > > FWIW, I'm pretty certain that the only upstream supported way to retrieve > the dir where to install xine plugins is to use "xine-config --plugindir" > or "pkg-config --variable=plugindir libxine". > Ah, nice to know. Now we use "xine-config --plugindir to get the path. Regards Matthias -- Matthias Schwarzott (zzam) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-sxfe don't start..
On Sonntag, 17. Februar 2008, Joerg Bornkessel wrote: > > Actually problem is bigger.. Gentoo xine-lib-1.1.10.1 don't install (or > > even compile) file xineplug_inp_xvdr.so... > > xine-lib-* will never install xineplug_inp_xvdr.so ;) > this is the part of vdr-xineliboutput > > The problems comes only with/from the xine-lib-1.1.10.1 > > It creates/install the xine-* in /usr/lib/xine/plugins/1.1.10 > not, depend for the Version, to /usr/lib/xine/plugins/1.1.10.1 > > But in the header file /usr/inlude/xine.h it shows the version > 1.1.10.1. > > We detect this in the vdr-xineliboutput-*.ebuild an let install the > xineplug_inp_*.so to the given dir by the headerfile. > There is nothing wrong. > > Jussy, just skip the xine-lib-1.1.10.1 Version, use an older version, or > i hope it will fixed by xine team, then the next version. This is fixed in ebuild vdr-xineliboutput-1.0.0_rc2_p20080120-r1. Now we restrict the xine-lib version to 3 components. Regards Matthias -- Matthias Schwarzott (zzam) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Straw poll: stable version 1.6.0 now?
On Sonntag, 3. Februar 2008, Andrey Kuzmin wrote: > What are chances that multiproto will be merged to kernel in the > nearest time (1-2 months?) If chances are big, I don't think that it > is a good time to lose valuable Klaus's time for releasing & > supporting new stable version that will freeze another stable 1.8 with > multiproto support till 2009 :) So my vote is is NO in this case > As far as I know the merge window for 2.6.25 is almost closed. So the first kernel that could contain multiproto api is 2.6.26. But I doubt it, as multiproto is not even merged to main development branch of the drivers. Regards Matthias -- Matthias Schwarzott (zzam) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] PANIC: watchdog timer expired - exiting
On Sonntag, 2. Dezember 2007, Klaus Schmidinger wrote: > On 12/02/07 14:34, Darren Salt wrote: > > I demand that Klaus Schmidinger may or may not have written... > > > > [snip] > > > >> While testing this, I found that on my system the monotonic clock only > >> has a resolution of 4000250 ns (about 4 ms), which in your original > >> patch would have caused VDR not to use the monotonic clock. > > > > That suggests that your kernel is built with HZ=250 (CONFIG_HZ in > > /proc/config.gz). > > I'm running the default SUSE 10.2 kernel. > > >> Are there actually systems that have a 1 ms resolution? > > > > Any with HZ=1000, I expect :-) > > Ok, I see. > > I'll make it a 5 ms limit then, to allow default kernels to work. > Then please do fix it so that it also works with HZ=100, as that is also a valid setting I think VDR should be able to run with. Matthias -- Matthias Schwarzott (zzam) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] Make kPlay start playback from recording list
On Sonntag, 14. Oktober 2007, Ville Skyttä wrote: > Hello, > > After about three years of VDR use, I still quite often try to start > playback of a recording from the recordings view using the play button, > swear for a bit, and then hit ok. I couldn't think of a reason why play > wouldn't start the playback, so here's a tiny patch against VDR 1.4.7 that > implements it. That sounds almost like another issue I guess could be handled (but is more complicated). Everytime there is a list of epg events (like Schedule menu) I try to press the "Info"-Key to open the details. That could work also for timer-entries having an associated epg-event. Matthias -- Matthias Schwarzott (zzam) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] ExtRecMenu-Plugin 1.0
On Sonntag, 7. Oktober 2007, Martin Prochnow wrote: > Hi, > > I'm proud to announce version 1.0 of my ExtRecMenu-plugin. Here the > changes since version 0.13: > > - it is now possible to cancel a moving-between-filesystems-process > - applied changes for MainMenuHooksPatch > - added MainMenuHooksPatch to contrib/-dir; removed old one, which is > now obsolete > - free disk space is shown for the filesystem of the current directory > (can be switched of in plugin's setup menu) > - added support for hidding PIN-protected recordings in co-work with > PIN-Plugin > - added queue for moving recordings between filesystems > - added cutter queue That seems to mean you now do the cutting on your own, and no longer use vdr-cutting functions. Sadly this means hardlinkcutter will no longer be used :( Is it possible to either apply hardlinkcutting patch to extrecmenu, too, or make extrecmenu 1.0 access vdr-core cutting like it did before? Is there such a big difference between original cutting, and the one from extrecmenu? Matthias -- Matthias Schwarzott (zzam) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] How to get dvb-type of a device
Hi there! getting some segfaults using newer reelchannelscan led me to some deeper look into the code. Reelchannelscan loops over all devices, and tries to check the dvb-type of each. If it can find the type it adds it to list of devices. device->ProvidesSource(cSource::stTerr) device->ProvidesSource(cSource::stCable) device->ProvidesSource(cSource::stSat) Now the check fails for me as I use DVB-s + sourcecaps patch, and sourcecaps interpretes cSource:stSat as S0.0E. Is there a better way to check dvb-type, or is it clearly a bug of sourcecaps. The crash itself is caused as reelchannelscan uses a cMenuEditStraItem to select from the 0 found devices. Should cMenuEditStraItem be patched to not segfault in these cases? Matthias -- Matthias Schwarzott (zzam) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH] Fix compiler warnings with gcc-4.2.0
Hi there!
This patch fixes a compiler warning gcc-4.2.0 now prints. This is about
assigning constant strings to non-const char variables.
Matthias
--
Matthias Schwarzott (zzam)
Index: vdr-1.5.7/i18n.c
===
--- vdr-1.5.7.orig/i18n.c
+++ vdr-1.5.7/i18n.c
@@ -61,7 +61,7 @@ const char *LanguageCodeList[] = {
NULL
};
-static char *I18nLocaleDir = LOCDIR;
+static const char *I18nLocaleDir = LOCDIR;
static cStringList LanguageLocales;
static cStringList LanguageNames;
Index: vdr-1.5.7/keys.h
===
--- vdr-1.5.7.orig/keys.h
+++ vdr-1.5.7/keys.h
@@ -82,7 +82,7 @@ enum eKeys { // "Up" and "Down" must be
struct tKey {
eKeys type;
- char *name;
+ const char *name;
};
class cKey : public cListObject {
Index: vdr-1.5.7/menu.c
===
--- vdr-1.5.7.orig/menu.c
+++ vdr-1.5.7/menu.c
@@ -1040,7 +1040,7 @@ int cMenuScheduleItem::Compare(const cLi
return r;
}
-static char *TimerMatchChars = " tT";
+static const char *TimerMatchChars = " tT";
bool cMenuScheduleItem::Update(bool Force)
{
Index: vdr-1.5.7/rcu.c
===
--- vdr-1.5.7.orig/rcu.c
+++ vdr-1.5.7/rcu.c
@@ -257,7 +257,7 @@ void cRcuRemote::SetNumber(int n, bool H
data = m;
}
-void cRcuRemote::SetString(char *s)
+void cRcuRemote::SetString(const char *s)
{
const char *chars = mode == modeH ? "0123456789ABCDEF" : "0123456789-EHLP ";
int n = 0;
Index: vdr-1.5.7/rcu.h
===
--- vdr-1.5.7.orig/rcu.h
+++ vdr-1.5.7/rcu.h
@@ -31,7 +31,7 @@ private:
void SetMode(unsigned char Mode);
void SetNumber(int n, bool Hex = false);
void SetPoints(unsigned char Dp, bool On);
- void SetString(char *s);
+ void SetString(const char *s);
bool DetectCode(unsigned char *Code);
virtual void Action(void);
virtual void ChannelSwitch(const cDevice *Device, int ChannelNumber);
Index: vdr-1.5.7/thread.c
===
--- vdr-1.5.7.orig/thread.c
+++ vdr-1.5.7/thread.c
@@ -416,7 +416,7 @@ bool cPipe::Open(const char *Command, co
return false;
}
- char *mode = "w";
+ const char *mode = "w";
int iopipe = 0;
if (pid > 0) { // parent process
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH] Also set correct locale-filename in i18n-to-gettext.pl for vdr-1.5.8
Hi there! as vdr-1.5.8 now uses vdr-$(PLUGIN).mo as filename, i18n-to-gettext.pl should add corresponding code to Makefiles. Matthias -- Matthias Schwarzott (zzam) Index: vdr-1.5.8/i18n-to-gettext.pl === --- vdr-1.5.8.orig/i18n-to-gettext.pl +++ vdr-1.5.8/i18n-to-gettext.pl @@ -323,7 +323,7 @@ i18n: $(I18Nmo) @mkdir -p $(LOCALEDIR) for i in $(I18Ndirs); do\ mkdir -p $(LOCALEDIR)/$$i/LC_MESSAGES;\ - cp $(PODIR)/$$i.mo $(LOCALEDIR)/$$i/LC_MESSAGES/$(PLUGIN).mo;\ + cp $(PODIR)/$$i.mo $(LOCALEDIR)/$$i/LC_MESSAGES/vdr-$(PLUGIN).mo;\ done }; ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] improving i18n-to-gettext.pl
On Samstag, 18. August 2007, Klaus Schmidinger wrote: > On 08/18/07 13:10, Matthias Schwarzott wrote: > > > > The directory /usr/lib/locale does NOT contain any translations, but > > rather a directory for every locale you can set via setlocale. > > Its meant as a replacement of the setlocale loop. > > I'm afraid I don't see what you mean. > I know that the "locale" directory doesn't contain translations directly, > but rather subdirectories. VDR gathers the names of these subdirectories > and does a setlocale() for each of them. Then it tries to get the > translation of "LanguageName$English" in order to build a list of all > available languages. How else do you suggest that could be done? > First: general directory layout: /usr/share/locale/*/LC_MESSAGES/*.mo contains translations the oposite is /usr/lib/locale. This does NOT contain translations (and if you insisit on the difference: nowhere in the subdirs are translations). There are just descriptions of the available locales. You now do this: Loop over the subdirs of vdr-private-locale directory and then check which of these are actually available by doing setlocale. Now this can also be done by a check if there is some matching directory under /usr/lib/locale/. Regarding the english name of the associated language: locale -a -v will not only print the list of locales, but also a lot of detail info. This info should also be available via some API. But searching did not produce any API to query this. Some cut out example: # locale -a -v ... locale: de_DE.utf8 directory: /usr/lib/locale/de_DE.utf8 --- title | German locale for Germany source | Free Software Foundation, Inc. address | 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA email | [EMAIL PROTECTED] language | German territory | Germany revision | 1.0 date | 2000-06-24 codeset | UTF-8 locale: en_GB directory: /usr/lib/locale/en_GB --- title | English locale for Britain source | RAP address | Sankt J�rgens Alle 8, DK-1615 K�benhavn V, Danmark contact | Keld Simonsen email | [EMAIL PROTECTED] language | English territory | Great Britain revision | 1.0 date | 2000-06-28 codeset | ISO-8859-1 ... Matthias -- Matthias Schwarzott (zzam) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] improving i18n-to-gettext.pl
On Samstag, 18. August 2007, Klaus Schmidinger wrote:
> On 08/18/07 12:55, Matthias Schwarzott wrote:
> > On Freitag, 17. August 2007, Klaus Schmidinger wrote:
> >> On 08/15/07 15:07, Matthias Schwarzott wrote:
> >>> On Mittwoch, 15. August 2007, Klaus Schmidinger wrote:
> >>>
> >>> This will work, but only if the locale de_AT you set does exist (being
> >>> in output of locale -a).
> >>>
> >>>> but it came up with the default English texts. Then I renamed
> >>>> "de" to "de_AT" and did the same again, and I got the German texts.
> >>>>
> >>>> I was hoping that gettext would be a little more intelligent and
> >>>> look for
> >>>>
> >>>> - an exact match ("de_AT")
> >>>> - a default ("de")
> >>>> - any suitable language ("de_DE")
> >>>
> >>> I think it does this but not doing "any suitable language".
> >>> ...
> >>
> >> Could you please try the attached patch and see whether this
> >> works for you?
> >>
> >> This should, e.g., select any "de*" locale in case there is no fully
> >> matching one.
> >
> > Not yet tested, but code looks promising.
> >
> > Another way to get list of usable locales is this:
> > Checking the subdirs of /usr/lib/locale/
> > And then using all, that have associated mo file under vdr's LOCALEDIR.
> > Sadly I don't know if there is a better way than hardcoding that
> > directory.
> >
> > But "locale -a" command will give the same result - maybe analyzing its
> > code will help (or just calling this external command).
>
> Currently VDR has its own directory with all its supported locales.
> It can quickly collect all locales by going through the entries
> in that directory. I can even compile my VDR so that it searches
> for the locales in "./locale" inside the source directory.
>
> I like the simplicity of this, and wouldn't want to make it any
> more complex.
>
The directory /usr/lib/locale does NOT contain any translations, but rather a
directory for every locale you can set via setlocale.
Its meant as a replacement of the setlocale loop.
Btw. arent these two calls identical
setlocale(LC_MESSAGES, oldLocale);
setlocale(LC_MESSAGES, "");
Matthias
--
Matthias Schwarzott (zzam)
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] improving i18n-to-gettext.pl
On Freitag, 17. August 2007, Klaus Schmidinger wrote:
> On 08/15/07 15:07, Matthias Schwarzott wrote:
> > On Mittwoch, 15. August 2007, Klaus Schmidinger wrote:
> >
> > This will work, but only if the locale de_AT you set does exist (being in
> > output of locale -a).
> >
> >> but it came up with the default English texts. Then I renamed
> >> "de" to "de_AT" and did the same again, and I got the German texts.
> >>
> >> I was hoping that gettext would be a little more intelligent and
> >> look for
> >>
> >> - an exact match ("de_AT")
> >> - a default ("de")
> >> - any suitable language ("de_DE")
> >
> > I think it does this but not doing "any suitable language".
> > ...
>
> Could you please try the attached patch and see whether this
> works for you?
>
> This should, e.g., select any "de*" locale in case there is no fully
> matching one.
>
Not yet tested, but code looks promising.
Another way to get list of usable locales is this:
Checking the subdirs of /usr/lib/locale/
And then using all, that have associated mo file under vdr's LOCALEDIR.
Sadly I don't know if there is a better way than hardcoding that directory.
But "locale -a" command will give the same result - maybe analyzing its code
will help (or just calling this external command).
Matthias
--
Matthias Schwarzott (zzam)
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] change make install to be really useful
On Mittwoch, 15. August 2007, Klaus Schmidinger wrote: > On 08/13/07 18:30, Matthias Schwarzott wrote: > > ... > > makefile-install-header.diff: > > It adds an install-header target which is also called by target install. > > This installs the header files and Make.config to $(HEADERDIR) (should > > that be changed to INCDIR ?) > > to be able to compile plugins against the installed vdr without the need > > to keep vdr sources. > > This doesn't make sense, because a plugin's Makefile does > > VDRDIR = ../../.. > ... > APIVERSION = $(shell sed -ne '/define APIVERSION/s/^.*"\(.*\)".*$$/\1/p' > $(VDRDIR)/config.h) > Sure one needs to point the plugin to the place where it can find the needed files. But I have not tried to find the minimal required changeset. Matthias -- Matthias Schwarzott (zzam) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] improving i18n-to-gettext.pl
On Mittwoch, 15. August 2007, Klaus Schmidinger wrote:
> On 08/15/07 14:02, Matthias Schwarzott wrote:
> > On Mittwoch, 15. August 2007, Matthias Fechner wrote:
> >> Hi Matthias,
> >>
> >>
> >> because German is spoken in more then one country: de_DE, de_AT and I
> >> think de_CH and more. I havn't not list with all locales here now.
> >
> > Yeah, german is spoken in other countries. Is there then a reason to
> > restrict the translation to germany?
> >
> > some example:
> > wget installs the file /usr/share/locale/de/LC_MESSAGES/wget.mo
> > this is to provide translations for "all" de* locales. Not just the
> > german one, but also for austria and swiss.
>
> I just tried renaming VDR's "de_DE" locale to "de" and did
>
> LC_ALL=de_AT ./vdr
>
This will work, but only if the locale de_AT you set does exist (being in
output of locale -a).
> but it came up with the default English texts. Then I renamed
> "de" to "de_AT" and did the same again, and I got the German texts.
>
> I was hoping that gettext would be a little more intelligent and
> look for
>
> - an exact match ("de_AT")
> - a default ("de")
> - any suitable language ("de_DE")
I think it does this but not doing "any suitable language".
trying it with ls:
# LC_ALL=de_DE strace ls xxx
open("/usr/share/locale/de_DE.utf8/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1
ENOENT (No such file or directory)
open("/usr/share/locale/de_DE/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT
(No such file or directory)
open("/usr/share/locale/de.utf8/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1
ENOENT (No such file or directory)
open("/usr/share/locale/de/LC_MESSAGES/coreutils.mo", O_RDONLY) = 3
You can see that gettext does this:
1. Trying the set locale with some different charsets (de_DE.utf8, de_DE)
2. stripping of country and trying language with different charsets (de.utf8,
de).
Only condition is that the locale one sets LC_MESSAGES to must exist.
Now my tests: I created de_DE and de_AT locales on my system, but not de_CH.
# LC_ALL=de_DE ls
ls: Zugriff auf nicht möglich: Datei oder Verzeichnis nicht gefunden
# LC_ALL=de_AT ls
ls: Zugriff auf nicht möglich: Datei oder Verzeichnis nicht gefunden
# LC_ALL=de_CH ls
ls: cannot access zzzz: No such file or directory
# LC_ALL=de ls zzz
ls: cannot access : No such file or directory
The reason vdr does not work with directory called de is the same as LC_ALL=de
will not work.
There is no locale called de even if the directory is called de.
Matthias
--
Matthias Schwarzott (zzam)
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] improving i18n-to-gettext.pl
On Mittwoch, 15. August 2007, Matthias Fechner wrote: > Hi Matthias, > > Matthias Schwarzott wrote: > > General question: Why is the locale dir called de_DE and not just de - as > > that seems what most other programs on my system do? > > because German is spoken in more then one country: de_DE, de_AT and I > think de_CH and more. I havn't not list with all locales here now. > Yeah, german is spoken in other countries. Is there then a reason to restrict the translation to germany? some example: wget installs the file /usr/share/locale/de/LC_MESSAGES/wget.mo this is to provide translations for "all" de* locales. Not just the german one, but also for austria and swiss. Matthias -- Matthias Schwarzott (zzam) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Comments on plugin Makefiles
Hi there! This time I have some comments on Makefiles for plugins. 1. Is there any reason to not allow plain "make" without target to work? It would be so easy to move the "all:" target before "%.o: %.c" line. Now when I call make I just get the first .c file compiled. when changing the all target to be the first this will do what is necessary. 2. Is it really necessary to have compiling and installing inside the same target? This even gets more annoying with the new i18n target that also spreads all files over my system when hitting "make all". Matthias -- Matthias Schwarzott (zzam) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] improving i18n-to-gettext.pl
Hi there!
This patch should improve i18n-to-gettext.pl to work with all plugins
1.It also lists i18n.h as there seem to be some plugin-writer putting
translations there.
2. It also strips // comments being in lines without "," at the end.
3. it strips /* ... */ comments being in just one line
4. it strips /* ... */ comments spreading over multiple line
5. it just ignores #if and #endif lines (like used to make plugins compile
with older vdr-versions which had less languages supported).
General question: Why is the locale dir called de_DE and not just de - as that
seems what most other programs on my system do?
Matthias
--
Matthias Schwarzott (zzam)
Index: vdr-1.5.7/i18n-to-gettext.pl
===
--- vdr-1.5.7.orig/i18n-to-gettext.pl
+++ vdr-1.5.7/i18n-to-gettext.pl
@@ -75,7 +75,7 @@ die "can't find plugin name!" unless ($P
# Locate the file containing the texts:
$I18NFILE = "";
-for ("i18n.c", `ls *.c`) { # try i18n.c explicitly first
+for ("i18n.c", "i18n.h", `ls *.c`) { # try i18n.c explicitly first
chomp($f = $_);
if (-f $f && `grep tI18nPhrase $f`) {
$I18NFILE = $f;
@@ -204,13 +204,26 @@ $POTFILE = "$PODIR/$PLUGIN.pot";
# Collect all translated texts:
open(F, $I18NFILE) || die "$I18NFILE: $!\n";
+$in_comment=0;
while () {
chomp;
s/\t/ /g; # get rid of tabs
s/ *$//; # get rid of trailing blanks
s/^ *\/\/.*//; # remove comment lines
- s/, *\/\/.*/,/; # strip trailing comments
+ s/ *\/\/.*//; # strip trailing comments
+ s/\/\*.*\*\///g; # strip c comments
+ if (/\/\*/) {
+$in_comment=1;
+ s/\/\*.*$//; # remove starting of comment
+ } elsif (/\*\//) {
+$in_comment=0;
+ s/^.*\*\///; # remove end of comment
+ } elsif ($in_comment) {
+next;
+ }
next if (/^ *$/); # skip empty lines
+ next if (/#if/);
+ next if (/#endif/);
next unless ($found or $found = /const *tI18nPhrase .*{/); # sync on phrases
next if (/const *tI18nPhrase .*{/); # skip sync line
last if (/{ *NULL *}/); # stop after last phrase
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] change make install to be really useful
On Dienstag, 14. August 2007, Artur Skawina wrote: > Udo Richter wrote: > > Matthias Schwarzott wrote: > >> makefile-destdir.diff: > >> It add variable DESTDIR to makefile to install under $(DESTDIR) instead > >> of / > > > > I would prefer something like DESTDIR=/usr/local that can be redirected > > to /usr or /tmp/newpackage/usr or similar, just as many configure > > scripts do it. On the downside, this wouldn't work for > > $(DESTDIR)$(VIDEODIR). > > the usual convention is PREFIX, which defaults to '/usr/local' and can be > changed to eg '/usr/' or '/sw/vdr-1.6.0' etc. > DESTDIR is completely independent -- it adds _another_ prefix; this is used > eg when building packages. > So "make install DESTDIR=/tmp/BLD-38746 PREFIX=/sw/vdr-1.6.0" > means to assume the program will be installed in /sw/vdr-1.6.0 (and look > for config files in /sw/vdr-1.6.0/etc/, binaries in /sw/vdr-1.6.0/bin/ > etc), but to copy all the files to /tmp/BLD-38746/sw/vdr-1.6.0. This way > you can build a package w/o disturbing the /sw/ tree and install using a > package manager later. I updated the patch to use DESTDIR and PREFIX. Comments on installing header files and Make.config? Should Make.config go to $PREFIX/share/vdr ? Matthias -- Matthias Schwarzott (zzam) Index: vdr-1.5.7/Makefile === --- vdr-1.5.7.orig/Makefile +++ vdr-1.5.7/Makefile @@ -15,9 +15,11 @@ CXX ?= g++ CXXFLAGS ?= -g -O2 -Wall -Woverloaded-virtual LSIDIR = ./libsi -MANDIR = /usr/local/man -BINDIR = /usr/local/bin -LOCDIR = /usr/share/vdr/locale +DESTDIR ?= +PREFIX ?= /usr/local +MANDIR = $(PREFIX)/share/man +BINDIR = $(PREFIX)/bin +LOCDIR = $(PREFIX)/share/vdr/locale LIBS = -ljpeg -lpthread -ldl -lcap -lfreetype -lfontconfig INCLUDES = -I/usr/include/freetype2 @@ -25,6 +27,7 @@ PLUGINDIR= ./PLUGINS PLUGINLIBDIR= $(PLUGINDIR)/lib VIDEODIR = /video +CONFDIR ?= $(VIDEODIR) DOXYGEN = /usr/bin/doxygen DOXYFILE = Doxyfile @@ -123,8 +126,8 @@ i18n: $(I18Nmo) done install-i18n: - @mkdir -p $(LOCDIR) - @(cd $(LOCALEDIR); cp -r --parents * $(LOCDIR)) + @mkdir -p $(DESTDIR)$(LOCDIR) + @(cd $(LOCALEDIR); cp -r --parents * $(DESTDIR)$(LOCDIR)) # The 'include' directory (for plugins): @@ -162,30 +165,31 @@ install: install-bin install-i18n instal # VDR binary: install-bin: vdr - @mkdir -p $(BINDIR) - @cp --remove-destination vdr runvdr $(BINDIR) + @mkdir -p $(DESTDIR)$(BINDIR) + @cp --remove-destination vdr runvdr svdrpsend.pl $(DESTDIR)$(BINDIR) # Configuration files: install-conf: - @if [ ! -d $(VIDEODIR) ]; then\ - mkdir -p $(VIDEODIR);\ - cp *.conf $(VIDEODIR);\ + @mkdir -p $(DESTDIR)$(VIDEODIR) + @if [ ! -d $(DESTDIR)$(CONFDIR) ]; then\ + mkdir -p $(DESTDIR)$(CONFDIR);\ + cp *.conf $(DESTDIR)$(CONFDIR);\ fi # Documentation: install-doc: - @mkdir -p $(MANDIR)/man1 - @mkdir -p $(MANDIR)/man5 - @gzip -c vdr.1 > $(MANDIR)/man1/vdr.1.gz - @gzip -c vdr.5 > $(MANDIR)/man5/vdr.5.gz + @mkdir -p $(DESTDIR)$(MANDIR)/man1 + @mkdir -p $(DESTDIR)$(MANDIR)/man5 + @gzip -c vdr.1 > $(DESTDIR)$(MANDIR)/man1/vdr.1.gz + @gzip -c vdr.5 > $(DESTDIR)$(MANDIR)/man5/vdr.5.gz # Plugins: install-plugins: plugins - @mkdir -p $(PLUGINLIBDIR) - @cp --remove-destination $(PLUGINDIR)/lib/lib*-*.so.$(APIVERSION) $(PLUGINLIBDIR) + @mkdir -p $(DESTDIR)$(PLUGINLIBDIR) + @cp --remove-destination $(PLUGINDIR)/lib/lib*-*.so.$(APIVERSION) $(DESTDIR)$(PLUGINLIBDIR) # Source documentation: Index: vdr-1.5.7/Makefile === --- vdr-1.5.7.orig/Makefile +++ vdr-1.5.7/Makefile @@ -20,6 +20,7 @@ PREFIX ?= /usr/local MANDIR = $(PREFIX)/man BINDIR = $(PREFIX)/bin LOCDIR = $(PREFIX)/share/vdr/locale +INCDIR = $(PREFIX)/include LIBS = -ljpeg -lpthread -ldl -lcap -lfreetype -lfontconfig INCLUDES = -I/usr/include/freetype2 @@ -160,7 +161,7 @@ clean-plugins: # Install the files: -install: install-bin install-i18n install-conf install-doc install-plugins +install: install-bin install-i18n install-conf install-doc install-plugins install-header # VDR binary: @@ -191,6 +192,13 @@ install-plugins: plugins @mkdir -p $(DESTDIR)$(PLUGINLIBDIR) @cp --remove-destination $(PLUGINDIR)/lib/lib*-*.so.$(APIVERSION) $(DESTDIR)$(PLUGINLIBDIR) +# Header files: + +install-header: + @mkdir -p $(DESTDIR)$(INCDIR)/vdr $(DESTDIR)$(INCDIR)/vdr/libsi + @cp *.h Make.config $(DESTDIR)$(INCDIR)/vdr + @cp libsi/*.h $(DESTDIR)$(INCDIR)/vdr/libsi + # Source documentation: srcdoc: ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] change make install to be really useful
On Montag, 13. August 2007, Joachim Wilke wrote: > 2007/8/13, Matthias Schwarzott <[EMAIL PROTECTED]>: > > install-i18n.diff > > I already posted this to the list yesterday. > > > makefile-destdir.diff: > > It add variable DESTDIR to makefile to install under $(DESTDIR) instead > > of / It also adds variable CONFDIR (by default identical to $(VIDEODIR)) > > to be able to set it to different value. > > Where gets DESTDIR actually set? > When you do make install DESTDIR=/directory/I/want/vdr/installed/to else DESTDIR remains unset and "make install" behaves as always. The ebuilds do this for example to satisfy some security by using a sandbox for compiling and installing programs. make install then uses some temporary image directory. After that the content gets merged to the live system. (Also preserving configuration files in that process, ...) Matthias -- Matthias Schwarzott (zzam) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] change make install to be really useful
Hi there! I now switched the ebuilds to use make install. But for that to work I needed to modify the Makefile. install-i18n.diff Lets install target call install-i18n target. makefile-destdir.diff: It add variable DESTDIR to makefile to install under $(DESTDIR) instead of / It also adds variable CONFDIR (by default identical to $(VIDEODIR)) to be able to set it to different value. Additionally it installs svdrpsend.pl makefile-install-header.diff: It adds an install-header target which is also called by target install. This installs the header files and Make.config to $(HEADERDIR) (should that be changed to INCDIR ?) to be able to compile plugins against the installed vdr without the need to keep vdr sources. Matthias -- Matthias Schwarzott (zzam) Index: vdr-1.5.7/Makefile === --- vdr-1.5.7.orig/Makefile +++ vdr-1.5.7/Makefile @@ -25,6 +25,7 @@ PLUGINDIR= ./PLUGINS PLUGINLIBDIR= $(PLUGINDIR)/lib VIDEODIR = /video +CONFDIR = $(VIDEODIR) DOXYGEN = /usr/bin/doxygen DOXYFILE = Doxyfile @@ -123,8 +124,8 @@ i18n: $(I18Nmo) done install-i18n: - @mkdir -p $(LOCDIR) - @(cd $(LOCALEDIR); cp -r --parents * $(LOCDIR)) + @mkdir -p $(DESTDIR)$(LOCDIR) + @(cd $(LOCALEDIR); cp -r --parents * $(DESTDIR)$(LOCDIR)) # The 'include' directory (for plugins): @@ -162,30 +163,31 @@ install: install-bin install-i18n instal # VDR binary: install-bin: vdr - @mkdir -p $(BINDIR) - @cp --remove-destination vdr runvdr $(BINDIR) + @mkdir -p $(DESTDIR)$(BINDIR) + @cp --remove-destination vdr runvdr svdrpsend.pl $(DESTDIR)$(BINDIR) # Configuration files: install-conf: - @if [ ! -d $(VIDEODIR) ]; then\ - mkdir -p $(VIDEODIR);\ - cp *.conf $(VIDEODIR);\ + @mkdir -p $(DESTDIR)$(VIDEODIR) + @if [ ! -d $(DESTDIR)$(CONFDIR) ]; then\ + mkdir -p $(DESTDIR)$(CONFDIR);\ + cp *.conf $(DESTDIR)$(CONFDIR);\ fi # Documentation: install-doc: - @mkdir -p $(MANDIR)/man1 - @mkdir -p $(MANDIR)/man5 - @gzip -c vdr.1 > $(MANDIR)/man1/vdr.1.gz - @gzip -c vdr.5 > $(MANDIR)/man5/vdr.5.gz + @mkdir -p $(DESTDIR)$(MANDIR)/man1 + @mkdir -p $(DESTDIR)$(MANDIR)/man5 + @gzip -c vdr.1 > $(DESTDIR)$(MANDIR)/man1/vdr.1.gz + @gzip -c vdr.5 > $(DESTDIR)$(MANDIR)/man5/vdr.5.gz # Plugins: install-plugins: plugins - @mkdir -p $(PLUGINLIBDIR) - @cp --remove-destination $(PLUGINDIR)/lib/lib*-*.so.$(APIVERSION) $(PLUGINLIBDIR) + @mkdir -p $(DESTDIR)$(PLUGINLIBDIR) + @cp --remove-destination $(PLUGINDIR)/lib/lib*-*.so.$(APIVERSION) $(DESTDIR)$(PLUGINLIBDIR) # Source documentation: Index: vdr-1.5.7/Makefile === --- vdr-1.5.7.orig/Makefile +++ vdr-1.5.7/Makefile @@ -20,6 +20,7 @@ BINDIR = /usr/local/bin LOCDIR = /usr/share/vdr/locale LIBS = -ljpeg -lpthread -ldl -lcap -lfreetype -lfontconfig INCLUDES = -I/usr/include/freetype2 +HEADERDIR = /usr/local/include PLUGINDIR= ./PLUGINS PLUGINLIBDIR= $(PLUGINDIR)/lib @@ -158,7 +159,7 @@ clean-plugins: # Install the files: -install: install-bin install-i18n install-conf install-doc install-plugins +install: install-bin install-i18n install-conf install-doc install-plugins install-header # VDR binary: @@ -189,6 +190,13 @@ install-plugins: plugins @mkdir -p $(DESTDIR)$(PLUGINLIBDIR) @cp --remove-destination $(PLUGINDIR)/lib/lib*-*.so.$(APIVERSION) $(DESTDIR)$(PLUGINLIBDIR) +# Header files: + +install-header: + @mkdir -p $(DESTDIR)$(HEADERDIR)/vdr $(DESTDIR)$(HEADERDIR)/vdr/libsi + @cp *.h Make.config $(DESTDIR)$(HEADERDIR)/vdr + @cp libsi/*.h $(DESTDIR)$(HEADERDIR)/vdr/libsi + # Source documentation: srcdoc: Index: vdr-1.4.7/Makefile === --- vdr-1.4.7.orig/Makefile +++ vdr-1.4.7/Makefile @@ -24,6 +24,7 @@ PLUGINDIR= ./PLUGINS PLUGINLIBDIR= $(PLUGINDIR)/lib VIDEODIR = /video +CONFDIR = $(VIDEODIR) DOXYGEN = /usr/bin/doxygen DOXYFILE = Doxyfile @@ -200,30 +201,31 @@ install: install-bin install-conf instal # VDR binary: install-bin: vdr - @mkdir -p $(BINDIR) - @cp --remove-destination vdr runvdr $(BINDIR) + @mkdir -p $(DESTDIR)$(BINDIR) + @cp --remove-destination vdr runvdr svdrpsend.pl $(DESTDIR)$(BINDIR) # Configuration files: install-conf: - @if [ ! -d $(VIDEODIR) ]; then\ - mkdir -p $(VIDEODIR);\ - cp *.conf $(VIDEODIR);\ + @mkdir -p $(DESTDIR)$(VIDEODIR) + @if [ ! -d $(DESTDIR)$(CONFDIR) ]; then\ + mkdir -p $(DESTDIR)$(CONFDIR);\ + cp *.conf $(DESTDIR)$(CONFDIR);\ fi # Documentation: install-doc: - @mkdir -p $(MANDIR)/man1 - @mkdir -p $(MANDIR)/man5 - @gzip -c vdr.1 > $(MANDIR)/man1/vdr.1.gz - @gzip -c vdr.5 > $(MANDIR)/man5/vdr.5.gz + @mkdir -p $(DESTDIR)$(MANDIR)/man1 + @mkdir -p $(DESTDIR)$(MANDIR)/man5 + @gzip -c vdr.1 > $(DESTDIR)$(MANDIR)/man1/vdr.1.gz + @gzip -c vdr.5 > $(DESTDIR)$(MANDIR)/man5/vdr.5.gz # Plugins: install-plugins: plugins
Re: [vdr] subtitles-0.5.0 and gentoo
On Samstag, 30. Juni 2007, you wrote: > Hi, > Hi Ville! Nice to hear there are actually users of the ebuilds ;) > AFAIK vdr 1.4.7 doesn't fix the error with subtitles not being > recorded (well, at least it's not in the changelog; OTOH I've > understod that the problem lies in the plugin, but then again I tried > vdr-subtitles 0.5.0 with vdr 1.4.6, and it had no effect). VDR 1.5.5 > works fine for me in this aspect, at least for now (haven't tested it > thoroughly yet though since I installed it only two days ago). > > However, VDR 1.5.5 ebuilds in the overlay have a few problems (which > is understandable since they are developing versions of the ebuilds). > But, since recording subtitles is such a core feature for me (and > probably for a lot of other people, too), I found it worthwhile to get > 1.5.5 running. Here are the problems I needed to work around > (hopefully I didn't forget anything): > Well, we hope to get the most annyoing problems out of the ebuilds soon. > text2skin: > (I need text2skin, since I'm using DXR3 and no other skins are stable > enough on DXR3. Also, on vdr 1.5.X, the default skin is totally > garbled and unusable on a dxr3.). I needed to add the patch from this > mailing list thread "updated text2skin for vdr-1.5.3 and enigma?" to > the ebuild. Then it compiled and seems to work fine. > I dont use it and have no real idea how it works. If you have a patch to make it working, just send it to me and I will add that to the ebuild. > epgsearch: > The current version does not compile against 1.5.X. There is > 0.9.23_beta1 ebuild in vdr-1.5 overlay, however that is outdated, > since the current beta is beta3, and the beta1 source is not anymore > on the epgsearch site. Just copying the ebuld to beta3 (and doing > 'ebuild X digest') solved that one - and probaly the ebuild will be > renamed on the overlay soon, too =). Done that! > Don't now if this beta has some nasty bugs, but at least the blue > smoke is still inside my VDR =) > > gentoo-vdr-scripts, locales, UTF-8 and Scandinavian characters (umlauts): > After getting VDR 1.5.5 working, one quite annoying problem was left: > all non-7-bit characters were displayed as ?-marks, if using > gentoo-vdr-scrips (which I'm quite dependant for the functionality > they provide, but unfortunately made for <1.5.0 in mind). I found that > in /usr/share/vdr/rcscripts/pre-start-45-utf8-check.sh all locales are > reset to POSIX; however, this makes VDR 1.5.5 misbehave. I modified > the script so that LC_ALL and LANG are set to fi_FI.UTF-8, and now > everything works like a charm. > Well, we are still in discussion phase how gentoo-vdr-scripts should behave. Attached is some code we think could be almost ready for commiting to gentoo-vdr-scripts. The conf-changes is just to comment that one can set LANG inside conf.d/vdr, and need not have it system-wide. > > Also, all recordings done previously have the scandinavian characters > displayed as ?-marks (in the info screen, don't have any DVB subtitles > in the old recordings to test with 'cause of this bug). This is also a > very minor problem IMO. Maybe fixable by running enca, if the files > containing the info's are in ASCII. Haven't looked into this since it > doesn't bother me. > You mean filename or content of info.vdr. Well both should be solvable. First by convmv, second by recode or similar like iconv. > Yep, these are really ugly fixes, for the most part. But just thought > worth to mention, since I do think a lot of people really need those > subtitles in recordings. > > Finally, here's a list of plugins I'm using and find working in 1.5.5, > for reference: > > dxr3 > femon > osdteletext > epgsearch > mplayer > undelete > streamdev-server > text2skin > lcdproc > subtitles > control > externalplayer > If you still have patches not yet inside the ebuilds we are happy to apply them. Greetings Matthias -- Matthias Schwarzott (zzam) pre-start-45-utf8-check.sh Description: application/shellscript Index: etc/conf.d/vdr === --- etc/conf.d/vdr (revision 478) +++ etc/conf.d/vdr (working copy) @@ -29,10 +29,16 @@ # Set the sort-order vdr uses # allowed values: locale-definitions listed by locale -a # e.g. de_DE, en_GB, ... -# default: glibc-default order (posix) +# default: glibc-default order (posix), or value of LANG if set and >=vdr-1.5.3 #VDR_SORT_ORDER="de_DE" +# Set the locale vdr should use (starting from vdr-1.5.3) +# allowed va
[vdr] [PATCH] vdr-burn-0.1.0_pre21 using correct charset with >=vdr-1.5.3
Hi there!
The attached patch lets vdr-burn-0.1.0_pre21 use the correct charset that vdr
itself uses. This stops vdr-burn to double utf8 encode texts.
Matthias
--
Matthias Schwarzott (zzam)
Index: burn-0.1.0-pre21/burn.c
===
--- burn-0.1.0-pre21.orig/burn.c
+++ burn-0.1.0-pre21/burn.c
@@ -45,8 +45,13 @@ namespace vdr_burn
string plugin::get_character_encoding()
{
-#ifdef UTF8PATCH
- return "utf8";
+#if VDRVERSNUM >= 10503
+ if (cCharSetConv::SystemCharacterTable())
+ return cCharSetConv::SystemCharacterTable();
+ else
+ return "utf-8";
+#elif defined(UTF8PATCH)
+ return "utf-8";
#else
return tr("iso8859-15");
#endif
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] changing default font
On Samstag, 23. Juni 2007, Klaus Schmidinger wrote: > On 06/21/07 14:10, Stone wrote: > > 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? > > 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 For cpumon and pilotskin the reason seems clear to me: They call GetFont to initialize a static member: static const cFont *font = cFont::GetFont(fontOsd); For skinelchi this seems a bit more complicated, but I guess it also is related to calling GetFont too early (before config settings has been loaded). Matthias -- Matthias Schwarzott (zzam) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH] vdr-dvdswitch crashing when pressing an arrow key in empty image directory
Hi there!
Opening DVDSwitch menu if the image directory is empty, and then pressing some
arrow key crashes vdr.
The attached patch solves this bug.
Matthias
--
Matthias Schwarzott (zzam)
Index: dvdswitch-0.1.3/menu.c
===
--- dvdswitch-0.1.3.orig/menu.c
+++ dvdswitch-0.1.3/menu.c
@@ -754,8 +754,10 @@ eOSState cMainMenu::MenuMove(eKeys Key)
SetHelp();
mItem = (cMainMenuItem*)Get(Current());
- MainMenuOptions.setLastSelectItemName(mItem->FileName());
- MainMenuOptions.LastSelectItemType(mItem->Type());
+ if (mItem) {
+MainMenuOptions.setLastSelectItemName(mItem->FileName());
+MainMenuOptions.LastSelectItemType(mItem->Type());
+ }
return state;
}
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] record plug-in..
On Freitag, 25. Mai 2007, JJussi wrote: > On Thursday, 24. Mayta 2007 23:15, Petri Helin wrote: > > Not a plugin but does exactly what you are asking for - the livebuffer > > patch: http://home.vrweb.de/~bergwinkl.thomas/ > > OK, now I have to move using non-gentoo version of vdr.. ;-) > You cannot "include" extra patches to gentoo compile process.. Atleast not > easily.. Have a look at this describing how you can easily add own patches to the vdr ebuild: http://www.linuxtv.org/vdrwiki/index.php/Gentoo_VDR_own_patches Matthias PS: I think bigpatch has livebuffer included. -- Matthias Schwarzott (zzam) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH] Small change to correctly query the systems charset
Hi there!
This patch just changes charset querying to not only look at environment
variable LANG, but respect all in correct order. So now I can overwrite
charset setting with LC_CTYPE and LC_ALL.
Greetings
Matthias
--
Matthias Schwarzott (zzam)
diff -ru vdr-1.5.2-vanilla/vdr.c vdr-1.5.2/vdr.c
--- vdr-1.5.2-vanilla/vdr.c 2007-05-01 17:04:45.0 +0200
+++ vdr-1.5.2/vdr.c 2007-05-01 17:05:18.0 +0200
@@ -493,7 +493,7 @@
// Set the system character table:
- char *LangEnv = getenv("LANG");
+ char *LangEnv = setlocale(LC_CTYPE, "");
if (LangEnv) {
char *CodeSet = strchr(LangEnv, '.');
if (CodeSet) {
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Hard link cutter [was: Suggestion: High speed cutting]
On Sonntag, 18. März 2007, Reinhard Nissl wrote: > Hi, > > Richard Lithvall wrote: > > Why not just change the naming of video files to four, five or even > > eight digits? > > The problem is not the file name, it's the index file. An index entry > stores the file number as "uchar", which allows 256 recording files. > I do not know if the index file has a signature/magic-code at the start. If yes, it should be easy to define a new index-format with Longer integers for the file number. Another thing that comes to my mind, but is sure hard to implement: If I do two or more simultanous recordings from the same channel, why couldn't VDR record this to the same file, and hardlink it to both directories. That would reduce the need to create one long recording, if one would like to record two or more shows that are broadcasted one after the other. Matthias -- Matthias Schwarzott (zzam) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Fwd: Re: Noch was
-- Weitergeleitete Nachricht -- Betreff: Re: Noch was Datum: Dienstag, 27. Februar 2007 Von: Matthias Schwarzott <[EMAIL PROTECTED]> An: Helmut Auer <[EMAIL PROTECTED]> On Montag, 26. Februar 2007, you wrote: > P.S. Benoetigt Ihr evtl. noch einen ebuilder ? Was muesste ich dafuer > fuer Vorraussetzungen mitbringen ? Generell brauchen wir immer mehr Leute :) Weil es hat ja eh nicht jeder jede Hardware, und auch nicht unbedingt die Zeit alles zu machen. Voraussetzungen: Am besten ebuild Kentnisse, geht aber auch ohne so schwer ist das nicht Eigentlich ist so ein ebuild shell-code Beste doku dazu ist die hier (mit vielen Beispielen): http://devmanual.gentoo.org/ Oder du schaust einfach mal in ein paar ebuilds rein. Matthias -- Matthias Schwarzott (zzam) ------- -- Matthias Schwarzott (zzam) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] New VDR hardware
On Thursday 04 January 2007 10:20, Laz wrote: > > Hmmm...I've got one of these and I've never seen it disconnect yet > (a few months so far...fingers crossed!). > > When I've seen USB disconnections with two USB2 Nova-T devices, I was > getting things like /dev/dvb/adapter0, /dev/dvb/adapter2, > /dev/dvb/adapter3, i.e. adapter1 missing from where one of them had > been originally before disconnecting and then being reassigned as > adapter3! in this situation, vdr only sees the first DVB device > because it starts at adapter0 and stops counting when the next number > doesn't exist. This is something I would like to change. Just let vdr iterate over (number only an example) the first 8 dvb-adapters and try them. For now you can also have your runvdr give vdr the parameters -D 0 -D 2 -D 3 (script loop) to use all adapters. Or better: Ask hal (if available) to enumerate them. That could even enable us to get vdr hotplug-able. My long term goal is to get the dvb-driver no longer crash on disconnect, but just signalize The error ENODEV. And that vdr cope with device plug/unplug. Matthias -- Matthias Schwarzott (zzam) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDRAdmin and character mapping
On Monday 01 January 2007 20:51, Pasi Juppo wrote: > Hi, > > I have a small annoying problem that most likely is quite trivial but > can find the cause. All characters above ASCII 127 are converted to > something else. E.g. 'ä' gets converted to ','. Funny thing is that on > my server (FC4) the conversion is done like that but on windows computer > they are converted to '?' chars. > > On the machine where VDRAdmin is running characters are shown correctly. > It seems to be related to language setting but can't figure out how to > fix this. Could someone with more knowledge help me? > Hi This can accur from vdradmin not running in a locale with same charset as vdr uses. The only use-case we have found yet is utf8-system and vdr running with latin1. For Gentoo we have this hack in the vdradmin-startskript at the moment: When vdr is not utf8-capable (only when self-patched) then execute this code to switch of utf8-locale: l=$(locale | sed -e 's/\.[uU][tT][fF]\(-\)\?8//' -e 's/^/export /') eval $l Perhaps it would help if epg.vdr would contain information about encoding (even if it is not even read by vdr this could be usefull, but just to inform other programs). Matthias -- Matthias Schwarzott (zzam) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [RFC] Shutdown rewrite for 1.5.x
On Sunday 31 December 2006 15:02, Helmut Auer wrote:
> Matthias Schwarzott schrieb:
> > On Sunday 31 December 2006 13:36, Joachim Wilke wrote:
> >> 2006/12/30, Udo Richter <[EMAIL PROTECTED]>:
> >>> However, it might be worth thinking about giving plugins the ability to
> >>> set a different wakeup time, so that a scheduled EPG scan plugin can be
> >>> written.
> >>
> >> I also think that this would be very helpful for some plugins. Manual
> >> start detection could also include a call to the plugins. A plugin
> >> that did "schedule" an EPG-scan or similar could tell VDR during start
> >> up, that VDR woke up because of this scheduled event set by this
> >> plugin.
> >> At the moment I use a relatively complex patch that does some
> >> "maintainance" task during the night. If it would be possible to
> >> modify the wakeup-time in a plugin I could re-implement the complete
> >> patch as a plugin.
> >
> > I think a much easier solution (implementable in runvdr/vdr-initscript)
> > is: Write down wakeup-time when shutting down and comparing that to time
> > when system/vdr starts (with some margin).
>
> That's exactly what my Gen2VDR distribution is doing, and it works fine.
> It's not the job of vdr to guess why it was started, but it would be nice
> if vdr offers an option to shutdown after next recording ( maybe via svdrp
> call ).
In gentoo vdr package we added a small hack (attached), which implements a
svdrp call "down" to tell vdr it is inactive and will shutdown in X minutes.
We call this from shutdown-scripts to let vdr retry shutdown in 5 min (or
other value if needed).
Matthias
--
Matthias Schwarzott (zzam)
Written by Matthias Schwarzott <[EMAIL PROTECTED]>
GENTOO_NO_PREPARE
diff -ru --exclude='*.o' vdr-1.3.36-orig/svdrp.c vdr-1.3.36/svdrp.c
--- vdr-1.3.36-orig/svdrp.c 2005-12-29 00:02:26.0 +0100
+++ vdr-1.3.36/svdrp.c 2005-12-29 00:18:45.0 +0100
@@ -293,6 +293,9 @@
"Updates a timer. Settings must be in the same format as returned\n"
"by the LSTT command. If a timer with the same channel, day, start\n"
"and stop time does not yet exists, it will be created.",
+ "DOWN [ ]\n"
+ "Starts an automatic shutdown (with 5 minutes waiting time) in given\n"
+ "minutes or now if no number was given.",
"VOLU [ | + | - | mute ]\n"
"Set the audio volume to the given number (which is limited to the range\n"
"0...255). If the special options '+' or '-' are given, the volume will\n"
@@ -1342,6 +1345,16 @@
Reply(501, "Missing timer settings");
}
+extern time_t LastActivity;
+void cSVDRP::CmdDOWN(const char *Option)
+{
+ if (isnumber(Option))
+ LastActivity = time(NULL) - Setup.MinUserInactivity*60 + strtol(Option, NULL, 10)*60;
+ else
+ LastActivity = time(NULL) - Setup.MinUserInactivity*60;
+ Reply(250, "Automatic shutdown triggered");
+}
+
void cSVDRP::CmdVOLU(const char *Option)
{
if (*Option) {
@@ -1413,6 +1426,7 @@
else if (CMD("STAT")) CmdSTAT(s);
else if (CMD("UPDT")) CmdUPDT(s);
else if (CMD("VOLU")) CmdVOLU(s);
+ else if (CMD("DOWN")) CmdDOWN(s);
else if (CMD("QUIT")) Close(true);
else Reply(500, "Command unrecognized: \"%s\"", Cmd);
}
diff -ru --exclude='*.o' vdr-1.3.36-orig/svdrp.h vdr-1.3.36/svdrp.h
--- vdr-1.3.36-orig/svdrp.h 2005-12-29 00:02:26.0 +0100
+++ vdr-1.3.36/svdrp.h 2005-12-30 02:28:08.0 +0100
@@ -59,6 +59,7 @@
void CmdDELC(const char *Option);
void CmdDELR(const char *Option);
void CmdDELT(const char *Option);
+ void CmdDOWN(const char *Option);
void CmdEDIT(const char *Option);
void CmdGRAB(const char *Option);
void CmdHELP(const char *Option);
diff -ru --exclude='*.o' vdr-1.3.36-orig/vdr.c vdr-1.3.36/vdr.c
--- vdr-1.3.36-orig/vdr.c 2005-12-29 00:02:26.0 +0100
+++ vdr-1.3.36/vdr.c 2005-12-29 00:09:49.0 +0100
@@ -89,6 +89,8 @@
exit(1);
}
+time_t LastActivity;
+
int main(int argc, char *argv[])
{
// Save terminal settings:
@@ -395,7 +397,7 @@
int PreviousChannel[2] = { 1, 1 };
int PreviousChannelIndex = 0;
time_t LastChannelChanged = time(NULL);
- time_t LastActivity = 0;
+ LastActivity = 0; // now being a global variable
time_t LastCamMenu = 0;
int MaxLatencyTime = 0;
bool ForceShutdown = false;
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [RFC] Shutdown rewrite for 1.5.x
On Sunday 31 December 2006 14:15, Joachim Wilke wrote: > 2006/12/31, Matthias Schwarzott <[EMAIL PROTECTED]>: > > I think a much easier solution (implementable in runvdr/vdr-initscript) > > is: Write down wakeup-time when shutting down and comparing that to time > > when system/vdr starts (with some margin). > > Thats right, this is even more robust. But I think this should be > implemented in the vdr core not in scripts. > How could vdr know what the system does otherwise. I think here the principle of KISS should be applied: keep it simple stupid. Matthias -- Matthias Schwarzott (zzam) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [RFC] Shutdown rewrite for 1.5.x
On Sunday 31 December 2006 13:36, Joachim Wilke wrote: > 2006/12/30, Udo Richter <[EMAIL PROTECTED]>: > > However, it might be worth thinking about giving plugins the ability to > > set a different wakeup time, so that a scheduled EPG scan plugin can be > > written. > > I also think that this would be very helpful for some plugins. Manual > start detection could also include a call to the plugins. A plugin > that did "schedule" an EPG-scan or similar could tell VDR during start > up, that VDR woke up because of this scheduled event set by this > plugin. > At the moment I use a relatively complex patch that does some > "maintainance" task during the night. If it would be possible to > modify the wakeup-time in a plugin I could re-implement the complete > patch as a plugin. > I think a much easier solution (implementable in runvdr/vdr-initscript) is: Write down wakeup-time when shutting down and comparing that to time when system/vdr starts (with some margin). Matthias -- Matthias Schwarzott (zzam) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH] Patches for a lot of plugins (uint64/uint64_t)
Hi!
Here are the patches we already added to Gentoo's plugin-ebuilds.
Matthias
--
Matthias Schwarzott
Gentoo Developer
http://www.gentoo.org
diff -ru control-0.0.2a-orig/gateway.c control-0.0.2a/gateway.c
--- control-0.0.2a-orig/gateway.c 2006-12-03 16:44:46.170845357 +0100
+++ control-0.0.2a/gateway.c 2006-12-03 16:44:58.149701387 +0100
@@ -100,7 +100,7 @@
if (_stack.poll(100)) {
- uint64 Command = 0;
+ uint64_t Command = 0;
uint i = 0;
cTimeMs t0;
t0.Set();
diff -ru control-0.0.2a-orig/keyboard.c control-0.0.2a/keyboard.c
--- control-0.0.2a-orig/keyboard.c 2006-12-03 16:44:46.170845357 +0100
+++ control-0.0.2a/keyboard.c 2006-12-03 16:45:29.825253136 +0100
@@ -18,7 +18,7 @@
struct tKbdMap {
eKbdFunc func;
- uint64 code;
+ uint64_t code;
};
@@ -117,7 +117,7 @@
-bool cCtrlKeyboard::intPut(uint64 Command, bool Repeat, bool Release) {
+bool cCtrlKeyboard::intPut(uint64_t Command, bool Repeat, bool Release) {
bool ret = cRemote::Put(Command, Repeat, Release);
conLOG_KEYB("%s cKbdRemoteForControl::intPut(0x%016LX)", ret ? "true" : "false", Command);
@@ -126,7 +126,7 @@
-bool cCtrlKeyboard::Put(uint64 Command, bool Repeat, bool Release) {
+bool cCtrlKeyboard::Put(uint64_t Command, bool Repeat, bool Release) {
if (! _pRemote)
_pRemote = new cCtrlKeyboard();
@@ -136,7 +136,7 @@
-int cCtrlKeyboard::MapCodeToFunc(uint64 Code) {
+int cCtrlKeyboard::MapCodeToFunc(uint64_t Code) {
for (const tKbdMap *p = keyboardKbdMap; p->func != kfNone; p++) {
if (p->code == Code)
diff -ru control-0.0.2a-orig/keyboard.h control-0.0.2a/keyboard.h
--- control-0.0.2a-orig/keyboard.h 2006-12-03 16:44:46.170845357 +0100
+++ control-0.0.2a/keyboard.h 2006-12-03 16:45:14.261542675 +0100
@@ -30,11 +30,11 @@
cCtrlKeyboard();
virtual ~cCtrlKeyboard();
- bool intPut(uint64 Command, bool Repeat, bool Release);
+ bool intPut(uint64_t Command, bool Repeat, bool Release);
public:
- static bool Put(uint64 Command, bool Repeat = false, bool Release = false);
- static int MapCodeToFunc(uint64 Code);
+ static bool Put(uint64_t Command, bool Repeat = false, bool Release = false);
+ static int MapCodeToFunc(uint64_t Code);
};
diff -ru console-0.6.0-orig/menu.c console-0.6.0/menu.c
--- console-0.6.0-orig/menu.c 2006-12-03 15:28:31.522732562 +0100
+++ console-0.6.0/menu.c 2006-12-03 15:29:04.026492765 +0100
@@ -1193,7 +1193,7 @@
switch (BASICKEY(Key)) {
-case kKbd:{ uint64 buf = cKbdRemote::MapFuncToCode(KEYKBD(Key));
+case kKbd:{ uint64_t buf = cKbdRemote::MapFuncToCode(KEYKBD(Key));
WriteToConsole(buf);
// On every key press, we show the cursor immediately
@@ -1425,7 +1425,7 @@
-void cMenuConsole::WriteToConsole(const uint64& code) {
+void cMenuConsole::WriteToConsole(const uint64_t& code) {
unsigned char* data = (unsigned char*)(void*)&code;
diff -ru console-0.6.0-orig/menu.h console-0.6.0/menu.h
--- console-0.6.0-orig/menu.h 2006-12-03 15:28:31.526733517 +0100
+++ console-0.6.0/menu.h 2006-12-03 15:28:44.925932704 +0100
@@ -102,7 +102,7 @@
private:
void CaptureKeyboard();
void ReleaseKeyboard();
- void WriteToConsole(const uint64& code);
+ void WriteToConsole(const uint64_t& code);
bool TerminateConsole();
void AddSubMenu(cOsdObject* pSubMenu);
diff -ru remote-0.3.8-orig/remote.c remote-0.3.8/remote.c
--- remote-0.3.8-orig/remote.c 2006-12-03 16:24:36.438027599 +0100
+++ remote-0.3.8/remote.c 2006-12-03 16:26:19.222559030 +0100
@@ -56,7 +56,7 @@
// ---
-bool cRemoteGeneric::Put(uint64 Code, bool Repeat, bool Release)
+bool cRemoteGeneric::Put(uint64_t Code, bool Repeat, bool Release)
// ---
{
return cRemote::Put(Code, Repeat, Release);
@@ -72,7 +72,7 @@
#else
cTimeMs first, rate, timeout;
#endif
-uint64 code, lastcode = INVALID_KEY;
+uint64_t code, lastcode = INVALID_KEY;
bool repeat = false;
for (;;)
@@ -412,12 +412,12 @@
// ---
-uint64 cRemoteDevInput::getKey(void)
+uint64_t cRemoteDevInput::getKey(void)
// ---
{
struct input_event ev;
int n;
-uint64 code;
+uint64_t code;
do
n = read(fh, &ev, sizeof ev);
@@ -427,7 +427,7 @@
{
if (ev.value)
ev.value = 1;
-code = ((uint64)ev.value << 32) | ((uint64)ev.type << 16) | (uint64)ev.code;
+code = ((uint64_t)ev.value << 32) | ((uint64_t)ev.type << 16) | (uint64_t)ev.code;
}
else
code = INVALID_KEY;
@@ -443,7 +443,7 @@
// ---
Re: [vdr] Re: Problem with vdr-1.4.4-1 and extrecmenu
On Sunday 03 December 2006 15:36, Suur Karu wrote: > Peter Pinnau wrote: > > I just applied the vdr-1.4.4-1 maintainance patch and some plugins > > failed to compile. > > I could fix all problems within the plugins except for extrecmenu. > > Please advise me how fix compile errors with remote and streamdev plugins. > > Plugin streamdev: > make[1]: Entering directory > `/usr/local/src/vdr-1.4.4-1/PLUGINS/src/streamdev' > g++ -W -Woverloaded-virtual -O2 -c -D_GNU_SOURCE -DHAVE_AUTOPID > -I../../../include -I../../../../DVB/include -I. -o client/socket.o > client/socket.c > client/socket.c: In member function `bool cClientSocket::Command(const > std::string&, uint, uint)': > client/socket.c:57: error: `uint64' was not declared in this scope > client/socket.c:57: error: expected `;' before "elapsed" > client/socket.c:59: error: `elapsed' was not declared in this scope > make[1]: *** [client/socket.o] Error 1 > You should just replace every remaining uint64 by uint64_t. Matthias -- Matthias Schwarzott Gentoo Developer http://www.gentoo.org pgpJbEaYdCE8d.pgp Description: PGP signature ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Re: Problem with vdr-1.4.4-1 and extrecmenu
On Sunday 03 December 2006 15:53, Klaus Schmidinger wrote: > Udo Richter wrote: > > Klaus Schmidinger wrote: > >> Add the line > >> > >> #define uint64 uint64_t > >> > >> to VDR/tools.h. > >> > >> I'll add this in the next maintenance patch, too. > >> In the long run all plugins should change this to uint64_t, though. > > > > better, re-add it as typedef as it was before. Attached. > > I want to get rid of this completely, so it will be a #define > that, if possible, causes a compile time warning. And at some later > point I'll remove that #define. > > Klaus > Why not just keep it away. I think it is not too hard to replace that in the plugins. Matthias -- Matthias Schwarzott Gentoo Developer http://www.gentoo.org pgpnK51I5zQSp.pgp Description: PGP signature ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Re: vdr-vcd Polish translation patch
On Sunday 03 December 2006 14:16, Jakub Klawiter wrote: > Hello! > > Second version of i18n patch. > > Changes: > 1. added comments for all included languages strings > 2. One polish string was added in wrong place (as #8 not correct #9) Perhaps the plugin-writers directly should add the language-name instead of just todo as that confuses patch with context-diffs. Matthias -- Matthias Schwarzott Gentoo Developer http://www.gentoo.org pgphN75BHJfLN.pgp Description: PGP signature ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Parameter --manual-start/--timer-start (was: vdr shutdown handling / streamdev plugin)
On Saturday 02 December 2006 16:09, Udo Richter wrote: > Klaus Schmidinger wrote: > > The attached patch makes it call cPluginManager::Active() only > > if it really wants to shut down, and if there is actually an option > > for plugins to delay the shutdown (i.e. this is not a forced shutdown). > > > > If cPluginManager::Active() returns 'true' once, it waits for > > SHUTDOWNRETRY minutes before trying again. > > I'd suggest moving the if block a bit down in the code, at least behind > the manual start check, so plugins cannot interfere with this. I think To manual start check I have another idea. Perhaps vdr can get a parameter for setting explicitly manual-start or start based on timer. Then the startskript could check the time that was written into nvram/acpi/wherever and tell vdr if start was manual or not. Matthias -- Matthias Schwarzott Gentoo Developer http://www.gentoo.org ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] FF card A/V sync - in progress?
On Friday 01 December 2006 10:59, Halim Sahin wrote: > Hello, > > On Fr, Dez 01, 2006 at 10:46:15 +0100, Matthias Schwarzott wrote: > > On Friday 01 December 2006 03:04, Oliver Endriss wrote: > > > Carsten Koch wrote: > > > > > > Has anyone been able to identify the differences in the MPEG data if > > > (a) mplayer > > > (b) vdr > > > play the sample stream? > > > > My understanding of playback via mplayer is, that mplayer uses its > > included synchronization logic. > > ACK. > > > That means it demultiplexes its input (evtually transforms it to > > mpeg-1/2), > > then synchronizes it, and multiplexes it to pes. That means the FF-Card > > receives a synchron stream. > > Check your cpu-load during mplayer-playback. > Mplayer does not transcode something to mpeg1/2 etc because the cpuload > is > near 0. Ack. For playback of vdr-recordings you are right. I meant it can be eventually transcoded (playback of non mpeg2-files). Matthias -- Matthias Schwarzott Gentoo Developer http://www.gentoo.org pgpCYGXwTifb7.pgp Description: PGP signature ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] FF card A/V sync - in progress?
On Friday 01 December 2006 03:04, Oliver Endriss wrote: > Carsten Koch wrote: > > Has anyone been able to identify the differences in the MPEG data if > (a) mplayer > (b) vdr > play the sample stream? > My understanding of playback via mplayer is, that mplayer uses its included synchronization logic. That means it demultiplexes its input (evtually transforms it to mpeg-1/2), then synchronizes it, and multiplexes it to pes. That means the FF-Card receives a synchron stream. I think moving that synchronizing logic out of software-playback devices into vdr will solve that problem (and also other problems like audio near cutting marks). VDR however for now just forwards recorded data to FF-Card without ensuring any time-conditions. Matthias -- Matthias Schwarzott Gentoo Developer http://www.gentoo.org pgppHbieaY3Mx.pgp Description: PGP signature ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH] Polish translation for vdr-dxr3-0.2.6
Hi there! Jakub Klawiter from #gentoo-vdr supplied me with a polish-translation for vdr-dxr3-0.2.6. Matthias -- Matthias Schwarzott Gentoo Developer http://www.gentoo.org --- dxr3-0.2.6/dxr3i18n.c 2006-04-18 23:39:16.0 +0200 +++ dxr3-0.2.6/dxr3i18n-pl.c 2006-11-29 15:02:19.0 +0100 @@ -34,7 +34,7 @@ "", // Français "", // Norsk "DXR3-toiminnot", - "", // Polski + "DXR3", // Polski "DXR3", "", // ÅëëçíéêÜ (Greek) "", // Svenska @@ -57,7 +57,7 @@ "", // Français "", // Norsk "MPEG-purkukortti", - "", // Polski + "Sprzêtowy dekoder MPEG", // Polski "Descodificador MPEG Hardware", "", // ÅëëçíéêÜ (Greek) "", // Svenska @@ -80,7 +80,7 @@ "", // Français "", // Norsk "DXR3-toiminnot", - "", // Polski + "Ustawienia DXR3", // Polski "Opciones DXR3", "", // ÅëëçíéêÜ (Greek) "", // Svenska @@ -103,7 +103,7 @@ "", // Français "", // Norsk "Digitaalinen audioulostulo", - "", // Polski + "Cyfrowe wyj¶cie d¼wiêku", // Polski "Salida audio digital", "", // ÅëëçíéêÜ (Greek) "", // Svenska @@ -126,7 +126,7 @@ "", // Français "", // Norsk "Kortin järjestysnumero", - "", // Polski + "Numer karty", // Polski "Tarjeta", "", // ÅëëçíéêÜ (Greek) "", // Svenska @@ -149,7 +149,7 @@ "", // Français "", // Norsk "Näyttötila", - "", // Polski + "Tryb Video", // Polski "Modalidad vídeo", "", // ÅëëçíéêÜ (Greek) "", // Svenska @@ -172,7 +172,7 @@ "", // Français "", // Norsk "PAL", - "", // Polski + "PAL", // Polski "PAL", "", // ÅëëçíéêÜ (Greek) "", // Svenska @@ -195,7 +195,7 @@ "", // Français "", // Norsk "PAL60", - "", // Polski + "PAL60", // Polski "PAL60", "", // ÅëëçíéêÜ (Greek) "", // Svenska @@ -218,7 +218,7 @@ "", // Français "", // Norsk "NTSC", - "", // Polski + "NTSC", // Polski "NTSC", "", // ÅëëçíéêÜ (Greek) "", // Svenska @@ -241,7 +241,7 @@ "", // Français "", // Norsk "Palauta kortti alkutilaan", - "", // Polski + "Reset karty DXR3", // Polski "Reset hardware DXR3", "", // ÅëëçíéêÜ (Greek) "", // Svenska @@ -264,7 +264,7 @@ "", // Français "", // Norsk "Letterbox-näyttötilan pakotus päälle/pois", - "", // Polski + "Wymu¶ tryb panoramiczny", // Polski "Conmuta modalidad letterbox forzada", "", // ÅëëçíéêÜ (Greek) "", // Svenska @@ -287,7 +287,7 @@ "", // Français "", // Norsk "Kytke analoginen audioulostulo", - "", // Polski + "Prze³±cz na analogowe wyj¶cie d¼wiêku", // Polski "Selecciona salida audio analógica", "", // ÅëëçíéêÜ (Greek) "", // Svenska @@ -310,7 +310,7 @@ "", // Français "", // Norsk "AC3-ulostulo päälle", - "", // Polski + "Wyj¶cie AC3 w³±czone", // Polski "Activa salida AC3", "", // ÅëëçíéêÜ (Greek) "", // Svenska @@ -333,7 +333,7 @@ "", // Français "", // Norsk "AC3-ulostulo pois", - "", // Polski + "Wyj¶cie AC3 wy³±czone", // Polski "Desactiva salida AC3", "", // ÅëëçíéêÜ (Greek) "", // Svenska @@ -356,7 +356,7 @@ "", // Français "", // Norsk "Kytke digitaalinen audioulostulo", - "", // Polski + "Prze³±cz na cyfrowe wyj¶cie d¼wiêku", // Polski "Selecciona salida audio digital", "", // ÅëëçíéêÜ (Greek) "", // Svenska @@ -379,7 +379,7 @@ "", // Français "", // Norsk "DXR3: vapautetaan laitteet", - "", // Polski + "DXR3: zwalnianie urz±dzeñ", // Polski "DXR3: liberando dispositivo", "", // ÅëëçíéêÜ (Greek) "", // Svenska @@ -402,7 +402,7 @@ "", // Français "", // Norsk "Väriasetukset", - "", // Polski + "Ustawienia kolorów", // Polski "Ajustes color", "", // ÅëëçíéêÜ (Greek) "", // Svenska @@ -425,7 +425,7 @@ "", // Français "", // Norsk "Kirkkaus", - "", // Polski + "Jasno¶æ", // Polski "Luminosidad", "", // ÅëëçíéêÜ (Greek) "", // Svenska @@ -448,7 +448,7 @@ "", // Français "", // Norsk "Kontrasti", - "", // Polski + "Kontrast", // Polski "Contraste", "", // ÅëëçíéêÜ (Greek) "", // Svenska @@ -471,7 +471,7 @@ "", // Français "", // Norsk "Värikylläisyys", - "", // Polski + "Saturacja", // Polski "Saturación", "", // ÅëëçíéêÜ (Greek) "", // Svenska @@ -494,7 +494,7 @@ "", // Français "", // Norsk "Piilota valinta päävalikosta", - "", // Polski + "Ukryj w menu g³ównym", // Polski "Esconde entrada menú", "", // ÅëëçíéêÜ (Greek) "", // Svenska pgp1kOR9vqoq8.pgp Description: PGP signature ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] How to determine that VDR is ready to go ?
On Friday 10 November 2006 08:37, [EMAIL PROTECTED] wrote: > Hi, > I'd like to know when vdr is ready with its initializatin routines ( > starting plugins etc ). This is necessary to optimize the system boot up > time, because starting other services should wait until vdr is ready. Till > now I do a "sleep 15", but thats not really nice ;) A possible workaround > is to count the vdr pids and when this number does not grow for about 3 > seconds I decide that startup is done. Also I can search the syslog for > special messages, but thats all not very handy. Any other ideas are welcome > :) > Bye > Helmut > > Hi Helmut, you can wait for VDR responding to svdrp-connections. Matthias PS: Some plugins seem to do too much in its initialization routine. e.g. audiorecorder tries to load all filenames at start which takes for me around 30s. -- Matthias Schwarzott Gentoo Developer http://www.gentoo.org pgp85ccZHauX1.pgp Description: PGP signature ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] sourcecaps probelm!
On Tuesday 05 September 2006 10:14, JikJikMan wrote: > > Hi, > > The first thing I've tested was that patch, but it didn't work. In fact > when I wanted to apply the patch, it gave me errors and didn't work. > > Thanks. > > John. Hi, you can also try the version used inside gentoo-vdr-patchset for vdr-1.4.1 http://sources.gentoo.org/viewcvs.py/gentoo-vdr/vdr-patchsets/patches-1.4.1-1/030-hardware/ Matthias -- Matthias Schwarzott Gentoo Developer http://www.gentoo.org pgpB4xLpPd82O.pgp Description: PGP signature ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Which locale variables influence VDR?
On Wednesday 30 August 2006 17:48, Klaus Schmidinger wrote:
> Sebastian Kemper wrote:
> > Hi all,
> >
> > there's an open bug report for the Gentoo VDR ebuilds regarding locale
> > vars: http://bugs.gentoo.de/view.php?id=445
> >
> > Up till now everything gets set to POSIX and afterwards LC_COLLATE gets
> > set to whatever the user requests in the init script's config file. My
> > suggestion was to make LANG accessible in the config file as well,
> > because both are mentioned in the VDR docs.
> >
> > Is there any final wisdom on which locale vars influence VDR?
>
> VDR itself doesn't react on any environment settings, except when
> checking for the presence of UTF8 (which it refuses to run with).
>
> It's mainly the runtime library that reacts on these locale settings,
> using them to decide how to sort strings, for instance.
>
I think one part of the request was to find out which functions of libc/other
runtime libs exactly are influenced by locale-settings (and which settings?).
And if it only is searching/sorting why not just strip the utf8 out of the
locale-setting via code at the beginning of main and set charset to latin1 or
the one selected by lang.
Annotation: Why does vdr.c only check for LC_CTYPE and LANG as LC_ALL
overwrites them all when set.
Correct order for the check would be
if (LC_ALL set and contains utf8) ||
(LC_CTYPE set and contains utf8) ||
(LANG set and contains utf8)
{ error; }
I vote for at least correct usage of charsets by vdr, that has not to be utf8,
but will not be that more complicated once started. I could start a new
thread if this leads to any useful discussion.
Matthias
--
Matthias Schwarzott
Gentoo Developer
http://www.gentoo.org
pgp3wW8RvnS1z.pgp
Description: PGP signature
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
