+48V
hi-fi or die
Being that streaming services keep their "mechanical" secrets close and in house, it’s unlikely that anyone here can or will offer the defacto official answer. But it’s worth rag-chewing. So I’m just tossing this out here as one of my many contemplated wee hour wonder-zone brain farts.
On-Demand music services offer multiple kbps streams. (i.e. 96/160/256/320) Typically, one selects the preferred sound quality (bandwidth) from their desktop and/or their mobile app account settings. (mainly as a “courtesy”/selling point for reliable stream performance & mobile data caps. adaptive/variable feeds notwithstanding)
With the “advent” of stand-alone (IoT) devices like the Echo Dot, Chromecast Audio, and even the old Apple TV, I’ve yet to see any such “stream quality” option presented within the UI.
So this begs the question, Which stream is actually fetched from these services when these little gizmos connect to x-service?
Rational cynic in me says that since bandwidth cost is exponentially more the higher you go…their default stream for an IoT device is quite possibly not their “TOTL” pipe
Comments, thoughts, guesses welcome.
On-Demand music services offer multiple kbps streams. (i.e. 96/160/256/320) Typically, one selects the preferred sound quality (bandwidth) from their desktop and/or their mobile app account settings. (mainly as a “courtesy”/selling point for reliable stream performance & mobile data caps. adaptive/variable feeds notwithstanding)
With the “advent” of stand-alone (IoT) devices like the Echo Dot, Chromecast Audio, and even the old Apple TV, I’ve yet to see any such “stream quality” option presented within the UI.
So this begs the question, Which stream is actually fetched from these services when these little gizmos connect to x-service?
Rational cynic in me says that since bandwidth cost is exponentially more the higher you go…their default stream for an IoT device is quite possibly not their “TOTL” pipe
Comments, thoughts, guesses welcome.
