Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2021-02-16 Thread ralphy


wtnh wrote: 
> 
> So it looks like the remote is functioning, but Jivelite is ignoring the
> 70058 code. I guess I will need to remap the codes to get it to work if
> I want to keep it?
> 
> Is this typical of RF remotes? I would have expected Enter to be
> consistent/universal.
> 
> Sorry for the RF remote newbie questions. :confused:
I don't think you'll be able to remap the Keypad Enter key without
making changes to the SDL library sources.

Yes, this is typical of the remote makers.
The Justboom remote were no different, the OK button used to crash
jivelite until I changed the SDL library to support it.



Ralphy

*1*-Touch, *5*-Classics, *3*-Booms, *2*-UE Radio
'Squeezebox client builds'
(https://sourceforge.net/projects/lmsclients/files/) 'donations'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations=LL5P6365KQEXN=CA_name=Squeezebox%20client%20builds_code=USD=PP%2dDonationsBF%3abtn_donate_SM%2egif%3aNonHosted)
always appreciated.

ralphy's Profile: http://forums.slimdevices.com/member.php?userid=3484
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix


Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2021-02-14 Thread wtnh


Thanks for the pointer. It turns out this new remote is sending a
different code for the OK and Enter keys than the one that works.

Working remote:

Code:

Event: time 1613328411.379315, type 4 (EV_MSC), code 4 (MSC_SCAN), value 
70028
  Event: time 1613328411.379315, type 1 (EV_KEY), code 28 (KEY_ENTER), value 1
  Event: time 1613328411.379315, -- SYN_REPORT 
  Event: time 1613328411.387290, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70028
  Event: time 1613328411.387290, type 1 (EV_KEY), code 28 (KEY_ENTER), value 0


Non-working new remote:

Code:

Event: time 1613328715.194926, type 4 (EV_MSC), code 4 (MSC_SCAN), value 
70058
  Event: time 1613328715.194926, type 1 (EV_KEY), code 96 (KEY_KPENTER), value 1
  Event: time 1613328715.194926, -- SYN_REPORT 
  Event: time 1613328715.298836, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70058
  Event: time 1613328715.298836, type 1 (EV_KEY), code 96 (KEY_KPENTER), value 0



So it looks like the remote is functioning, but Jivelite is ignoring the
70058 code. I guess I will need to remap the codes to get it to work if
I want to keep it?

Is this typical of RF remotes? I would have expected Enter to be
consistent/universal.

Sorry for the RF remote newbie questions. :confused:



wtnh's Profile: http://forums.slimdevices.com/member.php?userid=36993
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix


Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2021-02-14 Thread Paul Webster


wtnh wrote: 
> 
> I was wondering about a quick way to check in the logs to see if these
> keys are getting recognized?
> 

See the 2nd post in this thread.



Paul Webster
http://dabdig.blogspot.com
author of \"now playing\" plugins covering radio france (fip etc), kcrw,
supla finland, abc australia, cbc/radio-canada and rte ireland

Paul Webster's Profile: http://forums.slimdevices.com/member.php?userid=105
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix


Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2021-02-14 Thread wtnh


Just got another RF remote to try out:
https://www.amazon.com/gp/product/B0787Z1C2G/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8=1

33368

I wanted to try this one since the front side is much simpler and should
do the job for jivelite control.

All the buttons work with jivelite EXCEPT the OK button and the enter
key on the back. They do nothing. These are obviously the most important
for selections, so it is pretty useless.

I suspect it is just defective and will send it back, but I was
wondering about a quick way to check in the logs to see if these keys
are getting recognized?

Thanks


+---+
|Filename: 61HvQTA2pkL._AC_SL1001_.jpg  |
|Download: http://forums.slimdevices.com/attachment.php?attachmentid=33368|
+---+


wtnh's Profile: http://forums.slimdevices.com/member.php?userid=36993
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix


Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2021-01-18 Thread wtnh


OK - thanks. I am finding the remote pretty useful out of the box. Like
I mentioned the space bar on the keyboard side does work as a
play/pause.

BTW - I am using this one:
https://www.amazon.com/gp/product/B01M7MRMYH/ref=ppx_yo_dt_b_asin_title_o04_s00?ie=UTF8=1

Also - I discovered that the HOME button returns Jivelite to the now
playing screen. Some of the other buttons (especially the qwerty keys)
do some strange things to the interface. I have to learn to avoid them!



wtnh's Profile: http://forums.slimdevices.com/member.php?userid=36993
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix


Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2021-01-18 Thread ralphy


wtnh wrote: 
> Question for @ralphy - I recently got a similar remote to the one CJS
> has. I was pleasantly surprised when I plugged it in and it mostly
> functioned. I immediately noticed the play/pause button did not work (as
> has been noted), but that the spacebar on the qwerty keyboard side of
> the remote did work for play/pause.
> 
> I was wondering if the mapping changes you created for the CJS test
> version will make it into the main repo anytime soon, or should I try
> the workaround with the test version?
> 
> Another mapping that I could not find is having a remote button which is
> the same as tapping the music icon in the upper right of the screen so
> that I can get back to the now playing screens, so that would be a nice
> bonus.
> 
> Thanks!

No that change will not be applied to main, it conflicts with other
supported remote key mappings.  You'll need to use the test version.



Ralphy

*1*-Touch, *5*-Classics, *3*-Booms, *1*-UE Radio
'Squeezebox client builds'
(https://sourceforge.net/projects/lmsclients/files/) 'donations'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations=LL5P6365KQEXN=CA_name=Squeezebox%20client%20builds_code=USD=PP%2dDonationsBF%3abtn_donate_SM%2egif%3aNonHosted)
always appreciated.

ralphy's Profile: http://forums.slimdevices.com/member.php?userid=3484
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix


Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2021-01-17 Thread Paul Webster


wtnh wrote: 
> 
> Another mapping that I could not find is having a remote button which is
> the same as tapping the music icon in the upper right of the screen so
> that I can get back to the now playing screens, so that would be a nice
> bonus.
> 

Try a long hold on Back (top left on JiveLite when not on Home page).



Paul Webster
http://dabdig.blogspot.com
author of \"now playing\" plugins covering radio france (fip etc), kcrw,
supla finland, abc australia, cbc/radio-canada and rte ireland

Paul Webster's Profile: http://forums.slimdevices.com/member.php?userid=105
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix


Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2021-01-17 Thread wtnh


Question for @ralphy - I recently got a similar remote to the one CJS
has. I was pleasantly surprised when I plugged it in and it mostly
functioned. I immediately noticed the play/pause button did not work (as
has been noted), but that the spacebar on the qwerty keyboard side of
the remote did work for play/pause.

I was wondering if the mapping changes you created for the CJS test
version will make it into the main repo anytime soon, or should I try
the workaround with the test version?

Another mapping that I could not find is having a remote button which is
the same as tapping the music icon in the upper right of the screen so
that I can get back to the now playing screens, so that would be a nice
bonus.

Thanks!



wtnh's Profile: http://forums.slimdevices.com/member.php?userid=36993
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix


Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2020-08-23 Thread CJS


ralphy wrote: 
> I've uploaded a new test jivelite extension that should fix the
> picoreplayer applet and as an added incentive to try it, I've remapping
> the PLAYPAUSE key to PAUSE just for the test build.  Use my previous
> instructions to install it.
Hi Ralphy, good news! I have installed the updated jivelite test version
per your instructions, and everything looks OK now:

1) PLAYPAUSE button is now working as intended (press first time =>
playback is paused; press second time => playback is resumed)
2) I can navigate into the piCorePlayer menu item again
3) NL and DE translations of menu item
"MENU_ENABLE_POWER_ON_BUTTON_WHEN_OFF" are updated and OK.
4) Behavior of POWER button is OK again.

