I'm getting crazy with an issue in gen~ (MAX 7.2.1, but also previous versions were affected).
Let's say at first I'm developing using MAX/gen~ 64-bit, Windows.
I made a patch using gen~ 'blocks' and everything works great. The next step for me is to enable/disable the processing of different portions of the code,
sub-routine is on => process
sub-routine is off => sleep
To make this, I have to do :
1--Go to the gen~ patch/abstraction (made by using "gen~ blocks")
2--click on "C" on the right of the screen, the auto-generated genexpr code is displayed
3--copy all the genexpr code in the -> right window
4--paste all the code inside a "gen~ Codebox"
5--link Codebox's output to the main output of the patch and delete all the previously used 'gen~ blocks'
6--place an IF-ELSE in the code to enable-disable the processing of different portions of the code.
If I use this method with simple patches, everything works fine.
If I use this method with very complex patches (700+ lines of genexpr are auto-generated), some Params /values that worked fine when the patch was written using 'blocks', do not work fine when the patch is written copying-pasting the auto-generated genexpr code -> inside a Codebox.
I remember I had the same issue using MAX version 7.1 : using the method above caused malfunctioning in the code.
At that point I repeated the procedure above BUT, before step #2, I simply disconnected the Param cord and suddenly I reconnected it to its original block/position (disconnect-reconnect a param to the same destination block). After that, following all steps #2,#3,#4... I noticed the Param worked fine as expected.
BUT now in MAX 7.2.1 this "sort of fix" do not work anymore.
Can I ask please if anybody in the forum (or also specially gen~ developers from C74 team/support) :
- have more detail on this, maybe it is related to some gen~ known bug...?
- or maybe know if there's ANY WAY to enable-disable processing directly using gen~ blocks ?
- or anything else: if happened also to other people, if it is a known issue to be fixed and when, etc... ?
-or maybe it happen only with the (MAX/gen~ 64-bit, Windows)? Maybe the 32-bit Windows / OSX versions are safe ?
Thank you so much, any help would be really greatly appreciated !