Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Current system sound IO #103

Closed
eofster opened this issue Apr 17, 2014 · 15 comments
Closed

Current system sound IO #103

eofster opened this issue Apr 17, 2014 · 15 comments
Assignees
Milestone

Comments

@eofster
Copy link
Member

eofster commented Apr 17, 2014

There should be an option to keep using system default sound IO. So that when default is changed in the OS, Telephone would also use it instead of using the previously configured and still present IO.

@derhuerst
Copy link

+1

@TobiasPfanner
Copy link

-1
I may configure my headset as the sound IO for Telephone - and listen to music over speaker at the same time. works perfectly as it is ;)

@chronum
Copy link

chronum commented Dec 1, 2014

+1
Removed USB Audio gets stuck in the setting resulting in no sound on incoming call. Using system default audio should in this case.

@SteamedFish
Copy link

+1
I set Telephone to automatically start at system boot. It'll fallback to builtin if it starts before my bluetooth headphone connects, which is not what I want.

Switched to x-lite, will switch back if this feature is added.

@kusmierz
Copy link

+1@eofster any chances to see this in the future?

@eofster
Copy link
Member Author

eofster commented Mar 17, 2016

It seems that what the majority wishes to be fixed here is not exactly this issue where Telephone has a setting to always follow sound IO selected in the System Preferences (I even don’t know yet if it is possible.) But rather the bug under the recent OS X versions when Telephone doesn’t automatically switch to the built-in sound IO when previously selected sound IO (like a headset) does not currently present and vice-versa, when a configured headset is disconnected. This must be fixed by the combination of #143 and #145.

@kusmierz
Copy link

kusmierz commented Jun 9, 2016

@eofster, #143 and #145 are now fixed. Any chances to look at this, please?

@eofster
Copy link
Member Author

eofster commented Jun 9, 2016

@kusmierz could you describe your use case?

@kusmierz
Copy link

kusmierz commented Jun 9, 2016

@eofster - normally I'm using my laptop as a... laptop (outside, in my home, etc), but I have also external LCDs, external soundcard, keyboard and mouse at the office (and I'm thinking about Thunderbolt dock/hub to connect it all by one cable), where I usually close the lid of my laptop an put it under the desk. So it appears as a desktop.

Anyway - I'm using internal soundcard when I'm at home or outside, and external soundcard (better DAC, etc) when I'm at the office.

You can also think about people using BT headset (which macOS sees as external devices) - it would be useful, especially for phone calls...

@eofster
Copy link
Member Author

eofster commented Jun 9, 2016

The situation when somebody’s using a preferred external device and expects a built-in device to be used when the external one is not connected should currently be covered. The following should also currently happen.

  1. Device A is selected in Telephone’s sound preferences.
  2. Device A is unplugged and not present in the system.
  3. A call is established.
  4. The built-in sound device is used.
  5. Device A is connected again.
  6. Telephone switches to device A automatically because it was selected before.

Or do you need automatic fallback from one non-built-in device to another non-built-in device?

@kusmierz
Copy link

Hm, indeed it changing devices as these are connected and works correctly. But in my mind, it is a little bit confusing, when there is no "system default" (such as ie. Skype has).

image

Anyway - thanks, it works to me :)

@eofster
Copy link
Member Author

eofster commented Jun 10, 2016

Well, the logic was that you might want to use a specific preferred device for phone calls, regardless of what is currently configured by default in the system. And Telephone does its best to select this device for you when it’s available.

This worked, as far as I understand from the lack of negative reports, successfully since the early Telephone releases. But then it stopped working a couple of years ago because of the changes in the OS. And it now works again in the last Telephone releases.

@eofster
Copy link
Member Author

eofster commented Jun 10, 2016

So I’m closing this issue because I currently don’t see a specific use case for “always following the default IO selected in the OS.” At least nobody wished that. And all plus-ones above are actually the complaints to a regression that has been fixed, and not related to the original topic of this issue.

@eofster
Copy link
Member Author

eofster commented Nov 4, 2016

Reopening because people really stated asking specifically about following the IO selected in the system. Other apps apparently do this and that’s what people expect.

@eofster eofster reopened this Nov 4, 2016
@eofster eofster removed the wontfix label Nov 4, 2016
@eofster eofster added this to the 1.4 milestone Jan 3, 2018
@gozoinks
Copy link

gozoinks commented Jan 9, 2018

+1. Yes, the use case is simply being able to switch between audio devices without having to make a round trip to preferences. Between bluetooth headsets, AirPods, display audio, and built-in audio, especially with a laptop, I wind up having to stop by preferences every time I place or receive a call, because I'm never sure what device it's going to try to use. If following system audio were an option, then as long as my system audio is doing what I want, then Telephone will always do the right thing. Thanks for reconsidering!

@eofster eofster removed this from the 1.4 milestone Jan 19, 2018
@eofster eofster self-assigned this Mar 2, 2018
@eofster eofster added this to the 1.4 milestone Mar 2, 2018
@eofster eofster changed the title Use system default sound IO Current system sound IO Mar 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants