max/audio_splitter
1
1
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[BUG]: Frontend can't apply codecs filters correctly #26

New Issue
Closed
opened 2026-09-02 13:58:07 +04:00 by max · 1 comment
max commented 2026-09-02 13:58:07 +04:00
Owner
Copy Link
Copy Source

📋 Description

When a certain container selected unsupported codecs in 'codecs' dropdown menu must be disabled (grayed out), but they are available

🔁 Steps to Reproduce

  1. Upload a file
  2. Select "OGG" container
  3. Check audio codec dropdown menu

✅ Expected Behavior

Shows: Copy, opus, vorbis, flac
Filters based on container compatibility

❌ Actual Behavior

Shows all codecs

📄 Logs / Screenshots

No response

📦 Audio Splitter Version

commit 25e8c0293e

💻 Operating System

Debian 13

🌍 Browser (if applicable)

Firefox

📎 Additional Context

No response

✅ Submission Checklist

  • I have searched for existing issues (open and closed) that report the same problem
  • I am using the latest stable release of Audio Splitter
  • I have provided clear steps to reproduce the issue
  • I have included relevant logs or error messages (with sensitive info removed)
### 📋 Description When a certain container selected unsupported codecs in 'codecs' dropdown menu must be disabled (grayed out), but they are available ### 🔁 Steps to Reproduce 1. Upload a file 2. Select "OGG" container 3. Check audio codec dropdown menu ### ✅ Expected Behavior Shows: Copy, opus, vorbis, flac Filters based on container compatibility ### ❌ Actual Behavior Shows all codecs ### 📄 Logs / Screenshots _No response_ ### 📦 Audio Splitter Version commit 25e8c0293e4b8bc52984c6c6a1711f98594603d9 ### 💻 Operating System Debian 13 ### 🌍 Browser (if applicable) Firefox ### 📎 Additional Context _No response_ ### ✅ Submission Checklist - [x] I have searched for existing issues (open and closed) that report the same problem - [x] I am using the latest stable release of Audio Splitter - [x] I have provided clear steps to reproduce the issue - [ ] I have included relevant logs or error messages (with sensitive info removed)
max added the bug label 2026-09-02 13:58:07 +04:00
max added the frontend label 2026-09-02 15:51:01 +04:00
max commented 2026-09-02 19:16:40 +04:00
Author
Owner
Copy Link
Copy Source

The same behavior with the other containers, they don't follow the rules defined in constants.py

The same behavior with the other containers, they don't follow the rules defined in constants.py
max closed this issue 2026-09-02 20:24:28 +04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
backend
Issues related to the backend
 bug
Something is not working
 core
Issues related to the core
 deploy
duplicate
This issue or pull request already exists
 enhancement
New feature
 frontend
Issues related to the frontend
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 refactoring
Some parts of the codebase are hard to read and maintain
 wontfix
This won't be fixed
No Label bug frontend
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
max
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: max/audio_splitter#26
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?