[vdr] Howto set dvb capability in vdr

2009-04-30 Thread Mr. Tux

My dvb-t usb device (TwinhanDTV USB-Ter USB1.1 / Magic Box I / HAMA USB1.1) 
works well with vdr 1.6.0-2,
but it can't handle more than one channel at once properly. If I record a 
channel and tune to a second channel
on the same frequency, this will cause artefacts in the recording or in live 
display of the second channel.

How do I change vdr detection of this device, so vdr knows it can only 
replay/record one channel at once? Is there a patch
available already? Vdr should change to the recording channel and lock it 
during the recording (usefull if someone tries
to switch channel by mistake).

I do have others dvb device installed in my vdr system - whatever changes I 
apply should not affect them.

Thanks and greetings

Mr Tux

_
http://redirect.gimas.net/?n=M0904xIE8_MSN4
Internet Explorer 8 jetzt für MSN  - kostenlos!___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


[vdr] howto change time of epg grap?

2009-06-08 Thread Mr. Tux

hello

>From what I observe vdr is waiting to grap the epg content of a 
timed recording until this recording starts. There are a bunch of channels
where this leads to unwelcome side effects:

- Take a channel that is using place holder events in the "now" section
of epg during commerical breaks between two events.
- Take a channel that is broadcasting only one status signal, timed
to the ending of each event. So you have the whole comerical break
recorded as well.

Vdr will start the recording with the status signal - this one bumps right into 
the
beginning of the placeholder event. Thus the epg data vdr grabs is from the 
placeholder
event, thus it is empty.

I know it is the broadcasters fault, not vdr - I assume broadcasters using 
digital vps
should *never* switch now/next epg events before the next event is indeed 
running.
They sure can use place holder events between two scheduled events, but if they 
decide
to do so, they should wait switching now/next event until the next event starts.

If my broadcaster only could stick to this rule of thumb, there couldn't be a 
problem, sadly he
never does.

What can I do?

I'd like vdr to wait a few minutes until he grabs epg data - or vdr could grab 
the epg data right
away when I add the timer. Both ways sould be working.




_
http://redirect.gimas.net/?n=M0906xWLM2009
Neu: Messenger 2009! Hier kostenlos downloaden!___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


[vdr] vdr Digest, Vol 53, Issue 17

2009-06-13 Thread Mr. Tux
What if the broadcaster does not send RST signal 2? I never see
any other status signal in syslog than status 4 with this broadcaster.

> Message: 7
> Date: Sat, 13 Jun 2009 11:47:59 +0200
> From: Klaus Schmidinger 
> Subject: Re: [vdr] howto change time of epg grap?
>
> If a channel is recorded using "VPS" (which is implemented by using the
> PDC descriptors), a particular event has its official broadcast time
> encoded in the PDC descriptor, and that's how VDR assigns an event to
> the timer. Whatever that event's data is at the time the recording starts
> (which happens when the "running status" of the event goes to 2) will be
> stored as the recording's info.
> I don't see how "waiting a few minutes" would do any good here.
>
> Klaus


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


Re: [vdr] vdr-sxfe cvs version segfault with vdr 1.7.8

2009-07-30 Thread Mr. Tux
Hello Mika

>
> Closing of vdr-sxfe (by mouse clicking the close icon in dialog title bar)
> has some problem. It will stop displaying the the video-stream but will
> not close the vdr-sxfe dialog itself. To close the app, I need to use
> "killall -9 vdr-sxfe". "killall vdr-sxfe" without -9 will not work.
>

This is bugging me as well with the same software setup - if you "killall-it" 
*TWICE* you won't need SIGKILL to close the empty window.

I changed my sxfe script to get along with this at the moment:

--

#!/bin/bash
sxfe_start="/usr/bin/vdr-sxfe --hotkeys --daemon --silent --video=xv --
audio=alsa:hw:1,3 xvdr://localhost"

if [ "$(pidof vdr-sxfe)" ]; then
while [ "$(pidof vdr-sxfe)" ]; do
killall -q -e vdr-sxfe
sleep 1
done
else$sxfe_start

--

Usually the while loop runs twice and the sxfe window closes with SIGTERM.

Greetings

Mr. Tux

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


Re: [vdr] ttxtsubs patch for vdr-1.7.10

2009-11-27 Thread Mr. Tux
Hi Magnus

