Re: [vdr] problems with playback and plugins with vdr-1.7.22
On 08/01/2012 08:43, René wrote: On 07.01.2012 23:23 , René wrote: The patch compiles now fine, but when activating livebuffer, vdr crashes with the following in the logs: I realized that i forgot to turn back a couple Gentoo-useflags that i had active til now: cutterlimit ddepgentry hardlinkcutter mainmenuhooks pinplugin timerinfo wareagleicon yaepg lircsettings Putting these back seems to have fixed the crash.. Still having trouble with playback/rewind/forwad of Regards, René ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr Yes, it works like this but it's a temporary workaround. I checked what Udo say and this is the real problem, the USE_LIVEBUFFER flag is not in use when the plugins are compiled. I don't know how to propagate this flag with portage. This would be a better solution. Regards, Marc. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.7.22 error while reading (config files...)
1) I forgot to report that vdr is compiled with flowing patch:
Index: vdr-1.7.22/libsi/si.c
===
--- vdr-1.7.22.orig/libsi/si.c 2011-03-22 12:19:25.694769064 +0100
+++ vdr-1.7.22/libsi/si.c 2011-03-22 12:20:07.526770314 +0100
@@ -381,7 +381,7 @@
if (SystemCharacterTable) {
iconv_t cd = iconv_open(SystemCharacterTable, fromCode);
if (cd != (iconv_t)-1) {
-char *fromPtr = (char *)from;
+const char *fromPtr = from;
while (fromLength 0 toLength 1) {
if (iconv(cd, fromPtr, fromLength, to, toLength) ==
size_t(-1)) { if (errno == EILSEQ) {
Index: vdr-1.7.22/tools.c
===
--- vdr-1.7.22.orig/tools.c 2011-03-22 12:17:47.022769064 +0100
+++ vdr-1.7.22/tools.c 2011-03-22 12:19:17.290769404 +0100
@@ -818,7 +818,7 @@
const char *cCharSetConv::Convert(const char *From, char *To, size_t
ToLength) {
if (cd != (iconv_t)-1 From *From) {
- char *FromPtr = (char *)From;
+ const char *FromPtr = From;
size_t FromLength = strlen(From);
char *ToPtr = To;
if (!ToPtr) {
2) and libiconv-full-1.11.1 with this patch:
http://pastebin.com/Sug25Edd
iconv.h here :http://pastebin.com/67wpbrtW
Thanks.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] problems with playback and plugins with vdr-1.7.22
On Sat, 7 Jan 2012, René wrote: Then i got an other problem. When watching a recording, and i fastforward of rewind the program, i get to a situation that the timecounter get's stuck to the frame i start from. The film moves, but when i hit play, i end up back to the frame from where i started to rewind/fastforwad. The only way to fix this is to jump with the yellow/green buttons. AFter this i can rewind/fastforwad normally. This again works for a while, but again if it fails to stop to the place i rewind to, i have to reset the rewind-issue with the yellow/green buttons... Is this a known bug in vdr, or is it something that i have messed up in my setup? I was under impression that this is already fixed in xineliboutput 10.12.2011 or newer. BR, -- rofa ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.7.22 error while reading (config files...)
debug using strace: stat64(0xb67818, 0x7f939de8)= 0 stat64(0xb67818, 0x7f939de8)= 0 access(/media/setup.conf, F_OK) = 0 gettid()= 1609 time([1326035707]) = 1326035707 open(/etc/TZ, O_RDONLY) = 4 read(4, CET-1CEST-2,M3.5.0/02:00:00,M10, 68) = 45 close(4)= 0 send(3, 11Jan 8 16:15:07 vdr: [1609] ..., 58, MSG_NOSIGNAL) = 58 open(/media/setup.conf, O_RDONLY|O_LARGEFILE) = 4 ioctl(4, TIOCNXCL, 0x7f939de8) = -1 ENOTTY (Inappropriate ioctl for device) read(4, AntiAlias = 1\nAudioLanguages = f..., 4096) = 4096 brk(0xb6b000) = 0xb6b000 brk(0xb6c000) = 0xb6c000 brk(0xb6d000) = 0xb6d000 read(4, xineliboutput.OSD.DvbSubtitles =..., 4096) = 1333 brk(0xb6e000) = 0xb6e000 read(4, , 4096) = 0 close(4)= 0 gettid()= 1609 time([1326035707]) = 1326035707 open(/etc/TZ, O_RDONLY) = 4 read(4, CET-1CEST-2,M3.5.0/02:00:00,M10, 68) = 45 close(4)= 0 send(3, 11Jan 8 16:15:07 vdr: [1609] ..., 88, MSG_NOSIGNAL) = 88 access(/media/sources.conf, F_OK) = 0 gettid()= 1609 time([1326035707]) = 1326035707 open(/etc/TZ, O_RDONLY) = 4 read(4, CET-1CEST-2,M3.5.0/02:00:00,M10, 68) = 45 close(4)= 0 send(3, 11Jan 8 16:15:07 vdr: [1609] ..., 60, MSG_NOSIGNAL) = 60 open(/media/sources.conf, O_RDONLY|O_LARGEFILE) = 4 ioctl(4, TIOCNXCL, 0x7f939e28) = -1 ENOTTY (Inappropriate ioctl for device) read(4, S19.0E ASTRA\n, 4096) = 13 gettid()= 1609 time([1326035707]) = 1326035707 open(/etc/TZ, O_RDONLY) = 5 read(5, CET-1CEST-2,M3.5.0/02:00:00,M10, 68) = 45 close(5)= 0 send(3, 11Jan 8 16:15:07 vdr: [1609] ..., 76, MSG_NOSIGNAL) = 76 read(4, , 4096) = 0 close(4)= 0 write(2, vdr: error while reading ', 26vdr: error while reading ') = 26 write(2, /media/sources.conf, 19/media/sources.conf) = 19 write(2, '\n, 2' ) = 2 access(/media/diseqc.conf, F_OK) = -1 ENOENT (No such file or directory) access(/media/scr.conf, F_OK) = -1 ENOENT (No such file or directory) access(/media/channels.conf, F_OK)= 0 gettid()= 1609 time([1326035707]) = 1326035707 open(/etc/TZ, O_RDONLY) = 4 read(4, CET-1CEST-2,M3.5.0/02:00:00,M10, 68) = 45 close(4)= 0 Thanks. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] problems with playback and plugins with vdr-1.7.22
On 08.01.2012 14:48 , Rolf Ahrenberg wrote: On Sat, 7 Jan 2012, René wrote: Then i got an other problem. When watching a recording, and i fastforward of rewind the program, i get to a situation that the timecounter get's stuck to the frame i start from. The film moves, but when i hit play, i end up back to the frame from where i started to rewind/fastforwad. The only way to fix this is to jump with the yellow/green buttons. AFter this i can rewind/fastforwad normally. This again works for a while, but again if it fails to stop to the place i rewind to, i have to reset the rewind-issue with the yellow/green buttons... Is this a known bug in vdr, or is it something that i have messed up in my setup? I was under impression that this is already fixed in xineliboutput 10.12.2011 or newer. Hi Rofa, I forgot to mention that i'm using dvbsddevice for outputting the signal via my FF-card. I think that my epia mii 12000 does not have enough horsepower (bit-power? :-) for using the onboard video output-connectors.. I actually never tried to use any other way to get a picture out from this board, because i was told that it will not work... René ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] problems with playback and plugins with vdr-1.7.22
On 08/01/2012 13:26, René wrote: On 08.01.2012 10:44 , Marc wrote: Yes, it works like this but it's a temporary workaround. I checked what Udo say and this is the real problem, the USE_LIVEBUFFER flag is not in use when the plugins are compiled. I don't know how to propagate this flag with portage. This would be a better solution. Hi Marc, I have USE_LIVEBUFFER=1 in /etc/make.conf, but this then does not seem to work correctly? The problem is to know how to tell portage to add this flag to gcc. With the others flags, this is done automatically, probably by the scripts launched in the ebuilds. I don't know how to do the same thing for local patches. Is the forwads/backward feature also part of this problem, or is it just me who has this problem.. I don't have this problem, I can't tell. I can use forward/backward on records and livebuffer. Has vdr-1.7 btw more resource-requirements than vdr-1.6? I still run my vdr on an epia mii 12000 board with 1gb memory. The 1.7 version of vdr has much more problem in keeping the palyback in sync. Also live-tv has problems keeping in sync. The sound is very often seconds behind the image... vdr itself take very low resources, it's the rendering witch require some resources. I use a nvidia card so all this part is handled by vdpau and, even in hd, my cpu has almost no load. Regards, Marc. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH v2] multi-frontend-support for vdr 1.7.21
Hi, Am 08.01.2012 02:09, schrieb Hawes, Mark: Hi Lars, I have got the sc plugin working with your hybrid patch v2 and introduced the premium card and all is working well. Are you planning any more revisions to the patch? Or at least a 1.7.22 version? Not really, because the driver changes introduced by Manu are on its way into linux-media. After that only one frontend will be left and new ioctls are there to switch between delivery systems. Rumours say Klaus is working on it for vdr 1.7.23... :-) But if you like, you can send me your changes. I'm curious about them. Lars. Thanks, Mark. -Original Message- From: Hawes, Mark Sent: Thursday, 1 December 2011 10:08 PM To: 'VDR Mailing List' Subject: RE: [vdr] [PATCH v2] multi-frontend-support for vdr 1.7.21 Hi Lars, First reports on v2 of your multi-frontend patch with HVR 4000 card: - can switch between both frontends successfully and very stable with repetitive tests - timer behaviour as expected - switching response seems quicker than before - Streamdev and xineliboutput plugins compile OK. Xlo tested OK, will look at Sd later - Have modified Rotor plugin to fit (maintaining personal version) and all seems OK - Working through sc plugin changes to fit. If I can get the sc plugin working I'll move across a sd premium card into the mix and see how it behaves, watch this space ... While this is all good obviously things will no doubt change when Klaus releases 2.x with the new multi-frontend adapter handling. However, reading between the lines this may not be in the immediate future so an interim workaround for these cards is appreciated by me and I expect others ... Thanks and keep up the good work. Mark. -Original Message- From: vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] On Behalf Of L. Hanisch Sent: Thursday, 1 December 2011 10:50 AM To: VDR Mailing List Subject: [vdr] [PATCH v2] multi-frontend-support for vdr 1.7.21 Hi, Here's version 2 of my multi-frontend-patch. It's still dirty, since it changes the constructor of cDvbDevice which will break compilation of some plugins. But I think it might be necessary to look at the relevant plugins since they might need to react on frontend changes. I haven't tested any of those plugins but will have a look at some that I'm using. Maybe there have to be some virtual functions like BeforeFrontendSwitch and AfterFrontendSwitch so the plugins are even able to know about it. Assumption for this patch: All frontends within one adapter have to be used mutually exclusive. All cards I know behave in this way. If there are cards with multiple frontends which can be used simultaneously I'd like to hear about it. Whenever the dvb-api-changes are upstream (the ENUM_DELSYS thingy) I think my patch can easily be converted to use that. I'm still working on this patch, it's not finished yet... :-) Have fun, Lars. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH v2] multi-frontend-support for vdr 1.7.21
On 08.01.2012 20:45, Lars Hanisch wrote: Hi, Am 08.01.2012 02:09, schrieb Hawes, Mark: Hi Lars, I have got the sc plugin working with your hybrid patch v2 and introduced the premium card and all is working well. Are you planning any more revisions to the patch? Or at least a 1.7.22 version? Not really, because the driver changes introduced by Manu are on its way into linux-media. After that only one frontend will be left and new ioctls are there to switch between delivery systems. Rumours say Klaus is working on it for vdr 1.7.23... :-) Version 1.7.23 will contain multi frontend support with the new API. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH v2] multi-frontend-support for vdr 1.7.21
Am 08.01.2012 21:10, schrieb Klaus Schmidinger: On 08.01.2012 20:45, Lars Hanisch wrote: Not really, because the driver changes introduced by Manu are on its way into linux-media. After that only one frontend will be left and new ioctls are there to switch between delivery systems. Rumours say Klaus is working on it for vdr 1.7.23... :-) Version 1.7.23 will contain multi frontend support with the new API. Will 1.7.23 require a kernel with the new API or will it be backwards compatible? Otherwise, s2apiwrapper ftw! ;) Cheers, Udo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH v2] multi-frontend-support for vdr 1.7.21
On 09.01.2012, at 00:19, Udo Richter udo_rich...@gmx.de wrote: Am 08.01.2012 21:10, schrieb Klaus Schmidinger: On 08.01.2012 20:45, Lars Hanisch wrote: Not really, because the driver changes introduced by Manu are on its way into linux-media. After that only one frontend will be left and new ioctls are there to switch between delivery systems. Rumours say Klaus is working on it for vdr 1.7.23... :-) Version 1.7.23 will contain multi frontend support with the new API. Will 1.7.23 require a kernel with the new API or will it be backwards compatible? It will be backwards compatible. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
