Hi Martin.

There seems to be an issue with the Virtual Inputs and Tally lights.

I used the Create Virtual Input to create few inputs with different zoom factors of a chroma key input.

Tally light should stay red (outgoing input) when I switch between these, but now it turns green when I select Virtual Input that should be used next.

Kind regards,
Jan

Program mixed in vMix 15

Turn English/Frensh subtitles on.

Tally and Intercom Solution:
http://tally.fi

Bardos,
One of the reasons we chose vMix is its very effecient use of PC recources. The demo I recorded in this case was made on my work laptop, which has a dual core low CPU-rate and graphics card not suitable for live productions. For real productions we have a number of different PCs, all balancing cost with production needs. I would definetly not say that vMix is becoming CPU hungry! Quite the contrary, with recent versions and Windows 8.1 we can do more with the same hardware we had three years ago :)

Don't go changing the ffmpeg.exe, it is not supported to do so.
In our tests the 32bit version tends to use less cpu, so that is why it was chosen.

Regards,

Martin
vMix

Please use vMix x64. While it uses 32bit external applications such as ffmpeg, the performance is still better.

@ admin

Not sure if it's a 'bug' or not.
While playing with "SelectIndex" function, I noticed the 'Virtual Set' value parameters do not necessarily correspond to the descriptions in the dropdown, but rather left to right, top to bottom of the 'Camera' angles of the Virtual Set "Input".
In particular "Studio115 A,B and C" (in my case, and I can only assume is similar for other "imported" or "altered" virtual sets) where the 'Close Up' is actually the 3rd angle, not the 1st.
I hate to suggest this because I prefer descriptive titles, but perhaps numerical Zoom/Angle references (i.e. 'Zoom 1, Zoom 2, etc) would be better descriptors if there is not a 'Standard' that Virtual Sets live by or people 'alter' the settings of each Zoom effect for their own needs.


Ice

Kibim,

The ShuttlePROv2 is currently the only supported controller for moving
back and forth through replay footage.

Using ReplayJumpFrames would not work the way one would expect with MIDI which is why it has been disabled.

The main reason being MIDI controllers send a fixed value from 0-127, so if vMix received the value 64, it would jump forward
64 frames, but if you move it slightly again to 65, it would move 65 frames on top of the previous 64.

A solution to this is non-trivial and depends on the device, so we will look at purchasing a CMD-PL1
at some point with the hope of supporting it in a future release.

Regards,

Martin
vMix

Thanks for the response Martin.

I got it working perfectly well like that using the bome midi translator. The values of 0-127 are fairly easy to work in.
At 64 it's stationary ... so for every value UNDER 64, it would be = frame - (64 - velocity value), and for anything OVER 64 it would be = frame + (velocity value - 64).
The controller issues the following command for movement of the platter : Channel 1 : Note 31 : Velocity.
It's touch sensitive too, so on touch, it issues velocity 127 and on release it issues velocity 0 (which is neither here nor there ... so ideally ignore this command, or as i have done, issue it as "pause" and "play" respectively)
Then winding it left issues a velocity value from 63 going downwards as you increase the speed of the turn, going right issues 65 upwards as you increase speed.
I had it set up as follows in Bome for advance:
65 = +1
66 = +2
67 = +5
68 = +10
69 = +20
70 = +100

You really have to wind the thing hard to get it to reach 70!

Even if I have to manually programme each shortcut for each corresponding frame count, i don't mind, but the 'find' although it reads velocity, doesn't allow it to be linked, so i can't do this.

All the turn wheels on the CMD-PL1 run in the same way, so it would be really nice for the software to allow the use of the velocity value as an input. We could assign knobs to scroll through selections of Event Lists, to increase or decrease in and out points ... the list goes on.

New update (16.0.0.60) has been uploaded to the same download link

http://www.vmixhd.com/download/vmix16preview.exe

This is the "release candidate" version which means if no other bugs are reported
in the next week it will be posted on the web site as the final version of vMix 16!

The help file has also been updated and improved:
http://www.vmixhd.com/help16/

Changes and fixes:

* Fixed bug when restarting after changing settings more than 5 times in a single session
* Fixed PlayList bug not restarting MultiView inputs
* Removed error when clicking Mark Out button in Instant Replay without clicking Mark Out first.
* Added ReplaySetDirectionForward/Backward shortcut functions
* Instant Replay will now automatically move the preview to the beginning of an event after clicking Mark Out.
* Web Interface renamed to Web Controller
* Fixed disabled shortcuts showing in Web Controller by mistake

Sounds like the Akai is changing channels or something like that.
When detecting the control again through find, check to see if the channel is different to what it was before?

I'm not sure if this is a bug, but only to mention it.
Only a guess: When I load a vMix 15 preset - vMix 16 use as default the option "Assign Shortcut to Input Number" ?