date:20130113

Re: [vdr] DVB_API_VERSION problem

2013-01-13 Thread Halim Sahin

Hi,
On Sat, Jan 12, 2013 at 12:50:13AM +0100, Leo Márquez wrote:
 I'm trying to build vdr-1.7.35.
 I know that it requires at least a DVB driver with api version 5.3 or
 higher. For this reason I downloaded and compiled the V4L-DVB dvb drivers
 from linuxtv.org.
 The process seems to be completed ok, I restarted to be sure the new driver
 is used and I also created a Make.config file in the vdr folder in order to
 specify the DVBDIR but VDR is still complaining about the DVB_API_VERSION.
 
 At this time I'm a little bit confused and I'm not sure if I'm using the
 new driver or not. Is there a way to check if I'm using a dvb api version
 5.3 or higher?
 If I check the DVB api version and it is ok, what can I do next?

Using DVBDIR in Make.config doesn't work any more because of removal of
these lines:

ifdef DVBDIR
INCLUDES += -I$(DVBDIR)/include
endif
Add these lines to your Make.config and vdr builds again.

@Klaus:
Whats the suggested way to use different dvb-headers in vdr versions
=1.7.35???
Regards
Halim


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

Re: [vdr] DVB_API_VERSION problem

2013-01-13 Thread Klaus Schmidinger


On 13.01.2013 13:26, Halim Sahin wrote:

Hi,
On Sat, Jan 12, 2013 at 12:50:13AM +0100, Leo Márquez wrote:

I'm trying to build vdr-1.7.35.
I know that it requires at least a DVB driver with api version 5.3 or
higher. For this reason I downloaded and compiled the V4L-DVB dvb drivers
from linuxtv.org.
The process seems to be completed ok, I restarted to be sure the new driver
is used and I also created a Make.config file in the vdr folder in order to
specify the DVBDIR but VDR is still complaining about the DVB_API_VERSION.

At this time I'm a little bit confused and I'm not sure if I'm using the
new driver or not. Is there a way to check if I'm using a dvb api version
5.3 or higher?
If I check the DVB api version and it is ok, what can I do next?


Using DVBDIR in Make.config doesn't work any more because of removal of
these lines:

ifdef DVBDIR
INCLUDES += -I$(DVBDIR)/include
endif
Add these lines to your Make.config and vdr builds again.

@Klaus:
Whats the suggested way to use different dvb-headers in vdr versions

=1.7.35???


A revised version of the Makefiles will be coming up in version 1.7.36.
I have attached the current versions of Makefile and Make.config.template.

Klaus
#
# Makefile for the Video Disk Recorder
#
# See the main source file 'vdr.c' for copyright information and
# how to reach the author.
#
# $Id: Makefile 2.49 2013/01/12 13:45:01 kls Exp $

.DELETE_ON_ERROR:

# Compiler flags:

CC   ?= gcc
CFLAGS   ?= -g -O3 -Wall

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

CDEFINES  = -D_GNU_SOURCE
CDEFINES += -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE

LIBS  = -ljpeg -lpthread -ldl -lcap -lrt $(shell pkg-config --libs 
freetype2 fontconfig)
INCLUDES ?= $(shell pkg-config --cflags freetype2 fontconfig)

# Directories:

CWD   ?= $(shell pwd)
LSIDIR?= $(CWD)/libsi
PLUGINDIR ?= $(CWD)/PLUGINS

DESTDIR   ?=
VIDEODIR  ?= /srv/vdr/video
CONFDIR   ?= /var/lib/vdr
CACHEDIR  ?= /var/cache/vdr

PREFIX?= /usr/local
BINDIR?= $(PREFIX)/bin
INCDIR?= $(PREFIX)/include
LIBDIR?= $(PREFIX)/lib/vdr
LOCDIR?= $(PREFIX)/share/locale
MANDIR?= $(PREFIX)/share/man
PCDIR ?= $(PREFIX)/lib/pkgconfig
RESDIR?= $(PREFIX)/share/vdr

# Source documentation

DOXYGEN  ?= /usr/bin/doxygen
DOXYFILE  = Doxyfile

# User configuration

-include Make.config

# Mandatory compiler flags:

CFLAGS   += -fPIC
CXXFLAGS += -fPIC

# Common include files:

ifdef DVBDIR
CINCLUDES += -I$(DVBDIR)
endif

# Object files

SILIB= $(LSIDIR)/libsi.a

OBJS = audio.o channels.o ci.o config.o cutter.o device.o diseqc.o dvbdevice.o 
dvbci.o\
   dvbplayer.o dvbspu.o dvbsubtitle.o eit.o eitscan.o epg.o filter.o font.o 
i18n.o interface.o keys.o\
   lirc.o menu.o menuitems.o nit.o osdbase.o osd.o pat.o player.o plugin.o\
   receiver.o recorder.o recording.o remote.o remux.o ringbuffer.o sdt.o 
