sleeplesswaves

I'm trying to set the display_range for live.gain~ like this:

message

live.gain~

But the range isn't changing... What am I missing? I'm actually trying to set the display range dynamically with "display_range -70. $1" with an incoming float.

This is driving me nuts, somebody throw me a line... lol

But the range isn't changing... What am I missing? I'm actually trying to set the display range dynamically with "display_range -70. $1" with an incoming float.
This is driving me nuts, somebody throw me a line... lol

I'm trying to set the display_range for live.gain~ like this:
 
But the range isn't changing... What am I missing? I'm actually trying to se

live-gain~-display_range-not-working

you have to open inspector and set range to -70 -20.

this is what default values look like in stored patch:

"saved_attribute_attributes" :                     {

                        "valueof" :                         {

                            "parameter_longname" : "live.gain~",

                            "parameter_mmax" : 6.0,

                            "parameter_mmin" : -70.0,

                            "parameter_shortname" : "live.gain~",

                            "parameter_type" : 0,

                            "parameter_unitstyle" : 4

                        }

not available as attrui parameters, and so one can't change them using messages.

you have to open inspector and set range to -70 -20.
then you can set display range.
and untick live mode
this is what default values look like in stored patch:


"saved_attribute_attributes" : 					{
						"valueof" : 						{
							"parameter_longname" : "live.gain~",
							"parameter_mmax" : 6.0,
							"parameter_mmin" : -70.0,
							"parameter_shortname" : "live.gain~",
							"parameter_type" : 0,
							"parameter_unitstyle" : 4
						}

Thank you! Is there a good alternative to live.gain~ for mixer style levels control? I'm diving back into max after a long hiatus so may be missing the new and shiny. At any rate, thanks for your help. Here are some screen caps of what I've built. It takes a bunch of inputs and automates panning in surround sound monitor setups.

Screen Shot 2021-11-20 at 8.28.42 AM.png

Screen Shot 2021-11-20 at 8.28.39 AM.png

Screen Shot 2021-11-20 at 8.28.35 AM.png

Thank you! Is there a good alternative to live.gain~ for mixer style levels control? I'm diving back into max after a long hiatus so may be missing the new and shiny. At any rate, thanks for your help. Here are some screen caps of what I've built. It takes a bunch of inputs and automates panning in surround sound monitor setups.
Cheers


I can't tell from the screenshots what your needs are.

I use matrix~ for any kind of volume - pan control.

Not only because it is so flexible, but also because it has ramp time built in.

I can't tell from the screenshots what your needs are.
I use matrix~ for any kind of volume - pan control.
Not only because it is so flexible, but also because it has ramp time built in.


simple question, simple advise: if you dont like a factory object, build your own.

gain is [*~ ]. everything else around it is your free choice.


simple question, simple advise: if you dont like a factory object, build your own.

gain is [*~ ]. everything else around it is your free choice.


I'll check out matrix~ I'm using vbap~ for panning across multiple monitors. Right now the patch can switch between 3-10 monitor panning with a separate LFE monitor. The panning is per track/input. I have 24 inputs coming in from my external mixer or Abelton Live, and I have 18 tracks that load sound samples. I've used this for immersive sound installations in the past, but I'm revisiting it and the inputs for a live music setup in surround sound.

I was working on that last screen capture that looks the most like a mixer. I was really just making that view to have an overview of what's going on levels wise... It's all working fine now. The whole patch can get a bit sluggish if I really try and run sound samples on all 18 tracks and many inputs... But I have tons of graphics going on... I really need to sit down and try and optimize and eliminate any bloat... But it seems so daunting at this point... hahaha

So for now I'm happy enough with how things are running. It's very functional!

@Roman Yes! I would love to dive into making my own objects... It's just TIME......... I've already put in like a whole week revising this patch... lol... I wish I were 20 again with limitless hours in the day to pour into creative things... :-)

Thanks for all the input & help... Most appreciated!

@source
I'll check out matrix~ I'm using vbap~ for panning across multiple monitors. Right now the patch can switch between 3-10 monitor panning with a separate LFE monitor. The panning is per track/input. I have 24 inputs coming in from my external mixer or Abelton Live, and I have 18 tracks that load sound samples. I've used this for immersive sound installations in the past, but I'm revisiting it and the inputs for a live music setup in surround sound.
I was working on that last screen capture that looks the most like a mixer. I was really just making that view to have an overview of what's going on levels wise... It's all working fine now. The whole patch can get a bit sluggish if I really try and run sound samples on all 18 tracks and many inputs... But I have tons of graphics going on... I really need to sit down and try and optimize and eliminate any bloat... But it seems so daunting at this point... hahaha
So for now I'm happy enough with how things are running. It's very functional!

I did not know that you really need level meter included.

I guess (but am not sure) that live.gain~ would be more efficient than

using separate objects for the level control and level meter.

Max can be slugish when displaying many items on the screen.

What I would remove in first place is spectroscope~ from all track input sections.

I did not know that you really need level meter included.
I guess (but am not sure) that live.gain~ would be more efficient than
using separate objects for the level control and level meter.
Max can be slugish when displaying many items on the screen.
What I would remove in first place is spectroscope~  from all track input sections.



live.gain~ display_range not working?