• 17
    So... ears?
  • 3
    nice 😄
    How would you name it?
  • 4
  • 5
  • 8
    Isn't that just whispering?...

    You can call it Digital Whispering, slap AI somewhere in the description and you got yourself a product. You're welcome.
  • 2
    MP3 requires 360kbps , NFC theoretical max is 424, may be you might have to remove protocol level bloat but then it won’t be NFC then

    but we can transmit shitty 16 bit PCM audio
  • 5
    Feature Request: Please support the gossip protocol.
  • 0
    Good for prisons maybe?
  • 2
    @devphobe Yes, give scuttlebutt support!
  • 1
    @hardfault mp3 doesn't require 360 kbps. And PCM of the same sample rate and bit depth requires more bandwidth than mp3. Mp3 is decoded to PCM when played.
  • 1
    @electrineer i mean to say mp3 is standard compression, when working with raw pcm we have more room to play around

    yes my calculations are off mp3 won’t be 360kbps if we talk about unframed packets
  • 2
    There are codecs for voice where you can transmit with as little as 10 kbps or so IIRC.
  • 2
    @cafecortado and Nvidia anounced an ai video compression for video conferencing. That only transmits the movement of the face. Ai moves then the picture on the other side.

    Video explanation

  • 0
    @heyheni good luck transmitting video with 10 kbps
  • 1
    This could be a good concept for a “Pass the note” like network at school.

    If only there was a way for storing audio in a programmable nfc tag.

    I couldn’t think of any practical usage apart from maybe between teens at schools as suggested by @devphobe - maybe audio in nfc could be a thing in museums 🤷‍♂️
  • 0
    @uziiuzair not a bad idea at all! I imagine those stations which currently tell you which number to press on the digital tour guide device being replaced by an NFC transceiver and you can just use your own phone, with your own head/earphones.
  • 0
    @cafecortado but that’s just voice If you work the math
    Audible frequency is 20 to 20k hz (theoretical)
    So we have to sample with 2f(max) now to represent the sample we have to use at least 16 bit samples
    so 2*20,000*16 bits per sec or 640kbps , to represent sound
  • 0
    Google removed the beam functionality from their APIs because they want to push cloud services (google isn't evil though, remember?) so this wouldn't even be possible with most phones today.

    Otherwise, I would have already started doing this for fun.
Add Comment