Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - mactalla

Pages: [1]
scratch that.  Its not working again.
It seems to work or not at random should the IR LEDs on the sensor bar be affected by lighting conditions in the room?
It's the only thing I can think of that would cause it to work and then not work so erratically.

The sensor bar emits two infrared lights.  The wiimote uses a camera to "see" these two light points.  The wiimote has a filter to only let pass infrared so the light from your TV doesn't confuse it.  However, sunlight and also lightbulbs will pass this filter.  If you have an actual wii, you can actually view what the wiimote is seeing to find what other lightsource it's picking up.  If there are other points of light (say reflection from a lightbulb) then the pointer will usually jump or flicker.  If it gets washed out so it can't identify points of light, it will stop moving.

Can I assume when your wiimote stops moving it is when you're poining towards your windows?

Installation issues / Re: Beta 0810 and nvidia drivers
« on: October 26, 2009, 05:45:39 pm »
It hangs now and again for a few seconds,

That sounds suspiciously like an xrandr problem I've seen.  I don't have an 8.10 machine running right now so I can't confirm.  While in KDE, open up System Settings -> Service Manager and look for "Detecting RANDR (monitor) changes" and turn it off if it's running.  xrandr had (has?) a bug that when it queries monitors on the outputs the screen freezes briefly.


Do you have a link to more info re the issue you mention?

/niz23  Comment #41 has a nice summary of the issue.  Comment #50 points to the trigger in the code (and the corresponding fix) but looking at the bug status this isn't resolved in Kubuntu proper until 9.04.

Installation issues / Re: 0810 - MD HDD Install?
« on: October 26, 2009, 03:15:58 pm »
Have a look at

darrenmason's suggestion looks like the most straightforward method, but AFAIK no one's tried it yet.  Alternatively there's my brute-force method on the wiki linked to from that thread.

Installation issues / Re: Beta 0810 and nvidia drivers
« on: October 26, 2009, 02:01:11 pm »
It hangs now and again for a few seconds,

That sounds suspiciously like an xrandr problem I've seen.  I don't have an 8.10 machine running right now so I can't confirm.  While in KDE, open up System Settings -> Service Manager and look for "Detecting RANDR (monitor) changes" and turn it off if it's running.  xrandr had (has?) a bug that when it queries monitors on the outputs the screen freezes briefly.


Installation issues / Re: Setup of Wii Remote
« on: May 07, 2009, 05:45:22 am »
Will somebody do the legwork, based on the HID remote notes I have dumped in the Gyration thread, and make a device template that uses wminput to handle the wiimote? preferrably someone who has a mobile orbiter in use?

First of all, please forgive me for any noob questions.  I can get around Linux and C++ well enough, but I'm very new to LinuxMCE with a recently setup core, MD, wiimote and no orbiter.  Ideally these questions are already answered somewhere and you can just point.  However I have not yet found them.  When things make sense, I think a clear step-by-step wiki page is in order.  I can certainly help with that.

I appreciate the valuable info you put in the other thread.  Could you point me to additional information for creating device templates?

I took a stab at a device template based on what I could find in the wiki, which sadly wasn't much.  I looked at the webadmin for creating device templates and aside from not understanding many of the fields, based on comments in the forums here it seems clear that's only one piece of the puzzle.

As a starting point, I would like to know the top-level flow of events and from there can ask more informed questions / more likely to figure things out on my own.

Let's take our case here of the Wii remote.  I assume there are two levels of polish for the device template for lack of a better term.  The first would be to have the buttons do what we want (ala create a Play/Pause key being the top priority here, methinks).  The more complete version would also handle creating the wminputd script, wminputd.conf, etc as described on the wiki so that when it's detected all those things are setup automatically.  Am I correctly understanding the scope of responsibility for device templates?

Let's focus on the first level of polish as the remainder is clearly laid out on the wiki and should be easy to automate.

My first question is associating a device with a template.  When creating the template I see you can specify a MAC range, etc.  How can I tell that the device has been associated with the template?  I assume one of the log files would contain that info?  Where/which one?

When a template is loaded it reads the mapping and configuration as you pointed out in your post.  Mapping is irrelevant for the Wiimote task as the wminputd.conf is doing the mapping.  So configuration is the only one we're interested in for this case.

You mentioned the syntax for configuration is:
RemoteMapping_Entry,x scancode,UDH,Y

The UDH,Y portions are clear (thanks to your post).  x scancode is the same as keycode, correct?  For some reason I thought scancodes were more raw than even keycodes, but xev is only showing the keycode and keysym, so perhaps I'm mistaken there.

The RemoteMapping_Entry I'm not clear on.  You provided an example of a RemoteMapping entry early in your post, but I missed where this is actually defined, whether this needs to be defined for every template, or where to find the list of existing mappings for standard actions (like Play/Pause).

Now with those pieces, it looks like making the right entries in #59 Configuration - Default Value would do the trick (assuming there's an existing RemoteMapping to point to).

So where do the changes for bluetooth & bluetooth_dongle code enter the picture?  (Your post here: said those are needed too).

Long post, but I hope it makes sense.  I'll write a wiki article when I understand things myself.

Users / Re: (Unsupported) disked MD on the wiki
« on: April 21, 2009, 02:08:43 am »
That sounds like a good approach.  Given that mine's working, I'm not keen on re-doing it.  But if anyone does do it, that should replace the instructions on the wiki.

Users / (Unsupported) disked MD on the wiki
« on: April 17, 2009, 02:17:36 am »
This question has come up numerous times (I should know -- I searched a lot when trying to set it up myself!)  I'm sure the devs are tired of the question.  I got mine working, so posted on the wiki how I did it.  Hopefully it'll help others who need it.

A reminder: This is unsupported; do not pester the devs with any questions related to this.  Thanks / Fixes / Problems should be kept to the wiki page and this thread.  The first two are preferred :)

The page in question is here:


Installation issues / Re: Setup of Wii Remote
« on: April 14, 2009, 06:30:46 pm »
I'm having issues with the Alpha list on the right.  when I click a letter on the right it just takes me to the top of the list.  Anyone heard of that?

Yes. It happens, if your list of displayed titles contains non-printable characters. It happened to me, when I imported a bunch of MP3 with tags. Some titles where spanish or french, and there were problems with umlauts as well. After fixiing those using the web admin, things went smooth.

I'm seeing the same thing.  Thanks for explaining the cause.  I won't bother with it, then.  (probably at least half my music has non-ASCII characters)

Users / Re: WIIMOTE Howto on the wiki
« on: April 13, 2009, 01:50:21 am »
3. It is currently not mapped. one of the things that needs to be worked out by adventurous hackers like yourself, and us.

Where should I be looking to find the mapping of keys to behaviour?  I see I can map a wiimote button to KEY_PLAYPAUSE, but that doesn't seem to affect the loaded media.  Does LMCE have a mapping somewhere that needs to link this key to the play/pause command sent to Xine?  Where would I find that?

Users / On-screen orbiter performance on an eee Box
« on: April 12, 2009, 06:53:05 pm »
I know several people here have setup an M/D using an eee box.  I recently picked one up and am in the process of setting it up.  I'm using a B202 with UI2 w/ masking running 810 Alpha2.  Videos seem to play fine so far (I'm still figuring out the interface, like how to pause/resume or set subtitles, etc but that's irrelevant here).  My problem is that browsing media (the whole box rotation animation) is unbearably slow.  Are other eee box owners experiencing the same thing?  I couldn't find anyone mentioning it, so I'm hoping some people have it working smoothly.  Did you have to do anything to get it to run smoothly?  I noticed that OrbiterGL takes up >70% of the CPU the entire time while trying to flip the cube.

A follow-up question if no one has it working smoothly; can I disable the animation?  WebAdmin has an option for NoEffects which I'm hoping would turn that off.  But for the life of me, I can't find here in the forums, wiki, or Google what parameter that option sets.  I'm not running a diskless M/D (can't run a cable to that room) so I need to set it manually.


Pages: [1]