-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix opus silence potential to generate huge files #2250
Conversation
Looking deeper at this I think I can improve by checking next rather than passing the count, but I'd be interested in opinion / downsides of the general approach. |
I think it's already helpful to avoid those issues. Not sure about the impact on recordings, as sometimes they're caused by timestamp resets at unfortunate places and may mean some missing audio packets when the additional command line flags are not used, but it should be very few of them anyway. This looks fine to me already, but if you think this can be improved before we merge please do let me know. |
Updated to use |
I have tested across audio recordings that are fine and also 3 with issues. It definitely resolves the issue of massive files which can impact the server / service quite badly and that I think is key (at least for me). In all the results the audio was fine and playable. In one case of the 3 with issues it reported an issue with |
Thanks! I'll have to double check how this behaves with "normal" losses to compensate with silence, since they'd be much more frequent than GB files and we don't want to break those. |
Seems to be working as the current |
This may not be the most optimal way to address the issue and I may be missing something. But this seems to work and resolve all the issues I have encountered where huge (example: 28gb) opus files can be generated.