[ad_1]
Two years ago, Apple removed the headphone jack from its mobile devices and said it was brave. the Kool-Aid In theory, by getting rid of this old analog port, we were all free to pay for new devices with the same features on a different connector or to buy the new Apple AirPods. Oh, and supposedly that would simplify and streamline the consumer experience by removing the abilities that no one wanted to get rid of in favor of a less effective solution with a dongle. The dongle is very important.
A recent PCWorld article clearly shows how fundamental this idea was. Despite the fact that USB-C audio should be well established and work perfectly now, instead, it has made things worse. And the problem comes down to what might well be a fundamental flaw in the USB-C standard – it's too complicated. By attempting to create a multitude of use cases, cable support levels, and feature sets, the USB USB (IF) forum may have built a standard on which consumers will never actually be able to operate. as a reference.
One of the most basic assumptions we make about standards is that cables and devices that meet these standards will work when connected to compatible hardware. While it is true that there are exceptions to this rule, you do not have to worry about whether your HDMI or DisplayPort cable supports certain resolutions or features. unless you work with much older cables. You can usually assume that a micro USB cable is a micro USB cable and that a USB device will work on a USB port. The situation with USB-C audio is much more complex, thanks to the difference between dongles that include a digital-to-analog converter and those that are not. The first type is digital, the second is analog. Ung writes:
The first problem is the lack of basic compatibility. For example, if you take the USB-C dongle supplied with a Motorola Z2 Force or a Sony Xperia XZ2, it will not work with a Google Pixel 2 XL, a Samsung Galaxy S8 or a OnePlus 6. The USB-C dongle comes with the Pixel 2 XL, it will work on all those phones, just like the USB-C headset that Huawei includes with its P20 Pro. But take the USB-C dongle that is also in the box with the Huawei P20 Pro and try it on your partner's Pixel 2 XL.
Image by PC World
It becomes even more strange. As Ung points out, the Libratone Q ADAPT headset will work with music across a wide range of devices, but only supports phone calls associated with Pixel and Pixel 2. Google sells a USB-C dongle with a DAC and the pixel. 2 XL come with only one – but if you try to connect a USB-C analog dongle (without DAC) in a Pixel 2 XL, the device will not play sound even if the phone's SoC contains an integrated DAC. Why not? Because Google has not enabled the feature. On some phones, you need to enable USB storage for the USB-C dongle to work properly. There is no explanation for this.
The restrictions are device-specific and are not always well communicated. The Razer phone, for example, will simply not transmit audio via an analog dongle and will not explain why you are getting no sound.
But the long and the short is as follows: the experiment did not work. If you have a device with a 3.5mm headphone jack at the end of it, you can almost certainly count on the audio output when you make the right connection. With USB-C audio, the whole situation is complicated. The third-party support and utility are device-specific, which is exactly the opposite of what a standard is supposed to provide. Companies like Apple will never see this as a bad point, because its solution is to buy more branded material at any price. But for everyone, this foray into the new world of USB-C audio solutions has a cost of use.
It's time to do something brave and bring back the headphone jack.
Now read: Apple kills the headphone jack and calls for courage, Apple is preparing the blitz of new iPhones and is USB-C pursuing an unattainable goal?
[ad_2]
Source link
