New feature or a new settings

[atikuz1]

Is your feature request related to a problem or new idea? Please describe.
Currently, the app only supports downloading songs at 128Kbps, and there is no option to choose higher qualities like 192Kbps, 256Kbps, or 320Kbps like soundbound app, these app preffered High Audio quality. Another missing feature is the ability to favorite a song directly from the notification panel while playing. Right now, users have to open the app to mark a song as favorite, which is inconvenient.

This image is from soundbound app.

This also.....

Describe the solution you’d like

1. Add multiple audio quality options (128Kbps, 192Kbps, 256Kbps, 320Kbps).

2. Introduce a setting where users can select their preferred default quality. Once selected, all future downloads should automatically be in that quality without needing manual selection each time.

3. Favorite Button in Notification Panel: Add a favorite (♥) button in the media playback notification.This will allow users to mark a song as favorite without opening the app, making it more user-friendly.

Additional context
This feature would improve user experience and give more flexibility to those who prefer higher-quality audio. It would also prevent frustration from having to manually choose the quality every time.

[blacklizzt]

when it comes to quality, the app use either m4a or opus, not sure which one is default for streaming, but if you download using .opus it downloads to 120-ish, for a context 128kbps opus is transparent or equal to that of 320 mp3, because opus compression is so much better

lowest setting might be somewhere on 66kbps, the other project like this, namely InnerTune or SimpMusic allows for higher bitrate for account with youtube premium, but most doesnt include the exact numbers for options, it just says low, high, and Max (on Metrolist, dunno what does that mean), i think this is the same with Youtube Music app.
Implementing higher quality option beyond 128 means requires loging to youtube account.

favorite button already requested on issue #317 , i also hope they implement this also in the future