@neauoire @eel @npisanti @Lutrinus should I remove the --portmidi-list-devices and --portmidi-output-device features ? I think they mostly aren't needed now. Unless people are using special launching scripts that are specifically required for their setup.

Show thread

@cancel @neauoire @eel @Lutrinus i'd prefer to still have the cli options, i will use orca inside installations or scripts (to save full setups of orca + other programs) and those options are really useful


@npisanti @neauoire @eel @Lutrinus Unless you can think of another way to accomplish the same thing? Having two ways to set the same stuff adds a significant amount of code to orca-c. Maybe something like, you can pass the config file as a string instead of having it use the file? (And that would let you set the PortMidi device by name using the commandline.)

· · Web · 1 · 0 · 0

@npisanti @neauoire @eel @Lutrinus would you prefer to pass a path to a config file, or pass the actual contents of the config file? hmm. I'm not sure what a good design here is.

@cancel @npisanti @eel @Lutrinus I'd remove them, I think people who would need them, are in a position to fiddle with the code themselves.

@neauoire @npisanti @eel @Lutrinus actually, since I coded orca-c to respect the FreeDesktop config dirs thing, you can sort of already do it. Set XDG_CONFIG_HOME environment variable to use an alternate directory path for config files. which should let you keep several alternate config files around for specific setups

@neauoire @npisanti @eel @Lutrinus so like,

XDG_CONFIG_HOME=~/orca_setups/rack_synths build/orca

and you would have a config file at


@cancel @neauoire @eel @Lutrinus ok also changing the xdg home is fine for me, but very poweuser-y

@npisanti @neauoire @eel @Lutrinus i think having to pass device IDs is also poweruser-y. i could add an explicit option for the config file, though. that's pretty easy to add.

@cancel @neauoire @eel @Lutrinus ps: i don't know how many things you are going to put into the config in future, i need at least to the --bpm and --seed cli option to keep existing as i am generating the seed for every execution from system random and parsing the bpm from my .orca files names

@cancel @npisanti @eel @Lutrinus it doesn't. What I do to save my bpm is just write E$bpm:128 at the top of my file.

@neauoire @npisanti @eel @Lutrinus OK. I'm not planning on removing --bpm or --seed anytime soon. Just the portmidi stuff, because dealing with portmidi is complicated and it leaks memory.

@neauoire @npisanti @eel @Lutrinus sorry, by removing the portmidi stuff, I meant just minimizing the number of ways it can be initialized and used. the alternate code path for the commandline flags to list the devices and exit, or to initial-start with a specific device ID, adds a decent chunk of code (and makes the usage help string pretty long.)

@cancel @neauoire @eel @Lutrinus if it's just for portmidi i'm fine with config and the possibility of changing xdg home

@npisanti @neauoire @eel @Lutrinus Passing --config filepath with a config file that can't be found. Should it cause orca to quit immediately with an error?

@cancel @neauoire @eel @Lutrinus yes in my opinion, reporting to the user the file does not exists

@cancel in linux many programs use -c /path/to/your.conf if you want to use another file instead of the default conf

@neauoire @eel @Lutrinus

Sign in to participate in the conversation

Merveilles is a community project aimed at the establishment of new ways of speaking, seeing and organizing information — A culture that seeks augmentation through the arts of engineering and design. A warm welcome to any like-minded people who feel these ideals resonate with them.