<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.linux.vdr">
    <title>gmane.linux.vdr</title>
    <link>http://blog.gmane.org/gmane.linux.vdr</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.vdr/47581"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.vdr/47580"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.vdr/47575"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.vdr/47569"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.vdr/47551"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.vdr/47550"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.vdr/47522"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.vdr/47516"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.vdr/47513"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.vdr/47501"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.vdr/47493"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.vdr/47486"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.vdr/47484"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.vdr/47480"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.vdr/47475"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.vdr/47474"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.vdr/47471"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.vdr/47466"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.vdr/47465"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.vdr/47463"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.linux.vdr/47581">
    <title>can't compile vdr-2.0.2 on alpinelinux distribution</title>
    <link>http://comments.gmane.org/gmane.linux.vdr/47581</link>
    <description>&lt;pre&gt;Hi,

I use alpinelinux (2.6.0) 64bit.
When I try to compile vdr I get the following error message:

--snip--
g++ -g -O3 -Wall -Werror=overloaded-virtual -Wno-parentheses -fPIC -rdynamic  audio.o channels.o ci.o config.o cutter.o device.o diseqc.o dvbdevice.o dvbci.o dvbplayer.o dvbspu.o dvbsubtitle.o eit.o eitscan.o epg.o filter.o font.o i18n.o interface.o keys.o lirc.o menu.o menuitems.o nit.o osdbase.o osd.o pat.o player.o plugin.o receiver.o recorder.o recording.o remote.o remux.o ringbuffer.o sdt.o sections.o shutdown.o skinclassic.o skinlcars.o skins.o skinsttng.o sourceparams.o sources.o spu.o status.o svdrp.o themes.o thread.o timers.o tools.o transfer.o vdr.o videodir.o -ljpeg -lpthread -ldl -lcap -lrt -lfreetype -lfontconfig   /usr/src/vdr-2.0.2/libsi/libsi.a -o vdr
i18n.o: In function `I18nInitialize(char const*)':
/usr/src/vdr-2.0.2/i18n.c:109: undefined reference to `libintl_textdomain'
/usr/src/vdr-2.0.2/i18n.c:110: undefined reference to `libintl_bindtextdomain'
i18n.o: In function `SetEnvLangu&lt;/pre&gt;</description>
    <dc:creator>Dieter Bloms</dc:creator>
    <dc:date>2013-05-21T20:27:51</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.vdr/47580">
    <title>[ANNOUNCE] VDR version 2.0.2 released</title>
    <link>http://comments.gmane.org/gmane.linux.vdr/47580</link>
    <description>&lt;pre&gt;VDR version 2.0.2 is now available at

      ftp://ftp.tvdr.de/vdr/vdr-2.0.2.tar.bz2

A 'diff' against the previous stable version is available at

      ftp://ftp.tvdr.de/vdr/Developer/vdr-2.0.1-2.0.2.diff

MD5 checksums:

5359cae7e14671cc9a3c690d45d8e0a2  vdr-2.0.2.tar.bz2
f4dfc7e6e9170cf56a10b1a2183e84a3  vdr-2.0.1-2.0.2.diff

This version fixes a few minor bugs that came up after the release of
version 2.0.1.


The changes since version 2.0.1:

