-
-
Notifications
You must be signed in to change notification settings - Fork 234
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
Enhancement: Allow different audio messages formats than aac for embedded play in other apps #73
Labels
stale
The item is going to be closed soon because of inactivity
Comments
Closed
Closed
This issue is stale because it has been open for 120 days with no activity. |
github-actions
bot
added
the
stale
The item is going to be closed soon because of inactivity
label
Mar 7, 2024
This issue was closed because it has been inactive for 14 days since being marked as stale. |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
I use a lot of bridges on my matrix instance (Telegram, Whatsapp, Signal). Audio messages sent in .aac cannot be played inside Telegram directly. You have to download them and it opens them in an external player. Opus/Ogg audio files on the other end, can be played directly (IIRC, it's also possible with mp3 files). When files are sent in this format, you see a little play button and a seek bar, and can play files directly in the application, giving an experience similar as if you received a voice message sent from another Telegram client.
Possible enhancement
Would it be possible to change the audio codec/format used by fluffychat when sending audio messages ? I don't know what motivated the choice of aac, but I guess there are a few reasons. So making it a configurable option and allowing users to change from aac to something else would satisfy more people than just switching from aac to Opus/Ogg.
The text was updated successfully, but these errors were encountered: