Re: [vdr] Trying to run satip w/ Geniatech EyeTV Netstream 4Sat

[Martin Dummer]

Am 29.03.23 um 18:09 schrieb Harald Milz:

Initially, all seems to look good:



Hello Harald,


I miss lines like these:

Mar 28 19:28:25 vdr vdr: [21100] SATIP: Adding server
'192.168.166.129|DVBC-4|FRITZ!Box 6490 Cable' Bind: default Filters:
none CI: no Quirks: n
one

These lines give you the information with which name the SAT>IP device
has been detected and added.

Some SATIP devices have not-standard behaviour and need "quirks" to work
properly.

For example, the "GSSBOX"Grundig Sat Systems GSS.box DSI 400 has a
"SessionID Bug" and there is a "quirk" to fix this.

run "vdr -h" and read what options your satip plugin has and try if
"0x01: Fix session id bug" helps you.

Looking into the source code

https://github.com/rofafor/vdr-plugin-satip/blob/02a842f95a09a74d7eba90648c97693638007141/server.c#L130

there is a comment

// Elgato EyeTV Netstream 4Sat ?

which is an indication that your receiver may need this quirk, but its
not coded in the source yet.

If yes, please report your results here.


Bye

Martin





___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Running VDR from systemd on Raspberry Pi OS

[Martin Dummer]

Am 27.12.22 um 21:49 schrieb Marko Mäkelä:


First, I removed the custom /etc/fstab entry. Everything will be
controlled by systemd as follows:



On systemd-systems, each line  in /etc/fstab is automatically converted
by a binary "systemd-fstab-generator" into "xxx.mount" units. So what
you do here



sudo tee /etc/systemd/system/video.mount << "EOF"
[Unit]
BindsTo=dev-disk-by\x2dlabel-VDR.device
After=dev-disk-by\x2dlabel-VDR.device
Requires=systemd-fsck@dev-disk-by\x2dlabel-VDR.service
After=systemd-fsck@dev-disk-by\x2dlabel-VDR.service
[Mount]
Where=/video
What=/dev/disk/by-label/VDR
Type=ext4
Options=defaults,noatime,nofail
[Install]
WantedBy=dev-disk-by\x2dlabel-VDR.device
EOF


is more or less the same as one line in /etc/fstab.

see "man systemd.mount" and "man systemd-fstab-generator"

Just a hint

Martin


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] irc/matrix/mastodon

[Martin Dummer]

Am 14.11.22 um 10:55 schrieb Mikko Tuumanen:

Are there any vdr-related irc channels or matrix rooms?



I know about #gentoo-vdr on libera.chat but it's a quiet place


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] projects.vdr-developer.org might come to an end

[Martin Dummer]

Am 07.07.22 um 17:02 schrieb Richard F:

Has code been copied to github ?  Who's owning / maintaining it there ?


Please use this

https://vdr-projects.github.io/

as a first info page. Although this list has not been updated,
vdr-convert has been mirrored to https://github.com/vdr-projects/vdr-convert

If you want to add more code etc.. place a pull request, or "want your
repo back", tell us on

https://www.vdr-portal.de/forum/index.php?thread/135173-migration-von-projects-vdr-developer-org-auf-alternative-plattformen/

what your plans are.


Bye

Martin


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Making VDR run under Systemd

[Martin Wache]

Hi all, hi Marko!

Am 12.09.21 um 11:46 schrieb Marko Mäkelä:

I was an active VDR user from about 2004 to 2010


Yes good times! :-)

Actually I still use the VDR excatly for the same reasons: to record
shows for my kids.


If my Raspberry Pi were not an "always-on server" that runs some other
services as well, I might want to reimplement the "wake-on-RCU" hardware
that is generating a wake-on-LAN signal via the Nova-T PCI card,
possibly by extending
https://spellfoundry.com/product/sleepy-pi-2-usb-c/ or a similar product
that would implement a wake-on-timer for the Raspberry Pi. Then, the
system would power up nicely either by RCU or by a recording timer.
Integrating the wake-on-timer logic with Systemd could be another
challenge. I might try this on PC hardware, which already supports
wake-on-timer out of the box. A quick search turned up a promising
starting point:
https://www.freedesktop.org/software/systemd/man/systemd.timer.html

The motivation of this exercise is to have a stand-alone VDR front/back
end installation that plays nicely with Systemd, without reinventing any
logic around scheduling, startup, and shutdown.


I currently don't use systemd, but I have a similar use case for my
server. I agree that a solution with systemd would be nicer, but a few
years back, I didn't get systemd to work with vdr the way I liked.

So I've created a python script which starts vdr, and if vdr stops it
captures the next time vdr requests to be run. Then it kills vdr,
unloads the dvb drivers (which also switches of the LNBs) and opens all
the network ports vdr is using.

A second script runs every 5 minutes or so and checks if vdr is running,
a user is logged in, or some other services have been recently used.
If not it suspends the server and sets the wake-up time to vdr requested
time. So the server wakes up ahead of a recording.

The python script checks if the start time requested by vdr is close,
and starts vdr a few minutes before the requested time.

If I need the server or vdr I just send a wol packet. When I access the
vdr and the python script is running instead of the vdr, the python
script closes all network ports, loads the dvb drivers and starts the vdr.
This even worked very nicely with kodi, but I stopped using kodi, I
don't like the user interface. Now I use vdr-xineliboutput. I have to
start vdr-xineliboutput several times until the vdr is started, but I
don't mind :-).

Using this setup I can use the server for many more services, and don't
waste power when I don't need the vdr.

This was partly inspired by systemd, but I think it is still not
possible to implement this with systemd.

I can share the scripts if you like to modify them for your needs.


Regards,

Martin

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope

[Martin Gansser]

Thanks for you help
Martin 

Gesendet: Mittwoch, 10. Oktober 2018 um 11:50 Uhr
Von: "Klaus Schmidinger" 
An: vdr@linuxtv.org
Betreff: Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not 
declared in this scope
On 10/10/18 11:46 AM, Martin Gansser wrote:
> I have contacted Andreas.
>
>
> On advice of Andreas, I have defined the IOCTL myself in the file 
> dvbhdffdevice.h
>
> this is the Patch: define_AUDIO_GET_PTS.patch
> with this patch i get this warnings: [2]
>
> --- vdr-2.4.0/PLUGINS/src/dvbhddevice/dvbhdffdevice.h.orig 2018-10-10 
> 09:03:47.464147905 +0200
> +++ vdr-2.4.0/PLUGINS/src/dvbhddevice/dvbhdffdevice.h 2018-10-10 
> 09:04:59.353350738 +0200
> @@ -4,6 +4,9 @@
> * See the README file for copyright information and how to reach the author.
> */
>
> +#ifndef AUDIO_GET_PTS _IOR('o', 19, __u64)

This should just be

#ifndef AUDIO_GET_PTS

Klaus

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope

[Martin Gansser]

I have contacted Andreas.


On advice of Andreas, I have defined the IOCTL myself in the file 
dvbhdffdevice.h

this is the Patch: define_AUDIO_GET_PTS.patch
with this patch i get this warnings: [2]

--- vdr-2.4.0/PLUGINS/src/dvbhddevice/dvbhdffdevice.h.orig  2018-10-10 
09:03:47.464147905 +0200
+++ vdr-2.4.0/PLUGINS/src/dvbhddevice/dvbhdffdevice.h   2018-10-10 
09:04:59.353350738 +0200
@@ -4,6 +4,9 @@
  * See the README file for copyright information and how to reach the author.
  */
 
+#ifndef AUDIO_GET_PTS  _IOR('o', 19, __u64)
+#define AUDIO_GET_PTS  _IOR('o', 19, __u64)
+#endif
 #ifndef __DVBHDFFDEVICE_H
 #define __DVBHDFFDEVICE_H


when the patch only have this line:
+#define AUDIO_GET_PTS  _IOR('o', 19, __u64)
it compiles without warnings: [1]

[1] https://kojipkgs.fedoraproject.org//work/tasks/9241/30159241/build.log
[2] https://kojipkgs.fedoraproject.org//work/tasks/9649/30159649/build.log

what is correct ?

Thanks Martin
 

Gesendet: Dienstag, 09. Oktober 2018 um 11:31 Uhr
Von: "Klaus Schmidinger" 
An: vdr@linuxtv.org
Betreff: Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not 
declared in this scope
On 10/9/18 10:27 AM, Martin Gansser wrote:
> Hello Klaus,
>
> will you provide a kernel> = 4.8 patch or will I need to contact the kernel 
> developer for this?

Hello Martin,

please contact Andreas Regel  about this.
He maintains the dvbhddevice plugin.

Greetings
Klaus

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope

[Martin Gansser]

Hi Klaus,

I will contact him.
Many Thank

Martin

Gesendet: Dienstag, 09. Oktober 2018 um 11:31 Uhr
Von: "Klaus Schmidinger" 
An: vdr@linuxtv.org
Betreff: Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not 
declared in this scope
On 10/9/18 10:27 AM, Martin Gansser wrote:
> Hello Klaus,
>
> will you provide a kernel> = 4.8 patch or will I need to contact the kernel 
> developer for this?

Hello Martin,

please contact Andreas Regel  about this.
He maintains the dvbhddevice plugin.

Greetings
Klaus

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope

[Martin Gansser]

Hello Klaus,

will you provide a kernel> = 4.8 patch or will I need to contact the kernel 
developer for this?

Martin

Gesendet: Sonntag, 30. September 2018 um 11:36 Uhr
Von: "Klaus Schmidinger" 
An: vdr@linuxtv.org
Betreff: Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not 
declared in this scope
On 9/28/18 8:05 PM, Jasmin J. wrote:
> Hi!
>
> This is obsolete since Kernel 4.8:
> https://www.kernel.org/doc/html/v4.8/media/uapi/dvb/audio-get-pts.html
> So VDR would already have needed to be changed quite some time ago.
> I guess it is time to do it now.

BTW: I always thought that Linux kernel policy is not to allow userspace 
applications
to break. Apparently this is no longer the case :-(.

Klaus

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr[https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr]

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope

[Martin Gansser]

I have opened a fedora ticket [1]

https://bugzilla.redhat.com/show_bug.cgi?id=1633979

thanks
Martin
 

Gesendet: Freitag, 28. September 2018 um 12:02 Uhr
Von: "Alexander Grothe" 
An: "VDR Mailing List" 
Betreff: Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not 
declared in this scope

It seems this definition has been removed upstream, because it was considered 
to be "unused": 
https://github.com/torvalds/linux/commit/d21c249b26311dd193b100e65fc9e7ae96233d40#diff-56193b27b16cac28881a16f295c6ff3cL133
 

Am Fr., 28. Sep. 2018 um 11:22 Uhr schrieb Klaus Schmidinger 
mailto:klaus.schmidin...@tvdr.de]>:On 9/28/18 11:04 
AM, Martin Gansser wrote:
> ok, the Fedora30 package [1] 
> kernel-headers-4.19.0-0.rc5.git2.1.fc30.x86_64.rpm contains the file 
> /usr/include/linux/dvb/audio.h,
> but definition
> #define AUDIO_GET_PTS              _IOR('o', 19, __u64)
> fehlt.
>
> [1] 
> https://kojipkgs.fedoraproject.org//packages/kernel-headers/4.19.0/0.rc5.git2.1.fc30/x86_64/kernel-headers-4.19.0-0.rc5.git2.1.fc30.x86_64.rpm[https://kojipkgs.fedoraproject.org//packages/kernel-headers/4.19.0/0.rc5.git2.1.fc30/x86_64/kernel-headers-4.19.0-0.rc5.git2.1.fc30.x86_64.rpm]
>   
> I don't know what to do, write to the packager, so he can put in this 
> definition again ?

The question is: why did he remove it in the first place?

> or is there a other solution ?

You could put it back in yourself ;-).
Or take the header file from a previous version, where it still worked.

Klaus

___
vdr mailing list
vdr@linuxtv.org[mailto:vdr@linuxtv.org]
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr___
 vdr mailing list vdr@linuxtv.org 
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr[https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr]

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope

[Martin Gansser]

ok, the Fedora30 package [1] kernel-headers-4.19.0-0.rc5.git2.1.fc30.x86_64.rpm 
contains the file /usr/include/linux/dvb/audio.h,
but definition
#define AUDIO_GET_PTS  _IOR('o', 19, __u64)
fehlt.

[1] 
https://kojipkgs.fedoraproject.org//packages/kernel-headers/4.19.0/0.rc5.git2.1.fc30/x86_64/kernel-headers-4.19.0-0.rc5.git2.1.fc30.x86_64.rpm
 
I don't know what to do, write to the packager, so he can put in this 
definition again ?
or is there a other solution ?

thanks
Martin

Gesendet: Freitag, 28. September 2018 um 10:45 Uhr
Von: "Klaus Schmidinger" 
An: vdr@linuxtv.org
Betreff: Re: [vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not 
declared in this scope
On 9/28/18 10:21 AM, Martin Gansser wrote:
> ...
> dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope
> if (ioctl(fd_audio, AUDIO_GET_PTS, &pts) == -1) {
> ^
> dvbhdffdevice.c:569:33: note: suggested alternative: 'VIDEO_GET_PTS'
> if (ioctl(fd_audio, AUDIO_GET_PTS, &pts) == -1) {
> ^
> VIDEO_GET_PTS

AUDIO_GET_PTS is defined in /usr/include/linux/dvb/audio.h.
Maybe this isn't included correctly, or you have a wrong version of it?

Klaus

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope

[Martin Gansser]

Hi,

i am trying to compile vdr-2.4.0 for Fedora 30 on the Fedora rpm build server, 
but this fails with the following error message [1]:

g++ -O3 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 
-Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong 
-grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic 
-fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fPIC 
-Werror=overloaded-virtual -Wno-parentheses -D_GNU_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-I/builddir/build/BUILD/vdr-2.4.0/include -c -DPLUGIN_NAME_I18N='"dvbhddevice"' 
 -o dvbhdffdevice.o dvbhdffdevice.c
make: Leaving directory 
'/builddir/build/BUILD/vdr-2.4.0/PLUGINS/src/dvbhddevice'
dvbhdffdevice.c: In member function 'virtual int64_t cDvbHdFfDevice::GetSTC()':
dvbhdffdevice.c:569:33: error: 'AUDIO_GET_PTS' was not declared in this scope
 if (ioctl(fd_audio, AUDIO_GET_PTS, &pts) == -1) {
 ^
dvbhdffdevice.c:569:33: note: suggested alternative: 'VIDEO_GET_PTS'
 if (ioctl(fd_audio, AUDIO_GET_PTS, &pts) == -1) {
 ^
 VIDEO_GET_PTS
make: *** [Makefile:64: dvbhdffdevice.o] Error 1

[1] https://kojipkgs.fedoraproject.org//work/tasks/6531/29936531/build.log

thanks
Martin

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] TT S2 6400 IR Pinout

[Martin Gansser]

Maybe you can ask here in the German-speaking VDR forum a few guys.
http://www.vdr-portal.de/board60-linux/board61-hardware/107135-mini-ir-on-f%C3%BCr-tt-s2-6400/

Martin
 

Gesendet: Samstag, 25. März 2017 um 10:23 Uhr
Von: "Richard Scobie" 
An: "Klaus Schmidinger's VDR" 
Betreff: [vdr] TT S2 6400 IR Pinout
Hi,

Does anyone know the pinout details for the IR receiver module supplied
with the TT S2 6400 card?

Thanks,

Richard

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] vdr-2.2.0 compilation fails with gcc7

[Martin Gansser]

Thanks for your patch, but then there are further error messages:

g++ -O3 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 
-fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 
-grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 
-mtune=generic -fPIC -Werror=overloaded-virtual -Wno-parentheses -D_GNU_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -fPIC -c 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-DREMOTE_KBD -DVDR_USER=\"vdr\" -DSDNOTIFY 
-DLIRC_DEVICE=\"/var/run/lirc/lircd\" -DVIDEODIR=\"/var/lib/vdr/video\" 
-DCONFDIR=\"/etc/vdr\" -DARGSDIR=\"/etc/vdr/conf.d\" 
-DCACHEDIR=\"/var/cache/vdr\" -DRESDIR=\"/usr/share/vdr\" 
-DPLUGINDIR=\"/usr/lib64/vdr\" -DLOCDIR=\"/usr/share/locale\" 
-I/usr/include/freetype2 -I/usr/include/libpng16-o osdbase.o osdbase.c
osdbase.c: In member function 'eOSState cOsdMenu::HotKey(eKeys)':
osdbase.c:513:38: error: ISO C++ forbids comparison between pointer and integer 
[-fpermissive]
   if (s && (s = skipspace(s)) != '\0' && '0' <= s[i] && s[i] <= '9') {
  ^~~~
make: *** [Makefile:126: osdbase.o] Error 1

I fixed this with this patch:

--- a/osdbase.c.orig2017-02-15 15:55:34.555128665 +0100
+++ b/osdbase.c 2017-02-15 15:56:30.898068614 +0100
@@ -510,7 +510,7 @@
   const char *s = item->Text();
   i = 0;
   item_nr = 0;
-  if (s && (s = skipspace(s)) != '\0' && '0' <= s[i] && s[i] <= '9') {
+  if (s && (s = skipspace(s)) != NULL && '0' <= s[i] && s[i] <= '9') {
  do {
 item_nr = item_nr * 10 + (s[i] - '0');
 }

it compiles fine, but I am not shure if this is correct ?
 
 

Gesendet: Donnerstag, 02. März 2017 um 11:35 Uhr
Von: "Klaus Schmidinger" 
An: "VDR Mailing List" 
Betreff: Re: [vdr] vdr-2.2.0 compilation fails with gcc7
On 02.03.2017 11:25, Martin Gansser wrote:
> vdr-2.2.0 compilation fails with gcc7 on Fedora26.
> ...

This will be fixed in version 2.3.3, where I have changed "unsigned"
to "signed" in several places to avoid these problems.
Attached are the respective changes, it still applies to version 2.2.0.

Klaus
___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] vdr-2.2.0 compilation fails with gcc7

[Martin Gansser]

vdr-2.2.0 compilation fails with gcc7 on Fedora26.

g++ -O3 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 
-fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 
-grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 
-mtune=generic -fPIC -Werror=overloaded-virtual -Wno-parentheses -D_GNU_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -fPIC -c 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-DREMOTE_KBD -DVDR_USER="vdr" -DSDNOTIFY -DLIRC_DEVICE="/var/run/lirc/lircd" 
-DVIDEODIR="/var/lib/vdr/video" -DCONFDIR="/etc/vdr" 
-DARGSDIR="/etc/vdr/conf.d" -DCACHEDIR="/var/cache/vdr" 
-DRESDIR="/usr/share/vdr" -DPLUGINDIR="/usr/lib64/vdr" 
-DLOCDIR="/usr/share/locale" -I/usr/include/freetype2 -I/usr/include/libpng16   
 -o dvbdevice.o dvbdevice.c
dvbdevice.c: In member function 'bool cDvbTuner::SetFrontend()':
dvbdevice.c:851:31: error: call of overloaded 'abs(unsigned int&)' is ambiguous
  frequency = abs(frequency); // Allow for C-band, where the frequency is 
less than the LOF
   ^
the full build.log file:
https://kojipkgs.fedoraproject.org/work/tasks/3857/18133857/build.log

corrected with the following patch, but i know that's not a good solution, 
because i am not a software developer.

--- a/dvbdevice.c.orig  2017-02-15 15:46:26.642238239 +0100
+++ b/dvbdevice.c   2017-02-15 15:46:51.820575674 +0100
@@ -848,7 +848,7 @@
 CHECK(ioctl(fd_frontend, FE_SET_VOLTAGE, volt));
 CHECK(ioctl(fd_frontend, FE_SET_TONE, tone));
 }
- frequency = abs(frequency); // Allow for C-band, where the frequency is 
less than the LOF
+ frequency = abs(int(frequency)); // Allow for C-band, where the frequency 
is less than the LOF
 
  // DVB-S/DVB-S2 (common parts)
  SETCMD(DTV_FREQUENCY, frequency * 1000UL);

Porting to GCC 7:
https://gcc.gnu.org/gcc-7/porting_to.html#cmath

can somebody help me to correct this ?

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Raspberry Pi, Streamdev + rpihddevice

[Martin Wache]

Hi Marko,

Am 08.07.14 13:34, schrieb Marko Mäkelä:

Like you say, it would be useful if the tuners and also the HDMI output
were suspended.

I wonder if it is possible to detect if anything is connected to the
HDMI output and powered on? If the HDMI attached display is disconnected
or powered off, it would make sense to suspend the video and audio
output (also on the electrical level) and detach all receivers that are
not being used for any recordings.


I like this idea :-)

According to this 
http://www.raspberrypi.org/forums/viewtopic.php?&t=18292 post it is 
possible to detect if a monitor is connected. Not sure what happens if 
the monitor is switched off...


Maybe tvservice can also be used (http://elinux.org/RPiconfig):
# /opt/vc/bin/tvservice -m CEA
Group CEA has 0 modes:

# /opt/vc/bin/tvservice -m DMT
Group DMT has 0 modes:

with no monitor connected. Unfortunately I'm not at home so I can't try 
out what happens if you connect a monitor, switch in on/off, etc...



For what it is worth, when I started using softdevice (not softhddevice)
several years ago, I developed a method that allows the video decoding
to be suspended when there is no interactive user (the system got
nvram-wakeup by timer, not by the user pressing the Power button). With
a software decoder, it is not only about power savings; it is also about
avoiding crashes when the decoder is buggy and you get a glitch in the
signal. I am still using the years-old hardware. I am interested in


Are you still using the old softdevice? I would have never guessed 
someone is still using it :-)


I must admit that I switched to the xineliboutput plugin years ago. I 
was missing the network features...



upgrading to something ARM-based (Cubieboard?) at some point, maybe when
USB DVB-T2 dongles become commodity (shortly after DVB-T2 is introduced
in Germany, I hope).


I'm using an ARM-Based Qnap-NAS as vdr server, it works really well with 
an USB DVB-T Dual-Tuner, and xineliboutput. I'm in the process of 
upgrading to a Cubietruck and a raspberry pi as client, but due to lack 
of time I have not got very far.


Cheers,

Martin


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] HD recording size

[Martin]

Now with Vdr 2.1.6

Same channel, same program, same time. (RTL, Alarm fur Cobra 11, 20.15)
Recording of RTL and RTL HD are now the same length.

Looks OK right now.

Martin


2014-05-09 14:07 GMT+02:00 Martin :

> Reverted the change :
> "Changed '%a' to the POSIX compliant '%m' in all scanf() calls "
>
> Now it compiles and can read the config files.
> HD Recording test will start soon.
>
>
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] HD recording size

[Martin]

Reverted the change :
"Changed '%a' to the POSIX compliant '%m' in all scanf() calls "

Now it compiles and can read the config files.
HD Recording test will start soon.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] HD recording size

[Martin]

I tried to compile vdr 2.1.6, it compiles with warnings but doesn't like my
settings files. channels.conf, diseqc.conf etc
So I can't test it with 2.1.6.

g++ -g -O3 -Wall -Wno-parentheses -fPIC -c -D_GNU_SOURCE
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
-DREMOTE_KBD -DLIRC_DEVICE=\"/var/run/lirc/lircd\"
-DVIDEODIR=\"/srv/vdr/video\" -DCONFDIR=\"/var/lib/vdr\"
-DCACHEDIR=\"/var/cache/vdr\" -DRESDIR=\"/usr/local/share/vdr\"
-DPLUGINDIR=\"/mnt/hdb1/vdr/t/vdr-2.1.6/PLUGINS/lib\"
-DLOCDIR=\"/mnt/hdb1/vdr/t/vdr-2.1.6/locale\" -I/usr/include/freetype2
 -o channels.o channels.c
channels.c: In static member function ‘static tChannelID
tChannelID::FromString(const char*)’:
channels.c:32: warning: unknown conversion type character ‘m’ in format
channels.c:32: warning: format ‘%d’ expects type ‘int*’, but argument 3 has
type ‘char**’
channels.c:32: warning: too many arguments for format
channels.c: In member function ‘bool cChannel::Parse(const char*)’:
channels.c:598: warning: unknown conversion type character ‘m’ in format
channels.c:598: warning: format ‘%d’ expects type ‘int*’, but argument 3
has type ‘char**’
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] HD recording size

[Martin]

I'm having a small problem.

Some HD recordings are 1/2 in time of the SD recording.
Not every HD recording has this problem, but most of the time I record from
RTL HD it has.

Recording is completed but only the length is wrong. So when I play it back
and jump in time, I must jump 60 sec to skip 120 sec etc.

VDR 2.1.1 but had the same problem with other versions.

Greetz from Holland,

Martin
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] [announce]: pvr350-1.7.5

[Martin Dauskardt]

There maybe a handful people still using the Hauppauge PVR350 card as 
output device. Although I have stopped active development, I will adapt 
the plugin as long as possible for newer vdr versions. I believe that 
the PVR350 is still a good choice in case you have a SD Tube TV and 
don't need digital audio output.


Version 1.7.5 is online:
http://projects.vdr-developer.org/attachments/download/1657/vdr-pvr350-1.7.5.tgz

- remove support for vdr < version 2.0
- adapt to changes in vdr-2.1.3
- remove support for ancient ivtv driver versions
- adapt Makefile to vdr's new Makefile system
- fix segfaults on exit when framebuffer device is missing

The plugin is still only for PAL ouput. If there are any users who want 
to use it for NTSC output, I may consider adding it. Please send me a mail.


Greets,
Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] diseqc.conf for Spaun and quad-LNBs

[Martin Lang]

Hi all,

I recently moved to Australia and now an looking to make my vdr work.
I have two quad LNBs (single local oscillator frequency) attached to a 
Spaun 9x7 multi-switch.


The spaun is set to "Quad mode".
For the S156E position ("satellite A") I can tune to both H+V and run a 
channel scan.
For the satellite "B" (S160E) I cannot tune anything - neither with vdr 
nor with dvbscan.


On S156E I have a Foxtel (Sky-equivalent) box attached and it tunes 
nicely, too. So maybe the Foxtel box did send some commands to the LNB 
which made it work, whereas on S160E this did not happen (yet) ?


Can anybody please help with the correct diseqC.conf ?
My attempt (see below) to modify the one from 
http://www.vdr-portal.de/index.php?page=Thread&postid=927921

did not work so far.

Thanks
Martin


# from this thread
# http://www.vdr-portal.de/index.php?page=Thread&postid=927921
# multiswitch + 2x Quad LNBs

##Multischalter Eingang A
#S13.0E 11700 V 9750 t v W15 [E0 10 38 F0] W15 A W15 t
#S13.0E 9 V 10600 t v W15 [E0 10 38 F1] W15 A W15 T
#S13.0E 11700 H 9750 t V W15 [E0 10 38 F2] W15 A W15 t
#S13.0E 9 H 10600 t V W15 [E0 10 38 F3] W15 A W15 T
##Multischalter Eingang B
#S19.2E 11700 V 9750 t v W15 [E0 10 38 F4] W15 B W15 t
#S19.2E 9 V 10600 t v W15 [E0 10 38 F5] W15 B W15 T
#S19.2E 11700 H 9750 t V W15 [E0 10 38 F6] W15 B W15 t
#S19.2E 9 H 10600 t V W15 [E0 10 38 F7] W15 B W15 T
#
#Multischalter Eingang A
S156E 9 V 10700 t v W15 [E0 10 38 F0] W15 A W15 t
#S156E 9 V 10700 t v W15 [E0 10 38 F1] W15 A W15 T
S156E 9 H 10700 t V W15 [E0 10 38 F2] W15 A W15 t
#S156E 9 H 10700 t V W15 [E0 10 38 F3] W15 A W15 T
#Multischalter Eingang B
#S160E 11700 V 9750 t v W15 [E0 10 38 F4] W15 B W15 t
S160E 9 V 10700 t v W15 [E0 10 38 F5] W15 B W15 T
#S160E 11700 H 9750 t V W15 [E0 10 38 F6] W15 B W15 t
S160E 9 H 10700 t V W15 [E0 10 38 F7] W15 B W15 T


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Contribution to VDR - source codes, compiling latest 2.x on raspberry pi

[Martin Stiborský]

Hi Christopher,
Thanks a lot for response.

The idea with debian vdr packages was just for getting the idea about build
process, nothing else.

Thanks for mentioning vdr4arch, that's it, I haven't found this so far,
I'll focus there.


On Sun, Sep 1, 2013 at 8:19 PM, Christopher Reimer  wrote:

> **
>
>
>
> Am 1.9.2013 19:58, schrieb Martin Stiborský:
>
> Hi guys,
> I'd like to ask you for a little help, small introduction into how it
> works in VDR development.
>
> My goal: I'd like to have latest VDR on my RaspberyPi, I have there
> Archlinux ARM installed, so it will be maybe a little bit more complicated,
> than just upgrading already existing 1.x debian package, which you can use
> on Raspbian.
>
> You know, previously I had Raspbian on the RasPi and installing and
> configuring VDR was really simple.
> There was webinterface and streaming to my workstation with VLC as a
> client was working out-of-box (I have right now only DVB-T USB dongle).
> As far as I know there is only 1.x deb package now.
>
> I'd like to create similar package for Archlinux (PKGBUILD).
>
> I'll definitelly use already existing debian package as a starting point
> for my work.
>
>
>  That's definitely the wrong attempt. You can't use debian packages as
> starting point for Arch Linux packages.
>
> Maybe you want to contribute to vdr4arch -->
> https://github.com/CReimer/vdr4arch
>
>
> There are also already some projects existing on that matter:
> http://sourceforge.net/projects/archvdr/
> https://aur.archlinux.org/packages/vdr/
> (I'm quite confused why there is already existing AUR PKGBUILD and also
> another project for the same purpose, Wiki is saying that the other project
> should be used instead of AUR package, really don't know why
> https://wiki.archlinux.org/index.php/VDR#Installation)
>
>
>  ArchVDR is not up-to-date and it doesn't take care of the rules in
> Arch's DeveloperWiki.
> AUR is the most chaotic place you which exists in the Arch world. Most of
> the PKGBUILDs there are in very bad condition.
>
>
> Now I need to get idea about the VDR project in general.
> For example, I was not able to find some code repository with your
> code...are you using git, hg or svn? Is the repository publicly accessible?
>
> Maybe this? http://projects.vdr-developer.org/git/
>
> I have found also this: http://linuxtv.org/repo/ But VDR is not there,
> although there is a lot of links and information about VDR.
>
> What is the main place for "dev" informations? Is it this wiki?
> http://linuxtv.org/vdrwiki/index.php/Main_Page
>
> Btw, what about to put such information on your homepage (
> http://www.tvdr.de/) ?
> Maybe even consider Github as a VDR development home, that would be
> awesome :) But that's completely your things how to keep you project
> running.
>
>
>  There's no publicly accessible GIT/HG repository for VDR, but you have
> the choice between stable versions (2.0.3) and developer versions (2.1.1)
>
>
> Christopher Reimer
>
> ___
> vdr mailing list
> vdr@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
>
>


-- 
S pozdravem / Best regards
Martin Stiborský

Jabber: st...@njs.netlab.cz
Twitter: http://www.twitter.com/stibi
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] Contribution to VDR - source codes, compiling latest 2.x on raspberry pi

[Martin Stiborský]

Hi guys,
I'd like to ask you for a little help, small introduction into how it works
in VDR development.

My goal: I'd like to have latest VDR on my RaspberyPi, I have there
Archlinux ARM installed, so it will be maybe a little bit more complicated,
than just upgrading already existing 1.x debian package, which you can use
on Raspbian.

You know, previously I had Raspbian on the RasPi and installing and
configuring VDR was really simple.
There was webinterface and streaming to my workstation with VLC as a client
was working out-of-box (I have right now only DVB-T USB dongle).
As far as I know there is only 1.x deb package now.

I'd like to create similar package for Archlinux (PKGBUILD).

I'll definitelly use already existing debian package as a starting point
for my work.
There are also already some projects existing on that matter:
http://sourceforge.net/projects/archvdr/
https://aur.archlinux.org/packages/vdr/
(I'm quite confused why there is already existing AUR PKGBUILD and also
another project for the same purpose, Wiki is saying that the other project
should be used instead of AUR package, really don't know why
https://wiki.archlinux.org/index.php/VDR#Installation)

Now I need to get idea about the VDR project in general.
For example, I was not able to find some code repository with your
code...are you using git, hg or svn? Is the repository publicly accessible?

Maybe this? http://projects.vdr-developer.org/git/

I have found also this: http://linuxtv.org/repo/ But VDR is not there,
although there is a lot of links and information about VDR.

What is the main place for "dev" informations? Is it this wiki?
http://linuxtv.org/vdrwiki/index.php/Main_Page

Btw, what about to put such information on your homepage (
http://www.tvdr.de/) ?
Maybe even consider Github as a VDR development home, that would be awesome
:) But that's completely your things how to keep you project running.

Thank you guys for any information for my thing!

-- 
S pozdravem / Best regards
Martin Stiborský

Jabber: st...@njs.netlab.cz
Twitter: http://www.twitter.com/stibi
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] why does the Makefile not install all include files

[Martin Gansser]

why does the Makefile of e.q. vdr-1.7.32 only install the includes from
include/vdr include/libsi and not the dvb* and libhd* files ?

vdr Makefile:
# Includes:

install-includes: include-dir
@mkdir -p $(DESTDIR)$(INCDIR)
@cp -pLR include/vdr include/libsi $(DESTDIR)$(INCDIR)
...


I miss the following include files to compile a vdr plugin

/usr/include/vdr/dvbsddevice/dvbsdffdevice.h
/usr/include/vdr/dvbhddevice/dvbhdffdevice.h
/usr/include/vdr/dvbhddevice/hdffcmd.h
/usr/include/vdr/dvbhddevice/libhdffcmd/hdffcmd.h
/usr/include/vdr/dvbhddevice/libhdffcmd//hdffcmd_av.h
/usr/include/vdr/dvbhddevice/libhdffcmd/hdffcmd_generic.h
/usr/include/vdr/dvbhddevice/libhdffcmd/hdffcmd_hdmi.h
/usr/include/vdr/dvbhddevice/libhdffcmd/hdffcmd_mux.h
/usr/include/vdr/dvbhddevice/libhdffcmd/hdffcmd_osd.h
/usr/include/vdr/dvbhddevice/libhdffcmd/hdffcmd_remote.h

thanks martinkg


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] EPG language info from VDR

[Martin]

After some research I started sniffing the stream with dvbsnoop and I
found the language setting for DMAX, it is DEU. Now I've got to sniff
some more to make my list complete.

According to the iso is should be 'ger' I think but I found it, so it
will be soon in my client.

Greetz

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [ANNOUNCE] Javascript VDR client for motorola VIP

[Martin]

Found a home at projects.vdr-developer.org.

Client page : http://projects.vdr-developer.org/projects/vdr-vipclient

Big thnx to them for hosting it.

Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] EPG language info from VDR

[Martin]

> Date: Sat, 15 Dec 2012 12:09:02 +0100
> From: Klaus Schmidinger 
> To: vdr@linuxtv.org
> Subject: Re: [vdr] EPG language info from VDR
> Message-ID: <50cc5a4e.8040...@tvdr.de>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 14.12.2012 18:43, Martin wrote:
>> Is there a way to get the language of a EPG transmission? For the
>> Motorola client I need to set the EPG language of a channel before
>> caching it.
>>
>> Most channels work, like ARD/ZDF but Deluxe Music (& SKY D) don't get
>> EPG with language set to 'ger'.
>> So can I log the (raw) EPG info from VDR so I can set the language.
>
> You might want to take a look at the code in eit.c.
> Search for "languageCode".
>
> Klaus
>


Too bad I'm not a C programmer, found some sections with
'languageCode' but don't understand what they do.
So for finding the right languagecode I just need to patch eit.c so
the EPG info is replaced by or added to the languageCode. Time for a
quick patch for that?

Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] EPG language info from VDR

[Martin]

Is there a way to get the language of a EPG transmission? For the
Motorola client I need to set the EPG language of a channel before
caching it.

Most channels work, like ARD/ZDF but Deluxe Music (& SKY D) don't get
EPG with language set to 'ger'.
So can I log the (raw) EPG info from VDR so I can set the language.

Greetz Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] [ANNOUNCE] Javascript VDR client for motorola VIP

[Martin]

Hi,

Because there isn't a video output plugin yet I'm working on a
javascript client so I can use this box with VDR.

Goal is a fully working VDR client, like VOMP. On the VDR site you
need streamdev.
Right now the basic function are working. Watching, zapping, EPG,
now/next guide and teletext.
DVB/Teletext Subtitles are build in the firmware of this box.

EPG works only with my channels list, box filters EPG on language.
Based on my channellist the language is switched 0-50 Dutch, 50-300
English, 400-550 German. But it can easily switched to german or other
language only.
Some auto switching must be made, hints?

Next will be the recording and timer access part.

Greetz from Holland,

Martin


html.tar.gz
Description: GNU Zip compressed data
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Error reading channels.conf on sh4 platform

[Martin]

Dec  3 23:24:21 192 vdr: [2462] loading /video/setup.conf
Dec  3 23:24:21 192 vdr: [2462] loading /video/sources.conf
Dec  3 23:24:21 192 vdr: [2462] ERROR: error in /video/sources.conf, line 21
Dec  3 23:24:21 192 vdr: [2462] ERROR: error in /video/sources.conf, line 22
Dec  3 23:24:21 192 vdr: [2462] ERROR: error in /video/sources.conf, line 23
Dec  3 23:24:21 192 vdr: [2462] ERROR: error in /video/sources.conf, line 24
Dec  3 23:24:21 192 vdr: [2462] ERROR: error in /video/sources.conf, line 25
Dec  3 23:24:21 192 vdr: [2462] ERROR: error in /video/sources.conf, line 26
Dec  3 23:24:21 192 vdr: [2462] ERROR: error in /video/sources.conf, line 27
Dec  3 23:24:21 192 vdr: [2462] ERROR: error in /video/sources.conf, line 28
Dec  3 23:24:21 192 vdr: [2462] ERROR: error in /video/sources.conf, line 29

The first line in sources.conf with info gives an error.

Target system :
Linux version 2.6.23.17_stm23_0123 (dailybuild@invergordon) (gcc version
4.3.4 20091123 (STMicroelectronics/Linux Base) ) #1 PREEMPT Fri Jan 6
10:47:20 CET 2012

Crosscompiled on:
Linux version 2.6.32-45-generic (buildd@batsu) (gcc version 4.4.3 (Ubuntu
4.4.3-4ubuntu5.1) ) #100-Ubuntu SMP Wed Nov 14 10:47:49 UTC 2012
With use of STlinux 2.3 for sh4-uclib. (STlinux 2.4 has a newer libuClibc
so it didn't work)
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] Error reading channels.conf on sh4 platform

[Martin]

Hi,

I'm trying to get VDR working on my motorola Vip1900.
VDR is running but it doesn't read the channels.conf
Tried 1.7.29 & 1.7.27 both give the same problem. Tested with my own
channels.conf and the channels.conf from the vdr-source.

Any hints?

/video # ls
> channels.conf  epg.data   setup.conf themes
> /video # vdr -L /vdr/lib -Pdummydevice -Pstreamdev-client
> vdr: error while reading '/video/sources.conf'
> vdr: error while reading '/video/channels.conf'



syslog

Dec  3 21:56:53 192 vdr: [1998] VDR version 1.7.27 started
> Dec  3 21:56:53 192 vdr: [1998] codeset is 'ASCII' - unknown
> Dec  3 21:56:53 192 vdr: [1998] ERROR (tools.c,1392): ./locale: No such
> file or directory
> Dec  3 21:56:53 192 vdr: [1998] no locale for language code 'deu,ger'
> 
> Dec  3 21:56:53 192 vdr: [1998] loading plugin:
> /vdr/lib/libvdr-dummydevice.so.1.7.27
> Dec  3 21:56:54 192 vdr: [1998] loading plugin:
> /vdr/lib/libvdr-streamdev-client.so.1.7.27
> Dec  3 21:56:54 192 vdr: [1998] loading /video/setup.conf
> Dec  3 21:56:54 192 vdr: [1998] loading /video/channels.conf
> Dec  3 21:56:54 192 vdr: [1998] ERROR: error in /video/channels.conf, line
> 1
> Dec  3 21:56:54 192 vdr: [1998] ERROR: error in /video/channels.conf, line
> 2
> Dec  3 21:56:54 192 vdr: [1998] ERROR: error in /video/channels.conf, line
> 3
> Dec  3 21:56:54 192 vdr: [1998] ERROR: error in /video/channels.conf, line
> 4
> Dec  3 21:56:54 192 vdr: [1998] ERROR: error in /video/channels.conf, line
> 5
> Dec  3 21:56:54 192 vdr: [1998] ERROR: error in /video/channels.conf, line
> 6
> Dec  3 21:56:54 192 vdr: [1998] ERROR: error in /video/channels.conf, line
> 7
> Dec  3 21:56:54 192 vdr: [1998] ERROR: error in /video/channels.conf, line
> 8
> Dec  3 21:56:54 192 vdr: [1998] ERROR: error in /video/channels.conf, line
> 9
> Dec  3 21:56:54 192 vdr: [1998] ERROR: error in /video/channels.conf, line
> 10
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] VDR consumes about 60% CPU load

[Martin Neuditschko]

On Mon, Jul 09, 2012 at 08:55:06AM +0100, Dave wrote:
> On 09/07/12 00:14, Martin Neuditschko wrote:
> >Hello,
> >
> >I actually recognized that my VDR consumes much CPU load.
> 
> Has the machine been rebooted since the leap-second on July 1? My
> VDR machine began to use much more CPU on that date (load average >
> 6 when recording!) but a reboot fixed it.

Thank you very much. After I rebooted my server, VDR consumes at
maximum 2.0% CPU during recording, so it looks like this was really
the problem.

As I had no real crash on 1. July I thought there is no problem (I
thought, either crash or no problem at all... x_x)

best regards
Martin Neuditschko

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] VDR consumes about 60% CPU load

[Martin Neuditschko]

Hello,

I actually recognized that my VDR consumes much CPU load.
I used 1.2.24 and updated now to 1.2.28, but the problem still is the same.
I also deactivated the epgsearch plugin which I am normally using for the
following tests.
The PC has a Dual Core CPU with 2 x 1,8GHz and 2GB RAM.

 # ps -T u -C vdr
 USER   PID  SPID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
 root 11975 11975 48.6  4.5 400564 92564 pts/4Sl+  00:52   0:51 ./vdr -w
 60 --vfat -c /transfer/video -v /transfer/video
 root 11975 11980  6.3  4.5 400564 92564 pts/4Sl+  00:52   0:06 ./vdr -w
 60 --vfat -c /transfer/video -v /transfer/video
 root 11975 11981  1.8  4.5 400564 92564 pts/4SNl+ 00:52   0:01 ./vdr -w
 60 --vfat -c /transfer/video -v /transfer/video
 root 11975 11982  0.0  4.5 400564 92564 pts/4Sl+  00:52   0:00 ./vdr -w
 60 --vfat -c /transfer/video -v /transfer/video

I attached the syslog lines of the last VDR start-up.
To my shame, I can't say when it started to use so much CPU. I set up MRTG 
several
month ago, but it looks like I didn't check its results afterwards since the
actual CPU graph is very strange (25% load the last 5 hours and also now,
nevertheless top says about 60-70% for VDR).

# top
Cpu(s): 34.9%us, 37.8%sy,  0.0%ni, 27.3%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:   2053476k total,  1411556k used,   641920k free,   127176k buffers
Swap:  4192248k total,74988k used,  4117260k free,   567280k cached

  PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+  COMMAND
  11975 root  20   0  391m 109m 4144 R 68.9  5.5  12:25.74 vdr

This shows half user / half system load. Pretty strange.

best regards
Martin Neuditschko
Jul  9 00:52:35 lacus vdr: [11975] VDR version 1.7.28 started
Jul  9 00:52:35 lacus vdr: [11975] codeset is 'UTF-8' - known
Jul  9 00:52:35 lacus vdr: [11975] found 0 locales in ./locale
Jul  9 00:52:35 lacus vdr: [11975] no locale for language code 'deu,ger'
Jul  9 00:52:35 lacus vdr: [11975] no locale for language code 'slv,slo'
Jul  9 00:52:35 lacus vdr: [11975] no locale for language code 'ita'
Jul  9 00:52:35 lacus vdr: [11975] no locale for language code 'dut,nla,nld'
Jul  9 00:52:35 lacus vdr: [11975] no locale for language code 'prt'
Jul  9 00:52:35 lacus vdr: [11975] no locale for language code 'fra,fre'
Jul  9 00:52:35 lacus vdr: [11975] no locale for language code 'nor'
Jul  9 00:52:35 lacus vdr: [11975] no locale for language code 'fin,suo'
Jul  9 00:52:35 lacus vdr: [11975] no locale for language code 'pol'
Jul  9 00:52:35 lacus vdr: [11975] no locale for language code 'esl,spa'
Jul  9 00:52:35 lacus vdr: [11975] no locale for language code 'ell,gre'
Jul  9 00:52:35 lacus vdr: [11975] no locale for language code 'sve,swe'
Jul  9 00:52:35 lacus vdr: [11975] no locale for language code 'rom,rum'
Jul  9 00:52:35 lacus vdr: [11975] no locale for language code 'hun'
Jul  9 00:52:35 lacus vdr: [11975] no locale for language code 'cat,cln'
Jul  9 00:52:35 lacus vdr: [11975] no locale for language code 'rus'
Jul  9 00:52:35 lacus vdr: [11975] no locale for language code 'srb,srp,scr,scc'
Jul  9 00:52:35 lacus vdr: [11975] no locale for language code 'hrv'
Jul  9 00:52:35 lacus vdr: [11975] no locale for language code 'est'
Jul  9 00:52:35 lacus vdr: [11975] no locale for language code 'dan'
Jul  9 00:52:35 lacus vdr: [11975] no locale for language code 'cze,ces'
Jul  9 00:52:35 lacus vdr: [11975] no locale for language code 'tur'
Jul  9 00:52:35 lacus vdr: [11975] no locale for language code 'ukr'
Jul  9 00:52:35 lacus vdr: [11975] no locale for language code 'ara'
Jul  9 00:52:35 lacus vdr: [11975] loading /transfer/video/setup.conf
Jul  9 00:52:35 lacus vdr: [11975] ERROR: unknown config parameter: PrimaryLimit = 0
Jul  9 00:52:35 lacus vdr: [11975] loading /transfer/video/sources.conf
Jul  9 00:52:35 lacus vdr: [11975] loading /transfer/video/channels.conf
Jul  9 00:52:35 lacus vdr: [11975] loading /transfer/video/timers.conf
Jul  9 00:52:35 lacus vdr: [11975] loading /transfer/video/svdrphosts.conf
Jul  9 00:52:35 lacus vdr: [11975] registered source parameters for 'A - ATSC'
Jul  9 00:52:35 lacus vdr: [11975] registered source parameters for 'C - DVB-C'
Jul  9 00:52:35 lacus vdr: [11975] registered source parameters for 'S - DVB-S'
Jul  9 00:52:35 lacus vdr: [11975] registered source parameters for 'T - DVB-T'
Jul  9 00:52:35 lacus vdr: [11975] probing /dev/dvb/adapter0/frontend0
Jul  9 00:52:35 lacus vdr: [11975] creating cDvbDevice
Jul  9 00:52:35 lacus vdr: [11975] new device number 1
Jul  9 00:52:35 lacus vdr: [11978] epg data reader thread started (pid=11975, tid=11978)
Jul  9 00:52:35 lacus vdr: [11978] reading EPG data from /

Re: [vdr] RFE: Make VDR more friendly when using combinations of DVB-S, DVB-T and DVB-C

[Martin]

And what about adding the satellite position to the source name?

Martin

2012/6/17 

> Send vdr mailing list submissions to
>vdr@linuxtv.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
> or, via email, send a message with subject or body 'help' to
>vdr-requ...@linuxtv.org
>
> You can reach the person managing the list at
>vdr-ow...@linuxtv.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of vdr digest..."
>
>
> Today's Topics:
>
>   1. Re: RFE: Make VDR more friendly when using combinations of
>  DVB-S, DVB-T and DVB-C (Klaus Schmidinger)
>   2. Re: RFE: Make VDR more friendly when using combinations of
>  DVB-S, DVB-T and DVB-C (Klaus Schmidinger)
>   3. Re: RFE: Make VDR more friendly when using combinations of
>  DVB-S, DVB-T and DVB-C (Luca Olivetti)
>   4. Re: RFE: Make VDR more friendly when using combinations of
>  DVB-S, DVB-T and DVB-C (Ludi)
>   5. Re: RFE: Make VDR more friendly when using combinations of
>  DVB-S, DVB-T and DVB-C (Klaus Schmidinger)
>
>
> --
>
> Message: 1
> Date: Sun, 17 Jun 2012 12:48:20 +0200
> From: Klaus Schmidinger 
> To: vdr@linuxtv.org
> Subject: Re: [vdr] RFE: Make VDR more friendly when using combinations
>of DVB-S, DVB-T and DVB-C
> Message-ID: <4fddb5f4.8040...@tvdr.de>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 17.06.2012 00:13, Marx wrote:
> > I use VDR mainly via www frontends, but I agree that there is need to
> tell VDR what to do with channels from different tuners. For example
> detection of recordings collision doesn't take into account that channels
> are from two different sources (two different tuners). It also doesn't
> understand that
> > it's possible to record simultanoesly from the same transponder. Vdr
> itself allow for all of it, but module which analyse collisions should be
> much more flexible. We also sometimes have the same channels in SD and HD
> which has different name but they differ only in quality.
> > I can imagine that it should be easily possible to teach colision
> detection module that some devices can record at once, also that it's
> possible to record multiple streams form the same transponder.
> > But it would be also great if we could virtually join some channels and
> tell recording module that they are the same channel, so they for example
> share EPG (it's possible now via plugins, I know). It should be possible to
> tell which one should be picked at first if we record from such virtual
> > channel. Collision module should advice for example "record from SD
> version of channel because it's on the same transponder that second
> recording we have planned" or "move this recording from DVB-S card to DVB-T
> card because DVB-S card records at the same time from another channel".
> > I can give example: polish channel TVP 1 is available from Hotbird as
> (1) SD version, (2) HD version. It's also available in DVB-T as (3) SD
> version and (4) HD version. I have this channel also available in (5) old
> good analogue version. It's probably also available from Astra, and from
> local
> > provider of DVB-C.
>
> The core VDR doesn't have these features, yet, but I'm planning on looking
> into these after version 2.0.
>
> Klaus
>
>
>
> --
>
> Message: 2
> Date: Sun, 17 Jun 2012 12:50:59 +0200
> From: Klaus Schmidinger 
> To: vdr@linuxtv.org
> Subject: Re: [vdr] RFE: Make VDR more friendly when using combinations
>of DVB-S, DVB-T and DVB-C
> Message-ID: <4fddb693.1020...@tvdr.de>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 17.06.2012 09:26, VDR User wrote:
> > On Sat, Jun 16, 2012 at 11:47 PM, Henning Pingel
> >   wrote:
> >> Hi,
> >>
> >> As some of you might already know, I'm working on a way to
> >> semi-automatically assign unique channel IDs to channels of different
> DVB
> >> providers. As I currently don't have time to explain it in detail
> today, I
> >> will just post some links and join this discussion later on when I have
> more
> >> time to sit down and explain stuff. ;-)
> >
> > Why not just patch VDR so it cycles through channels that use the same
> > channel number. No bothering with sql databases&  dependency, no
> > altering the real channel numbers, no real pain that I can think of.
> &

Re: [vdr] Streamdev to Streamdev with PVRInput card

[Martin Dauskardt]

> > streamdev doesn't query for a new device if the current and the next
> > channel has the same transponder. This is checked via the following
> > define:
> > 
> > channels.h:#define ISTRANSPONDER(f1, f2)  (abs((f1) - (f2))<  4) //XXX
> > 
> > All the channels in channel.conf have the same frequency, so streamdev
> > only changes the receivers but doesn't query for a device.
> > I havent understand exactly what you are doing. Do you use an analogue
> > input (like scart) of the pvr500 card and the channel switch script
> > changes the channel of another device ? If so, i could imagine the
> > frequency in channels.conf doesn't matter and you could simply modify
> > the frequencies.
> 
>   The frequency matters since he is using the tuner input.
> 
> Lars.

I think Rob's version of pvrinput has already the code for calling the 
externchannelswitch-script in "case eTelevision" and not only in "case 
eExternalInput". (Otherwise it wouldn't work at startup).

The code in ProvidesChannel() and SetChannelDevice checks not only for the 
same frequency, but also for the channel number:

if ((Channel->Number() == CurrentChannel.Number()) && (CurrentFrequency == 
Channel->Frequency()) && (CurrentInput == input) && (CurrentNorm == norm)) 

When Rob switches to another channel number, pvrinput should return
needsDetachReceivers = true
in ProvidesChannel(). It should also get a call for SetChannelDevice().

The problem is that both functions are never called - but obviously only in 
combination with running streamdev.

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Streamdev to Streamdev with PVRInput card

[Martin Dauskardt]

> I have a PVR500 with the PVRInput plugin running on my Backend.
> 
> I am using an old Hauppauge FF DVB-s card just as a frontend on another
> low powered system in order to throw the PVRInput channels to the
> kitchen.  On the backend it's all working, however, switching between
> channels doesn't quite work, as the streamdev server will give the
> client the same channel over and over again regardless of what it
> requested, unless the device changes (ie, if I go from /dev/video1 to
> /dev/video2 it'll change channel).
how do you force switching the video device?

> 
> An example of the channel list is:
> 
> 
> 2-WTTW PBS_Affiliate
> ntsc;WTTW:67250:TV|NTSC:V:0:301+101=2:300=@4:0:0:30020:32:32:0
> 3-WREX NBC_Affiliate
> ntsc;WREX:67250:TV|NTSC:V:0:301+101=2:300=@4:305:0:30030:48:48:0
> 4-WTVO ABC_Affiliate
> ntsc;WTVO:67250:TV|NTSC:V:0:301+101=2:300=@4:0:0:30040:64:64:0
> 5-WIFR CBS_Affiliate
> ntsc;WIFR:67250:TV|NTSC:V:0:301+101=2:300=@4:0:0:30050:80:80:0
> 6-WQRF Fox_Affiliate
> ntsc;WQRF:67250:TV|NTSC:V:0:301+101=2:300=@4:0:0:30060:96:96:0
> 
> 
> 
> But, obviously all on the same line.  I think this is probably an issue
> with streamdev rather than pvrinput as it works with Vomp happily.
> 
> I need it to detach and change channel in order to trigger the external 
> channel changer script.


pvrinput does its channel settings (this includes executing the 
externchannelswitch-script) inside its function OpenDvr() while the  encoder 
is still stopped. 
The settings will only be done if the bool ChannelSettingsDone is false. This 
bool is always false at first plugin start. I guess this is the reason why 
your channel settings were done once:

> Jun  7 19:13:24 oac vdr: [8795] entering cPvrDevice::OpenDvr: Dvr of
> /dev/video1 (PVR500#1) is closed
> Jun  7 19:13:24 oac vdr: [8795] entering cPvrDevice::CloseDvr: Dvr of
> /dev/video1 (PVR500#1) is closed
> Jun  7 19:13:24 oac vdr: [8795] cPvrDevice::ResetBuffering(): tsBuffer
> prefill = 314524 for /dev/video1 (PVR500#1)
> Jun  7 19:13:24 oac vdr: [8795] channel is television.
> Jun  7 19:13:24 oac vdr: [8795] OpenDvr: calling
> /etc/vdr/plugins/pvrinput/externchannelswitch.sh 30040 4 1 67250
> Jun  7 19:13:25 oac vdr: [8795] OpenDvr: returned from
> /etc/vdr/plugins/pvrinput/externchannelswitch.sh 30040 4 1 67250
> Jun  7 19:13:25 oac vdr: [8795] OpenDvr: sleeping for 3 seconds...
> Jun  7 19:13:28 oac vdr: [8795] OpenDvr: waking up
> Jun  7 19:13:28 oac vdr: [8795] SetVBImode(525, 0) on /dev/video1

When leaving OpenDvr, the bool is set to true. 
It will only become false again during runtime, if vdr calls the pvrinput-
function SetChannelDevice() and determines the needed settings.

And this is your problem. There are no debug messages from pvrinput's 
SetChannelDevice() or ProvidesChannel(), so vdr never calls  these pvrinput 
functions - although a channel switch for a pvrinput device is requested. 

But why? I have no idea. It works for you with vomp. It worked for me with 
streamdev when I tested this last year. But I had only streamdev-server 
running and used vlc to switch channels.

Maybe a streamdev developer reads this and has an idea or can explain possible 
interactions between streamdev-client, vdr and a receiving device.

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] AvetTV a761

[Martin Dauskardt]

> From: ? ?? (Pridvorov Andrey)   

> It crash also:
> 
> root@ua0lnjvdr:/var/log# v4l2-ctl -D -d /dev/video0

then it is for sure a serious driver bug. You should report this to  
linux-me...@vger.kernel.org

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] AvetTV a761

[Martin Dauskardt]

> > And yet. If I try use Avertv a761 and PRV 150 with pvrinput plugin, I have 
vdr crash:
>   It seems that the driver for your a761 registers also an analog video
> device. pvrinput tries to open it and sends a VIDIOC_QUERYCAP to determine
> if it's a device it can handle. But the driver don't like it...
> 
>   A dirty workaround would be to add the option "video_nr" and "vbi_nr" to
> your bttv-module (look at "modinfo bttv") and set the number to something
> greater than 16. pvrinput will only test the first 8 video-nodes (see
> global.h in its source if it's modified).
> 
>   The right way is to look into the driver and test it if it crashes when
> you send the ioctl mentioned above.

To the original poster:
I guess  ? ??  is not your real name. It would be nice if you 
would use at least a nickname.

Try "v4l2-ctl -D -d /dev/video0" while vdr is not running. Does this work or 
does it crash also?




___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] vdr Digest, Vol 63, Issue 32

[Martin Dauskardt]

> Date: Tue, 27 Apr 2010 07:03:50 +1200
> From: "Simon Baxter" 
> Subject: Re: [vdr] PVRINPUT plugin and "black/cinema bars"
> 
> Found the original hack (attached).
 
It will take time to have a look at  your code. 

Just to let you know:
The current pvrinput source allows to execute a script on every channel 
change. Have a look at "externchannelswitch" in
http://projects.vdr-developer.org/repositories/entry/plg-pvrinput/README

We won't support the usage of lirc transmitters directly in the plugin, but 
you could do it with an own binary.

Greets,
Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] PVRINPUT plugin and "black/cinema bars"

[Martin Dauskardt]

> From: VDR User 
> Subject: Re: [vdr] PVRINPUT plugin and "black/cinema bars"

> > I am pretty sure that your TV station broadcasts analogue TV not
> > anamorphic, which means it "delivers" the black bars to prevent the
> > aspect ?ratio of a 16:9 content.
> 
> The 'black bars' are called letterboxing.  It's used to _preserve_ the
> aspect ratio of widescreen content on 4:3 displays, not prevent it as
> you've suggested.
I meant that. Sorry for the mistake, english is not my native language.
> 
> > Unfortunately there is no way to detect the incoming signal (Tuner or
> > extern). Therefore it is not possible to automatically choose the right
> > setting.
> 
> Sure there is, just look in the mpeg headers.  If for some reason that
> flag isn't set correctly, you can also use the resolution along with
> some simple math to calculate the aspect ratio.

The mpeg is not delivered by the broadcaster, it is generated by the encoder. 
The content of the header is a result of the V4L2_CID_MPEG_VIDEO_ASPECT 
setting done by the application. 
> 
> >> Any ideas how to remove these?
> > 
> > The driver does not support clipping/cropping. We will always encode the
> > whole capture size. If there is already a bar, it will also be in the
> > encoded stream. You could try to use the zoom mode of your TV.
> 
> You _could_ write some functions to detect and remove letterboxing,
> though I don't know anyone motivated enough to actually do it.

The main goal of the pvrinput-plugin is to use the hardware encoder.I think it 
is a bad idea to do software-based on-the-fly-recoding.

Simon, which output device do you use? Maybe the xine- or xineliboutput-Plugin 
can do the needed zoom for you. (?)

Greets,
Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] PVRINPUT plugin and "black/cinema bars"

[Martin Dauskardt]

> From: "Simon Baxter" 
> Subject: [vdr] PVRINPUT plugin and "black/cinema bars"
> 
> Hi Everyone
> 
> My machine has (among others) a PVR-500 dual-channel analog card and I'm
> running vdr-1.6.0 with pvrinput-2008-07-05.

you should upgrade to our new pvrinput version:
http://projects.vdr-developer.org/attachments/download/288/vdr-
pvrinput-2010-04-14.tgz
see http://projects.vdr-developer.org/repositories/entry/plg-pvrinput/HISTORY

> 
> Doesn't matter which aspect ratio I choose, every channel under the PVR-500
> displays with black (cinema) bars on the top and bottom of the image.

I am pretty sure that your TV station broadcasts analogue TV not anamorphic, 
which means it "delivers" the black bars to prevent the aspect  ratio of a 
16:9 content.

Using the full screen for 16:9 content would result in "egg heads".  We call 
this anamorphic. A 16:9 TV would stretch this; a 4:3 TV screen would need to 
scale it down (generating the needed bars).
At least in Germany analogue broadcastings are never anamorphic.
I gues you are using the extern inputs to supply video from a digital 
receiver? Then it could be anamorphic of course. You would need to tell your 
digibox that you have a 16:9 TV.

The pvrinput setup-entry "aspect ratio" does not really change the aspect 
ratio. It is only an ID inside the mpeg which notifies the TV if it is 
anamorphic or not. 

Unfortunately there is no way to detect the incoming signal (Tuner or extern). 
Therefore it is not possible to automatically choose the right setting.

> Any ideas how to remove these?
The driver does not support clipping/cropping. We will always encode the whole 
capture size. If there is already a bar, it will also be in the encoded 
stream. You could try to use the zoom mode of your TV.
> 
> Plugin setup is as follows:
> pvrinput.BackupHack = 0
> pvrinput.BackupInterval = 30
> pvrinput.EnableDigibox = 1
> pvrinput.FastChannelChange = 1
> pvrinput.RedRemoteDevice = /dev/ledxmit

These setup items have never been in any pvrinput version, so I gues you made 
patches. Could you provide them to me? 

Greets,
Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] System unresponsive and picture breakup with VDR 1.7.10 and Tevii S660 (USB)

[Martin Curran]

Hi,

> I use Xubuntu 9.10 and that has 2.6.31. 2.6.33 and higher wont't do
> for me, because the nvidia kernel driver won't compile on 2.6.33 and
> higher.

It will compile with the following patch: 
http://bugs.gentoo.org/show_bug.cgi?id=301318
Related thread at the nvidia forums, here: 
http://nvnews.net/vbulletin/showthread.php?t=148290

This old post gives handy pointers if you've never unpacked and patched the 
nvidia
driver before: http://forums.debian.net/viewtopic.php?t=24776

Martin (who appears to have run out of full stops)

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

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

[Martin Dauskardt]

> I can give you a setup option that switches between the old and the
> new version - if it really turns out to be necessary. Anything else
> would probably quickly become "rocket science" ,-)
> 
> Klaus

As already mentioned by Udo, the current behaviour often generates useless 
names when using search timers for series.

It may be a problem of bad epg data, but the quality of the epg data is as it 
is. 

I never had any problems before with displaying the recording name. 
But now I have wrong names for nearly every timer.

My vote is to fully revert the change or make it selectable with a setup 
option. 

Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

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

[Martin Dauskardt]

Several users have reported in the vdrportal forum that the bandwidth problem 
on FF cards became worse when switching from vdr 1.6 to 1.7

Even installing an additional budget card will not help, because since 1.6 vdr 
does not always prefer the budget card for recordings. 

A simple solution could be to install a DVB-T device and configure vdr to 
always start on a DVB-T channel. But the suspendoutput plugin should do the 
same trick.

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Hauppauge PVR HD

[Martin Dauskardt]

> Date: Tue, 12 Jan 2010 11:00:49 -0600
> From: Rob Davis 
> Subject: [vdr] Hauppauge PVR HD

> 
> Does anyone have any experience with this?  Does it work with the
> pvr-input plugin?

there is a linux driver and support for mythtv. But pvrinput does not support 
it, as it is currently a "cx2341x"-plugin (mpeg2-hardware encoder chips  
cx23415/cx23416/cx23418). There is also a big difference: The HD PVR delivers 
not mpeg2 but a h264/mpg4 stream. I don't  know if this stream is compliant to 
DVB-S2. 
One would need such a box for testing to see if it is possible to implement 
support in pvrinput or if it is easier to write a new plugin.

Greets, Martin

PS: Did you read my answer to your last question about pvrinput?

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

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

[Martin Dauskardt]

> Date: Mon, 11 Jan 2010 12:51:19 +0200
> From: Theunis Potgieter 
> Subject: Re: [vdr] [ANNOUNCE] VDR developer version 1.7.11
> 
> Hi Klaus, any plans on including vdr-1.7.9-pluginparam.patch for
> pvrinput plugin? http://drseltsam.device.name/vdr/pvr/src/pvrinput
> 
> This seems to create an input device of Plugin Type. I guess the
> vdr-iptv plugin also creates something similar.

pvrinput uses exactly the same pluginparam.patch. (It is taken from the iptv-
plugin.)


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [Patch] Allow to limit SVDRP port to given IP

[Martin Emrich]

Hi!

Klaus Schmidinger schrieb:

> How about this: if svdrphosts.conf contains only one single IP number, then
> open the port for only that IP number. Otherwise i needs to be opened 
> generally,
> anyway.

AFAIK one can only bind an IP socket to a local address (usually
corresponding to a network interface, e.g. 127.0.0.1) or 0.0.0.0, so if
I want to accept SVDRP _from_ a specific address via eth0, I have to
bind to the address configured on eth0.

As I get the peer address via accept(), I can directly determine if I
want to "risk" talking to (or even reading from) it, I assume VDR does
exactly this by looking up the address in svdrphosts.conf.

IMHO: If there is a vulnerability that is effective when one only calls
accept(), this is a problem of the OS (Kernel/libc). If one is really
paranoid, there's always netfilter.

Ciao

Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] PVRinput Ideas..

[Martin Dauskardt]

Am Donnerstag, 7. Januar 2010 04:10:21 schrieb Rob Davis:
 
> Would it be possible to get the pvrinput plugin to be able to create
> different channels line which all call the same s-video channel 
this works:

Test1:1:PVRINPUT|SVIDEO1:P:0:301=2:300:305:0:9012:0:0:0
Test2:1:PVRINPUT|SVIDEO1:P:0:301=2:300:305:0:9013:0:0:0
Test3:1:PVRINPUT|SVIDEO1:P:0:301=2:300:305:0:9014:0:0:0

> but also
> call the channel change script?

I will think about a possibility to call an external script (e.g. 
/usr/local/bin/extern_channelswitch.sh)  in SetChannelDevice() with two 
parameters: card-number (e.g. 1 if the available pvrinput device that will be 
used is /dev/video1)  and the SID (Service-Id, e.g. 9012 for channel 12 in 
your receiver)
 
> All it would need to do would be execute the program dct6200 (which
> could be in the /etc/vdr/plugins/pvrinput directory) with the argument
> of 41 or 08 and the cable box would change.  This would also work for
> someone using an irblaster with a SkyBox and a PVR card.

you would need to write a bash-Script (extern_channelswitch.sh) that executes 
your dct6200 binary with the needed commands.  Should be simple.
Please contact me privately with an example how your dct6200 binary has to be 
called. Is "dct6200 12" sufficient to switch to channel 12?

This solution could indeed be useful for other users, as it is not limited to 
your box. The script could execute lirc irsend or whatever.

I can't promise too much but I have an idea and will see if I get it working.

Greets,
Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] femon plugin doesn't work "ERROR (femonosd.c, 504): Function not implemented"

[Martin Dauskardt]

> > Sep 15 08:37:36 video vdr: [17541] ERROR: cOsd::SetAreas returned 6
> 
> Your OSD is running out of memory. The only cure is to shrink your 
> current OSD size.

Rolf, you know that this happens with the vdr default OSD size?

With my FF DVB-C (2 MB) and vdr 1.7.9 I have the following default values 
after deleting the setup.conf:
Left and Right 8%
Width 87%
Height 84%
To avoid the above mentioned error I reduced width and height to 82%. Then I 
got the femon OSD display, but with an other error:

Sep  8 20:26:27 ubuntuvdr vdr: [3668] ERROR: cFemonOsd::cFemonOsd() OSD height 
(461) smaller than required (480).

I increased the height to 84% and the error message disappeared. But now I got 
no display of the transponder and stream information - only the title. 

After setting width to 81% and height to 87% everything worked. 

Why is it not possible to show all femon OSD content with the vdr default OSD 
size? I don't remember that I had to change the OSD size with earlier 
vdr/plugin versions.

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] vdr 1.7.8 shows wrong recording length

[Martin Dauskardt]

I have a TS recording of more than two hours which seems to have no errors 
(Project X demux log looks fine). When I start playing it with vdr, the 
replay osd shows a recording lenghth of only 9 minutes. 

The same values is displayed in the recording menu (yes I know, this is not a 
vdr feature but comes from a patch)

Is it worth to investigate it? I still have this recording on my disc.

Greets,

Martin 

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] PVRInput and Streamdev

[Martin Dauskardt]

There is a bug in pvrinput which may also effect streamdev. (I know for sure 
that the bug leads to no picture with vdr 1.7.8)

Have a look in reader.c

There is at four places a wrong assignment. Instead of


ts_buffer[1] = (first ? 0x40 : 0x00) || (kVideoPid >> 8);

it has to be bitwise:

ts_buffer[1] = (first ? 0x40 : 0x00) | (kVideoPid >> 8);


@ rob:
You are using the PVR500 with NTSC? Did you need to patch pvrinput? As long as 
the tuner does not support PAL, it should simply return an error and work 
with the default driver setting (NTSC).
I am working on a new pvrinput release and am looking for a NTSC beta tester. 
If you are interested, contact me privately.

Greets,
Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Analog TV plugin

[Martin Dauskardt]

> Date: Wed, 08 Jul 2009 14:14:08 +0200
> From: Thomas Netousek 
> Subject: Re: [vdr] Analog TV plugin

> Hi Martin,
> 
> first of all thanks for your work !
> I am using the HVR1900 which has a DVB-T and an analog part purely for
> the capturing from analog.
> I am using the pvrusb2 driver from kernel 2.6.29.
> This version has two configuration options:
> - pvrusb2 sysfs support (EXPERIMENTAL)
> - pvrusb2 ATSC/DVB support (EXPERIMENTAL)
> 
> I am disabling the ATSC/DVB support and I get a /dev/video[0,1,2] 
> instead of /dev/dvb/adapter[0,1,2]

I discussed this issue in the pvrusb2 ML:

http://www.isely.net/pipermail/pvrusb2/2009-July/002493.html

and suggested a possible solution:

http://www.isely.net/pipermail/pvrusb2/2009-July/002495.html

Would be fine if you could try if this works when "pvrusb2 ATSC/DVB support" 
is enabled. If you have no other DVB device than the pvrusb2, than I wonder 
if VDR would accept a not existing - D option.

Example: 
modprobe pbrusb2 adapter_nr=9
vdr -D 0 -Ppvrinput

Will vdr fail to start, because the selected dvb adapter is not found? Or will 
vdr start like there is no DVB device?
Note: Maybe you need the dummydevice plugin to get vdr started without any DVB 
devices.

> You are right that I cannot switch easily between DVB-T and analog, but
> I do not have that requirement.

It should be possible to start a small script via commands.conf, which stops 
vdr, unloads pvrusb2, reloads it with a different adapter_nr, and restarts 
vdr with a -D option which allows the usage of the pvrusb2 DVB-T part. 
This way one could switch between analogue and DVB usage by restarting vdr via 
OSD. 

> 
> So actually I can confirm that pvrinput and pvrusb2 not only work with
> one adapter, but with three - and there seems to be no
> limit.

Do you have three pvrusb2 devices? wow.
pvrinput supports a maximum of 8 devices

Greets,
Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Analog TV plugin

[Martin Dauskardt]

> Date: Wed, 08 Jul 2009 07:45:05 +0200
> From: Thomas Netousek 
> Subject: Re: [vdr] Analog TV plugin
> To: VDR Mailing List 
> Message-ID: <4a543261.5070...@netousek.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> I suggest you use a card with hardware MPEG encoder and the pvrinput plugin.
> This works perfectly with a Happauge HVR1900 USB card.
> 
> Thomas

Hi Thomas,

I am one of the developers of the pvrinput plugin and made the changes to 
support the PVRUSB2. This is the first time somebody confirmed that it also 
works with their successor. 

As far as I know you cannot use DVB-T and analogue both at the same time 
(shared hybrid device). I think vdr will always open the DVB device, so the 
analogue part would be not accessable. How did you solve it?

Greets,
Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] vdrconvert-vdr-1.7.0+

[Martin Gansser]

Hi,

I have applied your patch against vdrconvert-0.2.0 not 0.2.1,
it works, but only the 2 channel audio stream is in the .iso file


projectx output:
Video:
PID: 0xFF
Audio:
PID: 0x100(deu)
PID: 0x103(AC-3)(deu)[PD]

--> MPEG Audio (0xC0) on PID 0x100
check & synchronize audio file  001.mp

--> AC-3/DTS Audio on PID 0x103
check & synchronize audio file  001.ac

summary of created media files:
.Video (m2v):   30265 Frames00:20:10.600
'/vdrconvert/film/tmp/vdr2dvd/12519/1/VDRSYNC.4Xe0ra/001.mpv'
Audio 0 (ac3):  37831 Frames00:20:10.5920/0/0/0
'/vdrconvert/film/tmp/vdr2dvd/12519/1/VDRSYNC.4Xe0ra/001.ac3'
Audio 1 (mp2):  50441 Frames00:20:10.5840/0/0/0
'/vdrconvert/film/tmp/vdr2dvd/12519/1/VDRSYNC.4Xe0ra/001.mpa'

have that something to do with the DVDUSESTREAMS="apid1:mp2+de dpid1:ac3
+de apid2:mp2+en" settings ?

i have upload the vdr2dvd.log on the following side.
http://www.sendspace.com/file/d50i8b


Martin


Am Freitag, den 26.06.2009, 10:19 +0200 schrieb Falk Spitzberg:
> Am Freitag, den 26.06.2009, 09:43 +0200 schrieb Falk Spitzberg:
> > Am Donnerstag, den 25.06.2009, 21:50 +0200 schrieb Martin Gansser:
> > > I have also tested your patch with vdrconvert-0.2.0 but with a few
> > > Extensions in vdr2dvd.sh.
> > > 
> > > The final error message in vdr2dvd.log says, that no audio traces
> > > exists.
> > 
> > 
> > Oops, i compared my hacked version with the wrong file. 
> > 
> > Here a diff against the original vdr2dvd.sh from vdrconvert-0.2.1
> > 
> > My hack assumes that you are using ProjectX.
> > 
> > Sorry for the confusion!
> > 
> > Falk
> > 
> 
> Diff file attached
> > 
> > > 
> > > 
> > > > Am Mittwoch, den 24.06.2009, 17:41 -0400 schrieb hu_emulator:
> > > > > I edited your changes and when I run vdrconvert with the new 
> > > > > vdr2dvd.sh it 
> > > > > errors out. Could you post or make available your vdr2dvd.sh?
> > > > 
> > > > What kind of error do you get?
> > > ___
> > > vdr mailing list
> > > vdr@linuxtv.org
> > > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr



___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] vdrconvert-vdr-1.7.0+

[Martin Gansser]

S='de en'
+ '[' -z no ']'
+ '[' -z '' ']'
+ DVDSAVEAUTHORSRC=no
+ '[' -z yes ']'
+ '[' -z yes ']'
+ '[' -z /usr/local/src/vdrconvert/share/vdrconvert/images/pal/Main.pnm ']'
+ '[' -z /usr/local/src/vdrconvert/share/vdrconvert/images/pal/Sub.pnm ']'
+ '[' -z /usr/local/src/vdrconvert/share/vdrconvert/images/silence-1s.mp2 ']'
+ '[' -z /usr/local/src/vdrconvert/share/vdrconvert/images/silence-1s.mp2 ']'
+ case $VDRCONVERT_LANG in
+ '[' -z 'Film abspielen' -o 'Film abspielen' = '' ']'
+ '[' -z Titelmenü -o Titelmenü = '' ']'
+ '[' -z '' -o '' = '' ']'
+ DVDMENU_MENU_MAIN='Menu Title'
+ '[' -z '' -o '' = '' ']'
+ DVD_PAGETEXT=Page
+ '[' -z '' -o '' = '' ']'
+ DVD_MINUTESTEXT=Min
+ '[' -z '#A0A0FF' ']'
+ '[' -z '' ']'
+ DVDHIBUTTONCOLOR='#ff'
+ '[' -z '' ']'
+ DVDSELBUTTONCOLOR='#fff030'
+ '[' -z '#00' ']'
+ '[' -z '#00' ']'
+ '[' -z '' ']'
+ DVDMAINCOLFG='#00FF'
+ '[' -z '' ']'
+ DVDCOLBG='#'
+ '[' -z '' ']'
+ DVDSUBCOLFG='#C0C0C0FF'
+ '[' -z '' ']'
+ DVDMAINVERCOLFG='#C0C0C0FF'
+ '[' -z '' ']'
+ DVDMAINSUBTITLECOLFG='#C0C0C0FF'
+ '[' -z '' ']'
+ DVDMAINTITLECOLFG='#C0C0C0FF'
+ '[' -z '' ']'
+ DVDMAINPAGETEXTCOLFG='#C0C0C0FF'
+ '[' -z '' ']'
+ DVDBUTTONTEXTCOLFG='#C0C0C0FF'
+ '[' -z '' ']'
+ DVDMAINNUMTITLECOLFG='#C0C0C0FF'
+ '[' -z '' ']'
+ DVD_USE_COLOR_SCHEMA=YELLOW_WHITE
+ case $DVD_USE_COLOR_SCHEMA in
+ DVDMAINCOLFG='#'
+ DVDCOLBG='#'
+ DVDSUBCOLFG='#'
+ DVDMAINVERCOLFG='#090909FF'
+ DVDMAINSUBTITLECOLFG='#'
+ DVDMAINTITLECOLFG='#E2E2E2FF'
+ DVDMAINPAGETEXTCOLFG='#CDAD00FF'
+ DVDBUTTONTEXTCOLFG='#FFB90FFF'
+ DVDMAINNUMTITLECOLFG='#FFB9AFFF'
+ DVDBUTTONCOLOR='#FFD700'
+ DVDHIBUTTONCOLOR='#FFD700'
+ DVDSELBUTTONCOLOR='#fff000'
+ '[' -z '' ']'
+ export DVD_USE_FONT=arial
+ DVD_USE_FONT=arial
+ '[' -z /usr/local/src/vdrconvert/share/vdrconvert/fonts/truetype ']'
+ '[' '!' -z /usr/local/src/vdrconvert/share/vdrconvert/fonts/truetype -a '!' -z arial ']'
+ case $DVD_USE_FONT in
+ '[' -z arial/20 ']'
+ '[' -z arial/20 ']'
+ '[' -z arial/20 ']'
+ '[' -z '' ']'
+ font_big_additional=arial/14
+ '[' -z luximb/16 ']'
+ '[' -z '' ']'
+ font_medium_additional=arial/10
+ '[' -z luximb/16 ']'
+ '[' -z luximb/13 ']'
+ generatedvd_version='vdrconvert-0.2.0 cvs'
+ '[' -z '' ']'
+ DVDLABELMODE=--create-dvd-outside
+ '[' -z '' ']'
+ DVDLABELOPTIONS=--create-dvd-outside
+ '[' -z '' ']'
++ date +%d-%m-%Y
+ DVDLABELDATEFORMAT=DVD-25-06-2009
+ '[' -z '' ']'
+ DVDLABELTEMPLATE=/usr/local/src/vdrconvert/share/vdrconvert/postscript/penguin.eps
+ '[' -z '' ']'
+ DVDSUBCATECORY='vdrconvert-0.2.0 cvs'
+ '[' -z '' ']'
+ DVDLABELPRINTER=
+ '[' -z '' ']'
+ DVDDELETELABEL=yes
+ '[' -z /usr/local/src/vdrconvert/bin/jpeg2eps ']'
+ '[' -z no ']'
+ '[' -z no ']'
+ '[' -z '' ']'
+ DVDXMLNORM=pal
+ '[' -z '' ']'
+ DVDXMLASPECT=4:3
+ '[' -z '' ']'
+ DVDXMLAUDIO=mp2
+ '[' -z '' ']'
+ DVDXMLCHANNELS=2
+ '[' -z '' ']'
+ DVDXMLSAMPLERATE=48khz
+ '[' -z '' ']'
+ XML_VERSION=1.0
+ '[' -z '' ']'
+ XML_ENCODING=ISO-8859-1
+ '[' -z '' ']'
+ DVD_EPGCHARSPERLINE=60
+ '[' pal = pal -a -z '' ']'
+ DVD_EPGLINES

[vdr] VDR exited with status 134

[Martin Gansser]

Hi,

VDR 1.6.0 exited with status 134, when generating a iso-file with
vdr-burn.

system is Fedora 11 x86_64

installed rpm packages:
vdr-osdteletext-0.8.1-2.fc11.x86_64
vdr-burn-debuginfo-0.1.0-0.18.pre21.fc11.x86_64
vdr-1.6.0-21.fc11.x86_64
vdr-mp3-0.10.1-7.fc11.x86_64
vdr-devel-1.6.0-21.fc11.x86_64
vdr-text2skin-debuginfo-1.1-24.cvsext0.10.fc11.x86_64
vdr-skinsoppalusikka-debuginfo-1.6.4-1.fc11.x86_64
vdr-skinsoppalusikka-1.6.4-1.fc11.x86_64
vdr-mp3-debuginfo-0.10.1-7.fc11.x86_64
vdr-sudoku-0.3.4-2.fc11.x86_64
vdr-streamdev-debuginfo-0.3.4-3.fc11.x86_64
vdr-ttxtsubs-0.0.9-1.fc11.x86_64
vdrsync-0.1.3-14.PRE1.050322.fc11.noarch
vdr-ttxtsubs-debuginfo-0.0.9-1.fc11.x86_64
vdr-debuginfo-1.6.0-21.fc11.x86_64
vdr-tvonscreen-1.0.141-5.fc11.x86_64
vdr-femon-1.6.6-2.fc11.x86_64
vdr-osdteletext-debuginfo-0.8.1-2.fc11.x86_64
vdr-sudoku-debuginfo-0.3.4-2.fc11.x86_64
vdr-tvonscreen-debuginfo-1.0.141-5.fc11.x86_64
vdr-mplayer-0.10.1-7.fc11.x86_64
vdr-femon-debuginfo-1.6.6-2.fc11.x86_64
vdr-text2skin-1.1-24.cvsext0.10.fc11.x86_64
vdr-streamdev-server-0.3.4-3.fc11.x86_64
vdr-burn-0.1.0-0.18.pre21.fc11.x86_64
vdr-skins-20081124-5.fc11.noarch

/var/log/messages reports this message:

Jun 14 00:06:38 gecko vdr: [4824] burn: ISO_FILE=/film/Falling Down - Ein ganz
normaler Tag.iso
Jun 14 00:06:38 gecko runvdr: VDR exited with status 134, attempting restart

I set DAEMON_COREFILE_LIMIT=unlimited at 
end of /etc/sysconfig/vdr so that a core file could be dumped in /tmp.

# ulimit -c unlimited
set core dumps file size unlimited.

teling the kernel to become more verbose:

# echo "core.%e.%p" > /proc/sys/kernel/core_pattern

