Skip to content

Instantly share code, notes, and snippets.

@Hans5958
Last active September 14, 2019 11:43
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save Hans5958/a1d1e8c56da70738a6a9b98e48ea93f2 to your computer and use it in GitHub Desktop.
Save Hans5958/a1d1e8c56da70738a6a9b98e48ea93f2 to your computer and use it in GitHub Desktop.
MusiMasta's 2019 Mega Comparison - Markdown Converted

Warning

Please read the entire message before asking questions. The Discord account to send submissions & questions to is Kanna#1555. If your message fails to send, please send her a friend request. If you don’t have Discord, my email is newersupermariobros7@gmail.com. I WILL NOT accept submissions & respond to questions regarding the comparison DM’d to my main Discord account. If you have a basic question (i.e. how to set up PFA/OmniMIDI) please ask the Black MIDI Discord community - Kanna will think of you as a very inferior human if you ask her.

Thanks ~ Kanna Kamui

Introduction

Thanks for your participation in the Ouranos comparison video (if you did)! It was a huge success. People left and right have been asking for another comparison, some asking for redone comparisons of old MIDIs (Tau, Septette 14.9, TFL) and some asking for comparisons of new MIDIs. I recently had this idea of doing a mega comparison. These MIDIs imo have unique, varied crash points w/ sophisticated melodic structures & colorful note art. I purposefully did not choose some MIDIs, such as BA 8.49, as that has 2 very boring sustain crash points (imo).

This comparison will not have as many runs per MIDI, however, for practical reasons (especially due to the fact that this comparison covers 7 MIDIs, which is why there are eligibility provisions defined below!) Don’t worry if you do not meet the eligibility provisions, I’ll make comparisons in the future that don’t have a cutoff (I plan to do a no-cutoff comparison with Unify once the final version of it is released).

So, the MIDIs in this mega comparison will be (in the following order):

  • 9KX2
  • Tau
  • Tartarus
  • Septette 14.9
  • Ouranos
  • Reptilian Dark Ritual
  • TFL 19.4

Eligibility

There are 2 ways to be eligible, you only need to meet Provision 1 OR Provision 2.

Provision 1

If you have 8+GB RAM (12+ for Reptilian Dark Ritual) AND have any one of the following CPUs @ stock clocks OR overclock you automatically qualify for ALL MIDIs.

  • Ryzen 3 1200/1300X/2200G/2300X/3200G (includes PRO equivalents)
  • Ryzen 5 1400/1500X/1600/1600X/2400G/2500X/2600/2600X/3400G/3600/3600X (includes PRO equivalents)
  • Ryzen 7 1700/1700X/1800X/2700/2700X/3700X/3800X (includes PRO equivalents)
  • Ryzen 9 3900X/3950X
  • Ryzen TR 1900X/1920X/1950X/2920X/2950X/2970WX/2990WX
  • i3-8350K/9350K/9350KF
  • i5-6600K/7600K/8600K/9600K/9600KF
  • i7-6700K/6800K/7700K/8700K/8086K/9700K/9700KF
  • i9-9900K/9900KF/9900KS
  • i9-7900X/7920X/7940X/7960X/7980XE/9900X/9920X/9940X/9960X/9980XE
  • i5-6400/6500/6600 AND i7-6700 (if @ all-core OC of 4+ GHz w/ modded BIOS)

Notes

  • Kanna still has the executive permission to revoke eligibility of a CPU on this list if it's heavily underperforming. This is just for convenience's sake.)

  • You are not eligible under provision 1 if you underclock your CPUs (locking the base clock to a clock lesser than its max boost clock) even if they're on this list. You may still be eligible under provision 2 below. Overclocking is ok.

Provision 2

If you meet any one of the crash point cut times below for a particular MIDI, you are eligible to submit a run for that MIDI ONLY (per MIDI qualification).

  • 9KX2
    2:18.3, 3:45.4, 5:49.2

  • Tau
    3:15.7, 5:42.3

  • Tartarus
    2:07.8, 3:24.0

  • Septette 14.9
    3:07.1, 4:33.2

  • Ouranos
    2:48.8, 4:40.1

  • Reptilian Dark Ritual^
    4:24.6

  • TFL 19.4
    3:13.7, 3:53.6

Notes

  • Cut times are cut times. If you are 0.1 secs off, well, sorry. Try doing a rerun maybe, but I’ll be strict with these times so that I'm FAIR with everyone. PFA's counter may not be completely accurate. I will calculate most release times by hand using 60FPS timecode; inputs rounded to the nearest 10th of a second before each calculation. I will let you know if your run is in/eligible.

  • ^ The PFA counter is inaccurate on this MIDI due to the nature of the crash point. You must use a timer while running the MIDI. Press start on the 1st note and stop when the MIDI has released. Due to reaction time, you may submit your run if your time using this method is within 1 SECOND of the listed time above. I will calculate the time by hand using 60FPS timecode and let you know if your run is in/eligible.

  • The crash point times I’ve listed should be quite self-explanatory. If you’re confused on which crash point a time corresponds to, feel free to DM me.

