FFMPEG WDM Capture for Decklink Cards.

It is preferable to use the WDM Decklink driver, rather than the dshow support, with ffmpeg (or in fact any Windows software).This requires using a version of ffmpeg that has the Blackmagic WDM drivers included (see my downloads page for a possible source).

To use WDM Decklink driver, use a command like this:

ffmpeg -f decklink -i “DeckLink SDI 4K@14”

Use the number in the left column below after the @ symbol for defining the input source format.

Supported formats for ‘DeckLink HD Extreme 3D+’:
1       720×486 at 30000/1001 fps (interlaced, lower field first)
2       720×486 at 24000/1001 fps
3       720×576 at 25000/1000 fps (interlaced, upper field first)
4       1920×1080 at 24000/1001 fps
5       1920×1080 at 24000/1000 fps
6       1920×1080 at 25000/1000 fps
7       1920×1080 at 30000/1001 fps
8       1920×1080 at 30000/1000 fps
9       1920×1080 at 25000/1000 fps (interlaced, upper field first)
10      1920×1080 at 30000/1001 fps (interlaced, upper field first)
11      1920×1080 at 30000/1000 fps (interlaced, upper field first)
12      1920×1080 at 50000/1000 fps
13      1920×1080 at 60000/1001 fps
14      1920×1080 at 60000/1000 fps
15      1280×720 at 50000/1000 fps
16      1280×720 at 60000/1001 fps
17      1280×720 at 60000/1000 fps

 

Supported formats for ‘DeckLink SDI 4K’:

1 720×486 at 30000/1001 fps (interlaced, lower field first)
2 720×576 at 25000/1000 fps (interlaced, upper field first)
3 1920×1080 at 24000/1001 fps
4 1920×1080 at 24000/1000 fps
5 1920×1080 at 25000/1000 fps
6 1920×1080 at 30000/1001 fps
7 1920×1080 at 30000/1000 fps
8 1920×1080 at 25000/1000 fps (interlaced, upper field first)
9 1920×1080 at 30000/1001 fps (interlaced, upper field first)
10 1920×1080 at 30000/1000 fps (interlaced, upper field first)
11 1920×1080 at 50000/1000 fps
12 1920×1080 at 60000/1001 fps
13 1920×1080 at 60000/1000 fps
14 1280×720 at 50000/1000 fps
15 1280×720 at 60000/1001 fps
16 1280×720 at 60000/1000 fps
17 2048×1080 at 24000/1001 fps
18 2048×1080 at 24000/1000 fps
19 2048×1080 at 25000/1000 fps
20 3840×2160 at 24000/1001 fps
21 3840×2160 at 24000/1000 fps
22 3840×2160 at 25000/1000 fps
23 3840×2160 at 30000/1001 fps
24 3840×2160 at 30000/1000 fps
25 4096×2160 at 24000/1001 fps
26 4096×2160 at 24000/1000 fps
27 4096×2160 at 25000/1000 fps

Decklink Duo2/Quad 2

Card name will look something like ‘DeckLink Duo (2)’:

1 720×486 at 30000/1001 fps (interlaced, lower field first)
2 720×576 at 25000/1000 fps (interlaced, upper field first)
3 1920×1080 at 24000/1001 fps
4 1920×1080 at 24000/1000 fps
5 1920×1080 at 25000/1000 fps
6 1920×1080 at 30000/1001 fps
7 1920×1080 at 30000/1000 fps
8 1920×1080 at 25000/1000 fps (interlaced, upper field first)
9 1920×1080 at 30000/1001 fps (interlaced, upper field first)
10 1920×1080 at 30000/1000 fps (interlaced, upper field first)
11 1920×1080 at 50000/1000 fps
12 1920×1080 at 60000/1001 fps
13 1920×1080 at 60000/1000 fps
14 1280×720 at 50000/1000 fps
15 1280×720 at 60000/1001 fps
16 1280×720 at 60000/1000 fps