install all necessary debug files:
# debuginfo-install vdr-1.6.0-21.fc11.x86_64
vdr-burn-0.1.0-0.18.pre21.fc11.x86_64.

Debug the core file

[r...@gecko tmp]# gdb /usr/sbin/vdr ./core.vdr.4724 
GNU gdb (GDB) Fedora (6.8.50.20090302-23.fc11)
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
...
[New Thread 4729]
[New Thread 4731]
[New Thread 4735]
[New Thread 4781]
[New Thread 4728]
[New Thread 4730]
[New Thread 4727]
[New Thread 4732]
[New Thread 4733]
[New Thread 4734]
[New Thread 4780]

warning: Can't read pathname for load map: Eingabe-/Ausgabefehler.
Reading symbols from /usr/lib64/libjpeg.so.62.0.0...Reading symbols from
/usr/lib/debug/usr/lib64/libjpeg.so.62.0.0.debug...done.
done.
Loaded symbols for /usr/lib64/libjpeg.so.62.0.0
Reading symbols from /lib64/libpthread-2.10.1.so...Reading symbols from
/usr/lib/debug/lib64/libpthread-2.10.1.so.debug...done.
done.
Loaded symbols for /lib64/libpthread-2.10.1.so
Reading symbols from /lib64/libdl-2.10.1.so...Reading symbols from
/usr/lib/debug/lib64/libdl-2.10.1.so.debug...done.
done.
Loaded symbols for /lib64/libdl-2.10.1.so
Reading symbols from /lib64/libcap.so.2.16...Reading symbols from
/usr/lib/debug/lib64/libcap.so.2.16.debug...done.
done.
Loaded symbols for /lib64/libcap.so.2.16
Reading symbols from /lib64/librt-2.10.1.so...Reading symbols from
/usr/lib/debug/lib64/librt-2.10.1.so.debug...done.
done.
Loaded symbols for /lib64/librt-2.10.1.so
Reading symbols from /usr/lib64/libfreetype.so.6.3.20...Reading symbols from
/usr/lib/debug/usr/lib64/libfreetype.so.6.3.20.debug...done.
done.
Loaded symbols for /usr/lib64/libfreetype.so.6.3.20
Reading symbols from /usr/lib64/libfontconfig.so.1.3.0...Reading symbols from
/usr/lib/debug/usr/lib64/libfontconfig.so.1.3.0.debug...done.
done.
Loaded symbols for /usr/lib64/libfontconfig.so.1.3.0
Reading symbols from /usr/lib64/libstdc++.so.6.0.11...Reading symbols from
/usr/lib/debug/usr/lib64/libstdc++.so.6.0.11.debug...done.
done.
Loaded symbols for /usr/lib64/libstdc++.so.6.0.11
Reading symbols from /lib64/libm-2.10.1.so...Reading symbols from
/usr/lib/debug/lib64/libm-2.10.1.so.debug...done.
done.
Loaded symbols for /lib64/libm-2.10.1.so
Reading symbols from /lib64/libgcc_s-4.4.0-20090506.so.1...Reading symbols from
/usr/lib/debug/lib64/libgcc_s-4.4.0-20090506.so.1.debug...done.
done.
Loaded symbols for /lib64/libgcc_s-4.4.0-20090506.so.1
Reading symbols from /lib64/libc-2.10.1.so...Reading symbols from
/usr/lib/debug/lib64/libc-2.10.1.so.debug...done.
done.
Loaded symbols for /lib64/libc-2.10.1.so
Reading symbols from /lib64/ld-2.10.1.so...Reading symbols from
/usr/lib/debug/lib64/ld-2.10.1.so.debug...done.
done.
Loaded symbols for /lib64/ld-2.10.1.so
Reading symbols from /lib64/libattr.so.1.1.0...Reading symbols from
/usr/lib/debug/lib64/libattr.so.1.1.0.debug...done.
done.
Loaded symbols for /lib64/libattr.so.1.1.0
Reading symbols from /lib64/libexpat.so.1.5.2...Reading symbols from
/usr/lib/debug/lib64/libexpat.so.1.5.2.

Re: [vdr] vdr-xine-0.9.2 plugin does not support cutting.

[Martin Emrich]

Hi!

Carsten Koch schrieb:
> For example, when I use the '7' and '9' keys to jump to the
> previous/next cut mark, or when I use the '4' and '6' keys to
> fine-position a cut mark, the video image is not updated, so I
> am basically forced to navigate in complete darkness.
Huh, I always thought this was because of my graphics card (AMD RS690 
with radeon driver) when I tried it with the xine or xineliboutput 
plugin. Thus I still use the softdevice plugin on my desktop. (which has 
other problems, but is at least usable for cutting recordings). VDR is 
1.6.0.

VDR with xine was always "one keypress behind" when cutting, sounds like 
the symptoms you describe.

Ciao

Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] ERROR (dvbdevice.c,762): Bad file descriptor

[Martin Neuditschko]

What do you mean with "primary device"? I use a Hauppauge Nova-S-Plus DVB-S card
(it's the only DVB card in the system).

Thanks for the code.

regards
Martin


On Sat, May 09, 2009 at 06:55:28PM +0200, Klaus Schmidinger wrote:
> On 05/05/09 20:33, Martin Neuditschko wrote:
> > Hello,
> > 
> > I upgraded VDR from 1.6.0 to 1.7.7 (including DVB drivers). The VDR
> > is running and working correctly as I can say this after 30 minutes of 
> > testing.
> > 
> > But I get this strange error message each second after startup of VDR:
> > 
> >   ERROR (dvbdevice.c,762): Bad file descriptor
> 
> I assume your system has no real primary device for replay, right?
> 
> I'll add a check for fd_video being a valid file handle to this function.
> 
> You can put
> 
> if (fd_video >= 0) {
>...
>}
> 
> around the code that uses fd_video.
> 
> Klaus

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [OT] NVidia ION mini-ITX arriving

[Martin Emrich]

Hi!

Alex Betis schrieb:

> Fanless?!
> 
> All the pictures there clearly show the CPU fan.
> Ofcause it will be a lot better than other solutions we have today.

I took a look at the website (German: http://www.zotac.de). Only the
dual-core variant shows a CPU fan.

Has anybody already spotted a "street price" for the different variants?
Especially the one with the external PSU looks interesting...

Ciao

Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] ERROR (dvbdevice.c,762): Bad file descriptor

[Martin Neuditschko]

connection
May  5 20:02:20 lacus vdr: [21229] ERROR (dvbdevice.c,762): Bad file descriptor
May  5 20:02:20 lacus syslog-ng[2862]: last message repeated 29 times


lspci -v
01:06.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] 
(rev b2) (prog-if 00 [VGA controller])
Subsystem: eVga.com. Corp. Device b039
Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 11
Memory at f700 (32-bit, non-prefetchable) [size=16M]
Memory at e800 (32-bit, prefetchable) [size=128M]
Expansion ROM at fc00 [disabled] [size=64K]
Capabilities: [60] Power Management version 2
Kernel modules: rivafb, nvidiafb

01:07.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI Video and Audio 
Decoder (rev 05)
Subsystem: Hauppauge computer works Inc. Nova-S-Plus DVB-S
Flags: medium devsel, IRQ 17
Memory at fb00 (32-bit, non-prefetchable) [size=16M]
Capabilities: [44] Vital Product Data 
Capabilities: [4c] Power Management version 2
Kernel modules: cx8800

01:07.1 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio 
Decoder [Audio Port] (rev 05)
Subsystem: Hauppauge computer works Inc. Device 9202
Flags: medium devsel, IRQ 17
Memory at fa00 (32-bit, non-prefetchable) [size=16M]
Capabilities: [4c] Power Management version 2
Kernel modules: cx88-alsa

01:07.2 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio 
Decoder [MPEG Port] (rev 05)
Subsystem: Hauppauge computer works Inc. Device 9202
Flags: bus master, medium devsel, latency 32, IRQ 17
Memory at f900 (32-bit, non-prefetchable) [size=16M]
Capabilities: [4c] Power Management version 2
Kernel driver in use: cx88-mpeg driver manager
Kernel modules: cx8802

01:07.4 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio 
Decoder [IR Port] (rev 05)
Subsystem: Hauppauge computer works Inc. Device 9202
Flags: bus master, medium devsel, latency 32, IRQ 10
Memory at f800 (32-bit, non-prefetchable) [size=16M]
Capabilities: [4c] Power Management version 2



I did following to install the new DVB driver and VDR:
# Download DVB driver
hg clone http://linuxtv.org/hg/v4l-dvb

# Patch DVB driver
wget ftp://ftp.cadsoft.de/vdr/Developer/v4l-dvb-header-fix.diff
cd v4l-dvb/linux/
patch -p1 -i ../../v4l-dvb-header-fix.diff

# Build DVB driver
cd ..
make
make install

# Unload all DVB drivers
make unload

# Load required DVB drivers
modprobe budget_ci
modprobe dvb_ttpci

# Build VDR
wget ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.7.7.tar.bz2
tar -xjf vdr-1.7.7.tar.bz2
cd vdr-1.7.7/
cp Make.config.template Make.config

add:
DVBDIR=/usr/local/src/v4l-dvb/linux
to Make.config

cd ../v4l-dvb/linux/include/linux/
ln -s /usr/src/linux/include/linux/compiler.h
cd -

make

# Modify runvdr:
# Add following lines to function LoadDriver:
  modprobe dvb_ttpci
  modprobe budget_ci
  modprobe cx88_dvb
# Add following lines to function UnloadDriver:
  cd /usr/local/src/v4l-dvb/v4l
  make unload
  cd -

# Start VDR
./runvdr




best regards
Martin Neuditschko

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] weekly or daily timers

[Martin Emrich]

Hi!

VDR User schrieb:

> I've been using epgsearch and vdradmind-am for years and I can't
> imagine not using them!

Yes, I forgot to mention epgsearch. As more and more stations at least
in Germany have the nasty habit of moving TV shows to other time slots
if the ratings are not satisfactory, epgsearch is a "must-have".

It also saves disk space if your favourite TV show is temporary replaced
by e.g. a sports match.

Ciao

Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] weekly or daily timers

[Martin Emrich]

Hi!

marti...@embl.de schrieb:
> Is there someway in VDR to say schedule a repeated timer 'record this monday 
> to
> friday from 9pm til 11pm' or at least a daily timer 'record this every monday
> between 9pm and 11pm'
>
> Perhaps some plugin? Any hints?
>   
I am using vdradmin-am to schedule my recordings; there are checkboxes 
for every day of week.

Ciao

Martin


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] power consumption, powertop and wakups per second with a af9015 device, vp7045, and various plugins

[Martin Emrich]

Antti Palosaari schrieb:
> Heinrich Langos wrote:
>> How about a module option to force usage of the PID filter?
>> Should be easy to add if the code for enabling it on demand is aready 
>> there.
> 
> It is there.
> modinfo dvb-usb
> 

D'Oh, I only looked at 'modinfo dvb-usb-af9015' :)

Thanks!

Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] power consumption, powertop and wakups per second with a af9015 device, vp7045, and various plugins

[Martin Emrich]

Hi!

Antti Palosaari schrieb:

> All AF9015 devices supports PID-filtering by HW. And both Windows and 
> Linux driver supports also.

Interesting. How do I enable the HW PID filter? I have an old STB (Cyrix
MediaGX 300MHz) that has only USB 1.1.

Thanks

Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] power consumption, powertop and wakups per second with a af9015 device, vp7045, and various plugins

[Martin Emrich]

Hi!

Heinrich Langos schrieb:

> I am pretty sure the Siemens stick doesn't filter PIDs. The easy way to
> find out about that is to look at 
> http://www.linuxtv.org/wiki/index.php/DVB-T_USB_Devices
> and check if the device works with usb 1.1 or absolutely needs 2.0.

Hmm, I did't look at this page before. One more curious thing about my
af9015 USB device is that it seems to support USB 1.1 under Windows with
a special driver:

http://www.digittrade.de/shop/shop_content.php/coID/9


So I think it's just a question of the right firmware; the linux driver
does not support hardware PID filters (the driver says something like
"Found device in WARM state, disabling PID filter").

Ciao

Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] power consumption, powertop and wakups per second with a af9015 device, vp7045, and various plugins

[Martin Emrich]

Hi!

Heinrich Langos schrieb:
>
> I ran a couple of tests with a different DVB-T USB stick. The rather old
> "Fujitsu-Siemens DVB-T Mobile TV". That one turns out to need a lot less
> system resources. It also transfers the whole transport stream (several
> video and audio streams) over the USB and leaves demuxing to the host. 
> So we are not comparing apples and oranges.
> Comparing those numbers seems to indicate that there is room for improvment
> for the af9015 driver. 
>
> I'll try to get my hands on a couple more different usb receivers to try out
> some of the other drivers.
>
>   
I borrowed an af9015 device some time ago, and the owner told me that 
the primary problem with it is that it has no hardware PID filter. So 
even if VDR is only doing EPG scanning, the complete multiplex is 
congesting the USB link. Maybe your Fujitsu-Siemens receiver has a 
hardware PID filter...

Ciao

Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Pvrinput and HVR1300

[Martin Dauskardt]

> > In Germany the PVR150 ist still available in serveral web shops, while the 
PVR 
> > 250 seems to be out of stock everywhere.
> >   
> Are any of them delivering to other European countries? Or if youo could 
> tell me which sells it I can find out my self.
try www.amazon.de
They sell PVR 150 for 77,98 Euro
It seems they deliver to every european country.
http://www.amazon.de/gp/help/customer/display.html?nodeId=504950#ausland

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Pvrinput and HVR1300

[Martin Dauskardt]

> > My advise: Sell your HVR 1300 to a Windows user and buy a PVR150 + a 
> > Linux-supported DVB-T USB-stick.
> >   
> I have actually been thinking of that possibility also. The problem is 
> there are no PVR150 available. At least I have not seen those for a 
> while. Would PVR250 be as good/easy to install? I believe I could find 
> one of those.
In Germany the PVR150 ist still available in serveral web shops, while the PVR 
250 seems to be out of stock everywhere.

Both cards work fine. Some revisions of the PVR 150 have also a radio tuner. 
You could also use a PVRUSB2. 
The successor is the WinTV HVR-1950, which analogue part operates exactly as 
the predecessor PVRUSB2. It is tested with pvrinput yet, but I am pretty sure 
that I could do necessary changes easily. 

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Pvrinput and HVR1300

[Martin Dauskardt]

> So does anyone know if the same applies for analogtv plugin also?
> 
> \\Kartsa
> 
Forget the analogtv-plugin. Development stopped years ago. It does not support 
the current v4l2 mpeg API, so even a PVR150/250/350 would not work.

My advise: Sell your HVR 1300 to a Windows user and buy a PVR150 + a 
Linux-supported DVB-T USB-stick.

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Pvrinput and HVR1300

[Martin Dauskardt]

There is basic preparation for a future support in the pvrinput plugin, but it 
can't work for now.  I know that for sure because I am one of the pvrinput 
developers. The other developer who worked with the HVR1300 wrote a status 
report in the german vdrportal recently:
http://www.vdr-portal.de/board/thread.php?postid=789844#post789844

There are still problems with the driver (freezes), and (as far as I remember) 
the current release version of pvrinput would need additional hacks and 
patches.

Have a look in the FAQ from the plugin sources:

Q:
What about the HVR 1300?
A:
support is not finished yet.

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Pvrinput and HVR1300

[Martin Dauskardt]

The HVR 1300 is not supported by the pvrinput plugin. Card/driver work in a 
very different way from ivtv-supported cards, using a second device for the 
mpeg encoder.
It is not sure if pvrinput will ever support this card.

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Which extension for TS files?

[Martin Dauskardt]

> From: Klaus Schmidinger 

> Up to now VDR has used names like 001.vdr for its recording files.
> While moving to Transport Stream as the recording format, I need to
> use a different file name extension, and so was wondering which one
> to use. My first idea was *.ts, for "Transport Stream", but when I
> point, for instance, Konqueror to such a file, it thinks it is a
> "Qt Translation Source". So I was wondering if I should use *.mpg
> instead. This one is identified by Konqueror as an MPEG file and
> will make it launch a proper player.
> 
> What do you think about this?
I am strongly against this.
*.ts may conflict with KDE, but it is a usual ending for transport stream. 
Several mpeg-tools can handle this. I think the dreambox is also using *.ts 
for its recordings.

*.mpg would give much more problems with applications. A TS is not an 
mpeg-file. Applications which can play mpg but not TS may even crash.

Greets,
Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] [PATCH] S2API for vdr-1.7.1 vanilla and extensions patch 64 ( 071020008 )

[Martin Schlosser]

Hello,

thanks for the quick response! Everything compiled fine now.
But still something seems to be broken there. Watching TV with mplayer 
works fine but there is a problem with vdr/xine. I attached my syslog 
and the output of vdr-sxfe. I hope someone has an idea whats causing this.


Many thanks in advance!
Martin Schlosser

> Hi,
>
> you are using the older patch use the attached one.
> The fix-s2api-dvbs is not needed with this one.
>
> cu
>
> Edgar (gimli) Hucek
>
> >  > Hi All,
> >  >
> >  > this patches are for Steve Toth's repository at :
> >  > http://linuxtv.org/hg/~stoth/s2/ .
> >  > In theory they should work. I did them offline from my VDR.
> >  >
> >  > cu
> >  >
> >  > Edgar (gimli) Hucek
> >
> > Hi,
> >
> > I just can't compile my vdr. I applied the following patches to vanilla
> > vdr-1.7.1:
> >
> > - vdr-1.7.1_extensions.diff
> > - vdr-1.7.1-ext_h264.diff
> > - vdr-1.7.1-s2api-ext64.patch
> > - fix-s2api-dvbs-tuning.patch
> >
> > Everything worked fine until here. Now I downloaded and installed S2API
> > (from http://linuxtv.org/hg/~stoth/s2-mfe right?).
> >
> > After setting the paths etc in teh make configs I tried to compile vdr,
> > but this is what happens then:
> >
> > root at HTPC:/usr/local/src/vdr-1.7.1# make
> > g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -c
> > -DUSE_CMDRECCMDI18N -DUSE_CMDSUBMENU -DUSE_CUTTIME -DUSE_DDEPGENTRY
> > -DUSE_DOLBYINREC -DUSE_JUMPPLAY -DUSE_LIEMIKUUTIO -DUSE_PLUGINMISSING
> > -DUSE_SETTIME -DUSE_WAREAGLEICON -DREMOTE_KBD -DVDR_USER=\"vdr\"
> > -DLIRC_DEVICE=\"/dev/lircd\" -DRCU_DEVICE=\"/dev/ttyS1\" -D_GNU_SOURCE
> > -DVIDEODIR=\"/daten/Video/vdr/video.00\"
> > -DCONFDIR=\"/daten/Video/vdr/video.00\" -DPLUGINDIR=\"./PLUGINS/lib\"
> > -DLOCDIR=\"./locale\" -DUSE_PLUGINAPI -I/usr/include/freetype2
> > -I../s2-mfe/linux/include channels.c
> > channels.c:70: error: 'NBC_QPSK' was not declared in this scope
> > channels.c:71: error: '_8PSK' was not declared in this scope
> > channels.c:72: error: '_16APSK' was not declared in this scope
> > channels.c: In member function 'void
> > cChannel::SetLinkChannels(cLinkChannels*)':
> > channels.c:690: warning: format not a string literal and no format
> > arguments
> > make: *** [channels.o] Fehler 1
> >
> >
> > Any ideas?
> >
> > Regards
> > Martin Schlosser
Oct 15 00:39:49 HTPC vdr: [10244] cTimeMs: using monotonic clock (resolution is 
1 ns)
Oct 15 00:39:49 HTPC vdr: [10244] VDR version 1.7.1 started
Oct 15 00:39:49 HTPC vdr: [10244] codeset is 'UTF-8' - known
Oct 15 00:39:49 HTPC vdr: [10244] found 23 locales in /usr/local/share/locale
Oct 15 00:39:49 HTPC vdr: [10244] loading plugin: 
/var/lib/vdr/plugins//libvdr-femon.so.1.7.0
Oct 15 00:39:49 HTPC vdr: [10244] loading plugin: 
/var/lib/vdr/plugins//libvdr-xineliboutput.so.1.7.0
Oct 15 00:39:49 HTPC vdr: [10244] loading plugin: 
/var/lib/vdr/plugins//libvdr-remote.so.1.7.0
Oct 15 00:39:49 HTPC vdr: [10244] loading /etc/vdr//setup.conf
Oct 15 00:39:49 HTPC vdr: [10244] loading /etc/vdr//sources.conf
Oct 15 00:39:49 HTPC vdr: [10244] loading /etc/vdr//diseqc.conf
Oct 15 00:39:49 HTPC vdr: [10244] loading /etc/vdr//channels.conf
Oct 15 00:39:49 HTPC vdr: [10244] loading /etc/vdr//timers.conf
Oct 15 00:39:49 HTPC vdr: [10244] Failed to load translated 
'/etc/vdr//commands.conf.' for language ()
Oct 15 00:39:49 HTPC vdr: [10244] Falling back to default 
'/etc/vdr//commands.conf' (if any)
Oct 15 00:39:49 HTPC vdr: [10244] Failed to load translated 
'/etc/vdr//reccmds.conf.' for language ()
Oct 15 00:39:49 HTPC vdr: [10244] Falling back to default 
'/etc/vdr//reccmds.conf' (if any)
Oct 15 00:39:49 HTPC vdr: [10244] loading /etc/vdr//svdrphosts.conf
Oct 15 00:39:49 HTPC vdr: [10244] loading /etc/vdr//remote.conf
Oct 15 00:39:49 HTPC vdr: [10244] loading /etc/vdr//keymacros.conf
Oct 15 00:39:49 HTPC vdr: [10245] video directory scanner thread started 
(pid=10244, tid=10245)
Oct 15 00:39:49 HTPC vdr: [10245] video directory scanner thread ended 
(pid=10244, tid=10245)
Oct 15 00:39:49 HTPC vdr: [10246] video directory scanner thread started 
(pid=10244, tid=10246)
Oct 15 00:39:49 HTPC vdr: [10246] video directory scanner thread ended 
(pid=10244, tid=10246)
Oct 15 00:39:49 HTPC vdr: [10244] reading EPG data from /etc/vdr/epg.data
Oct 15 00:39:50 HTPC vdr: [10244] probing /dev/dvb/adapter0/frontend0
Oct 15 00:39:50 HTPC vdr: [10244] device 1 provides: DVBS2
Oct 15 00:39:50 HTPC vdr: [10244] device 1 forced to frontendType SYS_DVBS2 
O

[vdr] [PATCH] S2API for vdr-1.7.1 vanilla and extensions patch 64 ( 071020008 )

[Martin Schlosser]

 > Hi All,
 >
 > this patches are for Steve Toth's repository at :
 > http://linuxtv.org/hg/~stoth/s2/ .
 > In theory they should work. I did them offline from my VDR.
 >
 > cu
 >
 > Edgar (gimli) Hucek

Hi,

I just can't compile my vdr. I applied the following patches to vanilla 
vdr-1.7.1:

- vdr-1.7.1_extensions.diff
- vdr-1.7.1-ext_h264.diff
- vdr-1.7.1-s2api-ext64.patch
- fix-s2api-dvbs-tuning.patch

Everything worked fine until here. Now I downloaded and installed S2API 
(from http://linuxtv.org/hg/~stoth/s2-mfe right?).

After setting the paths etc in teh make configs I tried to compile vdr, 
but this is what happens then:

[EMAIL PROTECTED]:/usr/local/src/vdr-1.7.1# make
g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -c 
-DUSE_CMDRECCMDI18N -DUSE_CMDSUBMENU -DUSE_CUTTIME -DUSE_DDEPGENTRY 
-DUSE_DOLBYINREC -DUSE_JUMPPLAY -DUSE_LIEMIKUUTIO -DUSE_PLUGINMISSING 
-DUSE_SETTIME -DUSE_WAREAGLEICON -DREMOTE_KBD -DVDR_USER=\"vdr\" 
-DLIRC_DEVICE=\"/dev/lircd\" -DRCU_DEVICE=\"/dev/ttyS1\" -D_GNU_SOURCE 
-DVIDEODIR=\"/daten/Video/vdr/video.00\" 
-DCONFDIR=\"/daten/Video/vdr/video.00\" -DPLUGINDIR=\"./PLUGINS/lib\" 
-DLOCDIR=\"./locale\" -DUSE_PLUGINAPI -I/usr/include/freetype2 
-I../s2-mfe/linux/include channels.c
channels.c:70: error: 'NBC_QPSK' was not declared in this scope
channels.c:71: error: '_8PSK' was not declared in this scope
channels.c:72: error: '_16APSK' was not declared in this scope
channels.c: In member function 'void 
cChannel::SetLinkChannels(cLinkChannels*)':
channels.c:690: warning: format not a string literal and no format arguments
make: *** [channels.o] Fehler 1


Any ideas?

Regards
Martin Schlosser

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] [ANNOUNCE] pvrinput-2008-10-04

[Martin Dauskardt]

The pvrinput plugin uses a Hauppauge PVR card as an input device. All cards
supported by the ivtv or pvrusb2 driver should work. (Tested with PVR150, 
PVR250, PVR350, PVR500, PVRUSB2).

Winfried Koehler and I work on this plugin since the original maintainer 
stopped development in 2006. As far as I remember, our new versions were 
always only announced in the german vdrportal forum. So we think it is time 
to keep the non-german-speaking vdr users informed.

Look into the HISTORY for changes and into the README for further details.

http://drseltsam.device.name/vdr/pvr/src/pvrinput/vdr-pvrinput-2008-10-04.tgz

mirror:
http://wirbel.htpc-forum.de/unofficial_stuff/vdr-pvrinput-2008-10-04.tgz

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] [ANNOUNCE] pvr350-2008-09-07

[Martin Dauskardt]

Today I announced this version in the german vdrportal forum.  The last time I 
announced a new pvr350 plugin-version here in the ML was June 2007. So it is 
time to write here again to keep the non-german-speaking users informed.

The pvr350-plugin implements an output device for the PVR350 TV out, using the 
hardware mpeg2 decoder.

http://drseltsam.device.name/vdr/pvr/src/pvr350/vdr-pvr350-2008-09-07.tgz

Look into the HISTORY for the many changes since June 2007.

Attention: The plugin does not work properly with vdr 1.7.1: 
vdr now simply strips the TS headers and sends the payload to the usual 
PlayVideo() and PlayAudio() functions. The PES packets have no longer a size 
of 2kB, and the PES audio ID is always 0. The pvr350 hardware decoder and/or 
the ivtv driver cannot handle this. We would need a lot of additional code - 
time will see ...

Note:
For watching analogue TV from the tuner of the PVR350 you need a second plugin 
as input device. This is pvrinput, and as there is also a new version, I will 
announce it in a separate mail.

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Problem with v1.6.0 and two DBS-S cards

[Martin Dauskardt]

> From: "Stefan-W. Hahn" <[EMAIL PROTECTED]>

> I'm running two DVB-S cards (Nexus FF and Nova). The update was
> without any problem.
> When recording on one program I can view at the same time just the
> channels of the same bouquet but no other ones (two cards!!).  But
> recording simultaniously on two different bouquets works.
> 
> With v1.4.1 there was no problem in recording one channel and
> switching to all other channels.
> 
> I didn't find any hint on the mailinglist or vdr-portal about this
> problem. Is there any other having the same problem?
> 
> Are there any hints how to solve this problem?
Did you also update the driver/kernel? Is it a Nova SE with s5h1420 Frontend?
check with dmesg if both cards are initialized

There is a bug in the driver which was fixed a few days ago (still not in the 
man v4l-dvb hg):
http://linuxtv.org/hg/~pb/v4l-dvb/rev/cd7eae82baf9
http://linuxtv.org/hg/~pb/v4l-dvb/rev/84530ecadf89


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] OT: Deinterlacing algorithms [WAS:Re: [PATCH] RGB/PAL over VGA at variable frame rate]

[Martin Emrich]

Hi!

Morfsta schrieb:

> Have you tried changing the audio.synchronization.av_sync_method in
> xine-config to be resample instead of metranom?

Hmm, I didn't know there was such an option... I especially have these
problems with AC3 audio, and these cannot easily be resampled.

I have a cheap ASRock board in my media PC, and an SB Live 5.1 value
sound card that gave me quite some problems to set it up correctly, one
of these two is probably responsible for the problems.

In the last media PC before this one, I had an Asus board with onboard
digital out, and with this I didn't have that much problems (but the old
nVidia AGP card was not capable to run at 1920x1080 smoothly).

Ciao

Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] OT: Deinterlacing algorithms [WAS:Re: [PATCH] RGB/PAL over VGA at variable frame rate]

[Martin Emrich]

Hi!

Torgeir Veimo schrieb:
> On 23 Jul 2008, at 23:06, Martin Emrich wrote:
> 
>>  (I wonder why there's no simple "TV simulator" that upmixes 50  
>> fields/s to 50 frames/s just like a CRT TV?).
> 
> 
> It's very hard to simulate this 'upmix'. A CRT TV actually moves the  
> electron beam across the screen and the phosphor has some time it  
> stays illuminated after being hit by the beam. This is very hard to  
> simulate with a digital screen which is either on or off, or has some  
> slowness by itself which is different from how a CRT screen works.

I did not mean to actually simulate the brightness decay in the
phosphors, just the points in time where the fields are presented.

Let's assume we have two frames to be played back, which each consists
of two fields:  {1,2} and {3,4}.

I don't know if it actually works this way, but as far as I know,
playing back interlaced content with 25 frames/s on a progressive
display looks this way:

1  3
2  ...1/25th sec. later:   4
1  3
2  4

As field 3 is a 1/50th second "older" than field 4, there are jaggies in
moving scenes.

What I am looking for would be this, with 50 frames/s:

1 13  3
.  1/50th s.  2  1/50s 2  4
1 13  3
. 22  4

So each field ist still being shown for a 1/25th of a second, but for
the "right" 1/25th second. The output then no longer serves 25fps but
50fps to XVideo, DirectFB or whatever.

All of this of course makes only sense for PAL content when the TV can
do 50Hz, not 60Hz.

> The dscaler project has implemented some of the best deinterlacing  
> algorithms and most of the tvtime algorithms are implemented (to my  
> knowledge) with basis in dscaler source / ideas. See http:// 
> dscaler.org/ . dscaler basically is a deinterlace and display program  
> that takes input from bt8x8 based capture cards.

I assume these are the "tvtime" deinterlacers in the libxineoutput
plugin. I played around with them, but none of them resultet in a
picture as sharp and contrasty as without any deinterlacer. So I have to
choose between sharpness and clean motions. And even during the EURO
2008, I chose the first.

> Someone on that project had an idea to create a setup where the  
> display hardware was synced to the input clock of the capture card,  
> but I'm not sure if anything ever came out of that idea.

I also thought of that. One then would have to sync to the soundcard's
buffer, too, and remove/duplicate samples as necessary, to keep the
audio synchronized.

BTW: How does libxineoutput synchronize? I noticed a slight AV desync
growing over ca. 5 minutes, the the audio jumps once and the desync
jumps into the right position (Digital output to AV receiver).

Ciao

Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [PATCH] RGB/PAL over VGA at variable frame rate

[Martin Emrich]

Hi!

Thomas Hilber schrieb:
> On Wed, Jul 23, 2008 at 12:12:46AM +0200, Martin Emrich wrote:
>> I have connected my VDR box to my TV via a DVI-to-HDMI cable, set the
>> resolution to 1920x1080 and let the graphics card do the upscaling
>> instead of the TV, because the quality looks IMHO better this way. But
> 
> ok. But if doing so you still have to continue deinterlacing in
> software. This is because any scaling in Y dimension intermixes even/odd
> fields in the frame buffer. Finally producing a totally messed VGA output 
> signal.

Of course. As I also use other applications on the box (mplayer, photo
viewing), neither reducing the resolution nor enabling interlacing
(1080i) is desired.

Software deinterlacing is no problem, from time to time I experiment
with all the interlacer options. (I wonder why there's no simple "TV
simulator" that upmixes 50 fields/s to 50 frames/s just like a CRT TV?).

> right. Even if you still must use software deinterlacing for some reason
> you benefit from the 'sync_fields' patch. You then can enable
> sync-to-vblank and the patch dynamically synchronizes graphics card's vblanks
> and TV signal's field updates. Thus avoiding unsteady frame rates at
> VGA/DVI/HDMI output.

Ok. I'm really busy currently (but your project looked so cool that I
just *had* to write an email to the list), but as soon as I get to it,
I'll try to make it work.

