I and a couple others have found that when on Linux (has not been tested on mac, or windows yet so I can't say for sure). It seems that after a couple seconds of not playing any audio, playing an audio file will cut off the first half-second or so of audio as some sort of "start-up" or "warm-up". This is especially annoying when the sound is bound to the "VimEnter" auto command.
There seem to be a couple solutions as of now:
- Create a system service that always plays silence (idk how people might feel about this)
- Create a sub process when Neovim starts that plays silence (still probably wouldn't let sounds bound to the "VimEnter" auto command play in their entirety without some more finagling)
- Or setting up Professional audio stuff for your Linux machine (idk much about this, and it sounds like too much work for a novelty plugin)
The Neovim sub process seems like the best idea to me, and if someone really wants that "VimEnter" sound, they could figure out how to get that to work with their system with some pointers from the README. Of course, the sub process will be entirely optional, but I will look more into the issue to find the culprit because it may be because of my using CLI audio players.
I and a couple others have found that when on Linux (has not been tested on mac, or windows yet so I can't say for sure). It seems that after a couple seconds of not playing any audio, playing an audio file will cut off the first half-second or so of audio as some sort of "start-up" or "warm-up". This is especially annoying when the sound is bound to the "VimEnter" auto command.
There seem to be a couple solutions as of now:
The Neovim sub process seems like the best idea to me, and if someone really wants that "VimEnter" sound, they could figure out how to get that to work with their system with some pointers from the README. Of course, the sub process will be entirely optional, but I will look more into the issue to find the culprit because it may be because of my using CLI audio players.