You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know what I did, but the playhead tiny circle appears way off to the right. How can I fix that. I don't remember changing any settings from the default sample file from the audio section.
Question: How can I change the setting that on the RESTART (loop type button) so I can change its function to replay from 15 seconds prior the current playback time.
Question2: Is it possible to add more custom Speed increments and decrements ? eg. 0.80x 0.60x
NOTE: I mainly use MP3 for all my projects, so I removed the ogg file. I don't want to be converting files from MP3 to Ogg all the time... Is that ok?
@inglesuniversal is this available at a public URL so I could have a look at the misplaced playhead issue?
As for your questions:
The restart button wasn't intended to rewind 15 seconds - its purpose is to start over at the beginning. If you want to set the rewind and fast forward buttons to 15 seconds, add data-seek-interval="15" to the element.
In theory we could add more granularity to the playback rate. I'm not sure how granular browser support is though. I also think too many choices might burden users rather than help them. What's your use case for wanting such specific playback rates?
You're pretty safe using MP3 alone for audio. Historically the problem was Firefox, which still doesn't natively support MP3 due to patent issues, but as long as it's running on an OS that has Mp3 support, Firefox can handle it. Supported OS's include Windows Vista+ since Firefox 22.0, Android since Firefox 20.0, Firefox OS since Firefox 15.0, Linux since Firefox 26.0 (relies on GStreamer codecs) and OS X 10.7 since Firefox 35.0.
Activity
terrill commentedon Sep 17, 2017
@inglesuniversal is this available at a public URL so I could have a look at the misplaced playhead issue?
As for your questions:
joedolson commentedon Jun 16, 2025
The theme has been updated, this issue is now 8 years old with no follow-up, and was not reproducible; I think it makes sense to close.