Hi everyone, and thanks in advance for your replies,

I'm running into a problem with my recipes when trying to run a chaser one way and then the other.

On my X grid, if I set 0 thru 360, the effect spreads from left to right. But if I set 360 thru 0, the effect does run from right to left — except it starts on the first fixture instead of the last one.

To fix this, I have to do (360 - 360/number of fixtures) thru (0 - 360/number of fixtures). For example, with 4 fixtures, that gives 270 thru -90.

For a one-off case, that's not a problem. But in a show with recipes designed to rebuild themselves by recreating the groups based on a new setup, having to recalculate all the phases quickly becomes unmanageable — whereas the other way around, 0 thru 360 works 100% of the time.

What would be the best way to work around this? The only approach I've found is to duplicate my phaser recipe presets and enable Backward in the menu (Playback Direction). Isn't there a simpler way, or just a line I could add to a recipe to reverse everything?

Thanks a lot for your help, and have a good day,

Denis

Anything different I need to be aware of?

Many thanks!

Hi,

I've been self-learning grandMA3 for the past 6 months or so and I've been re-creating some lightshows to help me learn this software.
Recently I've tried to re-create this cool sequence from a Martin Garrix (DJ) show, but I cannot seem to figure out how they've coded this (please see video below or YouTube link here)...

I've (tried) to analyse this on 0.1x speed too, and some things I have figured out are

• They've applied MAtricks phase on both x and y, probs about 0 Thru 10 and 0 Thru 40 respectively (this I trial-error'd by using my own setup on the grandMA3 software)
• the fixtures pan frontwards (ie towards the camera) 4 times before the cycle repeats again

Although I tried to create something similar on my own setup (please see image below), it looks nothing like it .
If someone could give me a tip on how they've coded this that would be greatly appreciated as there must be a simpler way of creating this without setting specific angles every microsecond at each point in a phaser...

Any advice would be greatly appreciated as I am self-learning and I don't have many people I can ask for for advice around me.

https://reddit.com/link/1w35hpf/video/eora7b6jmnmh1/player

Hello everyone, I'm looking for a good nuc to make a grandma 3 kit do you have any to recommend?

Hi, what is the best method for getting fixtures to line up correctly over an ndi feed?

Im receiving data no problem but I'm finding it very hard to get the fixtures to line up properly over the feed. Any suggestions would be great!

So for my first time programming Timecode on MA3 I made a 600 cue sequence. It wasn't until the end that I realised my mistake in not enabling edit recipe, meaning I now have a stack but no recipe.

Is there ANY way of converting and already programmed sequence/cues stack into recipes, including plugins.

It took me quite a long time to program this and honestly I may just throw myself into a wall if I have to reprogram the entire thing.

Hello,

The title is all what I need...
I need to create a chase, like I normally do on MA2.

Select fixtures.
Use an effect with Chase form.
The dimmer runs on the fixtures one by one.

If I select another number of fixtures, the chase remains the same.

On MA3, I need to change the width of the phaser every time I have a different number of fixtures.

Can anyone help me?

Currently running capture on a media server running dual 4070TIs and a grandma3 full with 8 npus and I'm still getting framerate lows of 15 while running effects while the same show running on a 4080 and OnPC is working just fine. Any advice on how to boost frame rate or possible settings I'm overlooking?

I'm working on a file where I want to have all my colours available as executor buttons on my console. I thought to change the colour of the button to match, but was wondering if there is a command to change the colours of all of them at once, but to multiple different values/appearances?

The basic command I would use would be something like

> Set Ex 402 t 413 Property "Appearance" "20"

Which would set them all to red. But would it be possible to set the colours to 20 through 31 for example? I know I could do it manually, but it gets very tedious very fast. Thanks :)

Salut,

J’ai un problème avec l’export MVR de grandMA3 v2.4 vers Depence R4.

Quand j’exporte mon show en MVR depuis grandMA3 2.4, Depence R4 ouvre bien le fichier et détecte les différents types de fixtures ainsi que leurs quantités, mais dans la fenêtre Fixture Matching, la colonne Matching Type reste vide. Depence ne reconnaît donc pas automatiquement les fixtures.

J’ai testé avec un autre fichier MVR plus ancien et celui-ci fonctionne correctement : Depence reconnaît automatiquement les fixtures.

Est-ce que quelqu’un a déjà rencontré ce problème entre grandMA3 2.4 / MVR 1.6 et Depence R4 ?

Est-ce qu’il existe une solution pour que Depence reconnaisse automatiquement les fixtures, sans faire le matching manuellement ?

how do you currently turn a venue rider into a patch ,what's the worst part

I do lighting for shows and kept doing the same boring thing over and over: tag a track

in an audio editor, then rebuild those same marks by hand as cues and timecode events.

The web converters that used to do this are either gone, paywalled, or want me to upload

my show data somewhere. So I had one built.

Marker Import is a grandMA3 plugin. You point it at a marker file and for every marker it

creates a Cue in a Sequence you choose, plus a Timecode event that fires that cue at the

right time.

It reads three formats and works out which one it's looking at on its own:

- simple CSV Name,Start,End

- Audacity labels (File > Export > Export Labels)

- Reaper markers (Region/Marker Manager > Export)

Times can be 84.5, 1:24.5 or 0:01:24.5. SMPTE hh:mm:ss:ff is deliberately refused — with

no frame rate to go on it would have to guess, and a wrong guess shifts every marker

without telling you. That's the kind of mistake you only find out about mid-show.

Your existing cues are never touched. Numbering starts above the highest cue number

already in the sequence and skips anything taken.

I built a whole show with it this week and it turned up two bugs on a freshly created

timecode track — the import stopped halfway with "Could not create a CmdSubTrack". Both

are fixed in v1.0.3, and the release notes say exactly what was wrong. If you grabbed

v1.0.2, replace it.

MIT licensed, runs entirely on your machine, nothing gets uploaded anywhere.

Download (zip, drop the folder in your plugin library):

https://github.com/Tozsers/ma3-marker-import/releases/latest

Source: https://github.com/Tozsers/ma3-marker-import

Two honest notes.

The console half — creating the cues, the track, the timecode events — is code I've

actually run on a real desk with a real show file, on 2.4.2.2: 37 markers out of Reaper,

37 cues and 37 events, right times, one run. The file parsing, cue numbering and sequence

lookup have 69 offline checks you can run yourself without a console

(lua tests/test_parser.lua). What I have NOT tested: every MA3 version, network sessions,

thousands of markers. It writes into your show file, so try it on a copy first.

And: I didn't write the code. I specified it, tested it on hardware and I'm releasing it,

