Hi (again)!
I've found my problem, I compiled VDR against my kernel (2.6.23), not
against the include files from the multiproto tree, so a small change in
Make.config and recompilation of VDR and it works, great!
/Lars
On Wed, Jan 02, 2008 at 10:51:56AM +0100,
[EMAIL PROTECTED] wrote:
> Hi!
>
On Wed, Jan 02, 2008 at 11:38:15PM +0100, Reinhard Nissl wrote:
Hello,
> Hmm, I can only think of the following scenario:
> - you've pulled before me pushing version number
> - compiled
> - installed
> - you've pulled again, this time after pushing the version number
> - compiled, using the pre
Hi,
Gregoire Favre schrieb:
> Strange I only use xine-lib-1.2, I have the /usr/include/xine/vdr.h
> which has the
> XINE_VDR_VERSION as 801
>
> But I still get the :
>
> vdr-xine: Client reports unsupported version 712 => disconnecting!
> vdr-xine: Client connect failed!
>
> I think when I com
> I don't know why it fails (I'm using VDR 1.5.12 with text2skin
> currently, on Gentoo, so it is possible to compile it). but to get the
> errors in English build by typing 'LANG=C make' (i.e. change the LANG
> variable during compile). That way you'll may get more answers, I
> don't know how many
Hi,
Manu Abraham schrieb:
>>> The patched version doesn't look at the device capability flags, before
>>> issuing a tune ?
>>> Or is something else wrong/missing ?
>>
>> I must admit, I didn't have a look at the source code so far, but
>> from what I recall, I don't think that it is that easy. I
Hi,
2008/1/1, Andrey Kuzmin <[EMAIL PROTECTED]>:
>
> getting build error:
>
> make[1]: Entering directory `/ego/vdr/33/vdr-1.5.12/PLUGINS/src/text2skin'
> g++ -Wall -Woverloaded-virtual -O2 -g -c -DHAVE_IMAGEMAGICK -DHAVE_FREETYPE
> -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"text2skin"' -I/usr/include/fr
On Wed, Jan 02, 2008 at 06:23:24PM +0100, Reinhard Nissl wrote:
> That's not correct. The check ensures that both ends of the
> connection are compatible.
>
> Maybe it was no good idea to not mention in the announcement that
> this time xine-lib-1.1 needs to be patched or that you need to
> pull
> I think this might have been covered before, but the only problem I
> now see is with interlaced and spatial direct mode (particularly on
> the French and Polish HD channels): -
>
> [h264 @ 0x2d0b0700]Interlaced pictures + spatial direct mode is
> not implemented
> [h264 @ 0x2d0b0700]Int
Anssi Hannula schrieb:
> Thomas Schmidt wrote:
>
>> Hi,
>>
>> * Marcel Witte schrieb am 02.01.08, um 19:39 Uhr:
>>
>>> why doesn't svdrp support a "channel 0" like real vdr? If I press <0> on
>>> my remote, I can return to my last channel, but if I try "svdrpsend.pl
>>> chan 0" I get only "
Thomas Schmidt schrieb:
> Hi,
>
> * Marcel Witte schrieb am 02.01.08, um 19:39 Uhr:
>
>> why doesn't svdrp support a "channel 0" like real vdr? If I press <0> on
>> my remote, I can return to my last channel, but if I try "svdrpsend.pl
>> chan 0" I get only "501 Undefined channel "0"" Is it poss
Thomas Schmidt wrote:
> Hi,
>
> * Marcel Witte schrieb am 02.01.08, um 19:39 Uhr:
>> why doesn't svdrp support a "channel 0" like real vdr? If I press <0> on
>> my remote, I can return to my last channel, but if I try "svdrpsend.pl
>> chan 0" I get only "501 Undefined channel "0"" Is it possible t
Hi,
* Marcel Witte schrieb am 02.01.08, um 19:39 Uhr:
> why doesn't svdrp support a "channel 0" like real vdr? If I press <0> on
> my remote, I can return to my last channel, but if I try "svdrpsend.pl
> chan 0" I get only "501 Undefined channel "0"" Is it possible to add
> this functionality to s
Hi
why doesn't svdrp support a "channel 0" like real vdr? If I press <0> on
my remote, I can return to my last channel, but if I try "svdrpsend.pl
chan 0" I get only "501 Undefined channel "0"" Is it possible to add
this functionality to svdrp?
Greets and a happy new year!
Marcel
___
Reinhard Nissl wrote:
> Hi,
>
> Manu Abraham schrieb:
>
>>> I know DVB-S2 cards can do DVB-S that's the reason to force VDR to use
>>> DVB-S only cards for DVB-S before the DVB-S2 ones, which if you want a
>>> DVB-S2 channels, so is your DVB-S2 cards free.
>>>
>>> But one should get a way to tell
Hi,
Manu Abraham schrieb:
>> I know DVB-S2 cards can do DVB-S that's the reason to force VDR to use
>> DVB-S only cards for DVB-S before the DVB-S2 ones, which if you want a
>> DVB-S2 channels, so is your DVB-S2 cards free.
>>
>> But one should get a way to tell VDR no to try to tune DVB-S2 chann
Hi,
Ales Jurik schrieb:
>> vdr-xine: Client connecting ...
>> vdr-xine: Client reports unsupported version 712 => disconnecting!
>> vdr-xine: Client connect failed!
>
> The same problem had I. In xineCommon.h I've changed MIN_XINE_VDR_VERSION to
> 712 (from 801) and everything seems to be ok.
A diff of cx22702.c, cx22702.h and cx22702.mod.c between the normal hg
of v4l-dvb and the multiproto tree reveals no differences...
Almost the same for tda1004x (tda1004x.c makes reference to an include
for moduleparam.h) Is it these frontend modules that are the relevant
ones?
> If the driver wh
Morfsta wrote:
>> Over here, tests were done on STB0899, STV0299 and TDA10021 based
>> all work out of the same multiproto tree (http://jusst.de.hg/multiproto)
>
> There is something wrong then as it does not tune in vdr-1.5.12. I
> have the following DVB-T frontends: -
>
> [ 9539.157598] DVB: re
Gregoire Favre wrote:
> On Wed, Jan 02, 2008 at 07:32:13PM +0400, Manu Abraham wrote:
>
>> No, that seems silly. The DVB-S2 card works for DVB-S also. It should be
>> able
>> to use all the cards. Though you can't ask a DVB-S card to tune to DVB-S2,
>> that's all the limitation it poses.
>
> :-
> Over here, tests were done on STB0899, STV0299 and TDA10021 based
> all work out of the same multiproto tree (http://jusst.de.hg/multiproto)
There is something wrong then as it does not tune in vdr-1.5.12. I
have the following DVB-T frontends: -
[ 9539.157598] DVB: registering frontend 1 (Conex
On Wed, Jan 02, 2008 at 07:32:13PM +0400, Manu Abraham wrote:
> No, that seems silly. The DVB-S2 card works for DVB-S also. It should be able
> to use all the cards. Though you can't ask a DVB-S card to tune to DVB-S2,
> that's all the limitation it poses.
:-)
I know DVB-S2 cards can do DVB-S t
Gregoire Favre wrote:
> On Wed, Jan 02, 2008 at 07:12:52PM +0400, Manu Abraham wrote:
>
>> Over here, tests were done on STB0899, STV0299 and TDA10021 based
>> all work out of the same multiproto tree (http://jusst.de.hg/multiproto)
>
> Do you mean VDR keep the DVB-S2 card for DVB-S2 channels and
On Wed, Jan 02, 2008 at 07:12:52PM +0400, Manu Abraham wrote:
> Over here, tests were done on STB0899, STV0299 and TDA10021 based
> all work out of the same multiproto tree (http://jusst.de.hg/multiproto)
Do you mean VDR keep the DVB-S2 card for DVB-S2 channels and use the
others for DVB-S usage
Morfsta wrote:
>> Is there a way to use more than a card with it when only one is DVB-S2
>> capable ?
>
> I just dropped a mail to Reinhard asking the same question. My
> "production" system runs 2 DVB-T cards that currently don't work with
> vdr-1.5.12 / multiproto. I would love to start using it
On Wed, Jan 02, 2008 at 02:48:09PM +, Morfsta wrote:
> > Is there a way to use more than a card with it when only one is DVB-S2
> > capable ?
I could also use two separates VDR as my two other cards are supported
by multiproto and put DVB-S2 channels only on the vdr which run the
DVB-S2 card,
> Is there a way to use more than a card with it when only one is DVB-S2
> capable ?
I just dropped a mail to Reinhard asking the same question. My
"production" system runs 2 DVB-T cards that currently don't work with
vdr-1.5.12 / multiproto. I would love to start using it full time but
until I ca
On Tue, Jan 01, 2008 at 11:15:58PM +0100, Reinhard Nissl wrote:
Hello :-)
> The patches now include my recently released speedup patches as
> well as an unreleased speedup patch for cAudioRepacker and
> cVideoRepacker, because at least the latter one would have been
> hard to extract separately.
On Wed, 2 Jan 2008 11:59:36 +, in gmane.linux.vdr Morfsta wrote:
> On Jan 2, 2008 11:08 AM, Torgeir Veimo <[EMAIL PROTECTED]> wrote:
>> A howto outlining the steps you've taken to get this to work would be
>> appreciated! :)
>>
>
> I used a lot of information from: -
>
> http://www.vdr-wiki.
S2 is required for channel4 HD, not for BBC HD - they are running
MPEG4 DVB-S at the moment.
See http://www.lyngsat.com/hd/28east.html
On Jan 2, 2008 12:04 PM, Torgeir Veimo <[EMAIL PROTECTED]> wrote:
> Is S2 currently required to get BBC HD or CH4 HD? I've got a dvb-s card set
> up against Sky F
On 2 Jan 2008, at 21:59, Morfsta wrote:
1) Download and make install the multiproto tree from
http://jusst.de/hg/multiproto. I had to apply the HVR4000 patch for my
Hauppauge Nova S2
Is S2 currently required to get BBC HD or CH4 HD? I've got a dvb-s
card set up against Sky FTA, but no S2 ca
On Jan 2, 2008 11:08 AM, Torgeir Veimo <[EMAIL PROTECTED]> wrote:
> A howto outlining the steps you've taken to get this to work would be
> appreciated! :)
>
>
> --
> Torgeir Veimo
> [EMAIL PROTECTED]
>
Hi Torgeir,
I used a lot of information from: -
http://www.vdr-wiki.de/wiki/index.php/OpenSuS
On Wednesday 02 January 2008, Gregoire Favre wrote:
> vdr-xine: Client connecting ...
> vdr-xine: Client reports unsupported version 712 => disconnecting!
> vdr-xine: Client connect failed!
>
The same problem had I. In xineCommon.h I've changed MIN_XINE_VDR_VERSION to
712 (from 801) and everything
On 2 Jan 2008, at 21:04, Morfsta wrote:
> I can view channels such as BBC HD, Channel 4 HD and others perfectly.
A howto outlining the steps you've taken to get this to work would be
appreciated! :)
--
Torgeir Veimo
[EMAIL PROTECTED]
___
vdr
Reinhard,
Wow! I am running vdr-1.5.12 with the new xine-lib CVS (with your loop
filter and speed over accuracy changes enabled) alongside FFMPEG built
for 64bit linux on a k8 (AMD dual core BE-2350 processor overclocked
at 2.7Ghz) and the results are nothing short of amazing! Firstly I
would like
Hi!
I have discovered two more things:
1. When VDR have neeb running a while my HDTV-entries looks like this in
channels.conf;
SVT HD;Telenor:11421:hC23:S1.0W:25000:10512+512:640=sve;641=sve:0:0:3801:70:14:0
As you can see the auto update function in VDR have changed :hC23M5S1Z35: to
:hC23: -
35 matches
Mail list logo
