Thank you for your report, and I sincerely apologize for the audio download issue, especially when downloading audio from YouTube videos with multiple audio tracks.

It appears that this issue was introduced in a recent version. I’m currently investigating the cause and working on a proper fix. In the meantime, I recommend using version 2.3.3, which should provide a more stable experience for YouTube audio downloads.

If you continue to experience problems with version 2.3.3, I’d really appreciate it if you could open an issue on GitHub and include the affected YouTube URL, your browser, and your device details. This information would help me investigate the issue further.

Thank you for your patience and understanding!

Thank you for your review! I'm glad you're enjoying the extension.

I believe I understand the UI performance issue you mentioned. I've already made several optimizations to make the UI lighter and smoother, which are currently available in the v2.3.1 beta pre-release on GitHub.

If you'd like, you can try the beta and let me know if it improves the experience. If the UI still feels laggy or resource-heavy, I'd really appreciate it if you could create an issue on GitHub with some details about your browser, device, and where you notice the lag. That would help me investigate and optimize it further.

Thank you for your review. I believe I understand the issue you experienced, and I've already made changes that should address it in the next update based on my understanding of your report.

If this isn't the same issue, I'd appreciate it if you could create an issue on GitHub with more details (browser, website, and steps to reproduce). That would help me investigate and fix the problem more accurately.

Thank you for your review and for your feedback. I believe I understand the issue you experienced with videos that contain multiple audio tracks. Support for detecting and selecting multiple audio tracks has already been added and will be available in the next update.

If this isn't the same issue, I'd appreciate it if you could create an issue on GitHub with more details (browser, website, and steps to reproduce). That would help me investigate and fix the problem more accurately.