Audacity Forum

Have you tried zapping the pram? Hold down option-command-p-r right after the startup sound to do so...

Zapped the pram. No change whatsoever.
I'm sending the headphones back for repair.
Want them to tell me whether these headphones are compatible with macOS, something I'm beginning to doubt.

They should be, as they use OSX's built in USB audio class driver AFAIK.

But I'm beginning to doubt that.

I've seen other problems with Sennheiser's USB headphones. And I know the USB audio class driver works well on OSX as there are numerous devices out there that use it. I have a number of those myself and they never fail. Not even if I unplug while playing or recording sound.

They should be, as they use OSX's built in USB audio class driver AFAIK.
But I'm beginning to doubt that.
I've seen other problems with Sennheiser's USB headphones. And I know the USB audio class driver works well on OSX as there are numerous devices out there that use it. I have a number of those myself and they never fail. Not even if I unplug while playing or recording sound.

Cyrano,
See this:
http://www.computeraudiophile.com/f8-ge ... ter-29674/
Thanks

Thanks for the info.

Apple didn't drop support for USB 1.1 audio class. It's a bug in some Intel chips in some Macs and I believe it has been fixed by a system update. I'm not sure as I don't have one of the affected machines around.

Apple did drop support for Firewire audio class. But that only affects Apogee interfaces. And one other, the Griffin Firewave. Maybe that's where the confusion is coming from?

Besides, I think the Sennheiser USB headphones are USB 2 audio class compliant. They need that to be somewhat compatible with USB3 ports...

cyrano wrote:Apple did drop support for Firewire audio class. But that only affects Apogee interfaces.

Why does that only affect Apogee interfaces?

steve wrote:

cyrano wrote:Apple did drop support for Firewire audio class. But that only affects Apogee interfaces.

Why does that only affect Apogee interfaces?

I think this probably explains it https://discussions.apple.com/thread/72 ... 0&tstart=0. The takeaway seems to be that Apple Firewire support continues after a fashion for most Firewire interfaces that continue to update drivers for the new Mac operating systems and which can work with a Thunderbolt to Firewire adaptor.

I am not clear at all whether the new MacBook with USB-C only can accept Firewire input with USB-C > Thunderbolt and Thunderbolt > FireWire adaptors. Focusrite says no https://support.focusrite.com/hc/en-gb/ ... ith-USB-C-.


Gale

steve wrote:

cyrano wrote:Apple did drop support for Firewire audio class. But that only affects Apogee interfaces.

Why does that only affect Apogee interfaces?

Because Apogee is/was the only manufacturer using FW audio class. The only other device using it, disappeared from the market many years ago. That one, the Griffin Firewave was more consumer oriented and didn't sell well because it was expensive, compared to USB interfaces.

Apogee, OTOH, is professional high-end gear. And it is, or was, Mac only.

Gale Andrews wrote:

steve wrote:

cyrano wrote:Apple did drop support for Firewire audio class. But that only affects Apogee interfaces.

Why does that only affect Apogee interfaces?

I think this probably explains it https://discussions.apple.com/thread/72 ... 0&tstart=0. The takeaway seems to be that Apple Firewire support continues after a fashion for most Firewire interfaces that continue to update drivers for the new Mac operating systems and which can work with a Thunderbolt to Firewire adaptor.

Correct. The TB to FW adapter works with all interfaces I know of. So as long as there's a driver, no problem.

I am not clear at all whether the new MacBook with USB-C only can accept Firewire input with USB-C > Thunderbolt and Thunderbolt > FireWire adaptors. Focusrite says no https://support.focusrite.com/hc/en-gb/ ... ith-USB-C-.

Don't get me started on that one, Gale.

Even some of Apple's own cables aren't compatible with the newest Macbooks. One manufacturer had to scrap its entire range of docks. You can't tell what's in a USB-C port. It could contain display port, TB2 or TB3. But it might not. Some cables work in one direction, but not in the other. You can even blow up your Macbook, or your phone with the wrong cable...

It's a jungle, slowly turning into a disaster. I've never seen this kind of problems with any technology introduction from Apple, ever. And it's certainly not better on the Windows side.

cyrano wrote:Because Apogee is/was the only manufacturer using FW audio class.

MOTU (previously "Mark of the Unicorn"), RME, Focusrite, Lexicon, UAD ("Universal Audio") and more recently Behringer, and no doubt others too.

Cyrano, Gale, Steve et alia (if any)
I don't see why this thread is here,
Please, don't explain why; I'm already at the end of my tether with my issue unresolved and probably unresolvable issue and prefer not to get crazy because of sidetracking.
Thank you