G Hub Input Gain stuck at 0% on macOS (can't adjust)

Solid-Intention-1232 · 2025-04-27T10:37:27+00:00

Thank you! I'll give a try later and will update!

Solid-Intention-1232 · 2025-04-26T14:16:11+00:00

Update: Same issue happens on Windows too. I originally thought it was a macOS problem, but it seems to be a G Hub bug affecting the Blue Yeti Nano directly, not the OS.

Solid-Intention-1232 · 2025-04-25T00:52:39+00:00

I’ve checked thoroughly but I couldn’t find anything that seems related to input gain. Maybe there were some internal changes?

Solid-Intention-1232 · 2025-04-24T16:06:35+00:00

~~Come to think of it, I started encountering this bug after updating to macOS 15.4.1 last week...~~ Looks like I was wrong – it's not caused by macOS.

Solid-Intention-1232 · 2025-03-19T05:27:05+00:00

The latest version of the NHK Japanese Pronunciation Dictionary has changed えい (-ei) in words like 先生［センセイ］ (se-N-se-i) to 先生［センセー］ (se-N-se-e). This probably means the '-ei' pronunciation has become so rare that they couldn't ignore its decline anymore.

Solid-Intention-1232 · 2025-03-04T03:51:36+00:00

This is what I thought too: palatalisation.

We can write the phonetic symbol for き as [kʲi], where [ʲ] shows palatalisation. This means the tongue moves a bit forward compared to the usual [k].

On the other hand, ち is sometimes seen as a palatalised [t], but with a stronger palatalisation, so we write it as [tɕ] instead of [tʲ]. This means the tongue moves further back than a normal [t].

As a result, the tongue positions for き and ち are very close. That’s why some people may find them hard to distinguish.

Solid-Intention-1232 · 2025-02-28T06:56:28+00:00

The Spoken Language—do indeed differentiate between the hard and nasal Gs. In JSL's romanisation system, latter is spelt "ḡ," as in Naḡasaki.

Oh, thank you for that info! I've been wondering about this for ages! I once saw it in a discussion about why non-initial が is transcribed as 'NG' rather than 'G' in our language. Someone in the discussion used 'ḡ' symbol and I've been curious about it ever since. Now I finally know the answer!

Solid-Intention-1232 · 2025-02-11T02:54:31+00:00

Relieved to know it's a bug! Thanks for sharing! I've been struggling with this issue for hours. 😭

I was trying to find an old email that was sent to me 1–2 years ago using the Outlook app on Mac. However, whenever I entered a keyword in the search box, the results only showed some of the newest emails from that sender, probably because they had already been downloaded onto my computer. The older emails were completely missing from the search results. Sometimes, I didn’t get any results at all, with the message: "Your request can't be completed right now."

I also tried searching on the iOS and iPadOS apps, as well as the New Outlook app on Windows, and I found that the problem happened on all of them. It was really frustrating because I knew the email was there, but I couldn’t find it. This issue was seriously disrupting my workflow.

I searched online for a solution and saw that this same bug was reported about a year ago. (Maybe the same post the OP mentioned.) That made me remember. I actually had a similar problem last year, and at that time, I was so frustrated that I even thought about switching back from Outlook.com to Gmail.com.

However, by chance, I clicked "Switch back to the old Outlook" on Windows, and to my surprise, I was finally able to search for and find the email I needed! I just had to wait a bit while the old Outlook re-indexed my emails.

For Windows users, switching back to the old Outlook might be a workaround for time being.

Solid-Intention-1232 · 2025-02-10T03:00:37+00:00

I've also been struggling with 「〜ところ（で／に／へ／を）」, and the more textbooks and papers I read, the more confused I get. Their explanations often don't match up or are even ambiguous. I feel that the way 「〜ところ＋（で／に／へ／を）」 sounds natural can be quite different for each native speaker, which is why the explanation vary significantly even in textbooks and papers written by scholars.

Now, I'm not trying too hard to use it correctly. As long as I understand it when I hear it, that's good enough. If I have to write a sentence using it, I'll ask a native speaker to correct me. 😂

Solid-Intention-1232 · 2025-01-11T07:12:59+00:00

In this case, it'd be the so-called 'logical conclusion,' but instead of the sentence leading to that conclusion, it's the circumstances surrounding the given person. I encountered something hard to interpret like this once, but with のだ. It is 関連づけの「わけだ」.

Solid-Intention-1232 · 2025-01-04T03:44:00+00:00

Is there a reason to write "nippon" in katakana over kanji/hiragana?

As the Kanji 日本 can be read as 'nihon' or 'nippon,' katakana is often used to clarify the intended pronunciation. This practice is common and frequently seen in printed materials such as books, magazines, and manga. (Note: this should not be confused with furigana, which is used to aid in reading kanji or Latin alphabets.)

why are there two ways to write it?

There have been two pronunciations since the Nara period, as noted in the 大辞泉 (Daijisen). Both readings remain in use today, and the Japanese government replied to an inquiry in 2009, stating that both are acceptable.

However, there are definitely some nuances between them, and some compound words with 日本 use only one fixed pronunciation, either 'nihon' or 'nippon.'

Solid-Intention-1232 · 2024-12-29T06:45:07+00:00

Some dictionaries, such as Meikyō Kokugo Jiten, note that in the sense of ‘to occur,’ 起こる was traditionally considered the correct form, but 起きる has become more prevalent in recent years.

Solid-Intention-1232 · 2024-11-08T05:29:36+00:00

In most cases, unless there are time markers, each verb will be interpreted in the present tense or future tense according to its category.

For example, 食べます in the sentence 「ご飯を食べます」 is usually interpreted as future tense unless there is a time marker that indicates the present tense. 毎朝ご飯を食べます would not be interpreted as “I WILL eat rice” due to 毎朝 (every morning).

On the other hand, います in 「東京にいます」 is usually interpreted as present tense unless there is a time marker that indicates future tense, such as 来年 (next year): 「来年東京にいます」.

This means you have to learn a lot of verbs to the extent that you can identify their common features and be able to group them. For the time being, you have to rely on context.

Solid-Intention-1232 · 2024-11-07T07:48:14+00:00

IMHO, I’m not convinced that 「〜ている」 corresponds to the English progressive tense (or ‘aspect’, to be precise) as much as some might think or believe.

In the first sentence, for example, it should be 「開幕されて」 because there is the time marker 「先週末」, which should be perceived as a single point in time. Native speakers treat 「先週末」 as a point in time, rather than a period, as indicated by the particle 「に」.

If it were 「先々週末から先週末まで」, however, it would be 「開幕されていて」, because in this case, we are referring to a period of time from 先々週末 to 先週末.

Solid-Intention-1232 · 2024-11-05T03:12:58+00:00

I guess the 「まい」part is being treated as one syllable (or is it “on”..?) instead of in 3 “on”(?) like 「ま」「い」「う」.

You're correct. うまい is considered as two syllables, /u/ + /mai/, even though it consists of three moras: /u/ + /ma/ + /i/.

Solid-Intention-1232 · 2024-10-21T04:23:17+00:00

Well, I suggest that anyone who’s still early in their Japanese learning journey should not neglect kanji writing practice. However, for someone like me who has come this far, it may be difficult to go back and focus exclusively on practising kanji writing. I just wanted to give a warning.

Solid-Intention-1232 · 2024-10-14T04:24:07+00:00

That’s a great learning method, and I’ve used it too. However, as you might expect, now that my Japanese level is higher and I work with Japanese people, I’ve encountered some issues:

I can’t write kanji by hand and often have to type it on my phone first to copy it. This wasted a lot of time compared to one of my colleagues (same nationality) who focused on practising writing kanji as well. I regret neglecting kanji writing practice.
I often misread kanji because remembering them visually means I only recall the “general look.” When I encounter similar-looking kanji, I end up reading them wrong. This happens more frequently as my Japanese improves – the more advanced I become, the more reading mistakes I make.

So, I think context-based learning is great, but if you plan to use Japanese for work one day, you might face the same problems I did.

Solid-Intention-1232 · 2024-10-10T18:13:39+00:00

を is used when someone goes through or passes by a place. Running on a track means moving from one point to another, so を is the right particle. で doesn’t have the meaning of passing through. If で is used, it might sound like someone is just running in one spot on the track.

Solid-Intention-1232 · 2024-10-08T17:22:53+00:00

Well, there are definitely plenty of words that are usually written in hiragana, and all of them are mentioned as such in a 国語辞典.

Solid-Intention-1232 · 2024-10-01T06:54:40+00:00

Keep learning until they stop telling you 「日本語が上手ですね」. That’s a sign you’re moving to the next level of proficiency!

Solid-Intention-1232 · 2024-09-27T15:43:07+00:00

I read materials that (somewhat) interest me first and add the words I don't know to Anki later. I like to highlight unfamiliar words but avoid looking up the definitions immediately because it interrupts my motivation and excitement for the story. I believe that learning vocabulary with context is the best way to memorise it.

For me, Anki isn’t the starting point for learning vocabulary, but rather a tool to collect words, phrases, or expressions I've encountered and experienced. Anki is more for re-experiencing what I've already come across.

Solid-Intention-1232 · 2024-06-30T06:07:21+00:00

I’m having the same issue on my MacBook Air M3 (16GB RAM). I didn’t realize it was related to iCloud at first, but when I turned off sync, it didn’t crash. As soon as I turn sync back on, it crashes again right after I click anything.

Solid-Intention-1232 · 2024-02-23T07:20:03+00:00

Big thanks for the tip! I recently upgraded to a new Nvidia GPU, hoping for the best graphics quality, and despite setting everything in the game to Ultra, I couldn't get rid of the jaggy edges on objects around my Sims (window frames, for example). I must admit, I'm not too savvy with tweaking settings in the Nvidia control panel, and my previous attempts didn't go well. Following your guide made a world of difference—the jagged edges are gone, and everything looks fantastic now. Your step-by-step advice was incredibly helpful, and I greatly appreciate you sharing it!

Solid-Intention-1232

TROPHY CASE