Thanks, added to our list.
2 Likes
You are a good overlord
2 Likes
For 左腕, Kenichi’s right and for 右腕, probably Kyoko, but I’ll have to double check.
2 Likes
Maybe I’m wrong, but Kyoko sounds to me shi(L)na(H) and Kenichi - shi(H)na(L)
https://www.wanikani.com/vocabulary/品
@JenK Just checking you’re aware of this one too Inconsistent audio for 元
1 Like
Sounds correct to me. Both are 平板 or “flat” intonation.
1 Like
Both sound correct to me too (heiban).
1 Like
Thanks, added!
2 Likes
Thanks for all your contributions! Here’s the updated list (includes both mispronunciations and tonal differences):
取り逃がす
鼓
延期する
兵糧
丘陵
毎月
幼年時代
報道
警視庁
遅咲き
牛肉
左腕
報じる
第一印象
還元
成程
舞踏会
5 Likes
I have this problem every time an audio plays for the first time on a page… the first second or so of the audio is cut off. I am also using a bluetooth speaker, as others have mentioned that might be the cause.
You can always hit J on your keyboard to re-hear the spoken audio during reviews, or click the play button during a lesson. Whenever I replay the audio it is not cut off, but yeah, it’s a shame with this problem happening, I will have to do some testing but I bet it is having to do with Bluetooth.
1 Like
I was doing lessons and the audio for this word didn’t match with the vocab reading
Audio(kyoko): shikisai (or something like that)
Don’t know if the same happens for reviews
2 Likes
On the subject page, it looks like our audio is correct: WaniKani / Vocabulary / 遅咲き
Hmm, did you have 色彩 come up in the same batch of lessons, maybe right before or after 遅咲き？ It looks like they’re both in the same level so I’m wondering if there was some sort of lag.
1 Like
Probably, I didn’t take a screenshot of that part 
I changed backwards and forwards a few times to check and the audio didn’t match each time, if it’s ok in the page then maybe it was a temporary lag~
Thanks for taking the time to check! 
2 Likes
Shoot us an email next time you’re seeing the same issue! Also did you have multiple WK tabs open when you were doing the lesson?
2 Likes
Shouldn’t this issue be fixed now that jStorage is located in sessionStorage rather than localStorage?
2 Likes
I wasn’t sure if @cicada experienced this before or after we pushed the update on Tuesday. But yes we shouldn’t have these type of issues anymore!
4 Likes
Ok, to be honest I can’t remember 
I’ll pay more attention to those details if I encounter something again~
I experienced that issue on the same day I posted it
2 Likes
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.