[vdr] vdr 1.5.15 rpm packages available
Hi, I've updated the vdr15 package in the build service[1] to version 1.5.15. It's unpatched so don't hesitate to report bugs. The vdr-plugins package now also includes the xine plugin for xine version 1.1.10.1. cu Ludwig [1] http://download.opensuse.org/repositories/vdr/ -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr 1.6.0 - when ?
Klaus when will you plan to release the vdr developer version with support of the multiproto + h.264 + ts recording ? It will be the vdr 1.6.0 ? Igor ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.6.0 - when ?
Please read the following carefully: Date: Sun, 17 Feb 2008 15:46:42 +0100 From: Klaus Schmidinger <[EMAIL PROTECTED]> Subject: [vdr] [ANNOUNCE] VDR developer version 1.5.15 NOTE: = This is the final step towards a stable version 1.6.0. Please report any bugs as soon as possible, so that I can prepare a release candidate next weekend. If nothing unexpected happens, I plan to release version 1.6.0 on March 2. The changes since version 1.5.14: - Revoked the switch to the "multiproto" driver in order to make a new stable version before making this big switch and forcing all users to install a driver that is not yet in the kernel source. The removed code will reappear in version 1.7.0. István -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7.0 - when ?
On 02/19/08 13:05, Igor wrote: > sorry , I meant - when will be release the vdr 1.7.0 Shortly after 1.6.0. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7.0 - when ?
sorry , I meant - when will be release the vdr 1.7.0 -Original Message- From: FЭley IstvАn <[EMAIL PROTECTED]> To: Igor <[EMAIL PROTECTED]>, VDR Mailing List Date: Tue, 19 Feb 2008 12:52:53 +0200 (EET) Subject: Re: [vdr] vdr 1.6.0 - when ? > > Please read the following carefully: > > > Date: Sun, 17 Feb 2008 15:46:42 +0100 > > From: Klaus Schmidinger <[EMAIL PROTECTED]> > > Subject: [vdr] [ANNOUNCE] VDR developer version 1.5.15 > > > > NOTE: > > = > > > > This is the final step towards a stable version 1.6.0. > > > > Please report any bugs as soon as possible, so that I can prepare > > a release candidate next weekend. If nothing unexpected happens, > > I plan to release version 1.6.0 on March 2. > > > > The changes since version 1.5.14: > > > > - Revoked the switch to the "multiproto" driver in order to make a new > > stable > > version before making this big switch and forcing all users to install > > a > > driver that is not yet in the kernel source. The removed code will > > reappear > > in version 1.7.0. > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Event info in log
Event info has disappeared. In ver 1.4.x it is Feb 19 18:00:20 vdr vdr: [28242] channel 2 (YLE TV2) event Ti 19.02.2008 18:00-18:23 'Oikea kysymys' status 4 Feb 19 18:01:14 vdr vdr: [28242] channel 5 (YLE Teema) event Ti 19.02.2008 18:01-18:02 'Katsaus tulevaan' status 4 Feb 19 18:02:28 vdr vdr: [28242] channel 5 (YLE Teema) event Ti 19.02.2008 18:02-18:16 'opettaja.tv: Opinto-ohjaus' status 4 In ver. 1.5.x it is not, at least in 1.5.12 and 1.5.15 Log level ? or some other def ? -- [EMAIL PROTECTED] * Using HTML-mail is like breaking wind in a church * 60.2N 24.7E * it is not illegal, just extremely bad manners * ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Event info in log
Klaus Schmidinger wrote: > On 02/19/08 17:20, Lauri Tischler wrote: >> Event info has disappeared. In ver 1.4.x it is >> >> Feb 19 18:00:20 vdr vdr: [28242] channel 2 (YLE TV2) event Ti >> 19.02.2008 18:00-18:23 'Oikea kysymys' status 4 >> Feb 19 18:01:14 vdr vdr: [28242] channel 5 (YLE Teema) event Ti >> 19.02.2008 18:01-18:02 'Katsaus tulevaan' status 4 >> Feb 19 18:02:28 vdr vdr: [28242] channel 5 (YLE Teema) event Ti >> 19.02.2008 18:02-18:16 'opettaja.tv: Opinto-ohjaus' status 4 >> >> In ver. 1.5.x it is not, at least in 1.5.12 and 1.5.15 >> >> Log level ? or some other def ? > > Works fine here: > > Feb 19 17:14:41 video vdr: [31355] channel 1009 (ZDF) event Tue 19.02.2008 > 17:15-17:45 (VPS: 19.02 17:15) 'hallo deutschland' status 4 > > Note that this is only logged or channels that have timers. Ach, that was it, thanks.. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Event info in log
On 02/19/08 17:20, Lauri Tischler wrote: > Event info has disappeared. In ver 1.4.x it is > > Feb 19 18:00:20 vdr vdr: [28242] channel 2 (YLE TV2) event Ti > 19.02.2008 18:00-18:23 'Oikea kysymys' status 4 > Feb 19 18:01:14 vdr vdr: [28242] channel 5 (YLE Teema) event Ti > 19.02.2008 18:01-18:02 'Katsaus tulevaan' status 4 > Feb 19 18:02:28 vdr vdr: [28242] channel 5 (YLE Teema) event Ti > 19.02.2008 18:02-18:16 'opettaja.tv: Opinto-ohjaus' status 4 > > In ver. 1.5.x it is not, at least in 1.5.12 and 1.5.15 > > Log level ? or some other def ? Works fine here: Feb 19 17:14:41 video vdr: [31355] channel 1009 (ZDF) event Tue 19.02.2008 17:15-17:45 (VPS: 19.02 17:15) 'hallo deutschland' status 4 Note that this is only logged or channels that have timers. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR developer version 1.5.15 - compilation warnings
On 02/17/08 16:40, Dave P wrote:
> Compiling the new version on my 64-bit AMD processor produces the warnings
> below. I think they've probably been there for a while, I don't usually
> watch VDR compiling...
>
> # g++ -v
> Using built-in specs.
> Target: x86_64-mandriva-linux-gnu
> Configured
> with: ../configure --prefix=/usr --libexecdir=/usr/lib --with-slibdir=/lib64
> --mandir=/usr/share/man
> --infodir=/usr/share/info --enable-checking=release
> --enable-languages=c,c++,ada,fortran,objc,obj-c++,java
> --host=x86_64-mandriva-linux-gnu --with-cpu=generic --with-system-zlib
> --enable-threads=posix
> --enable-shared --enable-long-long --enable-__cxa_atexit
> --disable-libunwind-exceptions
> --enable-clocale=gnu --enable-java-awt=gtk
> --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre
> --enable-gtk-cairo --disable-libjava-multilib --enable-ssp --disable-libssp
> Thread model: posix
> gcc version 4.2.2 20071128 (prerelease) (4.2.2-3.1mdv2008.0)
>
> ---
> g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -c -DVDR_USER=\"vdr\"
> -DLIRC_DEVICE=\"/dev/lircd\" -DRCU_DEVICE=\"/dev/ttyS1\" -D_GNU_SOURCE
> -DVIDEODIR=\"/video/video\" -DCONFDIR=\"/video/video\"
> -DPLUGINDIR=\"./PLUGINS/lib\"
> -DLOCDIR=\"./locale\" -I/usr/include/freetype2 dvbsubtitle.c
> dvbsubtitle.c: In member function ‘int cDvbSubtitleConverter::Convert(const
> uchar*, int)’:
> dvbsubtitle.c:709: warning: format ‘%lld’ expects type ‘long long
> int’, but
> argument 3 has type ‘int64_t’
> dvbsubtitle.c: In member function ‘virtual void
> cDvbSubtitleConverter::Action()’:
> dvbsubtitle.c:776: warning: format ‘%lld’ expects type ‘long long
> int’, but
> argument 3 has type ‘int64_t’
> dvbsubtitle.c:776: warning: format ‘%lld’ expects type ‘long long
> int’, but
> argument 4 has type ‘int64_t’
> dvbsubtitle.c:776: warning: format ‘%lld’ expects type ‘long long
> int’, but
> argument 5 has type ‘int64_t’
> dvbsubtitle.c: In member function ‘int
> cDvbSubtitleConverter::ExtractSegment(const uchar*, int, int64_t)’:
> dvbsubtitle.c:845: warning: format ‘%lld’ expects type ‘long long
> int’, but
> argument 5 has type ‘int64_t’
>
>
> g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -c -DVDR_USER=\"vdr\"
> -DLIRC_DEVICE=\"/dev/lircd\" -DRCU_DEVICE=\"/dev/ttyS1\" -D_GNU_SOURCE
> -DVIDEODIR=\"/video/video\" -DCONFDIR=\"/video/video\"
> -DPLUGINDIR=\"./PLUGINS/lib\"
> -DLOCDIR=\"./locale\" -I/usr/include/freetype2 remote.c
> remote.c: In member function ‘bool cRemote::Put(uint64_t, bool, bool)’:
> remote.c:124: warning: format ‘%016LX’ expects type ‘long long unsigned
> int’, but argument 4 has type ‘uint64_t’
> remote.c:124: warning: format ‘%016LX’ expects type ‘long long unsigned
> int’, but argument 4 has type ‘uint64_t’
Apparently there are macros for this, like PRId64 and such.
But i don't like having to write something like
int64_t n = ...;
printf("Some number %" PRId64 "\n", n);
Don't know if the gettext mechanisms would be able to handle
tr("Some number %" PRId64 "\n")
I wonder why there ar no proper format specifiers for this.
Or are there?
Klaus
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] gentoo + vdr-1.5.12 + VDR_LOCAL_PATCHES_DIR
On Monday, 18. Februaryta 2008 13:06:35 Theunis Potgieter wrote: > ask your question on irc > > irc://irc.freenode.net > > #gentoo-vdr > > ask for nicknames: zzam or hd_brummy. Yeah, channel have quite many users logged in.. But nobody writes anything or answers to questions.. Dead channel? -- JJussi ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [ANNOUNCE] vdr-iptv-0.0.7
Hi all. We are pleased to announce a new release of vdr-iptv plugin. Iptv plugin is an attempt to add various IPTV reception capabilities to VDR. This version incorporates support for VDR version 1.5.15. Another new feature is configurable scanning of PIDs for streams where the full section information is not available. This version eliminates global sid scanning configuration option and instead provides per-channel settings for toggling sid and pid scanning. These settings are accessible from iptv plugin channel editor and are stored to channels.conf accordingly. For a sample of the new channels.conf format as well as full changelog and plugin download please see plugin homepage: http://www.saunalahti.fi/~rahrenbe/vdr/iptv/ Note: After new stable VDR version (1.6.0) is available support for VDR versions below 1.5.xx is likely to be dropped from future iptv plugin releases. -- Antti Seppälä ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR developer version 1.5.15 - compilation warnings
On Tuesday 19 Feb 2008, Klaus Schmidinger wrote:
> > remote.c:124: warning: format "%016LX" expects type "long long
> > unsigned int", but argument 4 has type "uint64_t"
>
> Apparently there are macros for this, like PRId64 and such.
> But i don't like having to write something like
>
> int64_t n = ...;
> printf("Some number %" PRId64 "\n", n);
It seems to be the POSIX way...
> Don't know if the gettext mechanisms would be able to handle
>
>tr("Some number %" PRId64 "\n")
It would probably be necessary to have multiple translations for the string
after macro expansion (negating the whole reason for having the macro in
the first place).
--
Dave
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR native mpeg decoder.
VDR include native mpeg decoder suport in their next versions for budgets cards ? Greetings. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR native mpeg decoder.
On Tue, Feb 19, 2008 at 08:14:04PM +, Albert Gall wrote: > VDR include native mpeg decoder suport in their next versions for > budgets cards ? I don't think so, but xine plugin or so can do it :-) -- Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org http://picasaweb.google.com/Gregoire.Favre ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR developer version 1.5.15 - compilation warnings
Klaus Schmidinger wrote:
> Apparently there are macros for this, like PRId64 and such.
> But i don't like having to write something like
>
> int64_t n = ...;
> printf("Some number %" PRId64 "\n", n);
>
> Don't know if the gettext mechanisms would be able to handle
>
>tr("Some number %" PRId64 "\n")
>
> I wonder why there ar no proper format specifiers for this.
> Or are there?
The gettext info page says:
>A similar case is compile time concatenation of strings. The ISO C
> 99 include file `' contains a macro `PRId64' that can be
> used as a formatting directive for outputting an `int64_t' integer
> through `printf'. It expands to a constant string, usually "d" or "ld"
> or "lld" or something like this, depending on the platform. Assume you
> have code like
>
> printf ("The amount is %0" PRId64 "\n", number);
>
> The `gettext' tools and library have special support for these
> `' macros. You can therefore simply write
>
> printf (gettext ("The amount is %0" PRId64 "\n"), number);
>
> The PO file will contain the string "The amount is %0\n". The
> translators will provide a translation containing "%0" as well,
> and at runtime the `gettext' function's result will contain the
> appropriate constant string, "d" or "ld" or "lld".
So translations should still work. The ugliness of those macros remains.
cu
Ludwig
--
(o_ Ludwig Nussel
//\ SUSE LINUX Products GmbH, Development
V_/_ http://www.suse.de/
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR developer version 1.5.15 - compilation warnings
Dave P wrote:
> On Tuesday 19 Feb 2008, Klaus Schmidinger wrote:
>
>> > remote.c:124: warning: format "%016LX" expects type "long long
>> > unsigned int", but argument 4 has type "uint64_t"
>>
>> Apparently there are macros for this, like PRId64 and such.
>> But i don't like having to write something like
>>
>> int64_t n = ...;
>> printf("Some number %" PRId64 "\n", n);
>
> It seems to be the POSIX way...
>
>> Don't know if the gettext mechanisms would be able to handle
>>
>>tr("Some number %" PRId64 "\n")
>
> It would probably be necessary to have multiple translations for the string
> after macro expansion (negating the whole reason for having the macro in
> the first place).
seems to promise that it works without multiple translations:
Assume you have code like
printf ("The amount is %0" PRId64 "\n", number);
The gettext tools and library have special support for these
macros. You can therefore simply write
printf (gettext ("The amount is %0" PRId64 "\n"), number);
The PO file will contain the string "The amount is %0\n". The
translators will provide a translation containing "%0" as
well, and at runtime the gettext function's result will contain the
appropriate constant string, "d" or "ld" or "lld".
gettext-0.14 (4 years old) already has this text, so it's probably safe
to use by now. (Apparently I have been living under a rock for the last
couple of years, I didn't even know about that PRId64 thing - thanks for
pointing it out.)
Regards...
Michael
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR developer version 1.5.15 - compilation warnings
On 02/19/08 21:26, Ludwig Nussel wrote:
> Klaus Schmidinger wrote:
>> Apparently there are macros for this, like PRId64 and such.
>> But i don't like having to write something like
>>
>> int64_t n = ...;
>> printf("Some number %" PRId64 "\n", n);
>>
>> Don't know if the gettext mechanisms would be able to handle
>>
>>tr("Some number %" PRId64 "\n")
>>
>> I wonder why there ar no proper format specifiers for this.
>> Or are there?
>
> The gettext info page says:
>
>>A similar case is compile time concatenation of strings. The ISO C
>> 99 include file `' contains a macro `PRId64' that can be
>> used as a formatting directive for outputting an `int64_t' integer
>> through `printf'. It expands to a constant string, usually "d" or "ld"
>> or "lld" or something like this, depending on the platform. Assume you
>> have code like
>>
>> printf ("The amount is %0" PRId64 "\n", number);
>>
>> The `gettext' tools and library have special support for these
>> `' macros. You can therefore simply write
>>
>> printf (gettext ("The amount is %0" PRId64 "\n"), number);
>>
>> The PO file will contain the string "The amount is %0\n". The
>> translators will provide a translation containing "%0" as well,
>> and at runtime the `gettext' function's result will contain the
>> appropriate constant string, "d" or "ld" or "lld".
>
> So translations should still work. The ugliness of those macros remains.
I agree. I wonder who came up with this idea?
Why would somebody totally break the printf mechanisms and introduce
such ugly macros?
I really hope we can avoid this insanity in VDR...
Klaus
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-sxfe don't start..
On Monday, 18. Februaryta 2008 12:42:07 Theunis Potgieter wrote: > I have Gentoo with xine-lib 1.1.9.1 and it works for me currently with > vdr-xineliboutput plugin. Right.. It's 1.1.10.1 what is problematic.. -- JJussi ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] gentoo + vdr-1.5.12 + VDR_LOCAL_PATCHES_DIR
zzam logged on 15min after you posted :) On 19/02/2008, JJussi <[EMAIL PROTECTED]> wrote: > > On Monday, 18. Februaryta 2008 13:06:35 Theunis Potgieter wrote: > > ask your question on irc > > > > irc://irc.freenode.net > > > > #gentoo-vdr > > > > ask for nicknames: zzam or hd_brummy. > > > Yeah, channel have quite many users logged in.. But nobody writes anything > or > answers to questions.. > > Dead channel? > > > -- > > JJussi > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR developer version 1.5.15 - compilation warnings
I am no expert, but if they teach STL for C++ why not use that instead which
is suppose to be type cast safe, instead of the older printf mechanism. I
don't want to start a war on what the best method is. But just wanted to
understand. Or would the cost in time be too high to convert everything?
my 2c
Theunis
On 19/02/2008, Klaus Schmidinger <[EMAIL PROTECTED]> wrote:
>
> On 02/19/08 21:26, Ludwig Nussel wrote:
> > Klaus Schmidinger wrote:
> >> Apparently there are macros for this, like PRId64 and such.
> >> But i don't like having to write something like
> >>
> >> int64_t n = ...;
> >> printf("Some number %" PRId64 "\n", n);
> >>
> >> Don't know if the gettext mechanisms would be able to handle
> >>
> >>tr("Some number %" PRId64 "\n")
> >>
> >> I wonder why there ar no proper format specifiers for this.
> >> Or are there?
> >
> > The gettext info page says:
> >
> >>A similar case is compile time concatenation of strings. The ISO C
> >> 99 include file `' contains a macro `PRId64' that can be
> >> used as a formatting directive for outputting an `int64_t' integer
> >> through `printf'. It expands to a constant string, usually "d" or "ld"
> >> or "lld" or something like this, depending on the platform. Assume you
> >> have code like
> >>
> >> printf ("The amount is %0" PRId64 "\n", number);
> >>
> >> The `gettext' tools and library have special support for these
> >> `' macros. You can therefore simply write
> >>
> >> printf (gettext ("The amount is %0" PRId64 "\n"), number);
> >>
> >> The PO file will contain the string "The amount is %0\n". The
> >> translators will provide a translation containing "%0" as well,
> >> and at runtime the `gettext' function's result will contain the
> >> appropriate constant string, "d" or "ld" or "lld".
> >
> > So translations should still work. The ugliness of those macros remains.
>
>
> I agree. I wonder who came up with this idea?
> Why would somebody totally break the printf mechanisms and introduce
> such ugly macros?
>
> I really hope we can avoid this insanity in VDR...
>
>
> Klaus
>
>
> ___
> vdr mailing list
> vdr@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
>
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR developer version 1.5.15 - compilation warnings
On 02/20/08 05:37, Theunis Potgieter wrote: > I am no expert, but if they teach STL for C++ why not use that instead > which is suppose to be type cast safe, instead of the older printf > mechanism. I don't want to start a war on what the best method is. But > just wanted to understand. Or would the cost in time be too high to > convert everything? I prefer the printf() format string way. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
