emj_antonin

table object seems to have some problems used together with preset object. i can store different values and recall them, but if i save and close the patch, when i re-open it table doesn't retain the different values stored into the different presets. sometimes max window report > table: doesn't understand "set".

table object seems to have some problems used together with preset object. i can store different values and recall them, but if i save and close the patch, when i re-open it table doesn't retain the different values stored into the different presets. sometimes max window report > table: doesn't understand "set".
try please and let me know:

table-object-strange-behaviour

can anyone reproduce it? sorry for my english, but maybe I was not clear.

1) try to save your own table presets, then recall them without closing the patch.

3) open it again and control your table presets.

please ignore the previous patch and use this one:

can anyone reproduce it? sorry for my english, but maybe I was not clear.
1) try to save your own table presets, then recall them without closing the patch.
2) save and close the patch.
3) open it again and control your table presets.

On 16 mai 08, at 14:47, Antonino Chiaramonte wrote:

> can anyone reproduce it? sorry for my english, but maybe I was not 

> 1) try to save your own table presets, then recall them without 

> 3) open it again and control your table presets.

I've been able to reproduce something similar while importing a preset 

> can anyone reproduce it? sorry for my english, but maybe I was not  
> clear.
> 1) try to save your own table presets, then recall them without  
> closing the patch.
> 2) save and close the patch.
> 3) open it again and control your table presets.

I've been able to reproduce something similar while importing a preset  
from 4.6. We will investigate.

Quote: Emmanuel Jourdan wrote on Fri, 16 May 2008 15:05

----------------------------------------------------

> I've been able to reproduce something similar while importing a preset 

the max window error report (table: doesn't understand "set") happens exactly when I open a 4.6 patch into max5. but also in a new brand max5 patch preset object doesn't store values for table, like in my little example...

Quote: Emmanuel Jourdan wrote on Fri, 16 May 2008 15:05
----------------------------------------------------
>
> I've been able to reproduce something similar while importing a preset  
> from 4.6. We will investigate.
>
> ej
----------------------------------------------------

thank you emmanuel.
the max window error report (table: doesn't understand "set") happens exactly when I open a 4.6 patch into max5. but also in a new brand max5 patch preset object doesn't store values for table, like in my little example...

Does anyone know if it's possible to store table presets when a patcher is saved?

Has there been any progress with this?
Does anyone know if it's possible to store table presets when a patcher is saved?

When I attempt emj_antonin's second example, everything works fine: presets are stored and recalled appropriately so it appears fine when creating a brand new patch in the current version of Max.

Also, the 'Bug Features and New Features List' for Max Version 5.0.4 show that something along those lines was fixed:

https://cycling74.com/version/version_5_0_4.html

"preset: fixed problems saving and recalling presets for table object after reading in files"

in case you ever need to find all the bug fix and new feature lists, they are all linked from the most current page:

https://cycling74.com/version/version_5_0_6.html

3rd entry from the bottom on that page:
"preset: fixed problems saving and recalling presets for table object after reading in files"

in case you ever need to find all the bug fix and new feature lists, they are all linked from the most current page:https://cycling74.com/version/version_5_0_6.html


the bug was solved since the 5.0.4 update.

table object strange behaviour