ProfDrJones

Thanks for the support, but the issue kind of settled by it self somehow, ... I think the output you were looking for was: USB Device... EEEF:2828 - 'TSTP', 'MTouch', 'CMTP_1.0' and corresponding to that: Input Device... /dev/input/event1, TSTP MTouch, usb-ci_hdrc.1-1.1/input0, CMTP_1.0 I don't know why, but the first 5 or 6 boots we had to recalibrate in order to get touch capability, ... but now, for the last week or so it worked like a charm. --- Hopefully this will be the case as well as soon as we get our new active usb hub. We need that to supply power to a backlight keyboard and the build in usb ports are to few as well.

Thanks for the reply, ... I will try this tonight.

We recently upgraded our external monitor to a 15'' IPS Touchscreen. (we have space constraints, ...) After trying different model, with various problems I thought we found an affordable offbrand one that seemed to work, and it kind of does, ... One of the main problems with the other screens was that they lost touch sporadically and even calibration wasn't helping. Or they would rotate trough different resolutions at the bootup, ... (even if set to a fixed resolution) The new screen works reliably, no flickering, the bootscreen is shown instantly and touch works, even if power is cut to the console and the screen for a couple of minutes. Everything comes back up as before. The Problem is if there is a longer powercut, e.g. over night. On the next boot touch is simply not working. A quick calibration fixes the issue as if the calibration data is lost, ... Is there a ways to keep the calibration or is there a magic setting I haven't seen? Or is there a debug option that logs the boot process? (As this might be asked, ... we already upgraded to zerOS 7.13)

Thanks Edward. @kgallen I'm a sofware engineer and thinkerer my self, therefore the thinkering solution might be the way to go for now. I already built a DMX receiver based on an arduino for a couple of simple show effects like a telefone that can ring on stage or some stepper motors for the colorwheels of our older spotlights. A signal converter to a reduced MIDI command-set shouldn't be that hard to implement from what I've seen in the MIDI protocoll specs.

I do appologize if this question is stupid, but I'm not a professional light engineer and haven't found a good solution so far. If there's an industry solution, please point me in the right direction. We are using our Zero88 FLX mainly for theatre and small music shows. Specially for theatre, there are often audio playbacks e.g. a telefone ring accompanied by a light cue. For the last 20 years our solution was to press the play button on the audioplayer and the Go button on the light controller simultaniously, which could get stressfull if other actions like a short burst from a fog machine (not DMX controller at the moment), a video cue, ... would follow. What seems to be the industry standard is "Midi Show Control" which requires a computer and running the show on there. I already tested this solution and I works fine, but I'm not very fond of using a Laptop for running shows for several reasons, one of them being older volunteers that run shows and are well versed with the light and audio controls but struggle with computers. I would love to cue audio playbacks via the FLX, so the volunteers would only have to trigger a cue via the GO button and the audio would be trigger automatically. The solutions I found that is more along these line are DMX controlled audio players, but there applications seem to be focused on showrooms and museums, which would explain why most of them don't have a display or other user interface of any kind. Have I missed another solution? Is there maybe a way to add midi commands to a cue and send them from within the FLX?