Genvid SDK 1.3.1¶
Welcome to Genvid SDK 1.3.1. This is a bug fix release. See other previous releases notes for more information on the content of the 1.3 release.
- [installer] Fix a false error message when the installer download the nomad url.
- [terraform] Fix bad variable in the terraform configuration for the game count variable.
- [terraform] Fix bootstrap never been set properly in genvid server scripts.
- [terraform] Fix default versions in terraform configuration.
- [js-api] Fix the UTF8ToString method to handle 3-4 bytes UTF-8 encoding (up to 21 bytes encoding). Some invalid encoding could be undetected.
- [engage] Fix a deadlock condition stopping the leaf to send data stream to the web page.
- [cloud] Use the terraform region for
save-amicommand, and allow to pass a
--regionargument for the source AMI for the
We weren’t able to fix some bugs in time for this release, but we intend to fix them shortly.
The application doesn’t work properly after Windows comes back from sleep¶
Nomad has some difficulties with sleeping jobs, including itself. This
is unlikely to get fixed in Nomad, but shouldn’t happen in production
environment. The best workaround you could have for that is to not
allow Windows to go to sleep when you are running the service, or simply
to restart the service with a
local.py reinstall (unfortunately,
local.py restart is not sufficient).
The YouTube stream isn’t properly reset after a manual restart¶
If the services are stopped and restarted shortly after, the YouTube streaming service will consider it as part of the same streaming session. Although a desirable effect most of the time, this could lead to showing up the previous session due to the long latency between the services and the actual view. A future version will provide a proper way to request a new stream, but until then, you can either reset your stream key from the YouTube dashboard or simply wait a little longer (a few minutes should be enough) before restarting the service.
Audio captures microphone, or loops infinitely¶
Since we capture audio with a loopback device, every sound going
through the machine running the game will get captured. This not only
includes system alerts or microphone input, but it also includes your
web browser. When viewing your game stream using the same machine
which is running the game, the game will also capture its own audio
stream with ~10s of latency, yielding some echo with progressively
worse sound quality (since it is compressed every time it is
streamed). The recommended workaround is to disable audio altogether
genvid.encode.input.silent = true in your config file), or to use
a separate machine to observe the website. These issues are moot when
the game is deployed in a cloud infrastructure.
Audio is out of sync¶
The audio might be out of sync by a slight margin. We intend to fix
this in an upcoming release. In the meantime, you can add delay to the
video by setting a video delay in your config file; the default value
genvid.encode.output.videodelay = "1250ms" (the format is a
string ending with
AWS servers are not working properly after a shutdown¶
If you shut down the servers, they lose their public IP addresses and
the system fails to take the new addresses into account. You must
reinstall the servers by doing a
cloud.py reinstall which takes a
very long time. We are currently working on a solution that will be
available on the official release of the cloud support.
Video capture is not supported in Unity editor¶
If you are running the stack and are attempting to start the application inside the Unity editor, you might encounter some issues. We recommend for now to run the stack only when your application is built as an executable file.
Small hang can be noticed when losing Unity application focus early¶
If you are running your Unity application with the stack and decide to proceed to a different window during the splash screen, you are bound to get a small hang several seconds later. This hang disppears when moving the mouse. This hang doesn’t affect the video, audio and data capture. We recommend to stay focused on the window around ten seconds after the application is launched to avoid this issue.