Recent changes to feature-requests

document what control-z does

Etienne Deleflie — Tue, 21 Oct 2003 22:58:59 -0000

... found it by accident

what does it do ?

jack transport mode

Patrice Tisserand — Mon, 20 Oct 2003 12:51:32 -0000

Add jack transport mode in jMax
When receive stop -> stop the dsp.
When receive start -> start the dsp.
Don't forget to add a way to disable this feature by the user at
running time.

a trigger for the new types

Jean-Philippe Lambert — Wed, 16 Jul 2003 14:04:34 -0000

the trigger object should work with any data objects (ivec, fmat,
dict...) as the fork object does.

Range operator in expressions

Diemo Schwarz — Thu, 05 Jun 2003 10:21:31 -0000

It would be useful (for index ranges in tuples or
matrices) to have a range operator that expands to a
list (tuple) of integer values, e.g. like in Perl:

2..4 -> 2 3 4 and reverse 1..-2 --> 1 0 -1 -2

or like in Matlab, with step:

2 : 4 1 : -1 : -2 or non-integer 6.5 : 0.5 : 8.1
--> 6.5 7 7.5 8

Midishare support

Patrice Tisserand — Wed, 04 Jun 2003 06:44:24 -0000

- Fix midishare package compilation (update for jMax 4.0.x MIDI API)
- Add midishare port in MIDI Configuration Panel

Graphics objects 2

Diemo Schwarz — Thu, 22 May 2003 12:28:31 -0000

Now the more complicated stuff:

It would be great if the graphics display objects could
be configured more flexibly.

First of all, as the scroll direction is in the wrong
sense for displaying time, we need to be able to choose
scrolling from right to left.

Second, the zoom x from the matrix display should be
available for the vector display, too, and should be
settable to < 1 for zooming out of large vectors.

Third, the y-axis of the matrix display (but also the
vector disp) should be flippable, to be able to
display frequency (e.g. of fft vectors) in the usual
sense.

The scroll direction and flip could be unified with the
zoom x/y parameters: negative values change the direction.
All of this of course settable by the inspector and by
messages.

Fourth, maybe it would be useful if the vector display
could receive also a bpf, to have an inline bpf display.

Sixth, for the latter, and in general, an auto-zoom
mode would be great that stretches the data to be
displayed to fit the size of the display object (x, y
or both). (This only has sense for a non-scrolling axis.)

Graphics objects 1

Diemo Schwarz — Thu, 22 May 2003 11:49:03 -0000

First the simple stuff:

Graphics objects (vector display, matrix display,
oscilloscope, but also slider, etc.) should make their
inspector configuration fields available as messages.

E.g. setting the min/max range would become equivalent
to sending a 'set min -5.0' or 'miny -0.5' message.

Also the coulour should be settable by 'foreground rgb
0 0.5 1' or 'background hsv 0 0 0' or 'set foreground
black'.

OSC implementation

Etienne Deleflie — Fri, 21 Feb 2003 03:26:22 -0000

Open Sound Control implementation.

This would greatly fascilitate communiaction with other
patcher software such as MAX/MSP, PD, etc.

Trying to communicate between jMAX and other patcher
software is something I am often challenged with
....... and always ends up being a messy mix of
different technologies ..... (I have to run PD at the
same time as jMAX, then I do an internal midi loop,
send midi data to PD which then converts to OSC then
out via ethernet to other MAX/MSP or PD users)

serial object port

Anonymous — Thu, 20 Feb 2003 19:57:14 -0000

Hi all,

As discussed earlier with Patrice, I would like to see the
serial object work again under 4.0.x. I use it in an
installation...

thank you

Alexandre

acastonguay@artengine.ca

package path

Patrice Tisserand — Thu, 06 Feb 2003 14:20:14 -0000

needs a way to define a user package path, maybe
adding a new tab in project editor.