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 - esev

Pages: 1 ... 4 5 [6]
Are the problems for non-pluto DVD screens documented anywhere?  The two buttons I mentioned at the start of the topic (Stop and Menu) didn't seem to be doing the correct thing.  My question was mainly aimed at trying to confirm whether this was a bug in the Orbiter buttons, or if the buttons were intended to work this way and I needed to modify my IR template accordingly.  It sounds like this might be a bug rather than something that was intended.

The other thing I noticed was the track/channel next and track/channel previous buttons were using the same icon (rather than opposite pointing arrows).  I figured this was a bug and wasn't intended.

Could one of the LinuxMCE project leaders confirm/reject that there is a bug on the the non-pluto DVD Orbiter screens for Stop and Menu?

Thom's response might not have been what I was looking for, but after viewing some of the tutorials I have a better understanding of how to fix the issues.  I have some equipment to test with (Blu-ray player and Roku) and would be willing to develop a fix that works with my devices.

I am trying to create a device template to control my Blu-ray player using an infrared transmitter.  When I created the template, it was populated with input boxes for several commands that DVD/Blu-ray players have in common (Media Ctrl and On Screen Menu Navigation).  Almost all of the IR codes I entered work as I'd expect, but there are two commands, "#95 Stop" and "#86 Menu (Show Menu)", that I'm having trouble with.  If I enter the IR codes for those commands, then try to press the "Stop" or "Menu" buttons on an Orbiter, nothing happens.

If I look at the log for the infrared transmitter device, I see "Could not find Infrared Code for Command 87" when I press the Menu button on the Orbiter, and I see "Could not find Infrared Code for Command 763" when I press the Stop button on the Orbiter.

I must not be understanding how the Orbiter buttons are supposed to be mapped to the device commands.  Is there a reason the Stop button on the Orbiter doesn't map to command #95, and the Menu buttion on the Orbiter doesn't map to command #86?  If so, why are input boxes for commands #95 and #86 displayed automatically when a new DVD/Blu-ray device is created rather than commands #87 and #763?

My apologies if this is already documented somewhere.  I did search the wiki and forums before posting this question, but wasn't able to find an answer.

Thank you,

Users / Re: Gyration GYR4101US Air Music Remote
« on: October 07, 2010, 07:30:26 am »
With TSHACK and MerkWerk's help on IRC tonight I managed to get this remote working on my system.  I've updated the trac ticket with the technical details of what needs to be done.

I also created a page for the remote on the on the wiki.  The Wiki page is a work in progress, but it contains step by step instructions for getting the remote working with the current version of 0810.

Please provide feedback if you are (or aren't) able to get this working on your setup.

Glad to help.  Good advice on launching from KDE.  Thanks!

Is this related to your Trac ticket?

If I remember correctly (I'm not in front of my setup right now), I found it after launching MythTV on the Media Director.  It was in the on screen MythTV Settings>General>General menu.  I remember I had to press Next 3-4 times before reaching the setting.  Enabling the Network Control Port and setting it to 10001 fixed this issue for me.  Beware though, I had to do this quickly as LinuxMCE will kill MythTV after about a minute until this setting was in place.

Thanks for mentioning that.  I ended up using schedulesdirect and everything on the backend (on my hybrid/core) works great.  But because Canada isn't supported in the LinuxMCE setup, I had to configure MythTV manually rather than letting LinuxMCE auto configure everything for me.

Later, when I created my MDs, MythTV wouldn't auto launch on the MDs and exited after about a minute.  From the responses I've received, it appears that if you cannot complete the LinuxMCE MythTV setup (and end up choosing Don't Auto Configure option) the mythfrontend settings needed for LinuxMCE to control MythTV on the MDs are never configured.  LinuxMCE then kills the mythfrontend after about a minute because it cannot be controlled.  Configuring the "Network Control Port" option manually on the MD solves this issue for me.

I'll look into what it would take to get the initial setup working for Canada using SchedulesDirect.  But it would be nice if there was also an option in LinuxMCE to auto configure everything in MythTV except for the guide data or tuner inputs.

I'm hesitant to just disable the "Don't Auto Configure" option because of the troubles another user had:

Thanks for the response posde.  When I initially setup LinuxMCE, the setup recommended having MythTV not auto configured by LinuxMCE.  I think this is due to not having a XML guide source for Canada.  Would it be possible to have a 'Autoconfigure MythTV except for guide data' option that configures all the input/capture cards and all the settings except for the lineup/guide/channel options?

Users / Re: Gyration GYR4101US Air Music Remote
« on: October 06, 2010, 05:52:30 am »
Thanks for the suggestion.  I opened a ticket.  If I find time to work on this I'll post updates on the ticket.


Is that still the case if LinuxMCE isn't managing MythTV?  I live outside the US and wasn't able to have LinuxMCE auto configure MythTV for me (ie, the 'Dont Auto Configure' box is selected in my MythTV Plugin device).  I just attributed my issue to that setting.  But now I'm realizing the MythTV_Player is an entirely different device.  Maybe something else is messed up with my setup.  I thought it was strange that everything worked out of the box on my Hybrid/Core but not on my diskless MDs.

Users / Re: Gyration GYR4101US Air Music Remote
« on: October 06, 2010, 02:36:42 am »
Attached is the patch from the previous message applied to the kernel.  If I remember correctly, all buttons except for the ones at the top (TV, PC, CAB/SAT, AUX, etc) are recognized and interpreted by the kernel with this driver.  That should make it 'easy' for someone to create a template for the remote in LinuxMCE.  I haven't had time to work in this recently, but maybe someone else can pick up where I left off...

** edit 2010/10/07 - removed the attachment.  See the Trac ticket for the latest version

I've had this happen under 0810 too on both my MDs (not the hybrid core).  In my case, the MythTV setting for the "Network Control Port" (Settings>General>General) was not enabled and not set to 10001.  Enabling it and setting the port to 10001 solved the problem for me.

Users / Re: Gyration GYR4101US Air Music Remote
« on: October 05, 2010, 03:29:33 pm »
I haven't had time to get them completely working, but I have three of these in my setup. I found that backporting this patch got the kernel to recognize almost all of the keys on the remote.

I haven't had time to look into how to map the key presses to something useful in LinuxMCE, but using the "GO Cordless GC1005M" template almost everything works.  The one annoying thing that doesn't work currently is the green menu button in the center, but I think that's just a matter of mapping the right key in the device template.

I haven't even tried to get the LCD to do anything useful.  It would be nice if it could operate as a mini-orbiter.  But I suspect it would take a lot of reverse engineering to get working properly.

I'll post the changes I made to the HID driver tonight when I get home from work.

Pages: 1 ... 4 5 [6]