Ticket Created
over 5 years ago

WERETECH-7661

WERETECH-7662

WERETECH-7663

WERETECH-7853

WERETECH-7854

Assorted Media Player Button Bugs Across Devices

I've been experimenting with some of the media player button handling code across different devices and run into a few issues. Below is a table which summarizes my findings.

For context, Runcasts currently implements fast-forward/rewind using some pretty crazy hacks which re-map the skip-previous / skip-next buttons into changing the ActiveContent playhead. Needless to say, I'd love to strip that code out and use the normal approach. Unfortunately, the various options below all suffer some drawback on one of the devices we're trying to support.

Feature Vivoactive3 Button-Based Button-Based Hotkey
SystemButton BUG [1] OK OK
CustomButton OK OK BUG [2]
PLAYBACK_CONTROL_SKIP_BACKWARD/FORWARD BUG [3] OK [4] OK
  1. Image doesn't show, button doesn't work              
  2. Image shows, button event doesn't fire when clicked                    
  3. Crashes, no CIQ.YML generated
  4. Not a bug per-se, but a record-scratch occurs during skip, hacks to implement fast-forward/rewind avoid the record-scratch sound (at the expense of being slightly delayed when starting) 

rconradharris
Parents
  • over 5 years ago in reply to Jarrod.ConnectIQ

    Ahh okay, I think I understand the confusion here.

    This isn’t a bug in a current version of Runcasts, this is a bug an API (CustomMenu) that I would like to use in a future version.

    To replicate the issue you would have to have an audio player test harness which returns a `CustomMenu` object as the first item of the `PlaybackProfile.getPlaybackControls()` method.

    I might be able to provide a code example a bit later, if not of the whole player, at least a relevant `PlaybackProfile` definition.

Comment
  • over 5 years ago in reply to Jarrod.ConnectIQ

    Ahh okay, I think I understand the confusion here.

    This isn’t a bug in a current version of Runcasts, this is a bug an API (CustomMenu) that I would like to use in a future version.

    To replicate the issue you would have to have an audio player test harness which returns a `CustomMenu` object as the first item of the `PlaybackProfile.getPlaybackControls()` method.

    I might be able to provide a code example a bit later, if not of the whole player, at least a relevant `PlaybackProfile` definition.

Children