logo

Live Production Software Forums


Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Options
Go to last post Go to first unread
jeregan  
#1 Posted : Sunday, February 26, 2017 5:40:13 AM(UTC)
jeregan

Rank: Member

Groups: Registered
Joined: 7/14/2016(UTC)
Posts: 24
Location: Canada

Was thanked: 10 time(s) in 3 post(s)
We have built a control room in a very cramped environment... used to house a large equipment rack for an analog sound system. We went digital and created the vMix control room.

It is probably the 'Worlds smallest TV Production Control Room'. One person can sit, and two people can stand in the space if need be.

We use 2 PTZOptics 20x, a 3rd fixed, plus a few GoPros.

The control surface layout (xkeys) is setup to emulate a commercial switching surface as much as possible, and we train volunteers to run it. Preview, Program, Overlay/DSK and a bus for the projectors in the worship space.

The iPad on the wall in some of the shots is to play music when vMix is not in use, as not all events are currently streamed or recorded, so this makes the sound system usable by users without vMix knowledge.

We have had some fun with the building HVAC, as it shakes the back wall, so the PTZ cameras have to sit on the side walls instead... not desirable, but until the HVAC is upgraded/replaced, it can't be dealt with easily.

See the attached pics. Enjoy!



jeregan attached the following image(s):
16143783_10154757330196259_7512073132900135435_o.jpg (81kb) downloaded 25 time(s).
16107385_10154743618141259_932776430877434586_o.jpg (168kb) downloaded 23 time(s).
16143477_10154743618146259_1138344899331873869_o.jpg (173kb) downloaded 19 time(s).
16112987_10154743648166259_7641848232096482177_o.jpg (83kb) downloaded 20 time(s).
15974904_10154743648261259_5061927765876115496_o.jpg (140kb) downloaded 17 time(s).

You cannot view/download attachments. Try to login or register.
zenvideo  
#2 Posted : Sunday, February 26, 2017 5:49:03 AM(UTC)
zenvideo

Rank: Advanced Member

Groups: Registered
Joined: 5/13/2014(UTC)
Posts: 514
Man
United Kingdom
Location: Manchester, UK

Thanks: 2 times
Was thanked: 183 time(s) in 130 post(s)
Very neat!
doggy  
#3 Posted : Sunday, February 26, 2017 5:55:22 AM(UTC)
doggy

Rank: Advanced Member

Groups: Registered
Joined: 12/27/2012(UTC)
Posts: 5,057
Belgium
Location: Belgium

Thanks: 283 times
Was thanked: 916 time(s) in 755 post(s)
Love the ledstrip :-)
IceStream  
#4 Posted : Sunday, February 26, 2017 12:05:18 PM(UTC)
IceStream

Rank: Advanced Member

Groups: Registered
Joined: 3/7/2012(UTC)
Posts: 2,600
Man
Location: Canada

Thanks: 33 times
Was thanked: 501 time(s) in 470 post(s)
@ jeregan

Very cool, thanks for sharing!
Really like how you've configured the x-Keys, can you elaborate on what you did?


Ice
dionv  
#5 Posted : Sunday, February 26, 2017 5:04:39 PM(UTC)
dionv

Rank: Member

Groups: Registered
Joined: 1/6/2017(UTC)
Posts: 16
Location: London, ON, Canada

Thanks: 3 times
Wow, nice setup!

That's quite the X-Keys rig, too.

Dion
jeregan  
#6 Posted : Monday, February 27, 2017 4:10:14 AM(UTC)
jeregan

Rank: Member

Groups: Registered
Joined: 7/14/2016(UTC)
Posts: 24
Location: Canada

Was thanked: 10 time(s) in 3 post(s)
IceStream wrote:
@ jeregan

Very cool, thanks for sharing!
Really like how you've configured the x-Keys, can you elaborate on what you did?


Ice


There are three Xkey units in total. One T-Bar 124, and two XK-80s. Two XK-80s were cheaper than one XKE-128 and gave me 160 keys to work with (20 wide) instead of 128 keys (16 wide).

I tried to emulate a commercial switching console, as I have worked with those in the past (a loooong time ago while volunteering for a local cable TV station) and found them easy to work with.

Bottom row: preview bus

Next row: program bus: same presets in the same virtual position on the board as the preview bus.

3rd row: Title buttons identifying the persons name/title (press and they overlay for 5 seconds), and further down the row fixed toggle ones such as the Bug logo in the bottom right corner, etc. Finally the double wide button is a means to mute the audio if you needed to quickly.

4th (top) row: same layout as the bottom row, but these send the feeds to the projectors in the worship space. The additional one button above that is a 'program follow' button which ties the projectors into following the program feed.

So the buttom row is the preview bus as mentioned... The first buttons are the base cameras... i.e.: no PTZ movement. Camera 1 is the north camera (with blue label) and Camera 2 is the south camera (with red label) and they are both PTZOptics 20x. Camera 3 is a fixed wide shot PTZOptics.

Buttons 4 thru 20 are PTZ presets for camera1 or camera2. When you press them, they tell the camera to move, but then automatically switch to the camera 1 or 2 button. (The reason for this will become apparent). So pressing, say, button 4 for the Pew Mic shot, lights up button 4 and then half a second later lights up camera 2.

When camera two is transitioned to be up on the program output bus, additional checks and balances are done in the background to make sure the operator doesn't accidentally call up the same camera to a different PTZ location via the preview bus. They get an X in the Preview window, the shot is then called up in preview (while it is still up in program), but no PTZ movement occurred. If the user wanted to override this movement, they would directly select that PTZ button on the program bus, causing the camera to move, but generally that is probably not desired.

The code also checks to make sure the X is not in preview (because all I am doing is calling up a graphic for .5 second) such that if the person tries to transition it to program via one of the Blue transition buttons on the right, it is just ignored.

This code tied to triggers and shortcut keys, really saves from user error, since in the real world there is a director, a camera operator, and the switcher operator, so there are human checks and balances... in our case one person is all three.

The rest of the buttons beyond button 20 are: a Gopro over the Baptismal Font (wide and slightly zoomed) which is used a few times per month, as well as a second for a similar use elsewhere on the font; buttons set up with Camera 1 and Camera 2 side by side, as well as one with Camera 2, Camera 1 and Camera 3 on one screen; some programmable buttons for videos, stills, etc., along with NDI inputs that are usually tied to a PC running Worship Him or PowerPoint elsewhere in the worship space; an input called 'Risefeed' which describes what is going on in the church (taken from a feed created via Risevision using HTML5 that is used to display information, pictures, event schedules, etc. on TVs in the hallways around the facility), as well as the required colour bars and black buttons. We don't use the FTB button because that really confuses users when they don't see it fade out on the program window.

In the upper right hand corner there are buttons to stop and start streaming with various messages that appear first on the stream or at the end of the stream before stopping.

I think that about does it. If that didn't answer your questions, let me know. :)

Jeff
thanks 3 users thanked jeregan for this useful post.
IceStream on 2/27/2017(UTC), dionv on 2/28/2017(UTC), sinc747 on 3/2/2017(UTC)
IceStream  
#7 Posted : Monday, February 27, 2017 11:23:35 AM(UTC)
IceStream

Rank: Advanced Member

Groups: Registered
Joined: 3/7/2012(UTC)
Posts: 2,600
Man
Location: Canada

Thanks: 33 times
Was thanked: 501 time(s) in 470 post(s)
@ jeregan

Thanks Jeff.
Very cleverly done.
Was there any "trial and error" or just a lot of pre-planning and then just doing it, as it looks like you've opted to eliminate half your buttons?


Ice
jeregan  
#8 Posted : Thursday, March 2, 2017 1:44:26 AM(UTC)
jeregan

Rank: Member

Groups: Registered
Joined: 7/14/2016(UTC)
Posts: 24
Location: Canada

Was thanked: 10 time(s) in 3 post(s)
IceStream wrote:
@ jeregan

Thanks Jeff.
Very cleverly done.
Was there any "trial and error" or just a lot of pre-planning and then just doing it, as it looks like you've opted to eliminate half your buttons?



Some preplanning for sure, but still yes, a lot of trial and error. We tried different things to see what worked starting last July and noted what looked good, what sort of errors we as humans were making, then I wrote some code to help block those errors (as mentioned above).

And we tried various control surface configurations before we landed on one that was fairly straight forward. One of the advantage of having so many blanks buttons on the Xkeys as that it minimizes finger errors. We had just one T-Bar unit at the start and had multiple rows side by side together to get the # of inputs we needed, but found it was too easy to make a mistake.

Jeff
Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.