Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
ruby.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
If you are interested in the Ruby programming language, come join us! Tell us about yourself when signing up. If you just want to join Mastodon, another server will be a better place for you.

Administered by:

Server stats:

1.1K
active users

ruby.social: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#mutex

0 posts0 participants0 posts today
Replied in thread
Public
cyclical_obsessive

@drfootleg Another tip that has been plaguing me for a month!

If you have processes inside a Docker container and other processes outside the Docker container that need mutex protection such as I2C bus or SPI bus accesses, you need to map the bus (obviously) **and** the mutex folder!

I had the sensor access working great but could not figure out why my inside and outside "mutex protected" accesses were colliding...

Diagram showing that a mutex protected class inside a Docker container and a mutex proteccted class outside the container - with mapped I2C bus and mapped mutex folder /var/lock
#GoPiGo3#Docker#RaspberryPiOS
Public *
stateful being

#tui #daw for #jack in #rustlang

Rewrote the UI of the #midi sequencer with #ratatui for double buffering.

We're polyphonic now! Multithreaded, too - I put a #mutex between input/render/audio threads instead of message passing.

Doesn't even properly support Note Off events yet, but it does play a mean cheerful dirge. Playback cursor position still off, though.

Hooking this up to the VST host every time I restart either is bit of a faff. Gotta teach it to auto-connect the MIDI/audio ports...

A transport and piano roll rendered using characters in a terminal.
ExploreLive feeds
About