On Thu, Apr 30, 2009 at 6:12 PM, Garth Dahlstrom <[email protected]> wrote:
>
> On Thu, Apr 30, 2009 at 12:16 PM, Russell Ryan <[email protected]> wrote:
>>
>> We should have a note about this somewhere. If you compile with `scons
>> prefix=/path/to/checkout/mixxx/res' then it can run out of its build
>> directory.
>
> scons -j3 prefix=`pwd`/res && ./mixxx # Use 3 threads to build Mixxx via
> scons with the resourcePath in the Mixxx BZR resources directory and run
> Mixxx when finished if successfully built.
>
>>>
>>> I noticed "Crossfader" was the first item in the midi wizard thingy, so
>>> I set that and exited the wizard. After that, the crossfader was the
>>> only control which worked (though its motion was still reversed). And I
>>> didn't see a "Crossfader" entry in the mapping table, so I wasn't able
>>> to find a place to manually adjust it.
>>>
>>
>> Ahh so Midi Learn replaces all mappings? We might want to make them merge
>> the mappings, though I'm not sure if we should before 1.7.0. Albert?
The code that I wrote is supposed to replace mappings for controls
that are already mapped. For example, if your crossfader was mapped to
something and you run the MIDI learning wizard, and exit it after
remapping your crossfader, only the crossfader mapping will be
updated.
It does not clear the mapping table.
>
> I saw something like this sometimes where you hit a non-button control
> (which slider/jog/knob which presumably sends multiple updates when bumped)
> and it was detected as multiple controls. Perhaps the midi queue needs to
> be cleared or learning needs to drop any signals from the last control
> detected... i.e.
> if (midi_code == last) { skip; }
> last = midi_code;
> // accept signal
I already made some changes to try to help combat this, but I guess
they weren't enough. The next thing I'd like to do is make is so that
the _last_ MIDI message received while "learning" is the one that is
mapped. (Most MIDI learning systems work like this, and it solves the
queuing problem in an easy way.)
> ...
>
> I also noticed that buttons were not assigned the correct "Button" option,
> if you adjust them from "Normal" to "Button" you might see those start to
> work.
>
Button shouldn't be the default behaviour - it's mostly used with the
Hercs, but I forget the exact reason why. (The Hercs are a bit weird
in that they send CC messages instead of NOTE_ON/OFF for their
buttons, it probably has something to do with that.)
Another simple thing I'd like to do in the future is add a checkbox or
combobox to the MIDI learning wizard that allows you to select an
"option" on the fly. For example, a little checkbox for "reverse"
would help people like Mark get their crossfaders working. Currently,
you need to go to the right-most column in the mapping table and
select "reverse" manually.
(Semi-OT: There's this (Qt?) bug where if I set the title for the
right-most column in the mapping table, the table header with all the
titles disappears, so for now the "Option" column is unlabelled. Does
this ring a bell with anyone? I don't know what else to do...)
Thanks,
Albert
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Mixxx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
