[vdr] Utilising Nvidia HW En/Decode capabilities with ffmpeg

[Richard Scobie]

Not directly applicable to vdr, but for those transcoding recordings or 
using plugins that use ffmpeg, here's a useful recent article around 
using the hardware encode/decode capabilities of Nvidia's cards.


https://devblogs.nvidia.com/nvidia-ffmpeg-transcoding-guide/

Regards,

Richard

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

Re: [vdr] A couple of noob questions on VDR + vaapidevice (output plugin)

[Richard Scobie]

Frantisek Rysanek wrote:


50i). Maybe the VLC can somehow cope with that (perform rate
conversion on the fly) but the vaapidevice plugin cannot. Maybe I
should attach a TV as a second display and set the PC's HDMI frame
refresh rate to 50 Hz.


I have not yet started down the vaapi path yet, (soon), but I believe 
you will need to set your display for 50Hz. See post #2 in this thread:


https://www.vdr-portal.de/forum/index.php?thread/132471-xserver-für-vaapidevice-optimieren/


Another issue is: how do I control the OSD on the vaapidevice output,
if I only have a PC keyboard and mouse?


Keyboard control needs to be specified at compile time - on by default, see
Make.config.template in the source package.

I have never used the keyboard, but I have assumed that when started for 
the first time, you are prompted for which keys you want mapped to which 
vdr function, when using a remote. Maybe this is not the case with the 
keyboard? See the "Remote Control Keys" entry in the command "man 5 vdr".


Regards,

Richard

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

Re: [vdr] Questions about good hardware to view VDR 4K

[Richard Scobie]

Frantisek Rysanek wrote:


I've grown up in an age when websites tended to be intuitive to
navigate, and straight to the point. Or maybe that's just the way my
merciful memories of my youth would have it. This is not about
motherboards. I'm getting old.


You and me both... :)

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

Re: [vdr] Questions about good hardware to view VDR 4K

[Richard Scobie]

Frantisek Rysanek wrote:


OTOH, I don't like Asrock for two reasons:
1) they tend to support UEFI booting only, no legacy BIOS boot
2) they don't seem to have BIOS images publically available on the
downloads site...


I've not had a problem finding BIOS updates - here's the page for the 
board I mentioned:


https://www.asrock.com/mb/Intel/J4105M/index.asp#BIOS

I've been using an older N3150 for a few years now, with a TT S2 6400 
and a DD Cine S2 V7. The only issues have been very occasionally, one or 
other of the cards is not found at boot up, but I've had this on other 
manufacturers boards as well. Not sure if it's related to power down state.


Regards,

Richard

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

Re: [vdr] Questions about good hardware to view VDR 4K

[Richard Scobie]

Karim AFIFI wrote:


I will take a look to Atom CPU and Gemini Lake, but it seems there is no ATX
motherboards, only mini-ITX (not enough slots PCI/PCI-E for me).

As you see, it's very complicated, I continue to search ...


Hi,

Asrock do a range of mATX cards with integrated Gemini Lake, but none 
with PCI slot, just 3 x PCIe 1x.


Klaus (VDR author), is using the J4105M, with vaapi, but be aware that 
not all Asrock boards play well with Digital Devices cards. This one 
seems to and DD are looking into it - see this thread:


https://www.vdr-portal.de/forum/index.php?thread/132649-i2c-timeouts-mit-ddbridge/=1

Regards,

Richard



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

Re: [vdr] Skinflatplus -Clear Image Cache?

[Richard Scobie]

Hi Andre,

André Weidemann wrote:

I see a reference to an image cache and I assume it is trying to load 
logos that no longer reside in the logos directory.


I presume it is the other way around...
There used to be a radio channel called "kuwait radio 1" which vanished 
for whatever reason.
VDR renamed the channel to "kuwait radio 1 obsolete", for you 
convenience (So you know it is gone). When ever VDR tries to tune to 
that channel, skinflatplus is now looking for a matching logo, which is 
just not there.


Thanks for that, it makes sense, as my channels.conf is full of many 
obsolete entries, so I guess on startup, skinflatplus is scanning 
channels.conf, (which is when I see all the spurious messages), in order 
to create the image cache.


Looks like some channels.conf housekeeping might be in order... :)

Kind regards,

Richard

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

[vdr] Skinflatplus -Clear Image Cache?

[Richard Scobie]

When I start vdr and using the skinflatplus plugin, I see many log entries:

Nov 18 11:23:06 vdr vdr[1639]: [1639] imageloader LoadLogo: 
/mnt/storage/video/plugins/skinflatplus/logos//kuwait radio 1 
obsolete.png could not be loaded
Nov 18 11:23:06 vdr vdr[1639]: [1639] imageloader LoadLogo: 
/mnt/storage/video/plugins/skinflatplus/logos//kuwait - radio quran 
obsolete.png could not be loaded


I see a reference to an image cache and I assume it is trying to load 
logos that no longer reside in the logos directory.


How can I clear the cache, (and where is it located)?

Thanks,

Richard

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

Re: [vdr] TT S2 6400 IR Remote

[Richard Scobie]

Hi Detlef,

Thanks very much for that.

Detlef Heine wrote:

Here it is:

remote-ir.Up 00010001000E
remote-ir.Down   000100010012


Snip


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

[vdr] TT S2 6400 IR Remote

[Richard Scobie]

If there is anyone using the TT S2 6400 with the supplied IR receiver, 
remote and the "remote" plugin, could they please post a few lines from 
the remote.conf file?


Thanks,

Richard

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

[vdr] Video-Audio disruptions with 4.16+ kernel

[Richard Scobie]

Apologies in advance for a somewhat long-winded post.

I am using an Asrock Celeron based N3150M board with a TT S2 6400 card 
and a Digital Devices Cine S2 V7A card and 64bit kernels. The frontends 
on the TT card are unused in favour of the DD card - the TT card is just 
used for output. vdr is 2.3.9.


For a while now I have been assisting Daniel Scheller with testing his 
mainline kernel DD drivers prior to release:


https://github.com/herrnst/dddvb-linux-kernel

Up until a few days ago, all was well, using his dd 0.9.32 drivers in 
conjunction with kernel 4.15.0-rc6+.


The system was then updated to his dd 0.9.33 drivers and kernel 4.16+ 
and intermittent video/audio freezes of two to three seconds appeared. 
After some driver bisecting it turns out that this is being caused by 
the new kernel, not the dd drivers, (the problem occurs with the old 
drivers in the new kernel.).


I am unsure quite where to start, to work out which kernel update has 
caused this, but was hoping that the following log errors might point 
somewhere useful:


Apr 11 09:46:18 vdr vdr[718]: [874] ERROR: driver buffer overflow on 
device 1


Apr 11 09:57:20 vdr vdr[718]: [892] ERROR: 1 TS packet(s) not accepted 
in Transfer Mode


Apr 11 10:11:29 vdr vdr[718]: [914] ERROR: 6 TS packet(s) not accepted 
in Transfer Mode


Apr 11 10:21:13 vdr vdr[721]: [816] ERROR: driver buffer overflow on 
device 1
Apr 11 10:21:21 vdr vdr[721]: [816] ERROR: driver buffer overflow on 
device 1


Apr 11 10:39:33 vdr vdr[721]: [873] ERROR: 11 TS packet(s) not accepted 
in Transfer Mode


Apr 12 14:37:32 vdr vdr[922]: [957] ERROR: TS packet not accepted in 
Transfer Mode
Apr 12 14:37:32 vdr vdr[922]: [957] ERROR: TS packet not accepted in 
Transfer Mode
Apr 12 14:37:32 vdr vdr[922]: [957] ERROR: TS packet not accepted in 
Transfer Mode
Apr 12 14:37:33 vdr vdr[922]: [957] ERROR: TS packet not accepted in 
Transfer Mode
Apr 12 14:37:33 vdr vdr[922]: [957] ERROR: TS packet not accepted in 
Transfer Mode
Apr 12 14:37:34 vdr vdr[922]: [957] ERROR: TS packet not accepted in 
Transfer Mode
Apr 12 14:37:34 vdr vdr[922]: [957] ERROR: TS packet not accepted in 
Transfer Mode
Apr 12 14:37:34 vdr vdr[922]: [957] ERROR: TS packet not accepted in 
Transfer Mode


