Skip to main content

Review: 【Original Song】愛の小さな歌 || Ai no Chiisana Uta - Moona Hoshinova

 


This ballad song is the song about Moona thanking her fans. It takes minimalistic approach using piano and digital strings.

I like the lyrics and the emotion in the singing. The chord progression also helps to convey the emotions throughout the song. It's a nice ballad.

However, it has fatal flaw on how the String and the keyboard layered together. On parts like the chorus and the climax, they have erroneous sounding. Like listening to two songs with different keys at the same time.

Studi Suara called this as dissonance. He tactfully said may be this is part of the song. Well, he probably afraid being attacked by mindless fans. It really not sounds well to me as well.

Based on my listening, I think the problem lies in the sustaining sound of the keyboard. It clashed with the String and the next key. The keyboardist played as if only he/her/them that will fill the song.

I tried to find covers as comparison and found djalto cover have it better. She made the first section with keyboard only and layered them with backing vocal adlibs. At the last part, keyboard and the string left some space for their counterparts. This making the sound more enjoyable to me.

I think I can give an example of the similar song to explain better.

This song style reminds me of Nero's Glow song. However, Nero approach for it is to make the strings staccato while Moona's makes every instrument played in sustain.

Also, listen to the Nero bass. The sustaining sound in lower frequency and it is subdued. Moona's sustaining sound in lower to mid-range persists a few beats. 

By the end of the day, I agree with Studi Suara to restructure the chords. Additionally, they need to make the melody sparser. It's too crowded.

The current strong structure is not for my ears. The way it is presented is too noisy like two different songs collided. That's how I feel when listening, may be others find it acceptable.


Comments

Popular posts from this blog

STAN vs. UI

Ugh, kasihan banget adek gue. Saking kepinteran dia jadi dapet Akuntansi UI dan STAN. Jadi bingung mau masuk yang mana. Beberapa orang (termasuk orang tua gue), menyarankan masuk STAN. Gue malah memperburuk suasana dengan membela memasuki Akuntansi UI, maklum bela almamater. Duh, gue jadi merasa bersalah bikin dia ragu-ragu. Kira-kira enakan masuk mana, yah? Gue juga gak tahu keuntungan masing-masing. Hasil debat sementara: ~ Untuk jangka panjang masuk UI, untuk jangka pendek STAN. ~~Tapi, dia itu kan cewek, ntar pas menikah kemungkinan besar karir terhambat. Eits, ntar, dulu, sekarang kan jamannya emansipasi, bisa aja cowoknya yang jadi BRT. ~ STAN sarang korupsi, kalo masuk STAN jadi pegawai negeri. Kalo mau kaya harus korupsi. Tapi kalo masuk UI, lulus masuk jadi akuntan publik. Sekarang ini, orang membayar akuntan publik untuk memanipulasi nilai pajak dan aset. *SIGH*. Jadi gak ada yang beres ~ dll. Yah, udah gue jadi bingung, apa lagi dia nanya saran gue. Buah, gue gak pengalaman ...

Installing Goodix Fingerprint Reader Driver on Fedora

I currently have a Lenovo Thinkpad L14 laptop equipped with fingerprint. I was `belok` from KDE Neon to use Fedora 40 because of someone. Now I am tempted to enable my fingerprint: lsusb | grep -i fingerprint Bus 001 Device 004: ID 27c6:55b4 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Dump the firmware Assuming this is a fresh install, lets do some magic by getting some dependencies: sudo dnf install gcc git python-pip python-devel openssl Let's get the source code: git clone --recurse-submodules https://github.com/goodix-fp-linux-dev/goodix-fp-dump.git cd goodix-fp-dump Create an isolated Python environment: python -m venv .v source .v/bin/activate Do the magic: sudo su pip install -r requirements.txt python run_55b4.py exit There are some python scripts available. I run run_55b4.py because my device ID is 27c6: 55b4 . It will spell some nonsense, which is a good thing. That nonsense actually the firmware captured by our device. Also, I typed exit becaus...

Vibe Coding Workflow

I am currently working for having A.I. workflow for generating projects. There are two things that need to be tackled for that: 1) hallucinations; and 2) old codes. I have met several patterns to tackle those two and just need to formulate the patterns into a general flow. Thankfully, a video of building fullstack app using A.I. from Raf Dev channel inspired me to make the formulation. He used multiple A.I. engines to his need: He used Google Gemini to onboard his ideas and summarized it. He forked a boilerplate of NextJS project into a new project. Then, he added the summary from Google Gemini into a file for context. He used QWEN Code, a QWEN3 code engine that is a fork from Gemini CLI, to build the project. When working with an existing project, A.I. will take the whole project as a context. It also means that it will stick with the version used by the libraries. It also will try to update its knowledge based on the common pattern in the project. Most of the time, it will use the c...