sections.o shutdown.o\
   skinclassic.o skinlcars.o skins.o skinsttng.o sourceparams.o sources.o 
spu.o status.o svdrp.o themes.o thread.o\
   timers.o tools.o transfer.o vdr.o videodir.o

DEFINES  += $(CDEFINES)
INCLUDES += $(CINCLUDES)

ifdef HDRDIR
HDRDIR   := -I$(HDRDIR)
endif
ifndef NO_KBD
DEFINES += -DREMOTE_KBD
endif
ifdef REMOTE
DEFINES += -DREMOTE_$(REMOTE)
endif
ifdef VDR_USER
DEFINES += -DVDR_USER=\$(VDR_USER)\
endif
ifdef BIDI
INCLUDES += $(shell pkg-config --cflags fribidi)
DEFINES += -DBIDI
LIBS += $(shell pkg-config --libs fribidi)
endif

LIRC_DEVICE ?= /var/run/lirc/lircd

DEFINES += -DLIRC_DEVICE=\$(LIRC_DEVICE)\
DEFINES += -DVIDEODIR=\$(VIDEODIR)\
DEFINES += -DCONFDIR=\$(CONFDIR)\
DEFINES += -DCACHEDIR=\$(CACHEDIR)\
DEFINES += -DRESDIR=\$(RESDIR)\
DEFINES += -DPLUGINDIR=\$(LIBDIR)\
DEFINES += -DLOCDIR=\$(LOCDIR)\

# The version numbers of VDR and the plugin API (taken from VDR's config.h):

VDRVERSION = $(shell sed -ne '/define VDRVERSION/s/^.*\(.*\).*$$/\1/p' 
config.h)
APIVERSION = $(shell sed -ne '/define APIVERSION/s/^.*\(.*\).*$$/\1/p' 
config.h)

all: vdr i18n plugins

# Implicit rules:

%.o: %.c
$(CXX) $(CXXFLAGS) -c $(DEFINES) $(INCLUDES) -o $@ $

# Dependencies:

MAKEDEP = $(CXX) -MM -MG
DEPFILE = .dependencies
$(DEPFILE): Makefile
@$(MAKEDEP) $(DEFINES) $(INCLUDES) $(OBJS:%.o=%.c)  $@

-include $(DEPFILE)

# The main program:

vdr: $(OBJS) $(SILIB)
$(CXX) $(CXXFLAGS) -rdynamic $(LDFLAGS) $(OBJS) $(LIBS) $(SILIB) -o vdr

# The libsi library:

$(SILIB):
$(MAKE) --no-print-directory -C $(LSIDIR) CXXFLAGS=$(CXXFLAGS) 
DEFINES=$(CDEFINES) all

# pkg-config file:

.PHONY: vdr.pc
vdr.pc:
@echo bindir=$(BINDIR)  $@
@echo mandir=$(MANDIR)  $@
@echo configdir=$(CONFDIR)  $@
@echo videodir=$(VIDEODIR)  $@
@echo cachedir=$(CACHEDIR)  $@
@echo resdir=$(RESDIR)  $@
@echo libdir=$(LIBDIR)  $@
@echo locdir=$(LOCDIR)  $@
@echo plgcfg=$(PLGCFG)  $@
@echo apiversion=$(APIVERSION)  $@
@echo cflags=$(CFLAGS)

Re: [vdr] Tuning timeouts blocks the other adapter

2013-01-13 Thread Klaus Schmidinger


On 06.01.2013 05:17, Richard Scobie wrote:



Mariusz Bialonczyk wrote:

On 11/10/2012 12:12 AM, Mariusz Bialonczyk wrote:

Is it possible that it is caused by some global lock or mutexes
in VDR?


Hello
It seems the cause of the problem has been located by Alex Pipelka.

The vdr freezes occurs when obtaining the signal strength/quality
with functions SignalStrength() and/or SignalQuality()
and when non-busy adapter has tunining issues
(frontend x/x timed out while tuning to channel ...).
It occurs only on multi adapters systems (one adapter is doing
EIT scan and the other is used, eg for a live-tv).

Guys, any thoughts on this?
I think it may be even kernel/drivers related issue.

some details in commit discussion:
https://github.com/pipelka/vdr-plugin-xvdr/commit/d3982714


I am running vdr 1.7.34 with a TT S2 6400 card on a dual core Intel Atom 1.8GHz 
board and believe I may be seeing these issues.

They manifest as intermittent video/audio disturbances of less than one frame duration - 
the audio usually gives a squawk.

I tried adding the suggested patch to vdr in the above thread:

diff -ur vdr-1.7.35-org/dvbdevice.c vdr-1.7.35/dvbdevice.c
--- vdr-1.7.35-org/dvbdevice.c  2012-12-30 12:27:39.0 +0100
+++ vdr-1.7.35/dvbdevice.c  2013-01-03 14:34:30.997489765 +0100
@@ -1510,12 +1510,12 @@

  int cDvbDevice::SignalStrength(void) const
  {
-  return dvbTuner ? dvbTuner-GetSignalStrength() : -1;
+  return -1;
  }

  int cDvbDevice::SignalQuality(void) const
  {
-  return dvbTuner ? dvbTuner-GetSignalQuality() : -1;
+  return -1;
  }

  const cChannel *cDvbDevice::GetCurrentlyTunedTransponder(void) const


