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

[FEATURE]: Multicore processing #38

New Issue
Open
opened 2026-09-15 19:12:40 +04:00 by max · 0 comments
max commented 2026-09-15 19:12:40 +04:00
Owner
Copy Link
Copy Source

🎯 Problem Statement

Currently, only one CPU core is used for processing. It's slow, almost all modern systems have at least two cores. It might be a good idea to implement multicore processing

💡 Proposed Solution

Process tracks on more than one core if user wants it. Single core will remain the default, but user should have an option to choose more cores

🔄 Alternatives Considered

No response

👤 Use Case / Persona

Any user

📸 Screenshots

No response

⚙️ Technical Approach

No response

✅ Acceptance Criteria

  • Core supports more that core
  • We have a CLI flag
  • We have an option for backend
  • We have an input field in frontend

🤝 Are you willing to contribute this feature?

Yes, I can contribute

✅ Submission Checklist

  • I have searched for existing issues (open and closed) that request the same feature
  • I have explained the problem this feature solves
  • I have described a concrete solution or direction
  • I have considered alternatives and explained why they fall short
### 🎯 Problem Statement Currently, only one CPU core is used for processing. It's slow, almost all modern systems have at least two cores. It might be a good idea to implement multicore processing ### 💡 Proposed Solution Process tracks on more than one core if user wants it. Single core will remain the default, but user should have an option to choose more cores ### 🔄 Alternatives Considered _No response_ ### 👤 Use Case / Persona Any user ### 📸 Screenshots _No response_ ### ⚙️ Technical Approach _No response_ ### ✅ Acceptance Criteria - [ ] Core supports more that core - [ ] We have a CLI flag - [ ] We have an option for backend - [ ] We have an input field in frontend ### 🤝 Are you willing to contribute this feature? Yes, I can contribute ### ✅ Submission Checklist - [x] I have searched for existing issues (open and closed) that request the same feature - [x] I have explained the problem this feature solves - [x] I have described a concrete solution or direction - [ ] I have considered alternatives and explained why they fall short
max added the coreenhancementbackendfrontend labels 2026-09-15 19:12:56 +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
documentation
Issues related to README.md, Wiki or comments
 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 backend core enhancement 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#38
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?