Author |
Message |
mattbatt
|
Posted: Wed Apr 15, 2015 9:23 pm |
|
Joined: Tue Aug 15, 2006 11:14 am
Posts: 1343
Location:
Orlando FL
|
This has nothing to do with anything but I keep getting an error when I install packages Code: Warning: directory permissions differ on /etc/ filesystem: 775 package: 755 should I do anything to fix this?
_________________ My System
|
|
Top |
|
|
mattbatt
|
Posted: Wed Apr 15, 2015 10:53 pm |
|
Joined: Tue Aug 15, 2006 11:14 am
Posts: 1343
Location:
Orlando FL
|
IT'S WORKING !!!!!!!! mostly... - I removed kodi and kodi-pvr-addons (just to be safe)
- Then I renamed the "kodi" directories left over to "kodeeOLD" (it's funny because it's phonetic)
- I reinstalled kodi and kodi-pvr-addons
- Remote didn't work
- I went into LinHES settings set my remote as Streamzap
- remote didn't work
- I went to Graysky's github page https://github.com/graysky2/streamzap
- I followed the directions on the readme https://github.com/graysky2/streamzap/b ... /README.md
- I think you can skip the first step of "Setup LIRC" since we are already set up with LinHES
- I did step 2 "for MythTV and mplayer" but I'm not sure if it's necessary
- I did step 3 (and this is the important one) except for the audio_switch.py
- there is a small typo it says to put Lirc.xml in ~/.kodi/userdata/ it should say Lircmap.xml
- Remote didn't work
- I used irw to capture keys as before and confirmed that the standard LinHES streamzap.conf only says "UP" "DOWN" "LEFT" and the ~/.kodi/userdata/Lircmap.xml uses "KEY_UP" "KEY_DOWN" etc. so I removed the "KEY_"s
- Remote worked!!!!!!!! yay!!!!
- except for fastfoward and rewind (BOOOOO) but we were expecting that
- I changed Lircmap.xml from "FOWARD" to ">>"
the remote stopped working all together
As an aside you don't have to restart lircd to test kodi but I did exit kodi before making changes. So what's missing is fast forward ">>", Reverse "<<", skip ahead ">>|", and skip back "<<|". I don't want to break MythTV to fix Kodi so what do I change where to fix the above.
_________________ My System
|
|
Top |
|
|
mattbatt
|
Posted: Wed Apr 15, 2015 11:54 pm |
|
Joined: Tue Aug 15, 2006 11:14 am
Posts: 1343
Location:
Orlando FL
|
OK I hacked it together now. I changed all the >> and << to FOWARD and REWIND, NEXT and PREVIOUS in /usr/MythVantage/templates/remotes/favorites/streamzap/lircd.conf.streamzap /usr/MythVantage/templates/remotes/favorites/streamzap/lircrc and ~/.kodi/userdata/Lircmap.xml In the lircrc file there were several applications that needed changing.
I know all my hard work will be erased in the next update so I need to save the files elsewhere.
_________________ My System
|
|
Top |
|
|
RacerX
|
Posted: Thu Apr 16, 2015 7:43 am |
|
Joined: Sun Sep 05, 2004 7:06 pm
Posts: 690
|
Matt
the Lircmap.xml file has to be exactly right, no syntax errors or anything like that. It's easy to make a mistake. To get it really right in the build your going to have to compare the custom one that you have to the one in the build. Pull your drive and setup R8.3 on your spare drive. SSH works good to capture the details. It's good that Graysky has some clues. Then open a ticket with the details and get t fixed in the build.
|
|
Top |
|
|
brfransen
|
Posted: Thu Apr 16, 2015 8:54 am |
|
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1194
Location:
SC
|
mattbatt,
Can you post your modified lircd.conf, lircrc, and Lircmap.xml and I will update the template.
Does the remote still work without the remote.xml? We don't currently support remote.xml in the templates.
Also, you can avoid overwrites by creating a ~/remotes/streamzap-mine dir with your modified files. Then select it in the Remotes LinHES Setting.
|
|
Top |
|
|
mattbatt
|
Posted: Thu Apr 16, 2015 8:56 am |
|
Joined: Tue Aug 15, 2006 11:14 am
Posts: 1343
Location:
Orlando FL
|
Here is my Lircmap.xml I will submit a bug tonight. Code: <!-- ~/.kodi/userdata/Lircmap.xml --> <!-- --> <!-- This file maps XBMC_buttons to LIRC_buttons --> <!-- and is works with a custom ~/.kodi/userdata/remote.xml which maps --> <!-- XBMC_buttons to actions --> <!-- --> <!-- How to add remotes --> <!-- <remote device="name_Lirc_calls_the_remote"> --> <!-- --> <!-- For the commands the layout following layout is used --> <!-- <XBMC_button>LIRC_button</XBMC_button> --> <lircmap> <remote device="Streamzap_PC_Remote"> <power>POWER</power> <play>PLAY</play> <pause>PAUSE</pause> <stop>STOP</stop> <forward>FOWARD</forward> <reverse>REWIND</reverse> <left>LEFT</left> <right>RIGHT</right> <up>UP</up> <down>DOWN</down> <pageplus>CHANNELUP</pageplus> <pageminus>CHANNELDOWN</pageminus> <select>OK</select> <back>EXIT</back> <menu>MENU</menu> <title>RED</title> <info>GREEN</info> <display>YELLOW</display> <blue>BLUE</blue> <skipplus>NEXT</skipplus> <skipminus>PREVIOUS</skipminus> <record>RECORD</record> <volumeplus>VOLUMEUP</volumeplus> <volumeminus>VOLUMEDOWN</volumeminus> <mute>MUTE</mute> <record>RECORD</record> <one>1</one> <two>2</two> <three>3</three> <four>4</four> <five>5</five> <six>6</six> <seven>7</seven> <eight>8</eight> <nine>9</nine> <zero>0</zero> </remote> </lircmap>
_________________ My System
|
|
Top |
|
|
mattbatt
|
Posted: Thu Apr 16, 2015 9:09 am |
|
Joined: Tue Aug 15, 2006 11:14 am
Posts: 1343
Location:
Orlando FL
|
OK I uploaded the 4 files you requested to Dropbox since the forum won't won't let me upload anything. https://www.dropbox.com/sh/2jqbrf6ha1vj ... Jezca?dl=0 My understanding is that kodi needs the remote.xml. the Lircmap.xml translates LIrc to the button names that Kodi uses and then the remote.xml file translates Kodi buttons to functions in Kodi. If there is no remote.xml file it will probably work in a default mode, however I noticed that the use of the up and down arrow to skip ahead when playing video in Kodi is opposite of MythTV so I will need to fix that. Now that I have a working remote I will experiment tonight after work.
_________________ My System
|
|
Top |
|
|
brfransen
|
Posted: Thu Apr 16, 2015 9:15 am |
|
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1194
Location:
SC
|
mattbatt wrote: My understanding is that kodi needs the remote.xml. the Lircmap.xml translates LIrc to the button names that Kodi uses and then the remote.xml file translates Kodi buttons to functions in Kodi. If there is no remote.xml file it will probably work in a default mode, however I noticed that the use of the up and down arrow to skip ahead when playing video in Kodi is opposite of MythTV so I will need to fix that. Now that I have a working remote I will experiment tonight after work. The default remote.xml is at /usr/share/kodi/system/keymaps/remote.xml and that is what is used for the other remotes that we have templated the Lircmap.xml. I didn't compare the remote.xml files and have no idea what the advantage is of the one you linked to. At this point I would prefer to have the Lircmap.xml work with the Kodi default remote.xml as that is what has been done with other remotes.
|
|
Top |
|
|
graysky
|
Posted: Thu Apr 16, 2015 2:56 pm |
|
Joined: Wed Dec 10, 2003 8:31 pm
Posts: 1996
Location:
/dev/null
|
I might have missed it, but what isn't working from my github? I have that same remote and it works with my files. The only thing that might be different with KM is the version of lircd it's using and the location of the remote.conf but I can't think of any other reason why it wouldn't work for you with my files.
_________________ Retired KM user (R4 - R6.04); friend to LH users.
|
|
Top |
|
|
brfransen
|
Posted: Thu Apr 16, 2015 4:52 pm |
|
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1194
Location:
SC
|
graysky, I think all your file work with each other. LH's template for the streamzap names the buttons different than you did (our lircd.conf and your streamzap.conf files and we don't use a remote.conf file at all) so mixing and matching caused the conflict.
What is the reason that you provide a remote.xml and don't use the default?
|
|
Top |
|
|
mattbatt
|
Posted: Thu Apr 16, 2015 6:30 pm |
|
Joined: Tue Aug 15, 2006 11:14 am
Posts: 1343
Location:
Orlando FL
|
I think it's because Graysky is starting from scratch not from LinHES. Graysky It was that your buttons are named "KEY_UP" and LinHES default for Streamzap is just "UP". Also the default streamzap.conf uses "<<" and ">>|" instead of "REWIND" and "SKIP" angle brackets break XML for kodi.
I noticed also in poking around in "lircrc" files for other remotes, there doesn't seem to be a standard function names for even the standard buttons like rewind and skip. It would be nice if all the remotes .conf files could output the same functions and maybe only feed one "lircrc" file. Everytime I think I start to understand how this stuff works i'm proven wrong.
_________________ My System
|
|
Top |
|
|
mattbatt
|
Posted: Thu Apr 16, 2015 8:57 pm |
|
Joined: Tue Aug 15, 2006 11:14 am
Posts: 1343
Location:
Orlando FL
|
I can confirm that kodi does work without the remote.xml file in ~/.kodi/userdata/keymap/
I had another look at /usr/share/kodi/system/Lircmap.xml Streamzap isn't listed in there. That's the reason why my remote didn't "just work" out of the box. Knowing what I do now about the >> and << buttons I could imagine that if someone had added support for Streamzap it would quickly have broken support for all remotes.
_________________ My System
|
|
Top |
|
|
graysky
|
Posted: Fri Apr 17, 2015 3:12 am |
|
Joined: Wed Dec 10, 2003 8:31 pm
Posts: 1996
Location:
/dev/null
|
Try this for me: 1) Move /etc/lirc/lirc.d.conf.d/streamzap.conf somewhere else (or where ever LH keeps the remote file). 2) Restart lircd 3) run `ir-keytable` as root and take note of the first line that contains /dev/input/something 4) Post the output of this `ir-keytable --read --device=/dev/input/something` as root. For me, my streamzap clearly has those prefixed values: Code: # ir-keytable --read --device=/dev/input/event0 scancode 0x28c0 = KEY_NUMERIC_0 (0x200) scancode 0x28c1 = KEY_NUMERIC_1 (0x201) scancode 0x28c2 = KEY_NUMERIC_2 (0x202) scancode 0x28c3 = KEY_NUMERIC_3 (0x203) scancode 0x28c4 = KEY_NUMERIC_4 (0x204) scancode 0x28c5 = KEY_NUMERIC_5 (0x205) scancode 0x28c6 = KEY_NUMERIC_6 (0x206) scancode 0x28c7 = KEY_NUMERIC_7 (0x207) scancode 0x28c8 = KEY_NUMERIC_8 (0x208) scancode 0x28c9 = KEY_NUMERIC_9 (0x209) scancode 0x28ca = KEY_POWER (0x74) scancode 0x28cb = KEY_MUTE (0x71) scancode 0x28cc = KEY_CHANNELUP (0x192) scancode 0x28cd = KEY_VOLUMEUP (0x73) scancode 0x28ce = KEY_CHANNELDOWN (0x193) scancode 0x28cf = KEY_VOLUMEDOWN (0x72) scancode 0x28d0 = KEY_UP (0x67) scancode 0x28d1 = KEY_LEFT (0x69) scancode 0x28d2 = KEY_OK (0x160) scancode 0x28d3 = KEY_RIGHT (0x6a) scancode 0x28d4 = KEY_DOWN (0x6c) scancode 0x28d5 = KEY_MENU (0x8b) scancode 0x28d6 = KEY_EXIT (0xae) scancode 0x28d7 = KEY_PLAY (0xcf) scancode 0x28d8 = KEY_PAUSE (0x77) scancode 0x28d9 = KEY_STOP (0x80) scancode 0x28da = KEY_BACK (0x9e) scancode 0x28db = KEY_FORWARD (0x9f) scancode 0x28dc = KEY_RECORD (0xa7) scancode 0x28dd = KEY_REWIND (0xa8) scancode 0x28de = KEY_FASTFORWARD (0xd0) scancode 0x28e0 = KEY_RED (0x18e) scancode 0x28e1 = KEY_GREEN (0x18f) scancode 0x28e2 = KEY_YELLOW (0x190) scancode 0x28e3 = KEY_BLUE (0x191) Enabled protocols:
_________________ Retired KM user (R4 - R6.04); friend to LH users.
|
|
Top |
|
|
RacerX
|
Posted: Fri Apr 17, 2015 7:11 am |
|
Joined: Sun Sep 05, 2004 7:06 pm
Posts: 690
|
Matt there is a reason that all the remotes are not the same. If's because in the beginning there was only keyboard and mouse supported in the OS. There was no remote and Lirc made it happen. Code was developed and sometime later depreciated due to changes in USB in the Kernel. Testing an alternative (ir-keytable) is a good thought....
|
|
Top |
|
|
mattbatt
|
Posted: Fri Apr 17, 2015 9:31 pm |
|
Joined: Tue Aug 15, 2006 11:14 am
Posts: 1343
Location:
Orlando FL
|
@Graysky your output is the same as the output I got. I was having trouble figuring out the best way to restart lircd, turns out that if you kill it in top it automatically respawns.
@RacerX I guess I was surprised to learn how much variety there is to naming the buttons in lircd I would have thought there were standard names.
_________________ My System
|
|
Top |
|
|