Le mercredi 10 février 2016 à 16:19 -0800, VDR User a écrit :
> Gerald,
>
> You freak out because I suggested an easier solution to yours, and
> then call me a troll for correcting you on your own nonsense. I hope
> you don't think you're fooling anyone with that fake b.s. Take your
> temper
Le mardi 09 février 2016 à 11:35 +0100, Gerald Dachs a écrit :
> Am 2016-02-09 10:43, schrieb Nicolas Huillard:
> > Le mardi 09 février 2016 à 10:33 +0100, Gerald Dachs a écrit :
> >> Am 2016-02-09 10:19, schrieb Nicolas Huillard:
> >> > Hi all,
> >> >
Le mardi 09 février 2016 à 10:33 +0100, Gerald Dachs a écrit :
> Am 2016-02-09 10:19, schrieb Nicolas Huillard:
> > Hi all,
> >
> > My new Raspberry Pi2 install lacks a media player, which begins to be a
> > bit annoying. The current setup :
> > * NFS server
>
Hi all,
My new Raspberry Pi2 install lacks a media player, which begins to be a
bit annoying. The current setup :
* NFS server
* DigitalDevices Octopus Net DVB network server
* VDR + rpihddevice + satip on the Pi2 : live TV, timers, recordings,
etc.
* an old VDR instance on the NFS server plays
Le mardi 09 février 2016 à 11:24 +0100, tho...@reufer.ch a écrit :
> Quoting Nicolas Huillard <nico...@huillard.net>:
>
> > The mplayer plugin seem very old and may not work neatly with the
> > rpihddevice output.
>
> As I understand the mplayer plugin, it just l
Le dimanche 25 octobre 2015 à 12:04 +0100, Klaus Schmidinger a écrit :
> On 10/25/15 11:44, Nicolas Huillard wrote:
> > Hi all,
> >
> > I still have a problem with my new setup:
> > * Raspberry Pi B (256MB system + 256MB video)
> > * MLD 5.0.0 testing distrib
Hi all,
I still have a problem with my new setup:
* Raspberry Pi B (256MB system + 256MB video)
* MLD 5.0.0 testing distribution (http://www.minidvblinux.de/) on a 4GB
class 6 SD card, using VDR 2.2.0.203-207
* vdr-plugin-rpihddevice (from MLD 1:2015.08.24-37+2.2.0.203)
* Octopus Net (firmware
Le dimanche 25 octobre 2015 à 12:04 +0100, Klaus Schmidinger a écrit :
> On 10/25/15 11:44, Nicolas Huillard wrote:
> > Hi all,
> >
> > I still have a problem with my new setup:
> > * Raspberry Pi B (256MB system + 256MB video)
> > * MLD 5.0.0 testing distrib
Le lundi 28 septembre 2015 à 18:30 +0200, fnu a écrit :
> ok, two points just for my couriousity.
>
> 1. Why don't you share channels.conf from your server as you do it with EPG
> data?
I did, but this channel.conf is very old, and lack some channels. I
wanted to take the chance to update it.
ve a 290e I use for DVB-T2 reception and it has worked really well
> > for some time now.
> > Shame you can't buy them anymore :-(
> >
> > On 19 September 2015 at 10:21, Jari Fredriksson <ja...@iki.fi> wrote:
> >
> > > On 17.9.2015 15:01, Nicolas Huilla
> some time now.
> Shame you can't buy them anymore :-(
>
> On 19 September 2015 at 10:21, Jari Fredriksson <ja...@iki.fi> wrote:
>
> > On 17.9.2015 15:01, Nicolas Huillard wrote:
> >
> >> Hello all,
> >>
> >> My previous mail to this
Le vendredi 18 septembre 2015 à 10:21 +0100, Morfsta a écrit :
> On Thu, Sep 17, 2015 at 8:58 PM, Karim wrote:
> > I use TBS6280 (dual tuner, pci-e) from Turbosight in dvb-t mode (no dvb-t2
> > signal here): good card, not expensive and great technical support. Newer
> >
Hello all,
My previous mail to this ML is apparently dated 2011 ;-) Everything was
OK there since then... Except that my Hauppauge Nova-T-500 died
recently, and my ancient PCI cards do not work in the 2013 server.
I'm looking for advice for a new DVB-T2 device, which should :
* have a good
Le jeudi 03 novembre 2011 à 20:57 +, Tony Houghton a écrit :
On Thu, 03 Nov 2011 22:00:10 +0200
prelude prel...@kapsi.fi wrote:
This maybe help:
http://lowbyte.de/vga-sync-fields/vga-sync-fields/README
No, that's so you can slightly adjust the rate at which the display is
refreshed
Le vendredi 28 octobre 2011 à 11:24 +0100, Laz a écrit :
I also suspect that I can run full vdr on the client to allow me to use
some plugins on there?! Not looked into that yet. I suspect I can probably
just use vdr-sxfe as a basic frontend, with lirc forwarding so I can
hide the server
Le vendredi 28 octobre 2011 à 22:59 +0200, Damien Bally a écrit :
I'm making some kind of embedded vdr distribution based on busybox and
minimal X11, the problem is I have no idea of how I can launch vdr and
xineliboutput at startup.
What I recently did, based on Debian + e-tobi + minimal
Le lundi 17 octobre 2011 à 09:39 +0200, brian a écrit :
Looks good. Any chance of underclocking, and getting it totally silent?
cpufreq minimum frequency is 1.6GHz for this Core i3 2100 (1.6-3.1 GHz).
I don't think one can underclock more than that. Maybe the BIOS can
lower voltage, thus heat
Le dimanche 16 octobre 2011 à 14:02 +0300, JJussi a écrit :
Any suggestions for small, powerful, quiet, FullHD VDR client?
So, I search machine what would act as VDR-client, using xineliboutput
with FullHD resolution and machine would have DVI or HDMI connection +
optical audio.
Of
Hi,
I have a new VDR+ server system, based on SandyBridge i3 CPU. This
server is located under the TV set, thus mixes the server (always-on
headless) + client (HD display) roles (previous setup was a Via EK8000
server + Via ML1 client which ended up on the same shelf + another
still-used
Hi all,
For some reason (API/kernel mismatch or so), I can't manage to run a
working DVB scan with either scan, dvbscan or w_scan, and VDR itself
don't seem to catch the new transponders, whatever I do...
Since this is a family urgency, I can't wait to upgrade everything
needed in my VDR server
Le jeudi 21 janvier 2010 à 09:27 -0600, Rob Davis a écrit :
More native support could be good.. However, I wonder what the
advantage would be to having this over an internal pci dvb card or even
a usb one? The pci card is surely cheaper, and the functionality is
already there in VDR?
It may
Hi,
Here is a patch that loads/unloads USB modules in the runvdr script
found in e-tobi and probably Debian packages.
It works since 1 month here, with the Nova-TD-500 PCI card (with onboard
USB), which uses dvb_usb and dvb_usb_dib0700.
Happy new year to everyone ;-)
--
NH
---
Le mardi 05 janvier 2010 à 00:14 +0300, Goga777 a écrit :
I wish we could get away from xine.
how ? does it possible at all ?
softdevice uses ffmpeg with DirectFB, and works wonderfully (worked,
in my case). Lack of X11 brings a lot of little improvements. In a pure
STB setup, X11 is really
Le dimanche 11 octobre 2009 à 13:46 +0200, Klaus Schmidinger a écrit :
The VDR homepage has moved to the new URL
http://www.tvdr.de
TVDR = TV Done Right
Great ! Nothing could be more true.
BTW : is your production instance still that old P5 / K6-2 / 80GB
machine ?
I use these P5 / K6-2
Gerald Dachs a écrit :
VDR User schrieb:
VDR + hdtv has been pretty stable for me for some time now. The few
problems I ran into (with VDPAU) were quickly fixed by the xine-vdpau
devs. I'm not the only one either, I know a bunch of guys doing the
same. It's a highly discussed topic and I'm
Paul Menzel a écrit :
there has been some talk about the new ION chipset from NVIDIA on this
list [1]. Intel also published a board which is said to be very
promising for SD (standard definition) material [2] (at least with the
FRC (frame rate control) patches [3].
This boards seems cool, but
Alex Betis a écrit :
Is there a way to configure VDR show the epgsearch plugin as default guide?
Currently I can access the plugin by pressing green button or from the menu.
I'd like it to replace the default EPG browser when pressing guide button
and another place (less
important for me)
Magnus Hörlin a écrit :
Well, my first imressions of the ION platform (Acer Revo) are very good.
It does the vdpau deinterlacing without problems and so far the video
decoding has not exceeded 1% cpu load for ANY 1080p clip I've tried.
This is the best VDR frontend/XBMC machine I've ever
Hi,
I'm having OSD problems when upgrading. The OSD is normally transparent,
using all 4 or 5 colors, on EPIA ML6000 / CLE266 graphics. When
upgrading kernel + xine + xorg + a few other things, all colors except
yellow are displayed as black, leaving a yellow + black + transparent OSD...
Nicolas Huillard a écrit :
I'm having OSD problems when upgrading. The OSD is normally transparent,
using all 4 or 5 colors, on EPIA ML6000 / CLE266 graphics. When
upgrading kernel + xine + xorg + a few other things, all colors except
yellow are displayed as black, leaving a yellow + black
Nicolas Huillard a écrit :
Everything else seems to be OK (except xvmc_bob_deinterlacing, which
seems to be replaced by one_field).
Still can't find anyting related to this missing deinterlacing...
No deinterlacer work at all (all display a single field, dividing the
vertical resolution by 2
http://www.mini-itx.com/2009/05/04/zotac-ion-itx-atom-mini-itx-board-unboxing-and-salivating
...which means 1080p HD playback from an embedded Mini-ITX board with a
fanless 1.6GHz processor whilst consuming 21W.
The ION-ITX-A has its own DC converter onboard, and is supplied with a
90W AC
Pasi Juppo a écrit :
What's the difference today's functionality? Very small. Only this time
user is shown more information and is provided help (a man page, if you
like) in case of need.
Many plug-ins would benefit from such a core help system.
I never managed to learn the remote keys for
marti...@embl.de a écrit :
Now, as for the instant recording, how about it gets deleted when you zap t
o another channel?
...or when there is no available tuner to continue the older
instant-recording... I think about zapping, when you would like to keep
the previous channel instant
VDR User a écrit :
512MB won't get you far with hdtv. It won't even get you 5 minutes
worth. Needless to say, you'd need at least a few GB of dedicated ram
to even bother with it. At least ram is cheap now as you've pointed
out (especially if you take advantage of MIR's). After seeing how
Rolf Ahrenberg a écrit :
On Sun, 3 May 2009, Tomas Berglund wrote:
Do you mean aspect ratio 2.21:1 ?
+const char *VideoAspectString[] = { 4:3,
+16:9,
+2.21:9
+ };
Besides of that
Matthias Becker a écrit :
and what about anamorphic material?
A 16:9 SD broadcast in fact still is 4:3 but is streached by the TV to
16:9 to look ok (no egg-heads).
Wouldn't it be correct also to draw the OSD anamorphic so that is not
screached by the TV?
Did you get the point? It's
Thomas Hilber a écrit :
On Wed, Jan 21, 2009 at 04:23:59PM +1000, Torgeir Veimo wrote:
There's no english howto anywhere?
sorry, not yet.
Is the below rough summary correct ?
What it currently is :
* a patch set to DRM kernel modules, xine-lib and xineliboutput
* that adds proper interlaced
Ville Aakko a écrit :
BTW there's also an english manual on the site.
I can't find it anywhere. Only german pages and manuals...
Do you have a link ?
--
NH
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Andrey Kuzmin a écrit :
I usually start by installing the latest version of ubuntu on one
computer and then duplicate that directory for every client.
Completely diskless clients booting through PXE or iSCSI from
single image or from dedicated images from server are also worth to
Hi,
Any reason the remotetimers [1] plugin is not part of e-tobi.net [2] ?
Is there an alternative, other than using the remoteosd plugin (that I'm
already using, but have a low WAF).
[1] http://vdr.schmirler.de/
[2] http://www.e-tobi.net/repositories/repositories.html
--
NH
Klaus Schmidinger a écrit :
On 08.01.2009 18:50, user.vdr wrote:
On Tue, Jan 6, 2009 at 7:06 AM, Klaus Schmidinger
klaus.schmidin...@cadsoft.de wrote:
+ The directory name for a recording has been changed from
-MM-DD-hh[.:]mm.pr.lt.rec (pr=priority, lt=lifetime) to
Klaus Schmidinger a écrit :
On 12.01.2009 13:41, Nicolas Huillard wrote:
-MM-DD-hh.mm.ch-ri.rec does not solve the problem of multiple VDR
instances recording the same show.
This is a usual problem of multiple instances sharing a single /video dir.
As we're talking about safety here, why
user.vdr a écrit :
On Fri, Jan 9, 2009 at 11:27 AM, Artem Makhutov ar...@makhutov.org wrote:
What points have to be done to finish 1.7.x and to get to 1.8.0.
In the years I've been using VDR, there has always been many
development versions before Klaus has released a new stable so based
on
Sascha Vogt a écrit :
And the second question is about the preferred distribution to use VDR
with. Are there any distributions optimized for VDR and fast boot times?
(Yes I know [1], but that didn't help me with choosing one optimized for
short boot times.) LinVDR seemed to be such, but the
Sascha Vogt a écrit :
Nicolas Huillard schrieb:
Sascha Vogt a écrit :
And the second question is about the preferred distribution to use VDR
with. Are there any distributions optimized for VDR and fast boot times?
I started with a bare-minimum Debian/e-tobi install (with debootstrap
Klaus Schmidinger a écrit :
If you're using the same compiler as I do, I don't see why such
a typecast is necessary on your side, while on my side it compiles
just fine.
Are you using any different compiler options than me?
Didn't I read x86_64 for Mika, when you may use x86_32, Klaus ?
--
Klaus Schmidinger a écrit :
Up to now VDR has used names like 001.vdr for its recording files.
While moving to Transport Stream as the recording format, I need to
use a different file name extension, and so was wondering which one
to use. My first idea was *.ts, for Transport Stream, but when
Klaus Schmidinger a écrit :
On 04.01.2009 19:21, Nicolas Huillard wrote:
file name was used as an extension). See:
index.vdr
info.vdr
marks.vdr
resume.vdr
Maybe you will find an opportunity to improve this at the same time...
Well, how about leaving the .vdr part
Rolf Ahrenberg a écrit :
On Mon, 15 Dec 2008, Nicolas Huillard wrote:
Is there a way to tell xineliboutput which file to use ? Like adding a
command-line param --config=~/.xine/config_xineliboutput.$(hostname)
The attached patch should implement this - no guarantees.
I hope I'll be able
Jörg Knitter a écrit :
Klaus Schmidinger wrote:
Well, tell that to people writing plugins for such output devices.
I don't see where *I* would be involved there?!
Are there enough interfaces to be able to read the and control the OSD
for including them seamlessly it into a different
BoNuZZZ a écrit :
Can I start vdr and xineliboutput separately? For example, vdr starts
when computer is on, so it works always. But xinelibout is starting
when I close xbmc.
Yes. You run the plugin in VDR, with no local front-end. You then launch
vdr-sxfe (X) or vdr-fbfe (DirectFB) front-end
Udo Richter a écrit :
On 12.12.2008 18:06, VDR User wrote:
I can say I've seen many people move away from VDR because it doesn't
provide a good solution to this. After years of using standalone VDR
boxes, I too would love if we had the option to use a networked VDR
with each client being
Frank Schmirler a écrit :
On Mon, 24 Nov 2008 21:41:54 +0100, Nicolas Huillard wrote
This also works around an annoying bug in the (non-upgraded) EPIA
BIOS: the PXE LAN boot does not always initialize the network
interface after a shutdown. One have to unplug power to boot
correctly next
Frank Schmirler a écrit :
On Tue, 25 Nov 2008 14:39:19 +0100, Nicolas Huillard wrote
I'd try to insert it on the PXE kernel command-line, but it's
explicitely ignored by the kernel :
ml6000 kernel: Unknown boot option `via_rhine.avoid_D3=1': ignoring
...or implicitely, when I just add
Torgeir Veimo a écrit :
On 24 Nov 2008, at 19:37, Nicolas Huillard wrote:
Blah, only one PCI slot. Where are proper low-power MB's with 2 or
more PCI
slots for DVB-cards? And how much does the server (NFS, DVB-
card(s)) use
power?
No use of PCI in the client.
Do you put the DVB
Mika Laitio a écrit :
What I have now tried to search for is a fast booting client for my old
P700, that could boot automatically to X with dummy user and then launch
the vdr-xineliboutput.
The ideal would be that once bios checks have been done, rest of the boot
would for getting X and
Darren Salt a écrit :
I demand that Nicolas Huillard may or may not have written...
[snip]
vdr 1.6.0
xineliboutput 1.0.3
xine 1.1.2
Maybe you should upgrade to 1.1.15. :-)
all Debian etch + e-tobi repository
Well... I think I'll have a step at 1.1.14, when e-tobi.net is ready
Alex Betis a écrit :
On Mon, Nov 24, 2008 at 3:24 PM, Nicolas Huillard [EMAIL PROTECTED]wrote:
From kernel first log line in the syslog server (I guess timestamps are
when rcS.d/ scripts start to run, ie. does not include kernel load time
+ initrd), to LIRC accepting the VDR client
Torgeir Veimo a écrit :
On 22 Nov 2008, at 21:04, Nicolas Huillard wrote:
I must tell that the xxmc (XVMC-VLD) decoding is nearly perfect, the
OSD is fully transparent on this, and does not take any CPU at all,
and the system is on par with softdevice.
What cpu usage did you get when
Hi,
I'm currently upgrading most of my VDR systems (going to diskless NFS
clients), using preferably prebuilt packages (so much easier to maintain
than custom patched ones ;-).
I was wondering what was the plan regarding the upcoming Debian lenny in
e-tobi repo ?
There are some packages I'd
Hi all,
I'd like to report that I'm really impressed by the new setup I now
have. The most problematic thing was proper transparent OSD which would
not eat much CPU. I must tell that the xxmc (XVMC-VLD) decoding is
nearly perfect, the OSD is fully transparent on this, and does not take
any
Hi,
This is the most annoying bug : after some time tweaking the video
output (which works), the video submenu just crashes VDR upon closing
(with back, menu or ok keys).
No matter that I change setting or not : closing will crash.
The current video setup is :
xineliboutput.Video.AspectRatio =
Ondrej Wisniewski a écrit :
With VDR getting ready for HD-TV it seems that today the MPEG4 decoding
can only be done on a high end processor or an external decoder card.
Many people are still waiting for a FF DVB-S2 card but it doesn't look
very promising at the moment.
So I was
Klaus Schmidinger a écrit :
Should there be a stable version 1.6.0 now, based on what's in
version 1.5.14, but without DVB-S2 or even H.264 support?
Yes or No?
1) a stable release shouldn't stop the current development for a long
time, thus shouldn't delay the S2/H264 and other neat
Reinhard Nissl a écrit :
Dominique Matz schrieb:
sound very good, but vdr as root do not :-(
do you think it is possible to use this or something else with an non
root user?
Well, only the LIRC_PRIORITYBOOST option requires root privileges
to work. If you don't have root privileges,
Stefan Hußfeldt a écrit :
Juergen Sauer schrieb:
So, which remote boot capaple distri do you use ?
Which is best to choose ?
I'm using debian (server, diskless client) with e-tobis VDR repository.Don't
know, if it's the best...
http://www.vdr-portal.de/board/thread.php?threadid=40936
Simon Baxter a écrit :
Simon Baxter a écrit :
I'd like to go fanless and cool. What I like about the shuttle is it's
size. The 1x PCI is fine, as is the VIA unichrome VGA s-video out.
Any ideas on a small compact fanless (DEAD quiet) case motherboard??
* mobo : compact + fanless = VIA
, EPIA EK-8000)
--
Nicolas Huillard
[EMAIL PROTECTED]
Fixe : +33 1 39 27 06 10
Mobile : +33 6 50 27 69 08
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
covert covert a écrit :
My question is what CPU should I chose for good noise reducing , heat
reducing solutions.
The most efficient CPU are still the VIA ones... Low power, very low
heat, very low noise.
There are lots of EPIA mobos (Mini-ITX for factor) with fanless CPUs
around. With these,
Hi all,
The subject says it all. Since the PCI card has an always-lit LED on it,
I wondered if the IR receiver was also powered and could turn on the
computer, using the green power button on the remote.
Since it's not working for me, are there any BIOS settings to allow that ?
TIA,
--
NH
71 matches
Mail list logo