Thanks  for the patch - runs like a charm :-)

bye

Mr Tux

>
>
>
> --
>
> Message: 9
> Date: Sun, 22 Nov 2009 16:59:28 +0100
> From: Magnus H?rlin 
> Subject: [vdr] ttxtsubs patch for vdr-1.7.10
> To: VDR Mailing List 
> Message-ID: <4b095fe0.3040...@alefors.se>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
> Hi, just thought I'd post an unofficial ttxtsubs patch for vdr-1.7.10 in
> case someone wants to use it. /Magnus H
>
>
> -- next part --
> A non-text attachment was scrubbed...
> Name: vdr-1.7.10-ttxtsubs.patch
> Type: application/mbox
> Size: 21273 bytes
> Desc: not available
> URL:
> <http://www.linuxtv.org/pipermail/vdr/attachments/20091122/a423bf35/attachm
>ent.bin>
>
> --
>
> ___
> vdr mailing list
> vdr@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
>
>
> End of vdr Digest, Vol 58, Issue 31
> ***


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


[vdr] Parental Rating Descriptor

2010-03-02 Thread Mr. Tux

Hi listI realize quite a few channels are showing some sort of parental rating 
descriptor flag - mostly the genre type of a broadcast.What I actually never 
saw within vdr is a display of "minimum age required" which would introduce an 
easy possibility to actually block a channel.Is the minimum age flag not 
displayed, do most broadcasters not send a minimum age req. flag or is the 
minimum age req. linked to the genre type?


  
_
http://redirect.gimas.net/?n=M1003xIE82
Damit Privates privat bleibt! Internet Explorer 8!
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] Remote xineliboutput crashes when scaling

2010-04-24 Thread Mr Tux
Hi Petri
Hello list

Bug #2952110 covered it for me - I had this segfault for quite a while now. I 
simply switched sw-scaling off after I didn't find a solution and no bug report 
either.

Now I recompiled with gcc 4.3 and CC=gcc-4.3 in Make.config and sw-scaling runs 
fine again :-)

@Petri; you still need this make output of xine_post_swscale.c to dig into 
this problem? I attached the whole make output of xineliboutput with gcc 4.4 
from Ubuntu/karmic 32bit repositories (gcc 4:4.4.1-1ubuntu2)

If you need more information other than what you already got from the bug 
tracker just tell me so, I'll gladly support you with more info.

@Sami: As a quick fix / workaround for this compiler related bug I recommend 
using gcc 4.3.1 from the Ubuntu repositories (aptitude install gcc-4.3)
then modify the CC line in Make.config from CC=gcc to CC=gcc-4.3

After that run make again, now you should be able to activate sw-scaling and 
use in on channels with smaller resolution than 720x576.

> Message: 2
> Date: Sat, 24 Apr 2010 11:03:49 +0300
> From: Petri Hintukainen 
> Subject: Re: [vdr] Remote xineliboutput crashes when scaling
> To: VDR Mailing List 
> Message-ID: <1272096229.2912.2147.ca...@ph-laptop>
> Content-Type: text/plain; charset="UTF-8"
> 
> Petri Hintukainen wrote:
> Maybe you're seeing the same problem as in the following bug report:
> https://sourceforge.net/tracker/?func=detail&atid=814342&aid=2952110&group_
> id=160063
>
Plugin xineliboutput:
make[1]: Betrete Verzeichnis '/usr/local/src/vdr/vdr-1.7.14/PLUGINS/src/vdr-xineliboutput'
Running configure
Checking for pkg-config ... yes
Checking for pkg-config libextractor ... yes
Checking for pkg-config libxine ... yes
Checking for xine plugin directory ... /usr/lib/xine/plugins/1.26
Checking for pkg-config libavutil ... yes
Checking for pkg-config libjpeg ... no
Checking for libjpeg ... yes
Checking for pkg-config x11 ... yes
Checking for pkg-config xext ... yes
Checking for pkg-config xshm ... no
Checking for xshm ... yes
Checking for pkg-config xrender ... yes
Checking for pkg-config xrandr ... yes
Checking for pkg-config xdpms ... no
Checking for xdpms ... yes
Checking for pkg-config xinerama ... yes
Checking for pkg-config vdpau ... no
Checking for vdpau ... yes
Checking for pkg-config dbus-glib-1 ... yes

Enabled features:
  x11
  fb
  vdr
  libxine
  libextractor
  libavutil
  libjpeg
  dbus_glib_1
  xshm
  xdpms
  xinerama
  xrandr
  xrender
  vdpau
Disabled features:

Creating features.h ...
Creating config.mak ...
make[1]: Verlasse Verzeichnis '/usr/local/src/vdr/vdr-1.7.14/PLUGINS/src/vdr-xineliboutput'
make[1]: Betrete Verzeichnis '/usr/local/src/vdr/vdr-1.7.14/PLUGINS/src/vdr-xineliboutput'
g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -fPIC -c -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"xineliboutput"' -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DXINELIBOUTPUT_VERSION='"1.0.90-cvs"' -Wall -I/usr/local/src/v4l-dvb/linux/include -I../../../include  -o xineliboutput.o xineliboutput.c
g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -fPIC -c -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"xineliboutput"' -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DXINELIBOUTPUT_VERSION='"1.0.90-cvs"' -Wall -I/usr/local/src/v4l-dvb/linux/include -I../../../include  -o device.o device.c
g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -fPIC -c -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"xineliboutput"' -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DXINELIBOUTPUT_VERSION='"1.0.90-cvs"' -Wall -I/usr/local/src/v4l-dvb/linux/include -I../../../include  -o frontend.o frontend.c
g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -fPIC -c -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"xineliboutput"' -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DXINELIBOUTPUT_VERSION='"1.0.90-cvs"' -Wall -I/usr/local/src/v4l-dvb/linux/include -I../../../include  -o osd.o osd.c
g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -fPIC -c -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"xineliboutput"' -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DXINELIBOUTPUT_VERSION='"1.0.90-cvs"' -Wall -I/usr/local/src/v4l-dvb/linux/include -I../../../include  -o config.o config.c
g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -fPIC -c -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"xineliboutput"' -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DXINELIBOUTPUT_VERSION='"1.0.90-cvs"' -Wall -I/usr/local/src/v4l-dvb/linux/include -I../../../include  -o menu.o menu.c
g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -fPIC -c -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE6

[vdr] Remote xineliboutput crashes when scaling

2010-04-24 Thread Mr Tux
Hi Sami

This I can not confirm with karmic, both autocrop and sw-scaling work inside 
the media player.

>
> Date: Sat Apr 24 17:37:44 CEST 2010
> From: Sami Sundell
> Subject: Re: [vdr] Remote xineliboutput crashes when scaling
> To: VDR Mailing List 
> Message-ID: <1272096229.2912.2147.ca...@ph-laptop>
> Content-Type: text/plain; charset="UTF-8"
> Sami Sundell wrote:
> Interestingly, though, media player still doesn't work - earlier file
> playback it crashed on swscale, now it's libavcodec. Well, at least
> I'm seeing channels. :P
>

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


[vdr] vdr-sxfe crashing all the time

2010-05-04 Thread Mr. Tux

Hello Martti

Please add the following two lines in ~./.xine/config to enable OSD with
opengl:

video.driver:opengl
video.output.opengl_renderer:2D_Tex

then restart vdr for changes to take effect



Date: Mon, 03 May 2010 17:19:31 +0300
From: Martti Kuparinen 
Subject: Re: [vdr] vdr-sxfe crashing all the time

02.05.2010 21:55, Halim Sahin kirjoitti:

Hi,
Try the opengl driver with fglrx (not xv!).


It starts but I don't see the OSD and I noticed this warning





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


[vdr] radio-0.2.5 compile error

2010-06-07 Thread Mr Tux
Hello Simon

Uwe offers a 1.7.x preversion (vdr-radio-0.9.0pre) on his webspace [1] - builds 
fine with 1.7.15

[1] http://www.egal-vdr.de/plugins/in_progress/20090905_vdr-radio-0.9.0pre.tgz


>Simon Baxter  wrote on Mon Jun 7 08:41:28 CEST 2010
>Under vdr-1.7.15 I'm getting this compile error:
>Any ideas? 





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


[vdr] Arabic language EPG is inappropriately displayed

2010-09-11 Thread Mr. Tux
This will only build vdr, no plugins, no installation into the system
It will just give you the idea if the patch still works

This is basically my setup if I test new vdr stuff (patches, upgrades, etc)

sudo aptitude install libfribidi-dev
sudo apt-get build-dep vdr

