overture2112 Wrote:It isn't that I answer the cards too fast. For example, I answer a card, then the plugin starts playing the Unreal track, and before it ends, it stops and the next cards audio plays instead. It seems that Anki isn't waiting for your plugin to do its work before playing the card's audio, so if the Unreal track is relatively long and the next card has its own audio, Anki just "crops" the Unreal track and goes to the next audio.Sebastian Wrote:There is a tiny bug though, where sometimes Anki stops playing the "Unreal" sounds before the audio ends, to play next card's sound instead. No big deal and it only happens sometimes, but since your plugin has proven effective for my, I actually miss listening the full track when I'm in a Killing Spree. =)You must review much faster than I do
I'll dig to see if there's an easy fix, but I *think* Anki has more of a fire-and-forget policy with the way it utilizes mplayer.
overture2112 Wrote:I was curious if anyone had suggestions on things to add, particularly for the following sounds (some suggestions by me or others provided):I agree that the sounds shouldn't be too repetitive, since it would make people start perceiving them just as "noise", and the plugin would lose its charm.
Headshot
* eg, answering new card correctly? might be too common/irritating for those who don't spread out new cards or only add to Anki after learning thoroughly
Anyway, getting a "Headshot" once in a while would be nice. It could be left, for example, for when you answer 4 within the first seconds or something like that.
Quote:Double Kill (and Triple / Multi)It sounds similar to what I said before for the "Headshot", and they could work together (Headshot => Double Kill => Triple Kill...). It could get a bit too repetitive, though.
* eg, answering correctly in < N seconds since last answer
Quote:30 Seconds Left (and One Minute Remains)I would like that a lot. Of course, it would be necessary to be careful so that the audio from the plugin from multimedia decks don't create any conflict.
* eg, before your session is about to max out it's timebox duration
Quote:Humiliating DefeatI liked the last one the most.
* eg, failed mature card, failed N in a row, less than X% accuracy at session end?
Quote:Bottom FeederI think punishing people for pressing the "Hard" button would go against the way some people use Anki. For example, I tend to press "Hard" a lot because I like not letting so much time before some cards appear again.
* eg, marking more than N in a row as "hard"?
Ideally, it would be great if the plugin had some GUI where you could assign sounds manually for all the events. It also would be very handy having a "Mute" button in Anki's toolbar, for when you're in a situation where you don't want the rest of the world to listen to the sounds (specially the female version).
BTW, since some events could be triggered only when people use Anki's timeboxing options, it would be great if the plugin recognized when people are using time limits or not. So that, for example, if you set a time limit, then you would have an "Humiliating defeat" if you have less than X% of correct reviews in that time, but if you just review without time limits, you would have the "Humiliating defeat" when failing more than X cards in a row.
Sorry if I ask for too much.


Regrettably, I decided to remove it as I personally found it too distracting.