Advertisements

PowerShell Automation of FFMPEG

Want to create thumbnails from video files or convert from .ts to .mp4? FFMPEG can do it but the command line can be a bit tricky to figure out. There is a nice .Net library for automating ffmpeg that can be used in PowerShell. See NrecoSite

Example PowerShell:

# Download https://www.nrecosite.com/video_converter_net.aspx
# copy ffmpeg.exe to C:\Windows\SysWOW64\WindowsPowerShell\v1.0\
# Documentation - https://www.nrecosite.com/doc/NReco.VideoConverter/
$thumbnail = "D:\Capture\Conference_20170722_090251.png"
$video = "D:\Capture\Conference_20170722_090251.ts"

add-type -path 'C:\Users\imorrish\Documents\WindowsPowerShell\NReco.VideoConverter.dll'
$ffMpeg = new-object NReco.VideoConverter.FFMpegConverter
#Create thumnail
$ffMpeg.GetVideoThumbnail($video, $thumbnail,1653); #seconds from start
#Convert to MP4
$ffMpeg.ConvertMedia($video, "d:\capture\Conference_20170722_090251.mp4", [NReco.VideoConverter.Format]::mp4)

Sony BVS T-Bar reused

I picked up an old Sony BVS-3200 broadcast vision mixer from ebay (my first experience of the Global Shipping program and it actually works).

I’m still undecided whether I will be able to use the panel through the existing serial interface (need to get a frame to decode the messages), rip out the microprocessor and put in an Arduino (requires reverse engineering all the logic) or gut it for the parts to build my own panel.

Just testing the T-Bar as it is non-destructive to remove it for testing. Rather than using a potentiometer, Sony used a rotary encoder that outputs pulses (must be a technical name for this which I’ll find on Google eventually).

It actually outputs 2 signals so you can detect the direction by which line goes high first.

I get 536 counts from full movement of the T-Bar.

PowerShell and demo video showing this controlling the Blackmagic Design ATEM fader coming soon. In the mean time I’m also converting an old EchoLab MVS panel but that uses very simple circuit by the look of it so I’ll be replacing its Z80 processor with an Arduino.

Video:

https://youtu.be/dZNZ4jW0nuw

Frustrated with Windows default audio device changing?

You can include PowerShell commands to change the default device (for playback and recording) using PowerShell

Using this GitHub project https://github.com/jtheller/AudioDeviceCmdlets/tree/ce0bd480e96e934621c5ca6f846a65830c1a74d3

I found this useful when using a DVI Extender that would change the default audio to itself even though it required the main sound card to provide the audio into it.

Just install using the script below

#region Install code, just run once
$url='https://github.com/frgnca/AudioDeviceCmdlets/releases/download/v3.0/AudioDeviceCmdlets.dll'
$location = ($profile | split-path)+ "\Modules\AudioDeviceCmdlets\AudioDeviceCmdlets.dll"
New-Item "$($profile | split-path)\Modules\AudioDeviceCmdlets" -Type directory -Force
(New-Object System.Net.WebClient).DownloadFile($url, $location)
#endregion

#run this or add it to your profile so the module is always imported
Import-Module AudioDeviceCmdlets

#List current audio devices
Get-AudioDevice -List | select Index,Default,Type,Name| ft

Output:

AudioDevices

ATEM SuperSource Box configuration using PowerShell script

I finally sorted the code for enumerating the collection of super source boxes in the 2 M/E and tested it this weekend.

Download the latest version here…

add-type -path 'C:\Users\imorrish\Source\Workspaces\VISE_ATEMLib\SwitcherLib\bin\Debug\SwitcherLib.dll'

