yurki

- I close everything and remove the device from the track

both when I put back the device and when I press the edit button:

a crazy amount of tables are opened from my subpatches.

(actually all just the same table with a common name. and with a

triple dash '---' in front of the name to make it not mixable with

I do understand that you have to close everything before saving

so these windows won't open when you edit ( which is on it's own

a bit time consuming to do all the time).

But the tables keep on coming up and it takes a few seconds to load

all the time which is very unpleasant. Worse is that the end user

will see useless tables coming up for no reason.

Anyone knows what is the proper way to deal with this?

- I edit my device
- I close all subpatches and tables
- I save the main patch
- I close everything and remove the device from the track

both when I put back the device and when I press the edit button:
a crazy amount of tables are opened from my subpatches.
(actually all just the same table with a common name. and with a
triple dash '---' in front of the name to make it not mixable with
other devices)

I do understand that you have to close everything before saving
so these windows won't open when you edit ( which is on it's own
a bit time consuming to do all the time).
But the tables keep on coming up and it takes a few seconds to load
all the time which is very unpleasant. Worse is that the end user
will see useless tables coming up for no reason.

Anyone knows what is the proper way to deal with this?
thanks in advance...


table-windows-open-when-device-is-loaded-or-edited

to be more clear, it goes already wrong at saving:

- I close everything except the main device patch.

- I save and RIGHT away 50 or more tables are opened

Saving and opening costs really a lot of time this way.

- I close everything except the main device patch.
- I double check this in menu 'window'.
- I save and RIGHT away 50 or more tables are opened
coming from subpatches.

Saving and opening costs really a lot of time this way.


I solved it by using coll instead of table...

doesn't explain the weird behaviour of max,

doesn't explain the weird behaviour of max,
but at least I got rid of it :)


When you save your patch/device, it will also store wether or not your table's window was open. So if you want to avoid the window to open you have to remember to close it before saving.

anyway, the colls don't have the problem, so I'm fine now...

I know, but as I said:
it also happened when I did close all
tables before saving...
even made the patch 'dirty' by quickly
adding and deleting an object so I knew
it saved for sure.

anyway, the colls don't have the problem, so I'm fine now...


I am having the same issue here: patch is saved with table window closed, but when the device is loaded in Ableton, the table window pops up automatically. 

Is there any way to tell table not open at startup? 

It didn't use to behave this way. Using Max 7.3.4 and Live 10.0.1

I am having the same issue here: patch is saved with table window closed, but when the device is loaded in Ableton, the table window pops up automatically. 
Is there any way to tell table not open at startup? 
It didn't use to behave this way. Using Max 7.3.4 and Live 10.0.1


renaming the table fixed the issue, weird...

table windows open when device is loaded or edited