I've been tracking down a bug in Jack recently; it prevents GStreamer's Jack element from connecting Jack ports. It's a tricky multithreaded, multiprocess bug that's triggered by some thread interlocking and timing issues. It's taking a bit of time.
I've been working on beatbox for over a year now. It's why I got started with GStreamer and with Jack, and things are finally looking good. I've got a new vision for it; once the Jack element is complete for GStreamer, beatbox will be a Jack-only mixer and effects processor. It will produce no audio, only mix together Jack streams, applying effects along the way. Should be pretty neat. Probably more on this in the future.
the task stack
It's funny how you (read: me :) want to do something, but you end up having to do some many other things first to enable you to do that thing. I want a scriptable, real-time music generation framework that can respond to ambient
sounds. So, one tool is a scriptable mixer for multiple audio streams. So, I need a framework to build that app. So
I start work with GStreamer, work on Jack a little, etc etc... pushing items onto the task stack. Once you finish a
goal, pop off the stack and return to what you were working on, until you realize you need to do something else first... so much ongoing, small-stepped effort that oftentimes never gets completed.
but damn, I want to make some thumping, swirling beats !
Comments are closed.