On Thursday 09 September 2010 00:32:18 Olivier Guilyardi wrote:
> On 09/08/2010 11:37 PM, Arnold Krille wrote:
> > http://positron.physik.uni-halle.de/~arnold/fadercolors-system_colors-won
> > ton.png
> > http://positron.physik.uni-halle.de/~arnold/fadercolors-system_colors-ob
> > sidian.png
>
> Sorry but wouldn't it be clearer with tiny level bars, instead of colors?
>
> http://testing.samalyse.com/lad/widgets/numbers.png
> http://testing.samalyse.com/lad/widgets/numbers.svg
Hm.
No. The left-to-right level-bars imply a left-to-right movement to change the
values.
And one of the reasons to do the color-thing is space. If I hide the text and
only show it when the mouse hovers, I can fit a lot of mixing-nodes on screen.
A horizontal (or vertical) bars needs more space to have a comparable
resolution.
I like the idea of hiding the mouse during value-changing moves. I already
have these "sliders" react to the mouse-movement logarithmic. That also helps
a lot when both coarse and fine changes should be possible with similar mouse-
movement.
And somehow I dream of a toolkit where you select a knob/slider/fader and it
then reacts to the turn-knob you have on your desk. But given the variety in
toolkits, I think this is a dream of the distant future unless that big knob
sends out mouse-movement signals...
Have fun,
Arnold
So far, nobody's mentioned how to get to the aforesaid knob in the
first place, or alternatives
to manipulating it.
Navigating with the mouse is a poor second to precise locating, and
using qwerty actions to set values, be it a knob or slider, is more
accurate.
So, tab, or an associated action to get to the knob in the first
place, and something like ALT+ up/down arrows (as an example) to change the knob
value. Then it's irrelevant whether the knob responds to mouse
up/down/left/right, or mouse wheel, for users who find those options
second best, when a more efficient and precise option already exists.
For graduated speed in the case of a spin knob (starting slow and
getting faster), the user only needs to
keep the actions pressed.
Alex.
--
www.openoctave.org
midi-subscribe(a)openoctave.org
development-subscribe(a)openoctave.org
Hello
EMutrix is a simple, easy-to-use graphical mixer application for EMU
1010 based cards like the E-MU 1212m, E-Mu 1616m and E-MU 1820 models.
I am releasing the first source package of EMutrix, version 0.1 at
http://emutrix.googlecode.com
It is mostly functional, allowing arbitrary routing between the card's
multiple inputs, outputs and ALSA, setting clock rate and pads. More
features to come in future versions. Try it out if you have an E-Mu
card!
Any comments welcome.
Greetings,
Camilo
After many month of development, we are proud to announce the version
0.6 beta of jMax Phoenix.
The major highlights for this version are:
- A first version of the puredata source compatibility kit, including
the build system and a full example of recompiled object library.
- A large set of usability bug fixed; all the bugs preventing a
smooth work flow have been fixed.
- Error handling improvements: most of the bugs and configuration
errors now results in error messages, and not unexplained freezes.
- A set of examples and tutorials has been recovered from old ISPW
archives; they are not updated to include all the major jMax
functionalities, but it is better than nothing.
Full release notes are available in the release notes section of the
projet site.
This release has been tested on Ubuntu and Ubuntu Studio 10.04, Debian
5, Fedora 13 and Mandriva Spring 2010; check the installation
instruction on the projet site for specific caveats for Debian and Fedora.
The Puredata compatibility sub-project has been *very* time consuming;
in order to better manage my scarce time resources,
we need some user feedback (and possibly help) to be able to evaluate
the actual interest of pursuing this development direction.
For more information and download and installation instructions go to
http://www.jmax-phoenix.org/.
For contacting the project team: contact(a)jmax-phoenix.org
The jMax Phoenix team
Thank you very much for your advice everyone.
As mentioned I have already made the LADSPA plugin and tested it with PulseAudio, so I will take a look at the PulseAudio LADSPA plugin module loader and see if I can add the functionality I need (multichannel audio and detection of when headphones are plugged in). Then I will see how it goes from there.
/Kim
