jdb8167
About
- Username
- jdb8167
- Joined
- Visits
- 197
- Last Active
- Roles
- member
- Points
- 1,587
- Badges
- 1
- Posts
- 627
Reactions
-
13-inch MacBook Pro with Apple Silicon M1 review: Unprecedented power and battery for the ...
loopless said:You should all go to the dark side for a bit to hear all the gnashing of teeth in the "PC" world. Quite amusing....
https://www.pcworld.com/article/3596814/new-macbook-air-is-not-faster-than-98-percent-of-pc-laptops.html
The definition of butt hurt. -
M1 benchmarks prove Apple Silicon outclasses nearly all current Intel Mac chips
Mike Wuerthele said:beowulfschmidt said:I'm guessing you didn't yet have the new Air or Mini to add to the comparisons?
I'd be interested in seeing what, if any, differences the cooler in the Pro makes over the Air and Mini.Cinebench R23MC 7226SC 1494Geekbench 5MC 7560SC 1727Compute OpenGL 18138 -
Compared: New Apple Silicon Mac mini versus Intel Mac Mini
MacPro said:I have a suspicion we are all going to be surprised at how much less RAM is needed with Apple's new technologies to achieve as good or better results. Everyone is judging the M1 by what just could be old school Intel thinking.I can’t come up with any reason to think that memory intensive apps will have their requirements lessened because of a CPU architecture. -
How Apple Silicon on a M1 Mac changes monitor support and what you can connect
dominickelly said:I have 2 x LG Ultrafine 4K monitors and an Intel MBA.
I run both monitors from a single TB port, the monitors are daisy chained.
Is this not possible with the MM M1??Are there any downside to connecting one LG to TB and the other LG to HDMI if I went with the MM M1? Apart from untidy wires? -
Native Instruments warns macOS Big Sur can damage its music hardware
spheric said:jdb8167 said:Sounds like a hardware problem ... for Native Instruments. There should be no way any digital input should damage peripheral hardware (different if it is analog).
However, if there is some unfixable design flaw that could damage the hardware (I've seen synthesizers permanently bricked by sending the wrong kind of Sysex data via MIDI, resulting in Boot Flash corruption that required replacement*), and Apple's update is sending spurious, errant data that it shouldn't be, then the problem is indeed Apple's to fix.
It's sort of like if I forget to lock my front door and a burglar just walks in and steals stuff — yes, I should have locked my door, but it was the burglar who actually ruined the day.
This is speculation, of course.*) The guy who told me this was using it as an example of how software engineering had gone to shit since the days when he still wrote the code for that brand's machines. He'd always test the resiliency of the machines he was writing for by sending them a huge .TIFF file via SysEx to see if they'd lock up.