Using ultrasound as a carrier isn’t going to solve any of the problems in the “historical challenges” intro:
Companies closely guarded proprietary standards, forcing complex reverse engineering or exclusive partnership deals. Integrating new peripherals like printers and scanners required low-level software development. The process of binding devices into cooperative workflows was cumbersome and fragile, usually involving ducttape.
So, you’d like everyone to use your new standard for encoding data? Also, there’s no way ultrasound is going to be reliable as RF pretty much any distance, to say nothing of environmental noise.
Like, is there a value add or is this just some marketing jargon salad?
UPDATE: reading further, this gem appears:
Ultrasound communication can have lower latency over short distances due to the speed of sound in air. For close-proximity devices, this could result in faster real-time communication compared to RF, which might experience more latency due to network congestion and signal processing delays.
Bull crap. This is so ludicrous that it makes me give credence to the folks here wondering if this is AI slop.
Oh, so, your ultrasound system will have lower latency because it won’t have network congestion like RF? Yeah right. 5 GHz WiFi already yields a lot of the same benefits (or drawbacks?) of being blocked by walls, so it works fine in high-density deployments. And, like, speed of light >>> speed of sound. This is just hilarious.
I was expecting some kind of demo that worked with commercial/existing speakers and mics. I've already heard stories of ultrasound being used for tracking advertisement reach.
5 comments
[ 3.0 ms ] story [ 25.3 ms ] threadThere are misspellings, pointless verbiage on the merits of an open standard without using the words open standard.
A 2. Numbering without a 1.
A blurb about 140 billion network AI put of the blue, what does that have to do with a network protocol
Companies closely guarded proprietary standards, forcing complex reverse engineering or exclusive partnership deals. Integrating new peripherals like printers and scanners required low-level software development. The process of binding devices into cooperative workflows was cumbersome and fragile, usually involving ducttape.
So, you’d like everyone to use your new standard for encoding data? Also, there’s no way ultrasound is going to be reliable as RF pretty much any distance, to say nothing of environmental noise.
Like, is there a value add or is this just some marketing jargon salad?
UPDATE: reading further, this gem appears:
Ultrasound communication can have lower latency over short distances due to the speed of sound in air. For close-proximity devices, this could result in faster real-time communication compared to RF, which might experience more latency due to network congestion and signal processing delays.
Bull crap. This is so ludicrous that it makes me give credence to the folks here wondering if this is AI slop.
Oh, so, your ultrasound system will have lower latency because it won’t have network congestion like RF? Yeah right. 5 GHz WiFi already yields a lot of the same benefits (or drawbacks?) of being blocked by walls, so it works fine in high-density deployments. And, like, speed of light >>> speed of sound. This is just hilarious.