- Bugfix: Makes sure that the "changed" event will be triggered when we will
set the right value (the trick of setting an out of range value do not work
anymore with gtk+-2.x).
- Bugfix: Same as above for toggle buttons.
Signed-off-by: Giuliano Pochini <pochini@shiny.it>
- Matrix mixer drawing code cleanup.
- New feature: echomixer can load and restore the status of nominal level
switches.
Signed-off-by: Giuliano Pochini <pochini@shiny.it>
- Big cleanup in the matrix mixer drawing code. It make is way
smaller and readable.
- New feature: echomixer can load and restore the status of nominal level
switches.
- Version number bumped to 1.0.3.
Signed-off-by: Giuliano Pochini <pochini@shiny.it>
Fix by Dirk Jagdmann <doj@cubic.org>:
The attached patch fixes a compiler warning, which points to a possible
bug when initializing the midi controllers.
From Dirk Jagdmann <doj@cubic.org>
Hello developers,
I just gave the latest CVS version of envy24control a try and had to add
this simple patch, so it would not abort upon program start immediately.
Hello devlopers,
I have made the mixer sliders in envy24control react to MIDI
controllers. This way the hardware mixer can be controlled from a
sequencer program or some external MIDI controller hardware.
envy24control became a standard ALSA sequencer client which you can
connect to arbitrary other MIDI sources/sinks.
Signed-off-by: Dirk Jagdmann <doj@cubic.org>
This patch converts hyphens to minus signs in the man pages (for options,
emails, or command line examples).
This patch also closes one font modifier in iecset.1.
(s/\fIfalse\fI,/\fIfalse\fP,/)
Signed-off-by: Nicolas FRANCOIS <nicolas.francois@centraliens.net>
Tascam US-224/428 MMC Implementation
This is my latest patch against the alsa-tools tree (as of todays CVS
HEAD), regarding the us428control MMC implementation as for the Tascam
US-224/428 audio/midi USB control surfaces:
us428control now bumps to version 0.4.4.
Interesting points are: jog wheel dialing is now alternating between
spitting out some MMC-Step or MMC-Shuttle messages, depending on transport
state, instead of those MMC-Locate(s) which was an early implementation
mistake of mine.
Controlling ardour with (my) US-224 is getting much more fun now :)
However, there's still some little annoyances due to my lack of advice
regarding ardour's Play/Record control behaviour:
1) Ardour doesn't seem to send out MMC-Play messages when one starts
transport within it (e.g. by clicking the playback button widget).
2) Ardour doesn't seem to react against MMC-RecordPause, which I assume
(probably erroneously) it would be equivalent to clicking on its record
widget button.
3) Sending a MMC-RecordStrobe message to ardour has the strange effect to
start playback while toggling recording off instantaneously.
AFAICT these issues seems to be specific to ardour (0.9beta18.4), not to
us428control which is just sending out the proper MMC messages. Or that I
think.
I would like to settle all this before I'm going off on holidays. Hope
it's welcome and on time for the imminent alsa dot-6 release :)
MMC support has been improved and transport LEDs is getting almost
functional. Tascam control protocol sysex decoding is also complete (LEDs
control mainly).
