opentsg

Make a test pattern suitable for checking your studio setup

Event Day

For the event, the software will run in the cloud, only a browser required.

Challenge

In the browser you will find a file called hackathon.ipynb. Double click on it to open it in the user interface. This special tutorial will take you about 10 minutes to run through. It will teach you how to include images, logos and other components into a test pattern that could be used for setting up displays, studios, lighting or, more importantly and complete end-to-end virtual studio.

Traditionally test charts have been very engineering oriented with elements like skin tones being overly biased to a minority of the population. If you were going to create a test chart for a twitch or tiktok or facebook streaming event then what would you put on it? Feel free to use images and ideas from the web. Show us your creativity and be prepared to explain the thinking behind your creations.

Try it out - Alpha testers

For the event, all that is required is a web browser. Everything else should be done in the cloud. If you want to test the system beforehand & run tutorials 1-9 for a full in-depth demo of how it all works, then follow the instructions below.

Alpha setup - local PC

The Docker container holds all the code and executables. Your personal test signals appear in a /usr folder in the interface. This is mapped to an otsg subfolder of your home folder on your machine. The instructions below are the bare minimum to get you going. See the comments in the start script if you need to customize how it runs on your system.

Install

Check the prerequisites . This is REALLY important.
From docker desktop or the docker website :
- amd is for 64 bit Intel or AMD Ryzen laptops - most people need this one
  - docker pull mrmxf/opentsg-amd:v0.4.1
- arm64 is for Apple silicon & arm-Windows laptops only
  - docker pull mrmxf/opentsg-arm:v0.4.1
Download the start script start.cmd from downloads
- Windows may give you a security warning. Select the appropriate Keep and then Keep it anyway or I trust this file options and download to somewhere in your PATH or somewhere that you will always start opentsg from.
- Mac doesn’t know (or care) that the file extension .cmd is a command file. Just save it to somewhere on your PATH or somewhere that you will always start opentsg from.

Start Docker desktop or start the docker daemon if the desktop option is not available.

 # only needed if you don't have docker desktop running
 sudo systemctl start docker    # for Debian / Ubuntu
 dockerd                        # for other systems

Run the docker container using start.cmd from Mac’s Terminal.app or Windows’ cmd. If start.cmd is not in your path, you should cd to the folder where you downloaded it and run it
```
: # Mac: command for Terminal.app
zsh start.cmd
: # Windows: command for user mode cmd.exe (not powershell!)
start.cmd
: # Linux: command for bash
bash start.cmd
```
if the browser does not start automatically, then look in the logs and copy the start address and token for your machine. It will look like this, but with a different token:
```
http://127.0.0.1:8888/lab?token=3b3ecb922417c0835f8fb26dfd6424a7ec114acc0f1308ef
```

Alpha software - usage

All tset signal definitions and patterns saved in the /usr folder of opentsg-lab will be preserved in the otsg subfolder of your home folder. Any other saved data will probably be reset when to restart the container from the image!

Always save your new work in the /usr folder if you want to keep it.

opentsg

Last modified 2024-10-24

refactor( 87d95c9 )