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
In other words, if you have the bot in a voice channel, and have it record to a basic AudioSink (Let's say an FFMPEG sink), it will only have written 45-50 minutes of audio to the file when the hour is up.
When I use a very barebones AudioSink, that purely does a print when its write(...) method is called, it is still unable to keep up with the data coming in. I have debugged that the AudioReader.callback(...) method would be called fast enough, given that I replace all code within it with a print statement.
This means that (I think) there is some major inefficiency in this extension. Could it be the locks that you are using? If you are aware of any issues with this, could you point me in the right direction on how to fix it so I could maybe work on a PR?
Thanks again for your work.
The text was updated successfully, but these errors were encountered:
Thanks to all the contributors of this project for the work you have done on it. I have been enjoying this extension so far.
I have ran into an issue when trying to use audio sinks. Even for the basic example at https://github.com/imayhaveborkedit/discord-ext-voice-recv/blob/main/examples/recv.py, I am running into the issue that
AudioSink.write(...)
is just not called fast enough for it to keep up with all the data coming in.In other words, if you have the bot in a voice channel, and have it record to a basic
AudioSink
(Let's say an FFMPEG sink), it will only have written 45-50 minutes of audio to the file when the hour is up.When I use a very barebones
AudioSink
, that purely does a print when itswrite(...)
method is called, it is still unable to keep up with the data coming in. I have debugged that theAudioReader.callback(...)
method would be called fast enough, given that I replace all code within it with a print statement.This means that (I think) there is some major inefficiency in this extension. Could it be the locks that you are using? If you are aware of any issues with this, could you point me in the right direction on how to fix it so I could maybe work on a PR?
Thanks again for your work.
The text was updated successfully, but these errors were encountered: