jamulussoftware / jamulussoftware/jamulus
Enhance Load Mixer Channels
- Dominant language
- C
- Stars
- 1.1k
- Forks
- 248
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 9
Description
### Discussed in https://github.com/orgs/jamulussoftware/discussions/3063
Originally posted by **pcar75** May 10, 2023
Currently (3.9.1) this facility does no error checking and expects the full 250 "fader" entries (like jamulus.ini) to be present.
Feature request :
Enhance this function to verify and add , or update if already present , fader entries (1 < nb <= 250 ) to jamulus.ini.
Suggestion : on the hypothesis that tag# have no dependence on Alias / Name , and new entries are always added from tag# 0 upward and discarded after tag# 249 Re-tag changes (entries new and updated) from tag#0 ( or tag#1 if tag#0 is reserved for "own user").
Ref : Discussion #3063 , #2842
Contributor guide
Research direction
Start with Discussion #3063 and the existing load-mixer handling for jamulus.ini. Determine how current fader entries are read, then verify the requested behavior for adding or updating 1–250 entries and retagging entries from tag 0 through 249. Done means partial or changed fader lists are handled without requiring all 250 entries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- audio-video-rtc
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100