![]() ![]() Dual outputs allow for redundant backup systems for failsafe show control.įor use as a QLab Remote, MIDI Go Button, Ableton Remote, SCS Remote, SFX Remote, or MIDI Remote in supported applications, with dual USB outputs and a footswitch GO jack.īuilt with the highest quality components, the Q-Widget-PRO is designed to work as hard as you do.įootswitch jack as an alternate “GO” input The Q-Widget-PRO is a simple and dependable show-control remote for QLab, Ableton, Show Cue Systems’ SCS, Stage Research’s SFX, and any other Mac or PC application with MIDI support. If in doubt please drop us a line and we’ll try to help. We can also point you in the right direction for specialised services that we are unable to provide ourselves. Please email us with your dates & spec for a quotation, or give us a call to discuss your requirements in depth. We are based close to Edinburgh city centre for fast response in an emergency.ĮXTENDED FESTIVAL OPENING HOURS Monday to Friday We offer exceptional equipment and service – including after-hours support and extended opening times during the Edinburgh Fringe Festival – and competitive prices. With a long list of Edinburgh Fringe clients, including the biggest venues in the festival, you can be sure that your show is in safe hands. The ESP-01 is also a 3.3v device the power source I was using was a portable battery setup which was around 5v so that is why the voltage regulator is included in the breadboard.At DM Audio we understand the commitment required to put on a show as part of the Edinburgh Fringe Festival, and we will do everything we can to make your life easier by providing the sound equipment you need at a reasonable price and with unrivalled local support from our Edinburgh base. In my protoboard mockup seen in the main picture for this project I simply used regular male headers for both the pin input and power, it is really just personal preference. The other thing worth mentioning is the power input the schematic has a barrel jack only to make it easy to distinguish between the power source and the switch input. It is also small enough that working it into a small object wouldn't be that much of a challenge. The one stipulation is that it needs to able to be configured to be naturally closed, which is why I used a micro arcade style switch for the trigger. The switch port is meant to be able to be used with different kinds of switches. I have also included a wiring diagram in case you want to make a protoboard version like in the thumbnail. I have again included a diagram of how the ESP-01 should be wired up so that it works with the included sketch. They can be modified before uploading so that the device will use the values you want the first time around.Īfter this is done it is on to wiring up the ESP-01 for switch inputs. They are the files the device needs to host the configuration pages and store the configuration. First would be to change the default settings, these are located in the "data" folder in the sketch folder. There are few things I would like to note that could potentially make the process easier. Once this is all up and running it is all that needs to be done is upload the Device sketch and the included data to the ESP-01. It does require an additional plugin for the Arduino IDE which is available here along with instructions on how to install it and use it. It is used to store the device's configuration as it isn't volatile and keeps the values after resets/power loss. My sketch makes use of another feature of the esp8266 which is SPIFFS, it is essentially small amount of flash memory that files can be written to and read from from inside the sketch. For convenience I have included a schematic for how I wired the ESP-01 for programming. There are many guides that illustrate how to add the Eesp8266 board to the list of boards and Arduino There are also many guides on how to wire up the ESP-01 for programming. There are some more background details and some improvements or features that I would like to add but I will touch on that later. That's pretty much the idea behind the project. For the QLab example if I wanted to fire cue 1 the command would be "/cue/1/start". The command is the exact string that the device will send in a UDP packet. The port is the port on which the UDP packet containing the command will be sent on (QLab default is 53535). The IP is the IP address of the computer (in my case it is the computer running QLab) that the command will be sent to. The ID is a name given to the device so devices so devices can be told apart if there re multiple in use at once. The four boxes in the configuration page correspond with the main settings that are configurable on the device. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |