Uplink,

Thanx for you patience........and help.
Hopefully last question.........Device number.... Orbiter number I want to use?

Karel

PS, I have the same prob as cfernandes.

Device number: is the device number of the Generic Web Device in the tree (the parent of the Generic Proxy Orbiter device).

If you get this wrong, you'll get a 404 error from the scripts.

We can't easily port the Dusky control from Dianemo to LinuxMCE, since we diverged from the standard way of doing things. It's not easy mainly because I have no idea how this is properly done (and hence the reason why Dianemo diverged )

HI ,

i try to run  but on screen of  qtorbiter  show
error downloading  http://192.168.90.1/lmce-admin/weborbiter_image.php

if i try to open this url on browser   show 404 error ,   but this files  is on /lmce-admin

This is a problem on the web server. Are you sure you're looking at the same machine in all the cases? Look at the Apache log to see if the requests come in when you try to connect.

I also confirmed that you can't compile TouchOrbiterQt on 0810. One of the errors is fixable by adding an include. The next error can't be fixed easily because of a missing member in QNetworkRequest. Anyone willing to make a workaround is welcome to do so.

You don't need those if you connect locally. They're used for HTTP authentication. We use that in Dianemo in combination with the SSL tickbox for remotely accessing machines.

TouchOrbiterQt: cannot connect to X server

Do one of these:

- Option 1:

Run TouchOrbiterQt from the desktop (as the logged in user).

- Option 2:

export DISPLAY=:0
then run TouchOrbiterQt

If it's option 2, it's because your DISPLAY variable was deleted when you sudo'ed, or you logged in via ssh or something.

I tried those instructions with Ubuntu 11.10 alpha 2 since I had a fresh install of it in a virtualbox. I'll make a clean install of 10.04 LTS now and see if it is any different.

This bears the question: what kind of system did you attempt this on?

That depends, are you going to keep pretending that you're retarded?

Zaerc, this time around you're digging yourself a big hole on your own. I wonder what you'll do to yourself when you're the one who screwed you over.

Dude. PLEASE spend at least a year with this system yourself, before even considering deployment. This system has many moving parts.

You will need as many capture cards as there are video input sources. One video input source can be multiplexed to multiple media directors.

I tend to get very angry with people who think they can get exactly the info they need spoon fed to them, before deploying a massive installation, because these people tend to lack the in depth knowledge needed to support a large installation of this software; they tend to come screaming back to the forum when they trip up.

You have been warned.

-Thom

Actually, it doesn't matter when you start developing. Day 1 or day 3000, you'll still know nothing unless you get into code. I've been 7 years on this project, as a developer, and when I still don't know anything

If someone wants to jump head first into code, don't suggest they don't. Ever!

Source code?

Oh hey, I did it. Found out what's happening: Xine uses its own fonts. Totem uses the system's FreeType fonts.

To tell Xine to use a FreeType font for subtitles, find and set these like so in xine.conf:

subtitles.separate.font_freetype:/usr/share/fonts/truetype/freefont/FreeSansBold.ttf
subtitles.separate.font_use_freetype:1
subtitles.separate.src_encoding:iso-8859-7

Reference: http://www.xine-project.org/faq#supportedfonts

You don't even need language-support-el.

Try xine-ui on the machine where totem works fine and see what happens.

OK, I just did this on my system: set Xine to ISO-8859-7 and installed language-support-el. I downloaded a subtitle from the Internet, and even after this all I see are punctuation marks. This is on my Ubuntu 10.10 laptop.

First of all, nl isn't Greek. You want el. Specifically, you probably want language-support-el, which brings in fonts and other stuff for Greek.

Second, Intrepid is probably EOL, so it's no longer in the main archive. If that's the case, you have to edit /etc/apt/sources.list and replace archive.ubuntu.com with old-releases.ubuntu.com and apt-get update with this new address before you install anything else. If you are using a mirror, XX.archive.ubuntu.com, you have to replace the entire XX.archive.ubuntu.com with old-releases.ubuntu.com, dropping XX.

Try this and tell me if it gets you anywhere.

What's the error?

I'm not sure how to see what fonts are installed. What's the package name you use with apt-get?