Hello.
I've tried to play the new ts recordings with vlc and it seems that
there is a typo in remux.c.
--- remux.c.orig2009-01-16 12:22:43.0 +0200
+++ remux.c 2009-01-16 12:23:39.0 +0200
@@ -320,7 +320,7 @@
uchar *cPatPmtGenerator::GetPmt(int Index)
{
if (Index
ke, 2009-05-13 kello 15:55 +0200, Theunis Potgieter kirjoitti:
Hi, is dvb-h a subset of dvb-t? our country decided to switch on
dvb-t, we receive dvb-t and dvb-h with h.264.
Any hints?
I wrote some instructions for receiving DVB-H:
http://users.utu.fi/mijutu/digitv/dvb-h/index-en.html
I
I have one Hauppauge WinTV-HVR4000 DVB-S/S2/T/Hybrid
[card=68,autodetected] at work.
Currently there is
- Debian 5.0.1 (lenny) with
- self compiled 2.6.29.2
- dvb drivers from hg, pulled around 11.5.
- vdr-1.7.7
- streamdev-server from vdr-developer.org CVS
With this setup I am finally able to
Hello.
VLC 1.0 doesn't even try to show subtitles from ts recordings, because
vdr sets subtitling type to zero in remux.c
If you want to watch dvb-subtitled ts recordings with vlc, try this
patch:
http://users.utu.fi/mijutu/digitv/vdr/vdr-1.7.8-subtitling_descriptor_for_vlc_1.0.diff.bz2
ma, 2010-08-02 kello 18:41 +0300, Antti Ajanki kirjoitti:
Only xineliboutput is supported at the moment, sorry.
How about transcoding or remultiplexing the downloaded videos to normal
vdr recordings?
Is there a way to run a command (like vdr's -r) after a video has been
downloaded?
Running an external commad after a download is finished sounds like a
good idea. I'll implement it in the next version.
Great, thanks. Those who have their tv still connected to FF-card tv
output will have to transcode sooner (with the external command) or
later (mplayer plugin, etc) anyway.
to, 2010-08-19 kello 08:57 -0700, VDR User kirjoitti:
Nouveau is that there are no plans to support VDPAU. That drivers
seems like a case of too little too late.
I've just tried to use a tnt2 card with the nvidia legacy drivers
because a couple of capacitors blew up on my newer card. It didn't
I got a dvb card, installed it in my vdr box and it didn't work. So I decided
to compile the driver, but alas, I had accidentially deleted the kernel
compile tree.
So it seems it's time to upgrade everyting: kernel, vdr, dxr3 driver and
dxr3plugin.
But what are the recommended versions at the
What is the latest kernel that dxr3 driver works on?
2.6.37 AFAIK
With which patches? Any url to pull from?
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
i am still working on it.
I have a feature reuqest for the vdr dlna server.
I bought a tv and fast forwarding through the dlna is terribly slow (tried
minidlna) and there are no skip one minute or goto hh:mm etc.
functionality at all.
Skipping minute forward, backward and goto hh:mm like vdr
In real life we all spread our things all over the house to keep
them in order.
Exactly. And the point of spreading files all over the directory
tree (not filesystem) is to be able to easily:
- split the tree into several filesystems that have different properties
such as size, speed,
Once version 2.0 is finished, I'm planning on dealing with the same channel
from multiple sources problem.
There is a related problem with the PCTV nanostick T2-usb receiver.
The nanostick T2 can receive C/T/T2 though the same antenna connector.
Change between C and T is done the normal way
Moving from VDR 1.6 to 2.06 for HD (DVB-T2) and seeing regular kernel oops w
ith the PCTV nanostick 290e when using DVB-T2.
The kernel is 3.0.76 (SLES 11 SP3)
There have been some fixes to the nanostick driver after 3.0. If you are
not sure that they have been backported to 3.0, try 3.3 or
+ streamdev and rpihddevice (which additional plugins ?)
The second way seems to be more complicated to configure, and I'm not
sure it suits my project, but the rpihddevice is well maintained though.
Could you tell me more please ?
I haven't tried the fbfe, but I borrowed a raspberry pi
torstaina 14. joulukuuta 2017 8.26.29 EET Harald Milz kirjoitti:
> I don't know how to handle this properly. My suggestion would be to ignore
> the channel pid change during an active recording on this channel, and
> defer the change until the recording is finished _if_ "-r something" is set
How
> Actually it should be possible to run several VDRs on the same machine
> without any exta efforts. All you need to do is use separate SVDRP ports
> via the --port option.
I was missing address of the machine from the other svdrphosts.conf. 127.0.0.1
there didn't help, because peering doesn't
I have two vdr instances running on the same machine, one for recording and
other for viewing. Then I wanted them to use the new vdr peer system to be
able to edit timers from the viewing side.
Running two vdr's didn't work because they both want to bind the 6419 port, so
I made a work-around
> - lirc_serial move out of staging (is no longer part of the kernel)
> and/or rename to serial_ir.
Here are my notes about those lirc changes from March 2019.
You still need to release the serial port from normal serial driver:
setserial /dev/ttyS0 uart none
Load serial_ir module, no need for
Martin Dummer kirjoitti maanantaina 14. marraskuuta 2022 12.16.56 EET:
> Am 14.11.22 um 10:55 schrieb Mikko Tuumanen:
> > Are there any vdr-related irc channels or matrix rooms?
> I know about #gentoo-vdr on libera.chat but it's a quiet place
I created a Matrix space: #vdr
Hello
Are there any vdr-related irc channels or matrix rooms?
Which hashtag we should use when mentioning VDR on Mastodon?
___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
20 matches
Mail list logo