Since everything looks OK I have stored a backup of the updated test
versions of files pcp-jivelite.tcz and pcp-jivelite.tcz.md5.txt.

Thank you very much for your time and for your great support!



| LMS 7.9.3 | Squeezebox Boom | RPi0W + pCP 6.1.0 + HiFiBerry DAC+ Zero
|

CJS's Profile: http://forums.slimdevices.com/member.php?userid=68700
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix


Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2020-08-23 Thread ralphy


CJS wrote: 
> Yes, that is also what I see.
and are they the translations you expected?

CJS wrote: 
> With unplug I suppose that you mean unplug the power supply.

yes that's what I meant.

CJS wrote: 
> If I navigate to a track in my library and  press the PLAYPAUSE key then
> indeed the track starts to play, both before and after installing the
> test jivelite. If this means that you can't map KEY_PLAYPAUSE to
> KEY_PAUSE without breaking other remotes than I agree that we can better
> stop our attempts to make the PLAYPAUSE key functional.

Yes I won't be able to change the mapping in the official builds,
however.

CJS wrote: 
> 
> Observations after updating to the test jivelite extension:
> * Behaviour of PLAYPAUSE button of my remote control has not changed, it
> still behaves like a PLAY button
> * I can't enter the piCorePlayer menu item anymore
> * Behaviour of POWER button has changed. Pressing first time => Power
> off, playback stops; pressing second time => playback starts for a
> fraction of a second but then almost immediately stops again.
> After selecting a screensaver for "When off", after pressing POWER for
> the first time playback stops and the screensaver is shown. After
> pressing POWER for the second time the Now Playing screen is shown for a
> fraction of a second (and sometimes I hear a very short audio glitch)
> but then the screensaver is shown again.

I think the POWER button changes are a side effect of the picoreplayer
applet not loading, because the code in the repository jivelite build is
the same.  Otherwise, I've introduced an issue that I need to resolve
before starting on the next release.

I've uploaded a new test jivelite extension that should fix the
picoreplayer applet and as an added incentive to try it, I've remapping
the PLAYPAUSE key to PAUSE just for the test build.  Use my previous
instructions to install it.

CJS wrote: 
> 
> I am not sure why the test jivelite works different in my environment
> than in yours. Maybe it is because I have a different Raspberry Pi Model
> (ZeroW) that uses different kernel modules? I am just guessing now.
> For now the "normal" jivelite version that comes with pCP 6.1.0 works
> better for me, so I will revert to the configuration that I had before
> updating to the test jivelite. 
> Thanks for your time and let me know if you have additional questions.

Very unlikely that different kernel modules armv6 vs armv7 would cause
the problem.

To switch back to the jivelite package in the repository, if the new
test build still has issues, without having to reinstall jivelite.

Code:

tc@rpi27:~$ *ceo*
  tc@rpi27:/mnt/mmcblk0p2/tce/optional$ *wget -O pcp-jivelite.tcz 
http://repo.picoreplayer.org/repo/10.x/armv7/tcz/pcp-jivelite.tcz*
  tc@rpi27:/mnt/mmcblk0p2/tce/optional$ *wget -O pcp-jivelite.tcz.md5.txt  
http://repo.picoreplayer.org/repo/10.x/armv7/tcz/pcp-jivelite.tcz.md5.txt*
  tc@rpi27:/mnt/mmcblk0p2/tce/optional$ *pcp br*




Ralphy

*1*-Touch, *5*-Classics, *3*-Booms, *1*-UE Radio
'Squeezebox client builds'
(https://sourceforge.net/projects/lmsclients/files/) 'donations'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations=LL5P6365KQEXN=CA_name=Squeezebox%20client%20builds_code=USD=PP%2dDonationsBF%3abtn_donate_SM%2egif%3aNonHosted)
always appreciated.

ralphy's Profile: http://forums.slimdevices.com/member.php?userid=3484
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix


Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2020-08-22 Thread CJS


CJS wrote: 
> 
> => I will check what happens when I start from scratch using the
> downloaded pCP6.1.0 image, only install jivelite on the Tweaks page, and
> then update to the test jivelite. I will report back in this thread what
> is the result of this experiment.
I did this experiment. I burned the original PCP6.1.0 image to the SD
card and apart from selecting the proper audio output device on the
Squeezelite Settings page (in my case Hifiberry DAC Zero) I did not
change any setting. Then I installed the Jivelite extension on the
Tweaks page, and after reboot checked that Jivelite was working as
expected. I checked that in the piCorePlayer menu option "Enable Power
On Button when Powered Off" was enabled, and that the POWER button was
behaving according to this setting (pressing first time => Power off,
playback stops; pressing second time => Playback resumes). Then I
updated to the test jivelite extension following your instructions. 

Observations after updating to the test jivelite extension:
* Behaviour of PLAYPAUSE button of my remote control has not changed, it
still behaves like a PLAY button
* I can't enter the piCorePlayer menu item anymore
* Behaviour of POWER button has changed. Pressing first time => Power
off, playback stops; pressing second time => playback starts for a
fraction of a second but then almost immediately stops again.
After selecting a screensaver for "When off", after pressing POWER for
the first time playback stops and the screensaver is shown. After
pressing POWER for the second time the Now Playing screen is shown for a
fraction of a second (and sometimes I hear a very short audio glitch)
but then the screensaver is shown again.

I am not sure why the test jivelite works different in my environment
than in yours. Maybe it is because I have a different Raspberry Pi Model
(ZeroW) that uses different kernel modules? I am just guessing now.
For now the "normal" jivelite version that comes with pCP 6.1.0 works
better for me, so I will revert to the configuration that I had before
updating to the test jivelite. 
Thanks for your time and let me know if you have additional questions.



| LMS 7.9.3 | Squeezebox Boom | RPi0W + pCP 6.1.0 + HiFiBerry DAC+ Zero
|

CJS's Profile: http://forums.slimdevices.com/member.php?userid=68700
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix


Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2020-08-22 Thread CJS


ralphy wrote: 
> This is the commit for your changes.  And I've confirmed that the
> strings.txt file in that test jivelite extension has those two lines.
Yes, that is also what I see.

ralphy wrote: 
> I'm not sure why you can no longer navigate into the picoreplayer menu, 
> it works for me.  If you unplug picoreplayer and back in again, does it
> work then?
With unplug I suppose that you mean unplug the power supply. If I unplug
the power supply, wait a few seconds and then plug in the power supply
again then after reboot I can still not navigate into the piCorePlayer
menu item. Another observation is that after installation of the test
jivelite extension the behavior of the POWER button has changed, as if
setting "Enable Power On Button when Powered Off" has been disabled. 

Note that I now installed the test jivelite on a customized pCP
installation (installed FFmpeg libraries, Bluetooth extension, evtest
extension, hdmi-power-on-off-script, customized InputToActionMap.lua,
etc).
=> I will check what happens when I start from scratch using the
downloaded pCP6.1.0 image, only install jivelite on the Tweaks page, and
then update to the test jivelite. I will report back in this thread what
is the result of this experiment.

ralphy wrote: 
> If you navigate to an album or track in your library and press the
> PLAYPAUSE key does the selection start to play?
> If so, then the SDLK_AudioPlay key symbol, which is mapped to KEY_PLAY,
> is overriding the PLAYPAUSE change and I can't map it without breaking
> other remotes.
If I navigate to a track in my library and  press the PLAYPAUSE key then
indeed the track starts to play, both before and after installing the
test jivelite. If this means that you can't map KEY_PLAYPAUSE to
KEY_PAUSE without breaking other remotes than I agree that we can better
stop our attempts to make the PLAYPAUSE key functional.



| LMS 7.9.3 | Squeezebox Boom | RPi0W + pCP 6.1.0 + HiFiBerry DAC+ Zero
|

CJS's Profile: http://forums.slimdevices.com/member.php?userid=68700
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix


Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2020-08-22 Thread ralphy


This is the commit for your changes.  And I've confirmed that the
strings.txt file in that test jivelite extension has those two lines.


Code:

diff --git a/tcz/jivelite/piCorePlayer/strings.txt 
b/tcz/jivelite/piCorePlayer/strings.txt
  index 810d9bd..47add2f 100644
  --- a/tcz/jivelite/piCorePlayer/strings.txt
  +++ b/tcz/jivelite/piCorePlayer/strings.txt
  @@ -42,9 +42,9 @@ MENU_WAKE_ON_LAN
  
  MENU_ENABLE_POWER_ON_BUTTON_WHEN_OFF
DA  Tillad Tnd knap nr afspiller er 
slukket
  - DE  Einschaltknopf anzeigen wenn ausgeschaltet
  + DE  Einschaltknopf aktivieren wenn ausgeschaltet
EN  Enable Power On Button when Powered Off
  - NL  Toon aan/uit-knop wanneer de speler uit staat
  + NL  Aan-knop activeren wanneer de speler uit staat
  
  WOL_MENU_TITLE
DA  Wake-on-LAN



I'm not sure why you can no longer navigate into the picoreplayer menu, 
it works for me.  If you unplug picoreplayer and back in again, does it
work then?

If you navigate to an album or track in your library and press the
PLAYPAUSE key does the selection start to play?

If so, then the SDLK_AudioPlay key symbol, which is mapped to KEY_PLAY,
is overriding the PLAYPAUSE change and I can't map it without breaking
other remotes.



Ralphy

*1*-Touch, *5*-Classics, *3*-Booms, *1*-UE Radio
'Squeezebox client builds'
(https://sourceforge.net/projects/lmsclients/files/) 'donations'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations=LL5P6365KQEXN=CA_name=Squeezebox%20client%20builds_code=USD=PP%2dDonationsBF%3abtn_donate_SM%2egif%3aNonHosted)
always appreciated.

ralphy's Profile: http://forums.slimdevices.com/member.php?userid=3484
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix


Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2020-08-21 Thread CJS


Thanks Ralphy for spending time on making KEY_PLAYPAUSE functional!

I followed your instructions for installation of the test pcp-jivelite
extension. Unfortunately it does not work as expected.

These are my observations:
1) The PLAYPAUSE button still does not work, i.e. audio playback is not
paused. When I press the PlayPause button the only thing that happens is
that the jivelite GUI moves a few millimeter to the right on the
connected monitor and then within a fraction of a second moves back to
its original position.
2. I can't enter the piCorePlayer menu (Home => Settings =>
piCorePlayer) anymore. So I also can't check if the Dutch translation of
menu item "MENU_ENABLE_POWER_ON_BUTTON_WHEN_OFF" has changed. When
selecting the piCorePlayer menu item and pressing the OK button I only
see the short movement of the GUI (same as when pressing the PlayPause
button).

FYI, I copied the updated pcp-jivelite.tcz file from the pCP SD Card to
my Windows PC and inspected the content with 7-zip.
I found that /opt/jivelite/share/jive/applets/piCorePlayer/strings.txt
does contain the updated translations for menu item
"MENU_ENABLE_POWER_ON_BUTTON_WHEN_OFF"

Based on my observations, do you have an idea what goes wrong?



| LMS 7.9.3 | Squeezebox Boom | RPi0W + pCP 6.1.0 + HiFiBerry DAC+ Zero
|

CJS's Profile: http://forums.slimdevices.com/member.php?userid=68700
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix


Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2020-08-21 Thread ralphy


I've applied your menu translation changes and created a test
pcp-jivelite extension for you to try which maps the KEY_PLAYPAUSE
(keycode 164) on your remote to KEY_PAUSE.

Login to picoreplayer and run the commands in bold.

Code:


  tc@rpi37-wls:~$ *ceo*
  
  tc@rpi37-wls:/mnt/mmcblk0p2/tce/optional$ *wget -O pcp-jivelite.tcz.md5.txt 
http://ralph-irving.users.sourceforge.net/pico/pcp-jivelite.tcz.md5.txt*
  Connecting to ralph-irving.users.sourceforge.net (216.105.38.10:80)
  pcp-jivelite.tcz.md5 100% 51  0:00:00 ETA
  
  tc@rpi37-wls:/mnt/mmcblk0p2/tce/optional$ *wget -O pcp-jivelite.tcz 
http://ralph-irving.users.sourceforge.net/pico/pcp-jivelite.tcz*
  Connecting to ralph-irving.users.sourceforge.net (216.105.38.10:80)
  pcp-jivelite.tcz 100% 7136k  0:00:00 ETA
  
  tc@rpi37-wls:/mnt/mmcblk0p2/tce/optional$ *md5sum -c pcp-jivelite.tcz.md5.txt*
  pcp-jivelite.tcz: OK
  
  # Backup your config, if needed.
  tc@rpi37-wls:/mnt/mmcblk0p2/tce/optional$ *pcp bu*
  [ INFO ] Backing up files to /mnt/mmcblk0p2/tce/mydata.tgz/
  Done.
  [ OK ] Backup successful.
  
  # Reboot
  tc@rpi37-wls:/mnt/mmcblk0p2/tce/optional$ *pcp rb*




Ralphy

