Magma Error :
- This topic is empty.
-
Posts
-
This is a new MAGMA error for me.. any ideas…?
ERROR: MIDI Compiler: (PART DRUMS): Difficulty expert: Gem at [3:1:000] is only 2.45 seconds into the song; gems cannot appear before 2.45 seconds into the song
I have a tempo map authored for the whole song. 192 BPM (this is the correct speed – it is a fast one!)
(I did see this error message referred to link below, but the situation was a little different in that author had no tempo map authored).
http://pksage.com/ccc/IPS/index.php?/topic/11304-magma-problems/?hl=%2Bseconds+%2Binto+%2Bsong
Well, it’s pretty self explanatory. You can’t have gems appear so early. So either add an extra measure and start the song at 4.1 or slow down the tempo of the first measures a tiny bit so by the time you hit 3.1 you’re like at 3 seconds or so. That should work.
I have never been able to successfully manage moving the tempo map and all authored notes by adding in another measure… without major problems… is there a specific way of doing this …?
Here we go….. “You can’t have gems appear so early”
Well, honestly there simply is no way the error message can be any clearer: you can’t have notes appear that early because the UI elements are still settling on screen.
To add a measure, select an entire measure and then Insert space at time selection from the Actions menu in the main window. Or, select all your tempo markers, cut them and paste them a measure later.
>> UI elements are still settling on screen.
I have no idea how that can be translated from an error message of such few words!
To add a measure, select an entire measure and then Insert space at time selection from the Actions menu in the main window.
This is the way I did it recently for a couple of fast songs, and it works quite smoothly. I did not, however, initially realize that it turns the selected portion into a loop. Just make sure to remove the loop afterwards
” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif” />>> UI elements are still settling on screen.
I have no idea how that can be translated from an error message of such few words!
Not sure why you would need to know though: this is also one of the very few documented error messages in the RBN docs, I honestly can’t see a reason why that would stump you. Notes appear too early, you need to move them, that’s it.
>> gems cannot appear before 2.45 seconds into the song…
>>I honestly can’t see a reason why that would stump you
I knew this would likely become a protracted debate….
As far as I am concerned it is not self explanatory. (Why cant there be gems 2.45 seconds into a song….? Who really knows, understands or even cares about UI elements settling on a screen for that matter?)
“Tempo too fast for gem display, insert an extra measure before 3.1.0” … Now that is a clear error message of that there is no debate.
Apologies for not knowing it all…… must try harder.
Guido, if you think your snark is not coming through, rest assured that it is, and it’s not well taken.
The message that you find so complex, was implemented by Harmonix, not me. I had the choice of altering it or leaving it as is. It’s pretty self-explanatory insofar as what it say is easy to understand. Why you can’t have a note so early doesn’t matter and it’s not up for debate. The software is telling you that you can’t. Therefore you move it later in time. That’s all there is to it.
- You must be logged in to reply to this topic.