Jumps in SpinEternally often seem more noticeable than those in other songs. So SpinEternally seems like a good song to study to identify weaknesses in the remix implementation and how to improve it. Things to explore:
- Is
shiftTimestampsSeconds (in RemixableSongs.cs) close enough?
- Is
QueueBasedAudioRemixer.cs doing a good job of scheduling the audio?
- Is
InfiniteRemix.cs producing song slices with bad timestamps (e.g. maybe BeatAlignedObject is flawed and is messing up the timestamps).
- Is
InfiniteJukeboxAlgorithm/ doing a good job of identifying similar beats in the song?
- Maybe its implementation or its parameter values should be tweaked to improve SpinEternally.
- Maybe it’s being too lenient on SpinEternally and suggesting jumps between beats that aren’t similar enough.
- Are there any issues with the analysis data provided by Spotify's audio analysis web API?
Related
Jumps in SpinEternally often seem more noticeable than those in other songs. So SpinEternally seems like a good song to study to identify weaknesses in the remix implementation and how to improve it. Things to explore:
shiftTimestampsSeconds(inRemixableSongs.cs) close enough?QueueBasedAudioRemixer.csdoing a good job of scheduling the audio?InfiniteRemix.csproducing song slices with bad timestamps (e.g. maybeBeatAlignedObjectis flawed and is messing up the timestamps).InfiniteJukeboxAlgorithm/doing a good job of identifying similar beats in the song?Related