add-type -path 'documents\windowspowershell\SwitcherLib.dll'
$Global:atem = New-Object SwitcherLib.Switcher("192.168.10.240")
$atem.Connect()
$Global:ME = $atem.GetMEs()
$SuperSources=$atem.GetSuperSource()
$SuperSources[0].InputFill=2001
$SSBoxes=$Atem.GetSuperSourceBox()
#Display current box values
$SSBoxes | ft
#Assign each box to object
$Box1=$SSBoxes[0]
$Box2=$SSBoxes[1]
$Box3=$SSBoxes[2]
$Box4=$SSBoxes[3]
#set options for Box1
$box1.PositionX = -4
$box1.PositionY = 6
$box1.Size = .25
$Box1.InputSource=1
$Box1.Enable = 1
#Put SuperSource on-air
$ME[0].Preview=6000
$ME[0].Cut()

Output

PS C:\Users\imorrish> $SSBoxes | ft
Enabled InputSource PositionX PositionY Size Cropped CropTop CropBottom CropLeft CropRight
——- ———– ——— ——— —- ——- ——- ———- ——– ———
1       1           -8        4.5       0.25 0       0       0          0        0
1       2           8         4.5       0.5  0       0       0          0        0
1       3           -8        -4.5      0.5  0       0       0          0        0
1       4           8         -4.5      0.5  0       0       0          0        0

ATEM SuperSource Box Configuration UI

The software panel is a but cumbersome when it comes to making a lot of settings that involve size and position of effects.

I have provided a few examples of making adjustments to things like chroma key settings using a midi device but probably the ultimate in complexity is setting the super source parameters and option for the 2 M/E.

The following screenshot is more of a teaser as I don’t have a 2 M/E right now but will try and get a video of it working soon. I’ll also be publishing a new switcherlib for PowerShell that has a full implementation of the SuperSource Box configuration options.

Panasonic PXW270 camera and AK-HRP200 CCU configuration

The last time I tried to get this combination of camera and Camera Control Unit (CCU/RCP/ROP – what ever you want to call it) working it took almost a day of searching for the required configuration settings and firmware versions. After finally getting it to work I was sure I had documented it but when I had to do it again this week for a couple of new cameras and CCU unit I couldn’t find it anywhere and search for the answer did not return any decent results.

What you need:

Software from Panasonic, CCU firmware available after 2013.

https://eww.pass.panasonic.co.jp/pro-av/support/content/download/EN/ep2main/soft/upghrp200_e.htm

This page also provides links to the following software:

Easy IP – this lets you discover the AK-HRP200 unit and change its IP if you want. The default is 192.168.0.130
Just a tip with the Panasonic software, only have one HRP200 plugged into the network (or direct to your PC) if you want to change its configuration.

Smart Configuration Tool (ROP Setup Software)

Network Settings

Set the CCU and Cameras to be on the same network.

The camera IP address is set by holding down the Menu button on the camera for more than 5 seconds, otherwise you only get the simple user menu settings.

The RCP IP address can be set by holding down the Shift and both up/down arrow keys. Then press the Select button 9 time to get to setting 10.

Enable Remote Control

The camera must be configured to allow remote control. This is in the network setting and there are two settings required to make it work.

[NETWORK SETUP] -> [NETWORK FUNCTION] -> [HTTP SERVER+REMOTE]

[NETWORK SETUP] -> [REMOTE] -> [ENABLED]

Set up a user name/password or use the camera default (guest p2guest)

Using the Smart Configuration Tool, you can tell the RCP about any cameras that it can control. The trick is to use the settings below:

Connection Mode: IP Mode

Camera Type: RemoteCamera

Camera Type: Camcorder IP

Camera Port No: 49152

Even if I have one CCU per camera, I always add the other cameras to each CCU just in case a CCU fails, you can hold down the Select button until the camera number flashes and then use the DATA SET up and down arrows to select another camera.

In the User Auth tab, set the username and password set in your camera. The RCP ships with a different default than the camera so the first time setting up the RCP you have specify the original account using the following:

Username: admin
Password: 12345

If the password doesn’t match the camera, you get a red flashing power lamp on the RCP.