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 only ever get around half a syllable of each word to actually play.
It’s not too bad how it is now, but it was nice how it was before because the sound helps solidify the reading in my brain a bit and it’s a bit jarring audio-wise to have it constantly cut out (unless I disable the option entirely). So I don’t know if this is due to a code change or what, but if it was, I’d put my vote in for the old functionality.
Just noticed the same. I also like to hit enter to continue while the word still sounds out. Wonder if this is related to the recreation of the pages in React, a browser update (I use Chrome) or just a fluke. With others experiencing the same, I’d say the fluke is out.
I’m having the same issue though I stopped hearing readings entirely. Except for some reason the very last word in my reviews was pronounced again. After reading what you two have said I’m guessing it’s because I use the lightning mode script which instantly goes to the next word, cutting it off before it starts, except on the very last item in the review.
I was switching between headphones and speakers for a bit before and thought I had just messed something up somehow but looks like I’m not the only one.
I’m having the same issue. Hearing the cut off bits of syllables is very distracting, not to mention the lack of reinforcement that hearing the whole words provided. I hope they fix it soon. (using Chrome by the way)
Just noticed this today. Perhaps it has something to do with user scripts? I’m only running the ultimate timeline reorder and ignore scripts, anyone else?
We have identified the problem and have a fix ready to deploy. But the fix is somewhat of a significant change. And given that it is Friday… (we don’t want to introduce new bugs on a weekend)…
The plan is the following:
Revert the last audio bug fix released the other day. The audio cut off bug should go away.
Next week we’ll reapply the reverted bug fix and introduce the audio cut off bug fix
The reverting of the last audio bug fix will happen in the next hour.
And I think this is a smart decision to go about it this way. This way we can enjoy the audio over the weekend without hiccups and the WK team need not go bug hunting over the weekend.
Thank you for letting us know!
now onwards to reviews. with sound of course!
