• WANTED: Happy members who like to discuss audio and other topics related to our interest. Desire to learn and share knowledge of science required as is 20 years of participation in forums (not all true). Come here to have fun, be ready to be teased and not take online life too seriously. We now measure and review equipment for free! Click here for details.

Dutch&Dutch 8C at Purité Audio

Purité Audio

Major Contributor
Industry Insider
Barrowmaster
Joined
Feb 29, 2016
Messages
3,291
Likes
1,123
Location
London
#2
Eric from D&D has explained the software but/automatic update issue over at Gearslutz,
Quote,
In firmware version 1.3.4 there was a bug that led to boundary presets not being programmed into the DSP correctly. The result was that the bass level was too high. The firmware version that succeeded it was 1.3.12. In 1.3.12 the boundary bug was fixed.


At the time we did not realize the implications fixing the bug could actually have. What happened, is that some users had compensated for the excess of bass with Active Room Matching. When the newer firmware version was automatically installed, all of a sudden the boundary settings were correct again, with the end result being anemic bass.


When we found out, we put on hold the development of all the new features we were working on and we put the entire team on making sure something like this can never happen again.


The first thing we did is put automatic updates on hold. We did this to make sure nobody else would be surprised by a sudden change in sound from their 8c’s. We invited everybody who wanted to keep up with firmware updates, or wanted to go back to firmware 1.3.4 to send an email to [email protected] with the serial numbers of their speakers. For those speakers, automatic updates is turned on again. Be aware that if you’re currently on 1.3.4 and you request to receive updates again, the sound from your 8c’s may change and you’ll have to match them to the room again with the lanspeaker-app.


The second thing we did was update the protocol for firmware releases, to reduce the risk of releasing a firmware version with bugs. We added many more software tests and we’re in the process of expanding and diversifying the group of beta-testers. This should increase the chances of finding and fixing any bugs before the public release.


The third and biggest thing our R&D team has been working on lately, is a complete overhaul of the firmware update software itself. This involves software that runs on the 8c’s and also software that runs on our servers. This platform will not only become more robust, it also gives the user more control. That means for instance no more automatic updates and the option of going back to the previous firmware-version if for whatever reason you wish to do so. We’ll also release a changelog for every firmware version.


When this new software is ready and thoroughly tested, first all new 8c’s will get it. Shortly after the update will be made available for all 8c’s in the field. This whole process is a significant detour from our development planning. Features such as Roon support were delayed. However, this is important work. The new software will provide us with a robust foundation to build on in the future.


We’d like to thank the people who posted here and corresponded with us about the bug. Thank you for your support and understanding. Your feedback has helped us a lot in dealing with this issue.


Kind regards, Eric van Duin
 

andrew

Active Member
Joined
May 3, 2018
Messages
105
Likes
17
#5
Eric from D&D has explained the software but/automatic update issue over at Gearslutz,
Quote,
In firmware version 1.3.4 there was a bug that led to boundary presets not being programmed into the DSP correctly. The result was that the bass level was too high. The firmware version that succeeded it was 1.3.12. In 1.3.12 the boundary bug was fixed.


At the time we did not realize the implications fixing the bug could actually have. What happened, is that some users had compensated for the excess of bass with Active Room Matching. When the newer firmware version was automatically installed, all of a sudden the boundary settings were correct again, with the end result being anemic bass.


When we found out, we put on hold the development of all the new features we were working on and we put the entire team on making sure something like this can never happen again.


The first thing we did is put automatic updates on hold. We did this to make sure nobody else would be surprised by a sudden change in sound from their 8c’s. We invited everybody who wanted to keep up with firmware updates, or wanted to go back to firmware 1.3.4 to send an email to [email protected] with the serial numbers of their speakers. For those speakers, automatic updates is turned on again. Be aware that if you’re currently on 1.3.4 and you request to receive updates again, the sound from your 8c’s may change and you’ll have to match them to the room again with the lanspeaker-app.


The second thing we did was update the protocol for firmware releases, to reduce the risk of releasing a firmware version with bugs. We added many more software tests and we’re in the process of expanding and diversifying the group of beta-testers. This should increase the chances of finding and fixing any bugs before the public release.


The third and biggest thing our R&D team has been working on lately, is a complete overhaul of the firmware update software itself. This involves software that runs on the 8c’s and also software that runs on our servers. This platform will not only become more robust, it also gives the user more control. That means for instance no more automatic updates and the option of going back to the previous firmware-version if for whatever reason you wish to do so. We’ll also release a changelog for every firmware version.


When this new software is ready and thoroughly tested, first all new 8c’s will get it. Shortly after the update will be made available for all 8c’s in the field. This whole process is a significant detour from our development planning. Features such as Roon support were delayed. However, this is important work. The new software will provide us with a robust foundation to build on in the future.


We’d like to thank the people who posted here and corresponded with us about the bug. Thank you for your support and understanding. Your feedback has helped us a lot in dealing with this issue.


Kind regards, Eric van Duin
Any idea, Keith, as to how the work on the new firmware is progressing?
 

Purité Audio

Major Contributor
Industry Insider
Barrowmaster
Joined
Feb 29, 2016
Messages
3,291
Likes
1,123
Location
London
#6
I believe, that the bug has been fixed and that the engineers have been re-purposed back to Roon readiness.
Keith
 

Purité Audio

Major Contributor
Industry Insider
Barrowmaster
Joined
Feb 29, 2016
Messages
3,291
Likes
1,123
Location
London
#8
Just installed a pair with ‘18’version, I have asked for the current state of play in terms of version.
Keith
 

Purité Audio

Major Contributor
Industry Insider
Barrowmaster
Joined
Feb 29, 2016
Messages
3,291
Likes
1,123
Location
London
#12
I believe new speakers ( delivery for me next week) will have the new firmware and then older speakers will be updated, if you speak to D&D they are always helpful.
Keith
 

Similar threads

Top Bottom