punk3st

Hi, I want to control live with a couple of midi devices (axis 49), since im new with max and i was away from the midi controller i decided to start patching using a computer keyboard to emulate the axid and begin to trhow some ideas into max. Finally and after a lot of try and error i was able to control live the way a i wanted (launching clips, scens, control volume, pan, sends, racks...). Since the beginning (but thought was normal) the patch only worked if the edit window was open and on top of live which at that moment didnt matter, but now that im trying to implement the patch with the axis 49, i realised that sending midi notes with the edit window open means a lot of latency which turns the patch useless.

So any one could point me in the right direction to fix this issue?

I would like to post the code but seems that .amxd files can not be open as text.

Hi, I want to control live with a couple of midi devices (axis 49), since im new with max and i was away from the midi controller i decided to start patching using a computer keyboard to emulate the axid and begin to trhow some ideas into max. Finally and after a lot of try and error i was able to control live the way a i wanted (launching clips, scens, control volume, pan, sends, racks...). Since the beginning (but thought was normal) the patch only worked if the edit window was open and on top of live which at that moment didnt matter, but now that im trying to implement the patch with the axis 49, i realised that sending midi notes with the edit window open means a lot of latency which turns the patch useless.
So any one could point me in the right direction to fix this issue?
Why is this happening?
I would like to post the code but seems that .amxd files can not be open as text.

max-patch-only-works-if-edit-window-is-open

the tests have to be done only in running mode, not in edit mode.

it means: if it doesn't work in running mode, it doesn't work at all :)

generally, midi I/O problem can give differences between the 2 "modes"

the tests have to be done only in running mode, not in edit mode.
it means: if it doesn't work in running mode, it doesn't work at all :)
generally, midi I/O problem can give differences between the 2 "modes"


This may not be at all relevant, but for awhile I was mis-diagnosing a problem as being something similar (only working when in edit mode), when in fact it was something else entirely and every time I opened the patch in edit mode it would reset the patch, and therefore work for a bit.

all live.path and other things are reliable ONLY in running mode.

all live.path and other things are reliable ONLY in running mode.
I checked that a lot of time.

so, it isn't an issue, it is as it is.
test things in running mode :)


Just to say tanks for your comments and let you know that the patch works as it should if the live API commands are triggered by midi but (not that i care) if triggered with computer keyboard the edit window most be opened and on top of live, otherwise patch wont work. Makes any sense? :)

||all live.path and other things are reliable ONLY in running mode.

It's good to know that what works in running mode is always ok.

But I think there are two reasons for edit mode not always working *is* an issue:

1. It's annoying to switch constantly between edit mode and running mode when developping a patch. Perhaps this can be overcome by deploying 2 patches: one in running mode and one in edit mode that communicate by using plugsend and plugreceive.

2. Sometimes the 169 bit high user interface is just too small. Developing patches to run in edit mode (albeit with 12 ms latency) can solve this sometimes.

To make the device-strip and/or single single device interfaces in running mode detachable (on a second monitor) is on my wishlist for Ableton and Cycling '74.

||all live.path and other things are reliable ONLY in running mode.
||I checked that a lot of time.
||
||so, it isn't an issue, it is as it is.
||test things in running mode :)

It's good to know that what works in running mode is always ok. 

To make the device-strip and/or single single device interfaces in running mode detachable (on a second monitor) is on my wishlist for Ableton and Cycling '74.


as a guess - perhaps you use computer keyboard input from say "key" which needs Max in the foreground? One possibility is using "hi" and input from e.g. trackpad 2. What is it you are using?

I have a similar problem where I can get device ids and control effect parameters if the Max window is in edit, but when closed the patch - very similar to the video theremin example, does not work.

Max patch only works if edit window is open