Hi TJ,

that article says the symptom is the following message:

WARNING: 140: This application, or a library it uses, is using the deprecated Carbon Component Manager for hosting Audio Units. Support for this will be removed in a future release. Also, this makes the host incompatible with version 3 audio units. Please transition to the API's in AudioComponent.h.

being reported on the OS X system console. Are you getting that when you run WSJT-X on El Capitan?

Other users are using WSJT-X on El Capitan without issue as has been reported on this list. What caused you to try the 10.11.02 beta release of OS X rather than the current GA release 10.11.1?

73
Bill
G4WJS.

On 21/11/2015 18:49, TJ Campie wrote:
This post accurately describes the issue which seems to affect other apps too.

http://www.machamradio.com/blog/2015/10/22-fldigiwsjt-x-and-pulseaudio-on-os-x-10111

TJ
On Nov 21, 2015, at 12:41 PM, Bill Somerville <g4...@classdesign.com <mailto:g4...@classdesign.com>> wrote:

Hi TJ,

that implies that the issue is at a lower level than the WSJT-X code.
Maybe a driver or operating system issue. Are there any driver updates
available for your audio device?

73
Bill
G4WJS.

On 21/11/2015 18:32, TJ Campie wrote:
It still shows the 590 sound card

I should also note that wsjt-x worked fine in 10.10.

On Nov 21, 2015, at 11:09 AM, Bill Somerville <g4...@classdesign.com <mailto:g4...@classdesign.com>> wrote:

On 21/11/2015 16:11, TJ Campie wrote:
I have been trying to solve my issues on OS X (10.11.2 beta) without
success.  I am using a TS590s with the build in audio interface and
after one or two transmissions, the app decides it doesn't want to use
my built in soundcard anymore and starts going over the default
soundcard for the system.
Hi TJ,

after this unwanted switch occurs, what is showing in the
"Settings->Audio" panel for the input and output devices? The state
while WSJT-X is still running and after restarting is of interest.

73
Bill
G4WJS.

------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



------------------------------------------------------------------------------


_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to