Paul, thanks for the information. The only reasons for Python are that is was recommended to me due to simplicity, and it also has some other libraries that I'd like to work with. For example, I need to transmit Art-Net also. It's been a little rough getting started as I'm giving myself a crash course in Python. I haven't touched C in ten years, but I used to know my way around in C. I've made some progress (posted below) with the start of what I am working on. Basically, I'm polling for mute status on a channel and printing it out. Eventually, my goal is to turn this into a DMX cue light or lights. I was able to get things talking last night finally. I'd also like to use TouchOSC on a tablet to create a cue light, or similar system, but I haven't explored that much yet. from oscpy.server import OSCThreadServer
from time import sleep
osc = OSCThreadServer()
sock = osc.listen(address='192.168.10.36', port=9999, default=True)
Well, I got the no value part to work out by changing the source code of the Python-OSC library I'm using. Now my issue is that I need to send the message and then listen on the same port number that it was sent from. Drawing a blank on that one at the moment. This is more of a Python problem, so I'm not sure if anyone here can help.
I am getting started on a small project using Python to work with the X32 via OSC. I know how I can send a command (eg. /ch/01/mix/on ,i 1) to turn a channel mute on or off. However, I'm not sure how I can poll the console for the status of the channel mute (or any other variable). Could someone point me in the right direction on how to request information from the console for a specific value via OSC? Thanks!
David Schumann;69345 wrote: That looks awesome! Mind if I add your screenshot to the Google Play store? Yes gains and 48V are currently missing, I will add them in the future. Opening a fixed channel is possible by adding two actions to a button: 1. Select Channel -> Main LR 2: Open View -> Channel PEQ Note: Adding more than one action to a custom UI item is only possible since V.062.5 I can email you a higher quality screenshot, but yeah! That's a great thing about the multiple actions. Works like a charm. Thank you! I've got some feature requests related to this if yall want to know them.
I am using a Samsung Galaxy S8.4. I think it has version 5 of Android on it, can't remember (don't have it with me now). I pressed the power and home buttons simultaneously to take the screenshot. I'm been happy with this tablet, as it has a very bright screen and high contrast, which makes it somewhat more useful outdoors during daylight.
Because Mixing Station is so customizable, I think it would be great to share screenshots and maybe a little explanation of how you've set it up to work for you. http://postimg.org/image/lculhcvtd/ http://postimg.org/image/wef50kyu1/ I have High Pass, Gate, and Comp adjustable from the left bar for the selected channel. DCA 8 is always for break music playback, and its handy to have this as a knob always there. Numbers 1-16 at the top are for quick access to Sends On Fader for each of the buses. The -0.2 is the Main fader level display, then an easy access to the Main GEQ, and then the Main Pan display, which is currently 0. On the right bar I have Tap delay and all mute groups easily accessible. My default starting pages contain 16 faders each, except for the User 1-5, which are just layers that have been added and are awaiting customization per the needs of the particular show. What I would like the ability to do is to select channels easier, have gain and 48V on the left bar, and also have a quick link to the main PEQ, which for some reason I was not able to get all of those things to work. Anyone else have any cool tricks with their Mixing Station layout?
I have a DL32 stage box and would like the X32 console to support fully redundant AES50 networking between console and the stage box. That is, ports A and B should both be connected, and there should be seamless failover if one of the cables was to stop working during a show. I think this is a huge feature for peace of mind, and find it hard to believe that it hasn't been implemented yet. The stage box would have to be able to be configured to receive clocking from either port A or B, and the console would have to avoid patching AES50A or AES50B inputs to a channel, and just have AES50 inputs, regardless of the A or B port. Perhaps full redundancy mode could be an option, since this obviously kills some of the functionality that others may be using the dual AES50 ports for.