Re: [vdr] What about vdr-1.6.1?

On 25.06.2009 21:55, Ville Skyttä wrote: >> Hmmm, this could also be a great opportunity: Why not nominate someone >> as the official maintainer of the 1.6 stable branch? Someone who >> collects or back-ports fixes and smaller enhancements to the 1.6 branch, >> and does minor releases based on comm

[vdr] [ANNOUNCE] runvdr extreme 0.4.2

Hi list, I've updated the runvdr extreme script to version 0.4.2 The script now handles the --instance switch and the VDR_CHARSET_OVERRIDE, can optionally unload DVB drivers on exit, supports shell functions DVBLOAD() { ... } alternatively to the classic DVBLOAD="...", and can do extra command

Re: [vdr] How do I listen to a channel's soundtrack and it's audio description at the same time?

On 02.09.2009 07:49, John Robinson wrote: I would very much like to hear the main programme's soundtrack and the audio description track at the same time, but at the moment, I can only hear one or the other - not both. Hmmm, interesting task. However, I don't think that this is possible curren

Re: [vdr] Plugin compiler arguments / Make.config

On 28.10.2009 09:01, Andreas Mair wrote: I wonder why no other plugin authors shared there opinion and how they fix it. As I understand it every plugin must be changed whenever VDR introduces changes in that area and if the VDR compiling user doesn't use (and adopt) Make.config. I guess this o

Re: [vdr] mdadm software raid5 arrays?

On 18.11.2009 18:28, H. Langos wrote: I/O-load can have some nasty effects. E.g. if your heads have to jump back and forth between an area from where you are reading and an area to which you are recording. I remember reading some tests about file system write strategies that showed major diffe

Re: [vdr] vdr shutdownskript - wrong time

Am 22.12.2009 23:59, schrieb Steffen Barszus: > Ian Bates schrieb: >> On 22 Dec 2009, at 21:36, Ian Bates wrote: >> If a timer is currently recording, or a recording would start within the >> next 30 minutes (default for the "Min. event timeout" setup >> parameter), and >> the user insists in shutt

Re: [vdr] vdr shutdownskript - wrong time

Am 10.01.2010 23:31, schrieb Steffen Barszus: > Am 10.01.2010 22:36, schrieb Udo Richter: >> 2. Timer less than 30min in the future >> - In that case, the critical question is whether VDR can complete a >> whole shutdown within that time. Worst case may be that VDR will never

Re: [vdr] implementing channel plug-in

Am 04.01.2010 18:26, schrieb Klaus Schmidinger: > There is an object of cChannel for each channel, and they are stored in > a list. You can either patch VDR to modify cChannel::Name() so that it > takes the original name as an index into some database of yours, or > modify the names in your channel

Re: [vdr] VDR crashes while recording a high bandwith channel

Am 11.01.2010 16:12, schrieb Manuel Reimer: > Depends on the source of the problem. If the problem is the tuner > part, then this part is not in a separate plugin, as VDR still > handles DVB cards without additional plugins. Most probably the bug > doesn't even have something to do with VDR. It see

Re: [vdr] Channel wrapping in live-tv

Am 11.01.2010 20:36, schrieb Ville Skyttä: > I haven't tested the patch, but it sounds useful to me. I wonder if it's > really necessary to make this configurable though - why not just go ahead and > do the wrap-around unconditionally? VDR has more than enough config options > already... Fina

[vdr] [ANNOUNCE] S2API wrapper + hard link cutter for VDR-1.7.11

Hi list, I've uploaded new versions of patches for the latest VDR versions: DVB/S2API wrapper patch, to run VDR-1.7 under DVB API V3: New versions of the patch for VDR-1.7.10 and VDR-1.7.11 http://www.udo-richter.de/vdr/patches.en.html#dvb-api-wrapper Hard Link Cutter patch, for fast editing o

Re: [vdr] [ANNOUNCE] S2API wrapper + hard link cutter for VDR-1.7.11

Am 18.01.2010 18:59, schrieb Christopher Reimer: >> Hard Link Cutter patch, for fast editing of recordings: >> New version for VDR-1.7.11 >> >> http://www.udo-richter.de/vdr/patches.en.html#hlcutter > > Why isn't this great patch integrated into VDR? Not everyone likes to have small file pieces,

Re: [vdr] How to seek/play splitted record files

Am 22.01.2010 19:01, schrieb Denis Loh: > I want to implement a record player for my UPnP plugin and was > wondering how the record files are played by the VDR. I found out > that cFileName und cUnbufferedFile may be my friends, but I don't > know how to seek a given file offset, if the recording i

