vdr

vdr@linuxtv.org

6731 discussions

multiplex to PES
by Patrick Cernko 17 Jun '07

17 Jun '07

Hi List, does anyone know how to multiplex some demuxed elementary streams (e.g. a video stream, an mpeg audio stream and an ac3 audio stream) into a proper vdr PES stream? I already tried mplex -f 8 but I'm not sure if the result is completely correct: It works (somehow, not sure if completely) but this is definitely not a PES stream. So long, -- Patrick Cernko | mailto:errror@errror.org | http://www.errror.org

2 2

[ANNOUNCE] VDR developer version 1.5.3
by Klaus Schmidinger 17 Jun '07

17 Jun '07

VDR developer version 1.5.3 is now available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.5.3.tar.bz2 A 'diff' against the previous developer version is available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.5.2-1.5.3.diff This version finally brings UTF-8 capability to VDR! There are still a few minor details to iron out, but all in all it already works pretty good. Note that if you run VDR on a UTF-8 system, it will write all its text files using UTF-8. Existing text files written in ISO will not be automatically converted to UTF-8. You will need to do this yourself if necessary. Channel and EPG data will be automatically changed to UTF-8 as new data comes in. If you run VDR on a system with ISO character set, files will still be stored in ISO just as before. Several bugfixes etc. that have been posted on the mailing list lately are still in my inbox and I have yet to look into them. WARNING: ======== This is a *developer* version. Even though *I* use it in my productive environment, I strongly recommend that you only use it under controlled conditions and for testing and debugging. The changes since version 1.5.2: - Fixed some spelling errors in 'newplugin' (thanks to Ville Skyttä). - Fixed a busy loop in fast forward if the next video data file is missing (thanks to Reinhard Nissl). - Fixed handling frequencies in NitFilter::Process() (thanks to Anssi Hannula). - Fixed a race condition with signal handlers at program exit (thanks to Udo Richter). - Non-primary devices in Transfer mode are now also used for recording (thanks to Anssi Hannula). - Fixed handling ChannelUp/Down keys if there is currently a replay running (thanks to Marco Schlüßler). - The new SVDRP command REMO can be used to turn VDR's remote control off and on in case other programs need to be controlled (based on patches from Krzysztof Parma and Helmut Auer). - Increased the maximum number of CA system ids to cope with the AlphaCrypt CAM's version 3.11 firmware. - Fixed getting the code setting from the locale (thanks to Matthias Schwarzott). - Implemented support for Freetype fonts (based on a patch from Alexander Riedel). The font names and sizes can be adjusted in the "Setup/OSD" menu. Note that VDR now requires freetype fonts to be installed in /usr/share/fonts/truetype. - If the OSD device in use has at least 8bpp bitmap depth and this is also used by the current skin, Freetype fonts are displayed "anti-aliased". The new setup parameter "OSD/Anti-alias" can be used to turn this off. - The new function cOsd::SetAntiAliasGranularity() can be used to help the OSD in managing the available color palette entries when doing anti-aliasing. Skins that use 8bpp bitmaps can call this function with the maximum number of colors used, and the maximum number of color combinations. The OSD will then evenly split the available palette entries between the various colors combinations, so that fonts can be "anti-aliased". By default a total of 10 colors and 10 combinations is assumed. - The pixel fonts have been completely removed from the VDR source. - VDR is now "UTF-8 aware". It handles strings according to the character encoding used on the user's system. All internationalization strings and incoming SI data are converted to the system encoding. - Plugins that handle strings need to be aware that on systems with UTF-8 encoding a "character symbol" may consist of more than a single byte in memory. The functions and macros named Utf8...() can be used to handle strings without needing to care about the underlying character encoding (see tools.h for details). - Even though the weekdays of repeating timers are presented to the user as UTF-8 characters in the OSD, the timers.conf file and the SVDRP timer commands still use single byte characters ("MTWTFSS") to make sure this information is handled correctly between systems with different character encodings. - Added a missing i18n string for "CAM" in the Turkish OSD texts. - Improved editing strings that are too long to fit into the editable area. - Changes to the OSD settings in the "Setup/OSD" menu now immediately take effect when the "Ok" key is pressed. Have fun! Klaus

8 39

anybody using the dxr3 plugin with vdr 1.5.3?
by Luca Olivetti 17 Jun '07

17 Jun '07

Hello, I wanted to try the development version of vdr (1.5.3) to see what's new and to keep my actuator plugin up to date. I think that the new vdr is doing funky things with the osd, since the menu is unwatchable (a lot of "dxr3: colormanager: bummer, too many sections (14), reusing last one"). OTOH the menu of my plugin displays just fine. I did not try any skin plugin yet, I loaded the bare minimum (dxr3, actuator and savechannel), so I just tested the 2 skins included in vdr (being the classic one the worst). Bye -- Luca

2 5

VDSB due to timer on off-air channel...
by iain＠bigserver.dnsalias.net 17 Jun '07

17 Jun '07

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-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/

1 0

Subtitles patch causing ProjectX warnings
by Tony Houghton 16 Jun '07

16 Jun '07

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 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

1 0

VDR 1.5.3: UTF-8 vs. ExchangeChars()
by Klaus Schmidinger 14 Jun '07

14 Jun '07

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 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

6 15

VDR timer + mplayer = VDR crash. Please fix!
by VDR User 13 Jun '07

13 Jun '07

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. :)

5 16

VDR with two DVBS cards
by Andrey Vlassov 13 Jun '07

13 Jun '07

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

3 3

vdr in client-server configuration?
by Oliver Joa 13 Jun '07

13 Jun '07

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

4 4

vdr 1.5.3 SUSE Linux rpm packages available
by Ludwig Nussel 12 Jun '07

12 Jun '07

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)

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr