Vocal authoring, help!
- This topic is empty.
-
AuthorPosts
-
July 12, 2014 at 4:33 pm #390726
Hi! My first custom is almost done, but Magma tells me that no vocal overdrive markers are present, although I placed overdrive markers in my project.
1) Why this happens?
2) Since I’m using the RBN2 Template, what is Range Shift and Vocal Shift? How work Displayed/Non-Displayed Percussions markers?
Thanks in advance!
July 12, 2014 at 4:47 pm #424541Hi! My first custom is almost done, but Magma tells me that no vocal overdrive markers are present, although I placed overdrive markers in my project.1) Why this happens?
Because you haven’t placed the overdriver markers in your project, check again your PART VOCALS track.
January 26, 2015 at 8:27 pm #437094I’m currently having the same issue of Magma error “no VOCAL overdrive markers were detected. Are you sure you want to compile without?”
Not sure what I did different this time, but there are 5 overdrive markers in PART VOCALS matching exactly the size of the phrase markers below them.
January 26, 2015 at 9:27 pm #437099Post the MIDI.
January 26, 2015 at 9:40 pm #437100If you’re wondering about things like that, throwing the MIDI at Song Analyzer in C3 CON Tools will list a lot of information, including how many overdrive markers there are. If it doesn’t see them, and Magma doesn’t see them, they’re not there ” src=”/wp-content/uploads/invision_emoticons/default_SA_wink.gif” />
If it sees them and Magma doesn’t see them, then there’s an interesting situation to look into.
January 26, 2015 at 10:53 pm #437106If you’re wondering about things like that, throwing the MIDI at Song Analyzer in C3 CON Tools will list a lot of information, including how many overdrive markers there are. If it doesn’t see them, and Magma doesn’t see them, they’re not there ” src=”/wp-content/uploads/invision_emoticons/default_SA_wink.gif” />If it sees them and Magma doesn’t see them, then there’s an interesting situation to look into.
You may be interested in this then…
I decided to add vocals to clumy-plumsy’s custom of California. But when I try to compile, Magma pukes.
Magma: C3 Roks Edition v3.2.7
=============================
Build started at 2:45 PM
Starting Nemo's MIDI Validator...
Everything looks good, continuing...
Loading MagmaCompilerC3.exe...
Nemo's MIDI AutoGen process started
Added drum mix events successfully.
Generated fake pro keys tracks successfully
Generated keys animation track successfully
Exported modified MIDI file successfully. All done.
Nemo's MIDI AutoGen process completed
Reading the archive
Project Compiler: Reading project 'C3CustomsPhantomPlanetCalifornia.rbproj'...
Project Compiler: Entering Phase 1 of 5...
Metadata Compiler: Starting...
Metadata Compiler: Done.
Project Compiler: Entering Phase 2 of 5...
MIDI Compiler: Starting...
ERROR: MIDI Compiler: PART KEYS: Empty track found
ERROR: MIDI Compiler: (PART KEYS): Overdrive phrase at [5] has no gems in expert difficulty
ERROR: MIDI Compiler: (PART KEYS): Overdrive phrase at [38] has no gems in expert difficulty
ERROR: MIDI Compiler: (PART KEYS): Overdrive phrase at [60] has no gems in expert difficulty
MIDI Compiler: Done.
ERROR: Project Compiler: Midi compiler failed.
Here’s my project.
Here’s an analysis of the MIDI.
Beginning song analysis...
MIDI File Name: ..................... California.mid
Has Keys?: .......................... Yes
- Expert Notes: ..................... 167 (51.8 NPM)
- Hard Notes: ....................... 118 (36.6 NPM)
- Medium Notes: ..................... 104 (32.2 NPM)
- Easy Notes: ....................... 33 (10.2 NPM)
- Overdrive Markers: ................ 3
- Trills: ........................... 0
- Solos: ............................ 0
Has Pro Keys?: ...................... No
Has Keys Right Hand Animations?: .... No
Has Keys Left Hand Animations?: ..... No
Analysis complete
Before Magma pukes…
Welcome to MIDI Tester 1.1
This program is intended to quickly let you test MIDI after MIDI for compliance with RBN2.0 standards.
All you have to do is drag the MIDI file(s) here. This program will read through it, and create an adequate test project. MagmaCompiler is then called to process the MIDI for RBN2.0 compliance without actually compiling the song (so no time wasted compiling the audio).
You can do back-to-back MIDIs without having to close this form.
Ready to begin....
Found PART DRUMS...
Found PART BASS...
Found PART GUITAR...
Found PART VOCALS...
Found HARM1...
Found HARM2...
Found PART KEYS...
Nemo's MIDI AutoGen process started
Added drum mix events successfully.
Nemo's MIDI AutoGen process completed
Starting Basic EMH Check
MIDI passed Basic EMH Check without reporting any problems
This means the charts most likely have reductions charted
Ready to send files to MagmaCompiler ... hold on.
Output from MagmaCompiler follows:
Reading the archive
Cannot find file: C:Program Files (x86)MagmaC3testtest.rbproj
MagmaCompiler reported some errors. Please see the log for details on what must be fixed.
Process completed in 0 minutes and 0 seconds.
You may drag another MIDI or just click Close to exit.
…and after…
Welcome to MIDI Tester 1.1
This program is intended to quickly let you test MIDI after MIDI for compliance with RBN2.0 standards.
All you have to do is drag the MIDI file(s) here. This program will read through it, and create an adequate test project. MagmaCompiler is then called to process the MIDI for RBN2.0 compliance without actually compiling the song (so no time wasted compiling the audio).
You can do back-to-back MIDIs without having to close this form.
Ready to begin....
Found PART DRUMS...
Found PART BASS...
Found PART GUITAR...
Found PART VOCALS...
Found HARM1...
Found HARM2...
Found PART KEYS...
Found PART REAL_KEYS_X...
Found PART REAL_KEYS_H...
Found PART REAL_KEYS_M...
Found PART REAL_KEYS_E...
Found PART KEYS_ANIM_RH...
Found errors in the MIDI file:
PART KEYS: MIDI note 65 at [3] is not allowed
PART KEYS: MIDI note 65 at [3] is not allowed
PART KEYS: MIDI note 65 at [3] is not allowed
PART KEYS: MIDI note 65 at [3] is not allowed
PART KEYS: MIDI note 65 at [3] is not allowed
PART KEYS: MIDI note 65 at [3] is not allowed
PART KEYS: MIDI note 65 at [3] is not allowed
PART KEYS: MIDI note 65 at [3] is not allowed
PART KEYS: MIDI note 65 at [4] is not allowed
PART KEYS: MIDI note 65 at [4] is not allowed
PART KEYS: MIDI note 65 at [4] is not allowed
PART KEYS: MIDI note 65 at [4] is not allowed
PART KEYS: MIDI note 67 at [4] is not allowed
PART KEYS: MIDI note 67 at [4] is not allowed
PART KEYS: MIDI note 65 at [4] is not allowed
PART KEYS: MIDI note 65 at [4] is not allowed
PART KEYS: MIDI note 67 at [6] is not allowed
PART KEYS: MIDI note 67 at [7] is not allowed
PART KEYS: MIDI note 65 at [37] is not allowed
PART KEYS: MIDI note 65 at [37] is not allowed
PART KEYS: MIDI note 65 at [37] is not allowed
There are 138 other errors that I'm not displaying...
Nemo's MIDI AutoGen process started
Added drum mix events successfully.
Nemo's MIDI AutoGen process completed
Starting Basic EMH Check
WARNING: PART KEYS Hard has the same amount or more notes than Expert
WARNING: PART KEYS Easy has the same amount or more notes than Medium
WARNING: PART REAL_KEYS_H has the same amount or more notes than Expert
WARNING: PART REAL_KEYS_M has the same amount or more notes than Hard
WARNING: PART REAL_KEYS_E has the same amount or more notes than Medium
MIDI failed Basic EMH Check. This means the charts are most likely expert only
Refer to the log to see which chart(s) reported problems
Ready to send files to MagmaCompiler ... hold on.
Output from MagmaCompiler follows:
Reading the archive
Cannot find file: C:Program Files (x86)MagmaC3testtest.rbproj
MagmaCompiler reported some errors. Please see the log for details on what must be fixed.
Process completed in 0 minutes and 0 seconds.
You may drag another MIDI or just click Close to exit.
Been chasing this error all day. It’s driving me batty.
edit: I fixed it too, but I had to use v3.2.5 to do so. It then compiled without changes.
January 27, 2015 at 12:28 am #437112Fixed it, thanks. Like to say what I did but I have no idea.
January 27, 2015 at 4:57 am #437130Before Magma pukes…
Reading the archive
Cannot find file: C:Program Files (x86)MagmaC3testtest.rbproj
DOWNLOAD & INSTALLATION INSTRUCTIONS
Unless you’re coming from a really old version of Magma: C3, you should extract these files over your existing installation so no settings or important files are lost. DO NOT INSTALL IN PROGRAM FILES.
So that answers your “Magma pukes” problem. Follow instructions.
Been chasing this error all day. It’s driving me batty.
Post the project and audio files in the Magma thread so I can try to replicate it on my end. I don’t get the errors when just playing with the RPP you posted.
edit: I fixed it too, but I had to use v3.2.5 to do so. It then compiled without changes.We can’t make progress forward and improve the tools if you guys (and not just you, but I see it happen too often) revert back for any little problem. There’s about 30,000 lines of code to make Magma: C3 run. You gotta give me more than “it broke” or “here’s a shitload of what I think is helpful information but a couple hours later I’m giving up” if you want me to be able to fix things.
Let’s keep it going on the Magma thread.
January 27, 2015 at 11:47 am #437137Hey there Nemo,
I also got the no keys part and no keys overdrive error when attempting to compile a song. It looked just like his except the spots for overdrive were different, of course.
January 27, 2015 at 11:52 am #437138And this is also another song with keys but no pro keys?
January 27, 2015 at 12:03 pm #437139And this is also another song with keys but no pro keys?Yes it was. Sorry I didn’t mention it. D’oh.
January 27, 2015 at 12:05 pm #437140Ok. Post or PM project files. Maybe with the new midi loading changes it’s failing to generate the pro keys chart.
July 28, 2017 at 6:14 pm #488543Same here the vocals are charted and when I put it into the analyzer it says NO vocals!!! no overdrive either!
July 28, 2017 at 6:17 pm #488545Nvm it was muted
-
AuthorPosts
- You must be logged in to reply to this topic.