by ArtW » Wed May 04, 2016 6:23 pm
I actually needed a "speed up" when I recorded lectures at school some years ago. I did it manually in an audio editing program. I was able to save about 15%-20% of my time when re-listening to the material.I imagine that both speed up and slow down would be useful to people.
I don't have much need for speed up/slow down these days but here is my opinion. I lean toward the per song setting and only change the speed for the duration of the audio clip. I'd imagine most people would use it for podcasts/audio book/voice recordings and most would listen to it only once in a while. This way you do not need to save the setting per song anywhere on the server unless you plan to save it in the audio file somehow.
I'm not sure about the need for the global setting. After all I think it is unlikely that someone would need to globally affect the speed of all of their recordings. But... if someone has an audiobook with multiple chapters it would probably be convenient to set it once and forget for the duration of the book rather then adjust if for every chapter(file). Perhaps a "per album" setting or for the duration of the album? Of course the "on until turned off" per album/per file setting would require more management in the back-end where as global or per file duration setting would be simpler to maintain and use because there is really no need to track anything. To to summarize, potentially we can have:
1 Apply speed change per album (on until turned off for that album)
2 Apply speed change per album for the duration of the album (turned off automatically once album finishes)
3 Apply speed change per song for the duration of the song (turned off automatically once song finishes)
4 Apply speed change per song (on until turned off for that song)
5 Global change applicable to all files (on/off)
it's probably not feasible or worth the dev effort having all the options but I think that #2 and #3 would be the most useful to begin with.
Another setting would set the priority if multiple setting are present should a combinaion of the above options be implemented.
Just some food for thought