Needs more than 12 I puts. I suggest 16-18. Possibly make 4 of the assignable to any active Input in the session

This is good, but you have 12 inputs, and Jim is asking for more...I would suggest, not to make a fixed number, but have the control surface so it will add the buttons as inputs are added, so that there will not be more buttons than is actually needed....I see this as much better than a fixed number. 12 is a good number to start, but for me personally, I prefer 8, and add as the inputs are added....I used Vidblaster, and that is how theirs work, this will avoid the clutter on the monitor.....This is just from observation of other similar software...I hope this can be resized by the user, as I see others have a fixed size.
I would also suggest using white buttons rather than so much colour, and change to either 'Yellow' or Green' when selected, and 'Red' when active, the same way all control surfaces work....this will be much easier to read in both daylight as well as night.....I also like the idea of dedicated function buttons....it helps to keep things simple....I like this control surface.....and am ready to beta test as soon as it is ready....

Now this is a bit over done...32 buttons.....why not leave it at 12, or make it 8 buttons, and let the program add more buttons as more inputs are added.....in that way, the users who only have 4 to 8 inputs would not have to worry about so many unused buttons......I think 32 is way too much....

I am still tweaking layout of control surface...

- Had 12 input's, users were saying 12 is not enough.

- Having inputs adjusted automatically for the number of inputs added in vMix is not
feasible due to screen real estate and programming. vMix does not return the
number of added inputs, or how many inputs are supported by which version of vMix user
currently have, API does not return number of added inputs... (easier said than done)

Video Window

Input Switching - 32 Program, Preview and Overlay buttons in traditional crosspoint layout for input control

DSK - 4 Downstream Keyer buttons to activate Overlays

Transitions - 2 transition buttons to control vMix configured transitions including Cut, Fade,
Zoom, Wipe, Slide, Fly, CrossZoom, FlyRotate, Cube and CubeZoom. Take button for quick cuts.

T-Bar - Smooth motion t-bar for clean transitions.

Function Keys - 4 User assignable functions keys for automation through vMix Shortcuts.

Overlay - 4 User selectable overlay button to change assigned input for overlay use...

Moved to Audio Window

- Reason for Talk back button is in our productions, we use them to talk to (camera operators,
talent, and production crew etc...)

- Reason for Tally light we use them in our productions to turn on light to notify talent, guest, and audience.
(eg. on air indicators, which camera is on talent, commercial breaks etc....)

I'm with Bandit62 on Tally and Talkback. We use ClearCom units for this in all our productions, which 90% of people do that are doing serious production and I see no way to interface that with this. My opinion remains this product should focus 110% on controlling the assets of VMix...nothing else. A preview/program out window for confidence purposes only is a great idea. I'd make it undockable so it could be pushed to a second non-touch monitor if desired. Otherwise, I think you're definitely headed in the right direction here.....GOID LUCK....can't wait to try it out.

+1 for having an integrated talk back. Clear Coms are great both wired and wireless. An integrated talkback would be great for our school set up.

Thanks

Anybody that thinks TeamSpeak at its present configuration is a substitute for real wired or unwired talkback is dreaming. And what are you going to do when your camera op on the 50 yard line says his phone battery is dead in the 4th quarter? it's not my call, but talkback and tally in this application takes up screen real estate that needs to be used for things like imput overlay channels, etc. Again, my advice...make it about running vMix, not peripherals.

First and for most, I am writing this software to help me in my productions JimJacobs, if you do not want to use the talk back or tally features then don't use them, it's that simple.

Secondly, you haven't even seen a beta of the software and haven't even been released already and you are already bashing it.

I couldn't care less if you even use the software I am developing.

Maybe i should just keep it to myself and not release it.

Desmar,

One more vote for you to do it. If you haven't heard the story of vMix you should know that Martin decided to create vMix because he wanted to help his church at Christmas. It started for the small guy and has grown....but there are still an abundance of us small guys. My junior high school is dreaming bigger....with vMix, but we are working without any coms and sounds like we would love what you have in mind.

Keep going....

I am seeing 3 or 4 versions of this controller.....the first for simple users, like me, a more advance controller for more advance users, and even more advance setups.....so, does this means that we will have a choice of controllers?...please say yes....hahahahaha......That would not be a bad idea ....more than one version of controllers.....I like the first one tho......with a 'T' bar rather than a left to right fader.....more traditional.....keep it coming buddy....we are watching and waiting ....

Thanks for sharing your ideas....

I also see another layout...where you can have the functions as tabs, just click on a tab to open a different setup panel....similar to how its done with TriCaster and similar....