To Mixer App developers

Jay Barracato

Graduate Student
Jan 11, 2011
1,528
5
38
Solomons MD
Now that I have been dragged kicking and screaming into wireless mixing (Yes, I still fight with touchscreens) and am willing to admit there is some value and it can make certain types of gigs/procedures easier, there is a particular function I would like to see in the wireless apps that I have not seen before.

I would like a modular custom screen where I can place controls I use frequently, so I can access them immediately. Often between songs I find I need to be on 2 or 3 different screens to be ready for the next song. It would be nice to have them in a single place where I can define the layout. For reference, the Blackboard software I use for teaching my college class has a multitude of functions, but the user can arrange their primary view as they wish. Everything is still available through the regular screens and menus but the user defines their primary view.

My custom screen would probably have
1. A key channel fader or two. My style of mixing is not a fader rider but their is always one (money channel) it is nice to put your finger on immediately.
2. A DCA fader or two depending on the show.
3. Aux output for the money channel wedge.
4. Input and Output and select for effects. A tap button big enough to hit consistently.
5. A meter bank.

The beauty of this type of programming is that if you don't like my setup you can set up your own. The interface would always make sense to the operator.
 
Re: To Mixer App developers

1. A key channel fader or two. My style of mixing is not a fader rider but their is always one (money channel) it is nice to put your finger on immediately.
2. A DCA fader or two depending on the show.
3. Aux output for the money channel wedge.
4. Input and Output and select for effects. A tap button big enough to hit consistently.
5. A meter bank.

The beauty of this type of programming is that if you don't like my setup you can set up your own. The interface would always make sense to the operator.


Not to over simplify... but...

DCA # 1,2 = money channel + other
DCA # 3 = money channel output mix bus
DCA # 4-8 = Effect output buss (es)
 
The X32 remote protocol is open, just write your own app ;)~;-)~:wink: .

Ron, ask me again in 3-5 years when we know what the shelf life of the hardware is.

For everyone else, it is not about what you would put on the layer, it is about being able to choose. This type of modular programming is all over programs today
Think custom toolbar gone oversized


Sent from my DROID RAZR HD
 
Re: To Mixer App developers

h e x l e r . n e t | TouchOSC
Lemur – Liine

There's others too.

Been around for quite a while.

You had me excited, but that is not what I am looking for. A big part is that custom layer should be native to the mixers control program, so you don't have to go digging in another app to get controls that aren't in common use. I got the touchOSC and starting digging through the documentation but it became clear quickly that the time effort for trying to make a custom interface is not worthwhile.

It may be my bias against midi control (I spent most of the 90's out of sound doing other things while midi went from a novelty to something usable) but I don't see trying to recreate what can be done with in the mixers native apps or trying to have different devices trying to access the same controls.

A visualize simply a blank screen that can be accessed just like you access any of the other control screens in the app.
A double click or something unlocks the view.
A double click or something pops up a menu with the controls accessible through the app.
You select one and it copies it to the blank page.
You slide it to where you want
You repeat for other controls
Another double click or something takes you out of the edit mode and locks the view.
Then when you use the control it acts just like it would in its usual location.
 
You had me excited, but that is not what I am looking for. A big part is that custom layer should be native to the mixers control program, so you don't have to go digging in another app to get controls that aren't in common use. I got the touchOSC and starting digging through the documentation but it became clear quickly that the time effort for trying to make a custom interface is not worthwhile.
If you're not willing to put the time and effort into it, and you're the one interested in controlling your equipment this way, why would you think anyone else would be interested in putting in that effort?
If you want it customizable and without limitations, it will necessarily be complex and require effort. Otherwise you're looking at the pre built apps from the manufacturer.
 
If you're not willing to put the time and effort into it, and you're the one interested in controlling your equipment this way, why would you think anyone else would be interested in putting in that effort?
If you want it customizable and without limitations, it will necessarily be complex and require effort. Otherwise you're looking at the pre built apps from the manufacturer.

You are not listening. I made a suggestion for something to be added, something that is ubiquitous in other software types.

Just because I am looking at an add on to a manufacturers software doesn't mean you need to throw it out and start completely over.

As a chemist I use subscripts and superscripts a lot more than average writers. Generations of the word program has allowed me to pin that tool button where it was accessible without having to write my own word processor.

Sent from my DROID RAZR HD
 
Re: To Mixer App developers

I am doing this with my Tablet running the iLive editor software. it has always been a function on the editor but not on the ipad app for iLive. I am not sure about the new ipad app that you pay for though.

In answer to your question Jay, some people are doing it some are not, but yes it should be on all of them!!!
 
Re: To Mixer App developers

My experience is with the Presonus app only, and I can say it is FAR from complete from a function standpoint. Jay's suggestions do seem reasonable enough.

I have witnessed a colleague using the Mackie app (actually the entire interface). I can't say if it is that he has not optimized his workflow or if the software is klunky, but it is a painful to watch his slow changeovers and setup on the ipad. There is still something to be said for the speed in setting up an analog console. The workflow process is more forgiving on the analog - easy to just back up and grab a knob, rather than swapping screen to screen.

I liken it to the software embedded in a digital camera - it is abundantly clear engineers and marketeers designed the interfaces without input from real photographers.