You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've observed an unexpected behavior when using the config file mushra_noloop_nowav.yaml. I would expect that the audio is played once (because enableLooping is set to false) and after the playback finished, the progress bar should be reset to position zero.
However, what I observed instead was that the audio was played once, but then it continued to play a few more audio samples from the beginning of the audio (as also shown by the progress bar). For audio files that don't have silence at the beginning, this results in strange sounds at the end of the playback.
Screenshot from the page after the audio was played (tried with Firefox and Google Chrome):
Hi @judithK10 I am unable to reproduce at this point but even worse I see that mushra_noloop_nowav loops all the time when running on Brave for me. So this is def a bug.
Hi,
I've observed an unexpected behavior when using the config file
mushra_noloop_nowav.yaml
. I would expect that the audio is played once (becauseenableLooping
is set tofalse
) and after the playback finished, the progress bar should be reset to position zero.However, what I observed instead was that the audio was played once, but then it continued to play a few more audio samples from the beginning of the audio (as also shown by the progress bar). For audio files that don't have silence at the beginning, this results in strange sounds at the end of the playback.
Screenshot from the page after the audio was played (tried with Firefox and Google Chrome):
I noticed that the progressbar is correctly reset to zero when I add a
break
after this line: https://github.com/audiolabs/webMUSHRA/blob/master/lib/webmushra/audio/MushraAudioControl.js#L286Was this issue observed before, or is there anything that could be wrong with my setup? And could the additional
break
be a reasonable solution?The text was updated successfully, but these errors were encountered: