@yuri.kim are you using the USD Viewer Kit app created from a Template in kit-app-template repo; and if so, are you launching the kit file that has “streaming” in its name?
From the screenshot, maybe you’re trying to use Firefox as the browser? My experience is that the example doesn’t work at all with Firefox, whereas I get farther if I use Chromium as the instructions indicate. (Though I have my own issues past that, which I just posted in a separate thread…)
I have a related issue. I am able to startup the USD Viewer Kit streaming app and also the web viewer sample and the streaming works. Also across machines within the same local network.
(BTW, only 106.3 builds OK, all other versions fail to build. and 106.3 only builds if I clone and build ‘main’ before (which also fails) and then switch to 106.3. It’s super weird.)
But when I try to attach another browser to :5173 it just tells me “waiting for stream to begin”.
How can I stream to multiple machines? It looks like only the first browser grabs the stream.
What might be related is webRTC. I am not sure it’s something included by default when you build the basic example?
The documentation states: “You will want to integrate the omniverse-webrtc-streaming-library. The library provides the AppStreamer class which enables both the streaming and messaging capabilities.” but it doesn’t say how.
I just found documentation Run the Solution — Guide: Embedded Web Viewer
stating “This example provides a peer-to-peer streaming solution. One USD Viewer can be streamed to one client. If you open many browser tabs, then only one can use the streamed application at any given time.”
So, how would I get streaming to more than one client?
@robert.karban Unfortunately you cannot get streaming to more than one client with our streaming technology. If you require WIDE streaming to multiple users, that would be done through our GDN network, which is a paid system. Or you can simply use any other web broadcasting tool, like Go to Meeting etc.
You know what, you are right. The docs do say that, and I am sadly going to admit that this document is actually wrong. WebRTC only supports one client at a time. So I apologize that this document page has made this false claim. I have immediately filed a ticket to get this edited out. Thanks for pointing this error out to me.