By the way, I just discovered that if you apply a Key mask to a zoom input, you can then use it on a layer in another input and do cropping there. So if you make a mask that is a full frame of white, and use it on all of your Zoom inputs, nothing gets masked out, but it allows the cropping later. But it's kind of weird that you have to do that

* Custom Output Resolutions like a 21:9 1080p output
* Multiple Outputs for EdgeBlending of Projectors
* Scopes(Histogram/Spectrum/...) of Inputs as Inputs and/or to be used as an Fullscreen Output
* More sophisticated Tally Engine for PTZ cameras. For example we use 3-4 Panasonic AW-UE150 with Vmix
via HDMI inputs. We make different Layouts/Inputs and merge between them. The Tally should reflect if a
Camera is actually used in the current Output/Preview and if its in the visable field of view. If its moved
out of the visable field of view, there should be an option to turn the tally off on those Cams.

After vmix 28 beta release i remembered this thread and i see what of our ideas have been implemented in Vmix 28

Instead of "oncountdown time" they add "on playback time" and "on playback remaining".


1.Flatten layers is finally implemented and that goes the layer composition a lot higher
2.No un-fortunatelly
3.No un-fortunatelly



Also the scroll wheel enable/disable has been added


From this list i see as implemented the All buses button in audio mixer

When vmix 28 will be final release, i think is usefull to have a vmix 29 ideas thread and hope vmix team to use it for some new features

Sem titulo.jpg (114kb) downloaded 83 time(s).

[img=https://1drv.ms/i/c/345875937cc17849/EXCWeK9SXAtFhgnFxQjjsPUBPucs4SpZecHJ54hR7uhsHQ?e=gHi6ex]PRINT[/img]

Como está na ilustração, editei o layout do "Title editor" para incluir seta para cima e para baixo, de maneira que possamos selecione um item e mova-o para outra posição desejada.
desde já agradeço a atenção de todos.
atenciosamente,
Bruno Gonzaga - CEO START TV LIVES

Add these possible functions to the DataSource group

Examples:





Update the vMix version of the .NET development code to include at least the System.Text.JSON framework. Retrieving data in that format is very basic these days and is already implemented, at least in DataSource.

For Input Trigger Menu: Add button or master checkbox to Select/Unselect (Activate/Deactivate) ALL triggers in list.
For Input Trigger Menu: Add function to 'sort' by the column. I expect triggers to sort when I click the top of the list, but it does not sort. Sort by active triggers, sort by type (ex. OnOverlay In), Sort by Input Number, Mix#, etc.
For Triggers Managers Menu: Same sort function, but also add filter function

For List Editor window: Add item preview. This could mean a thumbnail view for all files rather than a 'file name and length' view (like windows explorer). Alternatively it could mean that we retain the file name view, and add a single preview window inside List Editor. A Single mouse click on list item could show the file inside this special list editor preview window. Currently it can be tricky to know for certain which image/video is going to be activated by double-click because only file names are visible.
For List Editor window: click and drag file order
For List Editor window: highlight multiple files and move them together into new order
For List Editor window: Fix .webp files to work correctly (for years now, they 'auto next' instantly after being selected in a list).

For Video Mark In/Out: Current interface is VERY difficult to scrub to a specific timestamp to mark in and out. While I accept that some videos are encoded in a way that prevents precision Marking of In/Out, it still would be helpful to allow me to specify a timestamp by manually typing it (and then I accept the frame drift that may occur with some videos).

Restore ability to 'Change' an Input when created as a Virtual Input.

Not all users custom titles use "Headline" a a discription of a or the first textfield within a title ;-) so should be based on the index of the textfields.
That is something that can be retrieved from the vMix API together with it content ,
Then there is a function allready available to name a vMix input so no need to go through the cogwheel scenario.

so retrieve what you want and set it to the input name with a script

SetInputName





Keep Presets save to fall back on ( mark shortcuts and scripts as local) / save as bundle option etc....