• WANTED: Happy members who like to discuss audio and other topics related to our interest. Desire to learn and share knowledge of science required. There are many reviews of audio hardware and expert members to help answer your questions. Click here to have your audio equipment measured for free!

KEF LSX II

Way more ‘musical’?
Ultimately it just comes down to personal preference, sound quality/features/price/aesthetics.
Keith
 
From LSX II user manual:

Unsaved Image 2.jpg










Does this make any sense?
No WiFi or cabled network in my listening room equals to no way of listening to contents from my phone?
 
Last edited:
Sorry for quick double posting, but another question I always cannot answer is: why should I create an account and log in just to use a product I bought (and paid)?

Unsaved Image 3.jpg


Isn't the app just a different kind of remote? Why, for God's sake, I am forced to log on to a remote server to start using my product? No log in, no use?
I am sure 99,9% of customers would accept this with no complaints...not me.
 
There is a lot of functionality dependent on internet/network connection anyway so i get why they just made everything use the same interface .

For example Roon , spotify connect, firmware update .

The whole setup procedure with the App ? How should the App talk to the speaker if not via the network ?

I have no idea if what happens after you done the setup ? I use the spdiff inputs , I guess the speakers continue to work if the network fails during playback for spdiff or bluetooth , but you have to switch sources and control volume with the remote control
 
There is a lot of functionality dependent on internet/network connection anyway so i get why they just made everything use the same interface .
Why not requesting login only when really needed? I can easily list all the functionalities that do not need login to properly work (starting from BT)

The whole setup procedure with the App ? How should the App talk to the speaker if not via the network ?
Bluetooth? Local WiFi/cabled network autodiscover (like ALL network printers do)? NFC could be another option, if ever implemented.
I can see no technical blocking point in delivering most of the speakers functionalities without letting someone overseas know that in real time. And, please, don't ask me "what do you have to hide?"...
 
Bluetooth? Local WiFi/cabled network autodiscover (like ALL network printers do)? NFC could be another option, if ever implemented.
I can see no technical blocking point in delivering most of the speakers functionalities without letting someone overseas know that in real time. And, please, don't ask me "what do you have to hide?"...
By watching at this:
KEF LSX II - Android Setup
at 00:56 it appears evident that the App is actually using BT for connecting to the speaking at setup time.
So the question arises even more annoyingly: why login to KEF servers is mandatory for controlling the speakers?
 
Why not requesting login only when really needed? I can easily list all the functionalities that do not need login to properly work (starting from BT)


Bluetooth? Local WiFi/cabled network autodiscover (like ALL network printers do)? NFC could be another option, if ever implemented.
I can see no technical blocking point in delivering most of the speakers functionalities without letting someone overseas know that in real time. And, please, don't ask me "what do you have to hide?"...
Ok local wifi ? You did not have wifi in your listening position ? The account is probable just the same invasive practice as everyone else is using. I wonder what they think they need the user data for ? it's a common fallacy to collect just because you can .
 
Last post from me, I promise.

Can someone guess why Precise phone Location is needed to just perform device discovery in the local WiFi network?
1725893947607.png

I work in telecommunications and cannot figure this out.

Sorry, surely I am just and old whiner but I can no more understand the road taken by modern consumer electronic industry...
 
The account is probable just the same invasive practice as everyone else is using. I wonder what they think they need the user data for ? it's a common fallacy to collect just because you can .
You got the point: it is a so much widespread practice that nobody cares anymore...but this does not justify the approach
 
I’m another old whiner. This data collection really puts me off. They would never let me have their data free of charge so I can sell it. I would expect collection to be automated and easy to sell.
 
Sonos and KEF are now out of my list ;)
Sonos has been on the don't buy list since the forced privacy changes years back. Every so often they do something to remind me why they're on the list, like removing the bit about not selling your personal data from the privacy policy, let alone the recent debacle with removed functionality.
This is enough to make me look carefully at KEF's app requirements and privacy policy - it sounds like anything networked will be joining Sonos.

For me the right way to do wireless control is local-only unless strictly necessary, with a public API so that it can be kept working if/when the manufacturer decides to drop support, goes bust or whatever. See Parks Audio publiching the bluetooth API for the Waxwing for example. Or MOTU publishing the network API for their AVB series.
 
Back
Top Bottom