MiniPrem

uneeq's platform 2 0 update allows customers to install the uneeq digital human renderer (aka "renny") on any compatible system for most customers, miniprem (short for miniature on premise) is used on a single desktop or laptop equipped with a compatible graphics card capable of running the image prerequisites ubuntu 24 04 system with root access cpu high end intel 14th generation / amd zen 5 or newer cores 8 or more ram 32gb or more nvme ssd size 256gb or more speed pcie 4 0 or better nvidia rtx gpu nvidia geforce rtx 4080 / 6000 ada or better gpu memory 16gb or better driver version 535 183 01 (or later compatible version) cuda version 12 2 (or later compatible version) google chrome version 124 or newer step 1 p2 portal access & setup navigate to p2 portal complete the sign up process if you have received a direct invitation, but it is your first time accessing the p2 portal, you still must complete the sign up process to set your authentication information log in to access your dashboard create a tenant within your environment or select one of the existing tenants check the box private rendering pool and then click save click the pencil icon for the tenant you've just created and create an api key copy the api key to a safe place, it will not be displayed again step 2 download & installation the miniprem installer includes functionality to do the following checks to make sure the machine meets some minimum hardware specs checks to make sure the nvidia graphics drivers are installed and are operational checks to make sure google chrome is installed and its version is sufficient installs any software packages it needs either for the installer itself to run, or for miniprem to operate this includes installing docker and the nvidia container toolkit (so gpu enabled containers can be run) it also performs a check after installing these to ensure they are operational pulling the required docker images for the renderer and audio2face takes configuration specified by the user (described below) and fills out required config files steps for running the installer download the miniprem installer package wget presales services uneeq io/uneeq internal/ miniprem v1 10 bcb6a93 zip extract and navigate to directory unzip miniprem v1 10 bcb6a93 zip cd miniprem run the installation script (please note this can take a bit of time as it has to install many packages and pull some large docker images) /install miniprem sh step 3 configuration details during installation, you'll need to provide at least one tts provider, either azure or eleven labs here is a list of everything the installer will request signaling server leave as default api key & tenant id located in p2 dashboard click the pencil icon on the tenant you've created previously to retrieve the tenantid click '+' to generate new api key (if you did not already in the step above) copy and paste into the shell when prompted azure configuration provide your azure region provide your azure api key eleven labs configuration provide your eleven labs api key renny image configuration use facemeproduction/renny 0 513 79a70 docker hub authentication uneeq will provide temporary authentication information for docker hub where the image will be pulled from contact your delivery specialist for details step 4 starting the containers having successfully completed the installation process the miniprem services can be started using the miniprem sh script /miniprem sh start similarly to stop the services use the following command /miniprem sh stop step 5 verification check container status docker ps verify in p2 portal confirm renderer availability you will see within the tenant where you've registered renderers available rendering capacity 1 create new persona click "start" use default configuration click "launch" from within the running session, you will be able to send speak commands to the digital human and they will repeat this text back to you this confirms both rendering and the text to speech services are fully operational next steps integration your conversation layer with your digital human please see conversation platform integration for details debugging during installation the installer script creates a log of everything it does for reference later (or providing to your delivery specialist for diagnosing issues) the latest log is stored in the root directory in a file called install miniprem log older logs are stored (moved there) in the logs directory using filenames including the date and time if you have issues running the renderer application or starting sessions you can inspect the logs using the following command docker compose logs f renny you should also obtain the javascript console logs for the session if applicable framerate issues in the case of framerate issues one simple thing to check is to run top and inspect cpu and memory usage additionally, while a session is running run nvidia smi and inspect gpu memory and gpu utilisation metrics additional troubleshooting remote access consider installing either anydesk or teamviewer so the customer can provide remote access to one of our delivery specialists should the need arise if the digital human starts but does not respond cd inside the docker directory verify the contents (cat, nano, vim) of configuration dat { "server" " prod global ", "tenantid" "3f3122 5555 5555 o5o5o 99aexample7823", "jwssecret" "mm99examplexi3n/cz3r3h32exampleq9iydxfkwunnuww0g9vmdrbxq2c3ko0c9m/" } the tenantid is available from the uneeq admin portal the jwssecret is their api key verify by acccessing a customer account and before clicking on any tenant name, click the pencil/edit icon to the right of a tenant verify the tenant id matches in configuration dat the jwssecret is the api key which you can verify on the same admin page, by scrolling to the security section if the digital human does not start at all / audio2face errors nvidia / audio2face troubleshooting when starting miniprem, if you see an error related audio2face container audio2face with emotion error there could be an issue with the gpu card or driver check card and driver status verify card is physically installed lspci | grep i nvidia check if drivers are installed dpkg l | grep nvidia driver lsmod | grep nvidia if no output, no nvidia modules are loaded check if drivers are working nvidia smi a typical nvidia smi output should look like this copy+ +| nvidia smi 545 xx xx driver version 545 xx xx cuda version 12 x | + + \| gpu name persistence m| bus id disp a | volatile uncorr ecc | \| fan temp perf pwr\ usage/cap| memory usage | gpu util compute m | \| | | mig m | |===============================+======================+======================| \| 0 nvidia geforce off | 00000000 01 00 0 on | n/a | \| 30% 45c p8 16w / 200w| 456mib / 8192mib | 2% default | \| | | n/a | + + key things to look for driver version (top line) gpu name if you get a command not found error, it means the nvidia drivers aren't installed if you get "nvidia smi has failed" error, it usually means either the drivers aren't properly loaded there's a conflict with secure boot the drivers aren't compatible with your current kernel (re)install nvidia drivers update ubuntu linux first and then install latest available nvidia driver sudo apt update sudo apt install nvidia driver before rebooting, verify loading the nvidia drivers manually sudo modprobe nvidia if you see this specific message error could not insert 'nvidia' key was rejected by service the issue is that the system is rejecting the nvidia module, likely due to secure boot / uefi being enabled the bios must be accessed upon restarting (via del or f12 or similar during boot to access the bios) to disable secure boot while typically drivers from nvidia are digitally signed from official ubuntu repositories, sometimes an update or a change to the kernel might cause gpu drivers not to load once secure boot is disabled, you should be able to verify again if nvidia drivers are loaded lsmod | grep nvidia if no output, no nvidia modules are loaded updating renny edit docker/docker compose yml facemeproduction/renny 0 xxx xxxxx note keep the colon ( ) between renny and the tag stop & update containers docker compose down docker compose pull note this process can take several minutes to download verify installation docker images should show both old and new renny versions start containers docker compose up d you should see 3 containers starting, eventually all saying healthy if the digital human loads but isn't speaking get container info docker ps # note the container id for renny check logs r eplace \[container id] with renny's container id docker logs f \[container id] search logs for "tts" to check text to speech related issues review 5 lines before and after any tts mentions