[FEEDBACK REQUESTED]: ScribbleTune API-features for a command line interface.

[chozilla]

Hi,
I am working on a CLI / Chat version of a ScribbleTune interface.
I am not sure what features should be grouped together.
I think the max4live Devices are a good start to see what features are combined there.

scribbletune --riff C3 phrygian x-xRx_RR 0 AABC --sizzle sin 2
scribbletune --chord C3 major 1645 xxxx 1m --sizzle cos 1
scribbletune --chord C3 major CM-FM-Am-GM xxxx 1m --sizzle cos
scribbletune --chord C3 major random xxxx 1m
scribbletune --arp C3 major 1736 xxxx 1m --sizzle cos 4

Does this makes sense? (I will figure out when people are using it, - I guess.)
I would use the functions (--arp, etc.) to identify splits and then use spaces for parameters and regex to figure out the order and type of input.

Not sure if i will come up with something like repeating for the patterns inside of them. That would maybe be bad for the API.
Example: 'x-x-x-'.repeat(4); would be '4(x-x-x-)' or '(x-x-x-)4'

I know there is an extra project for the harmonics, but i wonder if there is something like scribbletunes-core planned. Something that is endpoint-agnostic and does not handle features for special endpoints (like midi export, browser sounds, etc.).
That would just bring you the creation of scribbletune clips, the data format for the clips, and the basics for modes and chords?

Best regards
\ chozilla

[walmik]

I apologize for the delay in responding here. I love this idea! I m surprised I didnt think of this before! I ll try to implement it 😃