I recent weeks, i've ported songs to SMW, and have had no problem.
Time to braek that strek, beacause i found a problem. When i tried to insert the .txt into SMW with AddMusic, It gives me about 50 errors telling me this.
ERROR = ## = Musical interval is too high
And a single error that says:
ERROR = ## = octave is too high
I know octaves can't go above o7, but i've looked. As far as i can see, there seems to be nothing wrong, So can someone please help me woth this?I have Changed. Perhaps for the better, or maybe for the worse.
well, have you checked for this
ex:
Code
o7b4>c4d4
the ">" command does also make the octave higher...
Originally posted by MaZ18
well, have you checked for this
ex:
Code
o7b4>c4d4
the ">" command does also make the octave higher...
Yes, i did.I have Changed. Perhaps for the better, or maybe for the worse.
## = ??
What does ## say?
Originally posted by MaZ18
## = ??
What does ## say?
The line number. But there was so many, so i put ## for short.I have Changed. Perhaps for the better, or maybe for the worse.
well, what's the first one?
If you find it, you might see what's wrong.
Moved to the custom music help forum.My YouTube channel
Get the official ASMT resource pack here!
Are you also making sure that all of your channels have an o4 at the very beginning? If you have:
Code
#0 o5
#1
#1 will start on o5 because of this. To fix this, you would put an o4 immediately after #1.
If you already have, it would also be a helpful option to provide the TXT for us.
Originally posted by MarioStarLuigi
You can use Kipernal`s MML Editing Tool to easily lower octaves. Changing only certain ones can make your song sound strange (not necessarily, but it could).
I did. It said it was as low as it could be
Originally posted by CrispyYoshi
Are you also making sure that all of your channels have an o4 at the very beginning? If you have:
Code
#0 o5
#1
#1 will start on o5 because of this. To fix this, you would put an o4 immediately after #1.
If you already have, it would also be a helpful option to provide the TXT for us.
Not sure i get what you mean. (yeah, i'm not good at this at all)I have Changed. Perhaps for the better, or maybe for the worse.
In #0, it starts at o5, lowers to o4, and rises to o5 again. Since #0 ends at o5, #1 will start at o5, rising to o6 and then to o7, which is an invalid octave. Stating the octave at the beginning of the channel will prevent this. In this case, you'd put this:
In #0, it starts at o5, lowers to o4, and rises to o5 again. Since #0 ends at o5, #1 will start at o5, rising to o6 and then to o7, which is an invalid octave. Stating the octave at the beginning of the channel will prevent this. In this case, you'd put this:
Code
#1 @0 v255 y10
o4a8 >b8c8d8e8f8g8
or
Code
#1 @0 v255 y10
o3>a8 >b8c8d8e8f8g8
.
Oh! I get it now! But the problem is still there. I have Changed. Perhaps for the better, or maybe for the worse.
Remove the first '>'.
After that, you should be good to go!
Holy Sh**! How did that change anything?I have Changed. Perhaps for the better, or maybe for the worse.
note C octave 1 is the lowest note. It'll sound weird with that in it most of the time.I think a post layout goes here somewhere...
God damn, new problem.
Now, when i try to enter the level to test it, the game crashes.
What is that all about?I have Changed. Perhaps for the better, or maybe for the worse.
Oops, forgot to tell you about the header.
Add this:
Oops, forgot to tell you about the header.
Add this:
Code
$ED $80 $6D $2B
$ED $80 $7D $00
$F0
to the top of the song.
Ohhhh yeah! You don't need to tell me what i header is, beacause i already know.
EDIT: Still crashes I have Changed. Perhaps for the better, or maybe for the worse.