Announcement

Collapse
No announcement yet.

Using VoipTalker component

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Using VoipTalker component

    Hi. I am trying to setup the voiptalker component but am having trouble with it.

    Currently I am following the tutorial posted here. https://forums.unrealengine.com/deve...ion-how-to-use

    I also edited the DefaultEngine and DefaultGame ini files to enable voice / push to talk following this tutorial. https://couchlearn.com/the-easy-way-...engine-4-game/

    All I want to do right now is have a basic sound play when the begin talking event and end talking events fire.

    I created a child blueprint of the VOIPTalker component and added sounds to play attached to those events but no matter what I do those events never seem to occur.

    The first screenshot is the voiptalker child blueprint I created and the other two are screenshots of the character blueprint where the voiptalker component is added to the character on begin play and then registered to the playerstate.

    When I do play in editor on a dedicated server I can see the console command firing in the output log. However I get error messages like the two below:

    LogOnline: Warning: OSS: No game present to join for session (GameSession)
    LogNet: Join succeeded: DESKTOP-MBN4RME-19EB
    LogVoiceEngine: Error: OSS: StopLocalVoiceProcessing: Ignoring stop request for non-owning user
    LogOnline: Warning: OSS: No game present to join for session (GameSession)
    Cmd: ToggleSpeaking 1
    LogVoiceEngine: Error: OSS: StartLocalVoiceProcessing(): Device is currently owned by another user
    Cmd: ToggleSpeaking 0
    LogVoiceEngine: Error: OSS: StopLocalVoiceProcessing: Ignoring stop request for non-owning user


    I assume that means my 1 microphone is already in use by the server or something as opposed to my character? googling the error didn't bring up any concrete results when I tried.

    Thank you for any advice.
    Last edited by Carock12; 11-23-2019, 06:00 PM.

    #2
    any solution?

    Comment


      #3
      Have the same problem on android. No solution yet?

      Comment

      Working...
      X