I’ve been reading about this and found posts like this one:
https://cycling74.com/forums/topic/para ... o-history/
I have what I *think* is a different problem – please correct me if I’m wrong!
I want:
– a M4L device with a visible live.numbox called "the_num" (for example) that has a frequently changing value in it
– I want to have "the_num" visible to other M4L devices like Max api param2param so I can map "the_num" to many other things in my Live set
– I don’t want "the_num" to write to the undo history, but if I set it to "hidden" then I can’t access it with other Max api devices
Is there any way to do this?
thanks,
j
M4L parameter visible for mapping BUT w/no undo history?
-
- Posts: 9
- Joined: Thu Apr 16, 2015 11:23 pm
Re: M4L parameter visible for mapping BUT w/no undo history?
Not possible... move on...
Cheers
D
Cheers
D
-
- Posts: 9
- Joined: Thu Apr 16, 2015 11:23 pm
Re: M4L parameter visible for mapping BUT w/no undo history?
Drag.
FEATURE REQUEST!!!
A 4th option in the M4L inspector window:
(old) - Automated and Stored
(old) - Stored Only
(old) - Hidden
(new!) - Visible but No Undo
FEATURE REQUEST!!!
A 4th option in the M4L inspector window:
(old) - Automated and Stored
(old) - Stored Only
(old) - Hidden
(new!) - Visible but No Undo