Real Keys Part has “no keyboard ranges” on Medium and Hard [SOLVED]
- This topic is empty.
-
AuthorPosts
-
May 23, 2016 at 11:27 am #393917
This error only says this for the Medium and Hard Pro Keys parts, but I have range marker notes on all four difficulties. In fact, all four Pro Keys tracks are the same, because they all have Expert Pro Keys authored into them. All my notes fit within one range, so I just put one range marker note at the beginning of the song. That’s how I’m supposed to do it, right?
It also says “Overdrive phrase at [every overdrive phrase] has no gems in Medium and Hard difficulties”, but all overdrive phrases have gems in all difficulties of the Pro Keys charts…
Anyone have any idea what’s going on?
UPDATE: What’s really interesting is that my tracks for the Medium and Hard mode Pro Keys are a lot different than the Expert and Easy ones… the Expert and Easy tracks have a lot more rows. I’m using the C3 Custom RB3 Template, btw.
UPDATE 2: When I look at my non-Pro Keys track, it has these weird white bars on it. When I open the MIDI editor for it, there’s nothing there. They’re like ghost notes or something. Weird.
Please help.
I’ve been up all night trying to fix this. Found a few threads where this issue is mentioned, like this one, but I’ve not seen it been resolved in any thread. Guess I’ll just go to sleep. Hopefully someone will have answered by the time I wake up.
UPDATE 3: I did one last check, and I noticed that whenever I go to export the project’s MIDI, it writes 11 of the tracks. But I have 13 tracks that should be getting written. It’s set to export the entire project, and all 13 tracks are unmuted. Could it be that it’s somehow not exporting the Medium and Hard Pro Keys tracks, and that’s what’s causing all the errors? Like wtf… unless it just counts the entire Pro Keys folder as one track, and counts the Master as a track as well….. but then what’s causing the errors!?
May 23, 2016 at 7:29 pm #469210Still can’t figure out how to solve this error. Still says I don’t have keyboard ranges and overdrive notes, when I clearly do…
May 23, 2016 at 7:49 pm #469213Open your exported MIDI to check what’s in there.
May 23, 2016 at 10:05 pm #469221Open your exported MIDI to check what’s in there.
Good idea. Let’s see here…
All difficulties of the Pro Keys track are in here, and they all look exactly the same, minus the overdrive phrases, which are only in the Expert track. They all have range marker notes as well.
May 23, 2016 at 10:18 pm #469223Here, I’ll open up the RPP again and post a screenshot. You can see the range markers in all four difficulties, and all sections under the overdrive marker are the same. Still says there are no notes, and no range markers, but only for Medium and Hard difficulties.
May 23, 2016 at 10:34 pm #469225Depending on how you cut and paste MIDI events from the higher difficulty tracks to the lower difficulty ones, you may have gotten some extra cruft in the hard and medium tracks that is keeping Magma from parsing them correctly. On occasion I’ve had the event for track name get copied along with the other bits I was trying to copy.
If you’re willing to post your RPP project files, someone might be better able to see and explain what’s going on.
May 23, 2016 at 11:00 pm #469226Depending on how you cut and paste MIDI events from the higher difficulty tracks to the lower difficulty ones, you may have gotten some extra cruft in the hard and medium tracks that is keeping Magma from parsing them correctly. On occasion I’ve had the event for track name get copied along with the other bits I was trying to copy.
If you’re willing to post your RPP project files, someone might be better able to see and explain what’s going on.
I checked the MIDI events, and everything looks fine.
Here’s a link to my RPP.
Pls halp. I’ve been beating my head against a wall here all day trying to figure this out ” src=”/wp-content/uploads/invision_emoticons/default_SA_frown.gif” />
May 24, 2016 at 3:11 am #469236Found it!
You’re not supposed to surround your track name text events in square brackets. [PART REAL_KEYS_M]
Check that you have those removed on all tracks and try exporting and testing your MIDI again.
May 24, 2016 at 3:15 am #469238Found it!
You’re not supposed to surround your track name text events in square brackets.
[PART REAL_KEYS_M]
[Commits seppuku internally]
Thank you so much!
May 24, 2016 at 9:19 am #469250I am 100% not going after you in any way, but I’m gonna use this thread just to reiterate one thing in case new authors read this: this is why I limit my help to issues I recognise as plausible and I don’t pursue this kind of scenario. If you touch the template in any way, you’re gonna break things. But the important thing is that you’re gonna break things in an unexpected way that makes helping out so time consuming that it’s not worth it. The reason why we distribute this template is so that common mistakes, often hard to track down, are minimized. There is no reason in any scenario to edit a track name: the name is set, so there is no reason to change it or, in turn, to check if it’s correct. Once you open that door, once you touch something that’s not supposed to change, tracking down an issue, as you discovered, can be a matter of days.
Just as a reference, since I first used the correct template right after I fixed the RBN template ages ago (it used to have PART HARM1 as a track name, in example) I have not encountered a single error I couldn’t fix in 5 minutes. This is over the course of years and this is true for over 800 songs I compiled. So, if you work properly, as in don’t edit things that don’t need editing, you just can’t run into an issue you can’t solve very quickly.
May 24, 2016 at 10:01 am #469253[deleted because Farottone’s reply makes a great end to the thread]
-
AuthorPosts
- You must be logged in to reply to this topic.