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 been trying to get my bluetooth earbuds working without a bluetooth card for a while now. After some testing, I found specific apps which don't cause transcoding (Youtube, some games, etc) and some that do (This app, some games, music players)
The latency I roughly tested with a youtube video has pretty much no delay but using this app has a is really noticeable delay which I'm roughly estimating at 100ms+. I don't know how to test this more precisely, but its 100% noticable
Is there some possible way to have this be avoided in some way? Like maybe handing transcoding to AAC within the app? Using AAC alone seems to stop all transcoding nonsense and give decent results
The text was updated successfully, but these errors were encountered:
Can you describe the "transcoding"? The app consumes uncompressed PCM and so there is no decoding on the app end. PulseAudio and the Windows server should simply be sending uncompressed PCM from the raw source and so there is no encoding on that end.
The delay is probably most likely due to inefficiences in the app buffering up large amounts of uncompressed data to send to Android for rendering. To test this, you can try lowering the bitrate of the PCM data.
If anything, my guess is that it's better to try and let Android handle the decoding.
But implementing an additional code in the app is not in the future plans.
I've been trying to get my bluetooth earbuds working without a bluetooth card for a while now. After some testing, I found specific apps which don't cause transcoding (Youtube, some games, etc) and some that do (This app, some games, music players)
The latency I roughly tested with a youtube video has pretty much no delay but using this app has a is really noticeable delay which I'm roughly estimating at 100ms+. I don't know how to test this more precisely, but its 100% noticable
Is there some possible way to have this be avoided in some way? Like maybe handing transcoding to AAC within the app? Using AAC alone seems to stop all transcoding nonsense and give decent results
The text was updated successfully, but these errors were encountered: