Re: [vdr] French DVB-T Channel IDs vs. EIT Channel IDs

On Fri, 9 Mar 2018 11:55:02 +0100 Klaus Schmidinger <klaus.schmidin...@tvdr.de> wrote: > On 09.03.2018 11:51, Patrick Boettcher wrote: > > On Fri, 9 Mar 2018 11:30:36 +0100 > > Klaus Schmidinger <klaus.schmidin...@tvdr.de> wrote: > > > >> On

Re: [vdr] French DVB-T Channel IDs vs. EIT Channel IDs

On Fri, 9 Mar 2018 11:30:36 +0100 Klaus Schmidinger <klaus.schmidin...@tvdr.de> wrote: > On 01.03.2018 10:22, Patrick Boettcher wrote: > > On Wed, 28 Feb 2018 11:01:23 +0100 > > Klaus Schmidinger <klaus.schmidin...@tvdr.de> wrote: > > > >> On

Re: [vdr] French DVB-T Channel IDs vs. EIT Channel IDs

On Thu, 1 Mar 2018 10:22:10 +0100 Patrick Boettcher <patrick.boettc...@posteo.de> wrote: > On Wed, 28 Feb 2018 11:01:23 +0100 > Klaus Schmidinger <klaus.schmidin...@tvdr.de> wrote: > > > On 27.02.2018 17:58, Patrick Boettcher wrote: > > > On Tue, 27

Re: [vdr] French DVB-T Channel IDs vs. EIT Channel IDs

On Thu, 1 Mar 2018 10:22:10 +0100 Patrick Boettcher <patrick.boettc...@posteo.de> wrote: > On Wed, 28 Feb 2018 11:01:23 +0100 > Klaus Schmidinger <klaus.schmidin...@tvdr.de> wrote: > > > On 27.02.2018 17:58, Patrick Boettcher wrote: > > > On Tue, 27

Re: [vdr] French DVB-T Channel IDs vs. EIT Channel IDs

On Wed, 28 Feb 2018 11:01:23 +0100 Klaus Schmidinger <klaus.schmidin...@tvdr.de> wrote: > On 27.02.2018 17:58, Patrick Boettcher wrote: > > On Tue, 27 Feb 2018 16:54:35 +0100 > > Klaus Schmidinger <klaus.schmidin...@tvdr.de> wrote: > > > >> Hello Pat

Re: [vdr] French DVB-T Channel IDs vs. EIT Channel IDs

On Tue, 27 Feb 2018 16:54:35 +0100 Klaus Schmidinger wrote: > Hello Patrick, > > your scan doesn't contain the NIT, which is where the transponder > innformation is broadcast. Can you scan that, too, please? Hi Klaus, NIT attached (from another multiplex with the

Re: [vdr] French DVB-T Channel IDs vs. EIT Channel IDs

Hi Klaus, thank you for your reply. On Mon, 26 Feb 2018 16:58:20 +0100 Klaus Schmidinger wrote: > > How should this be fixed correctly? > > > > Is this a regression introduced somewhere? > > > > Can it be solved by configuration? > > where did the channel with ID

[vdr] French DVB-T Channel IDs vs. EIT Channel IDs

Hi list, since some time (1-2 years) I noticed that the DVB-T channels do not show EPG anymore. I'm not sure what is the root-cause: either it was the migration of French DVB-T to HD (in 2016) or an update of VDR. Anyway, this morning I took the time to figure out what is wrong and here is what

Re: [vdr] broken recordings

On Mon, 8 Aug 2016 22:51:13 +0200 Patrick Boettcher <patrick.boettc...@posteo.de> wrote: > Hi, > > On Mon, 8 Aug 2016 20:30:33 +0200 > Matthias Bodenbinder <matth...@bodenbinder.de> wrote: > > > Hello Christoph, > > > > based on your feedbac

Re: [vdr] broken recordings

Hi, On Mon, 8 Aug 2016 20:30:33 +0200 Matthias Bodenbinder wrote: > Hello Christoph, > > based on your feedback I made another test. The USB HD performance > seems to be ok (see my other reply). But anyways I made a test with > recording directly to the Flash SD card.

Re: [vdr] Sat>IP-plugin: how to configure 2 DD Octopus NETs with different satellites

On Tue, 19 Jul 2016 02:37:42 +0200 "fnu" wrote: > Hi, > > I remember that Rolf always does suggest to use "OctopusNet" or > "minisatip" as device name. Yep, that's for the quirks, I think. I simply copied the string as I found them in the README. > The other

