-
-
Notifications
You must be signed in to change notification settings - Fork 54
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
Audio GLITCHES #571
Comments
first let me say that google play is no longer the main distrubution channel for this app. |
which tox client is the receiver side using? and are you calling audio only or also video? |
both smartphones are exactly as described above, and both see the glitches. |
did you change it in the source code and compiled yourself to fix it, or what do you mean by "Some years ago I solved a similar problem" ? TRIfA uses native code for audio recording and playback via OpenSLES |
it was my own app, but the effect was exactly the same |
audio mode is tricky stuff on android. i ran into lots of issues depending on the device. i can let CI build a debug version with COMMUNICATION_MODE, could you test that version? |
I can repeat the tests tomorrow and upload the file(s) with the glitches, but sorry, I cannot do much more than that. |
can you install and test with the nightly version? it can be installed alongside the regular trifa |
you mean with the new experimental feature? Sure, I can do that. |
https://github.com/zoff99/ToxAndroidRefImpl/releases/download/nightly/TRIfA-nightly.apk it has also turned logging on. |
unfortunately the same behavior |
Describe the bug
The audio signal shows many glitches
To Reproduce
Record audio on receiver side (e.g. connecting speaker in USB sound card to mic in a PC running Audacity)
Expected behavior
The audio signal has no glitches
Your system information:
Add screenshots, if possible
Additional context
The output volume seems to be very low!
I tried several different combinations of settings without success (audio buffer, frame size, sampling rate, UDP active, force UDP mode).
Some years ago I solved a similar problem by opening the audio interface with CALL_MODE instead of COMMUNICATION_MODE
The text was updated successfully, but these errors were encountered: