www.LickByNeck.com

[Peppie]

At the moment a Song.exe has that format

<PlayerApp.exe>
<GuitarSongData>

That advantage of that is that you simply have one file - ready for use.

But one drawback is that so each song-download gets bigger as it would only contain <GuitarSongData>. Another is that the more LickByNeck-SongRelease you make the bigger the efforts get to update the <PlayerApp.exe>.

You problably discovered bugs in ya software(and fixed it and also made improvements to the <PlayerApp.exe> like the loop- or slow play feature/functions. But what is with ya old release that still have an old <PlayerApp.exe>(with all the old known fixed bug & without the new functions)?

Well you could do it the classic way...
<PlayerApp.exe> -> Setup.exe
<GuitarSongData> -> song_xyz.LBN Download
(Before a use can play 'song_xyz.LBN' he needs to download and install Setup.exe.)
... but you surely thought about that and intentionally choose the other 'standalone-player' way.

Well so why not combine both? (StandalonePlayer+Installer)

When I start a song.exe it copies/installs <PlayerApp.exe> to some fix location on the PC lets say %Programmfiles%\LickByNeck\Player.exe before it runs <GuitarSongData>. And before it performs the installs it checks if there is already a newer version of Player.exe on the system.
And if that's the case it simple uses the newer player.exe instead on the old one.
That would make it possible to easly run the <GuitarSongData> with the newest player version. The user may choose to download the setup for the newest player.exe, to just download and run song.exe as it is now (..but then he get's an older version player with lesser functionallity and hopefull not too worse bugs)

Incase you change the dataformat of <GuitarSongData> in a new version so it get incompatible just change the name of
%Programmfiles%\LickByNeck\Player.exe to for ex.
%Programmfiles%\LickByNeck\Player2.exe
so you stop updating the older player and start a new generation(/revision)...