Could not find MIDI track authored for real_keys, possibly due to incorrect track name event
- This topic is empty.
-
Posts
-
I have muted all the pro key tracks so just part keys in unmuted. I have unticked the pro keys and have ticked both auto generate pro keys and auto generate keys animations in magma, and yet im still getting this error. have I missed something?
Nope, still not working.
http://www.mediafire.com/download/vuf8w … ted+V4.RPP
thats my project, if anyone wants to have a look and see what im missing
” src=”/wp-content/uploads/invision_emoticons/default_SA_frown.gif” />I see that your .rpp had the Pro Key’s muted.
To my knowledge, you need to export the Pro Keys (even if empty) and then Autogenerate. It still needs the the track in the midi to process. That built for me doing it that way.
I had tried that earlier but I got this:
ERROR: MIDI Compiler: d:/rockband/making customs/magmac3/test/complicated v4.mid (PART REAL_KEYS_X): File: e:prjrbnsystemsrcbeatmatchSongParser.cpp Line: 2394 Error: mKeyboardRangeSecondPitch == -1
This means you didn’t author Pro Keys but left the track in the MIDI – you must mute unauthored tracks in REAPER before exporting
On the X_Pro Keys track, there is a midi note over all the view range options at the bottom. Remove all but one of them and try that. The RB3_Template.rpp has that issue where you have to make only the correct range on the X_P keys.
That got it! thank you so much!
I’m guessing i’ll have to delete them everytime I open the template then.There was a topic about this before somewhere, and Trojan fixed some of the issues on the template. If yours is over a month old then I’d redownload it. From my* knowledge, this is what I remember being an issue:
– X_Pro Keys has all range views selected. You need to remove all but one.
– REAL_BASS has the wrong track name. It is using REAL_GUITAR’s track name, and if you plan on doing real instruments you have to switch that.
– Some editors have things like “view all midi notes” and “view velocities handles” on and such.
A good tip would be to open up a new project, and load the C3 template. Here, make ANY changes you want to the template that you prefer. I personally fixed those issues, and then preloaded the “color-maps” to each track. After you fix everything…. File -> Project templates -> Save project template. Here, you can overwrite the original C3 template with the updated/fixed/personal one. Very helpful for future customs.
I believe there was a reason for all the pro keys to be noted; something along the lines of if it throws an error you’ll remember to change the range views before compiling. However, as long as you remember, you’ll be fine.
– X_Pro Keys has all range views selected. You need to remove all but one.– REAL_BASS has the wrong track name. It is using REAL_GUITAR’s track name, and if you plan on doing real instruments you have to switch that.
– Some editors have things like “view all midi notes” and “view velocities handles” on and such.
The REAL_BASS/REAL_GUITAR thing was fixed a while back.
The reason for the all range thing is to keep them visible if you hide unused notes. But now that I think of it, you wouldn’t get the horrible compiler message if I just staggered them instead of laying them on top of each other. I’ll tweak that tonight.
I’ll try and tame the funny views too – thanks for reminding me it needs attention.
The reason for the all range thing is to keep them visible if you hide unused notes. But now that I think of it, you wouldn’t get the horrible compiler message if I just staggered them instead of laying them on top of each other. I’ll tweak that tonight.
I only ever use “Hide unused and unnamed note rows”, so I would have never thought about that. Makes sense on why you would do it. I just don’t see the point of not using unused/unnamed since only use unused will cause any files without reductions or animations yet to be missing a lot* of rows.
- You must be logged in to reply to this topic.