frantic wrote:Have other people experienced this as well? It has happened to me once.Have other people experienced this as well? It has happened to me once.
I confirm the bug. Latest defMON build (2017/10/26).
Testing results: empty affected song has 65 blocks, but finished affected song has 76 blocks (all 00-7F sequences used, all 00-FF instruments used). This is only 11 blocks of difference between empty and maxed out song.
Unaffected songs usually have 2 blocks when empty and go up to 60 blocks when maxed out. This time it is 58 blocks difference.
It means that something is unnecessarily saved as if it was user data in affected songs, but still can be overwritten by the actual user data.
Amelinium wrote:After saving the music for the first time I have 66 blocks file. And after compressing it, the raw file is $1000 to circa $2000 most of the time.
This is also true. Affected empty song has 16 blocks after saving it in RAW mode ($1000-$1F11). It feels super huge.
How often the bug happens? It is semi-permanent, in 75% cases I'm getting large files. Once the file becomes "affected", there's no going back. However, if you load "affected" song using older defMON build (eg. 20141108) and save it, the file will be "healed" from unnecessary data.
Where does the bug happen? Both on real C64 hardware and Vice 2.xx+3.xx emulators.
_____________________________________________________________________
PS. I know it won't change much, but the jump X times loop idea for instrument lines is a idea. Good directon. Useful to say the least. Would molest every here and there, 10/10.
Last edited by F7sus4 (Oct 21, 2018 1:04 pm)