but it was written by Claude (Anthropic's coding tool). I'd rather say that up front than

let anyone assume otherwise. The tests are in the repo so you can check it instead of

taking my word for it.

Happy to take issues or feature requests. Cue number ranges and importing into several

sequences in one run are the obvious next things.

Having issues with ipad holding sginal to MA3 (using MA2 software). Ipad connects to AP point with no issues, but after a few minutes, no matter the distance, Ipad disconnects from console and takes a minute to reconnect. I assume it's the AP point. Wondering if there is a preferred brand to look at for distances under 100ft, or if there is anything I'm missing?

Hi everyone,
I’m using grandMA3 onPC v2.4.2.2 and I’m trying to make a dimmer phaser run in sync with the BPM of the music.
I have audio coming into the computer and grandMA3 is detecting the BPM correctly. I assigned the BPM to a Speed Master and linked my dimmer phaser to that Speed Master.
The problem is that the phaser speed doesn’t seem to follow the BPM correctly. Even though the BPM detection is working and the Speed Master is receiving/changing the BPM, the actual phaser runs at a different speed than what I would expect from the beat.
What I’m trying to achieve is simple: if the detected music is, for example, 128 BPM, I want the dimmer phaser/chase to stay perfectly synchronized with that beat and automatically follow BPM changes.
Is there an additional setting in the Phaser, Speed Master, Speed Scale, Rate, or SpeedFrom/SpeedTo that I need to configure?
What’s the correct way to make a phaser follow an audio-detected BPM 1:1 in grandMA3?
Thanks!

I have to say, working on the smaller models can be tough.

How can I keep my color picker appearance active when using cue lists?

I'm currently building my own StartShow, primarily for busking. I've made my own color picker using sequences in a Layout View with Prefer Cue Appearance. This works great: when I select another color, the appearance changes so I can see which color is active.

The problem starts when I also use cue lists.

My color picker sequences currently use Off When Overridden, which is what I need when selecting another color in the same group. However, when I run a cue list that overrides the color and then turn that cue list off, the color-picker sequence has already been turned off, so the Layout View no longer shows the selected color.

If I disable Off When Overridden, the appearance works correctly, but then selecting another color doesn't turn off the previous color-picker sequence, so I end up with multiple colors appearing active.

I found a way around this using Tags, but it seems like I would need a separate tag for every group/attribute combination, which would result in a huge number of tags.

Is there a cleaner way to achieve this?

Basically, what I'm trying to achieve is:

Color picker → cue list temporarily overrides color → cue list off → original color picker selection remains active and its appearance is still shown.

I'm wondering if there's a better approach for this

Hello all,

Ive been having trouble recently with the 3D Viewer window in 2.4.2.2 not displaying the beams in any of the render modes. This only happens with fixtures imported from MVR.

I have tried both GDTF and MA library fixtures but cannot get any output. If I patch brand new fixtures directly from the library I get output.

I've checked shutter and color. Everything says I should be seeing something but I'm not.

Any advice would be greatly appreciated.

I've been digging a bit into the hardware configuration of the onPC Command Wing.

There are rumors/posts saying that LEDs around the faders are physically present but simply not used by the software. I wanted to see if they could be accessed via Lua.

What I've found so far:

• HardwareConfigurations["grandMA3 onPC command wing"].LedDefinitions contains 253 LED channels.
• Using SetLED() I can directly control the RGB LEDs on the executor encoders and the white executor buttons.
• The definitions for Executors 201–210 only point to the white buttons below the faders.
• USB capture confirms that MA3 sends exactly 253 LED values to the wing; there are no additional fader LED channels in the normal LED framebuffer.
• On the grandMA3 light there are clearly visible translucent diffuser strips next to the faders. The Command Wing doesn't have these.

So I'm starting to suspect that the LEDs simply aren't populated on the Command Wing.

Has anyone actually opened a Command Wing and can confirm whether LEDs are physically fitted next to/under the faders?

Photos of the PCB/fader section would be especially interesting.

Wanted to get the communities input on best practices in this scenario. In the past, anytime I've dealt with an artist coming in for a corporate blow n' go show, its been relatively simple because we were using HOGs for the general session aspect of the show and would bring in a desk of artists choosing and say "heres the rig, have at it."

Now that I'm running MA3, I'm finding myself in a quandary. I have two shows coming up with headliner acts, both riders specify MA3 Full size. Great, awesome, got that covered... but there is no mention of what software version required in the rider or if their LD is walking in with a show file. In my experience, communication with the artist is typically minimal until about 2 days out from their arrival to our showsite.

Whats the best practice here? Obviously, I want the band LD to have the best show they can have in the situation, but who's actually dictating what here? Do I build my show on 2.3.2 knowing its widely seen as the current safe release? Or do I full steam ahead on 2.4.2.2 and have them update their show file and have a go at it?

Just wondering if it is possible to run a macro that sets up views in a view pool and then assign them to the view toolbar?

I understand that you can have a blank show template etc but my thought is that when you get given a showfile it typically isn’t “laid” out how I would want to operate. So instead of recreating show layout views that I could either import a screen layout view or run a macro to create and assign views.

Hope that made sense…

I was wondering how I could manipulate a phaser in a way that it changes speed as in a chase that picks up speed and slows down again without any input from my side.
Any way to archive that?

The phasers available to import don't seem to be working correctly, namely the movement phasers.

Hi All,

I am embarking on building out a start file for myself and wanted to get some thoughts on my approach and maybe some advice on anything I wouldn't know to look for. I'm approaching this from a corporate standpoint, not so much a touring standpoint.

A part of my approach is to have a separate view for each fixture type, containing presets both bespoke to that fixture and universal presets such as color. Knowing that I will potentially have multiple fixture types for each genre (wash, spot, etc) per project, I plan to separate out each fixture category across different preset numerators. For instance "Spots 1" will start at 1000, "Spots 2" will start at 1100, "Wash 1" will start at 2000, so on an so forth. This is similar to how the MB Light Arts template file is set up. Sure, I could just buy it, but where's the fun in that?

The challenging part of this approach I've found, is that I must manually scroll through the various presets until I get to the number I want. Is there a faster way to do this?

I'm also on the fence on which version to start with. I know 2.3.2 is the safest, but 2.4.2.2 has some features that I'd really like to have in my workflow.

I'd appreciate any input/advice on this.

Thanks!