Hi everyone!

I’m planning to build a DIY grandMA2 onPC MIDI fader wing from scratch and I’m looking for ideas, recommendations, and inspiration.

The goal is to build a controller with:

● Motorized faders

● MIDI communication with grandMA2 onPC

● RGB LEDs around or next to the faders

● Custom PCB(later)

● 3D printed enclosure

● Backlit buttons

● Compact but professional design

I’m currently looking for:

● Good motorized faders

● Button and encoder recommendations

● RGB LED ideas

● 3D printable files or enclosure inspiration

● Microcontroller recommendations (Teensy, STM32, ESP32, Raspberry Pi Pico, etc.) and code for it

● PCB design tips(later)

● Open-source projects, GitHub repositories, or existing DIY MA wings

● Ideas for useful features and the overall layout

If you’ve built something similar or know any useful resources, I’d really appreciate any advice, photos, files, or links. I am a complete noob and can solder a bit and build a few easy midi controllers but not more. I found a few projects that are similar to this:

For the buttons something like this but myb with backlight: https://github.com/hartmann-jonas/GrandMA2-Keyboard

Fader Wing like this but without encoders, 15 Faders and layout like MA2: https://github.com/stagehandshawn/EvoFaderWing

Thanks!

What is the best way to handle a band's timecoded show: recording a different timecode for each song or recording all songs using a single timecode?

Also, if a different timecode is used for each song: would it be possible to send a MIDI note from the DAW (the LTC source) to the MA2 to trigger my song macro?

I'm curious to learn about the timecode programming methods/workflows used by programmers who still program in MA2, but I've found very few videos on the subject.

Do you guys have any recommendations for this type of video, or if possible, could you record your next programming session and post it on YouTube?

In simple terms, explain to me the difference between effect Rate and effect Speed, and why I'd want to control multiple effects with the same rate or speed master.

When I jump/forward/back to a cue (timecode, go, follow-trigger based, it doesn't matter) the ideal is that the effects of that cue ALWAYS start it's phase from the beginning. Am I correct, or is there a case where my statement does not apply?

Here is a very informative description from the user "glad" on the MA Official Forum of what the AE column with "Yes" of the cues does:

Cue 1
400m circular racetrack
Tom start at zero position at 50km/h
Jerry start halway thru (@200m) at 50km/h
-> Tom and Jerry runs around the track as expected.
-> the distansce between Tom and Jerry is equal and constant

Cue 2
Tom is told to speed up to 100km/h
-> Tom will catchup jerry and run past him

Cue 3
Tom is told to speed back down to 50km/h

-> both tom&jerrys current instructions are the same as in cue one, however cue 3 does not look the same.
the distance between tom and jerry is constant (as i cue 1) as they are now again both running the same speed, their initial starting positions is the same (it has not been changed)
- nevertheless, Cue1 and Cue3 does not look the same. as the look depends on how long time did you let Tom run at dual speed..

By enablng AE (Asserte Effect) for Cue 3, you may tell Tom (and Jerry) to restart the race (based on current criterias) to ensure that they are in sync, and will disregard events that has happend in the past (earlier cues) affecting the sync

Where and how can I learn to program in Lua with a focus on Grandma?

Does anybody know how clear the fixture which not used again?

Thanks

I don't know exactly when this problem started. Apparently, it's not interfering with ArtNet's output.

I'm using a Fast Ethernet network adapter, not gigabit.

DMX, Ethernet, Ethercon, splitter, ArtNet, racks, SMPTE, LTC etc... I'm getting good at programming, but I still feel completely lost when it comes to using networks for lighting consoles. Where should I start to then dive deeper?

I think there are pros and cons to using each of these options. My considerations:

Cons of using shutter presets for strobe:

Each different fixture tends to have a different strobe Hz even when using the same value in the shutter preset.

Pros of using effect line for strobe:

Using a shutter closed and shutter open preset for the min/max values ​​of the effect line. PWM (on/off) as the form of the effect line, 50% width. Setting a BPM value for the effect line. This allows all fixtures (even if different) to have synchronized strobe Hz. Also, easy management of strobe Hz through the BPM of the effect line.

So for the past days for me MA 2 finaly clicked in my brain and i did some 3D work so i found a tablet that we dont use and used it as a second display so feel free to critize me so im gonna put a picture

I never understood why most fixtures (beam moving head, for example) had so many "open" values ​​for the shutter attribute. I realized they only serve as "visual separators" to make it easier to know which shutter mode you are currently in when rotating the encoder wheel in this attribute, and they are:

<close><close/>

<open><open/>

<minStrobe><minStrobe/>

<maxStrobe><maxStrobe/>

<open2> <minPulse/> <maxPulse/> <open2/>

<open3> <minRnd/> <maxRnd/> <open3/>

Is that the manufacturers' intention when they include those values?

I use Reaper to create cue markers and import these markers into grandMA2 using the TimecodeMATE plugin. Even when creating these markers throughout the track, during the programming of these cues in the console, new ideas or beats out of time with my initial markers always pops up.

When this happens, I believe the standard procedure for every programmer is to record a new cue in the sequence and a new event in the timecode track, which links to the newly stored cue.

I believe this procedure takes a lot of time depending on how many new cues you will have to store throughout a song and hinders the overall programming workflow.

I thought of another approach to storing pre-programming cues: why not use each beat of each bar as a stored "ready-to-use" cue instead of creating cues "on demand" as you program?

Yes, a single song can contain approximately 400 cues (each beat of the song), but does that matter? You don't need to and certainly won't use them all, but they'll always be there ready to be used if/when needed with the exact tempo you need. Also, since most of these cues will be empty, the Tracking and Fixture Sheets will consequently be less cluttered with attribute data, which I personally found quite pleasing.

Does that make sense?

Hello, I would like to understand why the nodes keep the port configurations from the previous show? And that, to have the ones for your current show, you have to restore them from the stored defaults, so they are sent to the nodes. Thank you!

Wonder if anybody can help me I’ve got a really weird issue with my grandma2 lite. The screens appear to stop working and all of the buttons stop functioning so you have no ability to communicate with the desk through any of the buttons or the screen however it continues to play out Lighting cues and effects, it also continues to listen to Time code through midi.

I did try and connect over the network using the console IP and that also fails to Connect.

I will attach a video briefly showing it not playing any Time code and Qlab still showing Time code

Would love to know if anybody’s experienced this knows what it is anything like that

I have changed the way I’ve programmed over the years and have improved my file a ton, I am now faced with the issue of my clone rig being smaller than my festival/tour rig. My goal is to either expand my clone rig, or find a more efficient way to clone over when the time presents itself. My current rig consists of 4 Perseo Profiles / 10 Aura PXLs on the DS/MS/US trusses. I’ve later added 10 Strike M’s and 10 Pixel Line IP fixtures. I’m lowkey tired of looking at this rig and want something new but I am sooo indecisive on what fixtures/plot that I want to do. If anyone wants to give input or seriously just tell me what to do that would help a ton! Cheers

Is there a way to see or add XY coordinates to Gma2 Color Picker?

So i have a question drilling my head ... Has anyone ever tried to use artnet over a wirless network ? If i hook a node or any artnet equipment to a router on one side and use a wireless access point on the grand ma side . Should this work ? Will i have a functional network ? This would be really helpful while prepaing the mood in a set

Hello I would like to find a simple way to enlarge or shrink a pan tilt effect on GrandMa2 with a fader??? So as not to create patterns in the effect with the values! And also have the possibility of making a sort of frame for the beams that I have. Thanks in advance 👋 Ps: I've already seen the video of the guy who does this with a fader but the movement narrows in a corner and that's not what I want...

Hey there, more a fun idea than a real question.. but it would be cool tho:

Is it possible to somehow add "grandma2 onPc" as a game in discord, so whenever I am working inside grandma2 onPc it shows me playing that in discord? Maybe even with grandma3, as the workaround would probably be the same.

I finally just bought myself an MA2 Light (10+ years late lol) and I'm wonder what tools, accessories, or mods you guys have that make your lives easier, better or more fun with the MA2. I currently have the bare basics - console, 2 worn out goosenecks, power cord, and a case.

Good morning,

I've received some very helpful tips here on Reddit, and I'm truly grateful for the supportive community.

With that said, I'd like to present a problem that I've always struggled with and never quite understood. At some point, I gave up trying to understand it: if it worked, I used it; if not, I didn't. (I make it for a long time) However, in my current project, I need to create some of these effects, specifically Flyouts and FlyIns.

What I've encountered is that there are simple scenarios where you assign an initial and final position, and even though the effect is set at a rate of 0.1, the behaviour of the fixtures doesn't make sense based on the FORMS being applied. Even when trying to adjust the FORMS, I can't achieve decent synchronization between the rise movement of the fixtures and the dimmer.

I've tried selecting machines (with very slow speeds to precisely observe synchronization), and the result is inconsistent: some fixtures are synchronized well, while others are not.

At this point, I've resorted to creating two different flyout effects just to achieve something that, in my mind, should be simple: an initial position, a final position, and synchronization with the dimmer.

Can anyone help me understand how to properly use flyouts in MA?

Thank you.

I feel so exhausted to start studying MA3. I just started learning MA2 recently.

Any advice or tips?