2009-02-12, 22:47
sircube Wrote:Hi, any news on this?
I've been sick and haven't had a chance yet to test the updated version of XBMChelper. If anyone gets to it before me, feel free to post your results here. I'll try to give it a go tonight.
sircube Wrote:Hi, any news on this?
Brandroid Wrote:Hey Maestro, I finally got a chance to program some sequences into my Harmony 550. XBMChelper confirms that they are firing, however they aren't being recognized by XBMC as valid keymappings.
Here is the XBMChelper log showing three sequences properly executed by the remote.
Brandroid Wrote:Then the XBMC log showing the error while trying to fire these when viewing fullscreen video. And for good measure, here's the console log.
Can you think of a reason why XBMC wouldn't recognize the keymappings?
MaestroDD Wrote:Hi Brandroid,
It seems that the first log (from xbmchelper) doesn't match the other 2 (timestamps differ). For me it looks like you still use the old xbmchelper for Launcher/MultiFinder. Did you copy the new xbmchelper (the one that produced the good log) to /Applications/MultiFinder.app/Contents/Resources/ so it gets used by MultiFinder?
Brandroid Wrote:[...]sure, I'll try to:
Can you explain a little about the XBMChelper app? I had a feeling the error was probably mine, but I wasn't able to find any documentation on it in the wiki. I was under the impression that it was just a tool for diagnosing problems.
[...]
sircube Wrote:Brandroid,
still struggling with Harmony programming. I have the good results with Apple Remote for universal remote commands but not with sequence programmed in Hamrony One.
How have you captured the stop_hold event? As a RAW command? Or have you used the "analyzed" way for capturing it?
cheers,
sircube
Brandroid Wrote:[..]Settings in XBMC for the remote are currently ignored on ATV, but the 500ms is default for xbmchelper. To debug the problem you can again use xbmchelper standalone and check the timestamps. e.g.:
I did notice the occasional hiccup. Maybe one out of five times, the sequence would not be recognized (the volume would move up or down). What should I have my delay set to within the system preferences of XBMC? It's currently set to 500ms. If I increase it, will it improve the likelihood of the sequence firing properly? Universal mode is set to "always running." Do these settings sound good to you?
[...]
2009-02-17 20:42:02.002 xbmchelper[190] [DEBUG] Starting sequence with token 14
2009-02-17 20:42:02.002 xbmchelper[190] (released) Menu holding
2009-02-17 20:42:02.502 xbmchelper[190] [DEBUG] XBMCClientWrapperImpl::sendSequence: sent sequence 14 as button 8
2009-02-17 20:42:04.238 xbmchelper[190] (pressed) Volume up
MaestroDD Wrote:was just slow: Menu_H was pressed 20:42:02.002, Volume up followed 20:42:04.238, which is 2.2 seconds later and thus 1.7 seconds too late.
Please test it with xbmchelper first and check if the sequences are recognized. If they are properly recognized there and not while xbmc is running, it has maybe something to do with the load on the ATV and needs further testing and new ideas