I've successfully installed the eHD, but I use vdr-1.7.0. With that it
went without any probs using the mentioned HOWTO. ( And I didn't have to
patch any eHD-driver either. Thanks to Niels Wagenaar )
Per
Josce skrev:
I have now been working far too long on installing the eHD card.
Without
Jouni Karvo wrote:
Petri Helin wrote:
really causes VDR to not start also. My aim really was to start some
discussion on whether that should be changed. I myself think that VDR
should start although some plugin fails to start. I'd hate to find out
that some timed recording failed because
On Thu, 18 Sep 2008 18:54:33 +, Josce wrote
It now stops with this error:
In file included from HdTrueColorOsd.c:34:
fontsml-iso8859-15.c:1: error: 'tPixelData' in class 'cFont' does
not name a type HdTrueColorOsd.c: In member function 'int
Reel::HdTrueColorOsd::CacheFont(const
I had the same error. IIRC your VDR is missing the truecolor OSD patch:
http://www.vdr-wiki.de/wiki/index.php/OpenSUSE_VDR_DVB-S2_-_Teil3:_VDR#Patches_f.C3.BCr_Reelbox_Plugin_herunterladen
Good luck!
Frank
Thank you!
This did the trick. Some problems with the picture, but getting there
Did you try:
hg pull http://arvdr-dev.free-x.de:8080/testdvb/
hg pull http://jusst.de/hg/multiproto/
hg pull http://jusst.de/hg/multiproto_plus/
Tried http://jusst.de/hg/multiproto_plus/ and managed to get it without
problems.
Compiling it as I type this and so far no problems :)
Is there
Perhaps vdr in its developing phase support both, so when ever the API that
wins vdr and its users can continue without the API holding it back? What
does Klaus have to say about this?
On 19/09/2008, Niels Wagenaar [EMAIL PROTECTED] wrote:
-Original message-
From: Josce [EMAIL
-Original message-
From: Josce [EMAIL PROTECTED]
Sent: Fri 19-09-2008 13:36
To: [EMAIL PROTECTED];
Subject: RE: [vdr] reelbox plugin - help compiling
Did you try:
hg pull http://arvdr-dev.free-x.de:8080/testdvb/
hg pull http://jusst.de/hg/multiproto/
hg pull
I like that VDR won't load if a plugin failed. That means there was a
problem, and I should go fix it. Also, it's the plugins job to
continue on non-fatal errors, not VDR. How would VDR even know whats
a non-fatal error for a certain plugin? From VDR's perspective either
the plugin is working
VDR User wrote:
I like that VDR won't load if a plugin failed. That means there was a
problem, and I should go fix it. Also, it's the plugins job to
continue on non-fatal errors, not VDR. How would VDR even know whats
a non-fatal error for a certain plugin? From VDR's perspective either
On Fri, Sep 19, 2008 at 8:20 AM, Petri Helin [EMAIL PROTECTED] wrote:
But why should even a fatal error (from plugin's perspective) cause VDR
to not start? It should only cause the plugin not to be loaded. Of
course plugins could also implement more intelligent initialization and
try to deal
On 09/19/08 17:20, Petri Helin wrote:
VDR User wrote:
I like that VDR won't load if a plugin failed. That means there was a
problem, and I should go fix it. Also, it's the plugins job to
continue on non-fatal errors, not VDR. How would VDR even know whats
a non-fatal error for a certain
VDR User wrote:
I think it's a huge assumption (and incorrect one) to say the main
function of VDR is to record tv shows. I know many people who use it
for watching live tv, email notices, weather report, playing other
media something like an htpc, etc.
Ok, let me rephrase it: for my
So, if a plugin thinks VDR can well run without it, it should just
return true. If it's a plugin that's absolutely necessary for operation,
it shall return false upon failure. VDR can't know that by itself.
Maybe all plugins could have a setting on failure terminate vdr ?
Then the user could
Hi,
I was now able to compile a driver and get it running with VDR 1.7.1
here a short summary:
To get the driver:
cd /usr/local/src/
mkdir hvr4000
mkdir -p hvr4000/liblianindvb-test
cd hvr4000/liblianindvb-test
hg init
hg pull http://arvdr-dev.free-x.de:8080/testdvb/
hg update
Compile the
Petri Helin wrote:
In fact I am already wondering why plugins are not
hot-pluggable...
They are, to some degree, by using the proxy plugin. The proxy plugin
can delay loading a plugin, and for some plugins it can unload a plugin
while VDR is running. It can also do the requested
Op Vr, 19 september, 2008 21:21, schreef Josce:
-- SNIP --
I can't understand why compiler.h is not found, since I have no problems
finding it :)
Getting tired and frustrated, better give this some rest ...
Edit Make.config and change/edit the DVBDIR variable. I guess you don't
have it
Udo Richter wrote:
Petri Helin wrote:
In fact I am already wondering why plugins are not
hot-pluggable...
They are, to some degree, by using the proxy plugin. The proxy plugin
can delay loading a plugin, and for some plugins it can unload a plugin
while VDR is running. It can also do
I've got my box setup running Debian Etch 2.6.24-rc4, vdr 1.6.2 with Reinhard's
patches, the latest xine-lib compiled with the latest external ffmpeg, and
vdr-xine. With that configuration I can watch SD and HD in mpeg2 and mpeg4/h264
to 1080p resolutions. I installed the latest CVS of
18 matches
Mail list logo
