Some testing
Since the message isn’t there I’m guessing mpv
is installed.
To diagnose whether mpv
supports adding a pause between audio playbacks at all, I ran the following in the terminal (on debian linux):
mpv --audio-wait-open=1 ./A.mp3 ./B.mp3
Result? Audio is played just fine, just without the desired pause.
I couldn’t really find anything on the internet regarding possible reasons and fixes and thus asked an ai chat bot. Its answer might be inaccurate but it does seem to make sense to me. The AIs answer:
As of the latest versions of mpv, the option
--audio-wait-open
is primarily used to control how long to wait for an audio stream to become available before starting playback. It doesn’t create an intentional pause between tracks in the same way you might be expecting.
[…]
While you noted reports from users aboutaudio-wait-open
, it’s primarily utilized in scenarios where there’s buffering involved rather than controlling playback timing between multiple files.
Also: The manual (mpv.io) says this:
If this option is given, the player will wait for the given amount of seconds after opening the audio device before sending actual audio data to it. Useful if your expensive hardware discards the first 1 or 2 seconds of audio data sent to it.
So in short: Apparently it worked for the other users because their hardware just happend to behave this way.
Workaround
- You can open some audio creating tool (like
audacity
), - create one minute of silence,
- save the file,
- include it in your fields.
Not ideal but the best thing I can come up with right now.
(and maybe js can be used to automate this in your template)
Edit: I just remembered I helped a user a while ago to set up a “ding” sound. You can look through the code and discussion and modify the code to create an automated one second pause: Conditional Audio Playback - #5 by Anon_0000.