Rules

*I’ve split the rules into “required” & “suggested”. If you don’t follow the requirements, your submissions will NOT be accepted. However, I hope y’all are good people & also follow the suggestions.

Required

  • You must use original stock PFA (link below) & it must be a legit run (no slowdowns/speedups) (http://kaleidonkep99.altervista.org/pfamirror/downloads/index.html - V1.1.0 on this page)
  • Only raw SCREEN recordings, no video/audio edits. No camera recordings. Runs MUST contain audio. All 128 keys in PFA must be displayed.
  • NO RESUBMISSIONS for any reason unless I ask you to redo them. Make sure you’re happy with your submission before handing them to Kanna.
  • You may submit 1 run per MIDI per CPU. That means you could submit 14 runs if you have 2 CPUs that qualify for all the MIDIs!

Suggested - If You Want to be a Good Person

  • Please upload your submission to YouTube! I understand YouTube degrades the bitrate, but I will compress your submission anyway. Do the favor for Kanna so that she doesn’t have to work with 5+ GB video files, thanks (Wi-Fi in the dragon world is apparently very slow unfortunately).
  • Please submit ALL of your runs at the same time. That makes it much easier for me.
  • If you use PFA Configurator, please don't set the note speed below 0.05. 0.05 is the note speed PFA plays at when you move the "Notes" slider all the way to the right. 0.025 is the suggested note speed for Tartarus as that MIDI has pretty dense note art.
  • Please install LoudMax so that you don’t ruin the comparison video’s audio.
  • Set PFA’s background color to black.
  • Give Kanna a cookie. :)

Clarifications

  • You don’t have to make new runs for these MIDIs! A lot of these MIDIs are old classics so you may have already made a run of them.
  • Just because I know you made a run doesn’t mean I’ll automatically include it. You MUST submit your run to Kanna#1555 or newersupermariobros7@gmail.com. Kanna will reply that “your run is accepted” when it has been accepted. Kanna hasn’t gotten to your submission if there is NO REPLY. Please give her up to a week to reply. If she hasn’t replied by then, please DM a quick short message like “bump” that bumps the DM up.
  • I’ll try my best to upload the video in 5K/8K resolution again to circumvent bitrate issues on YouTube. I’ll also make all those graphs again and perhaps do some data analysis to boot (I’m currently taking AP Stats so I might be able to put some new insight into the analysis this time around!)
  • Advanced OCing is allowed - single-core/CCX/CCD OCing, etc. You may disable certain parts of your CPU (cores/threads) to obtain a higher overclock. I only need you to report the highest frequency when you make your submission as PFA is single-threaded (d3dx9_43.dll).

Submission Format for 1 CPU

Please don’t include any information not covered by this template.

Name (that you want to be known by in the comparison video, shorter is preferred): --- CPU: (CPU Model) @ (Stock or OC) (Cache OC, if applicable) RAM: --- GB GPU: --- 9KX2: (video link) Tau: (video link) etc etc

MIDI Downloads

(in the description of the videos listed below)

Timeline

Guess what, there’s no timeline yet! I do not actually plan on making the final video anytime soon. Maybe I’ll make the video in November, or maybe, January. I don’t know yet. I will immediately begin post-processing your submissions into “groups” and all that as soon as you send them to me however. Please submit your runs as soon as possible. I will announce the deadline once I have figured that out. Y’all will have AT THE VERY LEAST the entire month of September to submit a run.

Why am I not making the video right away?

I’m busy with school, a full-year internship, and college applications. I also want to give enough time to let the Ryzen 3000 chip stocks settle since many people have mentioned that they’re planning to upgrade to a Ryzen 3000 build. Also, for this mega comparison, one can submit 7 (actually more, I’ll explain below!) submissions. Given the immense difficulty some had with just submitting ONE run in 2 weeks last time, well, more time makes sense.

Rights, Terms, and Conditions

Just here for safety & privacy concerns.

By entering a submission into this comparison, you agree to the following:

  • You allow MusiMasta to download your video for the purpose of usage in the aforementioned comparison.

  • You allow MusiMasta to render & upload a comparison video (which will be unmonetized~) to MusiMasta's 1st YouTube channel (https://www.youtube.com/c/MusiMasta) which will include your video.

  • You allow MusiMasta to include identification info (including but not limited to: name & computer specs) in the description of the video.

  • Runs may be rejected for any reason, but there will always be a follow-up reason stating why. Do not beg, stalk, flame, etc, if your submission is ultimately not included in the comparison. That being said, I will try my best to include every eligible submission.

  • The status of this comparison (whether it occurs or not & how many MIDIs it ends up covering) will depend on the # of people who participate.

  • ~ The comparison video will be unmonetized on my end. However, some of the MIDIs are of songs that have legal 3rd-party claimants. I will edit the video description detailing what has been claimed if a claim arises. Thus, the video may still have advertisements running on it. Sorry about that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment