S
stunbot
Entourage and its associated notification sounds worked fine until I
paired my bluetooth headset with OSX. Even though the headset was not
the preferred audio output device, Entourage insisted on using it. So
when my headset was not connected to the mac, I did not get any
notification sounds. Annoying but fairly benevolent.
Then I discovered that when I turned on my headset, and used it to
make a phone call with Skype (which does handle multiple audio devices
correctly), once my call was connected, every Entourage sound that had
not played, had been stored in a buffer, and I had to wait while they
all played before continuing with my call. Again annoying but
harmless.
Then I discovered that Entourage was starting to consume a lot of CPU
(15-25%) even when idle. Then I discovered I could no longer close
Entourage. The window would disappear, but the process kept running
and required a force quit. Finally I connected the 2 things
together. I removed my BT audio device entirely, and Entourage is
back to normal.
So in summary it seems there are a few problems with how Entourage
handles sound:
1. It chooses the wrong audio device to use for sound output. It
should choose the MacOS default sound output device, or at least allow
me to choose the correct one in Entourage preferences.
2. It buffers all sounds to be played until that audio path opens up,
and then it plays them all.
3. It won't allow the process the be ended until all sounds have
played.
Please fix this! Currently I either have to choose between having
Entourage bog down my system, or not using my headset at all.
Julian Paas
paired my bluetooth headset with OSX. Even though the headset was not
the preferred audio output device, Entourage insisted on using it. So
when my headset was not connected to the mac, I did not get any
notification sounds. Annoying but fairly benevolent.
Then I discovered that when I turned on my headset, and used it to
make a phone call with Skype (which does handle multiple audio devices
correctly), once my call was connected, every Entourage sound that had
not played, had been stored in a buffer, and I had to wait while they
all played before continuing with my call. Again annoying but
harmless.
Then I discovered that Entourage was starting to consume a lot of CPU
(15-25%) even when idle. Then I discovered I could no longer close
Entourage. The window would disappear, but the process kept running
and required a force quit. Finally I connected the 2 things
together. I removed my BT audio device entirely, and Entourage is
back to normal.
So in summary it seems there are a few problems with how Entourage
handles sound:
1. It chooses the wrong audio device to use for sound output. It
should choose the MacOS default sound output device, or at least allow
me to choose the correct one in Entourage preferences.
2. It buffers all sounds to be played until that audio path opens up,
and then it plays them all.
3. It won't allow the process the be ended until all sounds have
played.
Please fix this! Currently I either have to choose between having
Entourage bog down my system, or not using my headset at all.
Julian Paas