Re: [vdr] Sat>IP-plugin: how to configure 2 DD Octopus NETs with different satellites

one_ Octopus NET. Like '[..]Octo2|S28.2E,S19.2E,S28.2E,S19.2E' wouldn't work without changing the URL-creation-method. It even looked like that the URL is created before the satipFrontend is chosen. That would have to be changed. best regards, -- Patrick Boettcher

[vdr] SatIP>plugin: how to configure 2 DD Octopus NETs with different satellites

Hi, I have 2 DD Octopus NET devices. One is a 2x DVB-S(2) + 2x DVB-T(2) (let's call it AA) and the other one is 4x DVB-S(2) (BB). AA's satellite orientation is Astra 28.2, BB's one is Astra 19.2. How can I associate AA's or BB's inputs in VDR's configuration so that it uses 1) the right

Re: [vdr] VDR deleting non-.del-dirs in video-path

On Wed, 17 Feb 2016 08:29:10 +0100 Reiner Bühl wrote: > The easiest way to fix this would be to separate backup and video > dir. Why don't you create two directories on your USB HDD and link > them into different locations? E.g. Mount the HDD as /mnt/usbdisk and > then create a

[vdr] VDR deleting non-.del-dirs in video-path

Hi list, I'm using a Raspi2 for vdr and attached a HDD over USB for storage. I'm also backuping the rootfs (SD-card) onto the HDD on a regular basis. Checking the logs for another problem it turns out the it enters my backup-dir and tries to delete empty-directories. I read in the ML-archive

Re: [vdr] VDR + SatIP + Octopus Net - no more data on SD channels

On Sun, 3 Jan 2016 22:29:20 +0100 Patrick Boettcher <patrick.boettc...@posteo.de> wrote: > Everything works fine. Except that after some time streaming on > SD-channels seems to stop. Zapping to a HD-channels works. > > When trying to receive a non-working SD-stream I can se

[vdr] VDR + SatIP + Octopus Net - no more data on SD channels

Hi list, I'm facing a problem with the following configuration: - VDR on a Raspi2 (raspian with packages from e-tobi) - Digital Devices' Octopus Net with 2 DVB-S2 receivers I'm using vdr-plugin-satip with the following arguments: -s |DVBS2-2|Octo -d 2 Everything works fine. Except that after

Re: [vdr] xineliboutput and streamdev at the same time

On Mon, 20 Apr 2015 16:05:45 +0300 Marko Mäkelä marko.mak...@iki.fi wrote: On Mon, Apr 20, 2015 at 11:40:41AM +0200, Patrick Boettcher wrote: vdr-fbfe is connecting over network to a vdr running on a full machine. No need for streamdev. This looks interesting. Am I right assuming

Re: [vdr] xineliboutput and streamdev at the same time

On Mon, 20 Apr 2015 11:33:02 +0200 Torgeir Veimo torgeir.ve...@gmail.com wrote: Have you tried rpihddevice plugin with VDR on the rpi? It might work even smoother than using xinelinboutput, but you'd have to find a different setup for cec i suppose.

Re: [vdr] from xineliboutput to ... perhaps softhdddevice?

Hi all, On Fri, 17 Apr 2015 09:25:22 +0300 Füley István airo...@tigercomp.ro wrote: I know, it's not a proper answer for your problem, but I think at the moment the best native vdr client is a Raspberry Pi with Thomas Reufer's great plugin. It's small, cheap and (using with vdr) it's fast.

Re: [vdr] xinelib / vdpau suddenly fails to detect Nvidia ION GPU

Hi, On Thursday 26 December 2013 19:13:05 Harald Milz wrote: Any idea where I should look? Why might xinelib or vdr-sxfe fail to correctly detect the ION (MCP79) chip when everything is unchanged? Yes I ran an apt-get upgrade on the underlying Ubuntu 12.04.3 OS but this didn't change

Re: [vdr] Bug in pat.c (VDR 1.7.27) - possible fix attached

On Monday 09 April 2012 13:39:36 Dominic Evans wrote: On 9 April 2012 10:40, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: + // http://www.smpte-ra.org/mpegreg/mpegreg.html + ... + case 0x44434949: //

Re: [vdr] Bug in pat.c (VDR 1.7.27) - possible fix attached

On Monday 09 April 2012 17:57:20 Klaus Schmidinger wrote: On 09.04.2012 17:49, Patrick Boettcher wrote: On Monday 09 April 2012 13:39:36 Dominic Evans wrote: On 9 April 2012 10:40, Klaus Schmidingerklaus.schmidin...@tvdr.de wrote: + // http://www.smpte-ra.org

[vdr] Bug in pat.c (VDR 1.7.27) - possible fix attached

Hi, I located a small bug which has been introduced in 1.7.18 (at least I think so). Reading the Changes file I could not determine which change caused it, but the problem is the following. In pat.c: if the PMT of a service has a stream of stream-type 128 (0x80) the vpid is overridden with

[vdr] recordings not deleted in additional video-dirs (video.0x)

Hi all, First let me descibe my setup: I'm using VDR from http://e-tobi.net/vdr-experimental (vdr (1.7.16/1.7.16), 1.7.16-2~ctvdr1 - vdr-abi-1.7.16-multipatch) I switched to vdr-experimental beginning of November 2010. I think the version I'm using now (above) is available only since last

Re: [vdr] recordings not deleted in additional video-dirs (video.0x)

On Monday 10 January 2011 23:41:48 Tobias Grimm wrote: Am Montag, den 10.01.2011, 23:28 +0100 schrieb Patrick Boettcher: When now I merged the two video.0x directories onto a new partition I resolved the symbolic links with a small script and mv'd the corresponding files into the right

Re: [vdr] VDR can no longer be compiled with the current driver from http://linuxtv.org/hg/v4l-dvb.

. If there was a mistake and it's not compatible, we still can fix it, as kernel 2.6.32 is not yet out. best regards, -- Patrick Boettcher - Kernel Labs http://www.kernellabs.com/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] DVB-H

Hi Theunis, On Wed, 13 May 2009, Theunis Potgieter wrote: 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. DVB-H is more than just DVB-T plus H264 services. I strongly think that what you're having in your country is standard

Re: [vdr] DVB-H

On Wed, 13 May 2009, Theunis Potgieter wrote: So far I only pick something up on 586MHz and 706MHz w_scan produces this: tune to: :586000:I999B8C999D999M999T999G999Y0:T:27500: --no signal-- tune to: :586000:I999B8C999D999M999T999G999Y0:T:27500: (no signal)

Re: [vdr] DVB-H

On Wed, 13 May 2009, Theunis Potgieter wrote: My country is South Africa, (soccer host for world cup 2010) so it would be nice, if there was any kinda information on dvb-h + vdr. As I said before: DVB-H and VDR I think it will be hard to do and the outcome would be minimal, as VDR is a

Re: [vdr] [v4l-dvb-maintainer] [Wanted] dvb-ttpci maintainer

Hi, On Fri, 26 Sep 2008, Niels Wagenaar wrote: [..] Maybe it's bad that 2 years of development has gone down the drain. [..] (talking about mutliproto) Only a small part of all multiproto changes will go down the drain: The drivers written especially for multiproto can and will be converted

Re: [vdr] vdr-xine + mplayer-plugin + MPlayer - is it possible ?

I don't know if this is applicable for your setup, but did you try vdr-plugin-xineliboutput instead of vdr-plugin-xine? It is at least 3 things in one: - Client/Server architecture: splits VDR (server) and displaying software - Media Player integrated (via OSD) - X11 (XV or others) display

Re: [vdr] xineliboutput: viewing 16:9 content on 4:3 output device

Hi, On Tue, 8 Apr 2008, Ian Bates wrote: One more remark, if as I believe from the comments in the code above, that the '16:9 crop to 4:3' behaviour is not implemented in xineliboutput, am I the only one suffering from the lack of this feature? Am I the only one still using a 4:3 TV? I

Re: [vdr] Straw poll: stable version 1.6.0 now?

Hi Klaus, On Sun, 3 Feb 2008, Klaus Schmidinger wrote: Should there be a stable version 1.6.0 now, based on what's in version 1.5.14, but without DVB-S2 or even H.264 support? With H264 support, because some DVB-T channels (at least here in France) are starting to carry H264-channels,

Re: [vdr] Straw poll: stable version 1.6.0 now?

On Sun, 3 Feb 2008, Klaus Schmidinger wrote: On 02/03/08 13:26, Patrick Boettcher wrote: Hi Klaus, On Sun, 3 Feb 2008, Klaus Schmidinger wrote: Should there be a stable version 1.6.0 now, based on what's in version 1.5.14, but without DVB-S2 or even H.264 support? With H264