ProTracker 2 clone v1.41

• Added support for loading XPK-compressed MOD files

ProTracker 2 clone v1.40

Don't handle mouse click if window wasn't in focus

ProTracker 2 clone v1.39

• macOS/Windows: Updated SDL to version 2.0.20

ProTracker 2 clone v1.38

• Added 128kB sample support again. This can be turned on by adjusting the 64K_LIMIT setting in (the new) protracker.ini to FALSE. Please read the 64K_LIMIT comment in protracker.ini first before doing this.
• Fixed a bug where it wasn't always possible to mark the last sample point in the sample editor
• Some other minor code changes

ProTracker 2 clone v1.37

Fixed potential thread issues between user input thread and audio thread, like when jamming a sample, toggling tuning tone, playing sample in the sample editor, adjusting sample loop, etc.

ProTracker 2 clone v1.35

• Implemented a config entry in protracker.ini for disabling the 2x downsample dialog that shows up when attempting to load >22kHz samples (NO_DWNSMP_ON_SMP_LOAD)
• Don't attempt to center window after leaving fullscreen mode. This could lead to issues on multi-monitor setups.
• Further accuracy changes to the Paula emulator. Read two samples at once into the AUDxDAT buffer. This is a minor change, but it can have a very small impact on sample-changing commands (EFx/E8x).

ProTracker 2 clone v1.36

• Fixed clicking issues in v1.35 during sample looping. Sorry!
• Fixed an issue where the quadrascope was not updated properly when a F00 command was triggered before the last channel

ProTracker 2 clone v1.34

• Bugfix: Pattern delay (EEx) did nothing on muted channels
• Bugfix: Less clicks/pops during E0x command (Set LED Filter)
• Added the missing Karplus-Strong command (E8x). Since this effect was sometimes replaced with visuals-syncing in demo music, it can be turned off by setting DISABE_E8X to TRUE in protracker.ini.
• Fix: Only do 2x oversampling if the audio output rate is below 96kHz. It would otherwise be a waste of CPU time (diminishing returns).
• Paula emulation is now slightly more accurate to a real Amiga (verified):
  1. Period/volume changes are now only updated when it's time to read
     a new sample point (period refetch). It was recently discovered that
     volume is also fetched (and cached) in the period refetch stage.
  2. During sample point fetching, the new sample point is now cached until it's
     time to read the next sample point. This can sometimes make a very small
     difference for sampledata-changing ProTracker effects (E8x / EFx).
• Removed BLEP'ing of volume changes, as it was no longer needed with the new way of doing volume changing, and it saves up some CPU time

ProTracker 2 clone v1.33

• The tracker now uses 2x oversampling and decimation for mixing and filtering for (theoretically) less aliasing
• Added Amiga 1200 low-pass filter (~34.4kHz, when not in A500 mode). This makes sense now, since we have twice the render/filter frequency than before.
• PAT2SMP now renders in higher quality thanks to the new high quality 2x decimator routine. Especially noticable in LO mode on high-frequency content.
• The "2x downsample" option while loading samples results in slightly less aliasing than before because of the new high quality 2x decimator
• The MOD2WAV audio rate is now the same as the tracker's audio rate
• Stereo separation now works like it should. The volume is a bit louder than before if you increase the separation, but that's expected.
• Removed the hand-made cutoff tweak on the Amiga 500 low-pass filter. It now uses the correct nominal cutoff frequency. The RC filter routines have been replaced with new ones, and with these I didn't have to tweak the cutoff to make it sound similar to an A500 (probably related to filter prewarping?).
• Windows/macOS: Updated SDL2 from version 2.0.14 to 2.0.16

ProTracker 2 clone v1.32

• Bugfix: If you had accidentally clicked somewhere on the sample data before using the "ramp volume" tool, it wouldn't work as expected
• Bugfix: The BPM was a tiny fraction off because of an off-by-one error in the Amiga CIA period -> Hz calculation. The error was about ~0.02%, so it would only be measurable when comparing several minutes of recorded audio