Hi,
AFAIK vdr 1.4.7 doesn't fix the error with subtitles not being
recorded (well, at least it's not in the changelog; OTOH I've
understod that the problem lies in the plugin, but then again I tried
vdr-subtitles 0.5.0 with vdr 1.4.6, and it had no effect). VDR 1.5.5
works fine for me in this
On 6/30/07, Stone [EMAIL PROTECTED] wrote:
vdr: [7841] connect from 127.0.0.1, port 49972 - accepted
vdr: [7841] grabbing to JPEG 70 384 288
Can I hardcode the default resolution from within VDR or the kernel
driver?
Best Regards.
Does it work if you use the v4lctl method?
Are
Stone wrote:
On 6/30/07, *Stone* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
vdr: [7841] connect from 127.0.0.1 http://127.0.0.1/, port
49972 - accepted
vdr: [7841] grabbing to JPEG 70 384 288
Can I hardcode the default resolution
On Friday 29 June 2007 18:24, Georg Acher wrote:
On Fri, Jun 29, 2007 at 08:21:45AM -0700, Jeremy Jones wrote:
I checked out the latest Reelbox testing svn code and browsed the code to
see if it supports this device. I didn't look too thoroughly but it appears
the reelbox-0.9.0 plugin
On 30 Jun 2007, at 12:17, Anssi Hannula wrote:
If I understood correctly, you only need proprietary parts for the
kernel that runs *in* the card. The kernel running on your actual
system
does not need proprietary parts, leaving you free to use a
different kernel.
The binary provision for
Stefan Lucke [EMAIL PROTECTED] wrote:
They decide on which kernel it runs. If I need for some other device
a different kernel which they don't / won't support, I'm left alone.
that's exactly what the GPL tries to prevent.
To my opinion that is a nogo way.
I doubt if that's compatible with
Anssi Hannula [EMAIL PROTECTED] wrote:
If I understood correctly, you only need proprietary parts for the
kernel that runs *in* the card. The kernel running on your actual
system does not need proprietary parts, leaving you free to use a
different kernel.
yes, but as there is linux also
On Sat, Jun 30, 2007 at 01:29:23PM +0200, Clemens Kirchgatterer wrote:
Anssi Hannula [EMAIL PROTECTED] wrote:
If I understood correctly, you only need proprietary parts for the
kernel that runs *in* the card. The kernel running on your actual
system does not need proprietary parts,
AFAIK:
The TV-out connectors in the dvb-ttpci board output automatically NTSC
if the stream is NTSC. They output automatically PAL when the stream is
PAL.
When there is no stream (channel switch or the like), they output PAL by
default, or NTSC if the tv_standard kernel option is used to
I demand that Torgeir Veimo may or may not have written...
[snip]
When some parts of the kernel becomes gpl3, which it might,
That can't usefully happen so long as there are GPLv2-only components: there
would be no common licence for the whole kernel, which would make it
undistributable without
On Sat, Jun 30, 2007 at 01:05:18PM +0200, Stefan Lucke wrote:
Actually there's not much closed source that affects the usage. On the PC
side there's none, on the card side it's only the driver for the HDMI-chip
in the kernel
Damm, that's the nvidia way.
They decide on which kernel
This is exactly what I have observed as well. Is there any way VDR could
perform this V4L ioctl without the need for external applications such as
VLC and v4lctl?
I hope so because installing x to do this seems pretty unreasonable.
___
vdr mailing
Hi there!
The attached patch lets vdr-burn-0.1.0_pre21 use the correct charset that vdr
itself uses. This stops vdr-burn to double utf8 encode texts.
Matthias
--
Matthias Schwarzott (zzam)
Index: burn-0.1.0-pre21/burn.c
===
---
Hi,
This is a beta version of vdr which support dvb-s2.
So this version is able to watch TVHD through a streaming plugin
(streamdev plugin is include in archive).
http://www.freewebs.com/jlacvdr/vdr-s2hd/vdr-1.4.6-s2hd-070630.tar.bz2
The DVB-S2 channels must have 'M8' in modulation field of
On Wednesday, 16. Mayta 2007 10:50, Arthur Konovalov wrote:
I discovered that only primary language saved with recording.
For example if set primary language to eesti and secondary to suomi and
record YLE2 channel so result will be without subtitles.
Didn't work for me...
Even If I put both
On 30 Jun 2007, at 14:44, Georg Acher wrote:
As a small hardware manufacturer you have three possibilities:
1) Don't use a HDMI transmitter and ignore the market demand.
2) Use a HDMI transmitter, care about the NDA and deliver binary
modules for
controlling it.
3) Use a HDMI transmitter,
Georg Acher [EMAIL PROTECTED] wrote:
1) Don't use a HDMI transmitter and ignore the market demand.
the market never demanded an encrypted data stream on the HDMI cable,
and it is clearly the only reason they are picky about their secrets
within that driver. THEY want their chips be supported in
On Samstag, 30. Juni 2007, you wrote:
Hi,
Hi Ville!
Nice to hear there are actually users of the ebuilds ;)
AFAIK vdr 1.4.7 doesn't fix the error with subtitles not being
recorded (well, at least it's not in the changelog; OTOH I've
understod that the problem lies in the plugin, but then
I just upgraded to vdr 1.5.5 and now the colour buttons on the remote
doesn't work anymore when there's no OSD. If I press the menu button
first they work.
Is there a new setting that can have this effect?
--
Torgeir Veimo
[EMAIL PROTECTED]
___
19 matches
Mail list logo
