is there a creative way to get around this 127 limit as cues. faders. and exec buttons quickly add up over that?
i have enabled 8 pages on apc20 but cant trigger everything i want.
is there a creative way to get around this 127 limit as cues. faders. and exec buttons quickly add up over that?
i have enabled 8 pages on apc20 but cant trigger everything i want.
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
well that is terrible.
can we enable another input midi port and then enable another 127 notes in please? this is a big limitation.
how about triggering page 2 cues ??
i can add toggle pg 1 and 2.. note in triggers same exec but different cues...this doubles my cues without using more notes.
just cant trigger same cue on both pages. hmm
just tryn to map this apc20 as default as possible with full functions
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!
i set up pg 1 and 2 quickshow.. pages 3 thru 8 dot2
wasup on that analog in ???? can i bomes to serial port that ?
Display MoreAlso, 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.
im not saying that the group is terrible.. thats just a kill on functionality.. why have 10 pages of exec / faders etc and only have 1 midi channel in..
24 faders
bw1 and bw2 =96
f1 and f2 = another 32
thats a total input already 150 plus..
well i added page up and down.... and that gives me almost endless amount of options so there is the work around.
Dont forget WE are also providing content for this forum and our problems should be their concern and guide the development of the next version.
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.
yes thats exactly what i have done but i use bomes w another program... to enable more flexibility... esp when it come to routing the midi feedback from different pages/programs
and again as i always,,,, i say the support here is great and thats why im here.
@btodog i havent had to use the variables in bomes.. i initate the program like this...
on note xx"pg1" any value .. note out value 10
on note xx"pg2" any value -- note out value 20
on note xx"pg3" any value -- note out value 30 etc.. 8 pages etc
then when it cycles back thru with this value it selects the function of the pads..
on note in value 10 active by name "bw1 exec"
on note in value 20 activate by name "bw2 exec"
on note in value 30 activate by name "quickshow" laser software cues
on note in value 40 acitvate by name "resolume" video software
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
very interesting... as soon as i find time
i see it uses universe 9 but i only have the free universe as of now.. anyway to get this to work?
The free universe is for output out of the dot2. this affects only patched fixtures.
input is not limited in any way.
artn-net is enabled but adress is 0.0.0.0. and doesnt show up in converter
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?
for those following.. found the 127 limit workaround no bomac needed... thankyou guys for pushing me
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)