Please fix that ducking feature

They've been developing this voice control for over a year, plenty of time to sort it out with Amazon. It won't be beta next week and i'm sure it won't be fixed by then.

Who said it won't be beta next week? Just because the Sonos One is released doesn't mean the Sonos skill via Amazon is not still in beta.

And this "been developing this voice control for over a year" BS has to stop. This is something that has never been done before, and it was highly dependent on the Amazon API which was released only 3 weeks ago. Neither you nor I know the number of man hours put into the effort, nor the estimate of hours required, so therefore we have no way of stating if there was "plenty of time to sort it out" or not. Speculative nonsense like that is nothing but shouting at the pigeons, and does about as much good.

Amazon API released 3 weeks ago? WTF are you talking about! So they developed it all in a week?! No wonder its crap :8

And yes, I don't expect to be paying £200 for a beta product otherwise it's going straight back.

There is also the possibility that stats show that households rarely have different sources playing in different homes. They may switch groups and such, but rarely do you play one source in zone A and another in zone B. That's how it seems to operate in my house anyway.

I also wonder what it would be like if they didn't implement ducking at all. People would complain that they can't hear/talk to Alexa when Sonos is playing.

It's also quite possible that Sonos doesn't really have the ability to turn off ducking...that's it's entirely in Amazon's code. If the command from Alexa to duck is actually just a command to lower the volume, no different then if you specifically asked Alexa to lower the volume. Sonos may not know if it's ducking or manually lowering the volume.

Amazon API released 3 weeks ago? WTF are you talking about! So they developed it all in a week?! No wonder its crap :8

And yes, I don't expect to be paying £200 for a beta product otherwise it's going straight back.


http://phx.corporate-ir.net/phoenix.zhtml?c=176060&p=irol-newsArticle&ID=2297100

Sorry, six weeks ago, my mistake. And obviously it was developed along with other speaker manufacturers, so the work was concurrent. The point is Sonos' timeline was dependent on Amazon.

By the way, any other speaker companies even close to Sonos in their implementation? No. Denon actually did promise 1st quarter 2017, and they have nothing. So knock it off with the nonsense, and can the profanity. Act like an adult.

And for the last time (read slow now), the "product" you purchased is not a beta, nor is the Sonos app. The beta is the Alexa skill that you VOLUNTARILY agreed to enable, thus joining the beta. Don't want to participate in a beta, don't enable it. Instead, wait for the general release, which will probably still be ahead of Denon's.

Act like an adult.

And for the last time (read slow now), the "product" you purchased is not a beta, nor is the Sonos app. The beta is the Alexa skill that you VOLUNTARILY agreed to enable, thus joining the beta.

I'm perfectly aware of that, when the Sonos One is out then I would think the Skill would be out of beta, otherwise they are selling a beta product.

Now quit with the arrogance 😃 And get your head out of Sonos' arse. Do you work for them 🆒

I'm perfectly aware of that, when the Sonos One is out then I would think the Skill would be out of beta, otherwise they are selling a beta product.

Now quit with the arrogance 😃 And get your head out of Sonos' arse. Do you work for them 🆒

And there it is folks, the accusation that I work for the company. Attacking the poster, the last bastion of defense for a failed argument. It would be annoying if it wasn't so predictable. :8

By the way, no comment on the Amazon API information that you conveniently snipped from your quote?

I kinda doubt the interface between Sonos and Alexa will be out of beta in a week, nor do I see the release of the Sonos One to mean beta has to be over. The Sonos One has to do all the things that Sonos does on it's own, and there is no reason to doubt that. It also has to do all the things that Alexa does on it's own, and that shouldn't be a problem. It then needs to automatically play music sources in whatever zone Sonos One is defined in, which really would be the only real new feature. Controlling other zones, grouping, music sources, and such can still be in beta, as I see it.

I also agree that regardless of how difficult the development may or may not be, a year of development could actually be rather impressive, if you consider the decisions that had to be made to get it done. These are things we will never be informed of, but having been on several software implimentation projects where several groups are involved with different objectives to the project, it's entirely possible that 95% of the 'year of development' was spent on higher ups negotiating.

If that's defending Sonos, so be it. I prefer to try and figure out why things are the way are then just assume that Sonos is just blatantly failing at whatever the issue is, particularly when they obviously have spent much more time on the issue then I have.

Attacking the poster, the last bastion of defense for a failed argument. It would be annoying if it wasn't so predictable. :8

You might want to re-read your post that I was replying to.


By the way, no comment on the Amazon API information that you conveniently snipped from your quote?

Sorry, the quoted text was to highlight the arrogant reply and insults made to me, I didn't read the link.

I've now read the link you posted about the API, it talks about an API to enable syncing echo devices? What has that got to do with Sonos' implementation?
So you think Sonos started developing all this voice control stuff 6 weeks ago, putting the beta live about 2 weeks ago, so 4 weeks development time :8

My reply was to your use of profanity. That was an attack on your posting, not a question of whether you were a paid shill hired to denounce Sonos.

And you should have kept reading, that link is also describing the new API for basic controls of third party speakers.

New Alexa developer tools extend multi-room audio to other connected speakers and audio systems

. . .

New Tools Let Device Makers Create Additional Voice-Controlled Music Experiences with Alexa

Amazon also announced two new sets of tools for developers to bring multi-room music control to their speakers.

. . .

Connected Speaker APIs

These new tools enable device makers with connected audio systems to control music playback using Alexa. A customer can then use any Alexa-enabled device – for example an Echo Dot – to play music throughout their home on their connected audio systems. Amazon is excited to be working with leading brands on this offering, including Sonos, Bose, Sound United, and Samsung.

See that above, "including Sonos, Bose, Sound United (aka Polk, Denon, Marantz), and Samsung". Now tell me, which one of those manufacturers have actually released these capabilities to the public?


As to the rest, I'm going to back away from you now. You completely misinterpreted my post, even after I clarified it. I would explain how I in no way said that the development started 6 weeks ago, but there is no sense arguing with someone so intent on seeing things in a negative manner. You have a nice day now, ya hear!

Well, I was going to add to this topic some observations I had on ducking. But, jgatie has again ruined another thread with vicious attacks on someone who doesn't completely worship Sonos as he does.