gmane.linux.vdr

HDMI 5.1 in VDR with Alsa : how ?

Karim — 2013-05-14T22:10:56

Hello,

I am trying this connexion with vdr-2.0.1 +  xineliboutput + nVidia 210 :
VDR-----<hdmi>-----"TV_with_internal_HP"-----<Cinch_audio_num>-----"ampli
HC_external_HP"

With Debian Wheezy and alsa 0.1.25 :
- PCM => OK on TV and on ampli HC speakers.
- 5.1 => no sound in TV and ampli HC.

Is there a special parameter I missed ? (Some "hdmi passthrough" like...)
Any hint ? 

Greetings.
Karim


_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: Problems with VDSB, how to automate in SYSLOG

Brian-Imap — 2013-05-12T11:39:23

Moin,
well I did have a problem in my rsyslog conf meaning I did sometimes 
send a VDSB email when it should have been something else.
That is OK now. What I am seeing is the following:

May 11 23:39:24 localhost vdr: [4863] frontend 1/0 timed out while 
tuning to channel 7, tp 210906

Where the channel and transponder are random.
I have three cards in my system, one is a Cine 2 that appears to provide 
frontends 0/0 and 2/0,
FE 1/0 is my FF card. I picked out various tuning messages and used 
FEMON to check that each
of the channels that had a problem could be tuned on each device, and 
that gave me no problems.

I wonder if its just a transient thing?

I have the clock stuff setup as suggested and dont see any clock sync 
messages, it is just set up to use ZDF now.

I guess I'll go back to an activated emergancy exit now to get the DVB 
module load/unload back.

Cheers Brian















_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailma

Re: noepg

Antti Hartikainen — 2013-05-09T15:19:07

Quote from vdr manual:

A particular channel can be uniquely identified by its channel ID, which is a string that looks like this:

S19.2E-1-1089-12003-0

The components of this string are the Source (S19.2E), NID (1), TID (1089), SID (12003) and RID (0) as defined above. The last part can be omitted if it 
is 0, so the above example could also be written as S19.2E-1-1089-12003).

So everything you need you can get from your channels.conf.

_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: noepg

Marx — 2013-05-09T15:01:32

The problem is how to translate single line of channels.conf into 
something like: V-0-3588-1
Marx


_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: noepg

Lars Hanisch — 2013-05-09T07:41:23

Hi,

Am 09.05.2013 08:49, schrieb Marx:

 I think that old thread is about the noepg-patch. If your vdr is recent enough (and contains the EpgHandler interface)
you can use the noepg plugin.

 https://github.com/flensrocker/vdr-plugin-noepg

 The format of the settings.conf file is described in the README:

 https://github.com/flensrocker/vdr-plugin-noepg/blob/master/README#L29

 If you want to block some channels from receiving DVB-EPG it's just:

mode=blacklist
V-0-3588-1
V-0-2916-1
V-0-2917-1

 If you want to get DVB-EPG only for some channels and block all other:

mode=whitelist
V-0-3588-1
V-0-2916-1
V-0-2917-1

 I hope this helps.

Regards,
Lars.


_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

noepg

Marx — 2013-05-09T06:49:52

I'm trying to configure noepg headless. Some time ago I had GUI and 
configured noepeg, but now it's headless and after channels update I 
need to configure it again.

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

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

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

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

Marx

:DVB-T
TVP1 
HD;EmiTel:191500:I999B7C999D999M999T999G999Y999:T:27500:102=27:103=pol< at >3;104=qaa< at >122,108=aux< at >122:105;106=pol,109=eng:0:1:8808:1:0
TVP1;EmiTel:184500:I999B7C78D0M64T4G16Y0:T:27500:102=27:104=pol< at >4;103=qaa< at >122,108=aux< at >122:105;106=pol,109=eng:0:44:8808:3:0
TVP2 
HD;EmiTel:184500:I999B7C78D0M64T4G16Y0:T:27500:202=27:204=pol< at >4;203=qaa< at >122,208=aux< at >122:205;206=pol,209=eng:0:2:8808:3:0
TVP2;Emi

Re: Xineliboutput doesn't compil under vdr-2.0.1

Karim — 2013-05-06T21:47:09

It works ! Thank you René for the tips...

Regards.
Karim

-----Message d'origine-----
De : vdr-bounces< at >linuxtv.org [mailto:vdr-bounces< at >linuxtv.org] De la part de
René
Envoyé : lundi 6 mai 2013 16:50
À : VDR Mailing List
Objet : Re: [vdr] Xineliboutput doesn't compil under vdr-2.0.1

I do the following in the vdr source-dir (vdr-2.0.1):

make install-plugins

With this my plugins end up in the plugin-dir.

René

On 04.05.2013 18:03 , Karim wrote:
Objet : Re:


_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: Xineliboutput doesn't compil under vdr-2.0.1

René — 2013-05-06T14:50:04

I do the following in the vdr source-dir (vdr-2.0.1):

make install-plugins

With this my plugins end up in the plugin-dir.

René

On 04.05.2013 18:03 , Karim wrote:


_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: Xineliboutput doesn't compil under vdr-2.0.1

