About track/FX channel mute automation
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 1.3k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 7
Description
In automation of track(or FX channel) mute button, 0 means it isn't muted, and 1 means it is muted. In other LED controls, however, 0 means inactive state, 1 means active state.
Maybe people use track/FX channel mute automation very rarely, I think it can be confusing because the mute buttons of NOT muted tracks look like other LED toggles in ACTIVE state. First one has value 0 while second one has value 1. This issue also applies on controller connections.
How do you guys think about it?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named in the issue. Trace track/FX mute automation and controller-connection handling, then resolve the proposed 0/1 semantics and define tests for both muted and unmuted states.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- audio-video-rtc
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100