Welcome to the inaugural event of the Audio Developer Meetup Berlin!

Join us to celebrate the start of this event series. For this very special occasion, we will be looking forward to talks by two world-renowned speakers: interdisciplinary artist and designer Astrid Bin and C++ guru Timur Doumler.

After the talks there will be time to network over drinks and pizza. Anyone interested in Audio development is welcome!

How to get to the venue: Unfortunately, the pin that meetup is showing for the event is not quite accurate. Holoplot is located here. You will need to enter the courtyard at Ringbahnstr. 10-14 and then walk to the entrance A2. The meetup will be on floor 4. Please use the stairs if possible. If you need to take the lift then please ask someone from Holoplot for assistance.

Talks: You've made it, now explain it Astrid Bin

Making the thing is one part of the design process, but documentation is part of a broader process of designing any hardware or software product, and one that has a significant impact on how and why people buy what you make. Music technology is particularly tricky, because no matter how intuitive the design people need to be able to start somewhere and learn how to use it, and use it in their own creative context. In this talk Astrid shares lessons she's learned through incorporating documentation into the design process of Bela, a hardware system for creating interaction with sensors and sound, as well as Bela's other products that range from touch sensors to synth modules.

Demystifying std::memory_order Timur Doumler

Atomic variables are an essential tool for programming for real-time audio processing as they are needed to implement any kind of lock-free algorithm or data structure. In C++, atomic variables are readily available in the Standard Library through std::atomic. In order to use std::atomic in an efficient and performant manner, it is crucial to pick the correct memory order for the atomic operation at hand depending on the requirements of the algorithm, which can be accomplished via the std::memory_order parameter that every atomic operation in C++ accepts. Yet memory order in C++ is notoriously hard to reason about and often misunderstood. In this talk, we give a brief overview over the C++ memory model, explain the differences between relaxed, consume, acquire, release, and sequentially consistent memory order, and give some guidelines for which to use when working with atomic reads, writes, read-modify-write operations, and memory fences.