[vdr] TT S2 6400 not working correctly on a single tuner

2014-05-28 Thread Richard Scobie
I am currently having problems with either cabling or the Diseq switch 
attached to tuner 0 on my TT S2 6400, so as a workaround, I thought I 
could use the - D 1 switch to vdr, to force using tuner 1 only.


When I do this, it seems vdr does not see the card as full featured any 
more - no MPEG decoder and no OSD:


May 28 18:00:16 atom kernel: [8.267126] SAA716x FF FPGA version 1.09
May 28 18:00:16 atom kernel: [8.322299] SAA716x FF loader version 1.03
May 28 18:00:16 atom kernel: [8.430376] Adding 511996k swap on 
/dev/sda2.  Priority:0 extents:1 across:511996k
May 28 18:00:16 atom kernel: [9.008765] DVB: registering new adapter 
(SAA716x dvb adapter)
May 28 18:00:16 atom kernel: [9.122724] stv6110x_attach: Attaching 
STV6110x
May 28 18:00:16 atom kernel: [9.131550] SAA716x FF :04:00.0: 
DVB: registering adapter 0 frontend 0 (STV090x Multistandard)...
May 28 18:00:16 atom kernel: [9.132215] DVB: registering new adapter 
(SAA716x dvb adapter)
May 28 18:00:16 atom kernel: [9.133222] stv6110x_attach: Attaching 
STV6110x
May 28 18:00:16 atom kernel: [9.166794] SAA716x FF :04:00.0: 
DVB: registering adapter 1 frontend 0 (STV090x Multistandard)...
May 28 18:00:16 atom kernel: [9.183091] EXT4-fs (sda1): mounting 
ext3 file system using the ext4 subsystem
May 28 18:00:16 atom kernel: [9.191439] EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)

May 28 18:00:16 atom kernel: [9.206251] XFS (sda4): Mounting Filesystem
May 28 18:00:16 atom kernel: [9.401740] XFS (sda4): Ending clean mount
May 28 18:00:16 atom kernel: [9.962394] SAA716x FF firmware version 
0.3.9
May 28 18:00:16 atom kernel: [9.962510] input: TT6400 DVB IR 
receiver as /devices/pci:00/:00:1c.0/:04:00.0/input/input2
May 28 18:00:16 atom kernel: [   10.880902] lirc_dev: IR Remote Control 
driver registered, major 250

May 28 18:00:16 atom network[588]: Bringing up loopback interface:  [  OK  ]
May 28 18:00:16 atom kernel: [   11.599562] r8169 :03:00.0: em1: 
link down
May 28 18:00:16 atom kernel: [   11.599581] r8169 :03:00.0: em1: 
link down
May 28 18:00:16 atom kernel: [   11.600289] ADDRCONF(NETDEV_UP): em1: 
link is not ready
May 28 18:00:17 atom kernel: [   11.755042] lirc_serial: auto-detected 
active low receiver
May 28 18:00:17 atom kernel: [   11.755204] lirc_serial lirc_serial.0: 
lirc_dev: driver lirc_serial registered at minor = 0

May 28 18:00:19 atom network[588]: Bringing up interface em1:  [  OK  ]
May 28 18:00:19 atom kernel: [   14.100351] r8169 :03:00.0: em1: link up
May 28 18:00:19 atom kernel: [   14.100986] ADDRCONF(NETDEV_CHANGE): 
em1: link becomes ready

May 28 18:00:22 atom vdr: [783] VDR version 2.1.6 started
May 28 18:00:22 atom vdr: [783] codeset is 'UTF-8' - known
May 28 18:00:22 atom vdr: [783] loading plugin: 
/home/rs/vdr/PLUGINS/lib/libvdr-dvbhddevice.so.2.1.6
May 28 18:00:22 atom vdr: [783] loading plugin: 
/home/rs/vdr/PLUGINS/lib/libvdr-femon.so.2.1.6
May 28 18:00:22 atom vdr: [783] loading plugin: 
/home/rs/vdr/PLUGINS/lib/libvdr-dvd.so.2.1.6
May 28 18:00:22 atom vdr: [783] loading plugin: 
/home/rs/vdr/PLUGINS/lib/libvdr-dvdswitch.so.2.1.6
May 28 18:00:22 atom vdr: [783] loading plugin: 
/home/rs/vdr/PLUGINS/lib/libvdr-streamdev-server.so.2.1.6
May 28 18:00:22 atom systemd[1]: Startup finished in 1s 518ms 652us 
(kernel) + 2s 475ms 105us (initrd) + 12s 930ms 930us (userspace) = 16s 
924ms 687us.

May 28 18:00:22 atom vdr: [783] loading /mnt/storage/video/setup.conf
May 28 18:00:22 atom vdr: [783] ERROR: unknown config parameter: 
streamdev-server.SuspendMode = 1

May 28 18:00:22 atom vdr: [783] loading /mnt/storage/video/sources.conf
May 28 18:00:22 atom vdr: [783] loading /mnt/storage/video/diseqc.conf
May 28 18:00:22 atom vdr: [783] loading /mnt/storage/video/scr.conf
May 28 18:00:22 atom vdr: [783] loading /mnt/storage/video/channels.conf
May 28 18:00:22 atom vdr: [783] loading /mnt/storage/video/timers.conf
May 28 18:00:22 atom vdr: [783] loading /mnt/storage/video/svdrphosts.conf
May 28 18:00:22 atom vdr: [783] loading /mnt/storage/video/remote.conf
May 28 18:00:22 atom vdr: [783] loading /mnt/storage/video/keymacros.conf
May 28 18:00:22 atom vdr: [783] loading /mnt/storage/video/folders.conf
May 28 18:00:22 atom vdr: [783] DVB API version is 0x050A (VDR was built 
with 0x0504)
May 28 18:00:22 atom vdr: [783] frontend 1/0 provides DVB-S,DVB-S2,DSS 
with QPSK (STV090x Multistandard)

May 28 18:00:22 atom vdr: [783] found 2 DVB devices
May 28 18:00:22 atom vdr: [783] using only 1 DVB device
May 28 18:00:22 atom vdr: [783] initializing plugin: dvbhddevice 
(2.1.6): HD Full Featured DVB device
May 28 18:00:22 atom vdr: [783] initializing plugin: femon (2.1.1): DVB 
Signal Information Monitor (OSD)
May 28 18:00:22 atom vdr: [783] initializing plugin: dvd (0.3.6-b03): 
turn VDR into an (almost) full featured DVD player
May 28 18:00:22 atom vdr: [783] initializing plugin: dvdswitch (0.2.2): 
Allows 

Re: [vdr] TT S2 6400 not working correctly on a single tuner

2014-05-28 Thread Klaus Schmidinger

On 28.05.2014 07:59, Richard Scobie wrote:

I am currently having problems with either cabling or the Diseq switch attached to tuner 
0 on my TT S2 6400, so as a workaround, I thought I could use the - D 1 
switch to vdr, to force using tuner 1 only.

When I do this, it seems vdr does not see the card as full featured any more - 
no MPEG decoder and no OSD:
...


That's because the full featured part of the TT S2-6400 is linked to tuner 0.

Klaus

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


Re: [vdr] TT S2 6400 not working correctly on a single tuner

2014-05-28 Thread Lars Hanisch
Hi,

Am 28.05.2014 09:03, schrieb Klaus Schmidinger:
 On 28.05.2014 07:59, Richard Scobie wrote:
 I am currently having problems with either cabling or the Diseq switch 
 attached to tuner 0 on my TT S2 6400, so as a
 workaround, I thought I could use the - D 1 switch to vdr, to force using 
 tuner 1 only.

 When I do this, it seems vdr does not see the card as full featured any more 
 - no MPEG decoder and no OSD:
 ...
 
 That's because the full featured part of the TT S2-6400 is linked to tuner 
 0.

 I'm not a DVB-S user, but maybe you can use the diseqc.conf to bound device 1 
(tuner 0) to a source you haven't in your
channels.conf (like a none existing S1E).

 OTOH you can write a plugin which provides an device hook, that returns always 
false in DeviceProvidesTransponder if
the given device is a cDvbDevice and has an adapter/frontend of 0/0.

Lars.

 
 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] TT S2 6400 not working correctly on a single tuner

2014-05-28 Thread Richard Scobie



Lars Hanisch wrote:

Hi,

Am 28.05.2014 09:03, schrieb Klaus Schmidinger:

On 28.05.2014 07:59, Richard Scobie wrote:

I am currently having problems with either cabling or the Diseq switch attached 
to tuner 0 on my TT S2 6400, so as a
workaround, I thought I could use the - D 1 switch to vdr, to force using 
tuner 1 only.

When I do this, it seems vdr does not see the card as full featured any more - 
no MPEG decoder and no OSD:
...


That's because the full featured part of the TT S2-6400 is linked to tuner 0.


  I'm not a DVB-S user, but maybe you can use the diseqc.conf to bound device 1 
(tuner 0) to a source you haven't in your
channels.conf (like a none existing S1E).

  OTOH you can write a plugin which provides an device hook, that returns always false in 
DeviceProvidesTransponder if
the given device is a cDvbDevice and has an adapter/frontend of 0/0.

Lars.



Klaus


Thanks both, I'll just swap the input cables for now.

Regards,

Richard

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


Re: [vdr] converting ts to mkv

2014-05-28 Thread Lucian Muresan
On 26.05.2014 13:41, Tony Houghton wrote:
[...]
 It's better to use mkvmerge (or ffmpeg etc for mpeg2) to remultiplex
 properly. You still don't have to transcode the streams so it doesn't
 take much longer. Players can't tell how long (in terms of time) TS
 files are, or how any point in the file corresponds to time for seeking
 etc.

Also, mkvmerge removes NALUs from h264 if there are any, on the fly with
no noticeable overhead.


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