Skip to content

Settings and activity

8 results found

  1. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Joseph Kesselman commented  · 

    As a stopgap, of course, you can implement this as an Intent in your own application -- but until/unless your app is allowed to use Name-Free Interaction, you'd have to prefix it with then name. "Alexa, tell mySkillName to rewind one minute."

    You can implement it by starting a new audio play with the offset adjusted appropriately, making sure not to go to a negative offset.

    Two points to note:

    1) StartOverIntent is a standard no-name operation which can be implemented as "reset offset to 0"; that handles "Alexa, restart".

    2) Specifying the offset as something deep in the audio file (minute 45 of an hour-long MP3, for example) will sometimes result in a very long delay before sound can start playing, especially if that audio isn't already locally cached. Basically, with a compressed format like standard MP3, the only way to move to a specific offset is to decompress sequentially through the file until that point is reached, basically doing a high-speed silent fetch-and-playback -- and for a long jump that can burn a lot of compute resource. Unfortunately I've found no way to determine whether that decompression delay will occur, so I have my choice of either always warning people that they may have to wait or never warning them; neither is ideal. (I'd settle for having it play a "scrubbing tape" sound effect quietly during the process, so the user can tell something is being done...)

    There are probably alternative compression formats which divide the file into separately compressed fixed-time-length chunks and so can speed up this fast-forward-long-distance process, but I don't know whether the Alexa supports any of those.

    So... basically, as things stand now, the human factors of fast forward/rewind may leave something to be desired, even if you're willing to use "ask skill to". I've left them disabled in my own skill for that reason, pending a better solution.

  2. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Joseph Kesselman commented  · 

    When developing with the Jovo toolkit, one of the supported options for early test and debugging is to have the skill's handler be a "webhook" URI which then forwards to an instance of the skill code running on your own machine. That doesn't require opening firewalls. Presumably something similar could be done for other development tools. There are some possible issues in terms of securing the webhook mechanism against abuse, admittedly, but this is one possible way to run the service on your private box.

  3. 60 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Joseph Kesselman supported this idea  · 
  4. 59 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Joseph Kesselman supported this idea  · 
  5. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Joseph Kesselman shared this idea  · 
  6. 175 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Joseph Kesselman supported this idea  · 
  7. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Joseph Kesselman shared this idea  · 
  8. 596 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Joseph Kesselman commented  · 

    It seems incredible that this capability isn't yet available to developers, but a websearch isn't finding it in APIs, "My Media", or anywhere else I've checked.

    The docs claim:

    The Alexa Music, Radio, and Podcast Skill API enables you to:
    Integrate your service with Alexa so that users can play music, radio, or podcasts from your catalog on Alexa-enabled devices.
    Integrate your service with Alexa features like setting music alarms, multi-room music, and more.
    [...]

    but I'm not seeing an example of that integration.

    Joseph Kesselman supported this idea  ·