William Koch
Member
Before I get into this, I know the X32 and M32 are not the best consoles available on the market, but I haven't experienced anything better in it's relative price range and work in a handful of venues with them. The scene management (or lack there of) is my only issue. It is built for concert/bar/club/festival and theatre is an afterthought.
I know that there is an existing scene parser tool for the X32/M32, but I have been unable to use it as I am a Mac user (don't hate too much) and therefore I don't know what the functionality of this tool is. I have started work on a scene management tool that would function via OSC to create it's own "scenes" that could be pushed back to the console. I know I hate the scene/channel snippet/cue management that the x32 offers, and I actually find it fairly impractical when it comes to running a large musical, or any musical for that matter.
The program would hold all scene data locally. It would use OSC to pull all console information from the desk to store a scene. It would then use OSC to broadcast data back to the console. It would allow master "recall safes" that would control what OSC commands the program sends out, hopefully both on the master and scene level the way the CL5 does.
My goal is to make a scene management tool that functions similarly to how the CL5 works, and hopefully add some of the functionality in terms of "tracking" values as well as adding a feature similar to the "aliases" in the digico SD consoles. My goal is to also eventually include OSC and/or MIDI back end to allow easy "go" button recall by sending MIDI commands from the console or MIDI or OSC commands from QLab for whatever integration would be easiest for your production.
My questions are:
Is there demand for this tool? How many of you would use this tool?
Is there anyone who would like to contribute to this project? I am working on getting the OSC working right now, but once I have that functioning I would love to bring any other swift developers in.
What kind of features would you like to be added? Anything that can be accessed over OSC is fair game, so 90% of the console is up.
Once I have this working and in a good place on the x32/m32, I would love to add flavors for other consoles in this price range that have the full OSC support that these consoles do, especially since it should just be minor changes in the code to adjust how it is accessing the console's OSC parameters.
I do intend to include redundancy checks in my code to ensure all OSC commands were received since this console is guilty of not liking to take OSC 100% of the time when it's receiving a lot of commands at once.
Is the idea of depending on an external program to control your console too terrifying for some of you to be willing to use this tool? I admit I have some hesitancy of my own right now as even a bug free program could disconnect and give me hell. That being said, we depend on network for a LOT of audio anymore so I think I can get over my hesitations. I would like to hear what others think of this. I will also work to eventually add support for a backup system to run simultaneously with a primary computer.
Another idea I have is to allow some program functionality over MIDI to where you could run this on a remote QLab computer and not mess with what your QLab op is doing while you are programming.
I know that there is an existing scene parser tool for the X32/M32, but I have been unable to use it as I am a Mac user (don't hate too much) and therefore I don't know what the functionality of this tool is. I have started work on a scene management tool that would function via OSC to create it's own "scenes" that could be pushed back to the console. I know I hate the scene/channel snippet/cue management that the x32 offers, and I actually find it fairly impractical when it comes to running a large musical, or any musical for that matter.
The program would hold all scene data locally. It would use OSC to pull all console information from the desk to store a scene. It would then use OSC to broadcast data back to the console. It would allow master "recall safes" that would control what OSC commands the program sends out, hopefully both on the master and scene level the way the CL5 does.
My goal is to make a scene management tool that functions similarly to how the CL5 works, and hopefully add some of the functionality in terms of "tracking" values as well as adding a feature similar to the "aliases" in the digico SD consoles. My goal is to also eventually include OSC and/or MIDI back end to allow easy "go" button recall by sending MIDI commands from the console or MIDI or OSC commands from QLab for whatever integration would be easiest for your production.
My questions are:
Is there demand for this tool? How many of you would use this tool?
Is there anyone who would like to contribute to this project? I am working on getting the OSC working right now, but once I have that functioning I would love to bring any other swift developers in.
What kind of features would you like to be added? Anything that can be accessed over OSC is fair game, so 90% of the console is up.
Once I have this working and in a good place on the x32/m32, I would love to add flavors for other consoles in this price range that have the full OSC support that these consoles do, especially since it should just be minor changes in the code to adjust how it is accessing the console's OSC parameters.
I do intend to include redundancy checks in my code to ensure all OSC commands were received since this console is guilty of not liking to take OSC 100% of the time when it's receiving a lot of commands at once.
Is the idea of depending on an external program to control your console too terrifying for some of you to be willing to use this tool? I admit I have some hesitancy of my own right now as even a bug free program could disconnect and give me hell. That being said, we depend on network for a LOT of audio anymore so I think I can get over my hesitations. I would like to hear what others think of this. I will also work to eventually add support for a backup system to run simultaneously with a primary computer.
Another idea I have is to allow some program functionality over MIDI to where you could run this on a remote QLab computer and not mess with what your QLab op is doing while you are programming.