*1*-Touch, *5*-Classics, *3*-Booms, *1*-UE Radio
'Squeezebox client builds'
(https://sourceforge.net/projects/lmsclients/files/) 'donations'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations=LL5P6365KQEXN=CA_name=Squeezebox%20client%20builds_code=USD=PP%2dDonationsBF%3abtn_donate_SM%2egif%3aNonHosted)
always appreciated.

ralphy's Profile: http://forums.slimdevices.com/member.php?userid=3484
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix


Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2020-08-20 Thread CJS


ralphy wrote: 
> You should be able to fix the KEY_POWER behaviour in jivelite go to
> settings->picoreplayer->enable power on button when powered off and save
> and restart jivelite.
After enabling the Power On button in Settings -> Picoreplayer the Power
button behaviour is indeed as I want it. Thanks Ralphy.

PS: The reason that I did not select the proper setting for the Power
button is that I was wrong-footed by an incorrect translation (normally
I have the Dutch language (Nederlands) selected in Jivelite advanced
settings).
English text says: "*Enable* Power On Button when Powered Off"
While the Dutch text says (translated back to English): "*Show* Power
On/Off Button when Player is Powered Off".

Anyway everything is OK now. Thanks again for your time!



| LMS 7.9.3 | Squeezebox Boom | RPi0W + pCP 6.1.0 + HiFiBerry DAC+ Zero
|

CJS's Profile: http://forums.slimdevices.com/member.php?userid=68700
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix


Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2020-08-20 Thread ralphy


First thanks for the keycode for the KEY_PLAYPAUSE.  A generic key
symbol is already defined for it in SDL, so I should just need to update
the jive_framework.c file to map it.

KEY_POWER has several special handlers in jivelite, where as KEY_Q does
not follow the same code path.

You should be able to fix the KEY_POWER behaviour in jivelite go to
settings->picoreplayer->enable power on button when powered off and save
and restart jivelite.



Ralphy

*1*-Touch, *5*-Classics, *3*-Booms, *1*-UE Radio
'Squeezebox client builds'
(https://sourceforge.net/projects/lmsclients/files/) 'donations'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations=LL5P6365KQEXN=CA_name=Squeezebox%20client%20builds_code=USD=PP%2dDonationsBF%3abtn_donate_SM%2egif%3aNonHosted)
always appreciated.

ralphy's Profile: http://forums.slimdevices.com/member.php?userid=3484
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix


Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2020-08-19 Thread CJS


One more question about the response of Jivelite/LMS on pressing button
KEY_POWER on my RF/USB remote control. The response on pressing this
button is not as I expected.

I made following observation:
In file InputToActionMap.lua, keys["q"] and [KEY_POWER] are both mapped
on action "power":

charActionMappings.press
["q"]  = "power",

keyActionMappings.press
[KEY_POWER] = "power",

Yet the reaction of LMS on pressing q and pressing KEY_POWER appears to
be different:

- pressing q *toggles power* (pressing q first time => power off,
  pressing q again => power on)
- pressing KEY_POWER gives *power off* (pressing KEY_POWER first time
  => power off, pressing KEY_POWER again => player stays off).
  To power the player on after pressing KEY_POWER I need to press a
  different key, for example a numerical key or the KEY_HOMEPAGE
  button.
  
My preference would be that pressing KEY_POWER toggles power.
*Question to Raplhy*: Can it be explained why pressing the POWER button
results in a different action than pressing q?

For completeness the full output of evtest on pressing KEY_POWER after
selecting event2 is given below:

Code:

sudo evtest
  No device specified, trying to scan all of /dev/input/event*
  Available devices:
  /dev/input/event0:  FREEWAY TECHNOLOGY RFIC-MOUSE Keyboard
  /dev/input/event1:  FREEWAY TECHNOLOGY RFIC-MOUSE Consumer Control
  /dev/input/event2:  FREEWAY TECHNOLOGY RFIC-MOUSE System Control
  /dev/input/event3:  FREEWAY TECHNOLOGY RFIC-MOUSE
  /dev/input/event4:  FREEWAY TECHNOLOGY RFIC-MOUSE
  Select the device event number [0-4]: 2
  Input driver version is 1.0.1
  Input device ID: bus 0x3 vendor 0x25a7 product 0x2402 version 0x101
  Input device name: "FREEWAY TECHNOLOGY RFIC-MOUSE System Control"
  Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
  Event code 116 (KEY_POWER)
  Event code 139 (KEY_MENU)
  Event code 142 (KEY_SLEEP)
  Event code 143 (KEY_WAKEUP)
  Event type 4 (EV_MSC)
  Event code 4 (MSC_SCAN)
  Properties:
  Testing ... (interrupt to exit)
  Event: time 1597609964.535842, type 4 (EV_MSC), code 4 (MSC_SCAN), value 10081
  Event: time 1597609964.535842, type 1 (EV_KEY), code 116 (KEY_POWER), value 1
  Event: time 1597609964.535842, -- SYN_REPORT 
  Event: time 1597609964.686864, type 4 (EV_MSC), code 4 (MSC_SCAN), value 10081
  Event: time 1597609964.686864, type 1 (EV_KEY), code 116 (KEY_POWER), value 0
  Event: time 1597609964.686864, -- SYN_REPORT 


Thanks in advance for your reply, and I hope that I am not asking too
much of your time.



| LMS 7.9.3 | Squeezebox Boom | RPi0W + pCP 6.1.0 + HiFiBerry DAC+ Zero
|

CJS's Profile: http://forums.slimdevices.com/member.php?userid=68700
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix


Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2020-08-13 Thread CJS


Howard Passman wrote: 
> I, for one, would like to thank you for this primer. 
> Thank you very much.
> Howard
You are welcome.



| LMS 7.9.3 | Squeezebox Boom | RPi0W + pCP 6.1.0 + HiFiBerry DAC |

CJS's Profile: http://forums.slimdevices.com/member.php?userid=68700
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix


Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2020-08-13 Thread CJS


ralphy wrote: 
> Maybe I could remap KEY_PLAYPAUSE to KEY_PAUSE for the next picoreplayer
> release, but I don't have a remote that generates a KEY_PLAYPAUSE
> event.
> What are the scancodes reported by evtest for it? 
It would be very nice if you could consider this for the next pCP
release.

Running evtest, selecting event1 and then pressing button KEY_PLAYPAUSE
gives the following output.
First only the output after pressing button KEY_PLAYPAUSE:

Code:

Testing ... (interrupt to exit)
  Event: time 1597347865.699200, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00cd
  Event: time 1597347865.699200, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), 
value 1
  Event: time 1597347865.699200, -- SYN_REPORT 
  Event: time 1597347865.851171, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00cd
  Event: time 1597347865.851171, type 1 (EV_KEY), code 164 (KEY_PLAYPAUSE), 
value 0
  Event: time 1597347865.851171, -- SYN_REPORT 



For completeness also the full output of evtest:

Code:

sudo evtest
  No device specified, trying to scan all of /dev/input/event*
  Available devices:
  /dev/input/event0:  FREEWAY TECHNOLOGY RFIC-MOUSE Keyboard
  /dev/input/event1:  FREEWAY TECHNOLOGY RFIC-MOUSE Consumer Control
  /dev/input/event2:  FREEWAY TECHNOLOGY RFIC-MOUSE System Control
  /dev/input/event3:  FREEWAY TECHNOLOGY RFIC-MOUSE
  /dev/input/event4:  FREEWAY TECHNOLOGY RFIC-MOUSE
  Select the device event number [0-4]: 1
  Input driver version is 1.0.1
  Input device ID: bus 0x3 vendor 0x25a7 product 0x2402 version 0x101
  Input device name: "FREEWAY TECHNOLOGY RFIC-MOUSE Consumer Control"
  Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
  Event code 1 (KEY_ESC)
  Event code 28 (KEY_ENTER)
  Event code 74 (KEY_KPMINUS)
  Event code 78 (KEY_KPPLUS)
  Event code 103 (KEY_UP)
  Event code 105 (KEY_LEFT)
  Event code 106 (KEY_RIGHT)
  Event code 108 (KEY_DOWN)
  Event code 110 (KEY_INSERT)
  Event code 111 (KEY_DELETE)
  Event code 113 (KEY_MUTE)
  Event code 114 (KEY_VOLUMEDOWN)
  Event code 115 (KEY_VOLUMEUP)
  Event code 116 (KEY_POWER)
  Event code 119 (KEY_PAUSE)
  Event code 120 (KEY_SCALE)
  Event code 128 (KEY_STOP)
  Event code 130 (KEY_PROPS)
  Event code 131 (KEY_UNDO)
  Event code 133 (KEY_COPY)
  Event code 134 (KEY_OPEN)
  Event code 135 (KEY_PASTE)
  Event code 136 (KEY_FIND)
  Event code 137 (KEY_CUT)
  Event code 138 (KEY_HELP)
  Event code 139 (KEY_MENU)
  Event code 140 (KEY_CALC)
  Event code 142 (KEY_SLEEP)
  Event code 144 (KEY_FILE)
  Event code 150 (KEY_WWW)
  Event code 152 (KEY_SCREENLOCK)
  Event code 155 (KEY_MAIL)
  Event code 156 (KEY_BOOKMARKS)
  Event code 158 (KEY_BACK)
  Event code 159 (KEY_FORWARD)
  Event code 161 (KEY_EJECTCD)
  Event code 163 (KEY_NEXTSONG)
  Event code 164 (KEY_PLAYPAUSE)
  Event code 165 (KEY_PREVIOUSSONG)
  Event code 166 (KEY_STOPCD)
  Event code 167 (KEY_RECORD)
  Event code 168 (KEY_REWIND)
  Event code 169 (KEY_PHONE)
  Event code 171 (KEY_CONFIG)
  Event code 172 (KEY_HOMEPAGE)
  Event code 173 (KEY_REFRESH)
  Event code 174 (KEY_EXIT)
  Event code 176 (KEY_EDIT)
  Event code 177 (KEY_SCROLLUP)
  Event code 178 (KEY_SCROLLDOWN)
  Event code 181 (KEY_NEW)
  Event code 182 (KEY_REDO)
  Event code 206 (KEY_CLOSE)
  Event code 207 (KEY_PLAY)
  Event code 208 (KEY_FASTFORWARD)
  Event code 209 (KEY_BASSBOOST)
  Event code 210 (KEY_PRINT)
  Event code 212 (KEY_CAMERA)
  Event code 216 (KEY_CHAT)
  Event code 217 (KEY_SEARCH)
  Event code 219 (KEY_FINANCE)
  Event code 223 (KEY_CANCEL)
  Event code 224 (KEY_BRIGHTNESSDOWN)
  Event code 225 (KEY_BRIGHTNESSUP)
  Event code 228 (KEY_KBDILLUMTOGGLE)
  Event code 229 (KEY_KBDILLUMDOWN)
  Event code 230 (KEY_KBDILLUMUP)
  Event code 231 (KEY_SEND)
  Event code 232 (KEY_REPLY)
  Event code 233 (KEY_FORWARDMAIL)
  Event code 234 (KEY_SAVE)
  Event code 235 (KEY_DOCUMENTS)
  Event code 240 (KEY_UNKNOWN)
  Event code 241 (KEY_VIDEO_NEXT)
  Event code 244 (KEY_BRIGHTNESS_ZERO)
  Event code 256 (BTN_0)
  Event code 353 (KEY_SELECT)
  Event code 354 (KEY_GOTO)
  Event code 358 (KEY_INFO)
  Event code 362 (KEY_PROGRAM)
  Event code 366 (KEY_PVR)
  Event code 370 (KEY_SUBTITLE)
  Event code 372 (KEY_ZOOM)
  Event code 374 (KEY_KEYBOARD)
  Event code 376 (KEY_PC)
  Event code 377 (KEY_TV)
  Event code 378 (KEY_TV2)
  Event code 379 (KEY_VCR)
  Event code 380 (KEY_VCR2)
  Event code 381 (KEY_SAT)
  Event code 383 (KEY_CD)
  Event code 384 (KEY_TAPE)
  Event code 386 (KEY_TUNER)
  Event code 387 (KEY_PLAYER)
  Event code 389 (KEY_DVD)
  Event code 392 (KEY_AUDIO)
  Event code 393 (KEY_VIDEO)
  Event code 396 (KEY_MEMO)
  Event code 397 (KEY_CALENDAR)
  Event code 398 (KEY_RED)
  Event code 399 (KEY_GREEN)
  Event code 400 (KEY_YELLOW)
  Event code 401 (KEY_BLUE)
  Event code 402 (KEY_CHANNELUP)
  Event code 403 (KEY_CHANNELDOWN)
  Event code 405 (KEY_LAST)
  Event code 407 (KEY_NEXT)
  

Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2020-08-13 Thread Howard Passman


I, for one, would like to thank you for this primer. 

Thank you very much.

Howard


CJS wrote: 
> For people that use a simular RF/USB remote control to control
> piCorePlayer via Jivelite I have attached a zip file with following
> content:
> >   >   > 
  - Original InputToActionMap.lua file that comes with Jivelite
  - Modified InputToActionMap.lua that changes the function of a few
  > buttons on the Remote Control, as discussed in my previous post
  - Excel sheet that shows the keycodes that are generated by the
  > model T3 remote control
  - README.txt file that explains how to install the modified
  > InputToActionMap.lua in piCorePlayer. This text file also contains
  > some extra information about how to use evtest for detection of
  > keycodes that are generated by a RF/USB remote control.
  > > > 
> Attachment => 31253
> 
> 
> HOW TO INSTALL A CUSTOM INPUTTOACTIONMAP.LUA FILE FOR JIVELITE IN
> PICOREPLAYER
> Instructions below make use of Win32DiskImager, Putty and WinSCP on a
> Windows PC. Also it is assumed that Jivelite is installed in
> piCorePlayer, and that the Joggler skin is used.
> Lines that start with $ are commands that are entered on the Putty
> commandline.
> 
> 1) First make a backup image of the piCorePlayer SD card using
> Win32DiskImager. To minimize the file size of the image select "Read
> Only Allocated Partitions" in Win32DiskImager.
> 
> 2) Boot piCorePlayer and SSH into piCorePlayer using Putty:
> login as: tc
> password: piCore
> 
> 3) Create folder temp in /home/tc
> $ mkdir temp
> 
> 4) Create folder jive in /home/tc/.jivelite/userpath
> $ cd /home/tc/.jivelite/userpath
> $ sudo mkdir jive
> 
> 5) Copy customized InputToActionMap.lua from Windows PC to
> piCoreplayer using WinSCP. Copy InputToActionMap.lua to folder
> /home/tc/temp that was created in step 3.
> 
> 6) Copy InputToActionMap.lua from folder temp to folder
> /home/tc/.jivelite/userpath/jive
> $ cd /home/tc/temp
> $ sudo cp InputToActionMap.lua ../.jivelite/userpath/jive
> 
> 7) Quit Jivelite, by pressing key o at the back side of the T3 Remote
> Control.
> Jivelite should restart automatically and pick up the custom
> InputToActionMap.lua file
> 
> 8) Check that the modified remote control keys work as expected.
> If the Jivelite GUI does not start, SSH into pCP and delete the custom
> InputToActionMap.lua from folder /home/tc/.jivelite/userpath/jive as
> follows
> $ sudo rm /home/tc/.jivelite/userpath/jive/InputToActionMap.lua
> 
> 9) This is an optional step to reduce data that is saved to SD card in
> the next step.
> If the modified keys work as expected, SSH into piCorePlayer again and
> remove InputToActionMap.lua from folder temp:
> $ cd temp
> $ rm InputToActionMap.lua
> 
> 10) Save the customized key map
> /home/tc/.jivelite/userpath/jive/InputToActionMap.lua to SD card using
> your Remote Control: 
> Jivelite HOME => Settings => piCorePlayer => Save Settings to SD Card
> This saves piCorePlayer settings to SD card, including all files under
> /home/tc. These settings are restored when booting PiCorePlayer
> 
> 11) Reboot piCorePlayer by selecting  "Reboot piCorePlayer" in the
> same piCorePlayer menu
> 
> 12) Double check that the modified keys work as expected.
> 
> Regards,
> CJS



