You are not logged in.

Dear visitor, welcome to VDR Portal. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.


Sunday, November 9th 2008, 9:55pm

[ANNOUNCE] vdr-femon-1.6.3

A new version of femon with a preliminary H.264 support is now available. As I don't have any H.264 streams available in my development setup there might be some problems with the support. Also there were heavy restructuring of source code that might provide some unwanted regression,. Please send all bug reports and patches to the author.

This post has been edited 1 times, last edit by "rofafor" (Nov 9th 2008, 9:59pm)


Monday, November 10th 2008, 2:10am

Thanks 4 the new version,

but ...

if i start the plugin from vdr menu, i see nothing.

In syslog i get following output

PHP Source code

Nov 10 02:02:20 vdr1 vdr: [25263ERRORcOsd::SetAreas returned 4
Nov 10 02:02:20 vdr1 vdr: [25673femon receiver thread started (pid=25263tid=25673)
Nov 10 02:02:20 vdr1 vdr: [25674femon osd thread started (pid=25263tid=25674
Nov 10 02:03:44 vdr1 vdr: [25674femon osd thread ended (pid=25263tid=25674)
Nov 10 02:03:46 vdr1 vdr: [25673femon receiver thread ended (pid=25263tid=25673)

Looks like, it starts but osd can not handle it.

The osd high in plugin i'm set it to 410, like the same high for osd menu of VDR.

Any hints ?

This post has been edited 1 times, last edit by "hd.brummy" (Nov 10th 2008, 2:28am)


Monday, November 10th 2008, 10:28am


Originally posted by hd.brummy
Looks like, it starts but osd can not handle it.

Well, I had to increase the size of used OSD by one row in order to include missing information for S2API. This change might break up OSD on 2MB FF cards due to memory limitation, but I couldn't test it on my setups (4MB FF & xineliboutput). However, your logs indicates about overlapping areas (the status window and detailed information window overlaps), so it seems that you should increase your OSD height until the OSD error number 4 vanishes.

Posts: 8,967

Location: Schwabenländle

Occupation: Bootmanager

  • Send private message


Monday, November 10th 2008, 10:49am

Tested with my Testsystem.

found the this entry in logfile:

Source code

Nov 10 10:41:48 [vdr] [24449] ERROR (femonosd.c,447): Die Operation wird nicht unterstützt

It seems it won't work correctly with my TT-3200.

Some parameters wil not shown in OSD.

This post has been edited 1 times, last edit by "C-3PO" (Nov 10th 2008, 1:12pm)


Monday, November 10th 2008, 11:45am


Originally posted by C-3POIt seems it won't work with correctly wit my TT-3200.

The femon is still using the old DVB api and it seems that your TT-3200 drivers don't support all those legacy ioctl commands. I'll wait for vdr-1.7.2 before implementing any S2API changes...


Monday, November 10th 2008, 8:37pm


it works now :)

im setup the Osd "high" to 420; lower, then i get an overlap in the 2 areas and an error in the syslog.

Maybe this parameter should be hardcoded in the sources to this high ?

output from a h264 channel: ( damnd quality from my mobilfone, sry )

Cheers :prost2

This post has been edited 2 times, last edit by "hd.brummy" (Nov 10th 2008, 8:47pm)

Immortal Romance Spielautomat