The effect coinciding with these, is a frozen picture and mute audio for 
up to several seconds.


Any help much appreciated.

Kind regards,

Richard Scobie

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

Re: [vdr] TT S2 6400 IR Pinout

[Richard Scobie]

Thanks Martin.

Regards,

Richard

Martin Gansser wrote:

Maybe you can ask here in the German-speaking VDR forum a few guys.
http://www.vdr-portal.de/board60-linux/board61-hardware/107135-mini-ir-on-f%C3%BCr-tt-s2-6400/

Martin


Gesendet: Samstag, 25. März 2017 um 10:23 Uhr
Von: "Richard Scobie" <r.sco...@clear.net.nz>
An: "Klaus Schmidinger's VDR" <vdr@linuxtv.org>
Betreff: [vdr] TT S2 6400 IR Pinout
Hi,

Does anyone know the pinout details for the IR receiver module supplied
with the TT S2 6400 card?

Thanks,

Richard

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

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



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

[vdr] TT S2 6400 IR Pinout

[Richard Scobie]

Hi,

Does anyone know the pinout details for the IR receiver module supplied 
with the TT S2 6400 card?


Thanks,

Richard

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

[vdr] VDR 2.3.2 and Plugins

[Richard Scobie]

Just wanted to draw attention to this thread at vdrportal for anyone who 
is discouraged from trying the 2.3.x vdr due to plugins not working.




Or, for English only speakers:



Klaus has very generously jumped in and updated some and more are sure 
to follow.


Anyone wanting extra skin capabilities, I have found SkinFlatPlus to 
work well.


https://projects.vdr-developer.org/projects/plg-skinflatplus

Have been running vdr 2.3.2 + dvdhddevice, femon, dvd, dvdswitch, 
streamdev-server and skinflatplus without problems for a couple of weeks 
now.


Regards,

Richard

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

Re: [vdr] VDR 2.3.2 and femon

[Richard Scobie]

Klaus Schmidinger wrote:



Try adding

  virtual int Width(void) const { return 50; }

to cFemonDummyFont.

Klaus


Thanks Klaus, that fixed it.

So far, so good with 2.3.2. I was having real problems with 2.3.1 but 
they're all fixed now.


Regards,

Richard

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

[vdr] VDR 2.3.2 and femon

[Richard Scobie]

Using the latest git version of the femon plugin:

https://github.com/rofafor/vdr-plugin-femon

I can successfully build it for vdr-2.3.1.

With vdr-2.3.2 I get the following errors:

*** Plugin femon:
g++ -O3 -Wall -Werror=overloaded-virtual -Wno-parentheses -march=native 
-D__user= -D__u8=uint8_t -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -I/usr/include/linux/dvb -c 
-DPLUGIN_NAME_I18N='"femon"' -DGITVERSION='"-GIT-7bc2ff5"' 
-I/home/rs/vdr-2.3.2/include  -o osd.o osd.c

In file included from /home/rs/vdr-2.3.2/include/vdr/config.h:20:0,
 from /home/rs/vdr-2.3.2/include/vdr/channels.h:13,
 from /home/rs/vdr-2.3.2/include/vdr/device.h:13,
 from /home/rs/vdr-2.3.2/include/vdr/receiver.h:13,
 from receiver.h:12,
 from osd.c:18:
/home/rs/vdr-2.3.2/include/vdr/font.h:48:15: error: ‘virtual int 
cFont::Width() const’ was hidden [-Werror=overloaded-virtual]

   virtual int Width(void) const = 0;
   ^
osd.c:148:15: error:   by ‘cFemonDummyFont::Width’ 
[-Werror=overloaded-virtual]

   virtual int Width(const char *sP) const { return 50; }
   ^
osd.c: In constructor ‘cFemonOsd::cFemonOsd()’:
osd.c:209:18: error: invalid new-expression of abstract class type 
‘cFemonDummyFont’

  fontM = new cFemonDummyFont;
  ^~~
