Eric_WVGG
About
- Username
- Eric_WVGG
- Joined
- Visits
- 142
- Last Active
- Roles
- member
- Points
- 3,292
- Badges
- 2
- Posts
- 971
Reactions
-
Lightning versus USB-C: Pros and cons for the iPhone
This article doesn't mention two of IMO the most interesting properties of Lightning.The first is that Lightning isn't simply a proprietarily shaped USB connection. Instead, it's a system where the pins can be re-assigned to different communication protocols. For example, one might make a lightning-to-RGB-video cable. This wouldn't be like a dongle or a conversion cable, where a USB device is talking to an interface board (like the old style USB-to-serial or USB-to-PS/2 connectors of the nineties); rather, it would allow an iOS device to send a native RGB video signal down the cable.This move has its roots in how the old Apple Dock Connector could transmit raw video and audio signals, on top of the USB and other pinouts that were in that beefy plug. I've never seen any Lightning cables that did anything other than a USB signal in the wild, though.The other thing is regarding the design of the lightning connector. There's a little tab on the plug; that's the weak point in the connection, if it ever breaks, it's almost certainly going to be due to the tab breaking. It's not a big deal, though; the tab breaks, you just get a new lightning cable.Now most folks might not realize this, but USB-C has a little tab too; except that for USB-C, that tab is on the device. Look inside the port on your Macbook or iPad, you can see that little guy in there; the USB-C plug is actually a sleeve that fits over the tab.The thing is, that tab is still the weak point in the connection; but now, when the tab breaks off, it's your Macbook or iPad that is damaged, and more likely than not it's a non-repairable part. (not the case with Mac Studio, actually, but I digress). Say what you will about industry compatibility or proprietary parts, but on a purely technical level, Lightning is a far better designed connector than USB-C.In an ideal world, Apple would have given away the license to the Lightning connector to the USB Consortium and said "hey, this should be your design for USB-C, have it, it's yours." USB-C would be a better plug, and Apple wouldn't be in this position of having to change ports and make an entire ecosystem of accessories obsolete. c'est la vie -
Apple wiped all but one third-party SDK from Shazam for iOS in last update
seanismorris said:Wow.
Shazam had a ton of crap included...
I probably would have banned Microsoft's HockeyApp on principle.
A “beta testing and management service deployed through Azure” is named HockeyApp? That’s not suspicious... -
Mac mini: What we want to see in an update to Apple's low-cost desktop
Damn. Those are cool. I'm nearly positive they are in violation of the USB 3.1 spec, but I'll be grabbing a couple anyway.
[edit] Here it is, courtesy of some wonk:
This adapter does NOT comply with the USB Type-C specification version 1.1 section 2.2 of the specification which states the following :
"USB Type-C receptacle to USB legacy adapters are explicitly not defined or allowed. Such adapters would allow many invalid and potentially unsafe cable connections to be contructed by users."
This is because if you combine this adapter with a USB Type-A to Type-C cable, you may create a dangerous condition where two power supplies may be connected together opposing each other using the combined cable.
Furthermore, this adapter violates Section 2.3.1 :
"Power is not applied to the USB Type-C host or hub receptacle (VBUS or VCONN) until the DFP detects the presence of an attached device (UFP) port."
In my testing, even when no UFP device is attached, this receptacle port's VBUS line is powered on at 5V. It should only be at 5V when a UFP device is present.
This adapter and port violates Section 4.5.1.2.1 - Please see figure 4-5. A correct DFP receptacle must use two distinct Rp resistors. According to my testing, the CHENYANG adapter leaves the CC lines completely floating, with no Rp at all on either CC pin.
This means that the Chromebook Pixel 2015 does not detect a charger device at all, as it depends on the presence of Rp to start charging.
Finally, this adapter also claims to support USB 3.1 SuperSpeed, but because it is only a passive adapter, there is no way to support both orientations of a potential USB device as that requires a mux on the receptacle end. Indeed, when I tried it, it would only ever enumerate a USB-C thumbdrive as high speed (usb 2.0).
Long story short : This adapter is a type forbidden by the USB Type-C specification, and should NOT exist. It gets my lowest rating of 1-star because there is no simple thing that the manufacturer can do to make this adapter correct.
-
WWDC19: SwiftUI was the brightest star in a galaxy of new ideas
-
USB-C group hopes new logos will solve customer confusion
-
16-inch MacBook Pro review: The keyboard is probably enough to convince those waiting
> And, Apple tells us that individual keys can be replaced. We didn't get any information on what this entails, but at this juncture, it still looks like a complete disassembly is required to do so.
No, they can be popped off just like the old 20xx-2015 models. https://www.ifixit.com/Teardown/MacBook+Pro+16-Inch+2019+Teardown/128106#s249714 -
Apple Studio Display review: How badly do you want an all-Apple experience?
-
Apple acquires popular weather app Dark Sky
Beats said:I wonder why? Is it more accurate or?
Dark Sky gives you very, almost frighteningly accurate predictions over about an hour. I use it during rainstorms to determine where there will be, like, a ten minute gap in rainfall to bicycle home. It's amazing.
Take a closer look at that screenshot for Cape Canaveral, FL. That graph shows moderate rain for about twenty minutes, then a light drizzle, then no precipitation. Whenever that screenshot was taken, you can bet that's exactly how the next hour panned out. -
macOS Catalina beta build suggests upcoming 'Pro Mode'
sflocal said:MplsP said:Fatman said:Tht - I thought the same thing. For the younger crowd ... older PC towers (circa 386, 486 era?) had a turbo button - I believe it simply overclocked the processor. I always wondered why you would want it off - to work slower? LOL
A lot of games written for 8088-series CPUs were timed against the speed of the CPU, not the internal clock. This would render an arcade game on a faster game as unplayable.
The effect was unnoticeable on non-game apps (word processors, whatever) because those old DOS apps really ran pretty fast on anything, as there was no GUI to update. Some sort of complex WordPerfect or Lotus 1-2-3 function would probably be visibly slower if one did a side-by-side benchmark, but not enough people has spare computers lying around to even do a comparison like that.
One would probably never notice unless they tried to play a game like King's Quest I on a 486, and games were improving at such a rapid clip that nobody cared, definitely not surprising that many buttons weren't hooked up. -
Spotify abandons AirPlay 2 support [u]
I was all set to jump on the “holy shit Spotify is completely inept” bandwagon (I personally ignored Spotify in favor of Beats Music because of the latter’s superior Mac software back in the day), but these tweets by Marco Arment — creator of the Overcast podcast app, Instapaper, and some social network called Tumbling or something — made me think twice.“An app can support AirPlay 2 […] with a four-step process outlined on Apple's developer website.”
Those “four steps” from developer.apple.com/documentation/… are:1. Set one flag. One line of code.2. Add the AirPlay picker to your UI. Probably already there.3. Respond to play/pause. Probably already do.4. Rewrite your ENTIRE AUDIO PLAYER to use a COMPLETELY DIFFERENT API…and that new API:- is barely documented- has no public sample code- is full of major gotchas- can’t change speeds seamlessly- doesn’t provide precise timing- requires much more complex logic- is less efficient, which can cause background CPU-overage terminations
i spent about a month of last winter trying to make a music player in the vein of Poolside.fm. It turned out to be a total bust; iOS has (at least) three different audio APIs, with non-overlapping levels of functionality, and uniformly poor documentation. it fucking sucks.
granted, Spotify has enough cash to buy all the talent it wants, but I’m not at all surprised to hear that Airplay 2 support could require a complete rewrite of the core functionality of a very mature app. Audio APIs represent Apple technology at their worst.