Unified · Split
| @@ -4,13 +4,12 @@ The project contains example code in the ft2play folder on how to interface with · 3 unmodified lines | |||
| 4 | 4 | ||
| 5 | # Notes | 5 | # Notes |
| 6 | - To compile ft2play (the test program) on macOS/Linux, you need SDL2 | 6 | - To compile ft2play (the test program) on macOS/Linux, you need SDL2 |
| 7 | - The replayer is the same in FT2.08 and FT2.09 (though the GUS routines differ in FT2.09) | 7 | - This is <i>not</i> the same replayer/mixer code used in the FT2 clone (the FT2 clone also uses a port, but it has some audio precision improvements) |
| 8 | - This is <i>not</i> the same replayer/mixer code used in the FT2 clone (the FT2 clone also uses a port, but it has some audio fidelity improvements) | ||
| 9 | - The accuracy has only been compared against a few songs | 8 | - The accuracy has only been compared against a few songs |
| 10 | - The code may not be 100% safe to use as a replayer in other projects, and as such I recommend to use this only for reference | 9 | - The code may not be 100% safe to use as a replayer in other projects, and as such I recommend to use this only for reference |
| 11 | 10 | ||
| 12 | # How to test accuracy | 11 | # How to test accuracy |
| 13 | 1) Open FT2.08 or FT2.09 (use a fresh program start for every render) and load a song. Make sure "16-bit mixing", "Stereo" and "Interpolation" is enabled in the config screen. | 12 | 1) Open FT2.08 or FT2.09 (use a fresh program start for every render) and load a song. Make sure "16-bit mixing", "Stereo" and "Interpolation" are enabled in the config screen |
| 14 | 2) Save as WAV (freq=44100Hz, amp=4) | 13 | 2) Save as WAV (Freq. = 44100, Amp. = 4) |
| 15 | 3) Render the same song to WAV using ft2play (f.ex. "ft2play mysong.xm --render-to-wav") | 14 | 3) Render the same song to WAV using ft2play (f.ex. "ft2play mysong.xm --render-to-wav") |
| 16 | 4) Use a program capable of verifying the binary integrity between the two output files. If they differ, you found a problem and should create a new issue for this project on github. :) | 15 | 4) Use a program capable of verifying the binary integrity between the two output files. If they differ, you found a problem and should create a new issue for this project on GitHub :) |