FAQs
This page provides information and explanations about using Digital DNA Studio and its features.
Orchestration Server
What is an Orchestration Server?
An Orchestration Server is effectively a block of code that enables a customer to pass any kind of data between their systems and Soul Machines systems. It is a bridge that moves data both ways so that the destination systems can use it. An Orchestration Server is commonly used in Digital DNA Studio for managing conversation data for customers who are using NLPs other than Google Dialogflow, IBM Watson Assistant, or MS LUIS—standard NLP platforms supported by DDNA Studio out of the box.
Soul Machines can provide you with the basic starting code template (In Node JS programming language) for the Orchestration Server. This template is completely customizable to suit any integration needs. Note that you are required to host the Orchestration Server on your own infrastructure, and its endpoints must be publicly accessible.
You can use an Orchestration Server in Digital DNA Studio’s Default UI (aka Auckland theme) or in your own custom UI.
If I’m currently using a Custom UI with an Orchestration Server, how do I leverage this feature most easily?
If you are using a Custom UI specifically to support an Orchestration Server, you can create a duplicate of your project within Studio, set it to use the default UI, and specify your Orchestration Server details. Once deployed, you can utilize the new Digital Person and deprecate the old one.
If you are using a Custom UI for other purposes, you should continue in the same manner. If you are doing any local development, you only need to specify your Public IP, while leaving the server URL blank.
Is there a limitation in using the same Orchestration Server for different projects?
No. Servers can be referenced for multiple Digital DNA Studio projects.
Do I need to use a subnet mask when developing locally?
Yes. Typically a /32 subnet mask can be appended to your IP to satisfy this requirement.
Supported Browsers
What Browsers can I use to access a Digital Person from the web?
Digital DNA Studio enables you to deploy a Digital Person that can be accessed from the web, using the latest version of the following browsers:
Windows: Chrome and Firefox
Mac: Chrome, Firefox, and Safari
Digital People can be accessed via desktops and mobile devices.
For Auckland Theme deployed projects, the latest version of any browser that supports WebRTC such as:
Windows: Chrome, Firefox, and Edge Chromium
Mac: Chrome, Firefox, and Safari
Android: Chrome
iOS/iPadOS: Safari and Chrome on iOS 14.6 and later ( no chrome support on 14.5 or earlier)
Some social media in-app browsers are not supported.
Interactive Preview
How do I unblock my Microphone and/or Camera?
Refer to How do I unblock my Microphone and/or Camera? for detailed guidance.
CUE Features
Is the Digital Person modeled after a real person?
Originally, Digital people were modeled after real persons and they still can be if a customer wants a Digital Twin. With the Human OS 2.0, Soul Machines is now mastering the generation of Digital People through descriptions of phenotypes including parameters such as gender, skin texture, and geometries.
How does the Digital Person know when and where to gesture?
A Digital Person can support or illustrate a conversation with the appearance and disappearance of content cards such as an image, a video, a menu list, or a web object created for a custom UI. This is done by adding speech markers within its text response with the option to gaze, gesture, or point at the associated content card. Ask a Digital Person equipped with the Youtube skill “how do I repair a flat tire” and it will move to the side while the best matching video appears on screen and gaze towards it (or gesture, or point at it). As the conversation moves on, the speech marker can be set to hide the content card, if applicable, and the Digital Person can move back to the center of the screen.
How does the Digital Person know when to zoom in or out?
The position of the Digital Person is determined by the camera behavior settings in Digital DNA Studio. The Cinematic camera cuts occur even if no content is shown, and one of three camera shots (close up, wide shot, and head and shoulders) will be picked. This will occur roughly after 10 seconds and after finishing a sentence of a multi-sentence response.
Network Access and Firewalls
What domains need to be reachable to use the DDNA Studio site?
The following domains should be reachable – that is, not blocked by a firewall – in order to use DDNA Studio:
studio.soulmachines.cloud
authenticate-studio.soulmachines.cloud
entity-service.soulmachines.cloud
config-service.soulmachines.cloud
assets.cdn.soulmachines.cloud
dp-images.cdn.soulmachines.cloud
dp-images-dev.cdn.soulmachines.cloud
dh.soulmachines.cloud
dh.az.soulmachines.cloud
*.soului.dh.soulmachines.cloud
*.soului.dh.az.soulmachines.cloud
designer.soulmachines.cloud
o395550.ingest.sentry.io (looks like maybe it needs to be *.ingest.sentry.io)
This list will change over time. Any firewall also needs to permit WebSockets and WebRTC.