Hi all man, there is a lot of time that im trying to make work correctly
dvb-s2 but Ive not understand how to make work coreavc, there is any
sep-by-step or similar howto or wiki???
Bye and tnx a lot for your biggest work ;-)
_
La mia Cartella di Posta in Arrivo è protetta con SP
Hi all,
I have a problem with Xineliboutput's OSD. In low resolution videos it
look doesn't fit the screen. It seems as if Xineliboutput actually
switches the resolution of the (VGA) monitor.
So how do I force Xineliboutput to first scale the _video_ to screen
(not vice versa) and then put OSD
> >> *sigh* messing with kernel stuff sucks. Does a vdr built with the
> >> multiproto headers at least also work on vanilla kernels ie stable
> >> dvb drivers? That way one would only need to use different headers
> >> for building vdr but no extra kernel modules at run time.
so, what do you mean
Morfsta wrote:
> Manu,
>
> Firstly, thanks for all your work - it's appreciated.
>
> Is the interface working properly for reading the signal strength, BER
> and status?
Currently, there is a small confusion. Most drivers in kernel, just
report some
crap as signal strength, snr etc.
For the ST
Manu Abraham wrote:
> Klaus Schmidinger wrote:
>> On 01/28/08 02:49, Manu Abraham wrote:
>>> Ludwig Nussel wrote:
Klaus Schmidinger wrote:
> On 01/27/08 16:25, Ludwig Nussel wrote:
>> Klaus Schmidinger wrote:
>>> - Implemented handling of DVB-S2 (thanks to Marco Schlüßler and
Klaus Schmidinger wrote:
> On 01/28/08 02:49, Manu Abraham wrote:
>> Ludwig Nussel wrote:
>>> Klaus Schmidinger wrote:
On 01/27/08 16:25, Ludwig Nussel wrote:
> Klaus Schmidinger wrote:
>> - Implemented handling of DVB-S2 (thanks to Marco Schlüßler and Reinhald
>> Nissl
>> f
On Jan 28, 2008 5:15 PM, Darren Salt
<[EMAIL PROTECTED]> pedantically wrote:
> c++filt says "cDevice::SwitchChannel(cChannel const*, cDevice*)". Maybe you
> need to recompile something...?
>
> [snip ; don't top post]
Nope, it's all compiled - just doublechecked with fresh source: -
vdr-1.5.14
vd
Klaus Schmidinger wrote:
> On 01/28/08 03:01, Manu Abraham wrote:
>> Klaus Schmidinger wrote:
>>> On 01/27/08 17:46, Thomas Schmidt wrote:
I really hope that either vdr 1.5.x gets a compile-time-switch to
build and run with the vanilla kernel-sources or even better that the
multiprot
I demand that Morfsta may or may not have top-posted...
> Seems that I spoke too soon - I get a problem running rotor on my
> system after compilation: -
> vdr: ./PLUGINS/lib/libvdr-rotor.so.1.5.14: undefined symbol:
> _ZN7cDevice13SwitchChannelEPK8cChannelPS_
> Whatever I try I can't seem to fi
On 01/28/08 17:50, Matthias Fechner wrote:
> Hi,
>
> Klaus Schmidinger wrote:
>> - Implemented handling of DVB-S2 (thanks to Marco Schlüßler and Reinhald
>> Nissl
>> for a patch that was used to implement this). VDR now requires the
>> "multiproto"
>> DVB driver, e.g. from http://jusst.de/hg
On 01/28/08 18:15, Klaus Schmidinger wrote:
> On 01/28/08 02:49, Manu Abraham wrote:
>> Ludwig Nussel wrote:
>>> Klaus Schmidinger wrote:
On 01/27/08 16:25, Ludwig Nussel wrote:
> Klaus Schmidinger wrote:
>> - Implemented handling of DVB-S2 (thanks to Marco Schlüßler and Reinhald
On 01/28/08 02:49, Manu Abraham wrote:
> Ludwig Nussel wrote:
>> Klaus Schmidinger wrote:
>>> On 01/27/08 16:25, Ludwig Nussel wrote:
Klaus Schmidinger wrote:
> - Implemented handling of DVB-S2 (thanks to Marco Schlüßler and Reinhald
> Nissl
> for a patch that was used to implem
Great thanks to Manu and Klaus for their latest updates.
The attached patch adds HVR4000 support to it. It has been tested successfully
together with kernel 2.6.24 on i686 using VDR 1.4.7 (DVB-S only) and VDR
1.5.14.
Regards,
Holger
multiproto-hvr4k-2008-01-28.patch.bz2
Description: BZip2
Hi,
Klaus Schmidinger wrote:
> - Implemented handling of DVB-S2 (thanks to Marco Schlüßler and Reinhald Nissl
> for a patch that was used to implement this). VDR now requires the
> "multiproto"
> DVB driver, e.g. from http://jusst.de/hg/multiproto.
if I have only two normal DVB-S cards (one
Manu,
Firstly, thanks for all your work - it's appreciated.
Is the interface working properly for reading the signal strength, BER
and status?
The rotor plugin doesnt return anything and I can't get anything out
of VDR-Femon.
Is it working OK with the TT 3200?
BTW I have a TT3200 on order so I
On Mon, Jan 28, 2008 at 01:40:15PM +0100, Klaus Schmidinger wrote:
> Just so I understand this correctly: the driver that is currently in
> the kernel is *not* able to do DVB-S2, while the driver at
> http://jusst.de/hg/multiproto *is* able to do it. And these are the only
> two driver versions we
On 01/28/08 03:01, Manu Abraham wrote:
> Klaus Schmidinger wrote:
>> On 01/27/08 17:46, Thomas Schmidt wrote:
>>> I really hope that either vdr 1.5.x gets a compile-time-switch to
>>> build and run with the vanilla kernel-sources or even better that the
>>> multiproto-drivers will be merged into th
Le lundi 28 janvier 2008 à 12:07 +0100, Ondrej Wisniewski a écrit :
> > There is a problem with xine, the openchrome driver and VDR. You are too
> > slow - I am seeing 9-12% CPU with current openchrome even with this bug.
> >
> > I am using vdr-xine rather than xineliboutput
> that was not the
Tony Grant wrote:
>
> There is a problem with xine, the openchrome driver and VDR. You are too
> slow - I am seeing 9-12% CPU with current openchrome even with this bug.
>
> I am using vdr-xine rather than xineliboutput
>
> Cheers
>
> Tony
Hi Tony,
that was not the answer I was hoping for ;-)
Seems that I spoke too soon - I get a problem running rotor on my
system after compilation: -
vdr: ./PLUGINS/lib/libvdr-rotor.so.1.5.14: undefined symbol:
_ZN7cDevice13SwitchChannelEPK8cChannelPS_
Whatever I try I can't seem to fix it. Reverting back to my old
version of rotor works fine.
On J
> Well, multiproto doesn't even compile on a current (2.6.24) kernel ..
> or I am doing something really wrong.
You must be.
Compiles and runs fine here with a plain vanilla 2.6.24 kernel (i686) and the
latest multiproto tree.
Regards,
Holger
___
v
I got the following error when compiling 1.5.14 with h264 patch
applied and your VDR diff from the tgz: -
g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -c -DREMOTE_KBD
-DLIRC_DEVICE=\"/dev/lircd\" -DRCU_DEVICE=\"/dev/ttyS1\" -D_GNU_SOURCE
-DVIDEODIR=\"/video\" -DCONFDIR=\"/video\"
-DPLUGI
Le lundi 28 janvier 2008 à 09:44 +0100, Ondrej Wisniewski a écrit :
> I am experimenting with xineliboutput using the xxmc video driver for
> the local sxfe frontend on an EPIA-M1 board with CLE266. I have the
> OpenChrome Drivers installed.
> MPEG2 HW decoding seems usually to work, I get
Hello again,
Am Montag 28 Januar 2008 10:10:31 schrieb Mario Aistleitner:
> there is a small update for the clock plugin available. The new version can
> be found here [1]
>
> 2008-01-28: Version 0.0.10 (thanks to Tobias Grimm)
> - Some corrections to avoid Warnings during make.
I am sorry but I
Hello,
there is a small update for the clock plugin available. The new version can be
found here [1]
2008-01-28: Version 0.0.10 (thanks to Tobias Grimm)
- Some corrections to avoid Warnings during make.
[1] http://vdr.aistleitner.info/vdr-clock-0.0.7.tgz
Greetings,
Mario
Hi,
I am experimenting with xineliboutput using the xxmc video driver for
the local sxfe frontend on an EPIA-M1 board with CLE266. I have the
OpenChrome Drivers installed.
MPEG2 HW decoding seems usually to work, I get around 25% CPU usage.
However, when I bring up VDRs OSD everything becom
Udo Richter wrote:
> Asking myself if I want to build kernels and drivers for 4 different PCs
> or try my luck with an old DVB API patch for vdr-1.5.14, I've chosen the
> latter. The attached patch implements fallback for VDR in case no
> multiproto DVB driver headers are available.
Nice, thank
27 matches
Mail list logo
