Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Clip attribute to the Chapter Object #285

Open
thebells1111 opened this issue Aug 23, 2021 · 6 comments
Open

Add Clip attribute to the Chapter Object #285

thebells1111 opened this issue Aug 23, 2021 · 6 comments

Comments

@thebells1111
Copy link
Contributor

There's been a request that I think would be beneficial to allow a podcaster to create a link to a clip of a different podcast, so when the link is clicked, the current podcast pauses, the clip is loaded and plays, then when finished, the original podcast continues. I think adding a clip attribute to the chapter object would be the easiest way to implement this.

clip (optional - object) This object defines an optional clip link that is tied to this chapter. It instructs the app to pause the podcast currently playing, load the link with the start and stop time, play the clip, then resume playing the original podcast.

clip object contains the following attibutes

url: required - string) The url of the audio file containing the clip
startTime: (required - float) The starting time of the clip
stopTime: (required - float) The stopping time of the clip
title: (optional - string) A title to show with the clip. Examples include a clip description, podcast name, episode name, etc.

@daveajones
Copy link
Contributor

This would be an easy addition to the spec. Thanks for documenting this Steven.

@saerdnaer
Copy link
Contributor

The start and stop time could also be part of the URL as specified in https://www.w3.org/TR/media-frags/ or https://podlove.org/deep-link/#appendingtimerangeinformation

The podcast specifies the selected range in the “normal play time” syntax of the Media Fragment specification:
t=[npt:][start][,end]
If you omit the start time, it defaults to the beginning of the media file, if you omit end it defaults to the end of the media file.

Here are some examples that show how the time field can be used:

t=1:35:52,1:42:16
play from 01:35:52 to 01:42:16
t=263
start playback at 4 minutes and 23 seconds
t=,24:12
play from beginning to 24 minutes and 12 seconds

For more examples and a full specification of the Normal Play Time syntax, consult the Media Fragments [1] specification.

@daveajones
Copy link
Contributor

Oh, I didn't know that stop time was a thing with MF. What url would be referenced? Just the direct mp3 enclosure url?

@thebells1111
Copy link
Contributor Author

Oh, I didn't know that stop time was a thing with MF. What url would be referenced? Just the direct mp3 enclosure url?

That's what I would do. Just create a new audio element in a modal that had the enclosurer url with #t=start, stop appended to it as the src.

@thebells1111
Copy link
Contributor Author

The start and stop time could also be part of the URL as specified in https://www.w3.org/TR/media-frags/ or https://podlove.org/deep-link/#appendingtimerangeinformation

I considered that, and ultimately, that's how I would build the enclosure url, but I was thinking adding the startTime and stopTime as two separate keys would me more consistent with the structure of the "Chapter" object and the "Soundbite" tag.

@daveajones
Copy link
Contributor

That sounds like a good solution @thebells1111

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants