# data[].attributes.body
(of embedded AI | for NIME)

# data[].attributes.body
(for NIME)

# data[].attributes.body
(for embedded AI | for NIME)

# data[].attributes.body
(for NIME)

# data[].attributes.body
(for embedded AI | for NIME)

# data[].attributes.body
* Inspired by NIME Workshops on NIMEhub, NIME archiving
* Embedded AI data, models and compute?

(as suggested on Jack Armitage's keynote)

# data[].attributes.headline
A few ML Opportunities (reflections from RF Keynote)

# data[].attributes.subject
A few ML Opportunities (reflections from RF Keynote)

# data[].attributes.body
Complex and new mappings.

New Design Approaches

Embedded systems lend themselves to small data sets (NB they don't have to be large)

Many ML NIME systems can actually be simple and focussed (less need to allow for noisy users), and a bit of looseness might in fact be quite nice.

Does the ML component need to be in Real-time? Use ML to pre-prepare a corpus or look-up

table for example.

# data[].attributes.headline
What is success? (from Rebecca Fiebrink's keynote)

# data[].attributes.subject
What is success? (from Rebecca Fiebrink's keynote)

# data[].attributes.body
accuracy? efficiency, latency?

# data[].attributes.headline
Releasing ML NIME Interfaces (from RF keynote)

# data[].attributes.subject
Releasing ML NIME Interfaces (from RF keynote)

# data[].attributes.body
Things to think about...

How accessible is it?

What controls are you going to make available?

Please add more! :)

# data[].attributes.headline
How can we helpfully use any parallels between craft methods and creating NIME ML?

# data[].attributes.subject
How can we helpfully use any parallels between craft methods and creating NIME ML?

# data[].attributes.body
Jack expressed an interest and Rebecca presented a cyclic development model of

=> building a model =>playing => use data from the playing to =>build ....

# data[].attributes.body
Can we bypass a lot of programming and hardware specific 'pain' by looking for browser type environments?  Can this approach actually widen the access to our projects?

# data[].attributes.headline
Following Rebecca's "smaller is better"...

# data[].attributes.subject
Following Rebecca's "smaller is better"...

# data[].attributes.body
A lot of AI for audio comes from MIR. Goals and constraints in MIR are quite different, with the result that huge models digesting entire pre-acquired music events are the norm in the discourse. Due to the real-time nature of musical instrument interaction, NIME has no choice but to focus on the other end of the spectrum. I would argue that less leading-edge architectures are actually going to be more useful for NIME. I also believe that attention towards minimal-latency time-domain models is long overdue!

Andrea

# data[].attributes.headline
How have you approached making usable/useful user interfaces for embedded AI systems?

# data[].attributes.subject
How have you approached making usable/useful user interfaces for embedded AI systems?

# data[].attributes.headline
Big shout for the developers cracking the hard code!

# data[].attributes.subject
Big shout for the developers cracking the hard code!

# data[].attributes.body
Getting systems like PyTorch running on BELA and Pi are out of reach of many artists - list here any amazing projects that do just that. Thanks to these pioneers!

# data[].attributes.headline
Key hardware focus for World or Hello Worlds

# data[].attributes.subject
Key hardware focus for World or Hello Worlds

# data[].attributes.body
What are the key hardware - Jetson, BELA, Raspberry Pi

# data[].attributes.body
Dedicated Discord? WiKi? a postable place?