Re: [vdr] demux fails in burn plugin
On Fri, 2006-10-13 at 20:55 +0200, Leo Márquez wrote: Anyone has idea of this problem? From dvd.log: [...] [demux] Unknown parameter -v-filter [...] This parameters are called from vdrburn-dvd.sh vdrsync is the last 0.1.2.2 burn version is cvs. I need help please. Your vdrsync.pl is too old, see the burn plugin's README. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.4 and osdpip anyone?
On Sat, 2006-10-14 at 14:00 +, Harald Milz wrote: receiver.h:32: error: extra qualification ‘cOsdPipReceiver::’ on member ‘cOsdPipReceiver’ make[1]: *** [osd.o] Fehler 1 http://koti.mbnet.fi/kurg/vdr/vdr-osdpip-0.0.8-extraqual.patch ___ 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 Tuesday 30 January 2007 19:28, Marko Mäkelä wrote: On Sun, Jan 28, 2007 at 05:50:46PM +0100, Udo Richter wrote: Plugin activity in %ld minutes, shut down anyway? Liitännäinen toimii %ld minuutin päästä, sammutetaanko? IIRC plugin has been translated to laajennos elsewhere in VDR - no matter if it's laajennos or liitännäinen, consistency would be good. And toimii sounds a bit weird to me in this context, but I don't have better suggestions right now. ___ 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 Tuesday 30 January 2007 21:56, Rolf Ahrenberg wrote: Laajennos aktivoituu %ld kuluttua - sammutetaanko? Should be ...%ld minuutin kuluttua... ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR version 1.4.6 released
On Tuesday 06 March 2007, Stone wrote: On 3/3/07, Klaus Schmidinger [EMAIL PROTECTED] wrote: VDR version 1.4.6 is now available at Should the APIVERSION be incremented to 1.4.6? No, there were no API changes between 1.4.5 and 1.4.6. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [ANNOUNCE] vdr-dxr3 version 0.2.7
Version 0.2.7 of the vdr-dxr3 plugin is out. Changes since 0.2.6: - add Polish translation (Mikolaj Tutak) - sync make install with VDR 1.4.2-2 (Ville Skyttä) - use cCondWait::SleepMs() instead of usleep (Ville Skyttä) - avoid deprecation warnings with newish libavcodec (Ville Skyttä) - add brightness/contrast/saturation settings to setup (Ville Skyttä) - apply more settings immediately from setup menu (Ville Skyttä) - apply AC3 and WSS patches which were in patches/ in previous releases - add setup option for enabling/disabling WSS (Ville Skyttä) - various minor tweaks Until I can reach Christian and/or he has time to upload the release tarball to the usual location @ SourceForge, it's available at http://cachalot.mine.nu/src/dxr3/vdr-dxr3-0.2.7.tgz ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Changing location of /srv/vdr
On Friday 08 June 2007, Andreas Mueller wrote: If you are using the RPM provided by Fedora Extras, you can change this in /etc/sysconfig/vdr, there should be a line starting with VDR_OPTIONS. But why don't you just create /srv/vdr? If you're using the Fedora (Extras) package, it should have created the dir for you when you installed the package, see rpm -ql vdr. What does rpm -V vdr output? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR exited with status 134
On Sunday 10 June 2007, Kartsa wrote: I've got fedora with runvdr from fedora vdr package and it tries to restart VDR if exit code is something else than 0, 2 or 137. Sometimes the exit code is 137 but most of the time it is 134. This causes VDR to restart (or runvdr makes VDR to restart) and dvb drivers to reload. What does exit code 134 mean? From man bash: The return value of a simple command is its exit status, or 128+n if the command is terminated by signal n. So 134 - 128 = 6, SIGABRT (kill -l 6). info SIGABRT says: This signal indicates an error detected by the program itself and reported by calling `abort'. Why is exit code sometimes 137 and most of the times 134? It's 137 when killproc (see /etc/init.d/functions) invoked from /etc/init.d/vdr gets tired of waiting for kill -TERM to result in vdr to shut down and issues a kill -KILL to really get rid of it. It's 134 when you got a crash caused by SIGABRT. If you wish to debug it further, uncomment DAEMON_COREFILE_LIMIT=unlimited at end of /etc/sysconfig/vdr and watch if core dumps start to appear in /tmp. What should exit code be when VDR is shutting down either because the user pushed power button or because there has been no user activity? 0 if all went well (and if I remember correctly). I've replaced fedoras VDR with my own vdr-1.4.6 compilation (due to some plugins not in fedora packaging). In my experience, crashes at vdr shutdown are almost always caused by plugin bugs. I'm not aware of any such in the Fedora plugin packages at the moment. By the way, which packaged plugins are you missing/adding? The last crash-at-shutdown bug I saw was in ttxtsubs; in case you're using it, my patch for the crash is included in Rofa's kermanekka edition (http://www.saunalahti.fi/~rahrenbe/vdr/patches/, Fedora 7 packages at http://cachalot.mine.nu/ and possibly sometime soonish in Fedora proper). Also, just in case you weren't aware of it, if your additional plugins don't require patching vdr itself (patches for subtitles and ttxtsubs plugins are already included), you can use Fedora's vdr and vdr-devel packages and build additional plugins for it instead of building a whole vdr of your own, see /usr/share/doc/vdr-*/README.package ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR exited with status 134
On Monday 11 June 2007, Kartsa wrote: Ville Skyttä kirjoitti: If you wish to debug it further, uncomment DAEMON_COREFILE_LIMIT=unlimited at end of /etc/sysconfig/vdr and watch if core dumps start to appear in /tmp. I'll give it a try. Would -t switch be helpfull with shutdown? No idea, I've never used that switch myself. One possibly way to find out if the abort is because of some plugin is to watch /var/log/messages when shutting down vdr and to see what the last output before runvdr: VDR exited with status ... is. If it's not vdr: [...] exiting but rather vdr: [...] stopping plugin: foo or vdr: [...] deleting plugin: foo, it's pretty likely that the foo plugin is somehow involved. I am compiling vdr my self mostly because I like Soppalusikka :) I think there was some other reason(s) as well but I can not recall what :) I had newer actually read the README.package and it was wery illuminating. Maybe I'll have to start using readymade packages and give up using Soppalusikka :( I don't think soppalusikka (in case you're referring to the skin) requires any patches to vdr, so it should be usable and buildable with the packaged version too. Some dirs are obviously a bit different than in the install instructions, but README.package and rpm -ql vdr should help with those. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] WSS signaling with DXR3 cards
On Sunday 05 August 2007, Kartsa wrote: At first I had problems with getting DXR card to work with fedora core 7 but now everything is otherwise fine but wss signaling does not seem to work. Do I need to patch the kernel or em8300 or something to make it work? Or do I still have to compile the CVS version of dxr3? Any pointers would be preciated. The WSS patches are included in the em8300 modules shipped in Fedora, and version 0.2.7 of the DXR3 plugin contains the WSS patch also upstream, no patchwork needed. Note that (AFAIK) you need an ADV7170 based DXR3/H+ for this WSS stuff to work, and it needs to be enabled in the DXR3 plugin's setup through VDR's OSD. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] WSS signaling with DXR3 cards
On Friday 10 August 2007, Kartsa wrote: Ville Skyttä kirjoitti: On Sunday 05 August 2007, Kartsa wrote: At first I had problems with getting DXR card to work with fedora core 7 but now everything is otherwise fine but wss signaling does not seem to work. Do I need to patch the kernel or em8300 or something to make it work? Or do I still have to compile the CVS version of dxr3? Any pointers would be preciated. The WSS patches are included in the em8300 modules shipped in Fedora, and version 0.2.7 of the DXR3 plugin contains the WSS patch also upstream, no patchwork needed. Note that (AFAIK) you need an ADV7170 based DXR3/H+ for this WSS stuff to work, and it needs to be enabled in the DXR3 plugin's setup through VDR's OSD. Thanks for the prompt responce. Did not have chance to check the card before now. It was not an ADV7170 based soI changed it to ADV7175. No luck though. Hm, so you have an ADV7175 based one currently? Sorry, I don't think that helps - again, as far as I know, the WSS stuff only works with ADV7170 based cards. The patched adv717x driver never even tries to set the WSS mode for any other DXR3/H+'s. I don't have any others than a couple of ADV7170 based cards so I can't test with anything else. It could be useful to ask on dxr3-devel or dxr3-plugin lists if someone can help out more. Any other hints? What should the parameters for adv717x module be? There are no module parameters that affect WSS. Programs using the driver set the desired WSS mode themselves. The patched em8300setup program can be used for this too if you want to try out something. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] DVD plugin stutters
On Monday 03 September 2007, Kartsa wrote: My audio replay is kinda stuttering when replaying DVD's with dvd plugin. It's like the volume would be waving up and down with a rate of about 5Hz. I have a DXR3 and I have tried all possible things I could think of. Anybody had similar problems? Yes, see the dxr3 plugin's TROUBLESHOOTING file. NPTL (in case it's the problem - I haven't used a non-NPTL system in quite a while) can't be disabled on Fedora 7 though. I thought I'd try using mplayer plugin for DVDplayback but for some reason my mplayer plugin does not want to play DVD's (don't know why all settings should be correct in mplayer.sh.conf, even set debug to true). Last time I tried it (I suppose you're talking about the vdr-mplayer package from livna.org) it did work for me out of the box. Mplayer didn't have DVD menu support back then - and I don't know if it has nowadays - so I lost interest to experiment further pretty quickly. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] DVD plugin stutters
On Monday 03 September 2007, Kartsa wrote: Ville Skyttä kirjoitti: Yes, see the dxr3 plugin's TROUBLESHOOTING file. NPTL (in case it's the problem - I haven't used a non-NPTL system in quite a while) can't be disabled on Fedora 7 though. There were no mention about NPTL. Also there were no mention about a stuttering audio (or similar to my problem). Sure there is. Copy-pasting from it: * If VDR becomes unresponsive when using the MP3 or Muggle plugins, or there are stuttering/stickiness problems with the DVD plugin, and you're using a NPTL system, try disabling NPTL if possible (eg. export LD_ASSUME_KERNEL=2.4.19 before starting VDR). NPTL cannot be disabled on all systems, and anyway it would be very nice if someone found what the problem is, and would submit a patch. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] DVD plugin stutters
On Monday 03 September 2007, Kartsa wrote: Igor kirjoitti: from livna.org) it did work for me out of the box. Mplayer didn't have DVD menu support back then - and I don't know if it has nowadays - so I lost interest to experiment further pretty quickly. now MPlayer has support for the navigation in DVD menu, you should compile it with the option --enable-dvdnav here you can see screenshot http://www.linux.org.ru/gallery/biglIDbEY.jpg So it wont support navigation when installing from livna.org? I haven't tested it in ages, but it does have a dependency on libdvdnav so maybe it supports that nowadays. If not - bugzilla.livna.org ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] DVD plugin stutters
On Monday 03 September 2007, Kartsa wrote: I decided to update my mplayer. Now the bahaviour changed so that the dvd starts but the screen stays black. [...] Seems like dxr3 is not supported. If you built it yourself, try yum install em8300-devel and then configure and build it again, look for this in ./configure output: Checking for DXR3/H+ ... yes ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH] Make kPlay start playback from recording list
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.
--- menu.c~ 2006-12-02 13:12:02.0 +0200
+++ menu.c 2007-10-14 22:03:06.0 +0300
@@ -2074,6 +2074,7 @@
if (state == osUnknown) {
switch (Key) {
+ case kPlay:
case kOk: return Play();
case kRed:return (helpKeys 1 RecordingCommands.Count()) ? Commands() : Play();
case kGreen: return Rewind();
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-iptv-0.0.2
On Sunday 28 October 2007, Udo Richter wrote: I have an experimental version of my streamplayer plugin that allows to use RTSP streaming, based on the liblivemedia library. Though this is not fully working yet due to mysterious stream throughput issues, I think that the decision to use liblivemedia as protocol layer is a good way to go. FWIW, not that I really know about either or about the reasoning, but there seems to be some kind of movement towards using libnemesi instead of liblivemedia (I assume this is the live555 thingy) in projects such as mplayer and ffmpeg recently. http://live.polito.it/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] DVD-Plugin compile failure
On Saturday 17 November 2007, Simon Baxter wrote: I've built a new VDR box, and can't get the dvd plugin to compile. kernel=2.6.22.9-61.fc6 libdvdnav-0.1.10-3.20070503.lvn6 libdvdnav-devel-0.1.10-3.20070503.lvn6 libdvdcss-1.2.9-4.lvn6 libdvdcss-devel-1.2.9-4.lvn6 libdvdread-0.9.7-2.fc6 libdvdread-devel-0.9.7-2.fc6 [EMAIL PROTECTED] dvd-0.3.6_b03]# make g++ -g -O2 -Wall -Woverloaded-virtual -fPIC -O3 -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='dvd' -I../../../../DVB/include -I../../../include -I../../../../DVB/include -I/usr/include/dvdnav dvd.c /usr/include/dvdnav/dvdnav.h:367: error: expected ',' or '...' before 'this' make: *** [dvd.o] Error 1 any ideas? Bug in that libdvdnav snapshot: http://bugzilla.livna.org/show_bug.cgi?id=1528 A fixed build for FC-6 is on its way but (like you may already know) FC-6 will go end of life in a couple of weeks so it could be a good idea to upgrade. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] PANIC: watchdog timer expired - exiting
On Sunday 02 December 2007, Darren Salt wrote: I demand that Klaus Schmidinger may or may not have written... On 12/02/07 14:34, Darren Salt wrote: I demand that Klaus Schmidinger may or may not have written... I'll make it a 5 ms limit then, to allow default kernels to work. Valid HZ options are 100, 250, 300 and 1000, unless overridden by an arch-specific Kconfig file. (AFAICS, only mips does this, offering 48, 100, 128, 250, 256, 1000 and 1024.) Not that I really know much at all about this, but how would this change behave with NOHZ kernels? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Crash while reading channels.conf
Hello,
I've started experiencing some weird crashes right after my VDR box boots.
The crash occurs when reading channels.conf, but not on every reboot. VDR
starts up automatically, and if it starts crashing while reading
channels.conf, no restarts appear to work, another reboot is needed. On the
next reboot, channels.conf is unchanged but the crash may no longer occur.
This is on Fedora 8 i386, VDR 1.4.7 with a bunch of patches and plugins.
There's only one patch affecting channels.c but I don't see how it could have
anything to do with the crash.
Backtrace attached; line 752 in my channels.c is
while ((q = strtok_r(p, ,, strtok_next)) != NULL) {
(the one for the apids loop)
The channels.conf line in the backtrace is the first one in my channels.conf.
At bootup, vdradmin-am starts slightly after VDR so I guess it could be
possible that it's trying to do some SVDRP commands at the same time when
things go south.
Any clues?
#0 0x00325e04 in strtok_r () from /lib/libc.so.6
No symbol table info available.
#1 0x0808b4bc in cChannel::Parse (this=0x994d688,
s=0x994d228 TV1;YLE:274000:C0M128:C:6900:512:650=fin:2321:0:17:0:1:0)
at channels.c:752
q = 0x994da20 650=fin
strtok_next = 0x994d688 ¸V\021\b
p = value optimized out
dpidbuf = 0x0
NumApids = 0
parambuf = 0x994d9f0 C0M128
apidbuf = 0x994da20 650=fin
namebuf = 0x994d9e0 TV1;YLE
sourcebuf = 0x994da00 C
vpidbuf = 0x994da10 512
caidbuf = 0x994da30 0
fields = value optimized out
ok = true
#2 0x0808c2c3 in cConfigcChannel::Load (this=0x81d4560,
FileName=0x994d460 /etc/vdr/channels.conf, AllowComments=false,
MustExist=true) at config.h:122
l = (cChannel *) 0x994d688
s = 0x994d228 TV1;YLE:274000:C0M128:C:6900:512:650=fin:2321:0:17:0:1:0
line = 1
ReadLine = {size = 120,
buffer = 0x994d228 TV1;YLE:274000:C0M128:C:6900:512:650=fin:2321:0:17:0:1:0}
f = (FILE *) 0x994ac38
result = value optimized out
#3 0x0808b999 in cChannels::Load (this=0x81d4560,
FileName=0x994d460 /etc/vdr/channels.conf, AllowComments=false,
MustExist=true) at channels.c:892
No locals.
#4 0x08107ae8 in main (argc=) at vdr.c:531
savedTm = {c_iflag = 135351912, c_oflag = 135034472,
c_cflag = 135307124, c_lflag = 136130584, c_line = 216 'Ø', c_cc = {177 '±',
244 'ô', 191 '¿', 43 '+', 78 'N', 17 '\021', 8 '\b', 0 '\0', 0 '\0',
0 '\0', 0 '\0', 120 'x', 49 '1', 29 '\035', 8 '\b', 232 'è', 177 '±',
244 'ô', 191 '¿', 193 'Á', 109 'm', 8 '\b', 8 '\b', 0 '\0', 0 '\0',
0 '\0', 0 '\0', 0 '\0', 0 '\0', 0 '\0', 0 '\0', 24 '\030'},
c_ispeed = 135351737, c_ospeed = 3020485}
HasStdin = false
StartedAsRoot = value optimized out
VdrUser = 0x81a719c vdr
SVDRPport = 2001
AudioCommand = 0x0
ConfigDirectory = 0x81a77a7 /etc/vdr
EpgDataFileName = 0x81a7688 epg.data
DisplayHelp = false
DisplayVersion = false
DaemonMode = false
SysLogTarget = 8
MuteAudio = false
WatchdogTimeout = 0
Terminal = 0x0
Shutdown = 0xbff4bcee vdr-shutdown.sh
UseKbd = false
LircDevice = 0x81a76ad /dev/lircd
RcuDevice = 0x0
PluginManager = {_vptr.cPluginManager = 0x819fa58,
static pluginManager = 0xbff4b104, directory = 0x992ac60 /usr/lib/vdr,
lastHousekeeping = 1197042263, nextHousekeeping = -1,
dlls = {cListcDll = {cListBase = {_vptr.cListBase = 0x819fb20,
objects = 0x992ac88, lastObject = 0x992b078,
count = 10}, No data fields}, No data fields}}
ExitCode = value optimized out
c = value optimized out
LangEnv = value optimized out
Menu = value optimized out
LastChannel = value optimized out
LastTimerChannel = value optimized out
PreviousChannel = {1, 1}
PreviousChannelIndex = value optimized out
LastChannelChanged = 1197042263
LastActivity = value optimized out
LastCamMenu = value optimized out
MaxLatencyTime = value optimized out
ForceShutdown = value optimized out
UserShutdown = value optimized out
InhibitEpgScan = value optimized out
IsInfoMenu = value optimized out
CurrentSkin = value optimized out
long_options = {{name = 0x8188c57 audio, has_arg = 1, flag = 0x0,
val = 97}, {name = 0x81a7936 config, has_arg = 1, flag = 0x0, val = 99},
{name = 0x81a793d daemon, has_arg = 0, flag = 0x0, val = 100}, {
name = 0x81a7944 device, has_arg = 1, flag = 0x0, val = 68}, {
name = 0x81a794b epgfile, has_arg = 1, flag = 0x0, val = 69}, {
name = 0x81a7953 grab, has_arg = 1, flag = 0x0, val = 103}, {
name = 0x81a7958 help, has_arg = 0, flag = 0x0, val = 104}, {
name = 0x81a795d lib, has_arg = 1, flag = 0x0, val = 76}, {
name = 0x81a7961 lirc, has_arg = 2, flag = 0x0, val =
Re: [vdr] vdr-xine and xineliboutput bug? - Re: kernel bug in 2.6.23.1-49.fc8 when switching DVB outputs
On Monday 24 December 2007, Simon Baxter wrote: [...] any ideas?? 1) Try the current Fedora 8 update kernel, currently 2.6.23.9-85.fc8 2) If it happens with it too - https://bugzilla.redhat.com ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Crash while reading channels.conf
On Friday 07 December 2007, Ville Skyttä wrote:
Hello,
I've started experiencing some weird crashes right after my VDR box boots.
The crash occurs when reading channels.conf, but not on every reboot. VDR
starts up automatically, and if it starts crashing while reading
channels.conf, no restarts appear to work, another reboot is needed. On
the next reboot, channels.conf is unchanged but the crash may no longer
occur.
This is on Fedora 8 i386, VDR 1.4.7 with a bunch of patches and plugins.
There's only one patch affecting channels.c but I don't see how it could
have anything to do with the crash.
Backtrace attached; line 752 in my channels.c is
while ((q = strtok_r(p, ,, strtok_next)) != NULL) {
(the one for the apids loop)
I'm pretty certain this was triggered by a hardware problem in my box, after
making some changes I haven't seen it in a while.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [ANNOUNCE] muggle 0.1.12
Muggle 0.1.12 has been released. 2008-01-04: Version 0.1.12-BETA - Fix compilation and some compiler warnings. - Fix build with FLAC++ = 1.1.3. - Rename image_convert.sh to muggle-image-convert, install it in make install, make it a bit more robust. Get it at http://sourceforge.net/project/showfiles.php?group_id=203825package_id=243035release_id=565728 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] improved LIRC remote for VDR-1.5.12
On Saturday 12 January 2008, Reinhard Nissl wrote: I think, the LIRC protocol misses a timestamp for each button press. Or an even more favorable solution would be to put the timeout and frequency processing into LIRC and have VDR to process each key as it arrives, just like with the KBD remote. Would using liblirc_client instead of the current homebrew implementation help out with this? Also, somewhat off topic: when running powertop[1] on my VDR box, I see lircd waking up the CPU from idle about 1000 times a second while VDR is connected to it: Top causes for wakeups: 54.3% (988.1) lircd : schedule_timeout (process_timeout) 28.5% (518.4) vdr : futex_wait (hrtimer_wakeup) [...] I already tried adding some cCondWait::SleepMs's to VDR's lirc action loop but it didn't seem to have any effect. Any ideas whether this is something that VDR could do anything about, or if it's a LIRC internal thing? [1] http://www.lesswatts.org/projects/powertop/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] improved LIRC remote for VDR-1.5.12
On Saturday 12 January 2008, Reinhard Nissl wrote: Ville Skyttä schrieb: Also, somewhat off topic: when running powertop[1] on my VDR box, I see lircd waking up the CPU from idle about 1000 times a second while VDR is connected to it: Top causes for wakeups: 54.3% (988.1) lircd : schedule_timeout (process_timeout) 28.5% (518.4) vdr : futex_wait (hrtimer_wakeup) [...] I already tried adding some cCondWait::SleepMs's to VDR's lirc action loop but it didn't seem to have any effect. Any ideas whether this is something that VDR could do anything about, or if it's a LIRC internal thing? Well VDR's lirc action loop uses a timeout only when it needs to generate a keyup event after a key repeat event. Otherwise it blocks in cFile::FileReady's select() until a button gets pressed on the remote. Try running irw instead of VDR and check powertop again. Yep, same thing with irw so I suppose this needs to be addressed in LIRC, not VDR. Thanks. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.5.13 dvb-s2 H.264 patch from Reinhard
On Sunday 20 January 2008, Gregoire Favre wrote: Oops, no, there is a problem when using http://users.tkk.fi/~rahrenbe/vdr/vdr-1.5.13-liemikuutio-1.17.diff.gz which is a must have for me... I like the idea of Hard Link Cutter, but I will stay with the cut_in_place for the time being. At least with the 1.4.x versions, modifying the hard link cutter patch so that it applies on top of liemikuutio patched VDR is trivial, just a matter of removing some diff context from the hard link cutter menu.c hunk. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Disappearing audio
On Sunday 20 January 2008, JJussi wrote: I updated this week my Gentoo vdr system and now if I use fast forward (or rewind) I loose audio. So after fast forward when I come back to normal speed playback, there is no sound anymore. After killing vdr-sxfe and starting it again, I have sound again. Jumping backward or forward don't make audio to disappear. Maybe a xine-lib 1.1.9+ problem? http://thread.gmane.org/gmane.comp.video.xine.devel/17621 http://thread.gmane.org/gmane.comp.video.xine.devel/17682 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] need help with UTF-8 error - vdr: please turn off UTF-8 before starting VDR
On Sunday 27 January 2008, techno wrote: Hello, When I run vdr from the command line I get this message: vdr: please turn off UTF-8 before starting VDR How do I turn off UTF-8? Why would I want to? Can someone tell me how to fix it? I have just installed it using YUM rpm, and I am running Fedora 7 if that helps. If you start vdr using the included init script (/etc/init.d/vdr), this and a bunch of other useful things will be taken care of for you automatically. ___ 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 Sunday 03 February 2008, Klaus Schmidinger wrote: Should there be a stable version 1.6.0 now, based on what's in version 1.5.14, but without DVB-S2 or even H.264 support? +1 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Wakeup methods
On Monday 11 February 2008, Luca Olivetti wrote: En/na Kartsa ha escrit: I can read germany but I do not understand it :). But understood that I could use that script to test acpi. Well this did not work. I did check that the time was actually written in /proc/acpi/alarm. Still not waking up. IIRC, acpi wakeup wouldn't work here if I didn't enable a wake up time before in the bios setup. Same thing here. I don't remember what it was called in my VDR box's BIOS, but something non-obvious anyway :P OTOH it does work now, but it doesn't take the date into account, so if there's no timer in the next 24 hours I schedule a wake-up at 21:00. IIRC cat /proc/acpi/alarm always displays bogus dates for me, but wakeup does work as expected anyway. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Wakeup methods
On Tuesday 12 February 2008, Kartsa wrote: So some say wakeup must be enabled in bios and some that it must be disabled. Tried both with writing twice to /proc/acpi/alarm. Still no luck. Any other suggestions? Anybody? BIOS updates? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Wakeup methods
On Wednesday 13 February 2008, Kartsa wrote: But this aproach (replace now with vdr shutdown info) creates a (one hour) problem when summer time comes. Doesnt it? Quite likely. But I suppose you shouldn't need any hacks like that if the system knows that the hardware clock is in UTC (UTC=true in /etc/sysconfig/clock) and I think the shutdown support scripts from the Fedora VDR packages should also work as is in that case. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Wakeup methods
On Wednesday 13 February 2008, Kartsa wrote: Tero Purra kirjoitti: I had to disable update HWCLOCK at shutdown -feature before ACPI wakeup started to work. I'm using gentoo and the feature is found /etc/conf.d/clock Does not exist in FC8. Atleast not in that position. In Fedora /sbin/halt.local runs after hwclock (see /etc/init.d/halt) so this is not an issue if you're writing to /proc/acpi/alarm from there. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH] Fix build with GCC 4.3's cleaned up C++ headers
Hello, Attached is a patch that fixes VDR 1.4.7's build for me on Fedora 9 devel against GCC 4.3's cleaned up C++ headers. The build errors were due to INT_MAX not being defined. diff -up vdr-1.4.7/epg.c~ vdr-1.4.7/epg.c --- vdr-1.4.7/epg.c~ 2006-10-28 12:12:42.0 +0300 +++ vdr-1.4.7/epg.c 2008-02-14 19:12:26.0 +0200 @@ -12,6 +12,7 @@ #include epg.h #include ctype.h +#include limits.h #include time.h #include libsi/si.h #include timers.h diff -up vdr-1.4.7/menuitems.h~ vdr-1.4.7/menuitems.h --- vdr-1.4.7/menuitems.h~ 2008-02-14 19:10:06.0 +0200 +++ vdr-1.4.7/menuitems.h 2008-02-14 19:12:39.0 +0200 @@ -10,6 +10,7 @@ #ifndef __MENUITEMS_H #define __MENUITEMS_H +#include limits.h #include osdbase.h extern const char *FileNameChars; ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-sxfe don't start..
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. ___ 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 February 2008, Darren Salt wrote: I demand that Ville Skyttä may or may not have written... 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. They are, but you should not use pkg-config unless your plugin is not 1.1-compatible. Hmm... I'm having some problems parsing that, do you mean that only plugins that are 1.2-compatible but not 1.1-compatible should be using pkg-config? If not, could you rephrase? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] DXR3 and subtitles in 1.5.x
On Thursday 06 March 2008, Luca Olivetti wrote: Yes, it should be in cvs, the only thing missing is calling the cOsd constructor with Level instead of 0 That's right - all patches posted for the DXR3 plugin are now in CVS, thanks again to everyone involved. However, Luca and Ville A, you seem to be using different patches to VDR's dvbsubtitle.c - looks like Luca's contains all the changes in Ville A's, but comments those out and uses something else instead. Unless a better fix emerges, I'm quite interested in including one of these in the upcoming VDR 1.6.x package for Fedora and also ship it in the DXR3 plugin tarball (possibly modified so that it's only enabled if the primary device is a DXR3 if possible), but I don't quite follow which would be the preferred one. Could you compare and comment (off-list is fine, this may be getting a bit off topic for the general VDR public)? http://article.gmane.org/gmane.linux.vdr/35860 http://article.gmane.org/gmane.linux.vdr/35881 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH] Use pkg-config to find freetype/fontconfig flags
Hello, The attached patch makes VDR's Makefile use pkgconfig for finding libs and include dirs of freetype and fontconfig instead of making assumptions. --- Makefile~ 2008-02-29 23:43:03.0 +0200 +++ Makefile 2008-03-06 21:29:58.0 +0200 @@ -20,8 +20,8 @@ MANDIR = $(PREFIX)/share/man BINDIR = $(PREFIX)/bin LOCDIR = ./locale -LIBS = -ljpeg -lpthread -ldl -lcap -lrt -lfreetype -lfontconfig -INCLUDES = -I/usr/include/freetype2 +LIBS = -ljpeg -lpthread -ldl -lcap -lrt $(shell pkg-config --libs freetype2 fontconfig) +INCLUDES = $(shell pkg-config --cflags-only-I freetype2 fontconfig) PLUGINDIR= ./PLUGINS PLUGINLIBDIR= $(PLUGINDIR)/lib ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] Use pkg-config to find freetype/fontconfig flags
On Friday 07 March 2008, Klaus Schmidinger wrote: Instead of having all applications work around freetyp2's weird include macro stuff, why not complain to the freetype2 people and have them provide just a plain old freetype2.h that can be included like any other header file? Sorry for being ignorant, but I have this tendency to try to solve problems at their root. FWIW, I think providing a pkgconfig file is very much a root solution (ditto $foo-config scripts, but *.pc are much simpler to write and read and have a unified interface). Lots of library packages (and also some others) provide them nowadays which is great, and has made the things you express dissatisfaction with in the above as well as other similar ones pretty much moot. In fact, I think VDR should also provide a *.pc file. I ship one in Fedora's VDR packages, and a good deal of it would be applicable to upstream VDR too. Just let me know if you're interested and I'll have a look at making a upstreamable version of it. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] Use pkg-config to find freetype/fontconfig flags
On Monday 10 March 2008, Udo Richter wrote: clemens kirchgatterer wrote: structure bin, lib, include, share, ... if i want to compile software using the libs (and headers) of opt1 i only have to do PKG_CONFIG_PATH=/opt1 make and to start that program LD_LIBRARY_PATH=/opt1 prog. given the Makefile of prog uses pkg-config properly. And thats so much better than make INCLUDES=/opt1/usr/include? If make INCLUDES=... or manually changing INCLUDES in Makefile [0] works better for you than using pkg-config, by all means use/do it. The patch I posted does not prevent that; it's possible just like it was before the patch. The intention of the patch is to make it more likely that there would be one thing less to touch when building VDR for most users. I think that's much more likely when using pkg-config than when hardcoding stuff; that's why I'm suggesting it to be used by default rather than telling people to build with make INCLUDES=$(pkg-config --cflags-only-I freetype2 fontconfig) ... My point is: There's one version of the libs that is in the default library search path. Shouldn't there also be one header in the default header search path then? Why do you assume that there are any versions of the libs in default lib search paths? There might not be any. In addition to setting include dirs, the pkg-config patch also takes care of library names and library dirs. It could also take care of other non-I CFLAGS possibly needed (replace --cflags-only-I with --cflags, I didn't do that because it doesn't seem well placed in a variable called INCLUDES and my intention was not to make too many changes to Makefile). And it could even handle RPATHs if the lib dirs are not in default search paths, but that's theoretical/guesswork - I haven't checked if any *.pc does anything like that. Btw. do I need to call /opt1/usr/bin/freetype-config? or will any freetype-config be ok? If using pkg-config, I don't know why you'd call freetype-config at all. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH] Install headers, add pkgconfig file
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 :)). Also, I don't know if all *.h are actually something that should be installed by install-headers, but since they're all available in the current setup for plugins to use too, I suppose weeding through them is an orthogonal task to this patch if needed in the first place (and maybe better discussed in the RFC: Makefile ravamp [sic] thread from Sat 8th Mar). --- Makefile~ 2008-03-06 21:29:58.0 +0200 +++ Makefile 2008-03-10 23:05:48.0 +0200 @@ -21,2 +21,3 @@ BINDIR = $(PREFIX)/bin +INCLUDEDIR = $(PREFIX)/include LOCDIR = ./locale @@ -77,3 +78,3 @@ -all: vdr i18n +all: vdr vdr.pc i18n @@ -103,2 +104,19 @@ +# pkg-config file: + +vdr.pc: Makefile + echo bindir=$(BINDIR) $@ + echo includedir=$(INCLUDEDIR) $@ + echo confdir=$(CONFDIR) $@ + echo videodir=$(VIDEODIR) $@ + echo plugindir=$(PLUGINLIBDIR) $@ + echo localedir=$(LOCDIR) $@ + echo apiversion=$(APIVERSION) $@ + echo $@ + echo Name: VDR $@ + echo Description: Video Disk Recorder $@ + echo URL: http://www.cadsoft.de/vdr/; $@ + echo Version: $(VDRVERSION) $@ + echo Cflags: $(CXXFLAGS) -I$(INCLUDEDIR) $@ + # Internationalization (I18N): @@ -163,3 +181,4 @@ -install: install-bin install-conf install-doc install-plugins install-i18n +install: install-bin install-conf install-doc install-plugins install-i18n \ + install-includes @@ -194,2 +213,8 @@ +# Headers: + +install-includes: include-dir + @mkdir -p $(DESTDIR)$(INCLUDEDIR) + @cp -pR include/vdr include/libsi $(DESTDIR)$(INCLUDEDIR) + # Source documentation: @@ -206,3 +231,3 @@ $(MAKE) -C $(LSIDIR) clean - -rm -f $(OBJS) $(DEPFILE) vdr core* *~ + -rm -f $(OBJS) $(DEPFILE) vdr vdr.pc core* *~ -rm -rf $(LOCALEDIR) $(PODIR)/*.mo $(PODIR)/*.pot ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] Install headers, add pkgconfig file
On Wednesday 12 March 2008, clemens kirchgatterer wrote:
On Tue, Mar 11, 2008 at 3:46 PM, Joerg Pulz [EMAIL PROTECTED] wrote:
Out of this four cases (there are probably more, one for every Linux
distribution on this planet), tell me which is the most reasonable
default?
the most reasonable default is simply to put vdr.pc in
[$(DESTDIR)/]$(PREFIX)/lib/pkgconfig. for cases that this is not
appropriate, there is $PKG_CONFIG_PATH.
Agreed. The second revision of the patch is attached; compared to the first
one this also installs the *.pc file to the first (colon separated) component
of $PKG_CONFIG_PATH, or to $(PREFIX)/lib/pkgconfig if $PKG_CONFIG_PATH is not
set in the environment. Unless I've missed something, as far as I'm
concerned this is good enough to go in.
By the way, if someone's interested, the bug I reported against pkg-config
because it can't be queried for its default *.pc dirs is
https://bugs.freedesktop.org/show_bug.cgi?id=14975
--- Makefile.orig 2008-03-06 21:29:58.0 +0200
+++ Makefile 2008-03-12 22:41:54.0 +0200
@@ -21,2 +21,3 @@
BINDIR = $(PREFIX)/bin
+INCLUDEDIR = $(PREFIX)/include
LOCDIR = ./locale
@@ -34,2 +35,4 @@
+PCDIR ?= $(firstword $(subst :, , ${PKG_CONFIG_PATH}:$(PREFIX)/lib/pkgconfig))
+
-include Make.config
@@ -77,3 +80,3 @@
-all: vdr i18n
+all: vdr i18n vdr.pc
@@ -103,2 +106,19 @@
+# pkg-config file:
+
+vdr.pc: Makefile
+ echo bindir=$(BINDIR) $@
+ echo includedir=$(INCLUDEDIR) $@
+ echo confdir=$(CONFDIR) $@
+ echo videodir=$(VIDEODIR) $@
+ echo plugindir=$(PLUGINLIBDIR) $@
+ echo localedir=$(LOCDIR) $@
+ echo apiversion=$(APIVERSION) $@
+ echo $@
+ echo Name: VDR $@
+ echo Description: Video Disk Recorder $@
+ echo URL: http://www.cadsoft.de/vdr/; $@
+ echo Version: $(VDRVERSION) $@
+ echo Cflags: $(CXXFLAGS) -I$(INCLUDEDIR) $@
+
# Internationalization (I18N):
@@ -163,3 +183,4 @@
-install: install-bin install-conf install-doc install-plugins install-i18n
+install: install-bin install-conf install-doc install-plugins install-i18n \
+ install-includes install-pc
@@ -194,2 +215,16 @@
+# Headers:
+
+install-includes: include-dir
+ @mkdir -p $(DESTDIR)$(INCLUDEDIR)
+ @cp -pR include/vdr include/libsi $(DESTDIR)$(INCLUDEDIR)
+
+# pkg-config file:
+
+install-pc: vdr.pc
+ if [ -n $(PCDIR) ] ; then \
+ mkdir -p $(DESTDIR)$(PCDIR) ; \
+ cp vdr.pc $(DESTDIR)$(PCDIR) ; \
+ fi
+
# Source documentation:
@@ -206,3 +241,3 @@
$(MAKE) -C $(LSIDIR) clean
- -rm -f $(OBJS) $(DEPFILE) vdr core* *~
+ -rm -f $(OBJS) $(DEPFILE) vdr vdr.pc core* *~
-rm -rf $(LOCALEDIR) $(PODIR)/*.mo $(PODIR)/*.pot
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Which is the best firmware for ADV7170
On Tuesday 18 March 2008, Kartsa wrote: I have DXR3 card with ADV7170. Me too. I have quite bad audio sync problems with it and was wondering if there is some fw which is better over others. It's been some time, but IIRC I've tried all that I could find, and the 0x29 one that comes with the drivers has worked best for me. The problem is that I must every once and a while pause replay for a second or so or when watching live TV change the channel back and forthto get the sync back. Same here, but not often enough for it to really annoy that much. I think it happens mostly for MTV3 here. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-sudoku-0.2.0
On Saturday 22 March 2008, Thomas Günther wrote: Hi! There is a new version of the Sudoku plug-in. Download: http://toms-cafe.de/vdr/sudoku/vdr-sudoku-0.2.0.tgz Here's a bunch of patches: - finnish: Add missing Finnish translations. - no-pattern-default: Turn of show numbers as pattern by default; I find the feature quite unexpected and it causes a mess (bleeding colors) with my DXR3 OSD. - no-exit: Remove the Exit choice from the commands menu; exiting the plugin using this menu entry exits the plugin fine but next time any VDR OSD should appear after doing this, VDR crashes (VDR 1.4.7, Fedora Core 8). This is obviously just a stopgap patch, it'd be better if this could be fixed properly. Remove Exit from commands menu, it causes crashes when opening the OSD next time after exiting the plugin. diff -up sudoku-0.2.0/commands.cpp~ sudoku-0.2.0/commands.cpp --- sudoku-0.2.0/commands.cpp~ 2008-03-22 04:00:00.0 +0200 +++ sudoku-0.2.0/commands.cpp 2008-03-22 14:11:15.0 +0200 @@ -43,7 +43,6 @@ CommandMenu::CommandMenu() : Add(new Command(hk(tr(Save the puzzle)), Menu::save)); Add(new Command(hk(tr(Reset the puzzle)), Menu::reset)); Add(new Command(hk(tr(Open setup menu)), Menu::open_setup)); - Add(new Command(hk(tr(Exit)), Menu::exit)); command = NULL; } Don't show possible numbers as a pattern by default, it's an unexpected feature and doesn't work properly with all OSD's. diff -up sudoku-0.2.0/setup.cpp~ sudoku-0.2.0/setup.cpp --- sudoku-0.2.0/setup.cpp~ 2008-03-22 04:00:00.0 +0200 +++ sudoku-0.2.0/setup.cpp 2008-03-22 13:43:53.0 +0200 @@ -39,7 +39,7 @@ SetupData::SetupData() symmetric = 1; mark_errors = 1; mark_ambiguous = 1; - show_possibles_pattern = 1; + show_possibles_pattern = 0; show_possibles_digits = 1; clear_marks = 0; transparency = 50; vdr-sudoku-0.2.0-finnish.patch.gz Description: GNU Zip compressed data ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-sudoku-0.2.0
On Saturday 22 March 2008, Thomas Günther wrote: Ville Skyttä wrote: - no-exit: Remove the Exit choice from the commands menu; exiting the plugin using this menu entry exits the plugin fine but next time any VDR OSD should appear after doing this, VDR crashes (VDR 1.4.7, Fedora Core 8). This is obviously just a stopgap patch, it'd be better if this could be fixed properly. Sorry, this was a last minute change, without testing the exit function. :-( Please try the attached patch. It solves the problem for me. Seems to work for me too, thanks. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] LOCDIR/LOCALEDIR and plugins
Hello, I'm a bit confused about the locale dir stuff in VDR 1.6.0 especially wrt. plugins. newplugin hardcodes LOCALEDIR to $(VDRDIR)/locale without taking Make.config into account at all. The result is that plugins will try to place their *.mo into a wrong location if LOCDIR was customized in in VDR's Make.config and/or make install was used. I suppose the attached patch would fix that. However that does not address weirdness in main VDR's locale dir handling; the value set for LOCDIR in Make.config gets built into vdr as the compile time default locale dir, but but make install-i18n will install the *.mo somewhere else unless one sets identical value for LOCALEDIR in Makefile (setting it in Make.config does not have any effect). Are both LOCDIR and LOCALEDIR needed? I'd try to clean this up and post a patch that fixes it if I knew what the intention is :) --- newplugin~ 2008-01-13 15:00:23.0 +0200 +++ newplugin 2008-04-06 19:34:52.0 +0300 @@ -84,6 +84,7 @@ VDRDIR = ../../.. LIBDIR = ../../lib TMPDIR = /tmp +LOCDIR = \$(VDRDIR)/locale ### Allow user defined options to overwrite defaults: @@ -129,9 +130,8 @@ ### Internationalization (I18N): PODIR = po -LOCALEDIR = \$(VDRDIR)/locale I18Npo= \$(wildcard \$(PODIR)/*.po) -I18Nmsgs = \$(addprefix \$(LOCALEDIR)/, \$(addsuffix /LC_MESSAGES/vdr-\$(PLUGIN).mo, \$(notdir \$(foreach file, \$(I18Npo), \$(basename \$(file)) +I18Nmsgs = \$(addprefix \$(LOCDIR)/, \$(addsuffix /LC_MESSAGES/vdr-\$(PLUGIN).mo, \$(notdir \$(foreach file, \$(I18Npo), \$(basename \$(file)) I18Npot = \$(PODIR)/\$(PLUGIN).pot %.mo: %.po @@ -144,7 +144,7 @@ msgmerge -U --no-wrap --no-location --backup=none -q \$\@ \$ [EMAIL PROTECTED] \$\@ -\$(I18Nmsgs): \$(LOCALEDIR)/%/LC_MESSAGES/vdr-\$(PLUGIN).mo: \$(PODIR)/%.mo +\$(I18Nmsgs): \$(LOCDIR)/%/LC_MESSAGES/vdr-\$(PLUGIN).mo: \$(PODIR)/%.mo [EMAIL PROTECTED] -p \$(dir \$@) cp \$ \$\@ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [ANNOUNCE] vdr-dxr3 0.2.8
vdr-dxr3 0.2.8 is out, the most noteworthy thing being compatibility with VDR 1.6.0. 2008-04-06: Version 0.2.8 - Fix build with ffmpeg = ~2007-07 (Ville Skyttä) - Fix build with VDR = 1.5.9 (Ville Skyttä) - Drop support for VDR 1.4.0 (Ville Skyttä) - Implement OSD level for VDR = 1.5.9 (Luca Olivetti) - Fix subtitles for VDR = 1.5.11 (Luca Olivetti, Sami Sundell) - Include VDR 1.6+ subtitle hack patch in patches/ (Luca Olivetti) https://sourceforge.net/project/showfiles.php?group_id=112648 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] Install headers, add pkgconfig file
On Wednesday 12 March 2008, Ville Skyttä wrote:
On Wednesday 12 March 2008, clemens kirchgatterer wrote:
On Tue, Mar 11, 2008 at 3:46 PM, Joerg Pulz [EMAIL PROTECTED]
wrote:
Out of this four cases (there are probably more, one for every Linux
distribution on this planet), tell me which is the most reasonable
default?
the most reasonable default is simply to put vdr.pc in
[$(DESTDIR)/]$(PREFIX)/lib/pkgconfig. for cases that this is not
appropriate, there is $PKG_CONFIG_PATH.
Agreed. The second revision of the patch is attached; compared to the
first one this also installs the *.pc file to the first (colon separated)
component of $PKG_CONFIG_PATH, or to $(PREFIX)/lib/pkgconfig if
$PKG_CONFIG_PATH is not set in the environment. Unless I've missed
something, as far as I'm concerned this is good enough to go in.
Here's the third revision, after a bit more testing. As a result of that,
there were a couple of minor bug fixes, most notable of which was to the
install-includes target.
--- Makefile.orig 2008-02-29 23:43:03.0 +0200
+++ Makefile 2008-04-04 20:18:51.0 +0300
@@ -19,6 +19,7 @@
PREFIX ?= /usr/local
MANDIR = $(PREFIX)/share/man
BINDIR = $(PREFIX)/bin
+INCLUDEDIR = $(PREFIX)/include
LOCDIR = ./locale
LIBS = -ljpeg -lpthread -ldl -lcap -lrt -lfreetype -lfontconfig
INCLUDES = -I/usr/include/freetype2
@@ -32,6 +33,8 @@
DOXYGEN = /usr/bin/doxygen
DOXYFILE = Doxyfile
+PCDIR ?= $(firstword $(subst :, , ${PKG_CONFIG_PATH}:$(PREFIX)/lib/pkgconfig))
+
-include Make.config
SILIB= $(LSIDIR)/libsi.a
@@ -75,7 +78,7 @@
DEFINES += -DVFAT
endif
-all: vdr i18n
+all: vdr i18n vdr.pc
# Implicit rules:
@@ -101,6 +104,23 @@
$(SILIB):
$(MAKE) -C $(LSIDIR) all
+# pkg-config file:
+
+vdr.pc: Makefile
+ echo bindir=$(BINDIR) $@
+ echo includedir=$(INCLUDEDIR) $@
+ echo configdir=$(CONFDIR) $@
+ echo videodir=$(VIDEODIR) $@
+ echo plugindir=$(PLUGINLIBDIR) $@
+ echo localedir=$(LOCDIR) $@
+ echo apiversion=$(APIVERSION) $@
+ echo $@
+ echo Name: VDR $@
+ echo Description: Video Disk Recorder $@
+ echo URL: http://www.cadsoft.de/vdr/; $@
+ echo Version: $(VDRVERSION) $@
+ echo Cflags: $(CXXFLAGS) -I$${includedir} $@
+
# Internationalization (I18N):
PODIR = po
@@ -161,7 +181,8 @@
# Install the files:
-install: install-bin install-conf install-doc install-plugins install-i18n
+install: install-bin install-conf install-doc install-plugins install-i18n \
+ install-includes install-pc
# VDR binary:
@@ -192,6 +213,20 @@
@mkdir -p $(DESTDIR)$(PLUGINLIBDIR)
@cp --remove-destination $(PLUGINDIR)/lib/lib*-*.so.$(APIVERSION) $(DESTDIR)$(PLUGINLIBDIR)
+# Headers:
+
+install-includes: include-dir
+ @mkdir -p $(DESTDIR)$(INCLUDEDIR)
+ @cp -pLR include/vdr include/libsi $(DESTDIR)$(INCLUDEDIR)
+
+# pkg-config file:
+
+install-pc: vdr.pc
+ if [ -n $(PCDIR) ] ; then \
+ mkdir -p $(DESTDIR)$(PCDIR) ; \
+ cp vdr.pc $(DESTDIR)$(PCDIR) ; \
+ fi
+
# Source documentation:
srcdoc:
@@ -204,7 +239,7 @@
clean:
$(MAKE) -C $(LSIDIR) clean
- -rm -f $(OBJS) $(DEPFILE) vdr core* *~
+ -rm -f $(OBJS) $(DEPFILE) vdr vdr.pc core* *~
-rm -rf $(LOCALEDIR) $(PODIR)/*.mo $(PODIR)/*.pot
-rm -rf include
-rm -rf srcdoc
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Watching old recordings with DVB subtitles with 1.6.0
Hello, I have quite a few old recordings with DVB subtitles that were recorded and watchable with 1.4.x and the subtitles plugin. When replaying these with VDR 1.6.0, the subtitles aren't shown (new recordings made with 1.6.0 seem to be fine). I see there's some kind of a compatibility mode for old subtitles plugin in 1.6.0 sources, so I guess they should be. Thoughts? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Watching old recordings with DVB subtitles with 1.6.0
On Saturday 12 April 2008, Rolf Ahrenberg wrote: On Sat, 12 Apr 2008, Ville Skyttä wrote: After figuring out how to access the subtitles menu (my remote.conf was from 1.4.x series so there was no button binding for it), yes, I do see an entry named 57 there. Selecting it gives me the Finnish subtitles I was looking for. Thanks for the tip. You could also map 57 to fin in info.vdr of all those old recordings and afterwards VDR automatically selects subtitles according to preferred languages. I tried to do that, but did not succeed so far. The old recordings I tried this with had no X lines in info.vdr, but they do have this selectable 57 entry in the subtitles menu. New recordings from the same channel (MTV3 Scifi) have both X 3 03 fin and X 3 03 sve there, and Finnish subtitles do show up automatically when replaying these. So I tried X 3 03 fin , X 3 57 fin , and X 57 03 fin in the old recordings' info.vdr but that did not seem have any effect. Tried also touching .update and restarting VDR in between, as well as replacing 57 with 39 and 87 (just in case there would have been a dec-hex conversion somewhere). SubtitleLanguages = fin 57 hack in setup.conf didn't help either. Did I miss something? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Watching old recordings with DVB subtitles with 1.6.0
On Sunday 13 April 2008, Klaus Schmidinger wrote: You can work around this by adding the lines X 3 03 X 3 03 X 3 03 X 3 03 X 3 03 X 3 03 X 3 03 X 3 03 X 3 03 fin suomi to your info.vdr files. This fills up the first 8 slots and puts suomi into the 9th slot. That works for me, thanks! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ts record (was - no channel update on vdr 1.7.0)
On Friday 23 May 2008, Klaus Schmidinger wrote: On 05/23/08 13:11, Goga777 wrote: is a lot of vdr-code need patch for this ? It's not too much, but at core locations and requires a lot of testing and debugging. Just a quick comment/question: have you considered changing the recording filenames to something else than *.vdr while doing the switch to TS? It's not that big of a deal, but distinguishing recordings from VDR's internal files, index.vdr and friends, by using eg. *.ts for recordings would help cases where apps are registered to handle files based on their filename extension and we want to use those apps to playback recordings and think that they can playback index.vdr etc. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Anyone having contacts to ZDF? (Re: TV channel logo collection)
On Wednesday 02 July 2008, Hanno Zulla wrote: Hi, So far, noone turned down the request and I have collected a critical mass of logos within a few days: http://www.linuxtv.org/vdrwiki/index.php/Logo_Collection [...] I applaud the effort, and IANAL, but with all due respect, are you certain that the license agreement draft says what you intend? For example, the non-commercial word is problematic. GPL _allows_ commercial distribution, and removing that possiblity makes your license incompatible with the GPL (which I'm sure you know is VDR's and practically all its plugins' license). http://www.gnu.org/licenses/gpl-faq.html#NoMilitary I suggest finalizing the license/copyright terms before asking logo copyright holders for permission in order to avoid having to ask them again if/when the license changes. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Failed to read channels.conf after adding transponder
On Saturday 06 September 2008, Klaus Schmidinger wrote: Since this kind of complaints keeps occuring ever again, I guess it's best to simply report errors when reading config files (as suggested by Tim) [...] Somewhat related - I'm wondering why comments are not allowed in channels.conf, remote.conf, setup.conf and timers.conf? Or actually more generally why an option for disallowing comments in some *.conf files exists in the first place :) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Failed to read channels.conf after adding transponder
On Saturday 06 September 2008, Klaus Schmidinger wrote: On 09/06/08 18:38, Ville Skyttä wrote: Somewhat related - I'm wondering why comments are not allowed in channels.conf, remote.conf, setup.conf and timers.conf? Or actually more generally why an option for disallowing comments in some *.conf files exists in the first place :) Some files are human written and will not be overwritten by VDR. In those files comments make sense. Other files are automatically written by VDR, so comments don't make much sense there. But I have no problem with allowing comments in all files and just dropping them when automatically writing back those files. Is this something you'd like to have? Yes, I think that's fine. It'd allow distro packagers to ship those files with some meaningful comments in them out of the box instead of just empty files. Especially channels.conf which (as far as I'm up to date with VDR's current behavior) still needs to be initially generated with external tools. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.6.0 device selection order for recordings
On Tuesday 16 September 2008, Malte Forkel wrote: Hello, I just upgraded from vdr 1.4.7 to vdr 1.6.0 (from the e-tobi.net experimental repository). That has changed the order in which devices are selected for recording significantly. Now, the only card with the CAM is selected first when recording non-encrypted channels, preventing later timers from recording encrypted channels. This is my hardware setup: DVB1: full-featured card (Hauppauge WinTV DVB-C rev 2.X) DVB2: budget card with CI and CAM (TerraTec Cinergy 1200 DVB-C) DVB3: budget card (TerraTec Cinergy 1200 DVB-C) As a test, I started tree recordings on non-encrypted channels, one after the other. With vdr 1.4.7, these recordings use DVB3, DVB1, and DVB2, sparing the card with the CAM as long as possible. With vdr 1.6.0, the recordings use DVB2 (!), DVB3, and DVB1, but using the the card with the CAM first. So one recording of a non-encrypted channels blocks all encrypted channels. I think I ran into a similar problem earlier myself. I have only two cards; one DVB-C TT budget (without CI/CAM) and one DVB-C Hauppauge FF with CI/CAM, and a DXR3 as the primary device. I haven't run into this problem in a while, but I'm not sure why - it might be that I swapped the cards' PCI slots or maybe I just haven't had a scenario where this would bite in a while. But anyway, I agree that VDR should save the CAM for last. And as a nice addition to that, perhaps even change the card used for a recording on the fly if that's what it takes to get all needed programs recorded, for example: Timer 1: 20:00-21:00, non-encrypted Timer 2: 20:30-21:30, non-encrypted (different MUX/$something than timer 1) Timer 3: 21:00-22:00, encrypted Card A: no CAM (can in theory do timers 1 and 2) Card B: CAM (can in theory do timers 1, 2 and 3) So, card A starts recording timer 1. Then, card B starts recording timer 2 (because it's on a different $something than timer 1, so card A can't take care of it simultaneously with timer 1). When timer 3 starts, timer 2 would be changed on the fly to continue recording on card A, and card B would start recording timer 3. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput sxfe / xxmc / via / EPIA ML6000 : great !
On Tuesday 25 November 2008, Frank Schmirler wrote: 7 seconds until I get a picture on my EPIA 6000. And this is still pretty long, as I need to upload DXR3 firmware first, then start VDR. Hmm, any particular reason why you need to do that? Recent em8300 driver versions should be able to load the microcode on demand, and vdr-dxr3 tries to load it at startup and in various other scenarios manually anyway. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [ANNOUNCE] vdr-dxr3 0.2.9
vdr-dxr3 0.2.9 is available at https://sourceforge.net/projects/dxr3plugin 2009-01-02: Version 0.2.9 - Update Italian translation (Diego Pierotto) - Error handling improvements (Ville Skyttä) - Add SVDRP commands for device release/reopen, audio output settings, brightness/contrast/saturation (Krzysztof Parma, Ville Skyttä) - Switch to VDR 1.6's i18n system (Ville Skyttä) - Drop support for VDR 1.6.0 (Ville Skyttä) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-dxr3 0.2.9
On Friday 02 January 2009, Jan Willies wrote:
Is there a way to apply the brightness/contrast settings on VDR-start?
Currently I have to go to Menu-System-Plugins-Dxr3 and press OK after
every start of VDR.
Hm, the configured values do get saved but I have no idea why there's no code
to apply them at startup. The attached patch should fix that.
And, can I apply these settings without starting
VDR, maybe via an entry in /sys/class/em8300 (like the zoom stuff)?
I don't think so. But I suppose it would be fairly easy to implement in the
driver - post a request for enhancement to the dxr3-devel mailing list?
Index: dxr3interface.c
===
RCS file: /cvsroot/dxr3plugin/dxr3/dxr3interface.c,v
retrieving revision 1.4.2.39
diff -u -r1.4.2.39 dxr3interface.c
--- dxr3interface.c 29 Dec 2008 21:21:31 - 1.4.2.39
+++ dxr3interface.c 2 Jan 2009 22:28:01 -
@@ -1046,6 +1046,17 @@
exit(1);
}
+// set brightness/contrast/saturation
+m_bcs.brightness = cDxr3ConfigData::Instance().GetBrightness();
+m_bcs.contrast = cDxr3ConfigData::Instance().GetContrast();
+m_bcs.saturation = cDxr3ConfigData::Instance().GetSaturation();
+dsyslog(dxr3: configure: brightness=%d,contrast=%d,saturation=%d,
+ m_bcs.brightness, m_bcs.contrast, m_bcs.saturation);
+if (ioctl(m_fdControl, EM8300_IOCTL_SETBCS, m_bcs) 0)
+{
+ esyslog(dxr3: unable to set brightness/contrast/saturation: %m);
+}
+
ConfigureDeviceAudio();
}
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Which extension for TS files?
On Sunday 04 January 2009, Vladimir Kangin wrote: You right. For example I'm keen of LinuxMCE (www.linuxmce.org) and it has a script that looking for media files, thus all .vdr are recognised as a video files of VDR while is not. It would would be a very wise step to improve this at the same time... Without knowing a thing about LinuxMCE, I suppose its scripts could be improved to only look for numbers.vdr. For example, if it uses find(1), instead of find /some/dir -name '*.vdr' ...it could do: find /some/dir -regex '.*/[0-9]+\.vdr' ...or if -regex is a problem, perhaps even simply this would be an improvement over '*.vdr': find /some/dir -name '???.vdr' (This is not in any way an objection to the renaming plans discussed here lately, the outcome of that seems good to me.) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] 1:1 pixel mapping - a waste of time?
On Tuesday 06 January 2009, Ville Aakko wrote: On my Sony it is called Täyskuiva (in finnish), Heh, is this spelling error yours or Sony's? :) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] auto shutdown (-s) question
On Saturday 07 February 2009, Udo Richter wrote: On 06.02.2009 13:49, Alex Betis wrote: I'm playing now with autoshutdown script (the one that is specified with -s switch) and have a question. When power button is pressed, VDR calls the script, but lets say the script decided not to shutdown the PC (other background work is done). I see that VDR shows a countdown of 5 minutes saying that it will shutdown soon. VDR does not know whether the shutdown script initiated the shutdown or decided to ignore it, I suppose it would be quite easy to implement that and maybe some other scenarios as well using shutdown script exit statuses. For example exit status 0 = shutdown successfully initiated (already in current VDR), 10 = shutdown ignored, 11 = something else, 12 = something else, anything else = an unexpected error occurred. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] auto shutdown (-s) question
On Saturday 07 February 2009, Ville Skyttä wrote: On Saturday 07 February 2009, Udo Richter wrote: On 06.02.2009 13:49, Alex Betis wrote: I'm playing now with autoshutdown script (the one that is specified with -s switch) and have a question. When power button is pressed, VDR calls the script, but lets say the script decided not to shutdown the PC (other background work is done). I see that VDR shows a countdown of 5 minutes saying that it will shutdown soon. VDR does not know whether the shutdown script initiated the shutdown or decided to ignore it, I suppose it would be quite easy to implement that and maybe some other scenarios as well using shutdown script exit statuses. For example exit status 0 = shutdown successfully initiated (already in current VDR), 10 = shutdown ignored, 11 = something else, 12 = something else, anything else = an unexpected error occurred. ...and based on some criteria, stdout and/or stderr from the script could be displayed on the OSD. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] auto shutdown (-s) question
On Saturday 07 February 2009, Udo Richter wrote: On 07.02.2009 11:26, Ville Skyttä wrote: VDR does not know whether the shutdown script initiated the shutdown or decided to ignore it, I suppose it would be quite easy to implement that and maybe some other scenarios as well using shutdown script exit statuses. For example exit status 0 = shutdown successfully initiated (already in current VDR), 10 = shutdown ignored, 11 = something else, 12 = something else, anything else = an unexpected error occurred. Unfortunately it's not that easy. Currently, VDR backgrounds the call to the shutdown script, and detaches the shutdown script from the VDR process. Only because of that, the script can 'survive' the kill of VDR, Why is that even necessary? Shutdown scripts could selectively background+detach things that need to survive killing of VDR and the script themselves, if any. and only because of that the script can display messages via SVDRP. Hmm, why wouldn't a non-background, non-detached script called by VDR be able to do that? Some shutdown scripts do set error levels, but there's no common definition about the meaning of error levels. Right, my post was about mentioning a possibility to add such common definitions if found feasible. Defining error levels for the shutdown script would thereby be potentially incompatible to existing scripts. Sure. Authors of such scripts get to keep both pieces if their scripts break due to use of undocumented features ;). I suppose changing the shutdown script not to run background+detached would probably be a source of more incompatibilities though, and ones that script authors would not be responsible for. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] auto shutdown (-s) question
On Sunday 08 February 2009, Udo Richter wrote: On 08.02.2009 10:19, Ville Skyttä wrote: On Saturday 07 February 2009, Udo Richter wrote: Unfortunately it's not that easy. Currently, VDR backgrounds the call to the shutdown script, and detaches the shutdown script from the VDR process. Only because of that, the script can 'survive' the kill of VDR, Why is that even necessary? Shutdown scripts could selectively background+detach things that need to survive killing of VDR and the script themselves, if any. Detaching as a script isn't that easy, the reason for these ugly echo ... | at now workarounds. There are other alternatives to choose from if one for some reason can't stomach the at approach. and only because of that the script can display messages via SVDRP. Hmm, why wouldn't a non-background, non-detached script called by VDR be able to do that? The main VDR thread would have to wait for the return, and SVDRP won't be handled until then. SVDRP connections from the script would timeout. You can see that if you use SVDRP commands from commands.conf without explicitly backgrounding. That sounds like a bug to me, irrespective of this discussion. The question for VDR is: If we don't shut down, when should VDR check again, or how does VDR know that the background job is done? Why would VDR check or care in the first place? An error level return is quite limited here. Sure, but quite a bit better than what's currently sanely doable. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Build failures with gcc 4.4
Hello,
I'm trying to build VDR 1.6.0-2 for the upcoming Fedora 11 release which has
gcc 4.4. There are a bunch of compilation errors as gcc has again become
less forgiving for C++ than it used to be.
One very common source of problems is explained here:
http://markmail.org/message/e5y6atneqztuvpw6#query:
+page:1+mid:hdkehz7bgl5b6vgc+state:results
There are quite a few of these problems in VDR 1.6.0-2 (error: invalid
conversion from 'const char*' to 'char*'). I started patching but quickly
realized that this is a job for someone who actually knows what he's doing.
Anyway, attached is a patch against VDR 1.6.0-2 that fixes the first few of
these errors. Approach with caution: I'm fairly confident that for example
the changes to cRecordings::DelByName are not the right thing to do but then
again I might not understand what it's doing anyway (changing the extension
of the filename to .del but not actually renaming the file accordingly?).
In addition to these errors, similar ones exist at least in StatNearestDir
(videodir.c) cSVDRP::CmdGRAB.
Help appreciated!
By the way, in case someone runs into it, some recent changes in DVB headers
(as in current Fedora devel) have caused other unrelated compilation
issues, -D__KERNEL_STRICT_NAMES appears to be needed to get compilation past
dvbdevice.c. See https://bugzilla.redhat.com/show_bug.cgi?id=483644
diff -up vdr-1.6.0/recording.c~ vdr-1.6.0/recording.c
--- vdr-1.6.0/recording.c~ 2008-02-24 12:28:53.0 +0200
+++ vdr-1.6.0/recording.c 2009-02-27 21:18:55.0 +0200
@@ -509,8 +509,8 @@ cRecording::cRecording(cTimer *Timer, co
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 *FileN
sortBuffer = NULL;
fileName = strdup(FileName);
FileName += strlen(VideoDirectory) + 1;
- char *p = strrchr(FileName, '/');
+ const char *p = strrchr(FileName, '/');
name = NULL;
info = new cRecordingInfo;
@@ -1022,15 +1022,17 @@ void cRecordings::DelByName(const char *
if (recording) {
cThreadLock DeletedRecordingsLock(DeletedRecordings);
Del(recording, false);
- char *ext = strrchr(recording-FileName(), '.');
+ char *NewName = strdup(recording-FileName());
+ char *ext = strrchr(NewName, '.');
if (ext) {
strncpy(ext, DELEXT, strlen(ext));
-recording-fileSizeMB = DirSizeMB(recording-FileName());
+recording-fileSizeMB = DirSizeMB(NewName);
recording-deleted = time(NULL);
DeletedRecordings.Add(recording);
}
else
delete recording;
+ free(NewName);
ChangeState();
TouchUpdate();
}
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] A new possibility for lower power high performance VDR
On Monday 02 March 2009, Thomas Sailer wrote: On Mon, 2009-03-02 at 15:35 +0100, Peer Oliver Schmidt wrote: as multiple people have asked me in private mail (why do we have a mailing list *grml*), here is name of the box, I am using: EXSYS PCI Express Bus zu 4 x PCI Slot Expansion Box EX-1010 (0004558-2008-LV) The EX-1010 is a bit short, so very long PCI cards like the full featured DVB cards won't fit. There's also the EX-1011, which is the same as the EX-1010 with a larger case, so long PCI cards fit. I use both (on different computers), and they indeed work very well. How much did you pay for these? I found some prices around 180€, that sounds surprisingly high to me. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Build failures with gcc 4.4
On Friday 27 February 2009, Ville Skyttä wrote: Hello, I'm trying to build VDR 1.6.0-2 for the upcoming Fedora 11 release which has gcc 4.4. There are a bunch of compilation errors as gcc has again become less forgiving for C++ than it used to be. One very common source of problems is explained here: http://markmail.org/message/e5y6atneqztuvpw6#query: +page:1+mid:hdkehz7bgl5b6vgc+state:results There are quite a few of these problems in VDR 1.6.0-2 (error: invalid conversion from 'const char*' to 'char*'). I started patching but quickly realized that this is a job for someone who actually knows what he's doing. [...] ...but until there's a real fix available, the attached ugly patch at least makes the build succeed with gcc 4.4. diff -up vdr-1.6.0/Makefile~ vdr-1.6.0/Makefile --- vdr-1.6.0/Makefile~ 2008-02-29 23:43:03.0 +0200 +++ vdr-1.6.0/Makefile 2009-04-14 19:10:22.0 +0300 @@ -82,6 +82,10 @@ all: vdr i18n %.o: %.c $(CXX) $(CXXFLAGS) -c $(DEFINES) $(INCLUDES) $ +recording.o: CXXFLAGS += -fpermissive +svdrp.o: CXXFLAGS += -fpermissive +videodir.o: CXXFLAGS += -fpermissive + # Dependencies: MAKEDEP = $(CXX) -MM -MG ___ 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 Tuesday 21 April 2009, Peter Dittmann wrote: So better suggestion for the distri maintainers would be to use the \mnt tree for mounting any partitions. I disagree, /mnt is system admin area, not something distros should touch. http://www.pathname.com/fhs/pub/fhs-2.3.html#MNTMOUNTPOINTFORATEMPORARILYMOUNT ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR exited with status 134
On Sunday 14 June 2009, Martin Gansser wrote: Hi, VDR 1.6.0 exited with status 134, when generating a iso-file with vdr-burn. system is Fedora 11 x86_64 Possibly a vdr-burn/boost compile/runtime mismatch. https://bugzilla.redhat.com/show_bug.cgi?id=505893 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] What about vdr-1.6.1?
On Sunday 21 June 2009, Udo Richter wrote: On 21.06.2009 17:08, Klaus Schmidinger wrote: On 17.06.2009 19:03, J.W. wrote: I thought you could just release vdr-1.6.1 with the patches you have already published (maybe with additional dvb_api patch) . Are there more bugfixes planed? I released VDR 1.6.0 only because several people wanted to have a stable release just before switching to the DVB-S2 API. Sure, I could release a 1.6.1 now, but that would be exactly the same as 1.6.0 plus the two patches 1.6.0-1 and 1.6.0-2. But would that actually be a big help? There's already quite some backporting of version 1.7.x stuff going on... I guess I'm going to concentrate entirely on version 1.7.x. 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? ;) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH] Don't hardcode lirc socket path in the sky plugin
Hello,
The attached patch avoids hardcoded lirc socket path in the sky plugin, making
it use the value from Make.config by default. The patch is against 1.6.0-2
but appears to apply cleanly to 1.7.10 as well.
diff -up vdr-1.6.0/PLUGINS/src/sky/Makefile~ vdr-1.6.0/PLUGINS/src/sky/Makefile
--- vdr-1.6.0/PLUGINS/src/sky/Makefile~ 2008-01-13 15:00:16.0 +0200
+++ vdr-1.6.0/PLUGINS/src/sky/Makefile 2009-11-22 22:37:27.0 +0200
@@ -41,7 +41,8 @@ PACKAGE = vdr-$(ARCHIVE)
INCLUDES += -I$(VDRDIR)/include
-DEFINES += -D_GNU_SOURCE -DPLUGIN_NAME_I18N='$(PLUGIN)'
+LIRC_DEVICE ?= /dev/lircd
+DEFINES += -D_GNU_SOURCE -DPLUGIN_NAME_I18N='$(PLUGIN)' -DLIRC_DEVICE=\$(LIRC_DEVICE)\
### The object files (add further files here):
diff -up vdr-1.6.0/PLUGINS/src/sky/sky.c~ vdr-1.6.0/PLUGINS/src/sky/sky.c
--- vdr-1.6.0/PLUGINS/src/sky/sky.c~ 2008-03-22 12:19:32.0 +0200
+++ vdr-1.6.0/PLUGINS/src/sky/sky.c 2009-11-22 22:33:03.0 +0200
@@ -88,7 +88,7 @@ cDigiboxDevice::cDigiboxDevice(void)
apid = vpid = 0;
struct sockaddr_un addr;
addr.sun_family = AF_UNIX;
- strn0cpy(addr.sun_path, /dev/lircd, sizeof(addr.sun_path));//XXX parameter???
+ strn0cpy(addr.sun_path, LIRC_DEVICE, sizeof(addr.sun_path));//XXX parameter???
fd_lirc = socket(AF_UNIX, SOCK_STREAM, 0);
if (fd_lirc = 0) {
if (connect(fd_lirc, (struct sockaddr *)addr, sizeof(addr)) 0) {
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [ANNOUNCE] vdr-dxr3 0.2.10
vdr-dxr3 version 0.2.10 is out, changes since 0.2.9: - Apply brightness/contrast/saturation configuration settings when configuring the device, e.g. on VDR startup (Ville Skyttä) - Error handling improvements (Ville Skyttä) - Fix avcodec context initialization (Ville Skyttä) This is just a quick release to fix a crash with recent ffmpeg versions (last item in the above list), more extensive work on the next version is underway at http://projects.vdr-developer.org/projects/show/plg-dxr3 Downloads are available at: http://projects.vdr-developer.org/projects/list_files/plg-dxr3 and http://sourceforge.net/projects/dxr3plugin/files/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Applying dxr3 subtitles patch to debian packages
On Tuesday 26 January 2010, Emyr Thomas wrote: My question is, given the way I've installed VDR, what's the best/easiest way for me to apply this patch? Do I have to compile VDR from source myself, or can I somehow modify the debian VDR package sources on my machine and build them with this patch applied? I'm not familiar with Debian packaging, but I suppose the latter would be possible, and perhaps the maintainers of your Debian VDR package would consider including the patch in the package's source tree as an optional one so it'd be easier for people who want to rebuild it. (Or even just apply it unconditionally by default, that's what we've done in Fedora for a long time and there have been no complaints.) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [ANNOUNCE] vdr-dxr3 0.2.11
vdr-dxr3 version 0.2.11 is out, changes since 0.2.10: - OSD, demuxer and audiodecoder fixes for vdr 1.7.14 (Luca Olivetti) - Don't switch to digital AC3 mode if configured to use analog (Luca Olivetti) - Ignore H.264 streams, display notSupported.mpg instead (Luca Olivetti) - Fix build with recent (May 2010) ffmpeg (Ville Skyttä) 0.2.x is the stable series of the dxr3 plugin, targeted primarily for VDR 1.6.x at the moment, but it should work to some extent also with VDR 1.7.x. More extensive work on the next version is underway at http://projects.vdr- developer.org/projects/show/plg-dxr3 Downloads are available at: http://projects.vdr-developer.org/projects/list_files/plg-dxr3 and http://sourceforge.net/projects/dxr3plugin/files/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Problem with VDR 1.7.15 and dxr3plugin 0.2.10
On Saturday 02 October 2010, you wrote: I'm currently using text2skin and Enigma without channel logos with 1.6.0-2 and it works fine for me. Forgot to mention that I'm not 100% sure if it's OSD related, but the only situation where I frequently run into problems in this setup is when working with cut marks; especially when moving them the OSD seems to get stuck or corrupt quite often. Sometimes just waiting a few seconds fixes it, sometimes restarting the replay and editing does the trick, and sometimes VDR restarts. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.15 + DXR3 lockup problem
On Friday 29 October 2010, Teemu Suikki wrote: Hmm, I noticed that my OSD Flush time was set to 59 seconds in VDR settings.. If I drop that to some small value like 5 seconds, VDR doesn't hang anymore because the watchdog is not triggered for such a short time. No idea about the cause, but I'd like to point out that the value range for the dxr3 plugin's OSD flush rate is 0 to 255 _milli_seconds. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Minor *.po patch
On Saturday 04 December 2010, Tobias Grimm wrote: The gettext version I use automatically adds a Language field to the headers of the po-Files. It would be nice to have this field there in the first place, so here's a small patch that adds it. The Language fields for the main dialect of a language should not have _COUNTRY (i.e. Language: de, not Language: de_DE etc). More info: http://www.gnu.org/software/gettext/manual/gettext.html#Header-Entry Attached is a patch I've sent to Klaus quite a while back, I believe this one does it correctly (and also fixes Language-Team values). From dba5695d5efd9cd2b6663eeea404f0460d98dbca Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ville=20Skytt=C3=A4?= ville.sky...@iki.fi Date: Mon, 30 Aug 2010 00:07:05 +0300 Subject: [PATCH 5/5] Add Language and fix Language-Team header of *.po. http://www.gnu.org/software/gettext/manual/gettext.html#Header-Entry --- PLUGINS/src/hello/po/ca_ES.po |3 ++- PLUGINS/src/hello/po/cs_CZ.po |3 ++- PLUGINS/src/hello/po/da_DK.po |3 ++- PLUGINS/src/hello/po/de_DE.po |3 ++- PLUGINS/src/hello/po/el_GR.po |3 ++- PLUGINS/src/hello/po/es_ES.po |3 ++- PLUGINS/src/hello/po/et_EE.po |3 ++- PLUGINS/src/hello/po/fi_FI.po |3 ++- PLUGINS/src/hello/po/fr_FR.po |3 ++- PLUGINS/src/hello/po/hr_HR.po |3 ++- PLUGINS/src/hello/po/hu_HU.po |3 ++- PLUGINS/src/hello/po/it_IT.po |3 ++- PLUGINS/src/hello/po/lt_LT.po |3 ++- PLUGINS/src/hello/po/nl_NL.po |3 ++- PLUGINS/src/hello/po/nn_NO.po |3 ++- PLUGINS/src/hello/po/pl_PL.po |3 ++- PLUGINS/src/hello/po/pt_PT.po |3 ++- PLUGINS/src/hello/po/ro_RO.po |3 ++- PLUGINS/src/hello/po/ru_RU.po |3 ++- PLUGINS/src/hello/po/sk_SK.po |4 ++-- PLUGINS/src/hello/po/sl_SI.po |3 ++- PLUGINS/src/hello/po/sv_SE.po |3 ++- PLUGINS/src/hello/po/tr_TR.po |3 ++- PLUGINS/src/hello/po/zh_CN.po |4 ++-- PLUGINS/src/pictures/po/de_DE.po |3 ++- PLUGINS/src/pictures/po/fi_FI.po |3 ++- PLUGINS/src/pictures/po/fr_FR.po |3 ++- PLUGINS/src/pictures/po/it_IT.po |3 ++- PLUGINS/src/pictures/po/lt_LT.po |3 ++- PLUGINS/src/pictures/po/ru_RU.po |3 ++- PLUGINS/src/pictures/po/sk_SK.po |4 ++-- PLUGINS/src/skincurses/po/de_DE.po |3 ++- PLUGINS/src/skincurses/po/fi_FI.po |3 ++- PLUGINS/src/skincurses/po/it_IT.po |3 ++- PLUGINS/src/skincurses/po/lt_LT.po |3 ++- PLUGINS/src/skincurses/po/ru_RU.po |3 ++- PLUGINS/src/skincurses/po/sk_SK.po |4 ++-- po/ca_ES.po|3 ++- po/cs_CZ.po|3 ++- po/da_DK.po|3 ++- po/de_DE.po|3 ++- po/el_GR.po|3 ++- po/es_ES.po|3 ++- po/et_EE.po|3 ++- po/fi_FI.po|3 ++- po/fr_FR.po|3 ++- po/hr_HR.po|3 ++- po/hu_HU.po|3 ++- po/it_IT.po|3 ++- po/lt_LT.po|3 ++- po/mk_MK.po|1 + po/nl_NL.po|3 ++- po/nn_NO.po|3 ++- po/pl_PL.po|3 ++- po/pt_PT.po|3 ++- po/ro_RO.po|3 ++- po/ru_RU.po|3 ++- po/sk_SK.po|3 ++- po/sl_SI.po|3 ++- po/sv_SE.po|3 ++- po/tr_TR.po|3 ++- po/uk_UA.po|3 ++- po/zh_CN.po|3 ++- 63 files changed, 125 insertions(+), 66 deletions(-) diff --git a/PLUGINS/src/hello/po/ca_ES.po b/PLUGINS/src/hello/po/ca_ES.po index 008b97e..1c2d2dd 100644 --- a/PLUGINS/src/hello/po/ca_ES.po +++ b/PLUGINS/src/hello/po/ca_ES.po @@ -12,7 +12,8 @@ msgstr POT-Creation-Date: 2007-10-13 11:52+0200\n PO-Revision-Date: 2007-08-11 12:34+0200\n Last-Translator: Jordi Vilà jv...@tinet.org\n -Language-Team: Catalanian\n +Language-Team: Catalan vdr@linuxtv.org\n +Language: ca\n MIME-Version: 1.0\n Content-Type: text/plain; charset=ISO-8859-1\n Content-Transfer-Encoding: 8bit\n diff --git a/PLUGINS/src/hello/po/cs_CZ.po b/PLUGINS/src/hello/po/cs_CZ.po index c4fa571..bbf110c 100644 --- a/PLUGINS/src/hello/po/cs_CZ.po +++ b/PLUGINS/src/hello/po/cs_CZ.po @@ -10,7 +10,8 @@ msgstr POT-Creation-Date: 2007-10-13 11:52+0200\n PO-Revision-Date: 2007-08-11 12:34+0200\n Last-Translator: Vladimír Bárta vladimir.ba...@k2atmitec.cz\n -Language-Team: Czech\n +Language-Team: Czech vdr@linuxtv.org\n +Language: cs\n MIME-Version: 1.0\n Content-Type: text/plain; charset=ISO-8859-2\n Content-Transfer-Encoding: 8bit\n diff
Re: [vdr] Minor *.po patch
On Tuesday 07 December 2010, Rolf Ahrenberg wrote: On Mon, 6 Dec 2010, Ville Skyttä wrote: On Saturday 04 December 2010, Tobias Grimm wrote: The gettext version I use automatically adds a Language field to the headers of the po-Files. It would be nice to have this field there in the first place, so here's a small patch that adds it. The Language fields for the main dialect of a language should not have _COUNTRY (i.e. Language: de, not Language: de_DE etc). More info: http://www.gnu.org/software/gettext/manual/gettext.html#Header-Entry Fill in the language code of the language. This can be in ONE of three forms: ‘ll’, ‘ll_CC’, ‘ll...@variant’ Where is the country code forbidden exactly? Don't stop reading there. I don't know about forbidden, but they do write that the value is something else, a bit below the above quoted part: The naming convention ‘ll_CC’ is also the way locales are named on systems based on GNU libc. But there are three important differences: * In this PO file field, but not in locale names, ‘ll_CC’ combinations denoting a language's main dialect are abbreviated as ‘ll’. For example, ‘de’ is equivalent to ‘de_DE’ (German as spoken in Germany), and ‘pt’ to ‘pt_PT’ (Portuguese as spoken in Portugal) in this context. * In this PO file field, suffixes like ‘.encoding’ are not used. * In this PO file field, variant designators that are not relevant to message translation, such as �...@euro’, are not used. So, if your locale name is ‘de_DE.UTF-8’, the language specification in PO files is just ‘de’. The core VDR doesn't have same language for different areas, but i.e. the femon does: zh_CN and zh_TW. If I would use the plain zh for both of these, the zh_TW.po file would be interpreted as zh_CN and that really doesn't sound rigth. But leaving out the country only applies to _the_ (there can be only one I gather) primary dialect of a language. So both zh_CN and zh_TW cannot be the primary dialect; dunno if there's such a thing for Chinese in the first place. If you look at my patch carefully, you'll see that for zh_CN.po the value of the Language field is zh_CN. I did not invent any of these values myself - I just first fixed the Language- Team fields so that gettext itself understands them, and then ran the files through gettext, and copied/included in my patch what gettext itself had added. With VDR's current language files this doesn't make any difference, but I prefer Tobias' patch with your language team modifications a bit more future proof. I think following what gettext's docs say/recommend and what it actually does itself is the best approach. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Minor *.po patch
On Tuesday 07 December 2010, Rolf Ahrenberg wrote: So, de is a synonym for de_DE and both definitions are as correct as they can be according to my interpretation. Well, I interpret it differently (that de is what one should use in this field for German as spoken in Germany) so I guess that just demonstrates that the documentation could be improved. But... meh. And you could use here the plain zh as it defaults to zh_CH - Swiss-Chinese, interesting ;) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Minor *.po patch
On Sunday 12 December 2010, Klaus Schmidinger wrote: On 04.12.2010 13:09, Tobias Grimm wrote: The gettext version I use automatically adds a Language field to the headers of the po-Files. It would be nice to have this field there in the first place, so here's a small patch that adds it. According to a patch I recevied from Ville Skyttä a while ago the Language... entries currently look like this in my source (which will become VDR version 1.7.17): [...] Please advise whether this is correct. I believe it is, see rest of the messages in this thread. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Request: E parameter in channels.conf for epg scan
On Wednesday 15 December 2010, Jouni Karvo wrote: I think adding dependencies to outside packages is a burden that should be avoided. There are already many things I need to install separately in order the vdr box to work; kernel, graphics drivers, and xine-lib. Luckily, lirc is now already part of the kernel, and DVB drivers, too; much less hassle than before. This is the right direction to go - not adding more moving parts that need to be installed (with compatible versions). I'm not saying anything about the epg data as plain text vs sqlite thing, but would like to note that things are not always that black and white as the above seems to say. In my opinion it does not make sense to reimplement everything that's required just in order to avoid dependencies (but other valid reasons for not using something that's already there might of course exist). ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [ANNOUNCE] vdr-dxr3 0.2.12
vdr-dxr3 version 0.2.12 is out, noteworthy changes since 0.2.11: - Make dist target depend on up to date *.po (Ville Skyttä) - Use pkg-config to locate libavcodec (Ville Skyttä) - Avoid deprecation warnings with libavcodec = 52.26.0 (Ville Skyttä) - Compiler warning cleanups (Ville Skyttä) - Reintroduce AC3 decoding (Luca Olivetti) - Fix fast forward with VDR 1.7.x (Luca Olivetti) 0.2.x is the stable series of the dxr3 plugin, targeted primarily for VDR 1.6.x at the moment, but it should work to some extent also with VDR 1.7.x. More extensive work on the next version is underway at http://projects.vdr-developer.org/projects/show/plg-dxr3 Downloads are available at: http://sourceforge.net/projects/dxr3plugin/files/dxr3-0.2.x/0.2.12/ http://projects.vdr-developer.org/projects/plg-dxr3/files ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-dxr3 0.2.12
On 02/06/2011 06:29 PM, Helmut Auer wrote: Thanks for the update ! Is there anyone working on the drivers ? As far as I know, Christian Gmeiner is the only one who has worked on them recently. I haven't tested that stuff, but his hg repository is at http://hg.assembla.com/em8300-cgmeiner/ With a recent kernel the em8300 modules won't compile. The attached patch [1] over driver 0.18.0 is enough to make them build and work for me with kernel 2.6.35.10; I haven't tested with later versions. [1] Backport of http://hg.assembla.com/em8300-cgmeiner/changeset/720/ diff -up em8300-0.18.0/include/linux/em8300.h~ em8300-0.18.0/include/linux/em8300.h --- em8300-0.18.0/include/linux/em8300.h~ 2009-12-21 00:24:55.0 +0200 +++ em8300-0.18.0/include/linux/em8300.h2011-01-23 22:39:34.938179632 +0200 @@ -234,6 +234,10 @@ extern int major; #include linux/wait.h /* wait_queue_head_t */ #include linux/list.h /* struct list_head */ +#if LINUX_VERSION_CODE = KERNEL_VERSION(2,6,34) +#include linux/semaphore.h /* struct semaphore */ +#endif + #if defined(CONFIG_SND) || defined(CONFIG_SND_MODULE) #if LINUX_VERSION_CODE = KERNEL_VERSION(2,6,16) #define snd_card_t struct snd_card ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-dxr3 0.2.12
On 02/07/2011 10:03 PM, Christian Gmeiner wrote: The goal of this repository is to get the driver finally into mainline. Hooray! It's about time, thanks a lot! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Messages from Lirc have to be longer than 21 chars, why?
On 03/06/2011 04:49 PM, Klaus Schmidinger wrote: I guess what we need first is a specification of the strings LIRC provides. Then we can adapt the VDR code accordingly. I quickly searched the web, but couldn't find that information. Anybody? Maybe it has been discussed before, but I wonder why VDR has a LIRC implementation of its own instead of using liblirc_client? http://www.lirc.org/html/technical.html#library ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] What are recommended versions for a dxr3 setup ?
On 10/11/2011 08:20 PM, Mikko Tuumanen wrote: What is the latest kernel that dxr3 driver works on? And where should get the dxr3 driver from? The latest fully functional combination I'm aware of is version 0.18.0 plus the following patch, I know it works at least up to Fedora 14's kernel 2.6.35.14: http://trac-hg.assembla.com/em8300-cgmeiner/changeset/720 Is the vdr-dxr3-0.2.12 in vdr-developer.org the latest and greatest version of the plugin or should I pull from git or hg somewhere? The 0.2.12 release is pretty much it. The 0.2-branch in vdr-developer.org git has some changes after 0.2.12, but they're more or less cosmetic. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [ANNOUNCE] vdr-dxr3 0.2.13
vdr-dxr3 version 0.2.13 is out, noteworthy changes since 0.2.12: - Remove old non-Xine OSD scaler - Reduce unnecessary GetSysClock calls - Implement DVB subtitles hack without needing to patch VDR - Include VDR = 1.7.13's Make.global in Makefile - Use LDFLAGS when linking Downloads are available at: http://sourceforge.net/projects/dxr3plugin/files/dxr3-0.2.x/0.2.13/ http://projects.vdr-developer.org/projects/plg-dxr3/files ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-dxr3 0.2.13
On 10/20/2011 05:41 PM, Joerg Bornkessel wrote: vdr-dxr3 version 0.2.13 is out, noteworthy changes since 0.2.12: - Remove old non-Xine OSD scaler - Reduce unnecessary GetSysClock calls - Implement DVB subtitles hack without needing to patch VDR Ville, will this works on unpached vdr-1.6.x too? Yes, unpatched in the sense that the old DVB subtitles hack patch to VDR sources that used to be shipped with the DXR3 plugin (vdr-dxr3subtitlehack.patch) is no longer needed - the hack is implemented internally in this version of the plugin. I don't know about _completely_ unpatched VDR (I don't think I've ever actually even tried one), but as far as I know this version of the DXR3 plugin does not require any patches to VDR. I haven't tried with anything newer than 1.6.0-2 myself though. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [ANNOUNCE] text2skin plugin version 1.3.2
Changes since 1.3.1: - Fix build with ImageMagick = 6.6.2 (thanks to Anssi Hannula) - Documentation spelling fixes. - Added experimental RELAX NG schema for skin XML files. - Set minimum value of bitmap cache size in menu to 1. - Fix bitmap cache size initialization when built with gcc 4.6. - Update epgsearch search timer name parsing for epgsearch = 0.9.21. - Warning and code cleanups. http://projects.vdr-developer.org/projects/plg-text2skin ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.22
On 12/04/2011 05:53 PM, Klaus Schmidinger wrote: The changes since version 1.7.21: [...] - Removed the '.pl' suffix from all scripts (thanks to Ville Skyttä). svdrpsend.pl still has the .pl suffix... ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7 in Fedora Rawhide
On 2011-12-21 17:36, Pim Zandbergen wrote: VDR 1.7.22 is in Fedora Rawhide, which means vdr 1.7.X should become available in Fedora 17 due in May 2012. Hopefully it'll be 1.8.x or 2.x by then ;) For those who can't wait, the rawhide binary RPM's install en work just fine in Fedora 16, though I rebuilt them from source rpm to be sure. Right. My VDR box runs F-16 plus the VDR related packages from Rawhide as-is, they've worked fine for me so far. Ville, can we expect more plugins in the final release? I don't personally have plans to use or maintain more plugins than I do now. There are a couple of other people maintaining plugins in Fedora, dunno if they'd be interested. They can be reached at vdr-streamdev-owner and vdr-tvonscreen-owner at fedoraproject.org. If you have interest and some time to spare, helping out isn't that hard... http://fedoraproject.org/wiki/PackageMaintainers/Join ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH] Fix build with g++ 4.7.0.
This is the PR24163 case mentioned in
http://article.gmane.org/gmane.linux.redhat.fedora.devel/157671
---
config.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/config.h b/config.h
index 7825364..b0233a9 100644
--- a/config.h
+++ b/config.h
@@ -122,7 +122,7 @@ public:
if (!isempty(s)) {
T *l = new T;
if (l-Parse(s))
- Add(l);
+ this-Add(l);
else {
esyslog(ERROR: error in %s, line %d, fileName, line);
delete l;
--
1.7.7.5
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] shouldn't a vdr recording pause during status 3 flag?
On 2012-01-14 13:40, Tobi wrote: On 13.01.2012 23:14, Dieter Hametner wrote: You can clone a git repository of all released versions of VDR: $ git clone git://projects.vdr-developer.org/vdr.git There used to be a Web-Access to that repository too, but currently it doesn't seem to work any more. It works, but I changed to cgit (much faster) last year: http://projects.vdr-developer.org/git/vdr.git/ The Redmine repo browser is broken though (Repository tab at the top of http://projects.vdr-developer.org/projects/vdr). But this doesn't seem to be limited to this project, others' Redmine browsers are affected as well. http://projects.vdr-developer.org/projects/vdr/repository | Internal error | | An error occurred on the page you were trying to access. | If you continue to experience problems please contact your Redmine | administrator for assistance. | | If you are the Redmine administrator, check your log files for | details about the error. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] howto ignore lines in channels.conf
On 2012-01-15 13:01, Klaus Schmidinger wrote: VDR reads the channels.conf file and doesn't store any information about comments. It only stores the channel data. When it writes the file, it writes only the channel data, and at that point any comments in the original file would be lost. Even though they'd get lost when VDR writes it, allowing comments there would be an improvement so distros (and VDR itself) could ship the file with some comments in it that instruct users what they need to do before things will work, or what the file is for, or... Same thing applies to remote.conf, setup.conf, and timers.conf. If the AllowComments parameter exists just for the purpose of disallowing comments in files where VDR doesn't preserve them, I suggest removing that restriction altogether and allowing comments everywhere. Allowing comments and preserving them are two different things. For files where VDR doesn't preserve them it could note that on the first line of such files, for example like: # Warning: VDR will overwrite this file without preserving comments. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] howto ignore lines in channels.conf
On 2012-01-15 16:45, Udo Richter wrote: I've been living with VDR's auto channel update quite well, back since VDR 1.3.x eliminated the need of the AutoPID patch. The only thing I need an external tool for is to clean up all the dead channels from time to time. I never understood why people need external scan tools anyway, at least on an average system. Does this mean that if one now starts up a new VDR installation from scratch without any channels.conf whatsoever, VDR will find some channels to show on its own? How long does it take for it to find some channels, and how does that look like from the user POV? (I suppose I could just try it out myself, but I'm too lazy to do that ATM.) When I started using VDR sometime in the 1.3.x series, I don't think that happened automatically at all, I had to use dvb-apps' scan to generate a channels.conf. This is on DVB-C, and I don't think I've ever used an AutoPID patch. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] howto ignore lines in channels.conf
On 2012-01-15 18:39, VDR User wrote: I see no real benefit in complicating file (which stores only channel information) functions with what you've suggested. VDR already contains code in file functions whose only purpose IIRC is to make it possible to disallow comments in some files. *That* is unnecessary complication (which also happens to get in the way in some corner cases) and I suggested getting rid of it. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.24
On 2012-02-20 11:18, Klaus Schmidinger wrote: On 20.02.2012 00:06, Joerg Riechardt wrote: With dvbplayer.[hc] from version 1.7.23 and adjusted menu.[hc] it is ok again. Other patches were not involved. Jörg Well, then I guess it's best if I revoke that change. Any objections? Or maybe a fix for the vdr-xine problem? It seems that the dxr3 plugin is similarly affected, and reverting to the 1.7.23 versions gets rid of the problem for it as well. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Make.config.template broken in 1.7.24
On 2012-03-01 23:30, Manuel Reimer wrote: Hello, if I have a look at the changes in 1.7.24, then for me it looks like the file Make.config.template is broken there. As Variables are set using ?=, the values in Make.config.template not longer override the defaults of Makefile. I'd vote for reverting this change. Any objections? None here, some of them seem broken to me too. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.28
On 2012-06-03 13:44, Klaus Schmidinger wrote: - Renamed the function cString::sprintf(const char *fmt, va_list ap) to vsprintf(), Hm, I don't see this change actually implemented in the source...? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
