Dear all,
I have lurked a while on this list but until now have not had reason to
post.
I am unable to configure xineliboutput to my liking. I don't imagine I
am the only one with this issue, but I have not been able to find a
solution, either by trial and error or by googling. I would
Torgeir Veimo wrote:
So (finally) a direct question: how do people with 4:3 output devices
and vdr with xineliboutput configure their boxes?
(shameless plug) Did you actually try softdevice?
Dear Torgeir,
Nothing shameless about the plug! Yes, I have tried softdevice (recent
CVS and
by xineliboutput (not tested).
--
__
Ian Bates
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Country: UK (receiving Astra 28.2E, Astra 19.2E and Hotbird-13E)
Transmission: DVB-S, DVB-S2 (DVB-T technically available but locally
poor reception)
Encoding: MPEG-2 SD, H.264
Hardware: Hauppauge NOVA PCI (DVB-S), Hauppauge HVR4000 (DVB-S/S2) (-T
available but untested)
Hello,
When editing recordings I am struggling to fine tune marker placement
as adjustments made with '4' and '6' keys while moving the marker as
indicated by the time line do not update the video display with the
corresponding position in the recording.
Current setup:
SW: VDR-1.7.9
On 29 Sep 2009, at 20:54, Matthias Schwarzott wrote:
On Dienstag, 29. September 2009, Helmut Auer wrote:
Hi list!
lirc starting from version 0.8.6, does use the socket /var/run/
lirc/lircd
instead of /dev/lircd, so all apps not using liblirc_client need
to be
changed. Else IR will not
On 6 Jan 2010, at 13:22, Tomasz Bubel wrote:
[...]
- Added support for DVB cards with multiple fontends. Note that
this only
works for DVB cards where each frontend can be used independently
of all
the others on the same adapter.
[...]
Any chance of using using DVB-T frontend on
On 1 Feb 2010, at 22:24, abbe normal wrote:
On 2/1/10, VDR User user@gmail.com wrote:
On Mon, Feb 1, 2010 at 7:12 AM, Halim Sahin halim.sa...@t-online.de wrote:
Hi List and Klaus,
It would be really nice if vdr could support diseqc setup directly in
vdr.
I don't know if this can be
On 6 Feb 2010, at 11:57, Klaus Schmidinger wrote:
On 02.02.2010 07:35, Ian Bates wrote:
On 1 Feb 2010, at 22:24, abbe normal wrote:
On 2/1/10, VDR User user@gmail.com wrote:
On Mon, Feb 1, 2010 at 7:12 AM, Halim Sahin halim.sa...@t-online.de
wrote:
Hi List and Klaus,
It would
Good Morning,
From what I recall of discussions held on this list the reasons are based on,
in no particular order :),
First
- initial basic common sense
then an iterative process involving
- satisfaction of common corner use cases
- satisfaction of problem use cases
- keeping most people
On 21 Sep 2010, at 16:06, support.intranet wrote:
The attached patch (for VDR 1.7.16) implements support for multituner cards
where only one tuner can be active at one time, the so called shared frontend
cards (notably the HVR-4000 and its derivatives).
Currently VDR tries to open all the
On 25 Sep 2010, at 10:20, Simon Baxter wrote:
Hi
My dvb-s LNB is a Ku-Band LNBG DKF-2024.
The box says:
Input 11.70-12.50 Ghz
L.O. 10.75 Ghz
Noise 0.6dB
Gain 60dB
If I set VDR up as follows:
Use DiSEqC:no
SLOF (MHz):10750
Low LNB frequency (MHz):
Hi,
Did you solve the eepg problem? I am experiencing the same error.
Slackware64-current, just upgraded a bunch of stuff (including xserver),
previously successful compile of eepg when recompiled eepg gives me the same
error as below. The libvdr-eepg.so from the earlier compile still works
13 matches
Mail list logo
