[vdr] vdr-sxfe doesn't work correctly with keyboard

2009-06-06 Thread Goga777
Hi

my system is

server - debian + kernel 2.6.29 + vdr 177 + s2-liplanin + hvr4000 + cvs 
xineliboutput + vdr-xine from hg
remote client - debian + vdr-sxfe from cvs xineliboutput + xine-lib-1.2 from hg

I have the problem with keyboard on remote frontend computer (vdr-sxfe)

For example -  If I  press and after that release the any digital button (2 
or 5) I have the 22 or 55
results - not 2 or 5 as usual .

Another example -  If  I press and release the button UP or DOWN the cursor 
will move on TWO lines to up or to down.

The problem is when I released the button - after release of button I have 
second event - double figure or double moving.

Also I couldn't use the pipe connection , rtp, udp protocols - only tcp 
connection

Jun  6 11:44:37 arvdr vdr: [17202] [xine..put] Trying PIPE connection ...
Jun  6 11:44:37 arvdr vdr: [17202] creating directory 
/video/plugins/xineliboutput/pipes.17195
Jun  6 11:44:37 arvdr vdr: [17202] [xine..put] Pipe not opened by client
Jun  6 11:44:37 arvdr vdr: [17202] removing 
/video/plugins/xineliboutput/pipes.17195
Jun  6 11:44:37 arvdr vdr: [17202] [xine..put] Trying RTP connection ...
Jun  6 11:44:37 arvdr vdr: [17202] [xine..put] RTP transport not implemented 
for vdr-1.7.x
Jun  6 11:44:37 arvdr vdr: [17202] [xine..put] Trying UDP connection ...
Jun  6 11:44:37 arvdr vdr: [17202] [xine..put] UDP transport not implemented 
for vdr-1.7.x


logs from vdr 177 

arvdr:/vdr# ./vdr -Pxineliboutput --local=none --remote=37890

Jun  6 11:43:45 arvdr vdr: [17195] cTimeMs: using monotonic clock (resolution 
is 1 ns)
Jun  6 11:43:45 arvdr vdr: [17195] VDR version 1.7.7 started
Jun  6 11:43:45 arvdr vdr: [17195] codeset is 'UTF-8' - known
Jun  6 11:43:45 arvdr vdr: [17195] found 23 locales in ./locale
Jun  6 11:43:45 arvdr vdr: [17195] loading plugin: 
./PLUGINS/lib/libvdr-xineliboutput.so.1.7.7
Jun  6 11:43:45 arvdr vdr: [17195] loading /video/setup.conf
Jun  6 11:43:45 arvdr vdr: [17195] [xine..put] Skipping configuration entry 
Frontend=sxfe (overridden in command line)
Jun  6 11:43:45 arvdr vdr: [17195] loading /video/sources.conf
Jun  6 11:43:45 arvdr vdr: [17195] loading /video/diseqc.conf
Jun  6 11:43:45 arvdr vdr: [17195] loading /video/channels.conf
Jun  6 11:43:45 arvdr vdr: [17195] loading /video/svdrphosts.conf
Jun  6 11:43:45 arvdr vdr: [17195] loading /video/remote.conf
Jun  6 11:43:45 arvdr vdr: [17196] video directory scanner thread started 
(pid=17195, tid=17196)
Jun  6 11:43:45 arvdr vdr: [17196] video directory scanner thread ended 
(pid=17195, tid=17196)
Jun  6 11:43:45 arvdr vdr: [17197] video directory scanner thread started 
(pid=17195, tid=17197)
Jun  6 11:43:45 arvdr vdr: [17197] video directory scanner thread ended 
(pid=17195, tid=17197)
Jun  6 11:43:45 arvdr vdr: [17195] reading EPG data from /video/epg.data
Jun  6 11:43:45 arvdr vdr: [17195] probing /dev/dvb/adapter0/frontend0
Jun  6 11:43:45 arvdr vdr: [17195] device 1 provides DVB-S2 (Conexant 
CX24116/CX24118)
Jun  6 11:43:45 arvdr vdr: [17199] tuner on device 1 thread started (pid=17195, 
tid=17199)
Jun  6 11:43:45 arvdr vdr: [17200] section handler thread started (pid=17195, 
tid=17200)
Jun  6 11:43:45 arvdr vdr: [17195] found 1 video device
Jun  6 11:43:45 arvdr vdr: [17195] initializing plugin: xineliboutput 
(1.0.90-cvs): X11/xine-lib output plugin
Jun  6 11:43:45 arvdr vdr: [17195] [xine..put] cTimePts: 
clock_gettime(CLOCK_MONOTONIC): clock resolution 0 us
Jun  6 11:43:45 arvdr vdr: [17195] [xine..put] cTimePts: using monotonic clock
Jun  6 11:43:45 arvdr vdr: [17195] [xine..put] RTP SSRC: 0x27fae0fc
Jun  6 11:43:45 arvdr vdr: [17195] setting primary device to 1
Jun  6 11:43:45 arvdr vdr: [17195] device 1 has no MPEG decoder
Jun  6 11:43:45 arvdr vdr: [17195] trying device number 2 instead
Jun  6 11:43:45 arvdr vdr: [17195] setting primary device to 2
Jun  6 11:43:45 arvdr vdr: [17195] assuming manual start of VDR
Jun  6 11:43:45 arvdr vdr: [17195] SVDRP listening on port 2001
Jun  6 11:43:45 arvdr vdr: [17195] setting current skin to sttng
Jun  6 11:43:45 arvdr vdr: [17195] loading /video/themes/sttng-default.theme
Jun  6 11:43:45 arvdr vdr: [17195] starting plugin: xineliboutput
Jun  6 11:43:45 arvdr vdr: [17202] Remote decoder/display server 
(cXinelibServer) thread started (pid=17195, tid=17202)
Jun  6 11:43:45 arvdr vdr: [17202] [xine..put] cXinelibServer priority set 
successful SCHED_RR 2 [1,99]
Jun  6 11:43:45 arvdr vdr: [17202] [xine..put] Listening on port 37890
Jun  6 11:43:45 arvdr vdr: [17202] [xine..put] Listening for UDP broadcasts on 
port 37890
Jun  6 11:43:45 arvdr vdr: [17202] [discovery] BROADCAST: VDR xineliboutput 
DISCOVERY 1.0^M Server port: 37890^M Server vers
ion: xineliboutput-1.0.90-cvs^M ^M
Jun  6 11:43:45 arvdr vdr: [17195] [xine..put] cXinelibDevice::StartDevice(): 
Device started
Jun  6 11:43:45 arvdr vdr: [17203] KBD remote control thread started 
(pid=17195, tid=17203)
Jun  6 11:43:45 arvdr vdr: [17195] remote control KBD - learning keys


Jun  6 

Re: [vdr] Build failures with gcc 4.4

2009-06-06 Thread Klaus Schmidinger
On 04.06.2009 09:12, Ludwig Nussel wrote:
 ...
 So gcc 4.4 finally hit openSUSE as well. I use the attached patch to
 make vdr compile. Seems to work fine too. The code that requires
 those const casts is really ugly though.

How about the attached change?
Should apply to VDR 1.6 just as well.

Klaus
--- svdrp.c	2009/06/06 13:42:52	2.4
+++ svdrp.c	2009/06/06 14:03:55
@@ -798,16 +798,17 @@
  char RealFileName[PATH_MAX];
  if (FileName) {
 if (grabImageDir) {
-   cString s;
-   char *slash = strrchr(FileName, '/');
+   cString s(FileName);
+   FileName = s;
+   const char *slash = strrchr(FileName, '/');
if (!slash) {
   s = AddDirectory(grabImageDir, FileName);
   FileName = s;
   }
slash = strrchr(FileName, '/'); // there definitely is one
-   *slash = 0;
-   char *r = realpath(FileName, RealFileName);
-   *slash = '/';
+   cString t(s);
+   t.Truncate(slash - FileName);
+   char *r = realpath(t, RealFileName);
if (!r) {
   LOG_ERROR_STR(FileName);
   Reply(501, Invalid file name \%s\, FileName);
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] vdr-sxfe doesn't work correctly with keyboard

2009-06-06 Thread martinez
Hi Goga,

remove

XKeySym.Up Up
XKeySym.Down   Down

does it fix up and down?

then remove the numbers 2

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


[vdr] making VDR ext4-ready

2009-06-06 Thread Marcel Witte
Hi,

today I've read an interesting article about ext4: 
http://www.heise.de/open/Das-Linux-Dateisystem-Ext4--/artikel/138431 (german, 
but there is also an english version). The new file system seems to be better 
for large files, as VDR-recordings are. Files up to 512 MB can be saved with 
just 1 inode, instead of a half Megabyte of inodes in ext3.

So ext4 seems to be perfect for a video-partition, but to make it more 
perfect, it would be nice if VDR could use the fallocate()-systemcall as 
mentioned in the article. This would prevent fragmentation in the file system.

For more information you should read the article ;)

Greets,
Marcel

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


Re: [vdr] making VDR ext4-ready

2009-06-06 Thread VDR User
Why not use the XFS filesystem?  Proven high performance with large
files, perfect for an htpc.

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