Never seen this kind of flakey-out-of-the-box bullshit from Apple. I really need a new machine but I'm holding out for a better run than what they have now. And maybe some undoing of their recent price hikes (they used to drop prices, substantially, with some frequency, in the distant past of a few years ago and earlier). Plus all the damn dongles. My '14 has lots of ports and zero USB-C and those ports are great, and I still don't have anything that's USB-C aside from adapters for work laptops, so... why do I want only USB-C again, and no other ports at all? Maybe in another 5-7 years it'll make sense. Give them time to switch all their iDevices to USB-C and for me to replace all those (they last many years, that's why we buy them). Then at least my laptop and iPads and iPhones and such can share peripherals, which is moving toward some kind of benefit to offset the loss of ports.
The USB-C thing is culturally a bit curious. It's been three or four years since reviewers of laptops and the like started complaining if they didn't have USB-C ports - but there still seems to be very little need for them. The few devices I've acquired that have a USB-C socket on the device have all come with a cable having a USB3 type A plug on the other end, never a C to C cable.
(I see the article mentions this, but I found it striking because to facilitate home working I've just bought two new devices with USB-C at the device end, and both came with cables to an A socket)
Hell, to this day the only actual USB-C devices I've seen in person are Apple peripherals and monitors catering to Macbook users, which almost all include other ports anyway. I'd add Android phones but those mostly have USB-A connectors on the other end of the cable (like the iPhones that were shipping for a while after the USB-C Macbooks came out—there's another giant WTF). USB-C market for flash drives seems to suck (form factor's worse, price is higher).
[EDIT] oh and when the new port is intended to replace all other ports the half-life on "legacy" devices for me probably goes from ~10 years to ~20. Seriously. WTF Apple.
They could have replaced the USB-A to Lighting cable and charger they ship with iPhones for USB-C to Lightning years ago.
(Personally I’d like to see Lightning replaced too but that’s a different story).
[EDIT] go figure, my wife just today bought a new iphone, wants to put some music from her 2019 Macbook Air onto it, needs to plug it in at least once in order to do that (have to plug in first to enable wifi sync), and can't because the phone shipped with a fucking USB-A cable and the single lightning-to-usb cable we have in our house is missing. This is going down right now. So much for not needing USB-A ports on a laptop in 2020 even if you're fully in the Apple ecosystem. She's so annoyed I wouldn't be surprised if she returns the phone. I mean granted the phone isn't the latest model but it came out way after they made the all-USB-C switch on their laptops.
One of the main reasons that I left the Apple laptops after using 3-4 of them over 10 years was because of the removal of the USB-A ports. Adding new USB-C, great. But removing all of the older ones? A big middle finger to the users. Then there's the removal of the ESC key, the butterfly keyboard debacle, the touchbar that removes the function keys, etc. Sorry Apple, you are going off in a direction that I cannot follow.
User friendliness is a problem. There's no easy way to tell what protocols a USB-C device actually supports, whether it's USB 2, USB 3, DisplayPort, etc.
USB-C hubs are not possible like you could do with USB 2 or 3, so you're always limited to the number of USB-C ports on your machine. The only possible hubs are those that give out USB-A ports, which is fine now because most peripherals are still USB-A, but will become a problem when peripherals start using USB-C themselves.
Remember, all USB Type-A ports aren't USB3. Likewise, all USB Type-C ports won't become USB4.
TIL. Why is this not possible?
USB-C can be used with alternate modes like DisplayPort or Thunderbolt, where the wires are no longer transmitting USB data but are used as a dumb pipe for the underlying protocol.
If you get a hub it can choose to either operate in the following conditions (depending on its type and capabilities):
* Upstream port is in USB mode, it can provide USB 2 and 3 to downstream ports, however the downstream device can no longer use DisplayPort or Thunderbolt.
* Upstream port is divided into USB 3 lanes and DisplayPort lanes. The DisplayPort side can be mapped to a single downstream port, but there is less USB 3 bandwidth available to share across the remaining ports. Still no luck if a downstream device wants to use Thunderbolt.
* Upstream port is Thunderbolt. Since TB is essentially PCI Express the hub could pass through some TB lanes to a single downstream port while having its own USB 3 controller to provide the USB side of things. Still no luck for DisplayPort downstream devices.
This doesn't even address the issue that not all devices can do Thunderbolt (my 12-inch Macbook can't) and it becomes very hard to find a hub that will actually work and do what you want. It took quite a bit of research for me to understand the specs so I could find a solution to do both 4K 60Hz video and USB (2 only, not enough bandwidth for 3) on my MacBook with a single USB-C port.
I won't even get into the bullshit naming conventions they use that they decided to apply retroactively. WTF is USB 3.1 Gen 1? Is the next one gonna be called USB 10 X Pro Max?
edit: I also looked for a usb A hub with usb-c upstream, still no luck and stuck with a hub+power adapter and dinky otg a-to-c.
Let's assume the hub requests 19V from the upstream port. Unless it has built-in, variable, per-port voltage regulation, it will not be able to respond to power requests from the downstream devices if they differ from what is coming from the upstream port.
This isn't a problem when providing USB-A ports because you either request 5V from upstream and pass it through or request a higher voltage and have a single 5V regulator and pass its output to the downstream ports.
This is all possible, it's just a HUGE pain in the ass (and costs a lot) to design that way. The problem is you essentially end up with potentially a giant, VERY expensive USB hub. And no one wants to spend $400 on a USB hub.
You could also theoretically use 10Gbit Ethernet to transfer data from your phone but we don't go around putting SFP slots on phones because we don't want every single cable or charger to cost $100 and be more complex (thus more prone to failure) than needed.
The ask for the 'really expensive' $400 one has vastly more options and capabilities than the traditional USB hub. It's basically a Thunderbolt hub with even more complexity, so it's not unreasonable to think those would be damn expensive.
I'm honestly not sure why no one has made a standard USB2.0 Type-C hub. There's really nothing stopping you from doing it. I guess maybe because it could be confusing for a consumer? I agree, that's a huge issue with Type-C right now. It's very unclear by looking at the port (or the cable) what it's actually capable of. If you're lucky there will be a tiny symbol indicating some subset of functionality, but often times there isn't.
(I assume you can still have a USB3 hub with type A sockets on it, plugged in to a USB-C port? - edit: oh, just noticed a sibling comment says this doesn't seem to exist either. Now that is very odd.)
Here’s the one i use:
Anker USB C Hub, Aluminum USB C Adapter with 4 USB 3.0 Ports, for MacBook Pro 2018/2017, ChromeBook, XPS, Galaxy S9/S8, and More https://www.amazon.com/dp/B07DFYQXY7
That said, I see no reason why you couldn't design a basic USB-C USB2 or USB3 hub. Hell, it could have 5 ports with no defined 'input' port (just 5 USB C jacks), and you could have that work properly with some pain.
If it has a captive USB-C cable and 4 USB-C outputs, that would be even easier to program. Again, it's just expensive. You need a lot of active circuitry to make it work.
And I'm not made of money and I have other hobbies that require cash so I buy used musical equipment so I can get low-end pro gear a generation or two old for at or under new prices for amateur/crappy gear. There's little chance I'll buy any USB-C native musical equipment of any kind before 2030 or so. Who's cycling out all their gear—musical or otherwise—so fast that dropping USB-A and HDMI entirely in 2016, on a "pro" laptop, made any damn sense?
>>other than the typical setup issues related to Jack (one time thing resolved in an hour or so)
I was never able to get Jack up and running on my MBP. I tried both Jack and Jack2, compiling from source, using their prepackaged binaries, using the cli vs the GUI, etc, .. nothing doing. Do you have any resources you can share detailing how you resolved the issue or how you configure it? Feel free to PM, emails in profile.
The only thing that isn't great moving from Windows to Linux for production is your VST ecosystem becomes much more limited. Running plugins under WINE is alright, but if they're heavy you'll run into latency issues. There's a sizable collection of plugins that are native under Linux though[0]. I've used many of these with great success.
* Apple knows best
* this is a totally legitimate product decision because no one likes wires on their headphones since like 2016
* what you really want is bluetooth, especially airpods -- have you bought your airpods yet? Ecosystem FTW!!1! -- even though they introduce latency that's unacceptable in some situations
* Apple knows best, and look, you don't get a career as a bold product thinker by caring about some kind of insignificant minority of niche creators who care about latency in music making
* Besides, why are you such a whiner? Just buy a $35 dongle that takes up your only port like everyone else (at least, until we finally succeed in our quest to remove that port too and achieve seamless invulnerable portless design, a rock, and island, and an island never cries)
* Apple knows best
* Look, why are you such a hater?
Or I guess they expect me to buy Bluetooth heaphones, but... why? We have like three sets of corded ones two of which are quite good, and about a dozen pairs of ear buds. We don't need new headphones. We need a headphone jack.
...which adds another source of frustration to the setup - bluetooth latency. At some point I've tried setup like this: midi keyboard -> USB dongle -> iPad -> bluetooth speaker; the latency sucked. Not something you observe when you listen to music on Youtube, so not something that 99% users will notice, which means it will never get fixed.
They've had SO many issues with it. It has randomly died mid-performance, the tempo click has completely gone off the rails mid-performance, and the loops got transposed once into a completely different key mid-performance.
I use a 2012 MBP stuck on High Sierra. It has occasional issues when I record, but nowhere near the amount of issues that we experience at the church. I want to upgrade badly, but I really don't want to deal with those kind of issues.
After a recent Catalina update all the streaming video / audio stutters stopped only to be replaced with random dots appearing over my display - almost like my graphics card was dying. That’s now disappeared (after the most recent update) but the stuttering has restarted.
Running console.app As these issues occurred showed a number of errors that came up time and again. Bluetooth seemingly interrupting the audio, graphics drivers failing, disk access halting the system. Catalina is a poor product - probably the version of MacOS where I’ve experienced the most issues.
It seems to only happen when using the built-in speakers. I never hear glitches using headphones (which is what I have as the default audio interface for Logic).
So I just use headphones all the time, but it's an incredibly negative experience to pop open one of your projects on your new laptop and hear this rhythmic popping. If it had also glitched in the headphones I might literally have thrown the laptop out the window.
* This isn't my post, but it's exactly the glitch I get in the built-in speakers: https://imgur.com/a/YPCmyiV
EDIT: More information https://www.gearslutz.com/board/apple-logic-pro/1289789-offi... and specifically https://www.gearslutz.com/board/showpost.php?p=14412122&post...
Threads requiring hard real-time responsiveness can (and do) request to be marked as such by the scheduler. And the OS is certainly aware of what hyperthreads-presenting-as-cores belong to which physical cores, and uses this information in scheduling. So I'd find it implausible that any modern OS (esp. one that already had good DAW support) doesn't already have logic to try to keep the other hyperthreads of a core on which a hard-realtime thread is running, as uncontended as possible, by either not scheduling, or very conservatively scheduling (i.e. "early" pre-empting) anything on that hyperthread.
I have a feeling it's something much more arcane. Maybe a hitch generated by the core switching "licenses" due to an AVX512 instruction.
It isn't hyperthreading, which has never been an issue before, on any platform. The audio subsystem has been fucked up in some way.
Maybe I should've bought 2015 MBP then. Or maybe I should downgrade to Mojave? Or buy the Apple adapter? Or a different interface? No idea; both Focusrite and Ableton say they are compatible with Catalina.
I have a new OWC SSD upgrade so that should be alright.. Trying to keep it running cool without heavy software but the battery is at like 500 charge cycles and 70% capacity man it feels so scary getting old
One fun benefit of 2013 tech is you can by a bunch and give them to your friends for the same price as a 2020 model. I've now bought 4 and given away 3. It's good that they are reliable - many other laptops don't really last 7 years.
To quote Scotty - the more complicated they make things the easier they are to foul up.
But wait, there's more! Sometimes I got glitches even when I'm not recording but playing tracks. I have this problem on literally the same Ableton projects that used to "just work" on the old machine (same number of tracks/plugins). The workaround is to restart the laptop. Seriously, it feels like Windows XP all over. I can't imagine playing live shows with such unreliable setup - fortunately I just make tracks for my own, but if I were to go out for some kind of jam session or open mic I'd consider switching to Windows.
EDIT: One more thing that sucks about new MacOS: dropping 32 bit compatibility. RIP all 32 bit VSTs. Fortunately I don't use that many plugins and it turned out everything I really care about has 64 bit version. But if it didn't, then I'd hold on to the old OS as long as possible.