EventGhost

The logs brought some light into the dark. First of all: it's not a far-reaching COM problem, as I guessed first. That's the good news. The bad news: It's probably still out of my reach.

I can see from the logs that setup and connection to DVBViewer using COM works all right in your environment. The error happens when the plugin tries to fetch the channel list from DVBViewer via COM interface.

The following error happens: "'ascii' codec can't decode byte 0xc4 in position 9: ordinal not in range(128)".
This is a common Python error, it happens when one tries to convert a unicode string containing special characters into an ASCII string (the ASCII character set has only 128 characters and NO special characters like ┬ú├º├®├¿├ñ├Â├╝ etc.). The bad thing is: this happens not in the DVBViewer plugin code (which I have more or less under control), but in the COM interface or in the generated stub code. So I don't see a chance to fix it by myself.

And I'm still in doubt WHY it can happen: The plugin as well as the COM interface can well handle unicode characters (= special chars) in general. Channel names as well as channel group names may contain special characters, they all are handled as unicode strings (I've tried by myself before).

However, at this time I assume it's somehow related to your channel list. In your place, I'd do the following:
- put the current channel list away (you may keep it as backup). The location is C:\ProgramData\CMUV\DVBViewer\channels.dat and channels.bak
- start from scratch with a blank channel list (delete channels.dat and channels.bak before) and do a channel scan again
- if you want, you can send me your channel list and I can try to reproduce it here (afterwards we know for sure if it's really the channel list or if my assumption is wrong)
- browse your current channel list and have an open eye for strange looking channel names / special characters in it (however, as I said, special characters in channel names are not a problem in general)

hope that helps. I'm rather confident that we can fix it, sooner or later

Great to hear!

Now when I think of it, this is starting to sound very plausible: There is actually one channel which may have an '├ñ' and '├Â' in it's name (I live in Finland), even '&' and '/'. It's actually a crappy channel I've used to put to the first place (number zero), so that the remote's buttons would work like they should, starting from channel number one.

Have to check this when I get back there in a couple of weeks. I did a channel rescan earlier, but didn't delete the old list.

Hi,

It's me bugging you again. Unfortunately it seems that the problem still persists

I deleted C:\ProgramData\CMUV\DVBViewer\channels.dat and channels.bak (even the two favourite files), did a rescan, deleted the channel with funny characters. Restarted DVBViewer and EG between each phase. Actually I tried starting DVBViewer with no channel list at all. Every time there's the same error in EG.

There are parentheses in about every other Finnish channel name, hopefully that's not the problem.

I attached my channel lists, though I'm not sure if it's of any use based on what I said above.

Any ideas next?

@pflox: may I lead your attention to this thread, which I think could concern your plugin: viewtopic.php?f=4&t=5333

Thank you

With the newest Version of DVBViewer (5.2.8.1) I got this Message in my Eventghost log. Seems that the new Version comes with changes in the COM-Interface. If I fall back to the former Version of DVBViewer (5.2.7) all is fine.

09:56:28 Failed to initialize COM interface: '{CA8A3ACB-6635-4399-8967-C9BA40F719EA}'

Deleting the content in the gen_py folder fixes the problem.

C:\Users\USERNAME\AppData\Roaming\EventGhost\gen_py

http://www.dvbviewer.tv/forum/topic/531 ... eventghost

Solved here http://www.dvbviewer.tv/forum/topic/531 ... interface/

You need to delete the COM device in C:\Users\USERNAME\AppData\Roaming\EventGhost\gen_py or under XP C:\Documents and Settings \ USERNAME \ Application Data\EventGhost\gen_py

I now have a problem with the exit command, it doesn't close Dvbviewer.

All OK with 5.2.7.

I don't know if this has been asked here before, but the DVB-Viewer always starts when i just hit a button (Example: "Forward-Button"), that is related to the program in eventghost. That's a bit too sensitive to me
Any idea why this happens or how to prevent it?

Do you use context folders?

Hey

If you're talking about commands and events in folders: yes
I tried the other way because I expected a solution here, but it didn't help
More precisely, I use the folder structure given by the plugin.

Stupidly, i also can't use the x10 driver inside the dvb-viewer, because the program crashes then :/

edit: okay i read about the context folder now. created it and put the stuff in. dvbviewer seems to start anyway..

You need to activate/deactivate the DVB folder.

When you are on desktop, the DVBViewer folder must be deactivated. Use the "Enable exclusive" command to enable the keyboard folder triggered by an event desktop related.
I use the yellow button to "enable exclusive" the DVB Viewer and launch the program.
Put all your folders under the Context Folder, except for those you won't deactivate.

Bye.

Hm, so I always have to switch between these two modes? That's not acceptable to me. Where is the problem to deactivate that "autostart"?
If this is the only solution, I'll try to get that dvbviewer x10 plugin working. Yes, it also doesn't work at the moment. ^^
(DVB-Viewer crashes while starting with that plugin)

You don't switch manually, eventghost does it automatically.
Each application has its own folder, under "context Folder".
Ex: you start eventghost, all folders are deactivated by default, except for Keyboard command.
Press yellow button -> trigger on Enable Exclusive DVBViewer Folder and launch program DVBViewer.
On Exit DVBVIewer, trigger on Enable Exclusive Keyboard Folder (something like "Desktop.enabled"), and you're back at start point.

Now i don't remember all details, but this is the sense.

Don't enable plug-in in DVBViewer, but configure in the correct way the plug-in DVBViewer in Eventghost.

Sorry, that it took a month for the answer

Pressing the yellow button is still manually to me, not?
The problem is, that I don't always start it by remote, so this is a leak in the concept.
Best would be, if there wasn't an autostart-function. I don't understand the sense of it anyway.
But maybe I still don't understand.

Windows can do IT for you. Don't need eventghost.