uxn, music, sndkit 

@paul @sejo can you drop a pointer to the inter app communication process in uxn. wanting to sync my orcas or other midi devices. thanks.

uxn, music, sndkit 

@furiousgreencloud @paul @sejo paul disconnected the varvara screen, and sends two bytes at the 00 and 01 ports of the second device(#20 DEO)

In orca, you can send raw bytes out using the / operator. This could allow you to make up your own micro-language :)

uxn, music, sndkit 

@furiousgreencloud @paul @sejo

If you uxnemu orca.rom | some_program, you can intercept these I/O events and use them as you like :)

wiki.xxiivv.com/site/ansi_c.ht

uxn, music, sndkit 

@neauoire @sejo @paul
thanks i didn't know about the / operator is there also a \ operator for input?

for:
$shim 1 | uxnemu orca.rom | shim 2
?

tho i know we use : for midi output.

would love to send or recv midi clock to orca-toy, im oddly invested in using orca.rom rather than the other versions, my inner idealist

(ps i know C and unix, just thought @sejo was talking about IPC (inter process communication, my mistake))

uxn, music, sndkit 

@furiousgreencloud @sejo @paul right now, orca will interpret any incoming byte as input, and 11, 12, 13, 14 as movements. I could store 127+ bytes and output them under a \ operator if that'll work for you?

Follow

uxn, music, sndkit 

@paul @sejo @neauoire

2/3 Looking at the ascii and midi specs and thinking about what a 'sequencer' should take as input leads me to think about start stop and clock being way more useful. There are many low bytes for this kinda thing. This is likely the most important use case.

Sign in to participate in the conversation
LIVE Platform

The LIVE Performance Art International Network
—a platform supporting the Discussion, Curation and Dissemination of LIVE Arts in all it's manifold forms.