Karim — 2013-05-04T15:03:51

Hi Salim,

I was looking for "libvdr-xineliboutput.so.2.0.0.lib" file, instead of
"libvdr-xineliboutput.so.2.0.0". After I copied it in vdr/PLUGINS/lib,
problem solved.

Thanks a lot !
Karim

-----Message d'origine-----
De : vdr-bounces< at >linuxtv.org [mailto:vdr-bounces< at >linuxtv.org] De la part de
Karim
Envoyé : jeudi 2 mai 2013 19:24
À : 'VDR Mailing List'
Objet : Re: [vdr] Xineliboutput doesn't compil under vdr-2.0.1

Hi Halim,

I have double checked : there is no "libvdr-xineliboutput.so.2.0.0" in
vdr/PLUGINS/lib (or anywhere).
I am afraid that compilation fails.

Thanks
Karim

 
-----Message d'origine-----
De : vdr-bounces< at >linuxtv.org [mailto:vdr-bounces< at >linuxtv.org] De la part de
Halim Sahin Envoyé : jeudi 2 mai 2013 05:39 À : vdr< at >linuxtv.org Objet : Re:
[vdr] Xineliboutput doesn't compil under vdr-2.0.1

Hi,
In the output you posted here are no error message (only warnings).
The build was successfull but xineliboutput didn't copy the binaries to
PLUGINS/lib because of the old Makefiles.
You ca

Re: Xineliboutput doesn't compil under vdr-2.0.1

Karim — 2013-05-02T19:28:41

PS :
I tried to run "make install" from vdr but xineliboutput doesn't "see" vdr.
Please see below :

root< at >pctest:/usr/local/src/vdr/PLUGINS/src/xineliboutput# make install
sed: impossible de lire /config.h: Aucun fichier ou dossier de ce type
Makefile:97: ********************************************************
Makefile:98: VDR not detected ! VDR plugins will not be compiled.    
Makefile:99: ********************************************************
sed: impossible de lire /config.h: Aucun fichier ou dossier de ce type
sed: impossible de lire /config.h: Aucun fichier ou dossier de ce type
sed: impossible de lire /config.h: Aucun fichier ou dossier de ce type
sed: impossible de lire /config.h: Aucun fichier ou dossier de ce type
sed: impossible de lire /config.h: Aucun fichier ou dossier de ce type
sed: impossible de lire /config.h: Aucun fichier ou dossier de ce type
Installing //usr/local/lib/xine/plugins/2.2/xineplug_inp_xvdr.so
Installing //usr/local/lib/xine/plugins/2.2/post/xineplug_post_autocrop.so
Inst

Re: Xineliboutput doesn't compil under vdr-2.0.1

Karim — 2013-05-02T17:24:23

Hi Halim,

I have double checked : there is no "libvdr-xineliboutput.so.2.0.0" in
vdr/PLUGINS/lib (or anywhere).
I am afraid that compilation fails.

Thanks
Karim

 
-----Message d'origine-----
De : vdr-bounces< at >linuxtv.org [mailto:vdr-bounces< at >linuxtv.org] De la part de
Halim Sahin
Envoyé : jeudi 2 mai 2013 05:39
À : vdr< at >linuxtv.org
Objet : Re: [vdr] Xineliboutput doesn't compil under vdr-2.0.1

Hi,
In the output you posted here are no error message (only warnings).
The build was successfull but xineliboutput didn't copy the binaries to
PLUGINS/lib because of the old Makefiles.
You can do it yourself :-).
cd PLUGINS/src/xineliboutput
cp libvdr-xineliboutput* ../../lib
cp libxineliboutput* ../../lib
To install the frontends:
sudo make install
Thats it.
HTH.
Halim


_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-

Re: Xineliboutput doesn't compil under vdr-2.0.1

Halim Sahin — 2013-05-02T03:38:55

Hi,
In the output you posted here are no error message (only warnings).
The build was successfull but xineliboutput didn't copy the binaries to
PLUGINS/lib because of the old Makefiles.
You can do it yourself :-).
cd PLUGINS/src/xineliboutput
cp libvdr-xineliboutput* ../../lib
cp libxineliboutput* ../../lib
To install the frontends:
sudo make install 
Thats it.
HTH.
Halim


_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Xineliboutput doesn't compil under vdr-2.0.1

Karim — 2013-05-01T20:20:23

Hi,

I am trying new vdr-2.0.1 with 2 plugins : 
- femon (v2.0.0) 
- Xineliboutput (cvs from today).
=> Xineliboutput doesn't compil (no problem with Femon).

I compile VDR with theses options :  make REMOTE=LIRC VFAT=1 LCLBLD=1



Here is the error message I always get :
----------------------------------------------------------------------------
*** Plugin xineliboutput:
WARNING: plugin xineliboutput is using an old Makefile!
Makefile:112: ********************************************************
Makefile:113: VDR source tree not detected !                         
Makefile:114: VDR plugins will not be installed.                     
Makefile:115: ********************************************************
make[1]: Rien à faire pour « all ».


*** plugins with old Makefile: xineliboutput
**********************************************************************
*** While this currently still works, it is strongly recommended
*** that you convert old Makefiles to the new style used since
*** VDR version 1.7.36.

Re: Viaccess CAM support in VDR

Karim — 2013-05-01T13:55:58

Hello,

FYI, now TBS6928 + CAM Neotion Viaccess (*) is working with VDR 1.7.33.

1/ in dvb-s2 (TBS6928)
- SD channels => OK
- HD channels => a few artefacts and sometimes video isn't smooth enough. If
anyone have an idea...


2/ in dvb-t (TBS6280)
Working in SD ans HD channels, but as soon as I add this hardware, VDR
doesn't decrypt anymore dvb-s/s2 channels.
I've to try  with vdr 2.0.1, in case problem persists, I will ask to Klaus.

(*) after stability problem  with SMIT, I sent this CAM to vendor for
repair.

Regards.
Karim


-----Message d'origine-----
De : vdr-bounces< at >linuxtv.org [mailto:vdr-bounces< at >linuxtv.org] De la part de
hederic
Envoyé : mardi 22 janvier 2013 12:25
À : vdr< at >linuxtv.org
Objet : Re: [vdr] Viaccess CAM support in VDR

Karim <karim.afifi <at> laposte.net> writes:


Hi,

I don't know if it's the same problem but i'm having errors in logfile :

"CAM tried to send a buffer larger than the ecount size!"

End all channels stop working even plain unencrypted channels.

Bye.

Hederic


_

Re: Problems with VDSB, how to automate in SYSLOG

Teemu Suikki — 2013-04-28T18:53:17

Handling of VDSB should be improved somehow, or at least add some
configuration.

It's annoying if VDR is recording multiple channels, and one channel has
VDSB.. emergency exit at this point will break all the other recordings,
which otherwise would be fine.

Also I think VDR should try tuning to same channel with another frontend.
People might have different size dishes on different tuners. Some channels
might be unavailable in bad weather with small dishes, but view with larger
one. VDR should try all possible methods to tune the wanted channel, before
resorting to emergency exit..

Perhaps VDR should also store the time of previous emergency exit.. if VDSB
continues after first emergency exit, it's not very useful to exit again.
One emergency exit per recording should be enough.
 28.4.2013 20.52 "Udo Richter" <udo_richter< at >gmx.de> kirjoitti:

_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: Problems with VDSB, how to automate in SYSLOG

Udo Richter — 2013-04-28T17:45:27

Am 28.04.2013 16:52, schrieb Brian-Imap:

Its the only false alarm I know of, and would be an explanation why this
happens on the start of a recording. Tuning to the channel for recording
may activate the clock sync for that transponder, and cause a time jump
once. All other explanations involve crappy driver/hardware or bad
reception.

There should be a log message indicating the clock sync.

Cheers,

Udo


_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: Problems with VDSB, how to automate in SYSLOG

Brian-Imap — 2013-04-28T14:52:14

Hmmm,
I wasn't setting system time, so I have now activated that and set it to 
use the ZDF transponder.
I'll take a look at what is happening with my system clock too.
So you assume it was falsely triggering a VDSB thinking 30 secs had 
passed when in fact the clock
probably was adjusted instead?
Cheers Brian
_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: RFC: one or many positioners?

Ales Jurik — 2013-04-28T11:58:38

...

I thought about the possibility from diseqc.conf:

# A line containing space separated integer numbers, terminated with a ':',
# defines that any following DiSEqC sequences apply only to the given list
# of device numbers.

But I'm afraid that this remark was not unnecessary, sry.


I thought about possibility to send gotoxx command to all tuners/cards 
used, not only to the one which has positioner connected. In this case 
only gotoxx command should be used in all cases - I don't know if only 
one new entry in diseqc.conf like

*  11700 V  9750  t V W15 P W15 v t
*  99999 V 10600  t V W15 P W15 v T
*  11700 H  9750  t V W15 P W15 V t
*  99999 H 10600  t V W15 P W15 V T

valid for all tuners/cards will be enough.

Thanks,

Best Regards,

Ales

_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: Problems with VDSB, how to automate in SYSLOG

Udo Richter — 2013-04-28T01:28:56

Am 27.04.2013 14:06, schrieb Brian-Imap:

Do you have an in-accurate system clock and/or clock syncing enabled?
VDR will falsely trigger an VDSB if the clock is set more than 30
seconds ahead while a recording is running. If you set the clock by DVB
time, I'd suggest restricting it to one channel only.

Cheers,

Udo


_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: RFC: one or many positioners?

Klaus Schmidinger — 2013-04-27T15:09:09

Well, I guess especially with the Step() function it could have been nice
to have the sign indicate the direction. But then again VDR itself probably
isn't going to use Step() with anything else but '1', so

   enum ePositionerDirection { pdLeft, pdRight };
   virtual void Step(ePositionerDirection Direction, uint NumSteps = 1);

should do just fine...

Klaus

_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: RFC: one or many positioners?

Klaus Schmidinger — 2013-04-27T14:58:34

I'm planning to do it that way.


I don't understand what you mean here.


I'm afraid I don't understand this, either.
Can you be more specific?

Klaus

_______________________________________________
vdr mailing list
vdr< at >linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr