Magic Leap Voice DemoMagicLeap Scene must connect twice to get voice both directions

Options
Hi we are integrating PUN Voice for Magic Leap. After some fiddling we have things working (yay!)

Note that forcing (hard coding due to demo implementation), a custom room name PhotonStatusDisplay.cs helps ensure a match.

An observation for those that are exploring: Using Magic Leap Remote with Unity to test voice (using an actual ML1) does not work. You have to push the app native to the headset to get a working voice connection.
Q?: Is this currently a known limitation or something related to Unity setup?

When connecting two devices to a room, for the 2nd connection (the client), upon first connection, the master hears the client's sending audio, but the client does not hear the master's unless one of the two has left and re-joined the room, at which point audio is bi-directional.
Q?: Is this a known bug or do you have any recommendations on how to fix that so it works on the initial connection? Could this be a firewall or port forwarding issue?

Thanks for your advice.

Comments

  • JohnTube
    JohnTube ✭✭✭✭✭
    Options
    Hi @makeSEA,

    Note that forcing (hard coding due to demo implementation), a custom room name PhotonStatusDisplay.cs helps ensure a match.
    I don't know what do do with this. What demo? What limitation? there is no PhotonStatusDisplay.cs in Photon Voice.

    Q?: Is this currently a known limitation or something related to Unity setup?
    We can't help you with Magic Leap or Unity related questions here.

    Q?: Is this a known bug or do you have any recommendations on how to fix that so it works on the initial connection? Could this be a firewall or port forwarding issue?
    Clients should be able to hear each other since they join the room. Can you reproduce this with the demos? It has nothing to do with the firewall or port forwarding. It's related to the workflow of voice stream linking maybe (Init local Recorder(s) + Send Voice Info to remote clients + link local Speaker(s) to remove Recroder(s), etc.) or a timing issue.
  • makeSEA
    makeSEA
    edited June 2019
    Options
    Hello, I have found that the stream is successful on connection first attempt most of the time when using the native app on the ML One. Using ML Remote plus the ML One is a bit more flakey.

    Once we got it working predictably it has been very stable. Thank you!