Home of the Squeezebox™ & Transporter® network music players.
Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 23
  1. #11
    Senior Member
    Join Date
    Apr 2008
    Posts
    1,318
    I, for one, would like to thank you for this primer.

    Thank you very much.

    Howard


    Quote Originally Posted by CJS View Post
    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 => 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

  2. #12
    Member
    Join Date
    Dec 2018
    Location
    The Netherlands
    Posts
    87
    Quote Originally Posted by ralphy View Post
    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)
        Event code 408 (KEY_RESTART)
        Event code 409 (KEY_SLOW)
        Event code 410 (KEY_SHUFFLE)
        Event code 412 (KEY_PREVIOUS)
        Event code 416 (KEY_VIDEOPHONE)
        Event code 417 (KEY_GAMES)
        Event code 418 (KEY_ZOOMIN)
        Event code 419 (KEY_ZOOMOUT)
        Event code 420 (KEY_ZOOMRESET)
        Event code 421 (KEY_WORDPROCESSOR)
        Event code 422 (KEY_EDITOR)
        Event code 423 (KEY_SPREADSHEET)
        Event code 424 (KEY_GRAPHICSEDITOR)
        Event code 425 (KEY_PRESENTATION)
        Event code 426 (KEY_DATABASE)
        Event code 427 (KEY_NEWS)
        Event code 428 (KEY_VOICEMAIL)
        Event code 429 (KEY_ADDRESSBOOK)
        Event code 430 (KEY_MESSENGER)
        Event code 431 (KEY_DISPLAYTOGGLE)
        Event code 432 (KEY_SPELLCHECK)
        Event code 433 (KEY_LOGOFF)
        Event code 439 (KEY_MEDIA_REPEAT)
        Event code 442 (KEY_IMAGES)
        Event code 576 (KEY_BUTTONCONFIG)
        Event code 577 (KEY_TASKMANAGER)
        Event code 578 (KEY_JOURNAL)
        Event code 579 (KEY_CONTROLPANEL)
        Event code 580 (KEY_APPSELECT)
        Event code 581 (KEY_SCREENSAVER)
        Event code 582 (KEY_VOICECOMMAND)
        Event code 583 (?)
        Event code 592 (KEY_BRIGHTNESS_MIN)
        Event code 593 (KEY_BRIGHTNESS_MAX)
        Event code 608 (KEY_KBDINPUTASSIST_PREV)
        Event code 609 (KEY_KBDINPUTASSIST_NEXT)
        Event code 610 (KEY_KBDINPUTASSIST_PREVGROUP)
        Event code 611 (KEY_KBDINPUTASSIST_NEXTGROUP)
        Event code 612 (KEY_KBDINPUTASSIST_ACCEPT)
        Event code 613 (KEY_KBDINPUTASSIST_CANCEL)
      Event type 2 (EV_REL)
        Event code 6 (REL_HWHEEL)
      Event type 3 (EV_ABS)
        Event code 32 (ABS_VOLUME)
          Value      0
          Min        0
          Max      908
      Event type 4 (EV_MSC)
        Event code 4 (MSC_SCAN)
    Properties:
    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 ------------
    Quote Originally Posted by ralphy View Post
    Currently a long press of the Fn (function) key saves to the presets and pressing an Fn key selects it.
    I am aware of this, and this works well for standard PC keyboards that have a full set of Fn function keys. However this model T3 Air-Mouse RC has only 5 function keys F3 to F7 (refer to picture in post #4), and these keys are not recognizable as Function keys (and they don't have a number). So for this particular RC and similar models it would be more convenient and intuitive if presets can also be set by long pressing numerical keys 0 to 9. It was just a thought and I can understand that this feature is not on top of your todo list
    Last edited by CJS; 2020-08-13 at 13:25.
    | LMS 8.0 | Squeezebox Boom | RPi0W + pCP 6.1.0 + HiFiBerry DAC Zero | SqueezeAMP |

  3. #13
    Member
    Join Date
    Dec 2018
    Location
    The Netherlands
    Posts
    87
    Quote Originally Posted by Howard Passman View Post
    I, for one, would like to thank you for this primer.
    Thank you very much.
    Howard
    You are welcome.
    | LMS 8.0 | Squeezebox Boom | RPi0W + pCP 6.1.0 + HiFiBerry DAC Zero | SqueezeAMP |

  4. #14
    Member
    Join Date
    Dec 2018
    Location
    The Netherlands
    Posts
    87

    Response on pressing POWER button

    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 8.0 | Squeezebox Boom | RPi0W + pCP 6.1.0 + HiFiBerry DAC Zero | SqueezeAMP |

  5. #15
    Senior Member ralphy's Avatar
    Join Date
    Jan 2006
    Location
    Canada
    Posts
    2,575
    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 donations always appreciated.

  6. #16
    Member
    Join Date
    Dec 2018
    Location
    The Netherlands
    Posts
    87
    Quote Originally Posted by ralphy View Post
    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.

    PS1: 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!

    PS2: Attached zip file contains an updated version of https://github.com/ralph-irving/tcz-...er/strings.txt
    I improved the Dutch (NL) and German (DE) translation of menu item "MENU_ENABLE_POWER_ON_BUTTON_WHEN_OFF". This should help to avoid misunderstandings. I think that the Danish translation is already OK. You may want to use this updated translation for the next version of piCorePlayer => jivelite_pcp_strings.zip
    Last edited by CJS; 2020-08-20 at 08:41. Reason: Atached updated strings.txt
    | LMS 8.0 | Squeezebox Boom | RPi0W + pCP 6.1.0 + HiFiBerry DAC Zero | SqueezeAMP |

  7. #17
    Senior Member ralphy's Avatar
    Join Date
    Jan 2006
    Location
    Canada
    Posts
    2,575
    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 donations always appreciated.

  8. #18
    Member
    Join Date
    Dec 2018
    Location
    The Netherlands
    Posts
    87
    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 8.0 | Squeezebox Boom | RPi0W + pCP 6.1.0 + HiFiBerry DAC Zero | SqueezeAMP |

  9. #19
    Senior Member ralphy's Avatar
    Join Date
    Jan 2006
    Location
    Canada
    Posts
    2,575
    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 T��nd knap n��r 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 donations always appreciated.

  10. #20
    Member
    Join Date
    Dec 2018
    Location
    The Netherlands
    Posts
    87
    Quote Originally Posted by ralphy View Post
    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.

    Quote Originally Posted by ralphy View Post
    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.

    Quote Originally Posted by ralphy View Post
    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 8.0 | Squeezebox Boom | RPi0W + pCP 6.1.0 + HiFiBerry DAC Zero | SqueezeAMP |

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •