127 midi note input

Hi @b52productions,

127 is the maximum number of notes defined by the midi standard...there is no workaround for this as we simply don't have more notes!

Cheers,
Lars

I'm sorry but this is a limitation of dot2, if you need more Midi Inputs then you could switch to its bigger sister.

Regarding the trigger for Execs on page two you could try the command: Goto Cue X Executor 2.Y

Hopefully this is helpful!

Cheers,
Lars

I'm working on using BOME to expand the functionality.

If you map everything in the 127 midi notes as a basic funtion, then use BOME to map different pages to send multiple notes, you may be able to expand the overall power of the APC20>BOME>dot2. These are "pages" in BOME, not in dot2.

Simple Example:
Assume you're using APC20's Track Selections to change "pages" within your BOME translator, which may just be setting a variable G = 1 or 2 or 3, etc

If G=1, then set things as basic function:
Clip Launch 1-8 are midi notes 1-8 change everything selected to Red, Orange, Yellow, Green, Blue, Violet, Pink
Clip Launch 9-12 are midi notes 9-12 are positions, High, Low, Mid, X, XX, Room, etc
Clip Launch 13-24 are midi notes 13-24 are selection groups 1, 2, 3, etc

To make group 1 move high and change red, in BOME page 1, you'd have to push C13, C9, C1.

But if Track Selection 2 is selected, set G=2 within BOME and have the following:
When G=2 have Clip 1 output notes 1, 9, 13, which would do it all in one button.

This idea doesn't exactly give you more functionality, but may be able to give you more capability or a macro-kind of function.

I haven't tried this, but thinking on it.

Process might be something like this for Clip Launch 1, I haven't worked through syntax yet.
Clip Selection 1:
If G=1
<Midi note 1 out>

If G=2
<Mid note 13 Midi note 9 Midi note 1 out>

If G=3
<other set of midi notes>

Track Selection 1 translator rule:
set G=1

Track Selection 2 translator rule:
set G=2

etc.

Just a thought.

Also, I'm not sure if there is anything in dot2 that is "terrible". You might chose better words when you have such a supportive group of guys like Michael, Lars, etc. responding to your questions daily.

Another idea that TVTM_Brian had was that maybe as you map the midi to an executor, you can set the "page" inside of the dot2 midi mapping to "current" instead of specifying. Then, if you change the dot2 page, maybe the midi note calls a different executor. I haven't tried this either.

Sorry to be so theoretical and not definitive in my posts. Hopefully these ideas inspire thought/progress. I have to find time to try everything that is in my head. dot2 is a hobby for me, so I don't always get to my ideas as quickly as I'd hope.

My APC40 arrives in two days, and the dot2 page idea will be one of the first things I try!

My software maps MIDI to Art-Net. As i know supports dot2 1.3 512 dmx input channels. in this case you get around that 127 limit.

Here is a video about my software:

Also benefit: you can remote the console over network.
use cases:
dj should do the lights or at the bar you need to adjust the room light.

You can use up to 14 midi events (two midi controllers) in the free version. The paid version is limited to 512 (1 universe) over as many midi controllers as you can connect.

Download at by message board:
https://quantendrehung.de/forum/viewforum.php?f=2

The free universe is for output out of the dot2. this affects only patched fixtures.
input is not limited in any way.

You need to assign your network adapter a valid Art-Net address like 10.0.0.2/255.0.0.0.

What does the system dialog show to you?

It's long ago, but how did you do it cause you say no bomac needed? Does it work with bome midi translator and when how ?

Greetings

bego

You can use Midimonster!

to translate anything to the MAweb backend.

The MAweb Backend can send Parameters (for example from mdiid devices to any playback fader/Button on your Console(Dot2 or GMA2)