Re: [vdr] OSD-Resolution

2007-01-23 Thread Petri Helin

Rene Hertell wrote:

Hi Guys,

I remember that someone had some kind of patch for increasing the
OSD-resoluion in VDR. I just can't find that post that mentioned about
that...

Could anyone post a link to that site that had that patch.. I would like
to try that out :-)

Regards,

René

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



The patches are here: http://www.netholic.com/viewtopic.php?t=1622
Unfortunately, if you do not speak Finnish, it might a bit hard to 
follow that thread


What comes to VDR, you just need to change the defines for MAXOSDHEIGHT 
and -WIDTH in config.h (this is against 1.4.3-4):



--- config.h.orig   2006-10-28 02:30:20.0 +0300
+++ config.h2006-10-28 00:14:11.0 +0300
@@ -41,9 +41,9 @@
 #define MAXLIFETIME 99

 #define MINOSDWIDTH  480
-#define MAXOSDWIDTH  672
+#define MAXOSDWIDTH  1280
 #define MINOSDHEIGHT 324
-#define MAXOSDHEIGHT 567
+#define MAXOSDHEIGHT 720

 #define MaxFileName 256
 #define MaxSkinName 16


In order to increase the resolution of the OSD you should use 
xineliboutput-plugin and patch it like this (patch will most likely be 
broken because it is inline):



--- osd.c.orig  2006-10-30 02:37:03.0 +0200
+++ osd.c   2006-10-30 03:46:49.0 +0200
@@ -155,7 +155,12 @@

   m_Device = Device;
   m_Shown = false;
-  CmdSize(m_Device, 0, 720, 576);
+
+  if(Setup.OSDWidth + (2*Setup.OSDLeft) > 720 || Setup.OSDHeight + 
(2*Setup.OSDTop) > 576) {
+CmdSize(m_Device, 0, Setup.OSDWidth + (2*Setup.OSDLeft), 
Setup.OSDHeight + (2*Setup.OSDTop));

+  } else {
+CmdSize(m_Device, 0, 720, 576);
+  }
 }

 cXinelibOsd::~cXinelibOsd()
@@ -182,11 +187,11 @@
   if(Result == oeOk)
 m_Shown = false;

-  if(Left() + Width() > 720 || Top() + Height() > 576) {
+  if(2*Left() + Width() > 720 || 2*Top() + Height() > 576) {
 LOGDBG("Detected HD OSD, size > %dx%d, using setup values %dx%d",
-  Left() + Width(), Top() + Height(),
-  Setup.OSDWidth, Setup.OSDHeight);
-CmdSize(m_Device, 0, Setup.OSDWidth, Setup.OSDHeight);
+  2*Left() + Width(), 2*Top() + Height(),
+  Setup.OSDWidth + (2*Setup.OSDLeft), Setup.OSDHeight + 
(2*Setup.OSDTop));
+CmdSize(m_Device, 0, Setup.OSDWidth + (2*Setup.OSDLeft), 
Setup.OSDHeight + (2*Setup.OSDTop));

   } else {
 CmdSize(m_Device, 0, 720, 576);
   }


After that you should change the resolution via VDR's setup menu. Note 
that menu plugins are not really compatible with the larger resolution, 
like for example the ttxtsubs plugin unless you make some changes in to 
them. Here is an example fix for the ttxtsubs plugin:


--- ttxtsubsdisplay.c.orig  2006-10-28 02:22:29.0 +0300
+++ ttxtsubsdisplay.c   2006-10-28 02:23:42.0 +0300
@@ -332,13 +332,13 @@

 enum {
   SCREENLEFT = 0,
-  SCREENRIGHT = 719,
+  SCREENRIGHT = 1280,
   SCREENTOP = 150,
-  SCREENBOTTOM = 575,
+  SCREENBOTTOM = 720,

   SIDEMARGIN = 125,
-  BOTNORM = 540,
-  BOTLETTERBOX = 482,
+  BOTNORM = 640,
+  BOTLETTERBOX = 520,

   ROWINCR = 43,
   ROWH = 34,

-Petri

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


Re: [vdr] FF card A/V sync - in progress?

2007-01-23 Thread Pasi Juppo
Pasi Juppo wrote:
> Anyway, I can report also that A/V sync problem does not seem to be
> bothering anymore. Excellent work!

I was a bit too hasty. Sync got lost once while watching Pako (Prison
Break). However, it was nicer than earlier. Sync was out of sync but the
video and audio played nicely - just out of sync. Previously audio was
making cracking noise time to time.

Br, Pasi

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


Re: [vdr] [RFC] Shutdown rewrite for 1.5.x

2007-01-23 Thread Udo Richter

Marko Mäkelä wrote:

The problem seems to lie in shutdown.c, in SystemExecSession().
It won't close file descriptor 0, but it will close anything above
STDERR_FILENO (which is normally 2).  This function appears to show
up in strace output as "clone()".  Adding close(0) to the function
fixes the problem.  Do you see any reason why the shutdown script
would need to access stdin?  (I can see reasons why it would want to
access stdout or stderr.)


Actually, the SystemExecSession() is just a modified version of 
SystemExec() in thread.c, that was used before to call the shutdown 
script. They only differ in the fact that VDR continues instead of 
waiting for the child process, and that the child process is detached 
into its own session. There's no serious difference regarding the file 
handles.
Since the shutdown script runs in the background, the stdin could 
probably be closed. After all, VDR should continue to 'own' stdin, and 
running in the background would probably cause a conflict. However, 
running the script with a closed file handle may cause other side effects.


Cheers,

Udo


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


Re: [vdr] channels.conf problem

2007-01-23 Thread Carlos Javier Borroto

On 1/23/07, Markus Hahn <[EMAIL PROTECTED]> wrote:

Am Dienstag, 23. Januar 2007 17:54 schrieb Torgeir Veimo:
>

please take this link:

http://www.reelbox.org/software/source/vdr-plugins/vdr-reelchannelscan-0.4.0.tgz



I had tested reelchannelscan-0.4.0 with Echostar 7(North American sat)
and it didn't work, someone said to me, that it is because it only
works with european sats, is it true?, is there any kind of debug
information I can submit to you that can be helpfull?


or with no garanty
svn co  svn://[EMAIL 
PROTECTED]/testing/src/vdr/vdr-plugins/src/channelscan-0.4.1


I'll test this svn version to see if it works.
--
Carlos Javier
Habana, CUBA

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


Re: [vdr] FF card A/V sync - in progress?

2007-01-23 Thread Pasi Juppo
Tero Siironen wrote:
> On 19.1.2007 22:30, "Oliver Endriss" <[EMAIL PROTECTED]> wrote:
> 
>> Oliver Endriss wrote:
>>> Marco Skambraks wrote:
 hi,

 are there any new information about the FF a/v sync problem?
 is the firmware development still in progress?
>>> Sorry, no success yet.
>> Werner fixed the A/V sync problem. Please test firmware f12623.
>> See http://www.vdr-portal.de/board/thread.php?postid=566692#post566692
>>
>> Oliver
> 
> I can also report A/V sync working, but also problem that might relate to
> this new test version of the firmware. Timer recording failed, because vdr
> couldn't change the channel. Logs were filled with entries below resulting
> recording of 0 bytes. Another two recordings earlier has worked however, so
> could be related or coincidence. But Wife Approval Factor just dropped
> dramatically :)
> 
> - logs -
> 
> /var/log/messages:
> 
> Jan 22 19:59:21 localhost vdr: [1758] timer 1 
> (4 1959-2110 'Huippumalli haussa') start
^^
...

I can fully understand why WAF is lower :-)

Anyway, I can report also that A/V sync problem does not seem to be
bothering anymore. Excellent work!

It was actually strange to watch 24-series episode when I didn't have to
jump back and forth every now and then. I just got so used to the
annoying factor someway..

Br, Pasi

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


Re: [vdr] FF card A/V sync - in progress?

2007-01-23 Thread Kartsa

VDR User kirjoitti:
On 1/23/07, *Tero Siironen* <[EMAIL PROTECTED] 
> wrote:


I can also report A/V sync working, but also problem that might
relate to
this new test version of the firmware. Timer recording failed,
because vdr
couldn't change the channel. Logs were filled with entries below
resulting
recording of 0 bytes. Another two recordings earlier has worked
however, so
could be related or coincidence. But Wife Approval Factor just dropped
dramatically :)



I don't think this is coincidence as I too have has timer recording 
failures since installing the new a/v sync-fixed firmware.  This is 
definitely something that should be looked into!
Could this be related to some sw or hw issue? I have had this new fw for 
a few days now and about 20+ succesfull recordings and no failures.


I've got vdr 1.4.4, burn 0.0.009, subtitles 0.4.0, femon 1.1.0, mplayer 
0.9.15 and vompserver 0.2.5.
And on the hw side AMD Sempron 3000+, 512MB, TT DVB-C FF 2.1, DVB-C 
budget, FC6, kernel  2.6.18-1.2849.


\\Kartsa

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


Re: [vdr] FF card A/V sync - in progress?

2007-01-23 Thread VDR User

On 1/23/07, Tero Siironen <[EMAIL PROTECTED]> wrote:


I can also report A/V sync working, but also problem that might relate to
this new test version of the firmware. Timer recording failed, because vdr
couldn't change the channel. Logs were filled with entries below resulting
recording of 0 bytes. Another two recordings earlier has worked however,
so
could be related or coincidence. But Wife Approval Factor just dropped
dramatically :)




I don't think this is coincidence as I too have has timer recording failures
since installing the new a/v sync-fixed firmware.  This is definitely
something that should be looked into!
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] channels.conf problem

2007-01-23 Thread Markus Hahn
Am Dienstag, 23. Januar 2007 17:54 schrieb Torgeir Veimo:
> 

please take this link:

http://www.reelbox.org/software/source/vdr-plugins/vdr-reelchannelscan-0.4.0.tgz
 

or with no garanty 
svn co  svn://[EMAIL 
PROTECTED]/testing/src/vdr/vdr-plugins/src/channelscan-0.4.1

> On 23 Jan 2007, at 16:16, Markus Hahn wrote:
> 
> > can you try it with REEL channelscan Plugin?
> >
> > http://www.vdr-wiki.de/wiki/index.php/Reelchannelscan-plugin
> > Please post results or problems.
> 
> [EMAIL PROTECTED] src]# svn co svn://[EMAIL PROTECTED]/home/
> svn: URL 'svn://[EMAIL PROTECTED]/home' doesn't exist
> 

-- 
-
Markus Hahn, Developer. 
Reel Multimedia AG
Felsenrainstrasse 33
CH-8832 Wollerau / Switzerland
Tel.: +49 (0) 180 / 508 81 11   (operator)
Fax.: +49 (0) 180 / 508 81 14

[EMAIL PROTECTED]
www.Reel-Multimedia.com

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


Re: [vdr] FF card A/V sync - in progress?

2007-01-23 Thread Tero Siironen
On 19.1.2007 22:30, "Oliver Endriss" <[EMAIL PROTECTED]> wrote:

> Oliver Endriss wrote:
>> Marco Skambraks wrote:
>>> hi,
>>> 
>>> are there any new information about the FF a/v sync problem?
>>> is the firmware development still in progress?
>> 
>> Sorry, no success yet.
> 
> Werner fixed the A/V sync problem. Please test firmware f12623.
> See http://www.vdr-portal.de/board/thread.php?postid=566692#post566692
> 
> Oliver

I can also report A/V sync working, but also problem that might relate to
this new test version of the firmware. Timer recording failed, because vdr
couldn't change the channel. Logs were filled with entries below resulting
recording of 0 bytes. Another two recordings earlier has worked however, so
could be related or coincidence. But Wife Approval Factor just dropped
dramatically :)

- logs -

/var/log/messages:

