
Hi!
The above replies are all very valid; and good overal practices. However, it is an active conversation that we have within the team that a overal volume slider / with an option to turn off the volume completely + a meter would be lovely.

@wjmackwood there should be control in the audio midi settings section of pax that will let you adjust the output. However ideally I would make a line up track at -20db FS and have a scene within isadora that plays this. Then you can calibrate whatever the output chain is to this. If you are going to to a mixing desk you should be able to alter the input gain so that the -20 output reads at -20 on the input of the desk. If it seems really loud in the path I would suspect that you might be sending a balanced output to an unbalanced input which will give you a substantial increase in volume.
With the controls greyed out it suggests that your pathway might be digital? If so whatever is receiving the signal might have some adjustment that needs lining up.
Do other signals going into whatever your amplification/output system is also come through very loud?
Hello John,
Thank you for your response. The main volume on my MOTU has no effect on the speaker volume. I can run it to -infinity and the volume is still outrageous. The individual channel assignments in the 'sound player' seems to be the only way I have to control volume . . . well and the 'sound player' master volume which I currently have at 3.5%. I'm not sure what the difference is in our setups. Hmmmm.
w

@wjmackwood Hi- I use a similar system. As far as I can tell the audio coming out of Isadora is standard line-level. I adjust the overall volume using the "main" volume knob on the front of the MOTU. Right now with my M1 MacBookPro, I have the MOTU at -15db setting and with my speakers (QSC10), that's a good volume to work with. It depends on the speaker what the final level is. Perhaps that helps a bit. - John
Hello Troikatronix team,
I’m using the ‘sound player’ actor with a MOTU Ultralite MK3 Hybrid. The updated version of the actor allows me to set an output to individual channels with specific levels. Fantastic!
The problem I’m having is the overall volume. I have to run the level on the sound player actor at 5% or less. In other words, as the actor feeds directly to the MOTU, there seems to be no way to set an overall output level in Isadora so the actor can run at a reasonably normal volume . . . and because the signal is so hot, I run the risk of damaging my speakers if I’m not super careful.
The Mac Studio Audio settings has the volume control to the MOTU grey-out, assuming it will be set by the program using it. Am I missing something? Is there another setting that would allow me to control an overall output volume from Isadora to the MOTU (in settings or elsewhere)?
Any suggestions would be appreciated.
William
Isadora: 4.0.2 (arm)
Chip: Mac Studio M2 Max
Mac OS: Sequoia 15.1.1 (24B91)

/* TT Kaleidoscope - Fragment Shader version v1.1 Created for Isadora by Mark Coniglio Updated for Speed Change and Reverse Mode */ // ISADORA_PLUGIN_NAME("TT Kaleidoscope") // ISADORA_PLUGIN_DESC("The classic kaleidoscope effect.") // ISADORA_INT_PARAM(divisions, divs, 1, 100, 5, "Number of divisions in the kaleidoscope."); uniform int divisions; // ISADORA_FLOAT_PARAM(src_horz, srcx, -100.0, 100.0, 0.0, "Horizontal offset when sampling the source image."); uniform float src_horz; // ISADORA_FLOAT_PARAM(src_vert, srcy, -100.0, 100.0, 0.0, "Vertical offset when sampling the source image."); uniform float src_vert; // ISADORA_FLOAT_PARAM(src_rotation, srcr, -180.0, 180.0, 0.0, "Rotation when sampling the source image."); uniform float src_rotation; // ISADORA_FLOAT_PARAM(out_horz, outx, -100.0, 100.0, 0.0, "Horizontal offset of the output."); uniform float out_horz; // ISADORA_FLOAT_PARAM(out_vert, outy, -100.0, 100.0, 0.0, "Vertical offset of the output."); uniform float out_vert; // ISADORA_FLOAT_PARAM(out_rotation, rot, 0, +360, 0.0, "Rotation of the output degrees."); uniform float out_rotation; // ISADORA_FLOAT_PARAM(speed, spd, 0.0, 10000.0, 1.0, "Speed multiplier for time progression."); uniform float speed; // ISADORA_INT_PARAM(reverse, rev, 0, 1, 0, "Enable reverse mode."); uniform int reverse; uniform float time; uniform vec2 resolution; uniform sampler2D tex0; const float PI = 3.14159265359; int integer_modulo(float a, float b) { // mod = a - b * floor(a/b) float m = mod(a, b); return int(m + 0.5); } void main() { float adjustedTime = time * speed; if (reverse == 1) { adjustedTime = -adjustedTime; } if (divisions > 1) { // map to range -0.5 to 0.5, accounting for the aspect ratio float aspect = resolution.x / resolution.y; vec2 c; c.x = (gl_TexCoord[0].x - 0.5 + out_horz / 100.0) * aspect; c.y = (gl_TexCoord[0].y - 0.5 + out_vert / 100.0);// apply time-based rotation float dynamicRotation = radians(adjustedTime) + radians(out_rotation); // convert from cartesian to polar coordinates float phi = abs(atan(c.y, c.x) + dynamicRotation); float r = length(c); float angleFrac = (2.0 * PI) / float(2 * divisions); int count = int(phi / angleFrac); phi = mod(phi, angleFrac); if (integer_modulo(float(count), 2.0) == 1) { phi = angleFrac - phi; } // from polar coordinates to cartesian float x = r * cos(phi + radians(src_rotation)); float y = r * sin(phi + radians(src_rotation)); // map back to range 0.0 to 1.0, accounting for the aspect ratio vec2 cc = vec2((x + src_horz / 100.0) / aspect, y + src_vert / 100.0) + 0.5; // set the output color gl_FragColor = texture2D(tex0, cc); } else { gl_FragColor = texture2D(tex0, gl_TexCoord[0].xy); }
}
Hello Troikatronix,
I use the 2D slider to move and record the position of my moving lights. Right now I use the limit/scale value actor to move the lights proportionally to my studio, but because I use "show value of linked properties" the value coming back from the 'record file' does not reflect the actual position of the moving light.
I'm wondering if there is a 2D slider that allows you to input a separate min/max for the X and Y. This would be very helpful.
William
Isadora: 4.0.2 (arm)
Chip: Mac Studio M2 Max
Mac OS: Sequoia 15.1.1 (24B91)

Hello, a very good and free solution for me is node-red. It runs on any platform, including Raspberry Pi, you can easely make an interface running on any navigator and it use perfectly OSC on a nodal, javascript and json ready platform.
Have a look,
Jacques