|
|
Aug 20, 2010 at 8:22pm
Stereo-gain attempt crashes Max
Hi!
I’ve tried to make a stereo-[gain~] where the two sliders always follows each other, by patching the Slider Value of the first [gain~] to Input of the other and vice versa (see below).
A touch on one of the sliders makes Max (5.1.4) crash.
1) Why is that?
2) Any suggestions on a stereo-gain’er? :-)
Copy all of the following text.Then, in Max, select New From Clipboard.
----------begin_max5_patcher----------
249.3ocoQEsZCCCC7Y6uBgeNaDm19x9UFkharIUiD4PrCzQo6au1NNsYiwnr
7h.e57o6jtvYhi1yFm.dCdGXrKbFKAEAX42LQm5bcqxknIZTH8knXpCpSX1i
e7R0LFM1YG8sFeheUFsev3LjW4QKcXvT6ml41MuVV.Ukw5bA1m+yjL9O6MSj
ENrgTshBPfTPfYd8Je8IjZVp6tnXxcOTWtcozAShzcOFwtx4wRwJWCx+dMrh
HI+uQJwPzhzOOzogDw+dNc1wg5Y+kOsf79bzFmGozgbAmPtgGd4Dp0lT6xLR
Gp6sgHls.r+W24OqijOgipVgiBOtxugrHf6R
-----------end_max5_patcher-----------
|
|
|
Aug 20, 2010 at 8:27pm
It’s because you’re creating a feedback loop/stack overflow. When you touch one of the sliders, you start an infinite loop going because they both feed into each other.
You can get around this by using the set message into gain~, like this:
Copy all of the following text.Then, in Max, select New From Clipboard.
----------begin_max5_patcher----------
249.3ocoQEsZCCCC7Y6uBgeNaDm19x9UFkharIUiD4PrCzQo6au1NNsYiwnr
7h.e57o6jtvYhi1yFm.dCdGXrKbFKAEAX42LQm5bcqxknIZTH8knXpCpSX1i
e7R0LFM1YG8sFeheUFsev3LjW4QKcXvT6ml41MuVV.Ukw5bA1m+yjL9O6MSj
ENrgTshBPfTPfYd8Je8IjZVp6tnXxcOTWtcozAShzcOFwtx4wRwJWCx+dMrh
HI+uQJwPzhzOOzogDw+dNc1wg5Y+kOsf79bzFmGozgbAmPtgGd4Dp0lT6xLR
Gp6sgHls.r+W24OqijOgipVgiBOtxugrHf6R
-----------end_max5_patcher-----------
|
|
|
Aug 20, 2010 at 8:37pm
He meant this.
Copy all of the following text.Then, in Max, select New From Clipboard.
----------begin_max5_patcher----------
399.3ocuTssaCBCC8Y3qHJOypHoPgt212wT0T.xnYBBHHUqaUce6KwA5s01A
cS8Eircv9bNwNabcvIUq4sXzinmQNNabcbfPl.Nc9N3R15zBVKbLrbUYBuA6
YSo8DxBtBxQ5BVyToKEx7WZ3oJasClMw2CQholOg9FKUaQK1WmpUp9BQ6hJx
fVVk71Cy563qURkjUxgLO0HXE8YrEP8QM21SrPpvdHbBSli20Iy+2J9DNCQC
GSzsttFi2Pk.96ZH02VEeMPRbcCulKyPsb0XkGhu+A5STvunOjepOA2f97uJ
J4Lg7qyxa5U3cLP0ovzQjcFY5nlKnWjcshbog714.zh6EmBlCTZpwNGrDZzX
nD4VnDTdbgPd51LfPS7i4Ya0plz9510UDYGHy3sJgjoDUxCNidIDsmHKEYYb
HseWjRQVckFZcP3BZ9PQTvQc67HhNNDQ7mOIzrZEC2KQQ1EsC8H1oP8MWn04
OxhgnqA2UckN.DQFGhn5mzMxkcElFYeM6XOvFFCmy+DYU6r08afur2G.
-----------end_max5_patcher-----------
|
|
|
Aug 20, 2010 at 8:40pm
haha, oops :) thanks Matt
|
|
|
Aug 20, 2010 at 9:28pm
Thanks a lot! Works! :-)
But usually a feedback loop/stack overflow doesn’t crash Max, does it?
|
|
|
Aug 20, 2010 at 9:33pm
In Max5 i’ve found that ‘non-infinite’ feedback loops (unlike your slider1 to slider2 to slider1 loop), for example something that depends on a metro or other timing object, does not crash Max; it merely pauses it and issues the stack overflow error. I haven’t crashed Max with something like your issue though (and obviously I’m not keen to try it)
Brendan
|
|
|
Aug 20, 2010 at 10:39pm
You shouldn’t crash, you should get a yellow warning bar along the top of the screen until you resume the schedular. Are you using the latest incremental?
|
|
|
Aug 21, 2010 at 11:53am
No yellow warning bar. It just crashes.
And yes, I’m using the newest (Max5_42462)…
|
|
|
Aug 21, 2010 at 6:58pm
it doesn’t crash for me either. You might also want to have a look to live.gain~ if you want to control a stereo signal.
|
|
|
Aug 23, 2010 at 11:35am
Thanx! I’ll check that one out. Are there any disadvantages in using these new live-objects (over the traditional Max-objects), with no live-connection in mind? …I’m thinking in terms of size (when building) or being heavier in use, because of live-communication-possibilities or something?
|
|
|
Aug 23, 2010 at 11:39am
Nothing that I can think of, those are just normal Max objects with enhanced functionalities to communicate with live in the MfL context.
|
|
|
Aug 25, 2010 at 7:22am
|
