It is absolutely silly that there is only a option for adding your microphone, but the developers have completely neglected the option to also add your headphones/speakers in the sound settings of Talk. What have NextCloud been thinking when building the Talk app /Desktop Client?
This is crazy and makes the app less useful. Nobody wants to have the sound from a online meeting coming out of the speakers or worse you cannot hear anything because you have no speakers connected to the system and since you have no out speaker/sound option you cannot do anything at all…
Don’t start the old trick of blaming it on the customer e.g. in this case on my Jabra headset it works perfectly fine in all other communications applications.
It is indeed a Nextcloud Talk issue in that the dev team never added the option for adding the output device.
I just saw this edit, if that is your intention, I can only recommend to take a look at the GitHub issues and if there’s none, create one. Posting it here in the hope someone sees it will not work out.
I added it afterwards because I did not wish to receive more silly stupid comments about my Jabra headset is the issue etc. as it is clearly not the issue here. The issue is how the developers built the “Talk” app and somehow missed to add an option for output sound device.
Nice to see that the issue is already to review on Github.
I really do not understand how you can miss to add the option of choosing output sound device. But hey… I guess things like this can happen and as such it did.
Its like building a Ferrari but you only add the front wheels and tires…
Quote:
As for @scubamuc…
Its sometimes better just to stay silent and not comment on a thread at alll when you do not fully understand it’s topic/subject and/or have no knowledge about it.
Everything you said/claimed, plus your recommendation was 100% incorrect and thus not useful.
Advising forum users with the incorrect advise is harmful for the whole community which I think @SysKeeper indeed agrees with.
You really should tone it down a notch or two, especially since your own posts were not exactly humble and full of your own assumptions and prejudices. To be honest, you should be happy that someone replied at all.
@scubamuc does a lot of work for this community, and if he made an incorrect assumption here, so be it. We are all volunteers, trying to do our best to help and point people in the right direction, and there is, of course, no guarantee of help, just as with FOSS in general there is no guarantee that every feature you consider essential will be implemented immediately.
By the way, with a little effort you could have found the GitHub issue yourself. But then you wouldn’t have been able to tell us how crazy and silly it is that this feature isn’t already included. Yeah, the devs clearly must have forgotten about it
Spare me for the 
