Alo Faro

I'm making a maxforlive device based on selected track ID number, routed as a number and stored as a preset. Everything works fine with a "clean" template (all track IDs are small numbers) but I got an old template I use to improve from time to time where track IDs are high numbers (for instance above 10000), and in this case, it seems [Preset] doesn't store these values... 

After investigations, [Preset] doesn't store above the 2048th slot...

It seems to be clearly enough for most uses :) but in this particular case, I'm a bit annoyed since I cannot find another way to achieve my goal (a preset slot per session track depending on his ID). 

IMHO This "ID method" seems to be the best because it allows to erase and move tracks across the Live session without disturbing everything else.

Is there a way to manage these unique IDs above 2048 ? 

Maybe an incremental system for each track created ?

Can I store and recall presets using a trackname ?

All leads are very welcome ! Thanks in advance for your help !

I'm making a maxforlive device based on selected track ID number, routed as a number and stored as a preset. Everything works fine with a "clean" template (all track IDs are small numbers) but I got an old template I use to improve from time to time where track IDs are high numbers (for instance above 10000), and in this case, it seems [Preset] doesn't store these values... 

After investigations, [Preset] doesn't store above the 2048th slot...

It seems to be clearly enough for most uses :) but in this particular case, I'm a bit annoyed since I cannot find another way to achieve my goal (a preset slot per session track depending on his ID). 
IMHO This "ID method" seems to be the best because it allows to erase and move tracks across the Live session without disturbing everything else.

Is there a way to manage these unique IDs above 2048 ? 
Maybe an incremental system for each track created ?
Can I store and recall presets using a trackname ?

All leads are very welcome ! Thanks in advance for your help !

I'm making a maxforlive device based on selected track ID number, routed as a number and stored as a preset. Everything works fine with a "c

-preset-object-limitation

https://cycling74.com/forums/how-many-slots-in-a-preset-object

I found this topic: https://cycling74.com/forums/how-many-slots-in-a-preset-object 
[pattr] seems to solve my problem !

I found this: https://cycling74.com/forums/how-many-slots-in-a-preset-object 
It seems [pattr] solve my problem !

[Preset] object limitation