vdr

vdr@linuxtv.org

2 participants
6731 discussions

intermittant "Channel Not Available" vdr-1.6.0
by Simon Baxter 27 Apr '10

27 Apr '10

Hi I'm running 2x DVB-C + CI/CAMS and getting intermittant channel not available messages: I'm running 2.6.27.41-170.2.117.fc10.x86_64 with a recent v4l-dvb. In the past when I've had these problems, I've been able to fix by adding some msleep(1); statements in v4l-dvb/linux/drivers/media/dvb/dvb-core/dvb_ca_en50221.c But it's still doing it. If I switch back and forth between channels and devices (using femon) I can get the channel to work on both cards/CAMs. Any ideas? Apr 27 22:06:06 freddy vdr: [11775] switching to channel 1 Apr 27 22:06:06 freddy vdr: [11775] buffer stats: 81216 (3%) used Apr 27 22:06:06 freddy vdr: [11775] info: Channel not available! Apr 27 22:06:08 freddy vdr: [11775] CAM 2: Menu ------------------ Apr 27 22:06:08 freddy vdr: [11775] CAM 2: 'AlphaCrypt' Apr 27 22:06:08 freddy vdr: [11775] CAM 2: 'You are not entitled' Apr 27 22:06:08 freddy vdr: [11775] CAM 2: 'to receive this programme !' Apr 27 22:06:08 freddy vdr: [11775] CAM 2: 'Press OK' Apr 27 22:06:17 freddy vdr: [11775] switching to channel 1 Apr 27 22:06:17 freddy vdr: [11775] info: Channel not available! Apr 27 22:06:56 freddy vdr: [11775] closing SVDRP connection Apr 27 22:07:03 freddy vdr: [11775] switching to channel 1 Apr 27 22:07:03 freddy vdr: [15407] transfer thread started (pid=11775, tid=15407) Apr 27 22:07:03 freddy vdr: [15408] receiver on device 1 thread started (pid=11775, tid=15408) Apr 27 22:07:03 freddy vdr: [15409] TS buffer on device 1 thread started (pid=11775, tid=15409) Apr 27 22:07:06 freddy vdr: [11775] switching to channel 1 Apr 27 22:07:06 freddy vdr: [15407] transfer thread ended (pid=11775, tid=15407) Apr 27 22:07:06 freddy vdr: [11775] buffer stats: 77268 (3%) used Apr 27 22:07:06 freddy vdr: [15410] transfer thread started (pid=11775, tid=15410) Apr 27 22:07:06 freddy vdr: [15409] TS buffer on device 1 thread ended (pid=11775, tid=15409) Apr 27 22:07:06 freddy vdr: [15408] buffer stats: 76892 (3%) used Apr 27 22:07:06 freddy vdr: [15408] receiver on device 1 thread ended (pid=11775, tid=15408) Apr 27 22:07:06 freddy vdr: [15411] receiver on device 1 thread started (pid=11775, tid=15411) Apr 27 22:07:06 freddy vdr: [15412] TS buffer on device 1 thread started (pid=11775, tid=15412) Apr 27 22:07:07 freddy vdr: [15410] setting audio track to 1 (0)

1 0

Re: [vdr] vdr Digest, Vol 63, Issue 32
by Martin Dauskardt 26 Apr '10

26 Apr '10

> Date: Tue, 27 Apr 2010 07:03:50 +1200 > From: "Simon Baxter" <linuxtv(a)nzbaxters.com> > 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

1 0

linux usb dvb-s card...
by martinez 26 Apr '10

26 Apr '10

Hi, Anybody could recommand a usb dvb-s card (or dvb-s2 but it is not a must) fully linux compatible (so that it works with vdr 1.7.x) Cheers, Art

2 1

any gui to make life easier with channels.conf ?
by Harald Overas 26 Apr '10

26 Apr '10

I use XXV to edit the channels.conf. It gives you a very good GUI in your web browser, and you can easy edit and sort these fields in channels.conf: Position Name Transponder frequency Signal source Various parameters, depending on signal source Symbol rate Video PID (VPID) Audio PID (APID) Teletext PID (TPID) Conditional access (CA) Service ID (SID) Network ID (NID) Transport stream ID (TID) Radio ID (RID) More information here: http://xxv.berlios.de/component/option,com_frontpage/Itemid,1/ Bye Harald

1 0

PVRINPUT plugin and "black/cinema bars"
by Simon Baxter 26 Apr '10

26 Apr '10

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. 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. Plugin setup is as follows: pvrinput.AspectRatio = 2 pvrinput.AudioBitrate = 10 pvrinput.AudioSampling = 1 pvrinput.AudioVolume = 58982 pvrinput.AudioVolumeFM = 65535 pvrinput.AudioVolumeTV = 62258 pvrinput.BackupHack = 0 pvrinput.BackupInterval = 30 pvrinput.BitrateMode = 0 pvrinput.Brightness = 128 pvrinput.Contrast = 64 pvrinput.EnableDigibox = 1 pvrinput.FastChannelChange = 1 pvrinput.FilterChromaMedianBottom = 0 pvrinput.FilterChromaMedianTop = 255 pvrinput.FilterChromaSpatialType = 0 pvrinput.FilterLumaMedianBottom = 0 pvrinput.FilterLumaMedianTop = 255 pvrinput.FilterLumaSpatialType = 0 pvrinput.FilterMedianType = 0 pvrinput.FilterSpatial = 0 pvrinput.FilterSpatialMode = 1 pvrinput.FilterTemporal = 0 pvrinput.FilterTemporalMode = 0 pvrinput.HideMainMenuEntry = 1 pvrinput.Hue = 0 pvrinput.LogLevel = 3 pvrinput.Pulldown = 0 pvrinput.Pvrusb2StopOnChange = 0 pvrinput.RedRemoteDevice = /dev/ledxmit pvrinput.Saturation = 64 pvrinput.SliceVBI = 0 pvrinput.TunerAudioMode = 4 pvrinput.UseDeviceType = 1 pvrinput.VideoBitrate = 6000 pvrinput.VideoBitrateFM = 1500 pvrinput.VideoBitrateTV = 6000 Also attached (if it comes through?) is a screenshot. Any ideas how to remove these? Thanks Simon

1 0

EPG background scan and corrupted recordings
by Jaakko Hyvätti 25 Apr '10

25 Apr '10

Hi, I tried to search but did not find this mentioned. I enabled EPG scan, and started getting garbled recordings. Looking at the recorded 00*.ts files, they contain ASCII text from EPG. Problem solved, set the background updates to 0 again. This is with 1.7.13 and 1.7.14, and two TT full DVB-C cards. I think the same happened with earlier generations of vdr, I vaguely recall disabling the background scan because of this years ago also. Regards, Jaakko

2 1

xineliboutput UDP detach from stream
by Kent Nielsen 25 Apr '10

25 Apr '10

I can't use UDP transport with vdr-sxfe after the changes to xvdr_metronom made on 2010-02-19 13:44:57 ( http://projects.vdr-developer.org/git/?p=xineliboutput.git;a=blobdiff;f=xin… ) When chaning channels there is a message "[demux_vdr] PMT changed", and thats it. Recordings can be watched and some HD channels also. With TCP it works, but unfortunately I often get screen blinking when chaning channels (the blinking doesn't go away until x is restarted). With UDP there is no screen blinking. I use xine-lib-1.2 (latest) with vdpau. It seems, that vdr-sxfe or xineliboutput think that the stream is detached? What could I do to debug or even change it? Would love to use newer xineliboutput and vdr-sxfe. Thanks in advance, Kent

1 0

Remote xineliboutput crashes when scaling
by Mr Tux 24 Apr '10

24 Apr '10

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 <vdr(a)linuxtv.org> > Message-ID: <1272096229.2912.2147.camel@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 >

1 0

Re: [vdr] Remote xineliboutput crashes when scaling
by Mr Tux 24 Apr '10

24 Apr '10

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 <phintuka(a)users.sourceforge.net> > Subject: Re: [vdr] Remote xineliboutput crashes when scaling > To: VDR Mailing List <vdr(a)linuxtv.org> > Message-ID: <1272096229.2912.2147.camel@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 >

2 1

Remote xineliboutput crashes when scaling
by Sami Sundell 24 Apr '10

24 Apr '10

Hello. Looks like this isn't strictly speaking VDR problem, since it appears to be a problem with Xine, but I'm wondering if anyone is using a similar setup in the first place and would've found a solution... To make it short, I'm using VDR bundle from e-tobi.net (1.6.0-16ctvdr2), running on 64-bit Debian Unstable. Output is done with xineliboutput plugin (1.0.6+cvs20100308.2219-1), and the image is spewed into CRT television through network using another machine - Debian Unstable, 32-bit x86. The output itself is done with xineliboutput-fbfe (1.0.6+cvs20100308.2219-1) using Matrox G450. Everything with 704x576 (and presumably 720x576) resolution works, but unfortunately some channels send other resolutions, such as 528x576. This results with a simple failure with error message in kern.log: vdr-fbfe[5429] general protection ip:af24feb1 sp:ad8c5f90 error:0 in xineplug_post_swscale.so[af24f000+4000] So, nothing that requires scaling, works. libxine1 pacakge is version 1.1.18.1-1+b2, same goes for libxine1-ffmpeg, libavcodec52 is version 5:0.5.1+svn20100411-0.0, libavutil49 4:0.5.1-3, libpostproc51 5:0.5.1+svn20100411-0.0. Any idea what might cause this kind of behavior? -- Sami Sundell

3 3

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr