Hide poly~ instance number in title bar
I’m using poly~ to load a subpatch that only needs one instance. Is it possible to hide the instance number in the title bar so that when the user opens the window for the subpatch they only see the name of the subpatch "My Subpatcher" instead of "My Subpatcher (1)"? Thanks.
Why do you need to encapsulate in a poly~ just for one instance? If you need muting, there are other ways. I suppose maybe if you need to be able to release the DSP/CPU usage? Poly~’s parallelization doesn’t function (far as I know) with only one instance, IIRC it spreads instances across threads evenly.
I’m more curious than anything, though, hope you don’t take this as being snarky.
One option (which is how I tend to make my poly~ stuff work) is to make all controls external, and let the poly~ just handle heavy lifting DSP functions.
One great reason to use a single voice poly~ is for dynamic fx chains.
The main reason I’m doing it is so that the window will load faster when the user opens it. It was a suggestion I saw here on the forum to speed up the loading (especially the first time) of a complex window. The idea is to load it into a poly~ first. Then the window opens very quickly, even the first time it is called.
Ah right! I always forget that poly can swap out the patch it has loaded dynamically, now. I’ll have to toy with that functionality one of these days…
As to the original question, then: Hide your controls in a subpatch within the poly~ object, and have users open that – not sure how your interface is designed, but subpatchers within poly~ instances do not inherit the instance number in the title. They also handle the Patcher Inspector ‘title’ variable correctly.
Load this in a poly and you’ll see what I mean:
----------begin_max5_patcher---------- 455.3ocoTssbaCBD8YzWACO6jQV1ooISeoeGY53AjV6tsHPCB43oYx+dgEIK Ts6kz7hzvY28vYWNvKELgxdB5E7G4OwYrWJXLBJBvFWyDsxS0ZYOkln111BF uXUJlGN4I7OcC+YTq4JfajsPCWos1N9Pm0vscfAMGlpQiFn1NXnBqFAwFhFq 5a2rYJw8ViORFE4yNTpmhzI80eMP4NGT6Sxey82ca4JdUE8a8ckwea1daI+K Yz0i+fnacUHbB1LzhFM3o9a8LncvOgVFAesnH9Y0+3fx.OGZlKlSc79AEIew kc95+qNu59xrN+COPKJeiMd40a77cEbis6X+FHF0vQv0iVS1viIl0V5X3gsj x1RK19wLsElhGz15uCMYaGSz.6eKbDMXy4SYr3yxLQSmC5ClXoeT346qbP62 c8I1x36k0vus3qd3wDGbXi0DEwhJivSa2SAuaxAmqaJCir6JE6sVsR5Nh8nR CKNGBNToAakdviI8TUdtNrsygoKgybg9DEB55qHinomIl0T7d7YPBKb6H4W5 kGglcAKc3PYmz6cnZvmRN2+7dGm+gP+sSxfqSI0i95ybrf4KTzux0XOm83PX N7ZwOwWsFwO -----------end_max5_patcher-----------
"patcher window name"
Hmmmmmm, perhaps my little hack above won’t work, then. My main tool that I’ve made in Max has about 6 windows to load, and it takes a while before they become active and switch themselves to presentation mode. My current workaround is to have a picture file that says "Loading" – it only displays in patching mode, and the windows are sized to only display that object (it keeps to itself, in the upper left corner of all my subpatchers) until they’ve fully loaded, at which point they swap to presentation mode, and resize themselves (via thispatcher) to fit the interface.
Roman — One of my quick tests a minute ago was with thispatcher loaded into a poly~ – doesn’t seem to affect anything when used in a poly instance.
Thanks, I’ll give that a go!
|MuShoo wrote on Fri, 31 July 2009 03:37|
|Roman — One of my quick tests a minute ago was with thispatcher loaded into a poly~ – doesn’t seem to affect anything when used in a poly instance.|
it should rename the window, just tried it in OS9 and
OSX max4 and max5 – but right, the instance number of
course does not go, just the filename.
Yeah, I tried the patcher "this name" message to thispatcher and I still get the instance number. If I can’t get rid of it, it’s not a huge deal, but it would be nice…
|bkshepard wrote on Thu, 30 July 2009 23:20|
|Yeah, I tried the patcher "this name" message to thispatcher and I still get the instance number. If I can’t get rid of it, it’s not a huge deal, but it would be nice…|
Well, you could give it a name that begins with "(1) ". It won’t get rid of the instance number, but at least it will be symmetrical.
one could make another good use of it.
in a situation where you have some modular effects in a big
program, you might want to layout them as [poly foo 32] even
though you dont plan to run more than one voice per poly~.
you could now use the "open 3" feature to get a nice window
name called "delay (3)" when this is the third instance of
a "delay" mopdule opened in your program.
----------begin_max5_patcher---------- 1212.3ocyYsrbaaCEcszWAJyhNSGGOffj5Q6ptpMaxLccbFMThvxHkDfCIji S8j7sWP.RQBRPvGQV1aHsvy68bw4buD94kKb1ydBm6.9cvm.KV77xEKjMUzv hxeuvII7oCwg4xg4Pweks+KN2n5hiehKaNMje3AbF3C6dH7Q7tvczvDb0nhI T7A1IpbnnxFkyfPOtKCefqrfMnag2.PnUEu78cKd456eKD74xIQhj6lvBdua P0xeOixkaWQW+YFILtpG5oDBMFykltacirS71sVrH4j+StHqfhcV0rZj7ukh UlnSN4HUrAmsnRGuDwJgLwxQhwOhyxILZicYgSsy5hBj92psEuV4CkN8FXs2 JBEGiYG9WrzogUMFgueZqBKESqmgbDZOzGIgllgywTdHuz3atygmh46ZhUtn aM1+8gGv8NYiQqENGyHQLZgQnMyhlq1NgGqb3fl1sbDzvTCSlyXw6CydjjS1 Gi0hEhC5gTRRHGyIJ6AAOOORRZFQchE1XB0jkFQaMRiV6sHOGXIIBjsxg0XP 247APdJINFGIdy3fLbBSbDBvnfjuAhXGuyo4DMQp5iX4BkfFZsjR4uV9qsaZ .gsHWqZtS8Gw5iiYfmAasfUAzhSrU878kKq9ialIBqIOoCvwrvnDbdNnRq5N mOx9J3uw+ZN3uXT7uniuFfQz5sJxlRmB5qd0OLht3vnaOvXCZnQYKgf00Ak4 OPxqzDsildvMJ4d4oQk.lMvz8hCln4Bl2HAzFCIWjzqry28wht0fAfyeT73c +SwSLMR0x0JhjNPbHPlGvEJe4gtMvdXX6alyzsREaJcrNj0aZ4omZt2zyyJE 8zRSOhT0iIc8forGYZaKotGW56ARgOPZ7ASk2W5byozachoCArS+CQD0Ii+1 OZ207XjsYk9sWV6wqNrST2NMyPGfkN.Ss43Nq5oq78yF.j9znAYEaTwPQA1w 30VQP3jPPSInaMjphEK1dmq.voLowe7byDftMVgNWqPGbl3ht9RQ4xCPzktZ w3rCZ4rSYGpBakmK.c89HbNmPOqL+oy7TCi8ARTTWQOYDhDkxDBWkl9LYPy0 y7mfms4EzyZzovM0K6JZmX2EmM2Ex4Yj8m3pvror+iLW1.cOlzphBC1GFWVL x40pytXLi6jSWurKpcApnrsN57zP0Jf2q2hCgip3P6hllEFt.HQGgwYJJpgE 9+jeC8PNa8kizQ4q1+MoKz.E5nGfZyw6QKvsy3LpCzuFf0n1Ts5si0p8eSY1 EzkQY2auflcYiUprCov973ubOKcMz8JZWM0nRpyjtixk0nf7oJ7MlqCWfFbQ vn+6z1yWdKQttqqteC8h40DEPy3hq6HJtOjdrrT6I5L8b29bf7Sxr3ikeTmW f5h6s5ivWrqsuNL2ETTeT4EDTROH14LVrEXAsQdAWtakWWXfmMXY0qBpbQQD BEfrcHQccoakWAsmUdPvqEXLVQu4qWzC1ILle.bsfdp5J7Qifg4cQPOncz65 CQDpcDZshroPHu01PHzqx4q1+mCmADJmqdAcJDscsEk3ZmZJBZVpPekAA0FT mZILWGQmf7XMoVamYaZ000jPuAgowD57tplzpwfRAWUSB8RaRhe78k++PuTe E -----------end_max5_patcher-----------
Well, doggoneit, that hides the instance number alright, but unfortunately, I’m back to the original problem of a slow load time. If I just open an instance of the poly~, the window opens almost instantly, but if I open a subpatcher within the poly~ instance, it takes as long as it did to open the window when it was just a basic subpatcher. I think I’ll live with the instance number. Thanks for all the tips, though!
Forums > MaxMSP