Page 1 of 1

Teamspeak 3 voices not being heard

Posted: Sun Aug 13, 2017 6:47 pm
by CVROY
When using action to record games All sounds are clear and fine except other people on Teamspeak 3. They are 98% inaudible. You can hear something but you can't really tell what it is. All game sounds are loud and clear, My voice is perfectly fine as I assume it is taking it directly from the mic and not through Teamspeak 3. Is there an issue with ACTION! getting the sound from Teamspeak 3 making it so you cannot hear the other players??? As a side note, when I use Geforce Experience to record game footage All sounds are perfectly audible. You can clearly hear the other players in Teamspeak 3. Could you folks take a look at this and get it remedied because I like your software a lot better however I would like to capture other peoples voices in game as well.

Re: Teamspeak 3 voices not being heard

Posted: Mon Oct 09, 2017 1:48 am
by CVROY
This is still an issue even after the most recent update. Cannot hear other teamspeak 3 voices in recording done with ACTION!

DEVS, any work on this???

Re: Teamspeak 3 voices not being heard

Posted: Wed Oct 11, 2017 8:18 pm
by CVROY
The record what you hear #24 in your product feature list is not true until it records teamspeak 3 voices with all the system audio... as it so claims to do.

This has been an issue for months actually. Please look into rectifying it, that would be awesome!

Re: Teamspeak 3 voices not being heard

Posted: Wed Oct 25, 2017 1:30 am
by CVROY
Still cannot get it to play incoming teamspeak 3 voices. Absolutely nothing works. Teamspeak 3 must be sent to audio in some fashion that ACTION! cannot utilize properly. I'd love to use this program however I am currently stuck using Geforce Experience because it captures all audio (truly). They even just implemented multi track recording options so you can separate your voice etc. You guys better get a move here, that's all I'm saying...

Re: Teamspeak 3 voices not being heard

Posted: Sat Oct 28, 2017 3:47 am
by CVROY
Seriously, does anyone else have this issue with ACTION! + Teamspeak 3?