IIDX DP hand positions – basics (by ereter)

Translator’s note: this is Korean -> English translation of ereter’s article here.

Before we begin

In this post, I have summarized the DP hand positions that I use. This post is not about “DP must be played this way” but it’s closer to “DP can be played this way”. I think that for DP hand positions, there is no one answer to rule them all, but I thought it would be useful to share a set of positions I use while I play.

This post is split into three parts. In this post – basics – I will talk about how each finger corresponds to button(s). Everything below is in reference to the right hand. ☆ refers to the IIDX scale, and ★ refers to the insane (発狂) BMS rating.

Thumb

Your right thumb hits #1 and #3.

In general, your thumb should be above #1 key, but when you see chords or streams that include #2+#3, the thumb should cover #3 to handle it sufficiently, so your thumb must handle both #1 and #3.

Index finger

Your index finger hits #2 and #3.

In general, the index finger should be on #2, but if there are things like #1+#3 chords, it should hit #3.

From the explanation above, #3 is covered by both the thumb and the index finger. In reality, out of all 7 buttons on one hand, #3 is the button that switches around what finger is covering it. Personally I believe that when you are able to handle #3 with both the thumb and the index finger, you have mastered the basics of DP position. When I started DP I only used my index finger to hit #3, but when #2+#3 patterns show up, I put an effort into using my thumb in order to learn this play style. It’s probably when you play ☆11s you’ll start to learn this play style, and when you are comfortable with low-mid ☆12s (= ★3) you’d be comfortable with hitting #3 with either finger.

Middle finger

The middle finger only hits #4.

When the other four fingers are on their home row, it’ll be really difficult to use your middle finger to hit #3 or #5, because it’s unnatural for your fingers to move that way. Therefore, fix your middle finger on the #4 key for stability.

Ring finger

The ring finger is responsible for #5 and #6 keys.

In practice, the ring finger is the most natural choice for pressing #5 and #6 keys. For #5+6 chords, drag (/slide) your ring finger down from #6 to #5. For #5 ->#6 16th notes, use the ring finger to rapidly hit them in succession. Among DPers, they refer to this as Ring Finger Slide or Ring Finger Hokuto (北斗, to hit individual keys rapidly).

Pinky

The pinky only hits #7.

Anatomically, the pinky can’t really hit anything other than #7; therefore, fix it on the #7 key. For bass rushes, this is one of the reasons for “bass on #7” being the easiest.

Summary

For high-density streams, other than #3 button, I use a static mapping of each key to one finger; the middle finger handles #4, ring finger hits #5 and #6, pinky is #7. Additionally, even for #3 key, for high-density streams I tend to use my thumb rather than my index finger. If you map (thumb, index, mid, ring, pinky) to (13, 2, 4, 56, 7), this minimizes the finger movement, so I believe this is the DP basic finger position.

(again, this is originally written by ereter, from https://ereterblog.wordpress.com/2016/11/19/dp-%EC%86%90%EB%B0%B0%EC%B9%98-%EA%B8%B0%EB%B3%B8%ED%8E%B8/)

Workaround for Logitech C922 Pro Stream webcam not saving video settings

I bought one of these for streaming (here is my YouTube channel):

c922-pro-stream-webcam.png

It’s a good webcam, but it turns out the webcam does not remember any of the video settings (the dialog below) — this includes brightness, sharpness, auto white balance, auto focus, gain, auto exposure, etc. If you unplug your webcam and plug it back in, all of these will get reset to default! Same thing if you ever reboot your computer.

Capture.PNG Capture.PNG

This might not be a problem for everyone, but for a “pro streamer” which is apparently the target audience for this (as indicated in its product name), this is a HUGE problem! Most likely, you’d want to keep the auto focus permanently disabled, use a custom white balance, and adjust exposure and gain according to your lighting.

Logitech has indicated that this is indeed by design:

Capture.PNG

Thankfully, this webcam uses the Windows in-box webcam drivers (KS + USBVideo), which means you can use the standard API set to interact with it. Github user SuslikV has already done most of the work here: https://github.com/SuslikV/cfg-cam

You can follow these steps:

  1. Download a release of cfg-cam from here. I’m using 1.0.
  2. Extract WebCameraConfig.exe.
  3. Open a command prompt and navigate to where you extracted it.
  4. Open your webcam settings dialog and modify settings as you desire.
  5. Run WebCameraConfig.exe –savedev. It’ll save cam_sett.cfg to the current directory. It looked like this when my Logitech C922 was plugged in:
/ WebCameraConfig settings file
Device #1
\\?\usb#vid_046d&pid_085c&mi_00#8&1cce1212&0&0000#{12121212-1212-1212-1212-00a012121212}\global
C922 Pro Stream Webcam
VideoProcAmp_BacklightCompensation=0 [Manual]
VideoProcAmp_Brightness=128 [Manual]
VideoProcAmp_Contrast=128 [Manual]
VideoProcAmp_Gain=29 [Manual]
VideoProcAmp_Saturation=128 [Manual]
VideoProcAmp_Sharpness=128 [Manual]
VideoProcAmp_WhiteBalance=4000 [Manual]
CameraControl_Exposure=-4 [Manual]
CameraControl_Focus=0 [Manual]
CameraControl_Pan=0 [Manual]
CameraControl_Tilt=0 [Manual]
CameraControl_Zoom=100 [Manual]
---end of the device #1
  1. Edit cam_sett.cfg as needed. You might have more devices in the file (such as your capture card) — erase them if you want. Make sure to keep the formatting consistent — check the “Device #1” and “–end of the device #1” part.
  2. You’re done! Whenever you want to restore these settings, run WebCameraConfig.exe from command prompt. It’ll read the file you saved and apply the saved settings to your webcam.
  3. You might want to create a small batch script for automating this. Here is mine:
@echo off
pushd %~dp0
.\WebCameraConfig.exe
popd

I have it configured so that this script is called when I launch OBS. Maybe you’ll want to do that, maybe you want to run the script when Windows boots.

Caveats: some settings are not stored or restored – anything that isn’t listed in the file is not saved. For my purposes this wasn’t really a problem.

SP皆伝

I got SP kaiden today. I wanted to jot down a few things before I forget.

Results

  • stage / groove gauge / clear rate
  • p+p  / 30% / 75%
  • BSB / 30% / 58%
  • Himiko / 32% / 70%
  • mei / 58% / 73%
  • Overall 69% (nice)

Playstyle

I play a mix of TAKA.S and 1048. About 50:50 split between the two playstyles, depending on the density / scratch patterns. For example,

  • TAKA.S for the entirety of HAERETICUS
  • 1048 for the entirety of quell
  • a good mix of both for MENDES

Hardware:

  • Switch: 50g
  • Spring: 60g

Skin:

  • bomb = 9th Style
  • judge =メタリックブルー
  • notes = パステル
  • key beam = ショート
  • sudden+ = default

Progression History

  • 2006 – release of Distorted AC – first time playing 7 key, was playing 9s on USKOC back then, but stopped playing around the time Troopers was released.
  • I was playing “claw”
    • 파일:external/gigglehd.com/0aae8273b62fd1bcd78dfbf5654a3b78.jpg파일:SL4g48E.png
  • July 2015 – Round 1 Southcenter opens in Seattle. I start playing IIDX occasionally again. For a year, I was playing SDVX mostly until I hit 十段 in that game.
  • June?? 2016 – 八段
  • July 17, 2016 – 九段
  • October 5, 2016 – first 12 NC (紅牡丹)
  • December 10, 2016 – bought my DJ DAO PEE
  • December 29, 2016 – 十段
  • December 31, 2016 – Level 11 NC lamp on Sinobuz AC
  • January, 2017 – I started to feel the limits of the “claw”. During the month of January I learned 1048 while playing Infinitas.
    • My right hand still does not use the pinky. Instead, I use ring finger for #7
  • April, 2017 – started to feel the limits of non-wrist 1048 thanks to MENDES. Started learning TAKA.S — still no pinky though.
  • May 12, 2017 – 中伝
  • August 10, 2017 – 発狂BMS 二段
  • September 12, 2017 – 発狂BMS 三段
  • October 17, 2017 – Passed BSB for the first time in 皆伝 course
  • February 10, 2018 – On this day, my “BMS recommend” rating was 8.58
  • February 15, 2018 – changed GN from 276 to 264
  • February 15, 2018 – Bad Maniacs, 天空の夜明け HC
  • February 16, 2018 – MENDES, quell HC
    • Snapshot of iidx12.tk on this day:
      • NC: 2018-02-17-kaiden
      • HC: 2018-02-17-kaiden
  • February 17, 2018 – Classic 皆伝
  • February 17, 2018 – 皆伝 !!!

On the day of

  • Had a cup of coffee and then started playing around 7pm
  • Warmed up playing:
    • the trigger of innocence
    • you’ll say now
    • waxing and wanding
    • #MAGiCVLGiRL_TRVP_B3VTZ
  • Played Classic Kaiden, passed for the first time
  • And then into Kaiden…

During

  • non-ran
  • sudden+
    • WN = 240
    • GN = 264
  • no hat … because I don’t have one…
  • in the last slow section of Himiko, I “floated” and went from <10% to 32%. This helped a lot.
  • During Mei, I had 90% or so before the slowdown; came out of speedup with ~10%

What helped?

  • Coffee???
  • Learning 1048 and then TAKA.S
  • Practicing BSB separately. During October 2017 I played BSB multiple times a day (in a row) until I was comfortable.
  • Focusing on reducing BP – trying to easy clear and then into hard clear
    • Additionally, working on timing as well
  • Changing GN a few days before. I was on 276 for a few months; reducing to 264 had a huge impact, and I started hard clearing bad maniacs / mendes / quell afterwards
  • Practicing Bad Maniacs, Mendes, quell, 天空, Haereticus
  • This video: Beatmania IIDX 단위인정 개전 冥 공략 (Korean Subtitled)

What I could have done better

  • Taking a long break in November / December of 2017. I was barely playing IIDX.
  • Learning to use the pinky on my right hand.
  • Experimenting more with GN, perhaps?
  • Not obsessing over clears, but instead playing a variety of charts

Closing words

I’d like to thank all of my friends and IIDX rivals for the support.

 

Bonus – from my YouTube channel that no one watches:

beatmania IIDX23 Copula STEP UP mode explanation

This is a rough translation… but hope it helps.

TLDR of the story: you’re going around the city, visiting train stations, and helping out local business so you can make the ultimate parfait. Seriously.

Each station has one ingredient that you need in order to complete the story mode. The overworld map is a single “line” of subway line – you start in the middle station, and you can move one station to the left, or to the right, after each credit. When you collect all ingredients from each station, a final station appears next to the starting point, and once you clear that final station, you see the ending for STEP UP.

The map is the following:

  1. Strawberry
  2. Pineapple
  3. Pudding
  4. Watermelon
  5. Melon
  6. Orange (you start here)
  7. Parfait (this is the final boss station – only appears when you cleared all other stations)
  8. Cherry
  9. Banana
  10. Kiwi
  11. Cream

At each station, you see the leader character that you have to “defeat” on the left side. On the left there is a little picture (e.g., an orange) that’s grayed out. Each time you complete a song (without failing) you fill up that fruit-meter. For normal-clear or assisted-clear, you get 33%. For Hard gauge clear, you get 50%.

Once you beat all stations, Parfait station will appear. Note that its location may be left of Orange, or right of Orange; it shows up closer to your current location. Once you clear the final station, you get ending credits.

Dokimeki meter (the little heartrate monitor thing on the top right) – if you choose the Dokimeki folders, which has a list of songs you cleared previously, you fill up the Dokimeki meter. Easy clear fills up the gauge by 1/6, normal is ¼, hard clear / full combo is 1/3. If you fill up this meter, you get the avatar for that station. It will ask you Yes/No – if you choose yes, you equip the items right away, if you do no, you still get them but they’ll go to your inventory.

Quests – they are random. They are things like, get less than 500 GOODs over 3 songs, etc. If you clear quests twice, you can move up to THREE stations left or right.

 

 

WinJS apps: programmatically open the App Bar, Nav Bar and the settings pane

It’s been a few years since the release of Windows 8, but teaching users how to use the edgy swipe is still difficult.

When I was first designing it, I added the search box to the top right because context-sensitive search charm is perhaps the most difficult to grasp for new users. This works really well, because a text box with a magnifying glass button next to it has good affordance.

However, I was still getting questions on how to change settings in the app, such as video quality.

So – I’m giving up. Instead of trying to explain things to users unfamiliar with edge swipes, I’ll be adding a “Gear” icon and “More” icon to Windows version of my Giant Bomb app:

GB app on Windows

See: top right corner.

Here is how you invoke a Settings pane (MSDN):

Windows.UI.ApplicationSettings.SettingsPane.show()

Here is how you open the nav bar (MSDN).

App bar is practically the same as nav bar (MSDN).

I noticed that this also helps with Windows 10 because edge swipes are gone.