Midi Crash!!!

Microsoft Visual C++ Runtime Library

It gives you a Runtime Error!

C:\MyDMX\MyDMX2.exe

This application has requested the Runtime to terminate it in an unusual way.

Please contact....

I'm liking the midi control. If/When it works. But Now I've lost key control. All I get as an option is Midi or ipad app....

What happened to being able to use the key's.
Did that go out w/ the latest release?

-Eccentric

Is anyone running midi control that dosnt crash like mine is?

Was this fixed in the Aug 28th version? or am I going to go home, test it and have the same problem?

Thanks
-Eccentric

Ok, first test on Aug28th version midi is working. fingers crossed!

ok, so midi is now stable. but there is still 1 issue. triggers.... knobs/slides map good. but if you try to map a trigger it dosen't work.

If you map a trigger in the designer it will work after you re-open mydmx2.0 only if you re-open the designer, set it to the fixtures tab and leave it open. If you then go and map it also to it's short cut fly out above the slider it will then work after you close out of the designer, but you still have to at leaset open the designer, access that fixture tab, test all of your buttons and then close every time you re-open mydmx.

It's a processess, work around, but still a bug that you should know about...

e.g. you have to midi map your buttons in both locations (the designer and the shortcut above the slider) and re-open the designer everytime you run mydmx and flip through the fixture tabs and press all of your buttons and then you can close the designer (only if you've also midi mapped them to your shortcut above your slider as well).

-Eccentric

Midi Update:
You CAN NOT run a midi controller under the MyDMX 2.0 minimum system requirements. My guess is that you will need at least a duel core processer.


I had to use my friends i7 to program my midi control and run my show with the midi controller. (Not saying you need an i7… I would imagine an i3 or any older duel core may suffice), but if you try to run a midi controller on a single core processer you will experience a huge delay and jumps in the control. Eg a slight turn of the knob/slide will move after a few seconds… a large turn of a knob/slide will just jump to sporadic location because the signal is so delayed that you are not seeing it on the screen in real time.

-Eccentric

Jeff, is this midi trigger issue on the list of potential fixes?
Thanks,
Pau