phiol

I have 4 small requests on my wishlist that I believe would GREATLY speedup the workflow in Max.

1. The param (attributes/messages) window that you get when you right click on an object's left most inlet.

Well it would be great to have a the option to keep it opened and floating like for the floating color panel.

I know new users that want to start learning MaxJitter and one of there biggest holdbacks/fears is the fact the you have to remember so many @ttributes by heart.

how often do I still forget some in my jitter objects and wonder why something isn't working.

2. Could you please , please bring back the color panel option when right clinking on an object. Just like it was in Max5 & 6.

Presently you only have the option to do it with wires.

Right now we have cmd+f to search and match name. Imagine if we could just change on a context name to to a bunch/group of Jitter objects on the fly.

Just type in the new name in the search tab and boom all object automatically have this new name. Similar to the way [groove~ #1name]  works in abstractions and bpatchers or poly~.

4. Automatic number increment on object duplication:

Using a special key combo (say option + d) click on an object, slide aside to duplicate ,

but like magic there would be an increment value beside the name.

then you copy/paste Or duplicate these objects ; do a search for the word send (like mention in request #3), the object become yellow like they do presently,

then you select the one you wanna change; replace send to receive and boom. All are changed in one go. :-)

I really believe this would really cut patching time down by a big 1/3rd if not 1/2.

THe 2 biggest ones you 've done up to now are.

-please give us a object border option in preferences , pretty please :-).

Thanks a lot to all you guys for all the hard work.

I also dig the new forum look and font. Nice touch!

Hi great C74 team :-)
I have 4 small requests on my wishlist that I believe would GREATLY speedup the workflow in Max.
and help out new and old users. 

1. The param (attributes/messages) window that you get when you right click on an object's left most inlet.
Well it would be great to have a the option to keep it opened and floating like for the floating color panel.
I know new users that want to start learning MaxJitter and one of there biggest holdbacks/fears is the fact the you have to remember so many @ttributes by heart.
how often do  I still forget some in my jitter objects and wonder why something isn't working.

WORKFLOW SPEED
2. Could you please , please bring back the color panel option when right clinking on an object. Just like it was in Max5 & 6.
Presently you only have the option to do it with wires.

the most important one.
3.  A search replace option:
Right now we have cmd+f to search and match name. Imagine if  we could just change on a context name to to a bunch/group of Jitter objects on the fly.
Just type in the new name in the search tab and boom all object automatically have this new name. Similar to the way [groove~ #1name]  works in abstractions and bpatchers or poly~. 

4. Automatic number increment on object duplication:
Using a special key combo (say option + d) click on an object, slide aside to duplicate ,
but like magic there would be an increment value beside the name. 

then you copy/paste Or duplicate  these objects ;  do a search for the word send (like mention in request #3), the object become yellow like they do presently,
then you select the one you wanna change; replace send to receive and boom. All are changed in one go. :-) 

image how much time would be saved.
I really believe this would really cut patching time down by a big 1/3rd if not 1/2. 

-----
THe 2 biggest ones you 've done up to now are.
-Encapsulate 
-Presentation mode 

ps. one last little one while on it,
-please give us a object border option in preferences , pretty please :-). 

Thanks a lot to all you guys for all the hard work.
I also dig the new forum look and font. Nice touch! 

4-smalls-request-for-c74-to-facilate-speedup-patching-workflow

Why not just send the "name " message to the objects you want to rename? Does that not work?

>the most important one.
3. A search replace option:
Right now we have cmd+f to search and match name. Imagine if we could just change on a context name to to a bunch/group of Jitter objects on the fly.

Why not just send the "name " message to the objects you want to rename? Does that not work?


in this drawing context example, the message would be @drawto balbalb

And to be more specific, in my request, the ctx name would visually change in the object too. that way it would be saved with your patch.

mmmm. I'm not sure I get you.
in this drawing context example, the message would be @drawto balbalb 

but I think I'm not getting you right.
And to be more specific, in my request, the ctx name would visually change in the object too. that way it would be saved with your patch.


ah yeah, visually changing the things, that makes it trickier, I agree. But then it's also not like #1 at all anymore, so the usefulness decreases a bit, does it not?

This is for workflow while patching? Is there a special reason why you're shifting contexts around? I ask, because I don't personally do this, so I'm eager to sort of find out what the routine is :)

ah yeah, visually changing the things, that makes it trickier, I agree. But then it's also not like #1 at all anymore, so the usefulness decreases a bit, does it not? 

This is for workflow while patching? Is there a special reason why you're shifting contexts around? I ask, because I don't personally do this, so I'm eager to sort of find out what the routine is :)


It's a bit hard to explain but extremely simple @ the same time.

Sometimes when you're building large patches for a contract, and all of a sudden you are asked to duplicate a section

to to test and try and see if you want to keep, well you could just copy/paste

Of course you could tell me, well just create abstractions or bpatcher of your patchers.

that will be duplicated. This mostly (if not always happens) when you are working with a client that will say, ""mmm , could we see it like this"

With the search/replaces I could just say, "oh you mean this section and this section, multiple times.

Yup just give me 2 mins. Duplicate / change names/ Boom !"

It's a bit hard to explain but extremely simple @ the same time. 

Sometimes when you're building large patches for a contract, and all of a sudden you are asked to duplicate a section
to to test and try and see if you want to keep, well you could just copy/paste 

Of course you could tell me, well just create abstractions or bpatcher of your patchers.
I would go 'yeah but' 
that will be duplicated. This mostly (if not always happens) when you are working with a client that will say, ""mmm , could we see it like this" 

With the search/replaces I could just say, "oh you mean this section and this section, multiple times.
Yup just give me 2 mins. Duplicate / change names/ Boom !" 

i use multiple 'new view' with different unlock + zoom levels, presentation mode, to keep things like duplicating sections semi tidy for testing, etc. before bundling stuff up.

i was thinking drag and drop to copy paste between 'new view' windows of the same patch would be nice, like a painter's palette, toy box metaphor. keep the mess in one area of the max canvas far away.

I try to modularize VERY early on, so that I can quickly create clones, variations and weird offshoots these days. I only *just* got friendly with bpatchers, strangely, after using max for about 10 years, hehe. Oops.

4 smalls request for c74 (to facilate & speedup patching workflow)