Re: [vdr] [PATCH] Gather necessary options for build in Make.global and include it.

Am 28.01.2010 22:52, schrieb Ville Skyttä: > On Thursday 28 January 2010, Paul Menzel wrote: > >> Therefore include strictly necessary options in `Make.global` and include >> this in all the Makefiles before `Make.config`. > > If these options are strictly necessary, shouldn't the leading "-" be

Re: [vdr] VDR plugin options

Am 25.01.2010 00:19, schrieb Adrian C.: > Now I want a variable or array at the top of the script so I could > easily add, remove and comment plugins... rewriting the above example: > > vdrplug=(-Pfemon > -P"softdevice -vo xv:full -ao alsa:mixer:pcm=default" > ) > $vdrbin -L $vdrlib ${vdr

Re: [vdr] [PATCH] Gather necessary options for build in Make.global and include it.

Am 30.01.2010 12:12, schrieb Paul Menzel: > Sorry, I do not know if I understood you correctly. Do you mean that > some other plugins (which are not shipped with VDR, i. e. the patch does > not need to be changed in that regard) need to use `-include > $(VDRDIR)/Make.global` instead of `include $(V

Re: [vdr] VDR plugin options

Am 30.01.2010 19:23, schrieb VDR User: > On Sat, Jan 30, 2010 at 3:07 AM, Udo Richter wrote: >> The correct way to place every array element as one parameter, without >> doing any additional whitespace separation, is this: >> >> "$vdrbin" -L "$vdrlib"

[vdr] [ANNOUNCE] Bandwidth limiting patch for FF cards (VDR-1.6)

Hi list, One of the known problems of the FF-DVB cards is the bandwidth limitation, that is addressed by the full-ts-mod for example. However, there are still enough FF cards out there that are not and wont ever be modded, and these cards tend to produce broken recordings on high bandwidth channe

Re: [vdr] runvr extreme with different lirc device?

Am 14.02.2010 00:29, schrieb Torgeir Veimo: > What's the proper way to configure a different lirc socket path with > runvdr-extreme? Eg. I need to pass --lirc=/var/run/lirc/lircd to VDR, > as this is the new default lirc socket path with lirc 0.8.6. The following variants are the same: no --lirc

Re: [vdr] 10 Year Anniversary of VDR

Am 19.02.2010 17:09, schrieb Klaus Schmidinger: > It has been exactly 10 years since version 0.01 of VDR (originally > named "OSM" - On Screen Menu) was released. What an anniversary! 10 Years, and still alive! In case you're celebrating it this evening: Cheers from here! For me I'm still a bit

Re: [vdr] [ANNOUNCE] VDR developer version 1.7.13

Am 28.02.2010 16:07, schrieb Klaus Schmidinger: > - The file name in the "Timers" menu now shows only the base name of the > recording > without the folder path (if any). Otherwise with long folder paths the > actual > recording name was not visible at all. If I understand that correctly, th

Re: [vdr] SVDRP Port

Am 04.03.2010 13:00, schrieb Theunis Potgieter: > On 4 March 2010 13:44, Christian Tramnitz wrote: >> The current SVDRP Port 2001 is being used for several years now, but >> unfortunately it has never been registered with IANA. >> > that can't be fixed in a few minutes. Would this then imply that

Re: [vdr] Timer macros vs. filename in "Edit timers"

Am 07.03.2010 15:05, schrieb Klaus Schmidinger: > On 28.02.2010 20:59, Udo Richter wrote: >> If I understand that correctly, then many of my repeating recordings >> will soon be named "TITLE" or "EPISODE" only in the timer menu, because >> many of my ti

Re: [vdr] Feature request: program guide scroll

Am 12.03.2010 16:28, schrieb Klaus Schmidinger: > On 12.03.2010 08:33, István Füley wrote: >> I wonder if it's possible to implement a different behaviour for the >> left/right keys: to "scroll" between programs. Pressing right should >> bring up the next event, pressing left should bring up the pr

Re: [vdr] DVB (usb) device hotswapping?

Am 03.04.2010 21:17, schrieb Teemu Rantanen: > now that I've moved from pci dvb-c cards to usb dvb-c cards, I started > to think what happens if dvb-devices are inserted/ejected when vdr is > running. I haven't actually tried what happens, but it looks like > hotswapping isn't supported? VDR is f

Re: [vdr] DVB (usb) device hotswapping?

Am 04.04.2010 03:37, schrieb Georg Acher: > It is now solved by the mcli plugin by allocating all (16) devices at > startup. When the various Provides*-methods are called for tuning, the > plugin searches in its internal resource database for an appropriate tuner > and assigns it to the vdr-device.

Re: [vdr] TS Play Plugin - breaks streamdev and radio plugins

Am 14.04.2010 09:24, schrieb Frank Schmirler: > I attached a patch for streamdev, making it automatically detect the tsplay > patch. Can you give it a try? > -#if VDRVERSNUM >= 10703 > +#if VDRVERSNUM >= 10703 || defined(MAXVIDEOFILESIZETS) Hey, good idea to use this #define for detection! I di

[vdr] [ANNOUNCE] tsplay-0.2 patch for VDR-1.6.0-2

Hi list, The tsplay patch for VDR-1.6.0 is available in version 0.2. The new version is updated with some backport changes from VDR-1.7, and adds the missing patch presence detection. More important, there are patches for streamdev-cvs and xineliboutput-cvs that add compatibility to tsplay to the

[vdr] [ANNOUNCE] S2API wrapper + hard link cutter for VDR-1.7.13-15

Hi list, Once again, I'm a bit late with updating my patches. However, here are the new ones: DVB/S2API wrapper patch, to run VDR-1.7 under DVB API V3: New version of the patch for VDR-1.7.13 - VDR-1.7.15 http://www.udo-richter.de/vdr/patches.en.html#dvb-api-wrapper Hard Link Cutter patch, for

Re: [vdr] [ANNOUNCE] S2API wrapper + hard link cutter for VDR-1.7.13-15

Am 06.06.2010 22:17, schrieb Helmut Auer: >> DVB/S2API wrapper patch, to run VDR-1.7 under DVB API V3: >> New version of the patch for VDR-1.7.13 - VDR-1.7.15 > > Thanks for the patches ! > > Just one question: > What is the reason for the DVB/S2API wrapper patch ? > Why are you using the old DVB

Re: [vdr] [ANNOUNCE] S2API wrapper + hard link cutter for VDR-1.7.13-15

Am 06.06.2010 22:40, schrieb Udo Richter: > After the release of etch, and after all systems are up to date again, > I'll probably drop the patch finally. But until then, there's a good > chance for even more updates: I guess I'll need runtime switching > between DVBV3A

Re: [vdr] Dual DVB-S2 Tuner cards

Am 09.06.2010 08:16, schrieb István Füley: > TT promised a FF DVB-S2 card (TT-6400) with dual tuner for May 2010. > Does anybody knows if it arrived? Latest unofficial news[1] is that the design is now final, a first series for final testing and CE certification is ready, and production is ready f

Re: [vdr] Feature request: program guide scroll

Am 17.06.2010 17:31, schrieb martinez: >> Date: Sun, 13 Jun 2010 13:03:49 +0200 >> From: Klaus Schmidinger >> Subject: Re: [vdr] Feature request: program guide scroll >> >> Well, it has *no* priority to *me* ;-) >> So if you want this, you can suggest a patch. > > I would love to see this impleme

Re: [vdr] Feature request: program guide scroll

Am 17.06.2010 19:29, schrieb Udo Richter: > Am 17.06.2010 17:31, schrieb martinez: >> Can any kind person write this patch? > > I'll see if I can come up with something on the weekend. As always, the more close you look on it, the more complicated it gets. In other words,

Re: [vdr] Feature request: program guide scroll

Am 20.06.2010 00:54, schrieb Torgeir Veimo: > On 20 June 2010 01:37, Udo Richter wrote: >> Am 17.06.2010 19:29, schrieb Udo Richter: >>> Am 17.06.2010 17:31, schrieb martinez: >>>> Can any kind person write this patch? >>> >>> I'll see if I

Re: [vdr] multiple patching trouble

Am 21.06.2010 09:28, schrieb martinez: > I've taken vanilla vdr 1.7.15 and applied the extensions patch V3 (see link > following) > [...] > and finally I try your patch (with --dry-run ) > > patch -p1 --dry-run < ../patches/event_1.7.15_patch > [...] > 2 out of 9 hunks FAILED -- saving rejects t

[vdr] [ANNOUNCE] S2API wrapper patch 0.6

... or why two legs are better than one. Hi list. Due to some unexpected S2 capable hardware, there's a new version of my S2API wrapper patch available for download. The new version adds S2API auto-detection at runtime, so that one binary vdr executable can handle old DVB V3 drivers and DVB V5

Re: [vdr] Shutdown deactivated

Am 30.06.2010 12:06, schrieb Dominic Evans: > For an always-on VDR, if shutdown is deactivated in the config, why do > we still call vdr-shutdown-message and output OSD messages about > 'shutting down in x seconds etc.' when VDR will actually never shutdown. In core VDR, the shutdown countdown is

Re: [vdr] How to properly attach stream to live view?

Hi list, hi Klaus, In continuation of this old topic [1] and the bug ticket [2]: I've written a patch that changes handling of receivers in VDR. The patch makes sure that receivers of priority of -1 won't block a device, without re-introducing the Live TV Freeze [3] bug. Details of this issue ar

Re: [vdr] How to properly attach stream to live view?

Am 19.07.2010 10:44, schrieb Frank Schmirler: > Good shot. Streamdev suffers from a similar problem and would benefit from > this patch, too. If a streamdev-client prepars to switch channels, the current > stream blocks a device which will also become available a little later. At the > moment strea

Re: [vdr] test-infrastructure

Am 02.08.2010 13:50, schrieb Rainer Blickle: > How do you (everyone subscribed to this list) test your developed code ? Dogfood testing, mainly. After some manual testing, most stuff quickly moves on to the production system, and if it survives there for some days, its ready to release. After rele

Re: [vdr] Primary Device

Am 13.08.2010 00:32, schrieb Rainer Blickle: > i have a question: What is the primary device. > > I have the following devices: > - xineliboutput or PVR350 > - pvrinput-device > > None of the devices can do both, receive and showing a stream . > > Which of the devices is the primary device. How

Re: [vdr] Automatic shutdown / restart of VDR

Am 24.08.2010 12:10, schrieb Lari Tuononen: > I've managed to get the waking-up working properly, and also so that > VDR will shutdown at night after the last timer has stopped, but if > there is a timer in the morning and it wakes computer up, VDR also > shuts down the computer, which is something

Re: [vdr] Impact in cDevice::GetDevice

Am 24.08.2010 07:57, schrieb Rainer Blickle: > in the method cDevice::GetDevice the device with the least impact is > searched (the block with "imp <<= x; imp |= "). For calculating the > impact (higher value = bigger impact) some "facts" are used. The most > prio fact is "prefer the primary devic

Re: [vdr] vdr-filemanager plugin not compiling

Am 11.09.2010 10:07, schrieb marti...@embl.de: > Hi, > > I am trying to compile on vdr 1.7.15 the filebrowser-0.2.0 plugin > > menu-filebrowser.c:205:70: error: invalid conversion from ‘const char*’ to > ‘char*’ You're using a newer GCC version that is more strict regarding implicit conversions

Re: [vdr] vdr-filebrowser plugin not compiling

Am 14.09.2010 12:20, schrieb Arturo Martinez: > It looks like the author is no longer maintaining the plugin. > > Which leads me to a question... > Has anybody thought of keeping a repository of plugins that the author > himself no longer seems to maintain and try to keep a patched version > avail

Re: [vdr] cDvbDevice::Initialize

Am 25.09.2010 16:38, schrieb syrius...@no-log.org: > I'm having a setup with 4 dvb cards, and I'm running 3 vdr instances. > I'm using an udev rules to make sure adapter numbers don't change. > I'm using the -D option the assign cards to vdr instances. > > I've just discovered that vdr -D 3 would

Re: [vdr] Feature-Request: MarginStart in INFO file of recording

Am 02.11.2010 12:20, schrieb Rene Bartsch: > So I suggest to add start margin (and maybe stop margin) to the info files > of recordings. There is no fixed start/stop margin. I have some timers with 5min before / 10min after, and others with 10min before and 30min after. Depends on how much delays

Re: [vdr] Feature-Request: MarginStart in INFO file of recording

Am 03.11.2010 02:24, schrieb Rene Bartsch: >> There is no fixed start/stop margin. I have some timers with 5min before >> / 10min after, and others with 10min before and 30min after. Depends on >> how much delays the channel usually has. > > I'm talking about the MARGINSTART in setup.conf or a man

Re: [vdr] xine-lib and vaapi support

Am 03.11.2010 10:06, schrieb Theunis Potgieter: > I'm considering to upgrade my current p3 system to a hdmi/optical > SPDIF and enough expansion slots to fill in dvb-s devices. > The unkown factor for me is, should I > consider a motherboard where the Core i3 (System on Chip) has got a > built in

Re: [vdr] Recordings Numbering

Am 09.11.2010 16:35, schrieb Matthias Wächter: > You just re-introduce the old problem. Don't ever re-number. If you > don't renumber any SVDRP client can be safe in assuming for (nearly) any > time span to mean the same recording as the server when it updates a > recording's schedule. In other wo

Re: [vdr] VDR 1.7.16 - emergency exit on recording HD shows

Am 14.11.2010 12:07, schrieb Luboš Doležel: > Aside from that I don't understand why it terminates completely if it > _thinks_ some bad data arrived. Data errors may happen at any time and > it's not a valid reason for an emergency exit. To clarify this: The emergency exit is triggered if and only

Re: [vdr] VDR 1.7.16 - emergency exit on recording HD shows

Am 14.11.2010 18:21, schrieb Eric Valette: > I think I said clearly that the code looks correct and gave the pointer > to the specs for unconvinced people. Those wanting to read the full specs > Page 72, Table 6-12, picture_coding_type: 000 forbidd

Re: [vdr] VDR 1.7.16 - emergency exit on recording HD shows

Am 14.11.2010 19:17, schrieb Eric Valette: > On 14/11/2010 19:05, Udo Richter wrote: >> The patch changes the behavior of VDR to accept picture_coding_type=0 >> and picture_coding_type=1 as I-Frame. picture_coding_type=0 is clearly >> specified as forbidden. Anything I'v

Re: [vdr] dvbsddevice-Plugin: Problems with A/V Sync

Am 24.11.2010 19:50, schrieb Christopher Reimer: > I am using vdr version 1.7.16 and I have discovered some A/V Sync > problems after jumping to another mark or jumping with the yellow/green > button. > > Is that an already-known-problem? Am 28.11.2010 18:37, schrieb Christopher Reimer: > Anyone

Re: [vdr] [PATCH] Improved pause handling

Am 01.12.2010 16:44, schrieb Matti Lehtimäki: > Sometimes when you want to pause live video you are already recording > the current channel. In such case it is not practical to start a new > instant recording but it would be more practical to start replaying the > recording already being made[...]

Re: [vdr] Request: E parameter in channels.conf for epg scan

Am 06.12.2010 13:38, schrieb Mario Schulz: > My previous platform had selectable EPG scans. > When I first got into touch with VDR, I asked myself, how I was supposed > to restrict searchtimers to interesting channels. So you want to cut off EPG data for these channels just because epgsearch shoul

Re: [vdr] dvbsddevice-Plugin: Problems with A/V Sync

Am 13.12.2010 13:56, schrieb Christopher Reimer: > OK, I think I know the reason of my A/V-Problems The Harddrive is > too slow. (Activy 300 => UDMA 66) Sure? For years now, I've been running slow spinning disks on an VIA EPIA board that theoretically delivers UDMA133, but never actually reac

Re: [vdr] Request: E parameter in channels.conf for epg scan

Am 13.12.2010 11:34, schrieb Steffen Barszus: > That was my point in the beginning. Then: I want to see sqlite3 being > less efficient on insert and fetch or memory consumption. I can not > imagine it (prove me wrong! ;)). Correct me if I'm wrong, but for sqlite you'll have to convert all these n

Re: [vdr] Request: E parameter in channels.conf for epg scan

Am 14.12.2010 20:20, schrieb Steffen Barszus: > 1.) Klaus doesnt like it, also does not like to make it possible to do > it in a plugin. Actually, no one stops you from doing lots of things from within a plugin. The EPG system of VDR has even a multithread safe interface, so you could constantly s

Re: [vdr] Request: E parameter in channels.conf for epg scan

Am 14.12.2010 21:20, schrieb Luca Olivetti: > Right now I have a recording going on. If I press the "up" channel past > the last channel on the same transponder, vdr is unresponsive for ~30 > seconds. > I guess that sqlite, with a well formulated query and the right indexes, > would take a fraction

Re: [vdr] Request: E parameter in channels.conf for epg scan

Am 14.12.2010 21:56, schrieb Luca Olivetti: > Instead of speculating I actually tried. > I created a test database with the contents of my channels.conf (only > containing the number, name, frequency, source, symbol rate and the > vpid, I don't think adding all the fields would change the result >

Re: [vdr] Request: E parameter in channels.conf for epg scan

Am 17.12.2010 22:58, schrieb Pasi Juppo: > That said and with no disrespect to the author of vdr in my opinion it > starts to be a time to fork vdr and redefine its base + few other > elements. > > Of course things can remain the same but will we ever see natively > implemented in vdr: > -_proper_

Re: [vdr] Cutting TS recordings outside of VDR

On 18.12.2010 21:21, Tobias Grimm wrote: Before reinventing the wheel - is there any tool that can cut VDR's TS recordings outside of VDR? (Something like hlcut for VDR 1.6 recordings). like, for example, "vdr --edit=/path/to/recording"? Yes, there is. ;) (see HISTORY for 1.7.11) Cheers, Ud

Re: [vdr] Cutting TS recordings outside of VDR

Am 19.12.2010 20:29, schrieb Tobias Grimm: > Am Sonntag, den 19.12.2010, 20:01 +0100 schrieb Helmut Auer: > >> Why don't you just use a wrapper script to get this running, like > > I've already tried this (not in bash, but a similar approach). But I > would like to avoid writing to the source di

Re: [vdr] projects.vdr-developer.org

Am 26.12.2010 15:04, schrieb Tobias Grimm: > Unfortunately projects.vdr-developer.org is currently down. > > It's seems like a stupid Hacker/DOS attack causing to fill up the memory > until the systems becomes non-responsive. There was no security leak, so > all data is safe. Seems like all the 1

[vdr] [ANNOUNCE] naludump 0.0.1

Hi list, This is the test version 0.0.1 of my h.264 nalu fill data removal tool. The tool deletes NALU fill data from h.264 streams embedded into TS files, like VDR recordings. The overall file structure isn't modified, only complete TS packets of NALU fill data are removed. On HD TV channels th

Re: [vdr] VDR creates 2GB files when using --edit (vdr 1.7.16)

Am 03.01.2011 23:34, schrieb Marco Göbenich: > tried to cut a one file recording per commandline with vdr 1.7.16, but > it always creates multiple files splitted after 2GB, used also "-c > /etc/vdr" so that vdr knows where to find setup.conf, but it doesen't > matter. That's because the editing p

Re: [vdr] Problem with osdteletext plugin 0.9.0

Am 06.01.2011 15:15, schrieb Michal: > I'm successfully using osdteletext-0.8.2.cz from > http://www.cssf.cz/showthread.php?35867-vdr-1.7.10-a-eHD with attached > patch. This issue is tracked at vdr-developer.org bug tracking: http://projects.vdr-developer.org/issues/469 Cheers, Udo ___

Re: [vdr] new OSD system

Am 16.01.2011 05:35, schrieb Gero: > I read about the ongoing work at the OSD system. > I have to confess, that I don't really miss a truecolor OSD, but what I miss > is the possibility to configure the OSD for each output-device separately. > > Currently I use a "backend"-vdr with budget-cards a

Re: [vdr] [ANNOUNCE] naludump 0.0.1

Am 21.01.2011 12:40, schrieb Matthias Wächter: > On 01.01.2011 22:29, Udo Richter wrote: >> Later versions will also integrate into VDR as a patch, and will filter >> out these fillers while recording. > > Is there any progress on this topic? For me that’s the most useful us

Re: [vdr] [ANNOUNCE] naludump 0.0.1

Am 22.01.2011 14:18, schrieb Rolf Ahrenberg: > On Fri, 21 Jan 2011, Udo Richter wrote: >> I had some issues integrating it properly into the recording function of >> VDR, and then ran out of time. But I think I'll find some time this >> weekend. > > Howabout jus

Re: [vdr] [ANNOUNCE] naludump 0.0.1

Am 22.01.2011 20:21, schrieb Rolf Ahrenberg: >> And I wouldn't consider it good style to provide just filtered >> streams for all in any case. > > Wouldn't stripping NALU fill data help to reduce the required network > bandwidth for streamdev, xineliboutput, and vnsi plugins? I do see many > benef

Re: [vdr] vdr crash on delete

Am 25.01.2011 16:38, schrieb JJussi: > Is this bug or feature. *(VDR 1.7.15)* > You select Menu - Recordings - (select one record) - press "Delete"-button. > 1. System asks, do you want to delete recording > 2. you don't press enter, just let that query be on the OSD > 3. after 60 seconds, vdr-thr

Re: [vdr] Detecting recording errors

Am 10.02.2011 01:59, schrieb Tobias Grimm: > Am Montag, den 10.01.2011, 20:19 +0100 schrieb Tobias Grimm: >> It shouldn't be too hard to scan a *.ts-File for discontinuity errors, >> but I would like to make VDR detect this while recording and somehow set >> a flag, so I can see if a recording migh

Re: [vdr] VDR 1.7.16 FF card crashes

Am 09.02.2011 21:13, schrieb - -: > I upgraded my VDr system from 1.6.0 to 1.7.16. After upgrade, I found > that my FF card (fujitsu-siemens dvb-c) crashes almost every time > when I exit from a recording playback. Using 1.7.16 on an unmodified FF DVB-S regularly, no special issues. Rock solid as

Re: [vdr] [ANNOUNCE] naludump 0.0.1

Am 01.01.2011 22:29, schrieb Udo Richter: > Later versions will also integrate into VDR as a patch, and will filter > out these fillers while recording. I've released an quick & early naludump patch for vdr-1.7.16, you can get it at VDR portal: http://www.vdr-portal.de/board/th

Re: [vdr] VDR 1.7.16 FF card crashes

Am 14.02.2011 01:33, schrieb syrius...@no-log.org: > Udo Richter writes: >> Using 1.7.16 on an unmodified FF DVB-S regularly, no special issues. >> Rock solid as usual, as long as you don't do transfer mode on high >> bandwidth channels. > > Are you still using

[vdr] [ANNOUNCE] naludump patch 0.1

Hi list, I've uploaded the final patch version of the h.264 NALU fill removal for VDR 1.7.16. The patch deletes NALU fill data from h.264 streams while recording. The overall stream structure isn't modified, only complete TS packets of NALU fill data are dropped. On HD TV channels that use fixed

Re: [vdr] How's the 24 bit OSD VDR coming?

Am 08.03.2011 22:09, schrieb Klaus Schmidinger: > Don't get too excited about the TrueColor OSD, though. > What comes with VDR is only the basic OSD platform that > allows plugins to use full screen 32 bit ARGB color, > with alpha blendable pixmaps and such. Do you have any numbers on OSD speed fo

Re: [vdr] priorities in streamdev

Am 13.03.2011 15:18, schrieb Klaus Schmidinger: > On 27.07.2010 15:15, Frank Schmirler wrote: >> On Tue, 27 Jul 2010 15:07:23 +0200, syrius.ml wrote >>> Have you had a look at >>> http://projects.vdr-developer.org/issues/show/10 ? >> >> Yep: http://www.linuxtv.org/pipermail/vdr/2010-July/023243.htm

Re: [vdr] priorities in streamdev

Am 13.03.2011 15:42, schrieb Klaus Schmidinger: > On 13.03.2011 15:36, Udo Richter wrote: >> That would be me, actually. This was on the list last July: >> http://www.linuxtv.org/pipermail/vdr/2010-July/023240.html >> >> Contact me if you have any questions. > > C

Re: [vdr] [ANNOUNCE] VDR developer version 1.7.17

Am 19.03.2011 18:40, schrieb Juergen Lock: > There is one remaining bug tho: After playback of a short recording > (sd in this case, 20s or so), vdr seems to kind of hang and I have > to kill it... Can you reproduce that? Longer recordings are not > affected. This is probably an old bug: For m

[vdr] [1.7.17][Patch] Program guide scroll

Hi list, In reference to [1], and to give this a push-up, I've attached an updated patch for program guide scroll for VDR-1.7.17. The patch also fixes the non-working scrolling in longer descriptions. If anyone needs this fixed for VDR < 1.7.17, let me know. Cheers, Udo [1] http://www.linuxtv.

Re: [vdr] [ANNOUNCE] VDR developer version 1.7.17

Am 13.03.2011 12:46, schrieb Klaus Schmidinger: > - While replaying, the editing marks are now updated every 10 seconds (based > on a > patch from Manuel Reimer). Thanks for this! With it, the jumpplay-patch gets obsoleted for me, as I only used the marks reloading. (As a good-bye, I've posted

Re: [vdr] [ANNOUNCE] VDR developer version 1.7.17

Am 20.03.2011 13:31, schrieb Klaus Schmidinger: > On 20.03.2011 12:46, Klaus Schmidinger wrote: >> I have attached a patch that implements this. >> Would this be ok? > > Sorry, there was a line missing that makes sure the initial load > takes place. Attached is a revised version of the patch. You

Re: [vdr] [ANNOUNCE] naludump patch 0.1

Am 22.03.2011 09:16, schrieb Matthias Fechner: > On 20.02.11 21:31, Udo Richter wrote: >> I've uploaded the final patch version of the h.264 NALU fill removal for >> VDR 1.7.16. > > which config parameter I must set in the setup.conf to enable this > patch? (I have no

Re: [vdr] [ANNOUNCE] naludump patch 0.1

Am 23.03.2011 07:58, schrieb Matthias Fechner: > One question here, if I shrink already existing recordings with the > command line tool, is it necessary to delete the index? The command line tool just processes a single .ts file. You have to process each file of the recording, and you have to reg

Re: [vdr] [Patch] Make RGYB buttons customizeable

Am 02.04.2011 12:23, schrieb Klaus Schmidinger: > I could imagine accepting a patch that centralizes handling > the sequence in which the color buttons are displayed, and > offers a standard interface to skin plugins that allows > them to arrange the color buttons accordingly. > > What I don't wan

Re: [vdr] [ANNOUNCE] VDR developer version 1.7.17

Am 27.03.2011 16:45, schrieb Klaus Schmidinger: > Can you please rewrite your patch so that it keeps the original 'd' > variable? I liked the fact that the 'nextUpdate' variable was incremented > in *one* place, and not in several places. Made the whole thing more > transparent to me. Besides, I co

Re: [vdr] *** GMX Spamverdacht *** Re: Can VDR use one specific transponder for EPG information?

Am 18.04.2011 00:15, schrieb VDR User: > On Sun, Apr 17, 2011 at 1:31 PM, Timothy D. Lenz wrote: >> Just a thought but you could set up a daily or weekly timer with a very low >> priority on the recording so it auto deletes it. I've never used the auto >> delete after set time because I never know

Re: [vdr] TT Premium S2-6400 (F?ley Istv?n)

Am 20.04.2011 10:54, schrieb serge pecher: > I was a little bit surprised to see in the specifications that it needs a CPU > minimum P4 2 Ghz. Thats probably because you need at least an 2GHz P4 to boot windows and a virus scanner nowadays. The CPU and RAM demands should be not much higher than w

Re: [vdr] TT Premium S2-6400 (F?ley Istv?n)

Am 20.04.2011 23:33, schrieb VDR User: > On Wed, Apr 20, 2011 at 10:34 AM, Udo Richter wrote: >> Thats probably because you need at least an 2GHz P4 to boot windows and >> a virus scanner nowadays. > > I seriously doubt virus scanners have anything to do with anything. >

Re: [vdr] [OT] Windows resource needs, WAS: TT Premium S2-6400 (F?ley Istv?n)

Am 21.04.2011 21:01, schrieb VDR User: > I can't believe a dvb card vendor sets their minimum requirements > based on things such as McAfee loads. It would be absurd to do so. Probably not that specific, but they have to calculate an average OS with average software running on it, and for a Windo

Re: [vdr] [Patch] Cannot delete last char in insert mode

Klaus Schmidinger wrote: deletes the character *after* the cursor. If this was the last character, then there's nothing more to delete. Just try this in any string entry field, for instance the "Subject" line of your email client. These are usually always in insert mode. If you press "Del" severa

Re: [vdr] [vdr bug]Shutdown during an active timer is broken

Klaus Schmidinger wrote: Please try the attached patch. Did some simple tests, seems ok so far. One thing remains: After "Recording - shut down anyway?", we should not ask "Recording in x minutes, shut down anyway?", as the 'next' recording is always the currently running one, and x is a neg

Re: [vdr] 2GB limit overcome?

JikJikMan wrote: How should I prevent vdr to split files in 2 GB files? VDR is limited to 2Gb by design and cannot process bigger files. Allowing large files would require major rewrites to VDR and even incompatible changes to the index.vdr format. If you really want your recording in one l

[vdr] Bug? Missing next timer event

Hi list, I just noticed a serious issue with a missed timer event. After a daily timer, VDR did an automatic shutdown, but not for the next day to record the same timer again, but for the next following timer event! I never noticed this before, so my guess is that this issue is somehow quit

Re: [vdr] Bug? Missing next timer event

Udo Richter wrote: I just noticed a serious issue with a missed timer event. After a daily timer, VDR did an automatic shutdown, but not for the next day to record the same timer again, but for the next following timer event! Ok, I was able to verify and debug this a bit. Using the attached

Re: [vdr] Error while Recording and loose signal

Herbert Poetzl wrote: for some reason channel A fails because of a thunderstorm or a covered lnc (think bird) or one of several DVB cards have a problem with the reception (cable unplugged, wrong diseqc commands issued or whatever), which leads to a vdr which is restarting every 10-15 seconds,

<    1   2   3   4   5   6   >