You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This isn't so much a bug report as just some general information about Archeage that may be useful for people who come across this tool.
Mabinogi puts middle C at octave 4. I'm not quite clear how many octaves it supports or what the range is. Archeage has 11 octaves (0-10), with middle C at octave 5. If someone uses the 3MLE program to create MML for Archeage, it must be post-processed to sound correct inside archeage and that post processing should also be done prior to feeding it through this tool. I've written a program that does this (https://github.com/kernighan/archeage-3mle). Prior to the recent fixes, running music through this tool put music in the wrong octave for Archeage. I think that n-notes would still be done incorrectly as the current code is based on the Mabinogi settings, but the tool I wrote already replaces them in line with the Archeage octave range.
Volume handling in Archeage works like this. If track1 is volume X, then every track after that has the same volume. But if track 2 were to set volume Y, then track 2 and every track after it would be at volume Y (leaving track 1 at volume X). I.e., v127abcd,v100defg,<abcd,<defg the last 3 tracks would be at volume 100. Volumes are also relational, for example:
v127abcdv100defgv90<abcd,<abcdefg<abcd the second track (and any other tracks) would match the volume changes made in track 1. The volume in archeage defaults to 100, with a minimum of 0 and a max of 127. You can find a Mabinogi to Archeage volume mapping chart at https://github.com/kernighan/archeage-3mle/blob/main/mml-guide.md
Tempo defaults to 120 in Archeage and Mabinogi. With archeage, if 32nd notes or faster are present, the tempo must be divisible by 6 or desyncs will occur. Tempo should only be changed in the first track, and it is relational in the same way multiple volume changes are relational as described above.
The text was updated successfully, but these errors were encountered:
This isn't so much a bug report as just some general information about Archeage that may be useful for people who come across this tool.
Mabinogi puts middle C at octave 4. I'm not quite clear how many octaves it supports or what the range is. Archeage has 11 octaves (0-10), with middle C at octave 5. If someone uses the 3MLE program to create MML for Archeage, it must be post-processed to sound correct inside archeage and that post processing should also be done prior to feeding it through this tool. I've written a program that does this (https://github.com/kernighan/archeage-3mle). Prior to the recent fixes, running music through this tool put music in the wrong octave for Archeage. I think that n-notes would still be done incorrectly as the current code is based on the Mabinogi settings, but the tool I wrote already replaces them in line with the Archeage octave range.
Volume handling in Archeage works like this. If track1 is volume X, then every track after that has the same volume. But if track 2 were to set volume Y, then track 2 and every track after it would be at volume Y (leaving track 1 at volume X). I.e., v127abcd,v100defg,<abcd,<defg the last 3 tracks would be at volume 100. Volumes are also relational, for example:
v127abcdv100defgv90<abcd,<abcdefg<abcd the second track (and any other tracks) would match the volume changes made in track 1. The volume in archeage defaults to 100, with a minimum of 0 and a max of 127. You can find a Mabinogi to Archeage volume mapping chart at https://github.com/kernighan/archeage-3mle/blob/main/mml-guide.md
Tempo defaults to 120 in Archeage and Mabinogi. With archeage, if 32nd notes or faster are present, the tempo must be divisible by 6 or desyncs will occur. Tempo should only be changed in the first track, and it is relational in the same way multiple volume changes are relational as described above.
The text was updated successfully, but these errors were encountered: