[thomeval]

Thanks for your efforts ” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif” /> The guitar reductions have been taken care of (since we use lower difficulties extensively here), and I’ve uploaded v2 of the CON that includes all of your awesome work.

[thomeval]

Thanks! Much appreciated.

[thomeval]

I’ve just finished charting my contribution for Week 2. If anyone is available to sanity check it, it would be greatly appreciated ” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif” />

 

Audio Adrenaline – “Move”

viewtopic.php?f=17&t=4919

[thomeval]

Updated version has been posted. Everything should be fixed or at least better.

 

One thing I’d like to bring up is the relative pitch on guitar at 22-23 issue. I ran the audio through a vocal remover and I get this progression: 3 1 3 1 3 1 3 1; 2 1 2 1 2 1 2 1. If you’d like to triple check, I uploaded a snippet of the audio for this section here: https://www.dropbox.com/s/zj7nr2b1wzhhk … remove.ogg

[thomeval]

You do realize that the review was only posted on Monday, after more than a month of inactivity, right? Is it usual procedure to demand all requested changes to be made on the same day?

The mitigating factor is that it’s your release week, so yeah, in this particular ~7-day window we’d like you to keep an eye on your song’s thread. I know we haven’t done a great job of communicating this. I’m not trying to come down hard on you or anything.

 

I’d recommend subscribing to your PT threads to get emails on them, especially when it gets closer to release:

 

 

Will do, thanks.

 

As for the drum solo: I absolutely agree that the drums is the support role during this section. The solo has a ‘guitar and drum solo’ feel just like No One Knows (Queens of the Stone Age). That’s basically what I was going for here. It plays well in-game, but I’m probably not being totally objective about it, so I’ll remove it for next release.

 

The when is actually irrelevant, because knowing you couldn’t have done an hour worth of fixes, before the deadline you should have posted a “guys, if you don’t check the song I’m gonna pull it, I’m not gonna have time to fix anything” message. The reason why we do sanity check is because songs have issues, which as you can imagine we don’t introduce… We don’t *enjoy* having to check the songs, we do so in order to make our authors shine: we do it for you, please understand that it’s should then be you the one most interested in staying on top of that.

 

Ignoring the rather curious “its your responsibility to tell us to hurry up” requirement, I’m not trying to sound ungrateful for the work the C3 staff is doing here. The level of detail of these inspections are far higher than I could ever manage, and will certainly make the end product shine (thanks to pksage, Nightmare Lyre, and whoever makes the videos). I just don’t like making last minute changes – it is out of respect for the testers that I would like to take time in making the suggested changes properly. Nonetheless, I should be able to comply with them by Thursday night, as requested. That is, assuming I have no issues uploading it.

[thomeval]

It’s way too late for that, video recording has been done as per the the usual deadline we have provided our authors (Monday night is the deadline, posted in the scheduling thread). You can’t just check back on your song on Wednesday and pull it, it just isn’t respectful of the work testers, sanity checkers and video recorders do to help you make your song look the best it can.

 

You do realize that the review was only posted on Monday, after more than a month of inactivity, right? Is it usual procedure to demand all requested changes to be made on the same day?

[thomeval]

Noted. I’m not keen on removing the drum solo, but if you insist I’ll do so. Due to the number and severity of changes here, I’ll need to request that the release date be bumped. I’ve moved it on the scheduler accordingly.

[thomeval]

Thanks for the detailed feedback! Unless I note otherwise, I’ll make the changes you suggest.

 

Tempo map: I tested it in phase shift and the timing of the entire chart seems to be too late. I’ll shift the audio a bit (45 ms) to see if it helps.

 

All guitar sustains have been adjusted as per your advice.

 

Expert Guitar:

 

12.2 12.4: This sounds like an A# and F together. If it is, the current notes make more sense. I am hearing it wrong?

 

22.1 etc: Took some effort, but I finally deciphered the actual note progression for this section – it alternates between low and high. I will update it accordingly.

 

28.1 etc: I can’t hear the clean guitar at all at this point. I only hear it at 31.1, so what would the notes be?

 

36.1 to 39.4 etc: I only hear three notes during this section from that guitar. If that’s the case, I’m hesitant to use that instead of the rhythm guitar.

 

97.3: The drum solo ends here, and can’t be moved forward like the guitar solo. Wouldn’t it make more sense to end them at the same time?

 

Good advice for Easy Guitar, to use Y/B/O only during the solo. Personally I don’t like the ‘use five colours on Easy’ rule. I will update this chart accordingly. I may do the same for Medium, but I’m not sure yet.

 

Vocals:

 

The ‘o’ in radio: There is a A# AND a C# here. Its already in the two HARM tracks.

Harmonies are a bit off: I respectfully disagree. Pretty sure the note pitches are correct, unless there’s a specific part that you’d like to point out.

115.1 – write numbers as words: I checked what Space Oddity does (it uses words), and I’ll use that as precedent.

I’ve never considered phrase marker position or gap length as issues (I generally went with any non-zero gap as fine, and phrase visual issues have no actual impact on the gameplay), but I’ll reconsider.

 

There are also some pretty serious allegations against the vocal charts, so I’ll likely look into them last. It may also be compounded by the timing map. For the rest, I’ll post an update soon.

 

Thanks again for the feedback.

[thomeval]

Congrats on the release Nemo!

 

For those interested, it is possible to run the MIDI tester directly by using the normal Windows Open With… and Send To… commands on any .mid file. Since v2.1, this doesn’t need any special tweaks; it just works like any other Windows program.

 

HOW TO ADD MIDI TESTER TO WINDOW’S OPEN WITH AND SEND TO COMMANDS

 

You can associate MagmaC3 with MIDI files by using the usual Right Click -> Open With -> Choose Default Program command (Or whatever its called for your particular OS version) on any .mid file.

 

To make it work with the Send To… command, create a shortcut to MagmaC3 in your SendTo folder, which is in C:Users[YourUsername]AppDataRoamingMicrosoftWindowsSendTo . However, this will make it an option for ANY type of file, regardless of whether MagmaC3 supports it.

[thomeval]

It’s your lucky day. I struggled with this exact problem today for a couple hours. The problem is in the tempo map. At some point in your song the time signatures are not lining up exactly at the start of your measures.

 

…

 

YOU ROCK!!!

[thomeval]

The most common cause of this is hitting an arrow key when you’ve got the MIDI track selected, moving it to the right or left by one puny tick. Try selecting the MIDI track in REAPER’s main window and nudge it to the left as far as you can with the left arrow. Alternately, you can right click on it, bring up the item properties window, and make sure the start time is 0:00.000.

 

Thanks for the tip, but the MIDI track item is positioned correctly at 0:00.000. What’s the second most common cause?

 

Also, just for kicks, try quantizing for both position and note end, that helps when the fill markers are ever so slightly shorter than needed.

 

I think it was already set to this. I quantized it again to be sure, and the issue persists.

[thomeval]

Yes, I’m sure I have the latest public version of MagmaC3 (although the about screen says v1.3.4, the readme is 1.3.5). And I’m definitely not confusing vocal_tonic_note with song_tonality.

 

I hope you don’t mind, but I did some snooping around, and it looks like the bug lies here (MainForm.cs, readC3Fix() ):

 

if (str1.Contains(“TonicNote=”) && !str1.Contains(“-1”))

{

this.ComboTonicNote.SelectedIndex = Convert.ToInt32(str1.Substring(str1.IndexOf(“=”, StringComparison.Ordinal) + 1, 1));

this.chkTonicNote.Checked = true;

}

 

This will not work correctly if the vocal tonic note is more than one character long.

[thomeval]

Minor bug: It looks like the current version of Magma C3 doesn’t save the vocal_tonic_note setting properly if its 10 or above (A# or . It saves either as 1.

 

Thanks for all the hard work with this tool.

[thomeval]

As a vocals player, I find it very useful, particularly for new or unfamiliar songs. Otherwise, the guidelines that appear on the background of the vocal highway aren’t very useful. I’d like to see them included, especially since all RB3 songs (disc and non-RBN DLC), have them.

 

Also, on the RBHP project, tone information is standard. I believe the lack of it is considered a bug? In any case, I’d be happy to send a couple updated .dtas with this data added for the recent release, if it would be useful.

[thomeval]

‘Psycho’ plays great in RB3, including harmonies, but it doesn’t have the vocal_tonic_note set. Pretty sure it should be F Minor (vocal_tonic_note 5, song_tonality 1).

 

Apologies if this report is in the wrong thread; this song isn’t listed on GHtoRB3 or the list above.

 

Thanks for a great release ” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif” />

[Author]

Posts