Make special BELA pattern for bela-specific command line arguments.

[sensestage]

If we keep adding Bela options to SC we could quickly run out of letters.
We could think to redesign the SC Bela-related command line options so that they take something like
--bela "-C 8 --pga-left -9 -H 0"
so that we do not need to implement that on both sides AND we save letters.

[giuliomoro]

I drafted this in giuliomoro@2fd434d

it is NOT ready to merge, I did not check your default options and you may want to add a bit more logic to check valid combinations of values, requires quite some cleanup, but shows the workflow.

Basically you can set defaults in main(), then pass the command line options straight to Bela's parser, then override/check those values again.

Bad things: 1) I am using a global variable 2) The BelaDriver depends now on what happens in main().

The "advantage" of this approach is that you do not have to implement all of Bela's command-line options every time one is added.
The disadvantage is that you depend more on the command line options assigned by Bela, which are slightly more likely to change meaning than the fields of the gBelaSettings structure.
As usual, the behaviour of SC heavily depends on the current version of the Bela files. At some point it may be worth adding a Bela subrepo with a tagged version to the SC repo .

Feel free to rearrange as needed (or dump completely) the code in my commit, this shows the path.

[sensestage]

I've started in this branch [1] with porting it, but there still seems to be an issue with starting scsynth from the web IDE.

[1] https://github.com/sensestage/supercollider/commits/bela_hackery_v02-belaoptions

[LFSaw]

there are peeps in the SC community thinking about integrating reading a config.yaml to scsynth. also to replace the (crude) commandline parsing by using a lib... I guess that's help a lot for this issue as well.

[giuliomoro]

Is it related to this? #42

[LFSaw]

not really... there's no issue for this yet. but I can ask around.

[LFSaw]

talked.
here are stub issues, will be filled in detail later-ish.
But I'd definitely wait before fiddling with the scsynth cli interface, and take part in these discussions.

supercollider#3117
supercollider#3118

[giuliomoro]

Continues here.