osd.c:145:7: note:   because the following virtual functions are pure 
within ‘cFemonDummyFont’:

 class cFemonDummyFont : public cFont {
   ^~~
In file included from /home/rs/vdr-2.3.2/include/vdr/config.h:20:0,
 from /home/rs/vdr-2.3.2/include/vdr/channels.h:13,
 from /home/rs/vdr-2.3.2/include/vdr/device.h:13,
 from /home/rs/vdr-2.3.2/include/vdr/receiver.h:13,
 from receiver.h:12,
 from osd.c:18:
/home/rs/vdr-2.3.2/include/vdr/font.h:48:15: note:  virtual int 
cFont::Width() const

   virtual int Width(void) const = 0;
   ^
cc1plus: some warnings being treated as errors
Makefile:73: recipe for target 'osd.o' failed
make[1]: *** [osd.o] Error 1

Can anyone offer assistence please?

Regards,

Richard

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

Re: [vdr] TT S2 6400 Live View vs. Recorded Audio

[Richard Scobie]

Klaus Schmidinger wrote:


In live mode all data is handled directly within the TT S2-6400's
hardware, while when playing a recording, the data (and expecially
the PAT/PMT) has been processed by VDR (when the recording was
made).

Don't know if this has any effect, but it's the only difference
I can think of.

Klaus


Thanks Klaus.

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

[vdr] TT S2 6400 Live View vs. Recorded Audio

[Richard Scobie]

A number of channels on one mux have HE-AACv2 audio which I believe to 
be incorrectly tagged as AAC and as a result, viewing them live in VDR, 
the audio is mute.


However, if they are recorded and played back in VDR, the audio plays fine.

Can anyone explain the difference between the audio handling?

System is VDR 2.2.0 and TT S2 6400 with 0.5.1 firmware and latest drivers.

Regards,

Richard

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

[vdr] Large amount of logging with vdr on Fedora 24

[Richard Scobie]

I have just updated the OS of my TT s2-6400 based vdr box from Fedora 16 
to Fedora 24 Server and all is working fine except the log (both 
journald and rsyslog) fill up rapidly with the following type of entry.


[ 1983.410546] demux_worker (0): dma buffer = 0
[ 1983.427146] demux_worker (0): dma buffer = 1
[ 1983.444525] demux_worker (0): dma buffer = 2
[ 1983.461113] demux_worker (0): dma buffer = 3
[ 1983.477710] demux_worker (0): dma buffer = 4
[ 1983.494305] demux_worker (0): dma buffer = 5
[ 1983.509629] stv090x_read_status: Status: Unlocked (Searching ..)
[ 1983.511662] demux_worker (0): dma buffer = 6
[ 1983.528265] demux_worker (0): dma buffer = 7
[ 1983.544857] demux_worker (0): dma buffer = 0
[ 1983.562229] demux_worker (0): dma buffer = 1
[ 1983.578835] demux_worker (0): dma buffer = 2


I am using a custom kernel with a fork of the DVB drivers, as opposed to 
the stock versions of both on the Fedora 16 install, so am just 
wondering if anyone is running a standard late Fedora install and seeing 
this behaviour?


Thanks,

Richard

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

Re: [vdr] Skinflatplus plugin Channel Logo Names [Solved]

[Richard Scobie]

Richard Scobie wrote:


A number of other PVR projects require the logo to be named identically
to the channel name in the EPG data, but this does not seem to work here.


I found that the above is true, but the filenames must be all lower case.

I am very impressed with the polished appearance and very flexible 
configuration of this plugin, which has just been updated:


https://projects.vdr-developer.org/projects/plg-skinflatplus/news

Regards,

Richard

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

Re: [vdr] Skinflatplus plugin Channel Logo Names

[Richard Scobie]

VDR User wrote:

png


Thanks for the reply.

I am using *.png, but what I meant was, what are the naming 
requirements, for the files, so that the skin selects the correct logo 
for the current channel tuned?


A number of other PVR projects require the logo to be named identically 
to the channel name in the EPG data, but this does not seem to work here.


Regards,

Richard

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

[vdr] Skinflatplus plugin Channel Logo Names

[Richard Scobie]

Can anyone who uses the skinflatplus plugin please tell me what the 
filename format for channel logo icons is?


I currently have them named the same as the channel name from 
channels.conf, but they do not display.


Thanks,

Richard

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

Re: [vdr] VDR 2.3.1 dvbhddevice plugin

[Richard Scobie]

Klaus Schmidinger wrote:

On 09.09.2016 21:14, Richard Scobie wrote:

...
The "recordings" menu is no longer navigable - the highlit entry will
not move and more than one iten in the list will become highlighted.


Yes, I have this, too. No fix yet, though.
Just press the Up or Down key in such a case and you get the cursor back.
Ignore the previous (stuck) cursor. I guess this is the typical flaw that
just isn't causing enough trouble to get fixed right away... ;-)


Interesting. In my case, opening Recordings menu places a the 
highlighted recording in the centre of the list.


A single "Up" press scrolls the list and places the highlighted 
recording at the botoom of the list. Furthur Up key presses have no effect.


A Down key press at this point moves the highlighted event down one 
entry and scrolls the list so that this is at the top of the list. 
Further Down key presses have no effect.


Regards,

Richard

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

Re: [vdr] VDR 2.3.1 dvbhddevice plugin

[Richard Scobie]

Hi Klaus,

Klaus Schmidinger wrote:


"vdr-2.3.1-fixcrashdelrec.diff" and
"vdr-2.3.1-grantrecursivewritelocks-2.diff" are the only two fixes I
have. I sincerely hope to find more time for VDR development in the
not so distant future. This past year I was rather busy with lots of
other stuff. And of course any known fixes will go into the next
version.

Klaus


Thanks for the reply.

Further testing last night after applying both those patches, revealed 
although it no longer crashes while deleting a recording, things still 
aren't right.


The "recordings" menu is no longer navigable - the highlit entry will 
not move and more than one iten in the list will become highlighted.


I'll try each patch seperately.

Regards,

Richard


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

Re: [vdr] VDR 2.3.1 dvbhddevice plugin

[Richard Scobie]

Further to my last post, I applied the "vdr-2.3.1-fixcrashdelrec.diff" 
and "vdr-2.3.1-grantrecursivewritelocks-2.diff" that Klaus posted to the 
thread on vdr.portal.de :


http://www.vdr-portal.de/board1-news/board2-vdr-news/127271-announce-vdr-developer-version-2-3-1/index2.html

and I am no longer seg faulting.

I did not try this initially, as the poster "UFO", on that thread, for 
whom the patches were written, had not found any improvement.


Regards,

Richard

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

Re: [vdr] VDR 2.3.1 dvbhddevice plugin

[Richard Scobie]

Replying to my own post, it looks like this crash on deleting recordings 
is probably not due to dvbhddevice plugin, as others have experienced 
it, according to comment no. 26 in this thread:


http://www.vdr-portal.de/board1-news/board2-vdr-news/127271-announce-vdr-developer-version-2-3-1/index2.html

@Klaus

This comment and replies from yourself were  a year ago.

Have you found a solution yet and it's due out in the next release, or 
would you like me to do any other testing or to provide any other 
information?


An incomplete backtrace is below:

Program received signal SIGSEGV, Segmentation fault.
cRecordings::MBperMinute (this=0x0) at recording.c:3049
3049}
Missing separate debuginfos, use: debuginfo-install 
expat-2.0.1-11.fc15.x86_64 fontconfig-2.8.0-4.fc16.x86_64 
freetype-2.4.6-3.fc16.x86_64 glibc-2.14.90-14.x86_64 
libattr-2.4.46-2.fc16.x86_64 libcap-2.22-1.fc15.x86_64 
libgcc-4.6.2-1.fc16.x86_64 libjpeg-turbo-1.1.1-1.fc16.x86_64 
libstdc++-4.6.2-1.fc16.x86_64

(gdb) bt full
#0  cRecordings::MBperMinute (this=0x0) at recording.c:3049
Recording = 
size = 0
length = 0
#1  0x0052ea0c in cVideoDiskUsage::HasChanged (State=@0x802660)
at videodir.c:214
RecordingsLock = {stateKey = {stateLock = 0x0, write = false,
state = -1, timedOut = false}, list = 0x0}
Recordings = 
MBperMinute = 
FreeMB = 629428
UsedPercent = 
#2  0x0052eb08 in cVideoDiskUsage::String () at videodir.c:231
No locals.
#3  0x004fde06 in cSkinClassicDisplayMenu::DrawTitle (this=0xaa4020)
at skinclassic.c:282
font = 0xa75540
WithDisk = 
#4  0x004d5c44 in Display (this=0xad3950) at osdbase.c:238
count = 
#5  cOsdMenu::Display (this=0xad3950) at osdbase.c:223
No locals.
#6  0x004cb5bb in cMenuRecordings::Delete (this=0xad3950)
at menu.c:3119
Recordings = 0x7f9bc0
Recording = 0x7fffe803cae0
FileName = {_vptr.cString = 0x79a350,
  s = 0xad1e50 
"/mnt/storage/video/Newshub_Live_At_6pm/_/2016-09-08.17.55.3-0.rec"}

ri = 
#7  0x004d6a1c in cOsdMenu::ProcessKey (this=0xaadc50, Key=kYellow)
at osdbase.c:528
state = 
#8  0x004cb734 in cMenuRecordings::ProcessKey (this=0xaadc50,
Key=kYellow) at menu.c:3177
HadSubMenu = true
state = 
#9  0x004d6a1c in cOsdMenu::ProcessKey (this=0xaa3ef0, Key=kYellow)
at osdbase.c:528
state = 
#10 0x004caa66 in cMenuMain::ProcessKey (this=0xaa3ef0, Key=kYellow)
at menu.c:4372
HadSubMenu = true
osdLanguage = 0
state = 
#11 0x00474836 in main (argc=, argv=)
at vdr.c:1354
state = 
Now = 1473396864
Interact = 
key = 
PreviousChannelIndex = 1
LastChannelChanged = 1473396826
IsInfoMenu = 
Menu = 
LastChannel = 12
LastTimerChannel = -1
PreviousChannel = {1, 12}
CurrentSkin = 
LastInteract = 1473396864
MaxLatencyTime = 0
InhibitEpgScan = false
ResourceDirectory = 0x57d2407f 
LocaleDirectory = 0x552300 "ing down"
MuteAudio = 255
savedTm = {c_iflag = 1280, c_oflag = 5, c_cflag = 191,
  c_lflag = 35387, c_line = 0 '\000',
  c_cc = 
"\003\034\177\025\004\000\001\000\021\023\032\000\022\017\027\026", 
'\000' , c_ispeed = 15, c_ospeed = 15}

ConfigDirectory = 0x552300 "ing down"
Args = 
VdrUser = 0x0
VideoDirectory = 
LircDevice = 
EpgDataFileName = 0x7f9f40 "\241\\\322W"
DisplayVersion = 12
WatchdogTimeout = 0
DeprecatedVdrCharsetOverride = 0x1 
PluginManager = {_vptr.cPluginManager = 0x797bf0,
  static pluginManager = 0x7fffdf70,
  directory = 0x809b60 "/home/rs/vdr/PLUGINS/lib",
  lastHousekeeping = 1473396825, nextHousekeeping = -1,
  dlls = { = { = {_vptr.cListBase = 
0x797c50,

objects = 0x809c20, lastObject = 0x809c20, count = 1,
stateLock = {name = 0x0, threadId = 0, rwLock = {rwlock = {
  __data = {__lock = 0, __nr_readers = 0,
__readers_wakeup = 0, __writer_wakeup = 0,
__nr_readers_queued = 0, __nr_writers_queued = 0,
---Type  to continue, or q  to quit---
__writer = 0, __shared = 0, __pad1 = 0, __pad2 
= 0,

__flags = 0}, __size = '\000' ,
  __align = 0}}, state = 0, explicitModify = false},
needsLocking = 0x0,
useGarbageCollector = false}, }, data fields>}}

StartedAsRoot = 
AudioCommand = 0x0
c = 
CodeSet = 
HasStdin = true
UserDump = 32
SVDRPport = 6419
CacheDirectory = 0x552300 "ing down"
DaemonMode = 90
EpgDataReader = { = {_vptr.cThread = 

Re: [vdr] VDR 2.3.1 dvbhddevice plugin

[Richard Scobie]

cedric.dew...@telfort.nl wrote:


Hi Richard,
Could you show the changes you made? Maybe we can see from that what you missed 
:-)


Hi Cedric,

Thanks for your help.

In dvbhddevice.c :

- static const char *VERSION= "2.2.0";
+ static const char *VERSION= "2.3.1";

In dvbhdffdevice.c:

void cDvbHdFfDevice::SetAudioTrackDevice(eTrackType Type)
{
//printf("SetAudioTrackDevice %d\n", Type);
const tTrackId *TrackId = GetTrack(Type);
if (TrackId && TrackId->id) {
int streamType = 0;
-cChannel * channel = Channels.GetByNumber(CurrentChannel());
+   LOCK_CHANNELS_READ;
+const cChannel * channel = Channels->GetByNumber(CurrentChannel());

After making these changes, the plugin compiled without error.

Regards,

Richard


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

[vdr] VDR 2.3.1 dvbhddevice plugin

[Richard Scobie]

Does anyone have  a vdr 2.3.1 modified version of the dvbhddevice plugin 
(or a patch against 2.2.0), that they can let me have?


I am not at all a coder, but with the help of the changes in the 2.3.1 
Release notes and looking at another plugin that had been updated to 
2.3.1, I made a few changes to the 2.2.0 plugin and got it to compile 
and it seems to work fine until I go to delete a recording, at which 
point vdr crashes.


This is vanilla vdr 2.3.1 and only my (probably incomplete) modified 
2.2.0 dvbhddevice plugin.


Thanks,

Richard

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

[vdr] Unreliable shutdown

[Richard Scobie]

This is not strictly a vdr problem, but was wondering if others have 
seen it and have suggestions for a solution.


I have an Intel Atom/Fedora based system running the latest vdr and 
about 20% of the time when either the Power OFF remote command is 
issued or the shutdown command (shutdown -h now), is run, the box will 
go into a sleep/standby mode, rather than a complete power down.


When it does this, the box will not wake up for the next programmed 
timer, nor from pushing the power button. A complete power down is 
required to restore operation.


The same thing happens on my Core2 Quad/Centos desktop machine, except 
that sleep occurs about 60% of the time.


Is there a better shutdown command to guarantee full power down?

Regards,

Richard

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

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

[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

[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] VDR test series about frame detector

[Richard Scobie]

Eike wrote:


I need reports which number your stream resulted in (the Maximum TS package frame 
size) and what you've tested
(Cable? Satellite? Terrestrical? HD, SD? Your country?). The result is 
interesting even if it is 5 or 6.


I tested DVB-S SD recordings from three different TV networks in New 
Zealand and all reported 5 as the maximum TS frame size.


Regards,

Richard

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

Re: [vdr] Channel dropout unless femon active

[Richard Scobie]

Klaus Schmidinger wrote:

On 25.08.2013 21:31, Richard Scobie wrote:



Klaus Schmidinger wrote:

On 25.08.2013 05:32, Richard Scobie wrote:

Perhaps a little off topic, but I wonder if anyone can shed any light
on the following.

I am viewing a signal that is very close to reception threshold - dish
a little small, STR value 65%, SNR value 67%, but BER and UNC errors
as reported by femon are zero.

As long as I leave the femon plugin active on screen, I can view it
uninterrupted. If I turn it off, within 60 seconds, the picture will
disappear until I activate femon again.

Initally it will only show SIGNAL and CARRIER indicators active,
then after a short period, everything will lock again and the channel
will re-appear.

I am running the latest vdr version with a TT 6400 S2 full feature
card, with latest drivers and firmware. Relevent drivers would be
perhaps stv090x or stv6110x.

Channel parameters DVB-S2, symbol rate 15000 FEC 3/5  QPSK Video 35Mb
MPEG2 1920 x 1080, Audio MPEG 270Mb


Do you have both inputs of the TT-S2 6400 connected to satellite cables?
And is there actually a signal on both of them?


Hi Klaus,

I have three dishes with dual LNB's, with each LNB output going to two
4x1 diseq switches, feeding each tuner, so both tuners have the same
signals available.

As two whether the other tuner always has a signal present, I cannot
say for sure as my channel list has quite a number of itinerant feed
channels loaded, which are not always active, so vdr may well be
scanning  across empty channels on the second tuner.

Indeed, this channel I am having trouble with is one of those - a feed
from a motor sport event and is only there on certain weekends.

My somewhat uninformed thought was that perhaps femon's constant
polling for front end values was somehow causing a marginal PLL to
re-lock, vs the no femon situation where it looses lock on the weak
signal and does not reaquire it.


Well, VDR also constantly polls the frontend to see whether it is still
locked.

I'm afraid I'm out of ideas then...


Hi Klaus,

No problem, thanks for taking the time to reply anyway.

Regards,

Richard

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

Re: [vdr] Channel dropout unless femon active

[Richard Scobie]

Klaus Schmidinger wrote:

On 25.08.2013 05:32, Richard Scobie wrote:

Perhaps a little off topic, but I wonder if anyone can shed any light
on the following.

I am viewing a signal that is very close to reception threshold - dish
a little small, STR value 65%, SNR value 67%, but BER and UNC errors
as reported by femon are zero.

As long as I leave the femon plugin active on screen, I can view it
uninterrupted. If I turn it off, within 60 seconds, the picture will
disappear until I activate femon again.

Initally it will only show SIGNAL and CARRIER indicators active,
then after a short period, everything will lock again and the channel
will re-appear.

I am running the latest vdr version with a TT 6400 S2 full feature
card, with latest drivers and firmware. Relevent drivers would be
perhaps stv090x or stv6110x.

Channel parameters DVB-S2, symbol rate 15000 FEC 3/5  QPSK Video 35Mb
MPEG2 1920 x 1080, Audio MPEG 270Mb


Do you have both inputs of the TT-S2 6400 connected to satellite cables?
And is there actually a signal on both of them?


Hi Klaus,

I have three dishes with dual LNB's, with each LNB output going to two 
4x1 diseq switches, feeding each tuner, so both tuners have the same 
signals available.


As two whether the other tuner always has a signal present, I cannot say 
for sure as my channel list has quite a number of itinerant feed 
channels loaded, which are not always active, so vdr may well be 
scanning  across empty channels on the second tuner.


Indeed, this channel I am having trouble with is one of those - a feed 
from a motor sport event and is only there on certain weekends.


My somewhat uninformed thought was that perhaps femon's constant polling 
for front end values was somehow causing a marginal PLL to re-lock, vs 
the no femon situation where it looses lock on the weak signal and does 
not reaquire it.


Regards,

Richard

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

Re: [vdr] Tuning timeouts blocks the other adapter

[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] Tuning timeouts blocks the other adapter

[Richard Scobie]

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


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?

Regards,

Richard

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

Re: [vdr] vdr-1.7.32 plugin dvbhddevice fails

[Richard Scobie]

Hi Gerald,

Gerald Dachs wrote:

If you would take a deeper look into your post you would have noticed 
that the mentioned file bitbuffer.o is not
build to this time. It must have been build in a former stage. So there 
is still no proof that it

has been build with -fPIC.



You are correct. It appears none of the object files in 
dvbhddevice/libhdffcmd are being built without -fPIC, whereas all other 
object files in all the other plugins are, so I will investigate further.


Regards,

Richard

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

Re: [vdr] vdr-1.7.32 plugin dvbhddevice fails

[Richard Scobie]

Hi Olover,

Oliver Endriss wrote:


The attached patch should fix this problem.


Many thanks, that has fixed it.

And bonus points for decoding the mangled grammer in my previous post...

Regards,

Richard

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

Re: [vdr] vdr-1.7.32 plugin dvbhddevice fails

[Richard Scobie]

Hi Klaus,

Klaus Schmidinger wrote:


Maybe this was caused by the change I introduced in order to be able to
easily build a 32-bit version of VDR (and all its plugins) on a 64-bit
machine:

 


--- PLUGINS/src/dvbhddevice/libhdffcmd/Makefile 2012/01/18 12:25:20 1.2
+++ PLUGINS/src/dvbhddevice/libhdffcmd/Makefile 2012/10/09 09:54:26 1.3
@@ -24,6 +24,18 @@
 AR  ?= ar
 ARFLAGS ?= r

+### The directory environment:
+
+VDRDIR ?= ../../../..
+
+### Make sure that necessary options are included:
+
+include $(VDRDIR)/Make.global
+
+### Allow user defined options to overwrite defaults:
+
+-include $(VDRDIR)/Make.config
+
 ### Implicit rules:

 %.o: %.c
 



However, I got no such error message here, and I do use a TT S2-6400.
Maybe check your Make.global and/or Make.config files.



I checked both and they seem OK. My previous post just showed the 
linking stage. Here is the full output from compiling the dvbhddevice 
plugin and -fPIC is present during compilation of all object files.



Plugin dvbhddevice:
make[1]: Entering directory `/home/rs/vdr-1.7.32/PLUGINS/src/dvbhddevice'
make[1]: Leaving directory `/home/rs/vdr-1.7.32/PLUGINS/src/dvbhddevice'
make[1]: Entering directory `/home/rs/vdr-1.7.32/PLUGINS/src/dvbhddevice'
g++ -O3 -Wall -Werror=overloaded-virtual -Wno-parentheses -fPIC -c 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-D_GNU_SOURCE -DPLUGIN_NAME_I18N='dvbhddevice' 
-I/mnt/storage/media_build_experimental/linux/include -I../../../include 
dvbhddevice.c
g++ -O3 -Wall -Werror=overloaded-virtual -Wno-parentheses -fPIC -c 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-D_GNU_SOURCE -DPLUGIN_NAME_I18N='dvbhddevice' 
-I/mnt/storage/media_build_experimental/linux/include -I../../../include 
dvbhdffdevice.c
g++ -O3 -Wall -Werror=overloaded-virtual -Wno-parentheses -fPIC -c 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-D_GNU_SOURCE -DPLUGIN_NAME_I18N='dvbhddevice' 
-I/mnt/storage/media_build_experimental/linux/include -I../../../include 
hdffcmd.c
g++ -O3 -Wall -Werror=overloaded-virtual -Wno-parentheses -fPIC -c 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-D_GNU_SOURCE -DPLUGIN_NAME_I18N='dvbhddevice' 
-I/mnt/storage/media_build_experimental/linux/include -I../../../include 
hdffosd.c
hdffosd.c: In member function ‘virtual void cHdffOsd::DrawText(int, 
int, const char*, tColor, tColor, const cFont*, int, int, int)’:
hdffosd.c:258:9: warning: variable ‘limit’ set but not used 
[-Wunused-but-set-variable]
g++ -O3 -Wall -Werror=overloaded-virtual -Wno-parentheses -fPIC -c 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-D_GNU_SOURCE -DPLUGIN_NAME_I18N='dvbhddevice' 
-I/mnt/storage/media_build_experimental/linux/include -I../../../include 
menu.c
g++ -O3 -Wall -Werror=overloaded-virtual -Wno-parentheses -fPIC -c 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-D_GNU_SOURCE -DPLUGIN_NAME_I18N='dvbhddevice' 
-I/mnt/storage/media_build_experimental/linux/include -I../../../include 
setup.c

make -C libhdffcmd all
make[2]: Entering directory 
`/home/rs/vdr-1.7.32/PLUGINS/src/dvbhddevice/libhdffcmd'
gcc -O3 -Wall  -fPIC -shared -o libhdffcmd-0.1.0.so bitbuffer.o 
hdffcmd_av.o hdffcmd_base.o hdffcmd_generic.o hdffcmd_hdmi.o 
hdffcmd_mux.o hdffcmd_osd.o hdffcmd_remote.o
/usr/bin/ld: bitbuffer.o: relocation R_X86_64_PC32 against undefined 
symbol `memset@@GLIBC_2.2.5' can not be used when making a shared 
object; recompile with -fPIC

/usr/bin/ld: final link failed: Bad value
collect2: ld returned 1 exit status
make[2]: *** [libhdffcmd-0.1.0.so] Error 1
make[2]: Leaving directory 
`/home/rs/vdr-1.7.32/PLUGINS/src/dvbhddevice/libhdffcmd'

make[1]: *** [libvdr-dvbhddevice.so] Error 2
make[1]: Leaving directory `/home/rs/vdr-1.7.32/PLUGINS/src/dvbhddevice'

The machine is running Fedora 16 64bit and gcc version 4.6.2 20111027 
(Red Hat 4.6.2-1) and I have no problem building vdr-1.7.31.


Regards,

Richard

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

[vdr] vdr-1.7.32 plugin dvbhddevice fails

[Richard Scobie]

I have just upgraded from vdr-1.7.31 to vdr-1.7.32 with S2-6400 and on 
making plugins, I receive the following error:


make[2]: Entering directory 
`/home/rs/vdr-1.7.32/PLUGINS/src/dvbhddevice/libhdffcmd'
gcc -O3 -Wall  -fPIC -shared -o libhdffcmd-0.1.0.so bitbuffer.o 
hdffcmd_av.o hdffcmd_base.o hdffcmd_generic.o hdffcmd_hdmi.o 
hdffcmd_mux.o hdffcmd_osd.o hdffcmd_remote.o
/usr/bin/ld: bitbuffer.o: relocation R_X86_64_PC32 against undefined 
symbol `memset@@GLIBC_2.2.5' can not be used when making a shared 
object; recompile with -fPIC

/usr/bin/ld: final link failed: Bad value
collect2: ld returned 1 exit status
make[2]: *** [libhdffcmd-0.1.0.so] Error 1

As -fPIC is being used, I am not sure how to handle the comment, 
recompile with -fPIC


Regards,

Richard


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

[vdr] DVD menu issue

[Richard Scobie]

I have recently installed the dvd and dvdswitch on a new vdr system 
using a TT S2-6400 and am seeing a problem I did not have on the 
previous full feature card based setup.


On all DVD images, the menu highlight area, (that moves around as you 
navigate the menu), is either horizontally or vertically, (depending on 
DVD), displaced by a large amount.


Is anyone else seeing this?

vdr-1.2.27 libdvdnav-0.1.10 libdvdcss-1.2.11

Regards,

Richard

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

[vdr] Emergency exit

[Richard Scobie]

Is it expected behavior for vdr to do an emergency exit with two 
recordings in progress? If so, perhaps there could be an option to 
disable this.


I was recording a program on one tuner, while recording and delayed 
viewing a sports feed on the second tuner.


When the carrier was dropped at the end of the event, this triggered an 
emergency exit, thus disrupting the recording in progress on the first 
tuner.


vdr 1.7.27 and TT S2-6400.

Regards,

Richard


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

Re: [vdr] Emergency exit

[Richard Scobie]

VDR User wrote:


You can prevent emergency exit from actually exiting within VDR setup,
or setting `EmergencyExit = 0` in the setup.conf file.


Thank you. I did check the MANUAL file before posting, but missed that 
entry.


Regards,

Richard

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

Re: [vdr] [ANNOUNCE] epgfixer-plugin 0.1.0

[Richard Scobie]

Hi,


On 05/08/2012 07:30 PM, Marx wrote:



because I see no changes in EPG whatever I put in
/etc/vdr/plugins/charset.conf
Marx


I may be way off the mark here - I have come in halfway through the 
thread and do not use this plugin, but wouldn't the path above be:


/etc/vdr/plugins/epgfixer/charset.conf ?

Regards,

Richard

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

Re: [vdr] Repeating Timers

[Richard Scobie]

Thanks Klaus and Dave,

Dave wrote:

There is a 'Series Link' plugin for VDR which can cope with varying times for 
items in a series, see http://projects.vdr-developer.org/projects/vdrtva


The plugin was written for the UK 'Freeview' DVB-T service, though it should 
work with any implementation of the 'TV Anytime' standard ETSI 102 323.


Though it seems that the NZ DVB-T service was inspired by the UK one, I'm 
unsure how similar they are at the technical level. Some documents I've 
quickly looked at state that the EPG is carried in MHEG-5, others that the TV-

Anytime CRIDs are present in the EIT as they are in the UK.


Unfortunately I am outside our DVB-T coverage area and am using DVB-S, 
which uses the 'no frills EPG and VPS is not used here.


Regards,

Richard

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

Re: [vdr] Repeating Timers

[Richard Scobie]

Dave wrote:

Some more research suggests that NZ DVB-S uses the standard SI-based EIT, and 
also that the extensions for Series Link recording are virtually identical to 
the UK. So there is a very good chance that the vdrtva plugin will work.


Thanks very much for that, I will certainly give it a try.

Regards,

Richard

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

[vdr] Repeating Timers

[Richard Scobie]

If one sets a daily or weekly timer, does EPG schedule time on the day 
override any difference between the two?


I am thinking of the situation where a weekly timer is set and for 
whatever reason, the broadcaster reschedules one weeks episode, with the 
 EPG showing the correct time, will vdr check the EPG and adjust 
accordingly?


Regards,

Richard

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

Re: [vdr] Segfault in dvbhddevice

[Richard Scobie]

Klaus Schmidinger wrote:


Are you using the latest driver [1] and firmware [2]?

[1] http://powarman.dyndns.org/hgwebdir.cgi/v4l-dvb-saa716x/
[2] http://aregel.de/


Hi Klaus,

Have the latest firmware - drivers were a week old so have just updated 
them and the result is the same.


Seems to always segfault on bootup, then usually starts OK (with the 
occasional seg fault) when manually started.


Here is a larger section of the log:

Mar  8 08:34:40 atom vdr: [751] VDR version 1.7.25 started
Mar  8 08:34:40 atom vdr: [751] codeset is 'UTF-8' - known
Mar  8 08:34:40 atom vdr: [751] ERROR (tools.c,1388): ./locale: No such 
file or directory

Mar  8 08:34:40 atom vdr: [751] no locale for language code 'deu,ger'
Mar  8 08:34:40 atom vdr: [751] no locale for language code 'slv,slo'
Mar  8 08:34:40 atom vdr: [751] no locale for language code 'ita'
Mar  8 08:34:40 atom vdr: [751] no locale for language code 'dut,nla,nld'
Mar  8 08:34:40 atom vdr: [751] no locale for language code 'prt'
Mar  8 08:34:40 atom vdr: [751] no locale for language code 'fra,fre'
Mar  8 08:34:40 atom vdr: [751] no locale for language code 'nor'
Mar  8 08:34:40 atom vdr: [751] no locale for language code 'fin,suo'
Mar  8 08:34:40 atom vdr: [751] no locale for language code 'pol'
Mar  8 08:34:40 atom vdr: [751] no locale for language code 'esl,spa'
Mar  8 08:34:40 atom vdr: [751] no locale for language code 'ell,gre'
Mar  8 08:34:40 atom vdr: [751] no locale for language code 'sve,swe'
Mar  8 08:34:40 atom vdr: [751] no locale for language code 'rom,rum'
Mar  8 08:34:40 atom vdr: [751] no locale for language code 'hun'
Mar  8 08:34:40 atom vdr: [751] no locale for language code 'cat,cln'
Mar  8 08:34:40 atom vdr: [751] no locale for language code 'rus'
Mar  8 08:34:40 atom vdr: [751] no locale for language code 
'srb,srp,scr,scc'

Mar  8 08:34:40 atom vdr: [751] no locale for language code 'hrv'
Mar  8 08:34:40 atom vdr: [751] no locale for language code 'est'
Mar  8 08:34:40 atom vdr: [751] no locale for language code 'dan'
Mar  8 08:34:40 atom vdr: [751] no locale for language code 'cze,ces'
Mar  8 08:34:40 atom vdr: [751] no locale for language code 'tur'
Mar  8 08:34:40 atom vdr: [751] no locale for language code 'ukr'
Mar  8 08:34:40 atom vdr: [751] no locale for language code 'ara'
Mar  8 08:34:40 atom vdr: [751] loading plugin: 
/home/rs/vdr/PLUGINS/lib/libvdr-dvbhddevice.so.1.7.25
Mar  8 08:34:40 atom vdr: [751] loading plugin: 
/home/rs/vdr/PLUGINS/lib/libvdr-femon.so.1.7.25

Mar  8 08:34:40 atom vdr: [751] loading /mnt/storage/video/setup.conf
Mar  8 08:34:40 atom vdr: [751] loading /mnt/storage/video/sources.conf
Mar  8 08:34:40 atom vdr: [751] loading /mnt/storage/video/diseqc.conf
Mar  8 08:34:40 atom vdr: [751] loading /mnt/storage/video/scr.conf
Mar  8 08:34:40 atom vdr: [751] loading /mnt/storage/video/channels.conf
Mar  8 08:34:40 atom vdr: [751] loading /mnt/storage/video/timers.conf
Mar  8 08:34:40 atom vdr: [751] loading /mnt/storage/video/svdrphosts.conf
Mar  8 08:34:40 atom vdr: [751] loading /mnt/storage/video/remote.conf
Mar  8 08:34:40 atom vdr: [751] loading /mnt/storage/video/keymacros.conf
Mar  8 08:34:40 atom vdr: [756] video directory scanner thread started 
(pid=751, tid=756)
Mar  8 08:34:40 atom vdr: [757] video directory scanner thread started 
(pid=751, tid=757)

Mar  8 08:34:40 atom vdr: [751] registered source parameters for 'A - ATSC'
Mar  8 08:34:40 atom vdr: [751] registered source parameters for 'C - DVB-C'
Mar  8 08:34:40 atom vdr: [751] registered source parameters for 'S - DVB-S'
Mar  8 08:34:40 atom vdr: [751] registered source parameters for 'T - DVB-T'
Mar  8 08:34:40 atom vdr: [751] probing /dev/dvb/adapter1/frontend0
Mar  8 08:34:40 atom vdr: [751] creating cDvbDevice
Mar  8 08:34:40 atom vdr: [751] new device number 2
Mar  8 08:34:40 atom vdr: [758] epg data reader thread started (pid=751, 
tid=758)
Mar  8 08:34:40 atom vdr: [758] reading EPG data from 
/mnt/storage/video/epg.data
Mar  8 08:34:40 atom vdr: [751] frontend 1/0 provides DVB-S,DVB-S2,DSS 
with QPSK (STV090x Multistandard)
Mar  8 08:34:40 atom vdr: [761] tuner on frontend 1/0 thread started 
(pid=751, tid=761)

Mar  8 08:34:40 atom vdr: [751] found 1 DVB device
Mar  8 08:34:40 atom vdr: [761] cTimeMs: using monotonic clock 
(resolution is 1 ns)
Mar  8 08:34:40 atom vdr: [762] section handler thread started (pid=751, 
tid=762)
Mar  8 08:34:40 atom vdr: [751] initializing plugin: dvbhddevice 
(0.0.4): HD Full Featured DVB device
Mar  8 08:34:40 atom vdr: [751] initializing plugin: femon (1.7.12): DVB 
Signal Information Monitor (OSD)

Mar  8 08:34:40 atom vdr: [751] setting primary device to 1
Mar  8 08:34:40 atom vdr: [751] device 1 has no MPEG decoder
Mar  8 08:34:40 atom vdr: [751] assuming manual start of VDR
Mar  8 08:34:40 atom vdr: [751] SVDRP listening on port 6419
Mar  8 08:34:40 atom vdr: [751] setting current skin to classic
Mar  8 08:34:40 atom vdr: [751] loading 
/mnt/storage/video/themes/classic-default.theme

Re: [vdr] Segfault in dvbhddevice

[Richard Scobie]

Richard Scobie wrote:


DVB-T'
Mar  8 08:34:40 atom vdr: [751] probing /dev/dvb/adapter1/frontend0
Mar  8 08:34:40 atom vdr: [751] creating cDvbDevice
Mar  8 08:34:40 atom vdr: [751] new device number 2
Mar  8 08:34:40 atom vdr: [758] epg data reader thread started (pid=751, 
tid=758)
Mar  8 08:34:40 atom vdr: [758] reading EPG data from 
/mnt/storage/video/epg.data
Mar  8 08:34:40 atom vdr: [751] frontend 1/0 provides DVB-S,DVB-S2,DSS 
with QPSK (STV090x Multistandard)
Mar  8 08:34:40 atom vdr: [761] tuner on frontend 1/0 thread started 
(pid=751, tid=761)

Mar  8 08:34:40 atom vdr: [751] found 1 DVB device
Mar  8 08:34:40 atom vdr: [761] cTimeMs: using monotonic clock 
(resolution is 1 ns)
Mar  8 08:34:40 atom vdr: [762] section handler thread started (pid=751, 
tid=762)
Mar  8 08:34:40 atom vdr: [751] initializing plugin: dvbhddevice 
(0.0.4): HD Full Featured DVB device
Mar  8 08:34:40 atom vdr: [751] initializing plugin: femon (1.7.12): DVB 
Signal Information Monitor (OSD)

Mar  8 08:34:40 atom vdr: [751] setting primary device to 1
Mar  8 08:34:40 atom vdr: [751] device 1 has no MPEG decoder


I notice here that it is only findin one frontend and it thinks the card 
does not have MPEG decoder.


Here is the output from a correct startup:

Mar  8 08:35:35 atom vdr: [837] VDR version 1.7.25 started
Mar  8 08:35:35 atom vdr: [837] codeset is 'UTF-8' - known
Mar  8 08:35:35 atom vdr: [837] ERROR (tools.c,1388): ./locale: No such 
file or directory

Mar  8 08:35:35 atom vdr: [837] no locale for language code 'deu,ger'
Mar  8 08:35:35 atom vdr: [837] no locale for language code 'slv,slo'
Mar  8 08:35:35 atom vdr: [837] no locale for language code 'ita'
Mar  8 08:35:35 atom vdr: [837] no locale for language code 'dut,nla,nld'
Mar  8 08:35:35 atom vdr: [837] no locale for language code 'prt'
Mar  8 08:35:35 atom vdr: [837] no locale for language code 'fra,fre'
Mar  8 08:35:35 atom vdr: [837] no locale for language code 'nor'
Mar  8 08:35:35 atom vdr: [837] no locale for language code 'fin,suo'
Mar  8 08:35:35 atom vdr: [837] no locale for language code 'pol'
Mar  8 08:35:35 atom vdr: [837] no locale for language code 'esl,spa'
Mar  8 08:35:35 atom vdr: [837] no locale for language code 'ell,gre'
Mar  8 08:35:35 atom vdr: [837] no locale for language code 'sve,swe'
Mar  8 08:35:35 atom vdr: [837] no locale for language code 'rom,rum'
Mar  8 08:35:35 atom vdr: [837] no locale for language code 'hun'
Mar  8 08:35:35 atom vdr: [837] no locale for language code 'cat,cln'
Mar  8 08:35:35 atom vdr: [837] no locale for language code 'rus'
Mar  8 08:35:35 atom vdr: [837] no locale for language code 
'srb,srp,scr,scc'

Mar  8 08:35:35 atom vdr: [837] no locale for language code 'hrv'
Mar  8 08:35:35 atom vdr: [837] no locale for language code 'est'
Mar  8 08:35:35 atom vdr: [837] no locale for language code 'dan'
Mar  8 08:35:35 atom vdr: [837] no locale for language code 'cze,ces'
Mar  8 08:35:35 atom vdr: [837] no locale for language code 'tur'
Mar  8 08:35:35 atom vdr: [837] no locale for language code 'ukr'
Mar  8 08:35:35 atom vdr: [837] no locale for language code 'ara'
Mar  8 08:35:35 atom vdr: [837] loading plugin: 
/home/rs/vdr/PLUGINS/lib/libvdr-dvbhddevice.so.1.7.25
Mar  8 08:35:35 atom vdr: [837] loading plugin: 
/home/rs/vdr/PLUGINS/lib/libvdr-femon.so.1.7.25

Mar  8 08:35:35 atom vdr: [837] loading /mnt/storage/video/setup.conf
Mar  8 08:35:35 atom vdr: [837] loading /mnt/storage/video/sources.conf
Mar  8 08:35:35 atom vdr: [837] loading /mnt/storage/video/diseqc.conf
Mar  8 08:35:35 atom vdr: [837] loading /mnt/storage/video/scr.conf
Mar  8 08:35:35 atom vdr: [837] loading /mnt/storage/video/channels.conf
Mar  8 08:35:35 atom vdr: [837] loading /mnt/storage/video/timers.conf
Mar  8 08:35:35 atom vdr: [837] loading /mnt/storage/video/svdrphosts.conf
Mar  8 08:35:35 atom vdr: [837] loading /mnt/storage/video/remote.conf
Mar  8 08:35:35 atom vdr: [837] loading /mnt/storage/video/keymacros.conf
Mar  8 08:35:35 atom vdr: [838] video directory scanner thread started 
(pid=837, tid=838)
Mar  8 08:35:35 atom vdr: [839] video directory scanner thread started 
(pid=837, tid=839)

Mar  8 08:35:35 atom vdr: [837] registered source parameters for 'A - ATSC'
Mar  8 08:35:35 atom vdr: [837] registered source parameters for 'C - DVB-C'
Mar  8 08:35:35 atom vdr: [837] registered source parameters for 'S - DVB-S'
Mar  8 08:35:35 atom vdr: [837] registered source parameters for 'T - DVB-T'
Mar  8 08:35:35 atom vdr: [837] probing /dev/dvb/adapter0/frontend0
Mar  8 08:35:35 atom vdr: [837] creating cDvbHdFfDevice
Mar  8 08:35:35 atom vdr: [837] new device number 1
Mar  8 08:35:35 atom vdr: [840] epg data reader thread started (pid=837, 
tid=840)
Mar  8 08:35:35 atom vdr: [840] reading EPG data from 
/mnt/storage/video/epg.data
Mar  8 08:35:35 atom vdr: [837] frontend 0/0 provides DVB-S,DVB-S2,DSS 
with QPSK (STV090x Multistandard)
Mar  8 08:35:35 atom vdr: [842] tuner on frontend 0/0 thread started 
(pid=837, tid=842

Re: [vdr] Segfault in dvbhddevice

[Richard Scobie]

I have found that adding a sleep 5 to my startup script, between 
loading the drivers and starting vdr, has caused it to successfully 
survive five reboots.


Regards,

Richard

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

[vdr] Segfault in dvbhddevice

[Richard Scobie]

For the past few weeks, I have been running the current 1.7.XX version 
of vdr with an S2-6400 card, using only one tuner, which is connected to 
a 4 x 1 diseqc switch, without any problems.


The startup command has been:

/usr/local/bin/vdr -L /home/rs/vdr/PLUGINS/lib -D 1 -P dvbhddevice -P 
femon -v /mnt/storage/video -s /usr/local/bin/pm 


Today I replaced my LNB's with dual output ones, with the second output 
connected to a second 4 x 1 disecq switch, which is connected to the 
second tuner on the S2-6400 card.


I removed the -D 1 from the startup command and I am now finding that 
sometimes vdr crashes on startup, with the following error:


Mar  7 17:40:46 atom kernel: [   12.257270] vdr[755]: segfault at 0 ip 
7fd3118426d0 sp 7fffcbf98968 error 4 in 
libvdr-dvbhddevice.so.1.7.25[7fd311835000+18000]


If I then run the vdr startup command again, it starts OK.

Please let me know if there is any other information I can provide - the 
current version I am using is vdr 1.7.25.


Regards,

Richard

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

[vdr] Using second tuner on TT S2-6400

[Richard Scobie]

I have just managed to get an S2-6400 based vdr sytem up and running and 
am trying to work out how I can use the second tuner.


Currently I have a diseqc switch with two dishes connected to tuner 1, 
which works now I use the -D 0 vdr option.


I did think that adding 0: to the top of diseqc.conf file would force 
it to use the first tuner, but this does not work.


In any case, if I add another dish to tuner 2, how do I inform vdr what 
sources are available on it?


I get the impression that a plugin may be required, but I can't see 
anything suitable on the Wiki plugin page.


Any help would be appreciated.

Regards,

Richard

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

[vdr] Fonts

[Richard Scobie]

Hi,

I am setting up a vdr system and am trying to minimise the number of 
packages - there is no X11 installed.


On Fedora 16, I have installed the required fontconfig and freetype 
packages, but when I run vdr, I get a OSD No fonts found message.


I have also installed fontpackages-filesystem, 
xorg-x11-fonts-ISO8859-1-100dpi and xorg-x11-font-utils but am still 
getting the same error.


Can someone suggest anything else I need, or where the fonts need to be?

Regards,

Richard

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

Re: [vdr] Fonts

[Richard Scobie]

For the archives, all went well after installing the the gnu-free-* font 
packages.


Regards,

Richard

Richard Scobie wrote:

Hi,

I am setting up a vdr system and am trying to minimise the number of 
packages - there is no X11 installed.


On Fedora 16, I have installed the required fontconfig and freetype 
packages, but when I run vdr, I get a OSD No fonts found message.


I have also installed fontpackages-filesystem, 
xorg-x11-fonts-ISO8859-1-100dpi and xorg-x11-font-utils but am still 
getting the same error.


Can someone suggest anything else I need, or where the fonts need to be?

Regards,

Richard

___
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] [PATCH v2] multi-frontend-support for vdr 1.7.21

[Richard Scobie]

L. Hanisch wrote:


 Assumption for this patch:
 All frontends within one adapter have to be used mutually exclusive. 
All cards I know behave in this way. If there are cards with multiple 
frontends which can be used simultaneously I'd like to hear about it.


I believe the TT S2-6400 DVB-S/DVB-S2 card has two frontends that can be 
used simultaneously.


Regards,

Richard

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

[vdr] TT S2-6400 - high bandwidthperformance.

[Richard Scobie]

The original AV711X based full featured, DVB-S cards have a well known 
internal bandwidth limitation, that could be addressed by performing the 
budget patch modification to the card.


Does anyone know if the same or similar limitation applies to the new 
S2-6400 card - better, worse or similar performance?


Regards,

Richard

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

[vdr] TT Premium S2-6400

[Richard Scobie]

Looking at the data sheet for the new TT Premium S2-6400 hardware 
decoder card, it mentions a Video Breakout Cable for analog audio/video.


Can anyone tell me if this includes YUV/RGB out, or just composite?

Thanks,

Richard

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

Re: [vdr] Plugin for MHEG (BBC RedButton service)

[Richard Scobie]

Is anyone able to confirm whether this plugin with a full feature, 
hardware decoder DVB-S card please?


Regards,

Richard

John Williams wrote:

Hello,

I have adapted the standalone redbutton program
(http://redbutton.sourceforge.net/) into a plugin for VDR. This allows
me to view the Redbutton data service broadcast by the BBC.

This is a preliminary version of the plugin and it is not robust enough
for general use, but if anyone would like to experiment with it, the
source code can be downloaded from http://pond-weed.com/redbutton/

Regards,
John Williams


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

Re: [vdr] vdr in new zealand

[Richard Scobie]

Klaus Gerding wrote:

 in germany i used two full featured nexus dvb-s cards.
 that's what is plugged to my computer for now.
 
 is there a satellite providing digital tv in new zealand?

Hi Klaus,

I am using a Nexus dvb-s. The following are seeding channels for each 
transponder of interest and if you have vdr set to add channels, tuning 
to each of these will add all the others on each transponder:

These are on Optus D1 S160.0E

TV ONE;Television New 
Zealand:12483:hC34:S160.0E:22500:515:653:579:0:1035:47:22:0

TV3;TV Works:12456:hC34:S160.0E:22500:512:650:712:0:1920:47:21:0

There are a lot of overseas broadcasts on Optus D2 S152.0E

BVN:12644:v:S152.0E:22500:503:560:0:0:111:1:1:0

Press TV;D2:12706:v:S152.0E:22500:1960:1920:0:0:9:1:3:0

Abu Dhabi;D2:12734:v:S152.0E:22500:2104:2204:0:0:204:1:2:0


Beware of the line break in the first one.

Regards,

Richard

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

Re: [vdr] pay TV channels New Zealand

[Richard Scobie]

Simon Baxter wrote:
 How do pay-per-view channels work?
 
 What do I need to do here??

I have no idea how PPV works, but I would assume some form of 
interactivity is required so that the provider knows you are viewing and 
can bill you accordingly.

This must then require you to send some data to them so they can send 
you a key to unlock this channel.

This is just guesswork...

Regards,

Richard

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

Re: [vdr] FF card A/V sync - in progress?

[Richard Scobie]

Heikki Manninen wrote:


Just tested and I can confirm this too. Lost, Prison Break, everything
that used to suffer from this problem seems to work now :)


Looks good here too, on a Nexus-S 2.1 also.

Thanks!

Richard

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

Re: [vdr] New VDR hardware

[Richard Scobie]

Tony Houghton wrote:


How good is Linux support for these? I was under the impression that
XvMC doesn't work with ATI at all, and is broken in many versions of
NVidia's Linux drivers. And that the latter don't support deinterlacing
even though the hardware has been capable for quite a while now (since
6600 I heard).


A list of NVidia hardware capabilities is here:

http://www.nvidia.com/page/purevideo_support.html

As for current XvMC support, only IDCT and Motion Compensation with 
MPEG2 (and possibly MPEG1) are available in hardware - no hw deinterlacing.


Full support may happen eventually, judging by a comment here from 
NVidia staff:


http://macslow.thepimp.net/   (see bottom of UDS 2006 recap, Google, 
nVIDIA etc. article.)


Furthermore I hinted them towards us OpenSource folks wanting to see 
nVIDIA’s PureVideo HD chip-features exposed in the Linux-drivers too. 
They have plans for that, but not in the immediate future.


Regards,

Richard


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

Re: [vdr] New VDR hardware

[Richard Scobie]

Timothy D. Lenz wrote:

Too bad it only has 1 expansion slot. That means only 1 tunner board. I
wouldn't even concider anything with less then 2-3 slots.


It does have 4 x USB 2.0 which seems to be becoming popular for tuners now.

Regards,

Richard

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

Re: [vdr] FF card A/V sync suggestion

[Richard Scobie]

Adding my 2 cents, in the hope that others more knowledgable may be able 
to reproduce the problem.


Using a Nexus S 2.1 with the latest beta firmware, I find I lose audio 
sync when doing multiple yellow button skips to jump through 
commercial breaks, where there is a 30-50% chance the audio will be out 
after this. Doing a green button skip backwards almost always corrects it.


Regards,

Richard

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