Troubleshooting
This page tries to provide some resources for troubleshooting GSM when it is not working properly. I will put this in a bit of an FAQ style.
GSM is not aware of the path that OBS is saving files to. These both need to be the same in order for GSM to pick up the replay.
This is actually how it used to be in the first iteration of GSM. All you will need to do is save the replay buffer in OBS, and GSM will kick it's processing off and update the latest card in Anki. You can configure hotkey in OBS's settings.
The Audio Trimming Logic has not been touched for months, and I don't plan on making changes anytime soon. With that being said, here are some issues you may face.
It's likely that GSM is not receiving Texthook/Clipboard Events from your texthooking software. Double check these settings in GSM and your texthooker to make sure they line up.
There isn't really much I can do about this. It's likely due to a poorly timed hook. What you can do however is set a negative beginning offset in GSM's Audio Settings. Note that End Offset also exists.
This could also be due to using a feature like Agent's "Translate", which creates a 2nd text event, and breaks the timing.
My script simply takes what is displayed in the OBS replay buffer at a certain point in time, so look through the OBS settings in order to attempt to fix any issues you have with screenshots.
This is something I can't fix, since OBS doesn't have a way to externally close gracefully. I prefer this due to pure convenience. Try closing OBS before GSM if you find that your changes in OBS aren't sticking.
There is an option to only work on Anki Cards that have a certain tag, this, in collaboration with Profiles in Yomitan can help alleviate this. I won't explain here, but I'm sure you can find some resources on how to setup profiles in Yomitan.