[ardour-dev] Mackie protocol
paul at linuxaudiosystems.com
Wed Jan 3 11:11:35 PST 2007
On Wed, 2007-01-03 at 18:25 +0000, John Anderson wrote:
> On Sat, 2006-12-23 at 18:52 -0500, Paul Davis wrote:
> > John, I'm gone and offline till January 1st.
> I hope you had a good holiday.
it was excellent, thanks. almost as good as sensing real progress with
your work ...
> * Out of curiosity mostly - where is the thread that does the reading of
> the port? I was kinda surprised that it was emitting signals without
> calls to Port::read().
i don't think this can happen. the parser is run as part of
Port::read(), so the signals are emitted from the same thread that calls
Port::read(). what signals are you seeing?
> * There are a bunch of buttons on a MCU that can be assigned to just
> about anything. Some of the Logic mappings didn't really make sense for
> Ardour. So I'm going with the MCU layout for now. Of course the mapping
> will be easy to change if necessary.
looks pretty reasonable.
> * For the route_table - I'm assuming that it would have 8 entries - one
> for each physical fader?
> (I'll leave the issue of the master fader til
> later - mainly because my bcf doesn't have one ;-). So each time a bank
> switch happens, the route_table must be repopulated according to a new
> set of remote ids?
> * When are the remote ids assigned to routes? Is this the responsibility
> of the control surface module, or of ardour's internals?
they default to a sequential ordering when created, the user can change
these from the GUI but it is imagined that this would be rare.
> * What's the best way to get to the pan widget/data for a route?
there are several cousins of this method. xpos varies between 0 and 1.0
for a stereo panner. "n" is the number of the stream you want the pan
information for, 0..1 for a 2-in track/bus, 0 for 1-in.
Route::panner().size() will tell you how many there are.
More information about the Ardour-Dev