Kasper

I very often use B-patchers using arguments to change 1 or 2 things in the same patch (which for instance could be the number/name of a slider from an external controller)

_in max 4 changing this argument updates the bpatcher and I can use it at once

_in max 5 when changing the argument max asks to quit and reload the patch containing the bpatcher to work with the new argument (number)

_still in max 5, when using a bpatcher done in max 4 (and not saved in max5, being "max4" somehow) I can change the argument and it works as it did in max 4 (so it's possible in max 5)

_I did not download the beta for max6 yet, but if the arguments could work as in max4 (without the need to quite/reload the patch) it would be great

arguments-to-b-patcher-max-4-5-6

I got a similar thing, though it didn't ask to quit/reload, it gave me "error loading bpatcher". Also earlier, it gave me the warning that my bpatch isn't in the search path, though it loaded OK. Then when I changed the argument, it gave me the error-loading message.

I put them into the search path by adding my folder in File Preferences, and the argument problem was solved---change them in the Inspector, they update right away.

I got a similar thing, though it didn't ask to quit/reload, it gave me "error loading bpatcher". Also earlier, it gave me the warning  that my bpatch isn't in the search path, though it loaded OK. Then when I changed the argument, it gave me the error-loading message.

I put them into the search path by adding my folder in File Preferences, and the argument problem was solved---change them in the Inspector, they update right away.


edit: when I embedded the bpatcher into the parent, I then got the error you mentioned. So, maybe it needs to be an external file to update right away...?

here's a basic main patch and a bpatch for testing dynamic args:

will re-check, but I am pretty sure my b-patchers are in the search-path (they all are in a folder "BPatchers" which is in the search path)

will re-check, but it happens so far with all my max5-native (so to speak) b-patchers, not with the max4-native, never saved as max-5, but still used in max5

will re-check, but I am pretty sure my b-patchers are in the search-path (they all are in a folder "BPatchers" which is in the search path)
will re-check, but it happens so far with all my max5-native (so to speak) b-patchers, not with the max4-native, never saved as max-5, but still used in max5

Arguments to B-patcher (Max 4 5 6)