spheric

auxio said:

JaiOh81 said:

I’m legitimately curious, how can iMessage “detect” sexually explicit photos being sent to or from a phone.

Does anyone know how this is being done on device?

A simplified explanation is that a "fingerprint" of the image (a unique number which is calculated using the pixels in the image) is created and sent to Apple.  This fingerprint is then compared with fingerprints of known sexually explicit images to see how similar it is.  It won't be done purely on device, but only when an image is sent/received via iMessage.  The fingerprint will be calculated on device, but the comparison will be done on Apple's iMessage servers most likely.

rundhvid said:

elijahg said:

mike_galloway said:

randominternetperson said:

sirdir said:

mike1 said:

rundhvid said:

Apple says this supports up to 96kHz, and means users "can enjoy high-fidelity, full-resolution audio."

—except ’s own Hi-Res Lossless in 192 kHz ߑట䭦lt;/div>

Soooo???? You're saying they therefore shouldn't have improved it all then?

Probably that you can't call something 'full resolution' if you yourself deliver a much higher resolution. 

The average human can detect sound in the 20Hz to 20 kHZ.  96kHz is way outside the range of human hearing.

96kHz is not upper frequency response - it is the encoding bite rate - higher = better resolution but 192kHz is more than necessary to do the job but that's audiophiles for you

Neither of you are right. It's not the maximum frequency that can be produced, nor is it the encoding bit rate. It's the sample rate. Completely different and entirely unrelated to the encoding bit rate. It's the number of times per second that the audio signal is sampled; sampled meaning a measurement or snapshot of the frequency at that exact moment is taken (or generated in the case of audio out).

Now where this does relate to human hearing's maximum frequency, is the fact that humans can't generally hear more than 20kHz. Sampling at double that rate means there will be no aliasing errors in the audio - where parts of the audio could be "missed" essentially, as the samples might fall on two sides of a frequency peak. This is known as the Nyquist rate. The sound between the samples is effectively interpolated (averaged), and of course the higher sample rates mean there's less averaging going on. Audiophiles claim they can hear this, but double blind tests have shown that almost no one can actually tell the difference. And the Nyquist rate says 44kHz is plenty high enough to accurately reconstruct a 20kHz signal, proving that high sample rates are pointless.

The bit rate is inversely related to how much of the original audio is thrown away, and how much the MP3/AAC/whatever decoder has to "guess" to reconstruct the audio.

Excellent written explanation 👍👍👍

Regarding audio quality and this 192 kHz sample rate: earlier this year,  announced immediate availability of ’s music catalog in 192 kHz/24 bit Hi-Res Lossless format (although limited to a subset of the catalog at first)—at no extra cost!!

What is mind-boggling is that ’s hardware is limited to 96 kHz—why?
—my antique +20 year old Denon AV-receiver happily supports uncompressed multi-channel audio in 192 kHz, but neither my  TV 4K 2nd gen., nor my Mac mini M1 is able to take advantage of  Music’s reference-class format! AFAIK, there is no technical reason for this HDMI-output buzz kill 🤒

approx said:

Yes that’s great. But it is still not possible to import Video from Sony SXS Cards. SXS Cards are used in Sony and Arri Broadcast and Cinema cameras

We are waiting since one year to get a updated device driver for SXS Cards. 

Without this updated driver, the super fast M1 MacBook Pro is useless for our job. Ingesting Footage is impossible. 

So sad!

fastasleep said:

ilarynx said:

So... USB-Cs (plural) are supposed to reduce the number of charging cables and related waste... how?

By providing common cables/connectivity that are interchangeable between numerous data protocols as well as charging? Are you serious?

scatz said:

Isn't this service currently in beta, and as such there  will be bugs found to be ironed out ? Don't see any mention of this in the article, so i could be wrong,…..