mkdir -v /usr/local/src/vdr
cd /usr/local/src/vdr

wget ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.15.tar.bz2
tar -xvjf vdr-1.7.15.tar.bz2

wget ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.0-bidi.diff.gz
gunzip -d vdr-1.7.0-bidi.diff.gz
sed 's/vdr-1.7.0.alrawab/vdr-1.7.15/g;s/vdr-1.7.0/vdr-1.7.15/g' \
vdr-1.7.15-bidi.patch
patch -b -p 0 -i vdr-1.7.15-bidi.patch

cd vdr-1.7.15/

make
make plugins

mkdir -pv $HOME/vdr-1.7.15/videos

cp -vai *.conf $HOME/vdr-1.7.15/
cp -vai runvdr.template $HOME/vdr-1.7.15/runvdr


## adjust runvdr:

nano $HOME/vdr-1.7.15/runvdr

export VDR_LANG="$LANG"
export LC_COLLATE="$LANG"
export VDR_CHARSET_OVERRIDE="ISO-8859-6"

VDRPRG="/usr/local/src/vdr/vdr-1.7.15/vdr"

VDROPTIONS="-w 60 --port=2001 --log=3 \
--localedir=/usr/local/src/vdr/vdr-1.7.15/locale/ \
--video=$HOME/vdr-1.7.15/videos --config=$HOME/vdr-1.7.15/ \
--lib=/usr/local/src/vdr/vdr-1.7.15/PLUGINS/lib"

# have a look @ syslog on a second terminal:
tail -fn100 /var/log/syslog | grep vdr

# now run vdr using the runvdr start script:
sudo sh $HOME/vdr-1.7.15/runvdr

#Replace CHANNEL with the channel you like to see
# LSTE does list EPG data of that channel

/usr/local/src/vdr/vdr-1.7.15/svdrpsend.pl -p 2001 -d localhost LSTE CHANNEL \
| grep '215-' | cut -d - -f2- | sed -s '/^e/d;/^c/d'


# stop vdr with "killall vdr" on another terminal

The patch applies/builds fine after the path adjustment, don't know if it does 
what it's supposed to without arrabic channels to test...
d

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


[vdr] vdr] Arabic language EPG is inappropriately displayed

2010-09-12 Thread Mr. Tux
Each of those packages carry the {u} marker, so they should be replaced by 
other packages, and are no longer in use.

Please do yourself a favour and backup important data anyway before you setup
a build environment.

I made some adjustments to the runvdr script:

export VDR_LANG="$LANG"
export LC_ALL="$VDR_LANG"
export LC_COLLATE="$VDR_LANG"
export VDR_CHARSET_OVERRIDE="ISO-8859-6"

VDRPRG="/usr/local/src/vdr/vdr-1.7.15/vdr"

# For other options see manpage vdr.1
VDROPTIONS="-w 60 --port=2001 --log=3 \
--config=$HOME/vdr-1.7.15/ \
--video=$HOME/vdr-1.7.15/videos \
--localedir=/usr/local/src/vdr/vdr-1.7.15/locale/ \
--lib=/usr/local/src/vdr/vdr-1.7.15/PLUGINS/lib"

VDRPLUGINS="-P xineliboutput"
# You will need to select your output device plugin if you want
# to use VDR to watch video. For instance, for a "Full Featured"
# DVB card that would be
# VDRPLUGINS="-P dvbsddevice"

VDRCMD="$VDRPRG $VDROPTIONS $VDRPLUGINS $*"

while (true); do
  eval "$VDRCMD"
  if test $? -eq 0 -o $? -eq 2; then exit; fi
  done


It makes no sense to load/unload dvb drivers right now, so let's leave those 
code passages aside, you can run it without sudo then.

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


[vdr] Arabic language EPG is inappropriately displayed

2010-09-13 Thread Mr. Tux
Monday 13 September 2010, at 12.00:02 Sami wrote:

> Did I do something wrong?
> 
> Regards
> Sami.
> 

Arr ... absolutely not, that's totally my mistake, sorry!

Please replace

VDRPLUGINS="-P xineliboutput"

with 

VDRPLUGINS=""

in $HOME/vdr-1.7.15/runvdr

I had a quick look at the Arabic menus using xineliboutput and forgot about 
that change.

The menus look fine, some text passages are not translated yet.

Try again with this setup of runvdr

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