The K2 Emulator is available here.
It is recommended that you install the K2 Emulator on a dedicated machine or a virtual machine such as Microsoft's Virtual PC. The reason for this is to not conflict other Grass Valley software that you may have installed or other components that you may have installed for other development efforts (e.g. another Microsoft database that conflicts with the MSDE database we install for the emulator).
K2 Classic Download:
Click here to download the K2 Emulator Prerequisites Installer - Size: 152 MB
Click here to download the K2 Emulator - Size: 25 MB version 188.8.131.520 updated Sep 29, 2009
Test Clips are also available for downloading and importing into the K2 Emulator. Click here to download them.
The PC requirements for the emulator are the same as the ControlPoint PC System Requirements.
- ver 184.108.40.2068 - fixed UI flicker that kept switching between Play and Record panels.
- ver 220.127.116.111 - fixed HD config files. Also changed config files so working bins are set to C:\default instead of V:\default.
- ver 18.104.22.1686 - you can now record "fake" clips. The stop button also now works on playback.
- ver 22.214.171.1246 - successfully tested RS422 protocol control using a RocketPort Plus 2P SMPTE PCI card
- ver 126.96.36.1999 - you can now enumerate assets via AMP. The emulator uses the C: drive instead of the V: drive. There were some hard-coded "V:" path issues in the AMP listener code that have been resolved.
The K2 Emulator is the full K2 software with the hardware codec portion emulated. That means:
- You can load a clip in AppCenter and press play. The application will show the clip playing and the time code will progress, but since there is not a real decoder, you cannot see the output displayed anywhere.
- You can record a "fake" clip. You will record with growing length. It will not have a thumbnail since there is no real video to decode.
- Transfers and FTP are supported.
- All APIs are supported - AMP, BVW, VDCP, and AppServer over both Ethernet and RS422 connections.
- RS422 protocol control has been successfully tested using a RocketPort Plus 2P SMPTE RS422 PCI card. However, a USB Digi Edgeport/4 RS422 converter box was not recognized by the K2 emulator.
1. First, install the K2 Emulator Prerequisites (download from link above). Unzip the prerequisites zip file and run "setup.exe". This installs:
- Microsoft MSDE 2000 Desktop Engine
- Direct Show 9
- MSXML 4
- .NET 1.1, 2.0, and 3.0
- Visual C++ 2005 SP1 redistributable
- QuickTime 7.0.4
- Install Shield MSI
2. Next, install the K2 Emulator (download from link above). Unzip the emulator zip file and run "setup.exe".
After the emulator is installed it will ask to reboot your system. Say Yes.
The K2 Emulator can be configured as:
- an SD system with channels C1, C2, C3, C4
- an HD system with channels R1, P1, R2, P2
The default configuration is an SD system.
To change the configuration to an HD system in the c:\profile\config directory:
- copy hd-config.xml to config.xml
- copy hd-systemInfo.xml to systemInfo.xml
To change the configuration to an SD system in the c:\profile\config directory:
- copy sd-config.xml to config.xml
- copy sd-systemInfo.xml to systemInfo.xml
To change the configuration to use PAL and not NTSC in the c:\profile\config directory:
- copy config.xml to ntsc-config.xml
- edit config.xml by replaceing all the “Format525_29_97Hz_2To1” with “Format625_25Hz_2To1” and save config.xml.
Make sure that the config.xml and systemInfo.xml are not set to read-only. The emulator needs read/write access to these files.
1. Click Start / Run and type "log". This starts the K2 log viewer so that you can see the services starting up.
2. On the desktop, double-click "WinRtpMgr". This starts the K2 services.
3. Watch the the log viewer for startup messages. Be patient.
4. If you do not have an RS422 serial card connected you will likely see "invalid serial port" messages. This is normal and expected.
5. Look for messages that all controllers (channels) are created. At this point the services are up and running.
6. Start AppCenter either from the WinRtpMgr icon or the desktop.
7. Login using an administrator username and password that you have setup for your system.
AppCenter has a default 30-day trial license. Contact GVDeveloperSupport@grassvalley.com to extend it.
From here on you can use the WinRtpMgr GUI to start AppCenter and start/stop the services.
- Imported MXF files do not show thumbnails of the clips correctly. Imported GXF files do not have this problems.
- FTPing to the emulator results in files in the V: drive instead of the C: drive. These will not be accessible from the Emulator. The best way to import or export files to the emulator is to useAppCenter's "Send To..." and "Import..." menu options.
- Striping clips does not work in the emulator. It depends on a lower level driver that is not present in the emulator.
- In AppCenter in a channel's Option / Timecode panel, if you choose any of the “Recorded Timecode” choices, the value that will be used is just a simulated timecode that is ever-increasing. The reason for this is that on a real K2, timecode information is provided from hardware (and that hardware interface is only simulated by the emulator). However, if you choose the “Generated Timecode” option in the emulator, when playing back a clip you will get a timecode that is relative to a clip starting point of 00:00:00,00. On a real K2 of course, all timecode modes are supported, and if you choose “system clock” as the time of day source, and select the “Time of Day” timecode mode, you would be able to record clips using the system clock as their timecode source.
- Scheduled context changes are not implemented in the K2 Emulator. On a real K2 Client these are messages we pass to the real-time system telling it to do something at a specified timecode (e.g. start playing at timecode "xx:xx:xx.xx"). Pre-roll commands in protocols are also implemented using scheduled context changes. So for testing purposes with the emulator, you can still watch the log output to see that a "Play" command is received.
1. Installation trouble or conflicts on start-up:
We seen conflicts when other software is already installed. This could be other Microsoft databases (MSSQL, MSDE, etc) or other Grass Valley software (Profile software in c:\profile). One way that you can guarantee that you are dealing with a clean environment without having to make changes to your system is to install the emulator on a virtual PC. This will give you an isolated environment to run in without requiring you to change your software.
2. Cannot login to AppCenter or cannot see and control channels in the emulator:
When AppCenter starts it checks to see if a user has administrator rights before granting access to channels. It is checking for administrator rights by looking for one of these conditions:
a. user is part of the group "BUILTIN\\Administrators" (this works for US versions of Windows XP), or
b. user is part of the group "\K2Administrators".
If you are using a non-US version of Windows XP, there are two ways of resolving this problem:
- Change all of your Windows "Regional and language options" to "US / English"
- add your username to the "BUILTIN\Administrators" group
- login to AppCenter with username.
- create a local group name on the emulator machine called "K2Administrators".
- create a new local user on the same machine and make them a member of the "K2Administrators" group.
- restart AppCenter and login with the new username.