Messages

Look in i18n.c in vdr for one way to do it. Basically that file contains the English version of every string output by vdr together with the translations in the different supported languages. When a text string needs to go to the user it passes through a translate function which identifies the English string and replaces it with the non-English equivalent. The PLUGINS.html file explains how a plugin can add its own strings to the translation system, and the plugin version of mediamvp uses this.

However I believe all of the user interaction within vomp is done by the client, ie all the text is included in dongle.bin, so the client would need to have its own implementation. That raises the question of how much space is there in the MVP memory? If space gets tight it might be necessary to create different dongle files for the different languages (ie one translation per file) or to do things an entirely different way.

Dave

Oops. I did say that vdr 1.3 support was experimental. Try this patch:

Index: vompserver/mvpclient.c
===================================================================
RCS file: /cvsroot/vomp/vompserver/mvpclient.c,v
retrieving revision 1.4
diff -u -r1.4 mvpclient.c
--- vompserver/mvpclient.c      23 Jul 2005 22:10:37 -0000      1.4
+++ vompserver/mvpclient.c      31 Jul 2005 11:58:38 -0000
@@ -331,7 +331,13 @@
#if VDRVERSNUM < 10300
     point = (char*)recording->Summary();
#else
-    point = (char*)recording->Info()->ShortText();
+    const cRecordingInfo *Info = recording->Info();
+    point = (char*)Info->ShortText();
+    printf("info pointer %p\nsummary pointer %p\n", Info, point);
+    if (isempty(point)) {
+      point = (char*)Info->Description();
+      printf("description pointer %p\n", point);
+    }
#endif
     strcpy((char*)&sendBuffer[count], point);
     count += strlen(point) + 1;
=========================================================

The new vdr version has removed the Summary() property and introduced ShortText() and Description(). It seems that ShortText isn't always populated. Actually I suspect that Description is the one needed even if ShortText is present.


Dave

The standby function is supposed to do what you expected, it does for me! When you put it into standby what is on your screen?

The screen goes black. I have to unplug the power connector from the MVP to get normal TV back.

I had the same behaviour with the dongle.bin provided with the MVP, however downloading a later release fixed it. There is mention of the fix in the Hauppauge release notes against build 22272.

Dave

After battling unsuccessfully for a couple of weeks with MVPServer I was delighted to get your software up and running in about 30 minutes. Very well done!

One item for the TODO list. Switching the MVP into standby should remove power from the SCART connector, as some TVs sense the voltage on one of the pins to switch back to normal mode. The most recent dongle.bin from Hauppauge does this.

Oh and the plugin doesn't compile under vdr 1.3.27 but you probably knew that.

Dave