Does anyone have a [EMAIL PROTECTED] modeline ready? Currently, I use the
settings provided by the TV via EDID, and I guess it defaults to 60Hz :(

>> I wonder if your patch could be applied to a DVI/HDMI connection, too?
>> Its a Radeon X850 currently with xf86-video-ati 6.6.3 and xorg-server 1.4.
> 
> In your case the only prerequisite is support of your Radeon X850 by Radeon 
> DRM driver. DRM normally is shipped with kernel. So this is a kernel/driver
> issue. But I don't expect problems here though I not yet testet the 
> X850 myself (yet).

As the box runs a home-built netboot mini distro, I am quite flexible
regarding kernel versions. As soon as I have some spare time (probably
after I finished my BA thesis :(, I get to it...

Ciao

Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [PATCH] RGB/PAL over VGA at variable frame rate

[Martin Emrich]

Hi!

First thing: A great idea!

Thomas Hilber schrieb:

> not to forget interlaced formats are still in effect for HDTV. I think
> you could recycle the basic idea behind my patch for HDTV as well.

I have connected my VDR box to my TV via a DVI-to-HDMI cable, set the
resolution to 1920x1080 and let the graphics card do the upscaling
instead of the TV, because the quality looks IMHO better this way. But
here still the same problem is present, the refresh rate of the graphics
card is not bound to the field rate of the incoming TV signal, so I can
either disable sync-to-vblank and have tearing artefacts or enable it
and have an unsteady framerate.

I wonder if your patch could be applied to a DVI/HDMI connection, too?
Its a Radeon X850 currently with xf86-video-ati 6.6.3 and xorg-server 1.4.

Ciao

Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Which DVB-S Card to buy in Germany

[Martin Emrich]

Hi!

Matthias Fechner schrieb:
> Hi,
> 
> I have here an old VDR system running and my DVB-S cards are stopping to 
> work now (VDR 1.6 and 2xDVB-S cards).
> It starts with a lot of distortions and then they stops to record 
> completely. I have only 0 minute records for my new timers.
> 
> In the log file I have:
> Jul  6 14:25:24 video vdr: [10063] ERROR: video data stream broken
> Jul  6 14:25:31 video vdr: [19846] ERROR: video data stream broken
> Jul  6 14:25:55 video vdr: [10063] ERROR: video data stream broken
> Jul  6 14:26:02 video vdr: [19846] ERROR: video data stream broken
> Jul  6 14:26:26 video vdr: [10063] ERROR: video data stream broken
> 
> If VDR records on the second DVB card everything is fine.
> 
> I'm quite sure that this a hardware issue.

Looks that way. With this hot weather in Germany at the moment: maybe
the cards just get too hot?

Ciao

Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] new videocard from ATI with hardware decoding of HD video -UVD2

[Martin Emrich]

Timothy D. Lenz schrieb:
> ATI is not known for good driver support in Linux

You should really take look what has happened in this direction
recently. They release a new AMD Catalyst (fglrx) driver every month,
and it gets better and better, while more and more specs are released to
FLOSS driver hackers (ati, radeonhd), too.

Ciao

Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] False timer conflict

[Martin Emrich]

Hi!

Christian Wieninger schrieb:
> I think this is just a matter of interpretation. EPGSearch checks if a 
> timer will receive an appropriate device for its complete recording 
> time. If there is none, it will report a timer conflict. Perhaps it 
> would be better to report a 'timer problem' because of constellations as 
> in your case, where it will never get such a device.

Yes, that's what I wanted to point out.

> Checking if there's a possible decryption at all should be feasible, but 
> wouldn't it be better to remove channels that can't be viewed of 
> recorded anyway, or adjust the search timer to the appropriate channels?

I temporarily enabled the search for new channels because some german
channels lately switched their transponder, so between the channel scan
and the next run of the decruft plugin these channels snuck in.

Ciao

Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] False timer conflict

[Martin Emrich]

Hi!

I saw these in my syslog:

Jun  7 10:12:01 sauron vdr: [5433] info: 1 timer conflict(s)! First at
11.06 00:19. Show them?
Jun  7 10:42:00 sauron vdr: [5433] info: 1 timer conflict(s)! First at
11.06 00:19. Show them?

At the time this recording is scheduled, only one of my two cards would
be in use. The recording was scheduled by EPGSearch on an encrypted
channel, where I don't have a smartcard/CAM/whatever for. I'll therefore
delete the timer entry, but maybe the error message could say something
like "timer on an encrypted channel, but no decryption possible" or so
to clarify things.

Ciao

Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] transponder hopping made easy?

[Martin Emrich]

Hi!

Carsten Koch schrieb:

> One feature that I have been missing for years in that area is:
> VDR should not add a channel to a list before it can actually
> receive at least audio from it. My "new channels" list is
> cluttered with a majority of channels that are not useful to me.
> 
> Some are useless because they require a CAM that I do not have.
> Some are useless because they broadcast in a language that I
> do not understand.
> Some are useless because they show still pictures of scantily clad
> females and command me to call 900 numbers

For this purpose, I have the decruft plugin (You can have some kind of a
"Spam list" with regular expressions for channes you don't want) and the
autosort plugin (Can sort the channels based on custom rules).

Sadly, the autosort plugin is not maintained for some time now, and
won't longer work with VDR 1.6.0.

http://www.vdr-wiki.de/wiki/index.php/Autosort-plugin
http://www.vdr-wiki.de/wiki/index.php/Decruft-plugin
(both in German)

Ciao

Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Controlling VDR with Asterisk PABX

[Martin Emrich]

Hi!

Mike Parker schrieb:

> The solution was to use my PABX (Asterisk), which runs on the VDR server.

Nice idea :)
I let my VDR show me the number of incoming calls:

extensions.conf:

 exten => number,1,agi(call.sh|${CALLERID})

call.sh:
-
#!/bin/sh

NUMBER="$1"

if [ "$NUMBER" = "" ]; then
NUMBER="Unknown Caller"
fi

vdrhost=your_vdr_hostname
echo -e "mesg Anruf von: ${NUMMER}\nquit\n" | /bin/nc $vdrhost 2001 \
2>/dev/null >/dev/null &


(SVDR must be allowed from the PBX host)

Ciao

Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] new graphics processor from VIA S3 for HD video

[Martin Emrich]

Hi!

Igor schrieb:

> there's VAAPI - Video Decode Acceleration API Specification
> http://www.freedesktop.org/wiki/Software/vaapi
> 
> but seems it hasn't finished yet :(

But the Idea sounds quite nice... I dream of a VDR box with an S3
graphics card, decoding full HD DVB-S2 with only free software at low
power consumption ;-)

Ciao

Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] new graphics processor from VIA S3 for HD video

[Martin Emrich]

Hi!

Theunis Potgieter schrieb:

> So it appears there is no hope for my old machine with an AGP port, and
> nvidia G-Force 4 MMX 440. 

I sit in a similar board (GF3 / GF2MX).

> Looks like I will have to upgrade, but the craze
> will have to settle first before I buy anything. I wonder why they don't
> create add-on cards in PCI format? so that it will work on older machines? I
> guess they want you to upgrade to keep on making money...

I don't think a simple PCI card can handle the bandwidth. Think Full-HD
PAL Video:

1920*1080*3 Byte/Pixel (RGB) * 25 FPS = 148MiB/s uncompressed RGB Data
(For performance reasons one probably would even use 32bit/Pixel). The
"classic" PCI Bus only does 133MB/s.

> Isn't there a method to use OpenGL to assist HD decoding?

AFAIK most of the current accelerators (AMD AVIVO, nVidia PureVideo,...)
use the programmable shaders for decoding, scaling, colorspace
translation, etc.
Most of the newer AMD/ATI cards seem not to have a "traditional" backend
scaler anymore (making it hard for opensource driver devs to implement
XVideo as they now have to touch the 3D engine).

Ciao

Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] new graphics processor from VIA S3 for HD video

[Martin Emrich]

Hi!

Udo Richter schrieb:

> There's a lot going on in the hardware accelerated HDTV area lately. 
> Beside the two big graphic chipsets, there's the Intel Atom/Poulsbo 
> chipset offering full HDTV acceleration at low power, the Intel G45 
> chipset, the AMD 780G chipset, and a cooperation of NVidia and VIA for a 
> new unnamed HD capable low cost chipset.
> 
> The question is: Which of them will offer decent open source drivers for 
> HD decoding, and when?

I wonder if every vendor pushes his own API for using these decoding
accelerators? Or is there some "standard" (It's surely beyond XvMC)?

Matrix-multiplying (AMD,Nvidia,S3,Intel) with (Linux, X.Org,
Mplayer/ffmpeg, Gstreamer,...) gives surely a lot of (duplicate) code.


Ciao

Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] How to change font data?

[Martin Prochnow]

>>>>> Is it possible to change font data directly in code or do I have to
>>>>> create my own true type font containing the icons?
>>>
>>> the best aproach IMHO would be an API in VDR that allows you to "nail"
>>> custom glyphs into the glyph cache. though this could lead to problems
>>> if multiple plugins overwrite the same codepoints in the cache. using a
>>> custom font would work too but you would force every user of your
>>> plugin to use that font. making a ttf font is no fun either. maybe
>>> there should be some way to mix cOsd::Bitmap with normal text?
>>
>> Messing with the fonts is not a good idea, IMHO.
>
> It works for VDR 1.4.x ;-)
>
>> I'll see about a method to add icons to the menu items.
>> However, this has veeery low priority ;-)
>
> So my only option for now is a true type font containing the icons. Or
> maybe to create a skin plugin that can displays the icons.
>
At the moment I try to solve the hole issue by using a true type font
containing the icons. There was done some work at vdr-portal.de (thanks
folks ;) )

But there comes the next problem. Until now, I use the space between 0x80
and 0x9f, which is marked as unused for ISO8859. But this does not work
for UTF-8. Amair from vdr-portal.de suggests to use the position after
0xe000 for this case. So I need two different fonts and I have to check,
if VDR is running in an UTF-8 environment and set the values for the icons
accordingly.

This hole TTF and UTF-8 crap makes the handling of the icons very
complicated. Maybe it is the best for now to replace the icons with normal
letters until VDR provides support icons. I don't want to dictate the
users what font they have to use.

Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] How to change font data?

[Martin Prochnow]

>>>> Is it possible to change font data directly in code or do I have to
>>>> create my own true type font containing the icons?
>>
>> the best aproach IMHO would be an API in VDR that allows you to "nail"
>> custom glyphs into the glyph cache. though this could lead to problems
>> if multiple plugins overwrite the same codepoints in the cache. using a
>> custom font would work too but you would force every user of your
>> plugin to use that font. making a ttf font is no fun either. maybe
>> there should be some way to mix cOsd::Bitmap with normal text?
>
> Messing with the fonts is not a good idea, IMHO.

It works for VDR 1.4.x ;-)

> I'll see about a method to add icons to the menu items.
> However, this has veeery low priority ;-)

So my only option for now is a true type font containing the icons. Or
maybe to create a skin plugin that can displays the icons.

Martin


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] How to change font data?

[Martin Prochnow]

Nobody there who can help me?

> Hi,
>
> My ExtRecMenu-plugin (and even my Nordlicht's EPG-plugin) uses a function
> to add icons to the used fonts. It changes some of the unused signs (
> between 0x80 and 0x9f) by directly changing their data.
>
> Since VDR introduced true type fonts, this function doesn't work anymore.
> I tried to understand how to use CreateFont from the class cFont to do the
> same with newer VDR versions but I failed.
>
> Is it possible to change font data directly in code or do I have to create
> my own true type font containing the icons?
>
> Regards,
> Martin


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] How to change font data?

[Martin Prochnow]

Hi,

My ExtRecMenu-plugin (and even my Nordlicht's EPG-plugin) uses a function
to add icons to the used fonts. It changes some of the unused signs (
between 0x80 and 0x9f) by directly changing their data.

Since VDR introduced true type fonts, this function doesn't work anymore.
I tried to understand how to use CreateFont from the class cFont to do the
same with newer VDR versions but I failed.

Is it possible to change font data directly in code or do I have to create
my own true type font containing the icons?

Regards,
Martin


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] wrong time in tv program

[Martin SCHREIBER]

h! damn it:

xtruder:/etc# cat timezone 
Europe/Berlin
xtruder:/etc# date -R
Sat, 09 Feb 2008 11:40:52 -0600

i thought that the timezone is automatically updated from the
file /etc/timezone on every boot.

here's the solution on debian:

xtruder:/etc# date -R
Sat, 09 Feb 2008 05:01:30 -0600
xtruder:/etc# export TZ=Europe/Berlin 
xtruder:/etc# hwclock --hctosys
xtruder:/etc# date -R
Sat, 09 Feb 2008 19:02:03 +0100
xtruder:/etc# date -s 12:03 -R
Sat, 09 Feb 2008 12:03:00 +0100

--
so thanx for your help and or course for developing vdr! :-)

martin


On Sat, 2008-02-09 at 11:34 +0100, Klaus Schmidinger wrote:
> On 02/03/08 19:04, Martin SCHREIBER wrote:
> > On Fri, 2008-02-01 at 16:32 +0100, Klaus Schmidinger wrote:
> >> On 01/29/08 20:16, Martin SCHREIBER wrote:
> >>> hello!
> >>>
> >>> the time in the vdr (right bottom) is displayed correctly but the time
> >>> for the tv movies are displayed with a 7 hour displacement.
> >>>
> >>> e.g. the local time is 20:11 but the start time of the tv movie is
> >>> displayed as 13:00. but the correct tv movie name is displayed.
> >>>
> >>> 'date' in the shell displays the correct time and also the correct
> >>> timezone is set up in /etc/timezone as 'Europe/Berlin'.
> >> Is this happening only on a particular channel or on all channels?
> > 
> > this happens on all channels
> > 
> >> Do you use the EPG data that comes from the broadcasters, or from
> >> some other source?
> > 
> > as far as i know i just use the epg data from the broadcasters (dvb-s)
> > i used the default settings on from the debian distribution.
> > 
> > i also uploaded a screenshot:
> > http://www.fs.tum.de/~schreibm/private/vdradmin.pl.jpeg
> > 
> > another thing is that the correct program schedule is displayed for the
> > first second and then it switches to the wrong one. but this only
> > happens once for each tv station after a few minutes or hours.
> 
> Are you sure you have the correct time zone setting on your machine?
> 
> Klaus
> 
> ___
> vdr mailing list
> vdr@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
-- 
Martin Schreiber

http://www.martin-schreiber.net

| Im Muehltal 48
| 91171 Greding
| GERMANY


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] wrong time in tv program

[Martin SCHREIBER]

On Fri, 2008-02-01 at 16:32 +0100, Klaus Schmidinger wrote:
> On 01/29/08 20:16, Martin SCHREIBER wrote:
> > hello!
> > 
> > the time in the vdr (right bottom) is displayed correctly but the time
> > for the tv movies are displayed with a 7 hour displacement.
> > 
> > e.g. the local time is 20:11 but the start time of the tv movie is
> > displayed as 13:00. but the correct tv movie name is displayed.
> > 
> > 'date' in the shell displays the correct time and also the correct
> > timezone is set up in /etc/timezone as 'Europe/Berlin'.
> 
> Is this happening only on a particular channel or on all channels?

this happens on all channels

> Do you use the EPG data that comes from the broadcasters, or from
> some other source?

as far as i know i just use the epg data from the broadcasters (dvb-s)
i used the default settings on from the debian distribution.

i also uploaded a screenshot:
http://www.fs.tum.de/~schreibm/private/vdradmin.pl.jpeg

another thing is that the correct program schedule is displayed for the
first second and then it switches to the wrong one. but this only
happens once for each tv station after a few minutes or hours.

ciao,
  martin


> Klaus
> 
> _______
> vdr mailing list
> vdr@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
-- 
Martin Schreiber

http://www.martin-schreiber.net

| Im Muehltal 48
| 91171 Greding
| GERMANY



___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

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

[Martin Binder (AON)]

Hi Klaus,
my opinion: the next stable version should contain DVB-S2/H.264 (HDTV) 
support. So there is no use for a stable version based on 1.5.14.

Kind regards
Martin

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
> Of Klaus Schmidinger
> Sent: Sunday, February 03, 2008 11:17 AM
> To: vdr@linuxtv.org
> Subject: [vdr] Straw poll: stable version 1.6.0 now?
>
> There has been some controversy about my recent decision to
> move forward and require the "multiproto" driver for VDR in
> the developer version. It is also currently rather unclear
> whether the current PES recording format can be kept to handle
> HDTV, or whether it would make sense (or even be feasible)
> to switch to TS (as suggested by the people from RMM).
>
> In order to take the edge of this, I was wondering if it would
> make sense to revoke the switch to the "multiproto" driver and
> go straight towards a stable version 1.6.0 with what is now in
> version 1.5.14. This should satisfy all those who are eagerly awaiting
> a new stable version, without forcing them to make the driver switch
> now.
>
> If we decide to go that way, I would release a version 1.5.15 with
> what could become the new stable, wait until like the end of the month
> to see whether it still needs some minor fixes, and call it 1.6.0 then.
> I know there are still some patches out there that some would expect
> to go into the next stable version, but I actually want to prepare VDR
> for HDTV before looking into these patches.
>
> So, here's the straw poll:
>
>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?
>
> Yes or No?
>
> Klaus
>
>
>
> ___
> vdr mailing list
> vdr@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr



___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Transfer-Mode without remux

[Martin Dauskardt]

Hi Klaus,

sending TS payload data directly to the device shouldn`t become a generally 
method. Please be aware that there are other output devices which can`t 
handle TS data. For example, the decoder of the PVR350 needs a multiplexed 
Audio/Video PES.

Greets,
Martin

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] wrong time in tv program

[Martin SCHREIBER]

hello!

the time in the vdr (right bottom) is displayed correctly but the time
for the tv movies are displayed with a 7 hour displacement.

e.g. the local time is 20:11 but the start time of the tv movie is
displayed as 13:00. but the correct tv movie name is displayed.

'date' in the shell displays the correct time and also the correct
timezone is set up in /etc/timezone as 'Europe/Berlin'.

has anyone a solution?

thx,
  martin


-- 
Martin Schreiber

http://www.martin-schreiber.net

| Im Muehltal 48
| 91171 Greding
| GERMANY


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr