Re: [vdr] Setup/OSD

2008-03-22 Thread Klaus Schmidinger
On 03/17/08 12:31, Guy Roussin wrote:
 Hi,
 
 After i pressed Setup/OSD, i need to wait about 6 or 7 seconds
 before i get the menu/page. I try to change the language,
 truetype fonts but no effect. This is the only sub-menu with
 this problem.
 
 How can i track this bug ?
 
 I use vdr-1.5.17 from e-tobi on debian sarge.
 I've another vdr with the same config but the screen is quickly
 display when i press Setup/OSD

My guess would be that it has to do with the freetype fonts.
When opening the Setup/OSD page VDR collects all available
font names, and maybe that takes time on your system.

I remember having this on my system, too, but at some point it
was gone, so I didn't persue it.

You could insert some debug output in cFont::GetAvailableFontNames()
to see whether this is causing the delay.

Klaus

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


Re: [vdr] ERROR: attempt to open OSD while it is already open - using dummy OSD!

2008-03-22 Thread Klaus Schmidinger
On 03/17/08 01:35, Wolfgang Rohdewald wrote:
 start the osddemo plugin and then
 
 echo -e MESG hallo\nQUIT |nc localhost 2001
 
 gives me the above error message with vdr 1.5.16
 
 and the message will never be visible.
 
 how can a plugin like a music player handle this
 correctly? It always has an open osd, but of course
 hides it with Hide(). 
 
 But vdr does not ask the plugin to hide before trying
 to show the message, so I am getting the same error
 message in that situation. I see no way to get rid of it.
 
 As a possible solution, can the player control somehow
 tell vdr that it can handle the message display itself?
 Something like
 
 class cControl : public cOsdObject {
 public:
   ...
   virtual bool DisplayMessage(...) { return false };
 
 so if a player is active, its DisplayMessage is called.
 Only when it returns false, vdr then tries to display
 the message. 

See cSkinDisplayReplay::SetMessage().

Klaus

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


Re: [vdr] [ANNOUNCE] vdr-xine-0.8.2 plugin

2008-03-22 Thread oleg roitburd
Hi,

2008/3/18, Darren Salt [EMAIL PROTECTED]:
  Update your snapshot and try again.

Well, it works now. thx a lot

Regards
Oleg Roitburd

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


Re: [vdr] [ANNOUNCE] vdr-sudoku-0.2.0

2008-03-22 Thread Ville Skyttä
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] Problems with defining CA-field to allow devices to access channels (fault in vdr's channels.conf handling)

2008-03-22 Thread Antti Hartikainen
I repeat this message, as nobody gave any comments about this matter 
previously. Problem still exists in 1.5.18.
And in my opinion it's fault in VDR handling CA-field. Biggest problem is still 
limiting access to scrambled 
channels, as antenna 2 (card #3) receives only scrambled channels.

In my opinion CA-field is not anyway proper way to control devices access to 
channels.

On Tue, Mar 11, 2008 at 07:59:27AM +0200, Antti Hartikainen wrote:
 Hello, list and Klaus.
 
 Is it possible to limit multiple DVB devices to access certain channel with 
 CA-field?
 
 I have following setup:
 
 Card #1: DVB-S full-featured (only for mpeg decoding and tv-output)
 Card #2: DVB-T budget (connected to antenna 1)
 Card #3: DVB-T budget (connected to antenna 2)
 Card #4: DVB-T budget (connected to antenna 1)
 
 So different DVB-cards can receive different multiplexes.
 
 Problem is:
 
 VDR doesn't seem handle correctly multiple CA-entries, when it's saving 
 channel config file.
 
 When defining CA field to 2,4 (editing config file by hand) to let both cards 
 2 and 4 to access channel, VDR sets CA-field to 2. But 
 would be nice if both cards which are capable to receive channel, could do 
 it. In this case only one card gets it.
 
 And it is not possible to limit encrypted channels, which in my opinion is 
 most critical here;
 
 1) When defining CA field to 3,B00 - VDR sets CA-field to 3, and this channel 
 won't be decrypted as it's not identified as Conax.
 2) When defining CA field to B00,3 - VDR sets CA-field to B00, and every card 
 can access this channel.
 
 
 Anyway it would be nice to limit access for devices by frequency (DVB-T/C) 
 and by source (DVB-S, SourceCaps does this, any similar 
 for DVB-T?). Or atleast to get this CA-field limiting working ;)
 
 Testing done with vdr 1.5.15

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