pouët.net

Saga Musix information 3503 glöps

• general:
• level: user
• personal:
• first name: µ6
• last name: ^Nuance
• portals:
• slengpung: pictures
• demozoo: profile
• cdcs:
• cdc #1: tHe S by Suspend [web]
• cdc #2: fr-052: platinum by Farbrausch [web]
• cdc #3: Frameskool - Breakpoint 2007 64k invit by Equinox [web]
• cdc #4: STS-05: Royal Temple Ball by Synesthetics
• cdc #5: f07 - The Function 2007 Invitation by Conspiracy [web]
• cdc #6: Atrium by TBC & Loonies [web]

• demo Nintendo DS Emulator Examination by Stargaze [web]
• Rad :D
• rulezadded on the 2026-04-12 12:18:05
• demotool Amiga AGA Amiga OCS/ECS ProTracker 2.3 FC
• It is true for any amount of bytes. Just to clear, I was investigating this from the perspective of being able to indicate that a module was made with OpenMPT (or any other tracker), which would be even less data to store. The problem is that MOD files have weak magic bytes, and there are a few variants of the format which require extensive checks (see above comment about the "inofficial" patterns in the order list). For a tracker that only loads MOD files this is not that important, but it is extremely important for playback libraries (like libopenmpt, libxmp, etc.) that are expected to be used in other software that may also want to play non-MOD files that can vaguely look like they might be MOD files. Just recently we found an Opus file that just so happens to have some string (8CHN) in just the right position that it looks like it's an 8-channel MOD file. So the following techniques may conflict with such validation, or may be mis-interpreted by some players:
  
  - Using unused pattern bits: May be detected as garbage data and thus get rejected. Or if not, might get interpreted as part of the sample number and thus make the track play incorrectly.
  - Using non-printable characters in sample/song names: May be detected as garbage data, and also limits sample/song names in length, which is not acceptable for a general-purpose MOD tracker.
  - Using unused finetune bits: May cause rejection or incorrect interpretation of the value
  - Using an unused sample or pattern: Not possible in every module, all 31 samples or 128 patterns may be used.
  - Using unused parts of the order list: Ditto, plus see the "inofficial pattern" variant already mentioned.
• isokadded on the 2026-04-11 16:03:49
• demotool Amiga AGA Amiga OCS/ECS ProTracker 2.3 FC
• Quote:

  Haven't checked so I might be completely off track, but the colors could be saved as a dummy sample or pattern to remain fully compatible

  
  
  Quote:

  What makes even more sense is to encode the color using 1 or 2 non printable characters (before the NULL characters) in the name of the instruments. That approach is fully compatible and the author's are well aware that a color means 1-2 char shorter name so it's really their decision.

  
  
  I have spent a lot of time over the last years thinking of how to encode such additional data in MOD files, but there simply is no space that will
  1) always be available, no matter how complex your module is and
  2) not cause a random module player to reject the module because sanity checks on the module structure don't pass.
• isokadded on the 2026-04-11 12:33:10
• demotool Amiga AGA Amiga OCS/ECS ProTracker 2.3 FC
• Something to note:
  
  Quote:

  When you save a module, the color information is also saved. Sample colors are
  saved at the end of the module file and do not break compatibility with the
  standard module.

  
  There are multiple issues with this that may not be immediately obvious to everyone. Most module playback libraries rely on the size of a ProTracker MOD to be correct in certain edge cases, because sometimes patterns found in the order list beyond the declared order list size need to be counted into size calculations and sometimes not. Intentionally messing with this can break those detections (although it's unlikely in this particular case). There is also no signature for those extra bytes so in the case where other trackers do the same thing (write extra data at the end of file), it's going to be difficult to figure out what the true meaning of those bytes is.
  
  I would urge you to consider putting this extra information in a companion file instead that sits next to the module file instead (e.g. mod.awesome + mod.awesome.colors). This way, the modification stays compatible with all of the existing MOD infrastructure out there.
• isokadded on the 2026-04-08 18:30:27
• 64k Windows inSight by Approximate [web]
• Completely broken on AMD by the way, no jungle visible :(
• isokadded on the 2026-04-08 14:17:52
• 64k Windows inSight by Approximate [web]
• What a mesmerizing ride. Beautiful!
• rulezadded on the 2026-04-07 12:30:57
• demo Windows JavaScript ABOMINATION by mfx [web]
• Danke, es ist sehr schrechklich.
• rulezadded on the 2026-04-07 12:17:26
• demo invitation Windows JavaScript The Golden Disk by Slipstream [web]
• Well that's going to be any annoying earworm at the party.
  
  <3
• rulezadded on the 2026-03-02 18:39:18
• demo Amiga OCS/ECS +=+ by Spreadpoint [web]
• Mesmerizing. Perfect sync. Audiomonster. <3
• rulezadded on the 2026-02-28 23:35:08
• demo Amiga OCS/ECS NETROU by AttentionWhore
• Saw the screenshot, knew exactly what the soundscape is gonna be like!
• rulezadded on the 2026-02-11 18:02:43