Mod Archive Forums
Music Production => MilkyTracker Feature Requests => MilkyTracker => Tracking => Feature Request Archive => Topic started by: yzi on April 12, 2013, 10:45:26
-
On real Amiga ProTracker, A-3 (or "A-5" in Fast Tracker II note naming, playback rate roughly around 28kHz) is actually the highest safe note, and A#3 and B-3 produce a grabled sound. I don't know if it's still the same with Amiga 1200, but at least on an Amiga 500, this is the case. It would be nice if MilkyTracker warned of these high notes, because nobody really wants to use them on something that will be played on an Amiga.
-
Using PT2.3d on an A500 in WinUAE, I cannot confirm this.
Edit: Now I can hear some rather quiet buzzing noise at B-3. It wasn't really noticeable.
-
I don't know about emulators, but here are the three highest notes A-3, A#3 and B-3 of a (badly looped) synth sample with finetune +7, recorded from an actual Amiga 500 and ProTracker 2.3d.
http://www.kameli.net/~yzi/amiga500_protracker_highest_notes_finetune7.mp3
Maybe it's not about the notes as such, but the period values. With a higher finetune, even A#3 gets badly distorted. And it's not just the distortion, but the sounding pitch is wrong as well.
But anyway, this was open source, so I can fix it myself.
Btw, I thought this was self-evident common knowledge to anyone in the mod scene, but I guess not everybody has tracked on Amigas back in the day. ;)
-
Ok, I didn't get that far yet, but at least I managed to mutilate the code enough to compile a working Win32 executable in VS2010 Express. Here's the modified source (in platforms/win32/milkytracker_vs9 folder)
http://www.kameli.net/~yzi/milkytracker-0.90.85_vs2010express.zip
The things I bumped into were like this:
- target name/path vs. linker in project settings, these seem to always require a bit of tweaking when bringing vs2008 stuff to 2010
- "auto int" definitions --> just "int"
- and some other similar things, just comment out the "auto" part, why is that there anyway
- some abs() functions had to be seasoned with (int)(...) because of ambiguity in overloaded function versions or something
- VS2010 Express doesn't have MFC, so I had to copy-paste some constant definitions and comment out "afxres.h" from Win32_resources.rc
-
Ok, I made a hacked version which highlights the risky notes. Happy!
(http://www.kameli.net/~yzi/milkytracker_0.90.85_amigasafewarning.png)
-
Oops. Did I not include a binary download link to the modified version.
http://www.kameli.net/~yzi/milkytracker_0_90_85_amiga_note_limits_warning.zip (http://www.kameli.net/~yzi/milkytracker_0_90_85_amiga_note_limits_warning.zip)
-
Oops 2. Apparently it only highlights notes HIGHER than the limit. Oh well.
-
Just stumbled upon your post on pouet, looks like a useful mod! Will incorporate it into the next release (whenever that happens..)