MIDI Communication

Hi, it's a neat idea what you've done. to me as long as that same faders that is linked to midi is being manipulated in the Show screen, it SHOULD also trigger the midi.... have you verified that the same exact fader is linked to the show page? 

Hey, thanks for your answer.

sadly yes, it is connected correctly, when i move the fader on the ipad, the fixture-fader is also moving, but the Midi doesn react.

The other way round - so moving the fixture-fader - the fader on the ipad is moving and the midi does react and everything is working properly...

So in my perception, it is a bug, because i cant figure out, how to make it work and i also doens't see the use of this one-way-connection.

Greets Tobi

Hi, so in Preferences > MIDI, is your MIDI device chosen and active for both MIDI in and out?

Hey, yes it is, i think outherwise the direct connection via the fixture-fader wouldn't work...

it works properly when i use the fixture fader, only when i use the ipad (show) fader, the midi doesn't react...

hey, is there a chance, that somebody tryes if that is a general bug or something in my system...

An is somebody of ADJ reading this and probably debugging it, or do i have to contact ADJ directly?

I just don't know how to handle this problem right now

thank you very much and greetings from germany

Tobi

Hi, i do apologize for the delay, we are still looking into this. i should know more in the next few days.

Hey,

thank you for your answer and your help!

No pressure, I'm already happy, that somebody is interested in finding a solution.

Greets Tobi

Hi, can you attach a copy of your .DVC show file? and record a small video of how you've set this up and showing it not working? That would be great as the devs and I are trying to reproduce this same error but it works for us when we try it.

Hey,

thank you for your help. Attached you find a short video clicking through the setup and showing my issue and the dvc-file

Hi Tobi, the developers looked at your show file and the video and i believe have reproduced the issue on their end. but now they will be digging in and trying to find the cause, and I cannot give a timeline for when we will have an answer and a fix. I will keep you posted.

Hey,

thank you for your engagement. If you need anything else from me, let me know.

Hey,

any news from the bug-fixing?

Looking forward to have a smooth running system ;-)

Greets Tobi

Hi Tobi, i'm sorry but we still do not have a precise timeline on a fix for this.

Ok, so the priority of this bug is pretty low?

Do you got an idea for an workaround until there is a bugfix?

Otherwise, I perhaps have to find a different solution, probably with a different system...

Is there a way to higher the priority of this fix? Like an official mail to ADJ?

Hi Tobi, it seems to me from the reply I got from my contact of the developers that they could try but need to do more testing, "I am also able to replicate the same behaviour in MyDMX 3 but I am not sure if it is a bug or just a consequence of how the software is designed. For this reason, I'm unable to say with any certainty whether we can implement this change or not."

So I do not currently know the priority of this issue that only you've found. I will ask for a update and can update you when I hear back but it very well could be i don't hear back until after the 4th of July holiday for us in the states, we will be closed July 4th & 5th, returning to work on Monday July 8th.
Lastly, my name is James, and I work for ADJ as the Controller division tech support.

Hi James,

thanks for your response.

Ah ok, so "the was it is deigned" is probably, that the main use of Midi in that software is to receive Midi-Trigger and not to send Midi-Trigger?

So perhaps i have to redesigne my setup and trigger everything from any Midi-App on the ipad and use MyDMX3 only as an receiver and not as the center of the system.

Let me know, when you got an response

Thank you!

Hi, i received a reply this morning saying it is something that will take a while to look into properly, we have no timeline for this.

Hi James,

thanks for the response, then I will have to figure out an other solution, till you were able to fix this bug...

I understand, and I apologize for the delay in finding a resolution.