- Fixed multiple occurrences of the same directory in the recordings list in case there
   are directories that only differ in non-alphanumeric characters (was broken by
   "Fixed selecting the last replayed recording in the Recordings menu in case there
   are folders and plain recordings with names that differ only in non-alphanumeric
   characters" in version 1.7.36).
- Fixed displaying the frame number when setting an editing mark (thanks to Thomas
   Günther).
- Fixed no longer generating any editing marks if the edited recording results in just
   one singl&lt;/pre&gt;</description>
    <dc:creator>Klaus Schmidinger</dc:creator>
    <dc:date>2013-05-20T09:29:11</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.vdr/47575">
    <title>vdr segfault while drawing menu</title>
    <link>http://comments.gmane.org/gmane.linux.vdr/47575</link>
    <description>&lt;pre&gt;Hello

I'm using vdr 2.0.1 on Debian (with Debian package) and xineliboutput (also provided by Debian).

I can connect xine on vdr, but once I hit 'ESC' to get the main menu, vdr segfaults.

Here's the backtrace:

Core was generated by `/usr/bin/vdr -v /mnt/video2/vdr -c /var/lib/vdr -L /usr/lib/vdr/plugins -r /usr'.
Program terminated with signal 11, Segmentation fault.
#0  0x00000000004eee4f in cSkinLCARSDisplayMenu::DrawLive (this=0x21c1c70, Channel=0x0) at skinlcars.c:1344

warning: Source file is more recent than executable.
1344         osd-&amp;gt;DrawText(xa00, yt00, itoa(Channel-&amp;gt;Number()), Theme.Color(clrChannelFrameFg), Theme.Color(clrChannelFrameBg), 
tallFont, xa02 - xa00, yt02 - yt00, taTop | taRight | taBorder);
(gdb) bt
#0  0x00000000004eee4f in cSkinLCARSDisplayMenu::DrawLive (this=0x21c1c70, Channel=0x0) at skinlcars.c:1344
#1  0x00000000004ef0f2 in cSkinLCARSDisplayMenu::Flush (this=0x21c1c70) at skinlcars.c:1659
#2  0x00000000004a5124 in cInterface::GetKey (this=0x21788e0, Wait=true) at interfac&lt;/pre&gt;</description>
    <dc:creator>Dominique Dumont</dc:creator>
    <dc:date>2013-05-18T15:49:59</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.vdr/47569">
    <title>noepg</title>
    <link>http://comments.gmane.org/gmane.linux.vdr/47569</link>
    <description>&lt;pre&gt;I'm trying to configure noepg headless. Some time ago I had GUI and 
configured noepeg, but now it's headless and after channels update I 
need to configure it again.

While there is no documentation, I've found thread describing it:
http://www.vdr-portal.de/board16-video-disk-recorder/board55-vdr-plugins/p961213-noepg-konfiguration/

Hovewer I use DVB-T and so channels have format like V-0-3588-1 
V-0-2916-1 V-0-2917-1 V-0-3589-1 V-0-2805-1 V-0-3700-1

My channels list doesn't contain anything like 3588, 2916 etc so I don't 
know how to manually build this list.

I'm attaching at the end my channels.conf.

Marx

:DVB-T
TVP1 
HD;EmiTel:191500:I999B7C999D999M999T999G999Y999:T:27500:102=27:103=pol&amp;lt; at &amp;gt;3;104=qaa&amp;lt; at &amp;gt;122,108=aux&amp;lt; at &amp;gt;122:105;106=pol,109=eng:0:1:8808:1:0
TVP1;EmiTel:184500:I999B7C78D0M64T4G16Y0:T:27500:102=27:104=pol&amp;lt; at &amp;gt;4;103=qaa&amp;lt; at &amp;gt;122,108=aux&amp;lt; at &amp;gt;122:105;106=pol,109=eng:0:44:8808:3:0
TVP2 
HD;EmiTel:184500:I999B7C78D0M64T4G16Y0:T:27500:202=27:204=pol&amp;lt; at &amp;gt;4;203=qaa&amp;lt; at &amp;gt;122,208=aux&amp;lt; at &amp;gt;122:205;206=pol,209=eng:0:2:8808:3:0
TVP2;Emi&lt;/pre&gt;</description>
    <dc:creator>Marx</dc:creator>
    <dc:date>2013-05-09T06:49:52</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.vdr/47551">
    <title>[ANNOUNCE] VDR Power Button Daemon 0.1.0</title>
    <link>http://comments.gmane.org/gmane.linux.vdr/47551</link>
    <description>&lt;pre&gt;Hello,

I tried to add all the suggestions, I got for vdrpbd 0.0.1 and created a new 
release.

This one comes with a template for vdrpbd.conf and even has a man page to 
describe the settings (man vdrpbd.conf).

Not it is also possible to customize the time range and the amount of keypresses 
for the emergency reboot feature (see vdrpbd.conf).

Please tell me if you still miss something.

Download here:
http://projects.vdr-developer.org/attachments/download/1363/vdrpbd-0.1.0.tar.xz

Yours

Manuel

_______________________________________________
vdr mailing list
vdr&amp;lt; at &amp;gt;linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

&lt;/pre&gt;</description>
    <dc:creator>Manuel Reimer</dc:creator>
    <dc:date>2013-04-27T08:55:00</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.vdr/47550">
    <title>Problems with VDSB, how to automate in SYSLOG</title>
    <link>http://comments.gmane.org/gmane.linux.vdr/47550</link>
    <description>&lt;pre&gt;Hi,
on some channels I get Video Data Stream Broken messages, not sure quite 
what triggers them yet.
They continue till the recording has finished.

I have switched off the emergency exit when VDSB occurs,  two reasons why:

1. It never cures the problem
2. Occasionally I get a single VDSB written when tuning to certain 
channels, the emergency exit
     would happen, but after the restart I would get a single VDSB again 
when the channel was tuned,
    ending up in a loop, as the VDR restart is not curing the problem.

So, I wanted to know if anyone has any code or rules for rsyslog to 
identify multiple VDSB messages
so I could trigger other actions. For example a reboot of the PC or 
maybe a driver load/unload.
I know I could extend the VDR start script to unload/load the DVB 
drivers after a VDR exit too.

Anyone have other suggestions maybe?

Cheers Brian
_______________________________________________
vdr mailing list
vdr&amp;lt; at &amp;gt;linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
&lt;/pre&gt;</description>
    <dc:creator>Brian-Imap</dc:creator>
    <dc:date>2013-04-27T08:50:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.vdr/47522">
    <title>ERROR: video data stream broken with DVB-T,AVC and ITE9135 device?</title>
    <link>http://comments.gmane.org/gmane.linux.vdr/47522</link>
    <description>&lt;pre&gt;Hi,

I've switched from DVB-S to DVB-T usb dongle with ITE9135 chipset and I'm
trying to record an AVC channel.
I'm using VDR-1.7.27.

Every thing OK when I use VDR with streamdev plugin. In fact I've set my
system to stream channels for more than 10 days. But after I create a timer
to record my stream, VDR gives following messages and jumps out.

ERROR: video data stream broken
initiating emergency exit
emergency exit requested - shutting down

I'm sure signal is fine, as I said there is no problem with streamdev. Also
I tried EPGScanTimeout=0 and EmergencyExit=0. Although it prevents VDR to
jump out, but nothing is recorded.

I've tested VDR-1.7.37 and problem persists.

Any idea?

Thanks.
Mike Smith.
_______________________________________________
vdr mailing list
vdr&amp;lt; at &amp;gt;linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
&lt;/pre&gt;</description>
    <dc:creator>Michael Smith</dc:creator>
    <dc:date>2013-04-21T16:11:40</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.vdr/47516">
    <title>RFC: one or many positioners?</title>
    <link>http://comments.gmane.org/gmane.linux.vdr/47516</link>
    <description>&lt;pre&gt;I'm currently implementing support for steerable dishes, loosely based
on https://linuxtv.org/patch/12911. In doing so, I'm defining a virtual
base class cPositioner, which defines all the functions necessary to
control the positioner. An implementation of cDiseqcPositioner will
allow control of "DiSEqC 1.2" and "USALS" motors. A plugin can derive
from cPositioner and implement its very own way of controlling a
positioner (like through a serial or USB port or whatever).

The question I have now is: will it be enough to have *one* single positioner
in any given setup, or are there actually users who have more than one
positioner?
Supporting only a single positioner (as is done in the aforementioned patch)
of course simplifies things quite a bit. So I wouldn't want to add this
level of complexity unless there is a real need for it.

Any opinions?

Klaus


_______________________________________________
vdr mailing list
vdr&amp;lt; at &amp;gt;linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

&lt;/pre&gt;</description>
    <dc:creator>Klaus Schmidinger</dc:creator>
    <dc:date>2013-04-21T12:54:13</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.vdr/47513">
    <title>VDPAU for AMD</title>
    <link>http://comments.gmane.org/gmane.linux.vdr/47513</link>
    <description>&lt;pre&gt;Anybody seen this?

&amp;lt;http://www.phoronix.com/scan.php?page=article&amp;amp;item=amd_opensource_uvd&amp;amp;num=1&amp;gt;

I think it's great news, at last there will be decent hardware
acceleration for AMD graphics, on a fully open source stack, and
without front-ends needing to use a new API. I know there was
already Intel and VAAPI, but that hasn't caught on as well as VDPAU for
some reason.

_______________________________________________
vdr mailing list
vdr&amp;lt; at &amp;gt;linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

&lt;/pre&gt;</description>
    <dc:creator>Tony Houghton</dc:creator>
    <dc:date>2013-04-19T13:22:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.vdr/47501">
    <title>difference between "g++ -pthread" and "g++ -lpthread"</title>
    <link>http://comments.gmane.org/gmane.linux.vdr/47501</link>
    <description>&lt;pre&gt;Hi,

 I'm hunting some race condition in my plugins which produce a segfault in libc or libavahi (still searching the right
packages with debug symbols, race condition may be related to having to dbus-mainloops in dbus2vdr and avahi4vdr, but I
don't know yet).
 While investigating this I found something about the option "-pthread" of g++.

 According to g++'s manpage this will set the right options for the preprocessor and compiler so the program can use the
pthreads lib. Especially it will set -D_REENTRANT and -lpthread etc.

 vdr seems only to use -lpthread and no other pthread-specific options.

 I'm not an expert on this topic, so I would like to know if someone can shed some light on this.
 Makefile may than be patched with:

==========
--- a/Makefile
+++ b/Makefile
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -14,12 +14,12 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
 CFLAGS   ?= -g -O3 -Wall

 CXX      ?= g++
-CXXFLAGS ?= -g -O3 -Wall -Werror=overloaded-virtual -Wno-parentheses
+CXXFLAGS ?= -g -O3 -Wall -Werror=overloaded-virtual -Wno-parentheses -pthread

 CDEFINES  = -D_GNU_SOURCE
&lt;/pre&gt;</description>
    <dc:creator>Lars Hanisch</dc:creator>
    <dc:date>2013-04-14T15:16:13</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.vdr/47493">
    <title>[ANNOUNCE] yaepghd-0.0.4</title>
    <link>http://comments.gmane.org/gmane.linux.vdr/47493</link>
    <description>&lt;pre&gt;Hello all,

version 0.0.4 of yaepghd is available, see the links at the end of the
message. These are the changes since the last community edition version
published in the vdr-portal.de forum:

2013-04-14: Version 0.0.4

- at least for now, this version is no longer hosted at
vdr-developer.org  as the old project (after ver. 0.0.1) still seems to
be abandoned, check the README file for the links
- switched to ScaleVideo API introduced with vdr-1.7.33 and dropped old
patch
- switched MAkefile to new style introduced with vdr-1.7.34
- integrated extra plugin themes found in the community edition thread
at vdr-portal.de
- updated anthra_1280 theme with the one from "pc_medusa" at vdr-portal.de
- added romanian translation
- added nOpacity_1920_darkblue theme contributed by "Saman" at vdr-portal.de
- added setup option to simulate returning back to the menu position
where yaepghd was entered from, adapted from a patch contributed by
"Saman" at vdr-portal.de



For now, the code is hosted here:
https://github.com&lt;/pre&gt;</description>
    <dc:creator>Lucian Muresan</dc:creator>
    <dc:date>2013-04-13T22:49:20</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.vdr/47486">
    <title>Which epg for Sky UK</title>
    <link>http://comments.gmane.org/gmane.linux.vdr/47486</link>
    <description>&lt;pre&gt;
Hi,

I used to use freesat diff patch to get the 10 day schedule from UK 
Freesat (BSkyB 28.2E), but seems its not been supported much for a while 
so I wonder what others are using?

--
Scott

_______________________________________________
vdr mailing list
vdr&amp;lt; at &amp;gt;linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

&lt;/pre&gt;</description>
    <dc:creator>Scott Waye</dc:creator>
    <dc:date>2013-04-13T19:52:52</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.vdr/47484">
    <title>[ANNOUNCE] VDR version 2.0.1 released</title>
    <link>http://comments.gmane.org/gmane.linux.vdr/47484</link>
    <description>&lt;pre&gt;VDR version 2.0.1 is now available at

      ftp://ftp.tvdr.de/vdr/vdr-2.0.1.tar.bz2

A 'diff' against the previous developer version is available at

      ftp://ftp.tvdr.de/vdr/Developer/vdr-2.0.0-2.0.1.diff

MD5 checksums:

e1b7a76c57c96300829dccd39eb20e7d  vdr-2.0.1.tar.bz2
fca54c4da4e9d9dd05f917b04a2eecf4  vdr-2.0.0-2.0.1.diff

This version fixes a few minor bugs that came up after the release of
version 2.0.0. It also allows compilation of VDR with older versions of
the DVB API.


The changes since version 2.0.0:

- Fixed initializing cDevice::keepTracks.
- Fixed an endless loop in cTextWrapper::Set() in case the given Width is smaller than
   one character (reported by Stefan Braun).
- Added definitions for older DVB API versions, back until 5.0 (based on a patch from
   Udo Richter).
- Fixed handling '/' and '~' in recording file names in case DirectoryEncoding is
   used (thanks to Lars Hanisch).
- Changed cThread::SetIOPriority() from "best effort class" to "idle class" in order to
   improve overa&lt;/pre&gt;</description>
    <dc:creator>Klaus Schmidinger</dc:creator>
    <dc:date>2013-04-13T11:40:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.vdr/47480">
    <title>Entering main menu with svdrpsend</title>
    <link>http://comments.gmane.org/gmane.linux.vdr/47480</link>
    <description>&lt;pre&gt;Hi!

I might be overlooking something really simple, but I can't figure
this out myself. :)

I'm trying to send "red" button to the LoadEPG plugin, to cancel the
scan. In theory, this is just:

svdrpsend hitk Menu 9 Red

(9 is the Loadepg mainmenu entry number)..

However, the above fails if there is a message on screen, in that case
it will start recording channel 9, which is not good. :)

This "works":

svdrpsend hitk Back Back Back Back Back Menu 9 Red

But if you are in playback mode, it will cancel the playback. Probably
also some other situations where this fails.

So, is there a 100% sure way to enter main menu?

_______________________________________________
vdr mailing list
vdr&amp;lt; at &amp;gt;linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

&lt;/pre&gt;</description>
    <dc:creator>Teemu Suikki</dc:creator>
    <dc:date>2013-04-09T07:53:59</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.vdr/47475">
    <title>[PATCH] VDR 2.0.0: Fix initialization of cDevice::keepTracks.</title>
    <link>http://comments.gmane.org/gmane.linux.vdr/47475</link>
    <description>&lt;pre&gt;As reported here

   http://www.vdr-portal.de/board17-developer/board97-vdr-core/p1137010-zu-sp%C3%A4tes-initialisieren-der-variable-keeptracks-in-device-c

the member variable keepTracks is initialized too late in the cDevice c'tor.
The attached patch fixes this.

Klaus
_______________________________________________
vdr mailing list
vdr&amp;lt; at &amp;gt;linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
&lt;/pre&gt;</description>
    <dc:creator>Klaus Schmidinger</dc:creator>
    <dc:date>2013-04-05T10:13:41</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.vdr/47474">
    <title>[PATCH] TT6400 dvbhddevice ScaleVideo aspect ratio correction</title>
    <link>http://comments.gmane.org/gmane.linux.vdr/47474</link>
    <description>&lt;pre&gt;Hi,

I wrote a patch for the ScaleVideo implementation in the dvbhddevice,
for keeping the actual aspect ratio of the video material when scaling.
It was tested by users at vdr-portal.de which also reported the
distortions (I don't own such a device), and they said it works [1]. You
can test it with the nOpacity skin and/or with the upcoming
yaepghd-0.0.4 plugin [2].

Regards,
Lucian


[1]
http://www.vdr-portal.de/board1-news/board2-vdr-news/p1137059-announce-nopacity-0-1-0/#post1137059
[2] http://sourceforge.net/projects/vdryaepghd/files/

From 1591c4cdc50dda35c52902ce46851ab57291351c Mon Sep 17 00:00:00 2001
From: Lucian Muresan &amp;lt;Lucian.Muresan&amp;lt; at &amp;gt;siemens.com&amp;gt;
Date: Fri, 5 Apr 2013 11:21:25 +0200
Subject: [PATCH] vdr-2.0.0 dvbhdffdevice ScaleVideo Aspect v3

---
 PLUGINS/src/dvbhddevice/dvbhdffdevice.c | 19 +++++++++++++++++--
 1 file changed, 17 insertions(+), 2 deletions(-)

diff --git a/PLUGINS/src/dvbhddevice/dvbhdffdevice.c b/PLUGINS/src/dvbhddevice/dvbhdffdevice.c
index dd7ace5..7a05ccb 100644
--- a/PLU&lt;/pre&gt;</description>
    <dc:creator>Lucian Muresan</dc:creator>
    <dc:date>2013-04-05T17:37:07</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.vdr/47471">
    <title>reelchannelscan for vdr-2.0.0???</title>
    <link>http://comments.gmane.org/gmane.linux.vdr/47471</link>
    <description>&lt;pre&gt;Hi,
It seems my old reelchannelscan doesn't work with vdr-2.0.0 and I
couldn't find a newer version.

Is this  plugin unmaintained?
If not, where can I download an updated version?
Regards
Halim


_______________________________________________
vdr mailing list
vdr&amp;lt; at &amp;gt;linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

&lt;/pre&gt;</description>
    <dc:creator>Halim Sahin</dc:creator>
    <dc:date>2013-04-06T15:57:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.vdr/47466">
    <title>VDR2 ATSC audio channels</title>
    <link>http://comments.gmane.org/gmane.linux.vdr/47466</link>
    <description>&lt;pre&gt;Solved. Used ChannelUpdate=2 in the setup.conf and VDR figured out the 
correct type, 0x81 in this case.



&lt;/pre&gt;</description>
    <dc:creator>Chris Florian</dc:creator>
    <dc:date>2013-04-05T02:06:48</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.vdr/47465">
    <title>VDR2 ATSC audio channels</title>
    <link>http://comments.gmane.org/gmane.linux.vdr/47465</link>
    <description>&lt;pre&gt;Hello,

        I recently had a problem with the audio of a live ATSC TV stream 
from VDR to XBMC using vnsi. One of the vnsi developers identified the 
problem a patched vnsi with a work around 
(http://forum.xbmc.org/showthread.php?tid=160951). I am also 
experiencing the same problem with VDR recordings, but this time I was 
told that this had to be fixed at the VDR end of things. If I make a 
recording and check the .ts file with ffmpeg, it shows:

Stream #0:0[0x21]: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), 
yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 17700 kb/s, 29.97 fps, 29.97 tbr, 
90k tbn, 59.94 tbc
Stream #0:1[0x24](eng): Audio: mp1 ([4][0][0][0] / 0x0004), 0 channels, s16
Stream #0:2[0x25](fre): Audio: mp3 ([4][0][0][0] / 0x0004), 0 channels, s16

But the streams should be AC3. My channels.conf for this channel looks 
like this:

CBLT-DT Toronto 
HD;(null):509000:M10:A:0:49=2:52=eng&amp;lt; at &amp;gt;4,53=es&amp;lt; at &amp;gt;4;52=&amp;lt; at &amp;gt;106,53=&amp;lt; at &amp;gt;106:0:0:3:0:0:0


Not being an ATSC or mpegts expert...can anyone help?



fedora 18
VDR &lt;/pre&gt;</description>
    <dc:creator>Chris Florian</dc:creator>
    <dc:date>2013-04-04T23:21:21</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.vdr/47463">
    <title>[ANNOUNCE] LIVE plugin version 0.3.0</title>
    <link>http://comments.gmane.org/gmane.linux.vdr/47463</link>
    <description>&lt;pre&gt;Hello

After the release of VDR 2.0 I'm happy to announce a new 'stable' version of 
the LIVE plugin.

Stable is written in quotes because it just declares the current stage of the 
development in the LIVE Git-tree as stable.

Since the last stable release of LIVE several contributions have been added by 
the community. I myself have only a very limited amount of time to do own 
development at the moment, so every good contribution was and is appreciated a 
lot. I thank all contributors to this version. You will find their names in 
the GIT history of this new version.

This version of LIVE still supports VDR versions before 1.7.36. Thus it still 
uses the old Makefile layout. Since a lot of VDR users still use older 
versions of VDR I wanted to make the current state of LIVE available for those 
who don't plan to upgrade their VDR with the VDR 2.0 release. Later versions 
of LIVE will offer only support for VDR 2.0.

More details about this release can be found on the LIVE plugin homepage:
http://live.vdr-d&lt;/pre&gt;</description>
    <dc:creator>Dieter Hametner</dc:creator>
    <dc:date>2013-04-04T20:59:15</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.vdr/47462">
    <title>Epgsearch mysteries</title>
    <link>http://comments.gmane.org/gmane.linux.vdr/47462</link>
    <description>&lt;pre&gt;Hi!

I have vdr 1.7.27 and epgsearch 1.0.1.beta2, from yavdr..

I'm recording "Game of Thrones" from Canal Digital Nordic. The third season
is starting in a few days..

The episodes have no episode name, and the description field simply says:
"(1:10/s3) 3. kausi maailman suosituimmasta HBO-sarjasta."

The text part is always the same, just the episode number varies. So just a
single character difference. But epgsearch thinks these are repeats! Even
if I set required match to 100%, it still thinks they are repeats..
shouldn't 100% mean exact match?
_______________________________________________
vdr mailing list
vdr&amp;lt; at &amp;gt;linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
&lt;/pre&gt;</description>
    <dc:creator>Teemu Suikki</dc:creator>
    <dc:date>2013-04-04T18:04:22</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.linux.vdr">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.linux.vdr</link>
  </textinput>
</rdf:RDF>
