So the problem is that white noise doesn’t compress very easily.
Compression algorithms are generally designed to reduce noise; if you have something that’s extremely noisy it’s really hard to compress because that’s not what the algorithms were designed to do.
This means that these podcasts take up more space, which means they use more bandwidth than an equivalent non-white-noise solution.
A middle ground would be banning these “podcasts” and then having a white noise generator built into the app. The white noise generator would run locally on your device (very easy to make white noise) and wouldn’t cost any bandwidth at all.
They should just do it procedurally on the fly.
because after all there was probably some algorithm that generated those all these and saved to a file. Just cut the file…
I’ve wondered for a while now why so few devices seem to generate it on the fly. Even Google Home and Alexa devices seem to play a 1 hour long file that fades out and in. The older, standalone “sound spa” units played a loop a few seconds long, which bothered some listeners who could hear a pattern due to the loop (maybe due to compression artifacts). I imagine it’s probably just computationally more expensive to generate it on the fly, rather than playing a file, but I also suspect that it’s also just companies pushing out the minimum viable product, and looping an audio file is easiest - especially if the device is already designed to play music, or other audio files like “ocean waves” and “babbling brook.”
I can totally hear a pattern overlaying the white noise sound in my kid’s white noise machine. The sound of the pattern varies based on the level of battery charge, as far as I can tell. I thought it was some kind of unintended noise coming from the circuitry (like maybe bad caps). Given that the underlying white noise sound doesn’t seem to vary based on the state of charge, I am still not sure that the sample length is what causes the pattern, but now you’ve got me super curious to tear the damn thing apart to test the caps.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !technology@lemmy.world
This is a most excellent place for technology news and articles.
So the problem is that white noise doesn’t compress very easily.
Compression algorithms are generally designed to reduce noise; if you have something that’s extremely noisy it’s really hard to compress because that’s not what the algorithms were designed to do.
This means that these podcasts take up more space, which means they use more bandwidth than an equivalent non-white-noise solution.
A middle ground would be banning these “podcasts” and then having a white noise generator built into the app. The white noise generator would run locally on your device (very easy to make white noise) and wouldn’t cost any bandwidth at all.
They should just do it procedurally on the fly. because after all there was probably some algorithm that generated those all these and saved to a file. Just cut the file…
I’ve wondered for a while now why so few devices seem to generate it on the fly. Even Google Home and Alexa devices seem to play a 1 hour long file that fades out and in. The older, standalone “sound spa” units played a loop a few seconds long, which bothered some listeners who could hear a pattern due to the loop (maybe due to compression artifacts). I imagine it’s probably just computationally more expensive to generate it on the fly, rather than playing a file, but I also suspect that it’s also just companies pushing out the minimum viable product, and looping an audio file is easiest - especially if the device is already designed to play music, or other audio files like “ocean waves” and “babbling brook.”
I can totally hear a pattern overlaying the white noise sound in my kid’s white noise machine. The sound of the pattern varies based on the level of battery charge, as far as I can tell. I thought it was some kind of unintended noise coming from the circuitry (like maybe bad caps). Given that the underlying white noise sound doesn’t seem to vary based on the state of charge, I am still not sure that the sample length is what causes the pattern, but now you’ve got me super curious to tear the damn thing apart to test the caps.