pouët.net

psk information 5 glöps

• general:
• level: user
• personal:
• first name: Piotr
• last name: Skórka

• demotool Amiga AGA Amiga OCS/ECS ProTracker 2.3 FC
• @Saga Musix, thank you for the many detailed, helpful explanations.
  I'm now certain that, regardless of the outcome of my investigation, this needs to be done in two files.
  
  The only thing I can think of is the possibility of using the lowest bits of the last twelve bytes of the sample. A little dithering never hurt anyone...
• isokadded on the 2026-04-14 01:05:44
• demotool Amiga AGA Amiga OCS/ECS ProTracker 2.3 FC
• Hi.
  
  First of all, I wanted to say that this situation isn't a result of ignorance.
  
  I did my homework, but as you can see, the problem turned out to be more complicated than I expected.
  
  I had two options: saving the colors in a separate file, next to the module file, or using the same file.
  
  Using two files was obviously safe, although it slightly complicated file handling on the tracker side and introduced some user interface issues.
  
  I decided to look into a solution based on a single file.
  At that stage, I hadn't even considered the possibility of distributing the module with this metadata.
  I imagined it would be necessary to remove this information before exporting the final version.
  
  First, I looked at how ProTrackers handle module files. It turned out that ProTracker doesn't even read the extra data at the end of the file. It simply closes the file after loading all the necessary data.
  
  Next, I looked at the code for several players. Some loaded the entire file, but the player code never even touched the address space occupied by the excess data.
  
  To be sure, I turned to the internet and reviewed all the documentation I could find regarding the module file format. There, I also encountered the issue of detecting unusual module format variants used by players to properly adapt the player code to the loaded module. There were suggestions for using various heuristics to identify the most exotic ProTracker progenitors, in which the total length of the module file could be essential for correct identification. However, I found no information anywhere suggesting that a module with an identifier like "M.K." or "M!K!" could have a structure whose correct identification would require knowledge of the file length.
  
  Based on this, I concluded that appending metadata to the end of a module like "MK" does not violate the format, as the only reasonable action in this case is to ignore, or even better, not load, this data at all.
  
  It's possible, however, that such "non-deterministic" "MK" modules exist, and I simply haven't found the right information.
  In such a situation, I take full responsibility and promise to correct any necessary issues as soon as possible.
  
  I'd like to make sure that the cause of this confusion isn't inaccurate heuristics in some players.
  Especially since everything works flawlessly in many players (unfortunately, not all).
  
  For now, if anyone would like to test writing modules with colored samples, I suggest using CLEAR -> SHIFT + SAMPLE before sharing, then saving the module, which will remove the metadata. Simply loading and saving such a module in regular ProTracker also removes the colors.
• rulezadded on the 2026-04-14 00:43:28