Howard Passman's Profile: http://forums.slimdevices.com/member.php?userid=16674
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix


Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2020-08-13 Thread ralphy


CJS wrote: 
> I was thinking, when you make the next update of Jivelite for
> piCorePlayer (maybe for the next version of piCorePlayer?), can you
> consider to add "KEY_PLAYPAUSE" to the jive framework and to
> InputToActionMap.lua? This would help people that use an RF remote
> control like myself. Let me know if it would help when I create an issue
> at https://github.com/ralph-irving/tcz-jivelite/issues.

Maybe I could remap KEY_PLAYPAUSE to KEY_PAUSE for the next picoreplayer
release, but I don't have a remote that generates a KEY_PLAYPAUSE
event.
What are the scancodes reported by evtest for it? 

CJS wrote: 
> Also, for setting presets 0 to 9, it would be convenient if this could
> be done by long-pressing numerical keys 0 to 9 at the front side of the
> remote control. This is how presets 1 to 6 can be set on the front panel
> of the Squeezebox Boom. Is this something that could be implemented in a
> next release of tcz-jivelite without breaking existing functionality?

Currently a long press of the Fn (function) key saves to the presets and
pressing an Fn key selects it.



Ralphy

*1*-Touch, *5*-Classics, *3*-Booms, *1*-UE Radio
'Squeezebox client builds'
(https://sourceforge.net/projects/lmsclients/files/) 'donations'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations=LL5P6365KQEXN=CA_name=Squeezebox%20client%20builds_code=USD=PP%2dDonationsBF%3abtn_donate_SM%2egif%3aNonHosted)
always appreciated.

ralphy's Profile: http://forums.slimdevices.com/member.php?userid=3484
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix


Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2020-08-13 Thread Paul Webster


Looks like a useful remote at a reasonable price.
I'm interested to see how it works after you have used it for a while -
i.e. build quality



Paul Webster
http://dabdig.blogspot.com
author of \"now playing\" plugins covering radio france (fip etc), kcrw,
supla finland, abc australia, cbc/radio-canada and rte ireland

Paul Webster's Profile: http://forums.slimdevices.com/member.php?userid=105
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix


Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2020-08-13 Thread CJS


Hi Ralphy,

I was thinking, when you make the next update of Jivelite for
piCorePlayer (maybe for the next version of piCorePlayer?), can you
consider to add "KEY_PLAYPAUSE" to the jive framework and to
InputToActionMap.lua? This would help people that use an RF remote
control like myself. Let me know if it would help when I create an issue
at https://github.com/ralph-irving/tcz-jivelite/issues.

Also, for setting presets 0 to 9, it would be convenient if this could
be done by long-pressing numerical keys 0 to 9 at the front side of the
remote control. This is how presets 1 to 6 can be set on the front panel
of the Squeezebox Boom. Is this something that could be implemented in a
next release of tcz-jivelite without breaking existing functionality?

Kind regards, CJS.



| LMS 7.9.3 | Squeezebox Boom | RPi0W + pCP 6.1.0 + HiFiBerry DAC |

CJS's Profile: http://forums.slimdevices.com/member.php?userid=68700
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix


Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2020-08-11 Thread CJS


For people that use a simular RF/USB remote control to control
piCorePlayer via Jivelite I have attached a zip file with following
content:

- Original InputToActionMap.lua file that comes with Jivelite
- Modified InputToActionMap.lua that changes the function of a few
  buttons on the Remote Control, as discussed in my previous post
- Excel sheet that shows the keycodes that are generated by the model
  T3 remote control
- README.txt file that explains how to install the modified
  InputToActionMap.lua in piCorePlayer. This text file also contains
  some extra information about how to use evtest for detection of
  keycodes that are generated by a RF/USB remote control.
  
Attachment => 31253


HOW TO INSTALL A CUSTOM INPUTTOACTIONMAP.LUA FILE FOR JIVELITE IN
PICOREPLAYER
Instructions below make use of Win32DiskImager, Putty and WinSCP on a
Windows PC. Also it is assumed that Jivelite is installed in
piCorePlayer, and that the Joggler skin is used.
Lines that start with $ are commands that are entered on the Putty
commandline.

1) First make a backup image of the piCorePlayer SD card using
Win32DiskImager. To minimize the file size of the image select "Read
Only Allocated Partitions" in Win32DiskImager.

2) Boot piCorePlayer and SSH into piCorePlayer using Putty:
login as: tc
password: piCore

3) Create folder temp in /home/tc
$ mkdir temp

4) Create folder jive in /home/tc/.jivelite/userpath
$ cd /home/tc/.jivelite/userpath
$ sudo mkdir jive

5) Copy customized InputToActionMap.lua from Windows PC to piCoreplayer
using WinSCP. Copy InputToActionMap.lua to folder /home/tc/temp that was
created in step 3.

6) Copy InputToActionMap.lua from folder temp to folder
/home/tc/.jivelite/userpath/jive
$ cd /home/tc/temp
$ sudo cp InputToActionMap.lua ../.jivelite/userpath/jive

7) Quit Jivelite, by pressing key o at the back side of the T3 Remote
Control.
Jivelite should restart automatically and pick up the custom
InputToActionMap.lua file

8) Check that the modified remote control keys work as expected.
If the Jivelite GUI does not start, SSH into pCP and delete the custom
InputToActionMap.lua from folder /home/tc/.jivelite/userpath/jive as
follows
$ sudo rm /home/tc/.jivelite/userpath/jive/InputToActionMap.lua

9) This is an optional step to reduce data that is saved to SD card in
the next step.
If the modified keys work as expected, SSH into piCorePlayer again and
remove InputToActionMap.lua from folder temp:
$ cd temp
$ rm InputToActionMap.lua

10) Save the customized key map
/home/tc/.jivelite/userpath/jive/InputToActionMap.lua to SD card using
your Remote Control: 
Jivelite HOME => Settings => piCorePlayer => Save Settings to SD Card
This saves piCorePlayer settings to SD card, including all files under
/home/tc. These settings are restored when booting PiCorePlayer

11) Reboot piCorePlayer by selecting  "Reboot piCorePlayer" in the same
piCorePlayer menu

12) Double check that the modified keys work as expected.

Regards,
CJS


+---+
|Filename: T3_Jive_keymap.zip   |
|Download: http://forums.slimdevices.com/attachment.php?attachmentid=31253|
+---+


| LMS 7.9.3 | Squeezebox Boom | RPi0W + pCP 6.1.0 + HiFiBerry DAC |

CJS's Profile: http://forums.slimdevices.com/member.php?userid=68700
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix


Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2020-08-10 Thread CJS


ralphy wrote: 
> There is a Quit menu item at the bottom of the main menu in jivelite. 
> Alternatively, you can press the small letter o to quit immediately. 
> Picoreplayer will restart jivelite automatically.
Thanks Ralphy. I had earlier hidden Quit from the HOME menu, that is why
I did not see it... Pressing letter o indeed works.

> Unfortunately, you can't add new key codes in InputToActionMap.lua as
> all keys must be registered in the jive framework C source first, which
> then requires recompiling jivelite and as you discovered if jivelite
> doesn't recognize the key code it won't start.
> 
> The Fn (function) keys are 'reassigned in the framework'
> (https://github.com/ralph-irving/jivelite/blob/master/src/jive_framework.c#L102)
> to KEY_PRESET_n so you should be able to map
> 
> > 
Code:

  >   > [KEY_PRESET_3] = "go_search",

> > 
Following your suggestion I have modified the behavior of function keys
F3 to F7 by means of following changes to sections
keyActionMappings.press as well as keyActionMappings.hold in
InputToActionMap.lua:

Code:

[KEY_PRESET_3] = "go_search",
  [KEY_PRESET_4] = "disabled",
  [KEY_PRESET_5] = "disabled",
  [KEY_PRESET_6] = "disabled",
  [KEY_PRESET_7] = "disabled", 


FYI, the reason for disabling the coloured function keys F4 to F7 is
that these keys are programmed to function as "Source Select" keys for
my Stereo set when the RC operates in IR mode. For selecting a different
input source for my Stereo, I need to long-press one of these function
keys in IR mode. It happened a few times that I long-pressed one of
these keys for selecting a different input source for my Stereo,
assuming that the RC was operating in IR mode, while in reality the RC
was operating in RF mode. By disabling the function keys in RF mode it
is avoided that presets are accidentally changed.

Apart from changing the behavior of the function keys I also modified
the mapping of the special characters for setting presets 1 to 9. I did
this because the order of special characters on this T3 Remote Control
is different from the order that is used on standard PC/Laptop
keyboards, refer to picture below:

31247

I changed the mapping of special characters to presets by selecting the
special character that is physically located directly below the
corresponding numerical key.
Following changes were made to section charActionMappings.press in
InputToActionMap.lua:


Code:

--  [")"]  = "set_preset_0",
["!"]  = "set_preset_1",
["^"]  = "set_preset_2",
["#"]  = "set_preset_3",
["$"]  = "set_preset_4",
["%"]  = "set_preset_5",
["&"]  = "set_preset_6",
["*"]  = "set_preset_7",
["("]  = "set_preset_8",
[")"]  = "set_preset_9",



With this mapping I can set presets 1 to 9 by means of the Remote
Control. Only limitation is that preset 0 (corresponding with preset 10
in LMS) cannot be set with the RC.

> If the KEY_PLAYPAUSE doesn't respond as KEY_PLAY or KEY_PAUSE  you won't
> likely be able to map it without modifying the SDL library and
> recompiling it and jivelite.
Not being a programmer,  at this moment in time I consider modification
of source code and recompilation of Jivelite a step to far. It is a pity
that I can't pause/play audio with the PLAYPAUSE key at the front side
of the RC, but I can still do this by using the SPACE bar at the back
side. This is a limitation that I can live with.

Thanks again Ralphy for your help! If there are piCorePlayer users that
own a similar RC are interested in the modified InputToActionMap.lua
file, just let me know in this forum topic. On request I can provide the
modified InputToActionMap.lua file including detailed installation
instructions.


+---+
|Filename: T3_Air-Mouse_keyboard.jpg|
|Download: http://forums.slimdevices.com/attachment.php?attachmentid=31247|
+---+


| LMS 7.9.3 | Squeezebox Boom | RPi0W + pCP 6.1.0 + HiFiBerry DAC |

CJS's Profile: http://forums.slimdevices.com/member.php?userid=68700
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix


Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2020-08-09 Thread ralphy


There is a Quit menu item at the bottom of the main menu in jivelite. 
Alternatively, you can press the small letter o to quit immediately. 
Picoreplayer will restart jivelite automatically.

Unfortunately, you can't add key codes in InputToActionMap.lua as all
keys must be registered in the jive framework C source first, which then
requires recompiling jivelite and as you discovered if jivelite doesn't
recognize the key code it won't start.

The Fn (function) keys are 'reassigned in the framework'
(https://github.com/ralph-irving/jivelite/blob/master/src/jive_framework.c#L102)
to KEY_PRESET_n so you should be able to map


Code:

[KEY_PRESET_3] = "go_search",



If the KEY_PLAYPAUSE doesn't respond to KEY_PLAY or KEY_PAUSE  you won't
likely be able to map it without modifying the SDL library and
recompiling it and jivelite.



Ralphy

*1*-Touch, *5*-Classics, *3*-Booms, *1*-UE Radio
'Squeezebox client builds'
(https://sourceforge.net/projects/lmsclients/files/) 'donations'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations=LL5P6365KQEXN=CA_name=Squeezebox%20client%20builds_code=USD=PP%2dDonationsBF%3abtn_donate_SM%2egif%3aNonHosted)
always appreciated.

ralphy's Profile: http://forums.slimdevices.com/member.php?userid=3484
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix


Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2020-08-08 Thread CJS


Hi Ralphy,

ralphy wrote: 
> 'This post'
> (https://forums.slimdevices.com/showthread.php?103330-Jivelite-for-piCorePlayer=938026=1#post938026)
> documents how to find the keycode generated for the keys you want to
> change ...
With the help of your instructions and the evtest program I found the
keycodes of all buttons that are located at the front of the T3 RF
remote control. The picture below shows the keycode for each button, as
well as the input / event (event0, event1, event2) on which the keycode
is received.

31226 

ralphy wrote: 
>  ... and 'this one'
> (https://forums.slimdevices.com/showthread.php?105117-lirc-rpi-gpio-IR-support-for-picoreplayer=883651=1#post883651)
> outlines how to modify the jivelite key mapping in picoreplayer.
I am struggling with this step. After extracting the default
InputToActionMap.lua file from /tce/optional/pcp-jivelite.tcz, I
modified the content of this file. My plan was to change c.q. create
following key mappings (keycode => wanted action):

Code:

[KEY_PLAYPAUSE] = "pause",
  [KEY_F3] = "go_search",
  [KEY_F4] = "disabled",
  [KEY_F5] = "disabled",
  [KEY_F6] = "disabled",
  [KEY_F7] = "disabled",
  


As it happens to be, none of these 6 keycodes exist in the default
InputToActionMap.lua file, even if jivelite does respond on pressing the
F3 to F7 function keys by playing presets 3 to 7. It seems that (for
example) key code [KEY_F3] is mapped on action "play_preset_3", even if
code [KEY_F3] is not defined in InputToActionMap.lua. Since the 6
keycodes did not exist I added the code shown above to the end of
section "keyActionMappings.press", and copied the modified
InputToActionMap.lua to
/home/tc/.jivelite/userpath/jive/InputToActionMap.lua, as instructed in
the linked post (btw I first created folder jive since this folder did
not exist under /home/tc/.jivelite/userpath) :

ralphy wrote: 
> Just copy the modified InputToActionMap.lua to
> /home/tc/.jivelite/userpath/jive/InputToActionMap.lua and "quit
> jivelite". When it automatically restarts jivelite will use your version
> instead of the one in the tcz package.
=> Can you )Ralphy' or anybody elsre tell me how to "quit jivelite"?
Since I did not know how to do this, I rebooted pCP expecting that
jivelite would pick up the modified InputToActionMap.lua. But the
respons of jivelite on the 6 added keycodes had not changed, and when I
used winscp to check the contents of folder /home/tc/.jivelite/userpath
it appeared that folder jive with the modified InputToActionMap.lua file
had dissapeared. It seems like folder /home/tc/.jivelite is recreated
after reboot? In a second attempt, I again copied the modified
InputToActionMap.lua to folder /home/tc/.jivelite/userpath/jive, but
before rebooting pCP I stored settings to SD card via the Jivelite GUI.
In this case after rebooting pCP, at the end of the boot process the
jivelite GUI did not appear on the screen. Maybe this is because
jivelite does not recognize the 6 added keycodes?

I noticed that in this case file
/home/tc/.jivelite/userpath/jive/InputToActionMap.lua was there. After
deleting folder /home/tc/.jivelite/userpath/jive the jivelite GUI did
appear on the screen.

Can anybody tell me what I should do to create the 6 custom keymappings
mentioned above?


+---+
|Filename: T3_RF_RC_keycodes_front_buttons.png  |
|Download: http://forums.slimdevices.com/attachment.php?attachmentid=31226|
+---+


| LMS 7.9.3 | Squeezebox Boom | RPi0W + pCP 6.1.0 + HiFiBerry DAC |

CJS's Profile: http://forums.slimdevices.com/member.php?userid=68700
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix


Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2020-08-06 Thread CJS


ralphy wrote: 
> 'This post'
> (https://forums.slimdevices.com/showthread.php?103330-Jivelite-for-piCorePlayer=938026=1#post938026)
> documents how to find the keycode generated for the keys you want to
> change and 'this one'
> (https://forums.slimdevices.com/showthread.php?105117-lirc-rpi-gpio-IR-support-for-picoreplayer=883651=1#post883651)
> outlines how to modify the jivelite key mapping in picoreplayer.
Thanks raplhy for providing links to essential informaton on this
subject!
I will give it a try and report back in this thread. This may take a few
days though due to other activities.



| LMS 7.9.3 | Squeezebox Boom | RPi0W + pCP 6.1.0 + HiFiBerry DAC |

CJS's Profile: http://forums.slimdevices.com/member.php?userid=68700
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix


Re: [SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2020-08-06 Thread ralphy


'This post'
(https://forums.slimdevices.com/showthread.php?103330-Jivelite-for-piCorePlayer=938026=1#post938026)
documents how to find the keycode generated for the keys you want to
change and 'this one'
(https://forums.slimdevices.com/showthread.php?105117-lirc-rpi-gpio-IR-support-for-picoreplayer=883651=1#post883651)
outlines how to modify the jivelite key mapping in picoreplayer.



Ralphy

*1*-Touch, *5*-Classics, *3*-Booms, *1*-UE Radio
'Squeezebox client builds'
(https://sourceforge.net/projects/lmsclients/files/) 'donations'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations=LL5P6365KQEXN=CA_name=Squeezebox%20client%20builds_code=USD=PP%2dDonationsBF%3abtn_donate_SM%2egif%3aNonHosted)
always appreciated.

ralphy's Profile: http://forums.slimdevices.com/member.php?userid=3484
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix


[SlimDevices: Unix] [piCorePlayer] Customization of RF remote control keys?

2020-08-05 Thread CJS


Dear Squeezebox community,

I have a few question about the possibility to customize RF remote
control keys in piCorePlayer. But let me start with describing my pCP
setup.

I built a Squeezebox player using a Raspberry Pi ZeroW board in
combination with piCorePlayer. I can control pCP with a smartphone
control app (I am using Squeeze Ctrl on an Android phone), but also
wanted to be able to control pCP using an RF remote control. To
accomplish this I installed the Jivelite extension in pCP, and bought an
RF remote control to control Jivelite. The Jivelite screen is displayed
on my TV via the HDMI output of the RPi ZeroW.

The RF remote control that I bought is a "model T3" device that is
described here: https://forum.kodi.tv/showthread.php?tid=278842 . This
remote is sold on Aliexpress for circa 10 US dollar, for example here:
https://www.aliexpress.com/item/4000671247122.html . It is actually a
multi-function remote control that can be switched between RF mode (in
this mode it can also work as a mouse) and IR mode. I am using the RF
mode for remote control of piCorePlayer via Jivelite, and the IR mode
for remote control of my Stereo set. The remote comes with an RF
receiver in the form of an USB dongle, that is connected to the USB port
of my RPi ZeroW using an USB to micro-USB adapter cable.

After connecting the RF receiver to the USB port of the RPi ZeroW, RF
remote control was working immediately (i.e. without installing LIRC or
IR tools for Jivelite), and most keys at the front side of the remote
have a function. So remote control is actually working quite well, but
if possible I would like to change the function of a few keys. For
example, with the existing key mapping, somehow I unintentially changed
presets a few times. I think I can avoid this by removing c.q. changing
the function of the 4 coloured buttons at the front side of the remote.
Also I would like to change the behavior of the pause/play button, i.e.
give it the same function as the space bar at the bottom side of the
remote.

Finally here are my questions:
1) Where in piCorePlayer is the mapping of RF remote control keys
defined? Is it in piCore Linux or in Jivelite?
2) Does anybody know if it is possible to customize the key mapping? If
so, how?
3) Is there a linux tool to detect the key code of RF remote control
keys? I suppose that I first need to know the key code of a specific key
before I can map the key on another action.

Thanks in advance for your help.



| LMS 7.9.3 | Squeezebox Boom | RPi0W + pCP 6.1.0 + HiFiBerry DAC |

CJS's Profile: http://forums.slimdevices.com/member.php?userid=68700
View this thread: http://forums.slimdevices.com/showthread.php?t=112709

___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix