On any examples, start_song parameter in config have no effet.
In any examples, putting "start_song" parameter have no effet. It will always set first song to index 0.
Setting "start_song":3 in the Amplitude.init object lead to have in the debug object : start_song: ""
Reproduce:
- Take the "Blue Playlist" example
- In the Amplitude init, add "start_song":3
- Load the page
- Push the big Play/Pause button. It will play song index 0
Pen showing that it doesn't work: https://codepen.io/jacob-raccuia/pen/jOqpBZv
I just moved this into the 5.3 release. Thanks for putting together a link for replication!
Thank you too!
Question // potential feature request - I am setting the starting time of the player on initialization. As of right now (and to get around this bug above), this is my code. If there was a option for start_song_time or so, would it be a better implementation? Or is it essentially going to be the same thing as this, where you set the song and then set the timestamp?
I don't love the below solution either because it autoplays on SkipTo, which I don't necessarily want to do.
callbacks: {
initialized: function() {
Amplitude.skipTo(100, 5);
}
}
Hey @jacobraccuia,
I created a feature request for you here: https://community.serversideup.net/t/set-start-time-of-song-on-initialization/198
If you want to see this feature, I would suggest creating an account on the forum and voting for the feature.

We're in the process of moving all of our feature requests to our forum so we can get a better understanding of demand for new features.
Regarding continuing the discussion of the "start @ time of song" feature, it would be a great help to continue the conversation on the forum so it keeps our discussions organized.
I would like to keep this thread focused on the "start_song parameter" issue.
Thanks! 👍
Thanks @jaydrogers. I have chosen this library for my (relatively large) project, and I imagine I will be in the code quite a bit. I will make feature requests there and keep the bug reports here!