Jan 22 19:59:21 localhost vdr: [1758] timer 1 (4 1959-2110 'Huippumalli
haussa') start
Jan 22 19:59:21 localhost vdr: [1758] record
/video/Huippumalli_haussa/2007-01-22.19.59.99.99.rec
Jan 22 19:59:21 localhost kernel: dvb-ttpci: StartHWFilter error  buf 0b07
0010  b96a  ret -1  handle d099
Jan 22 19:59:21 localhost kernel: dvb-ttpci: StartHWFilter error  buf 0b07
0010  b96a  ret -1  handle d099
Jan 22 19:59:21 localhost kernel: dvb-ttpci: av7110_fw_cmd error -1
Jan 22 19:59:22 localhost kernel: dvb-ttpci: StartHWFilter error  buf 0b07
0010 0012 b96a  ret -1  handle d099
Jan 22 19:59:22 localhost vdr: [1971] ERROR: can't set filter (pid=18,
tid=4E, mask=FE): Operation not permitted
Jan 22 19:59:22 localhost kernel: dvb-ttpci: StartHWFilter error  buf 0b07
0010 0012 b96a  ret -1  handle d099
Jan 22 19:59:22 localhost vdr: [1971] ERROR: can't set filter (pid=18,
tid=50, mask=F0): Operation not permitted
Jan 22 19:59:22 localhost kernel: dvb-ttpci: StartHWFilter error  buf 0b07
0010 0012 b96a  ret -1  handle d099
Jan 22 19:59:22 localhost vdr: [1971] ERROR: can't set filter (pid=18,
tid=60, mask=F0): Operation not permitted
Jan 22 19:59:22 localhost kernel: dvb-ttpci: StartHWFilter error  buf 0b07
0010 0014 b96a  ret -1  handle d099
Jan 22 19:59:22 localhost vdr: [1971] ERROR: can't set filter (pid=20,
tid=70, mask=FF): Operation not permitted
Jan 22 19:59:22 localhost kernel: dvb-ttpci: StartHWFilter error  buf 0b07
0010  b96a  ret -1  handle d099
Jan 22 19:59:22 localhost vdr: [1971] ERROR: can't set filter (pid=0,
tid=00, mask=FF): Operation not permitted
Jan 22 19:59:22 localhost kernel: dvb-ttpci: StartHWFilter error  buf 0b07
0010 0011 b96a  ret -1  handle d099
Jan 22 19:59:22 localhost kernel: dvb-ttpci: StartHWFilter error  buf 0b07
0010 0011 b96a  ret -1  handle d099
Jan 22 19:59:22 localhost vdr: [1971] ERROR: can't set filter (pid=17,
tid=42, mask=FF): Operation not permitted
Jan 22 19:59:22 localhost kernel: dvb-ttpci: StartHWFilter error  buf 0b07
0010 0010 b96a  ret -1  handle d099
Jan 22 19:59:22 localhost vdr: [1971] ERROR: can't set filter (pid=16,
tid=40, mask=FF): Operation not permitted
Jan 22 19:59:22 localhost kernel: dvb-ttpci: StartHWFilter error  buf 0b07
0010  b96a  ret -1  handle d099
Jan 22 19:59:22 localhost vdr: [1971] ERROR: can't set filter (pid=0,
tid=00, mask=FF): Operation not permitted
Jan 22 19:59:25 localhost kernel: dvb-ttpci: StartHWFilter error  buf 0b07
0010 00d7 b96a  ret -1  handle 
Jan 22 19:59:25 localhost vdr: [1758] ERROR (dvbdevice.c,683): Operation not
permitted
Jan 22 19:59:25 localhost vdr: [1758] ERROR: can't set PID 215 on device 2
Jan 22 19:59:26 localhost vdr: [1758] timer 1 (4 1959-2110 'Huippumalli
haussa') stop
.
.
.


dmesg:

DVB (dvb_dmxdev_filter_start): could not alloc feed
DVB (dvb_dmxdev_filter_start): could not alloc feed
DVB (dvb_dmxdev_filter_start): could not alloc feed
.
.
.

My Setup:
P3 700MHz
256 MB RAM
Technotrend DVB-C FF 2.1 + CICAM with Conax
Technotrend DVB-C FF 2.1
Fedora Core 5 2.6.16-1.2157_FC5 kernel
VDR 1.4.3,+streamdev,ttxtsubs,subtitles,tvonscreen,text2skin,
burn,wapd,osdteletext,mp3,femon


-- 
Tero



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


Re: [vdr] channels.conf problem

2007-01-23 Thread Torgeir Veimo


On 23 Jan 2007, at 16:16, Markus Hahn wrote:


can you try it with REEL channelscan Plugin?

http://www.vdr-wiki.de/wiki/index.php/Reelchannelscan-plugin
Please post results or problems.


[EMAIL PROTECTED] src]# svn co svn://[EMAIL PROTECTED]/home/
svn: URL 'svn://[EMAIL PROTECTED]/home' doesn't exist

--
Torgeir Veimo
[EMAIL PROTECTED]




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


Re: [vdr] channels.conf problem

2007-01-23 Thread Markus Hahn
Hi Bob, 
can you try it with REEL channelscan Plugin? 

http://www.vdr-wiki.de/wiki/index.php/Reelchannelscan-plugin
Please post results or problems. 
regards markus 


Am Montag, 22. Januar 2007 19:14 schrieb Bob Self:
> Im trying to generate a channels.conf file for vdr. I've read that you should
> use the scan utility to make it. The card works and I can use szap to display
> FTA channels:
> 
> szap -l DBS -c $HOME/.szap/x.conf -x $1
> x.conf = NASA:12370:v:1:2:4130:4131:213
> 



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


RE: [vdr] rambling newbie questions

2007-01-23 Thread Tony Grant
Le lundi 22 janvier 2007 à 19:54 -0500, Russell Treleaven a écrit :

> I would like to make the system very small.
> 
> http://www.gentoo.org/proj/en/base/embedded/gnap.xml 

Because you asked... Here you are rambling up the wrong track. Sorry!
Read the page carefully, do you see HTPC or PVR? No. Gentoo embedded
works for firewalls routers and whatever.

A video appliance is a good idea but you want loads of RAM and
acceleration for your video decoding. It can be done with specialised
hardware (I use a VIA EPIA-M) or in software with a fast CPU.

With VDR you can have a video server which uses a low power CPU because
the machine is just writing DVB streams to disk or to the network. The
client will need the power to decode the stream however.

Cheers

Tony
-- 


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