Hi all.
Running vdr 1.3.43, yes I should probably upgrade, but it's mostly
working...
Anyhow, the issue. Based in the UK, picking up DVB-t with reasonable
signal strength. Use vdradmin with a timer margin of 10 mins at the end.
Alas, sometimes timers get created that extend past the time a channel
goes off-air. VDR promptly video-data-stream-brokens repeatedly until the
timer ends, or is stopped/deleted manually.
Had a similar issue with timers for programs starting when the channel
goes on-…
[View More]air (Crystal Maze, f-tn), quickest fix was to reduce the
pre-padding from 2mins to 1 min. Can't really do that for the
post-padding; I've mostly seen programs ending late, not starting early...
The cause, seems to be that when certain channels go off-air, that PID
becomes disused, so no data arrives -> timeout.
The fix appears to be simple at least for this particular case. Providing
autopid is enabled. Get a message through syslog indicating the PIDs
have changed, followed by "stopping recording due to modification of
channel 15".
So, using the same technique as refusing to record with no disk space, the
attached patch refuses to record when all the PIDs are zero.
Shall have to wait for some channels to change state (might be able to use
ftn going off-air in about 4 hours) to verify how well this works, but
manually setting timers for off-air channels CBBC/Cbeebies/Five Life
behaves, when pre-patch a VDSB-restart would happen.
The logging could be better; it only logs for the first timer that
attempts to start/restart with no PIDs, and this will only resolve the
issue where the broadcaster transmits the PID updates, and autopid is
enabled. Should help in the cases Darren S and Dave P posted, uhm, a year
ago ("False \"video data stream broken\"", 15/Jun/2006). Shouldn't affect
VDSBs causes by bad signal/crashed firmware unless the PIDs changed to 0,
and stayed there as a result.
Attached are two files; one generated from 1.3.43, and one from 1.5.3
(some apparantly unrelated changes happened in menu.c). 1.5.3 appears to
behave the as 1.3.43 in this respect; VDSB 30 secs after setting a timer
on an off-air channel, but behaves with the patch.
Any feedback would be welcome...
If it helps prevent another ruined recording, that'd be even better...
--
Regards, Iain
W: http://www.triv.org.uk/~iain/
[View Less]
When demuxing my VDR recordings in ProjectX I get thousands of
apparently harmless warnings like this:
!> error in pes_extension of pes-ID 0xE0 @ pos: 101203597 (2048 / 19 / 20 / true / false)
!> error in pes_extension of pes-ID 0xC0 @ pos: 101229768 (592 / 16 / 37 / true / true)
I posted about a more serious problem at
<http://forum.dvbtechnics.info/showthread.php?t=3614> and someone
recognised these errors and thinks they're due to VDR's
subtitle/ttxtsubs patch. I'm not sure of …
[View More]the exact situation because the
full description of the problem is in German, but I gather that although
the subtitles are implemented in a plugin, VDR needs a patch to be able
to use it? Apparently it makes VDR write incorrect headers, at least as
far as ProjectX is concerned. Is this something that could be fixed in
VDR, or is it really ProjectX that needs fixing?
I'm not currently using subtitles, but I would probably find them useful
and might want to use the plugin. Besides, I'm using the Debian packages
and I don't want the inconvenience of recompiling without the patch.
--
TH * http://www.realh.co.uk
[View Less]
The function ExchangeChars() in VDR/recording.c converts characters
that can't be used in file names on Windows to "#XX", where XX is
the hex code of the character.
This was simple when VDR only worked with single byte character sets,
but now that it can handle UTF-8 this needs to be changed, too.
Currently it has a list of characters that can be used "as is",
and converts everything else to "#XX". I guess it is better
to convert any "disturbing" characters to "#XX" and leave the
rest …
[View More]untouched. However, this requires that we know exactly
which characters can't be used with Windows.
Does anybody have that kind of information?
Or should this be done completely different?
Note that I don't use this feature myself, so unless there
is some input from others, I won't be changing anything here.
Klaus
[View Less]
If a timer is triggered while the mplayer plugin is in use, VDR
crashes. This has happened to me about a zillion times now and I'm
hoping somebody will fix this! You can use the mplayer plugin after a
timer is started no problem. Correct me if I'm wrong but mplayer
should never have to take control of the tuner in the first place
since it's not required to play a media file.
Free booze to anyone who can fix this incredibly annoying problem once
and for all!!
Thanks. :)
Hi,
could somebody point me in right direction?
I am looking into configuring a second DVBS card to use with vdr.
Configuration:
Athlon 1.2GHz
MB: ABIT
Memory: 512MB
OS: Mandriva 2006
vdr: 1.4.5
DVBS1: Nexus-S
DVBS2: Twinhan 1025a
At this time I use Nexus-S and it works fine.
What modification/patches will require to make both cards work with vdr?
Is there any documentation for this case?
Greatly appreciated your help in advance,
Andrey
Hi,
i use vdr since a long time, i still use version 1.3.23 on 3 Computers.
The last months/years i did not follow the development. Is there already
a solution for the client-server Problem? I wonder if it is possible to
have 1 server recording and streaming to 2 client. And the clients
possible to start recordings on the server. Maybe the possibility to see
the osd of the server on the clients...
Klaus: Do you plan someting like this?
Thanks
Olli
Hi,
I've added vdr 1.5 to the buildservice now as well. Packages are
available for 10.0, 10.1 and 10.2 at
http://software.opensuse.org/download/vdr/
The package is called 'vdr15' and uses a different configuration
directory so it can be installed in addition to the 1.4 version.
The vdr-plugins package contains plugins both 1.4 as well as 1.5.
cu
Ludwig
--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.de/
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)
Hi,
Attached is a patch for vdr-1.5.3 and the timeline-1.0.141 plugin. Please
let me know if this patch is incorrect. Also, I am currently looking for
patches to fix epgsearch-0.9.22, tvonscreen-0.7.0, and liemikuutio.
Most of the time when VDR shuts the box down using vdrshutdown script
there is a line in the log
runvdr: VDR exited with status 134, attempting restart
I've got fedora with runvdr from fedora vdr package and it tries to
restart VDR if exit code is something else than 0, 2 or 137. Sometimes
the exit code is 137 but most of the time it is 134. This causes VDR to
restart (or runvdr makes VDR to restart) and dvb drivers to reload.
What does exit code 134 mean?
Why is exit code sometimes 137 …
[View More]and most of the times 134?
What should exit code be when VDR is shutting down either because the
user pushed power button or because there has been no user activity?
I've replaced fedoras VDR with my own vdr-1.4.6 compilation (due to some
plugins not in fedora packaging).
\\Kartsa
[View Less]
Hello everybody,
I live in Belgium, and would like to setup vdr with a budget DVB-T USB
Freecom Stick.
DVB-T is working well on my system with mplayer, xine, Kaffeine.
I have generated the required channels.conf for that, using scandvb
application.
But, with vdr (1.4.7), my channels.conf does not work.
I get this error:
$ ./runvdr
vdr: error while reading '/video/channels.conf'
When I use the original channels.conf given with vdr installation, I do not
get this error, but it does not …
[View More]correspond to my settings so it is useless.
The format of given channels.conf seems to be different from the one
generated by scandvb for DVB-T.
Here is an excerpt of both files:
Original VDR channels.conf
RTL Television,RTL;RTL World:12187:hC34:S19.2E
:27500:163:104=deu;106=deu:105:0:12003:1:1089:0
My channels.conf
LA
UNE:754000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:33:34:1
Could somebody help me on that issue?
Thx.
LOUIS
[View Less]