

- #Problems with onyx blackjack and osx el capitan install
- #Problems with onyx blackjack and osx el capitan update
- #Problems with onyx blackjack and osx el capitan software
Above all, avoid any software that purports to change the look and feel of the user interface. such as “themes,” "haxies," “add-ons,” “toolbars,” “enhancers," “optimizers,” “accelerators,” "boosters," “extenders,” “cleaners,” "doctors," "tune-ups," “defragmenters,” “firewalls,” "barriers," “guardians,” “defenders,” “protectors,” most “plugins,” "virus scanners,” "disk tools," or "utilities." With very few exceptions, such stuff is useless or worse than useless. Incompatibility with third-party software is by far the most common cause of difficulties with system updates. Before installing any Apple update, you must check that all system modifications that you use are compatible. Remove them when they are no longer needed.
#Problems with onyx blackjack and osx el capitan install
Don't install such modifications unless they're absolutely necessary. Keeping up to date is especially important for complex software that modifies the operating system, such as device drivers.

Otherwise you have to check yourself on a regular basis. Some third-party applications from other sources have a similar feature, if you don’t mind letting them phone home.
#Problems with onyx blackjack and osx el capitan update
In the App Store or Software Update preference pane (depending on the OS version), you can configure automatic notifications of updates to OS X and other Mac App Store products. If you get an indication that a backup has failed, don't ignore it. In fact, don’t rely on any single backup method, such as Time Machine. Backing up to a cloud-data service is one way to meet this need, but don't rely exclusively on such backups. Keep at least one backup off site at all times in case of disaster. A copy of a backup doesn't count as another backup all backups must be made directly from the original data. Make two or more backups of all your files Having the same issue with my Onyx Blackjack plugged into a thunderbolt display:ġ/4/16 9:00:20.000 PM kernel: USB Sound assertion in /BuildRoot/Library/Caches//Sources/AppleUSBAudio/AppleUSBAudio-302.15/AppleUSBAudioIsocPipe.cpp at line 86ġ/4/16 9:00:20.000 PM kernel: USB Sound assertion in /BuildRoot/Library/Caches//Sources/AppleUSBAudio/AppleUSBAudio-302.15/AppleUSBAudioEngine.cpp with return 0圎00002BC at line 2181ġ/4/16 9:00:20.000 PM kernel: USB Sound assertion in /BuildRoot/Library/Caches//Sources/AppleUSBAudio/AppleUSBAudio-302.15/AppleUSBAudioIsocPipe.cpp at line 152ġ/4/16 9:00:20.000 PM kernel: USB Sound assertion in /BuildRoot/Library/Caches//Sources/AppleUSBAudio/AppleUSBAudio-302.15/AppleUSBAudioIsocPipe.1. Nov 7 13:08:42 ebmbp-rd : > faqrp_startTimebaseAndAudioQueue signalled err=-66681 (err) (FigAudioQueueStart(now) failed) at /Library/Caches//Sources/CoreMedia/CoreMedia-1731.15.20/Prototypes/RenderPipelines/FigAudioQueueRenderPipeline.c line 1231 Nov 7 13:08:42 ebmbp-rd kernel: USB Sound assertion in /BuildRoot/Library/Caches//Sources/AppleUSBAudio/AppleUSBAudio-301.52/AppleUSBAudioIsocPipe.cpp at line 152 Nov 7 13:08:42 ebmbp-rd kernel: USB Sound assertion in /BuildRoot/Library/Caches//Sources/AppleUSBAudio/AppleUSBAudio-301.52/AppleUSBAudioEngine.cpp with return 0圎00002BC at line 2171 Nov 7 13:08:42 ebmbp-rd kernel: USB Sound assertion in /BuildRoot/Library/Caches//Sources/AppleUSBAudio/AppleUSBAudio-301.52/AppleUSBAudioStream.cpp at line 4737 Nov 7 13:08:42 ebmbp-rd kernel: USB Sound assertion in /BuildRoot/Library/Caches//Sources/AppleUSBAudio/AppleUSBAudio-301.52/AppleUSBAudioIsocPipe.cpp at line 106

Basic functionality like this shouldn't really be broken.

I hope Apple gets this sorted out in a patch. Workaround for me right now is to hook it up directly to the Mac's USB port. Encountered the same issue with an external DAC (Fiio E-17), but only when connected through a USB port or Thunderbolt display.