This would only have an effect when you open a menu of the channel display
with a skin that displays the signal strength and quality. If no such menu is 
open,
these functions are never called, and thus disabling them would make no
difference.


It's possible it has improved the situation - no longer getting audio 
disturbances, but there are still very short duration video glitches.

In an effort to eliminate the second tuner scanning empty channels as the cause, I set, 
UpdateChannels = 0 in setup.conf, but it appears to not have the desired 
effect:

Jan  6 16:47:27 atom vdr: [790] frontend 1/0 timed out while tuning to channel 
487, tp 212651
Jan  6 16:47:47 atom vdr: [790] frontend 1/0 timed out while tuning to channel 
124, tp 212671
Jan  6 16:48:08 atom vdr: [790] frontend 1/0 timed out while tuning to channel 
71, tp 212680
Jan  6 16:48:50 atom vdr: [790] frontend 1/0 timed out while tuning to channel 
110, tp 112280

Is there some way I can stop the unused tuner from scanning altogether?


You need to set EPGScanTimeout = 0.
UpdateChannels has no effect on automatic tuning.

Klaus

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

[vdr] range-select in live plugin

2013-01-13 Thread Torgeir Veimo

I was getting carpal tunnel symptoms trying to select multiple recordings
for deletion in the live plugin, so I made a patch to add range selection
using the Quickboxes mootools plugin. It works by allowing you to click and
hold the mouse, while moving over subsequent selection checkboxes of
recordings.

Is the live plugin still being maintained? It seems most activity halted
about four years ago.

This patch is a bit rough, so some testing in different browsers might be
required. The Quickboxes plugins i MIT licensed, so can safely be included
if accepted.


live.patch
Description: Binary data
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] range-select in live plugin

2013-01-13 Thread Dieter Hametner

Hi

Am Sonntag, 13. Januar 2013 schrieb Torgeir Veimo:
 I was getting carpal tunnel symptoms trying to select multiple recordings
 for deletion in the live plugin, so I made a patch to add range selection
 using the Quickboxes mootools plugin. It works by allowing you to click and
 hold the mouse, while moving over subsequent selection checkboxes of
 recordings.
 
 Is the live plugin still being maintained? It seems most activity halted
 about four years ago.

It is in apply external submission phase only. I do not add new functionality 
currently and doubt that I will be able to do so in the next future.

Of course I keep the plugin compilable against the development in VDR. I 
currently wait until the disturbance through the development on the Makefile 
in VDR 1.7.34 and following versions have settled.

 This patch is a bit rough, so some testing in different browsers might be
 required. The Quickboxes plugins i MIT licensed, so can safely be included
 if accepted.

Yes it could be accepted. I tried to apply the supplied patch with
patch -p1  live.patch
but it reported errors and rejected some hunks.

Could you please revise your patch against the current 'master' branch of the 
version in the git [1]? While still beeing marked as unstable the 'master' 
version in the git can be used in productive environments.

Kind regards
Dieter

[1] http://projects.vdr-developer.org/git/vdr-plugin-live.git/


-- 
Dieter Hametnerdh (plus) vdr (at) gekrumbel (dot) de
live plugin developer  http://live.vdr-developer.org

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

Re: [vdr] Tuning timeouts blocks the other adapter

2013-01-13 Thread Richard Scobie




Klaus Schmidinger wrote:

In an effort to eliminate the second tuner scanning empty channels as 
the cause, I set, UpdateChannels = 0 in setup.conf, but it appears 
to not have the desired effect:


Jan  6 16:47:27 atom vdr: [790] frontend 1/0 timed out while tuning to 
channel 487, tp 212651
Jan  6 16:47:47 atom vdr: [790] frontend 1/0 timed out while tuning to 
channel 124, tp 212671
Jan  6 16:48:08 atom vdr: [790] frontend 1/0 timed out while tuning to 
channel 71, tp 212680
Jan  6 16:48:50 atom vdr: [790] frontend 1/0 timed out while tuning to 
channel 110, tp 112280


Is there some way I can stop the unused tuner from scanning altogether?


You need to set EPGScanTimeout = 0.
UpdateChannels has no effect on automatic tuning.


Thanks Klaus,

I will give this a try tonight.

Regards,

Richard

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

Re: [vdr] DVB_API_VERSION problem

Re: [vdr] DVB_API_VERSION problem

Re: [vdr] Tuning timeouts blocks the other adapter

[vdr] range-select in live plugin

Re: [vdr] range-select in live plugin

Re: [vdr] Tuning timeouts blocks the other adapter

6 matches

Site Navigation

Mail list logo

Footer information