Let the product do the talking.
Give a shopper a closer look at a product demonstration. Let staff bring up the right supporting clip when the conversation needs it.
A product worth a closer look. A story worth hearing. Give a compatible button a video, an audio clip or a playlist. Lucy plays it once, then returns to your normal screen story.
Give a shopper a closer look at a product demonstration. Let staff bring up the right supporting clip when the conversation needs it.
Invite visitors to choose a short film or an audio story. Their chosen moment plays once, then the display returns to its usual programme.
Bring up a chosen playlist, a team announcement or a useful explanation. Keep the normal schedule ready to continue afterwards.
A compatible USB or Bluetooth controller supplies ordinary keyboard input. Lucy connects that key to the action you choose.
Select a screen in Lucy. Open More screen actions (⋯), beside Publish screen, then choose Button triggers.
Use Learn key when the controller is connected to the computer running the editor. For a controller connected to a remote player, enter its configured key manually. A and B make a simple starting point.
Pick a video, an audio clip or a playlist. Choose whether clip sound follows its saved setting or is switched on or off. Configure up to 16 bindings for the screen.
Enable button triggers and the bindings you want, then save. Use Publish screen to send the configuration and its content to the player.
When the chosen content finishes, Lucy returns to the normal playlist or current schedule. Your saved screen assignment stays in place.
The managed Lucy Player receives and verifies button content when you publish. Each configured press starts from saved content, without a cloud request for every press.
Paused screens and rest hours ignore button input. Held keys, repeats and further presses during an active button action are ignored too.
Bring the right button to the right player. Use Lucy Player 0.4.15 or later. Check your controller’s keyboard output, media decoding and audio output on the intended hardware before rollout. A controller that sends ordinary keys is the starting point; compatibility depends on the device.
Use a compatible USB or Bluetooth controller that behaves like an ordinary keyboard. Match each button to its configured key, such as A or B. The controller and its key output must be supported by your player; check your intended hardware before rollout.
Choose an uploaded video, a supported MP3, M4A or WAV audio clip, or a whole playlist. Video and audio play to their natural end; a selected playlist plays through once. Clip sound can inherit the saved setting or be switched on or off. Audio format and output support depend on the player.
Lucy returns to the normal playlist or whichever schedule is current. When the normal content has not changed, playback resumes its place. The button action does not replace your saved playlist or schedule.
On the managed Lucy Player, button content is published with the screen and verified in its local cache. Playing a configured button does not require a new cloud request for each press. Publishing changes and normal online account checks still use your connection. Live streams and connected widgets need their data connection.
Buttons are ignored while the screen is paused or outside its playing hours. Holding a key or sending repeat events does not start extra playbacks. Further presses are ignored while a button action is already playing.
Give a button something worth playing. Keep the rest of your screen story moving with Lucy.