table object strange behaviour
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:
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.
please ignore the previous patch and use this one:
On 16 mai 08, at 14:47, Antonino Chiaramonte wrote:
> 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.
ej
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...
anto
Hello.
Has there been any progress with this?
Does anyone know if it's possible to store table presets when a patcher is saved?
Cheers
Tom
the bug was solved since the 5.0.4 update.
cheers
antonino