Sorry, it’s right there in your last line…
To be fair, I edited my post to add that in, so it’s possible that if you replied immediately after I first hit post, you may not have seen it.
Update: In my most recent review sessions the sound played correctly 15/15 times. But it did definitely fail a couple times earlier (I recall it happening for 地蔵 and 酸素 in case that helps).
Update: This morning, the sound failed to play twice out of 64 vocab (on 込める、渋い). Strangely, both of those came near the beginning of the review session. I wonder if perhaps the sounds weren’t loaded yet or something.
As before, I’m using Chrome on ChromeOS with no userscripts. I have an adblock extension, but it’s disabled on Wanikani.
Update: In my most recent review session, the sound failed to play for 2/32 vocab (血液型、添える). However, the later case occurred towards the end of the session, so I think beginning vs end of the review session might be a red herring.
Update: Happened 2/22 times in latest session (片手、水仙).
Update: 3/37. I guess that disproves the “it always happens exactly twice per review session theory”. I stopped recording the individual words it happened for, since there doesn’t seem to be any pattern.
Just noticed the problem today, in my case it’s the lightning review script. Is there some other similar script that doesn’t have the same issue?
I just had a look in the Lightning Mode thread and found this:
Yup, I did that and it fixed everything, that one replaces both Lightning Mode and Override. Thanks!
For anyone else reading this, the link to install:
This bug is especially bad this morning. Almost all the vocab audio is failing to play. I hope they fix this soon.
Update: It failed a couple times before I started counting, but after I started counting this morning, it failed 5/70 times, which is still much higher than before.
Sorry for the slow reply. No, I would only occasionally hear sound, probably about 1 in 10 times. The problem is continuing.
I use MacOS Catalina 10.15.5. My browser is Safari 13.1.1. I don’t use scripts.
We are planning to revert both audio fixes today. Still trying to figure out what the root issue is with it, but it appears it has been disrupting people’s audio and access to lessons.
Great! Thanks for being so responsive and helpful to us users!
The sound is working great today! Thanks again!
today I installed the confusion guesser script and the visual similar kanji script. Since then the audio does not play anymore. Neither during the reviews nor on the self study script. I have to enter each vocabulary individually and hit the audio button.
Anyone any idea why that is and what I can do about it?
Thought I’m gonna write first here before starting a new thread
Have you tried uninstalling those scripts?
not yet… I was hoping that maybe there is another solution… since I would really like to use them
but if nothing works I will do that
My ConfusionGuesser script is only executed on the review screen, so I don’t think it is possible that it interferes with the Self-Study Quiz script, which as far as I know executes on the dashboard. But I also wasn’t able to reproduce the problem when trying out the Niai Visually Similar Kanji script. Does it still happen for you, or has it fixed itself in the meantime?
So at the moment it works during reviews, and on the Item inspector.
During lessons and the quizzes it is still not working. Which is quite weird.
I didn’t do anything beside turning off my computer and turning it back on now…
That does sound like a bug, but just to be sure, also check in the WaniKani settings if Autoplay audio in lessons is active. And in the Self-Study Quiz if the speaker-icon in the top left is yellow. And also make sure that you haven’t muted the browser tab (right click on the tab and see if you can unmute).
The next steps could be to disable your userscript manager (Tampermonkey,…) and test if it changes anything in the lessons, or disable all scripts except for Open Framework and Self-Study Quiz and see if the problem in the quiz is fixed. And/or, after the problem occurs, open the console of your webbrowser (F12 or Ctrl+Shift+I and go to “Console”) and look for error messages (and maybe post a screenshot of it here).