Idea for the next release of CoilSnake. Putting it here so it's on the radar/so we remember.
Right now, song packs export sequence data as a song.ebm with a song.ebm.yml - a sidecar file that corresponds to just that ebm.
The song.ebm.yml stores which primary and secondary instrument packs the song should use.
It would be more user-friendly/simpler to just include this data in songs.yml. Then, the song.ebm.yml wouldn't have any reason to exist, and musicians don't have to go digging through folders as much. (From my work on the remake, I've had to do this a lot!)
Like so:
0x4C:
Song Pack: 0x55
Song File: All That I Needed.ebm
Instrument Pack 1: 0x05
Instrument Pack 2: 0x54
For backwards compatibility with projects created with the current version of coilsnake, maybe it should still check to see if the sidecar file exists. Or, alternately, we should make the project file upgrade process go through every song and do it.
Idea for the next release of CoilSnake. Putting it here so it's on the radar/so we remember.
Right now, song packs export sequence data as a song.ebm with a song.ebm.yml - a sidecar file that corresponds to just that ebm.
The song.ebm.yml stores which primary and secondary instrument packs the song should use.
It would be more user-friendly/simpler to just include this data in songs.yml. Then, the song.ebm.yml wouldn't have any reason to exist, and musicians don't have to go digging through folders as much. (From my work on the remake, I've had to do this a lot!)
Like so:
For backwards compatibility with projects created with the current version of coilsnake, maybe it should still check to see if the sidecar file exists. Or, alternately, we should make the project file upgrade process go through every song and do it.