Re: [Loopdub-devel] Synchronizing MIDI controls with LoopDub
Brought to you by:
radarsat1
From: Stephen S. <rad...@gm...> - 2008-01-03 22:23:26
|
> I'd be quite happy to do the coding part of the job, if that's what > you're asking. As far as I'm concerned, the hard part of the job is > close to over, now that we've hammered out most of the design -- > something that I could not have done by myself. It has been a pleasure > thinking with you, by the way. Yeah, it's great that you've shown interest in my little audio project. :) I just mentioned that to warn you in case my replies start to come slower over the next few months. However, I'll try to be ready to commit patches whenever you have something. I really enjoy working on this program, but if you look at the logs you'll see that there were pretty much no commits in the last couple of years, except in december.. I'm working on a PhD at the moment and I have no idea how busy I'll be this year. In any case, I'll post if I come up with something for the MIDI stuff. I'm not sure how to implement what we discussed.. It seems that trying to set the GUI sliders directly from the MidiValue class isn't ideal, because of things like the Button Mode selection. Perhaps what's needed is instead of binding CC messages to GUI sliders, to bind them instead to messages (methods) that the LoopOb understands. I guess this would have to be a bidirectional communication. Of course, Button Mode selection isn't associated with a LoopOb, but is global. That may just be a different case entirely.. Perhaps the LoopDub class should also be able to receive messages from MidiValue. Steve |