Audio track not playing for some vocabulary

[killergerbah]

Is anyone else experiencing this?
It happens quite often for me, maybe over half the readings.
Does the client need time to buffer the audio now or something? (Just guessing because I’m on slow ass DSL).

[Rowena]

Do you have the Lightning Mode script installed? It has been shown to be causing problems (it doesn’t appear to be supported anymore).

[UInt2048]

There’s some related issues here:

1000×1000 11.8 KB

I don’t know if this is just my browser or what, but it used to be that when doing vocab, the voiceover would sound out the whole word even after you hit enter to the next word, unless you typed the next word fast enough that you triggered the next word’s speech while the first was going on. But as of today, immediately after hitting enter to go to the next review item, any playing vocab sound will cut off. So unless I specifically slow down my reviews and let the clip play before moving on, I …

Edit: In the above thread, Viet has stated the fixes have been reverted:

@viet

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.

[Jirachi]

@UInt2048 The team has already resolved the issue in the thread you linked to.

However, it’s not too uncommon for some audio to take a long time to load.
Try disabling usersripts, if you’re using any. Like @Rowena said, Lightning Mode and quite a few others are no longer supported.

[UInt2048]

@Jirachi

The team has already resolved the issue in the thread you linked to.

People seem to still be having issues there, so I linked it.

[Jirachi]

Huh, interesting. They did say they were going to implement something new in audio, maybe that’s messing things up now

[killergerbah]

I don’t have lighting mode, just stroke order and fonts enabled. I’ll try disabling some to see if that helps.

[Jirachi]

Wanikani is going into maintenance mode soon…maybe that will fix the problem

[killergerbah]

It looks like some deploy was reverted, and the problem is now fixed.

[UInt2048]

Yes - reverted in the thread linked. Hopefully they figure it all out!