Mod Archive Forums
Music Production => MilkyTracker => Tracking => MilkyTracker Bug Reports => Topic started by: theDESTROYER on November 11, 2014, 22:18:19
-
Hello there, i do tracks on oktalizer since '92, and i noticed that when i load em on milkytracker there are few importing bugs, all regarding the channel effects:
1 > it reads the volume changes only in the position they are writed..
inside oktalizer for example if i change the volume in 1 , the sample will following stay at volume 1 till another volume change parameter will be encountered.
2 > about the note change it doesn't works at all..
that parameter is changed with L (-) and H (+)
3> about the pitch slide it reads it but not how the oktalizer does , i think because when you work in 8-channels mode the oktalizer doesn't let you play samples at A#3 and B-3, that are available only in 4-channels mode.
that parameter is changed with D (-) and U (+)
hope this informations can helps you to fix those bugs... milkytracker has the potential to be the best tracker with the amiga sound emulator on it! ;)
-
I'd like to add that portamento up and down commands seem to be mixed in the loader code (src/milkyplay/LoaderOKT.cpp):
static void convertOKTEffects(mp_ubyte& eff, mp_ubyte& op)
{
switch (eff)
{
case 00:
op = 0;
break;
case 01: // porta down
eff = 0x02;
break;
case 02: // porta up
eff = 0x01;
break;
They work the exact opposite as intended.
Also, arpeggio does not seem to work. The loader recognizes the arpeggio commands but these get lost somewhere as they are not visible in editor, nor handled by playback.
Keywords: oktalyzer
-
I'm not sure why the portamento commands are reversed, according to okt-form.txt (http://www.textfiles.com/music/FORMATS/okt-form.txt) they are correct - perhaps that document is wrong?
Regarding the arpeggio and other commands; MilkyPlay does interpret them (the player library that MilkyTracker uses), but they are removed when converted into the XM format for MilkyTracker.
The best way to improve MilkyTracker's handling of Oktalizer mods would be to decide which XM effects should be substituted for the various Oktalizer effect codes - if you want to try editing the code yourself, have a look at ExporterXM.cpp (https://github.com/Deltafire/MilkyTracker/blob/master/src/milkyplay/ExporterXM.cpp) and submit a patch :)
-
I'm not sure why the portamento commands are reversed, according to okt-form.txt (http://www.textfiles.com/music/FORMATS/okt-form.txt) they are correct - perhaps that document is wrong?
Regarding the arpeggio and other commands; MilkyPlay does interpret them (the player library that MilkyTracker uses), but they are removed when converted into the XM format for MilkyTracker.
The best way to improve MilkyTracker's handling of Oktalizer mods would be to decide which XM effects should be substituted for the various Oktalizer effect codes - if you want to try editing the code yourself, have a look at ExporterXM.cpp (https://github.com/Deltafire/MilkyTracker/blob/master/src/milkyplay/ExporterXM.cpp) and submit a patch :)
The Oktalyzer format document is correct, but highly misleading.
1 Portamento down: decrease period of current sample by 'data',
once every 50Hz clock tick.
2 Portamento up: increase period of current sample by 'data',
once every 50Hz clock tick.
Portamento down == decrease period == increase pitch. Protracker et al call this command "slide up", hence the confusion.
Oktalyzer seems to have three different arpeggio commands. I may take a closer look at the code but don't hold your breath. :)
-
The reversed portamento effects have been fixed in commit 851c23 (https://github.com/Deltafire/MilkyTracker/commit/851c23d9fe06c03dcc2e47d94117dc5b15c1bd62).