It's for DC bias. They put out a square wave on the 3.5mm sleeve pin (which isn't connected to USB ground) and then the same 50% square wave on the line channel is silence, lower duty cycle goes negative, higher duty cycle goes positive. No AC coupling caps.
-
-
OH, one of those! Yeah, it's trying to be a cheap-ass class D, and those are generally designed to assume they're driving a coil. The 51nb people use them in their audio daughtercards for the X62 and T70.
1 reply 0 retweets 1 like -
People get into trouble because the X62 has a single mono speaker, but the amp is being driven in stereo, and so most builders connect the speaker to left + and right -. Except the amp is not always driving the same squarewave to both channels.....
1 reply 0 retweets 0 likes -
"why is my computer speaker squealing all the time?"
2 replies 0 retweets 1 like -
Ha. The datasheet for this one actually lists using L- as common for both L&R in a 3.5mm application, so I assume it's the same 48 kHz square wave on both. Looks like ~393MHz = 13-bit PWM, which is better than I expected TBH.pic.twitter.com/NkbLmUMJkE
1 reply 0 retweets 5 likes -
It's kind of amazing how much you can abuse audio and it's still passable.
1 reply 0 retweets 0 likes -
Remember that time my FireWire interface went stupid and was zeroing out every other sample? I didn't notice until I tried to play back something I'd recorded on it and 50% of the time it was silence (but other audio mixed in SW worked, as did the level meters). Drove me nuts.
1 reply 0 retweets 1 like -
That definitely would have stumped me for a good long time!
1 reply 0 retweets 0 likes -
I once tried to download and use this audio: https://www.youtube.com/watch?v=HlqrwOoLW4E … The catch: The left channel is a perfect inverse of the right one. After downmixing the file was completly silent. That one took some time to figure out
2 replies 0 retweets 5 likes -
Audible at least (if you listen to the original)!
1 reply 0 retweets 0 likes
Yeah, really obvious on headphones, and suspicious enough on speakers :-)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.