Support

Need help?

DOS 2.2.0 beta12 + Firmware 12.2.6 - February 5th

Was this article helpful?

11 out of 15 found this helpful

Follow

Hi

We are happy to announce a new beta release

DOS 2.2.0 beta12 + Firmware 12.2.6

Here is the changelog:
 
Fixed
  • 176.4kHz sampling frequency on companion (AIR, Airplay, Spotify, UPnP)
  • Sources displayed multiple times in Devialet App on dynamic config load
  • AirPlay working when 2 Expert Pro are on the same network
  • AirPlay metadata announcement 
  • Upon restart, Ram settings are now kept (affecting companion only)
  • On first start, fixed improper sampling rate of analog input (affecting companion only)
 
Partially fixed
  • Devialet AIR crashes when switching sampling frequency
 
Still being worked on
  • Roon “ Transport: Device in use”  with 2 Expert Pros on the same network
  • Default name on network not always the same (AirPlay / UPnP)
  • Analog inputs on companion not working
  • Fixed IP address mode
  • Network info not displayed on device screen
  • Devialet App not functional on streaming inputs when not streaming

This version has not been validated yet by third parties (Apple and Spotify) and is not a commercial version.

As a result, if you wish to test this version, you will need to join our Expert Pro Beta Program here.

You will receive instructions on how to download and provide feedback by email. Also, please read the README.pdf included in the DOS-2.2.0-beta12_12.2.6.zip.

If you have already joined, you will soon receive an email with download instructions.

At any point, you may revert to our final 2.1.0  Firmware 12.1.2 version, which you will find in the "my account" section of our website.

 

Have more questions? Submit a request

Was this article helpful?

11 out of 15 found this helpful

Follow

38 Comments

  • 0
    Avatar
    G51

    Already installed beta 10 on my 440PRO CI. Just tried to install the beta 12. The upgrade on the companion was successful. However the display on the master kept showing the 'upgrading dos' after more than 15 minutes. Have unplugged the master and did again but no luck. Reason unknown. Might switch back to the beta 10.

  • 0
    Avatar
    G51

    Reverted to beta 10 successfully.

  • 0
    Avatar
    Olivier

    Hello @G51,

    Thank you for your feedback. It might be an issue with SD card, would you mind trying again with the same card? And if still unsuccessful, try with another card?

    This version is definitely better than the beta10.

    Have a nice day.

  • 0
    Avatar
    Jakob Hansson

    I have succesfully upgraded my 440 PRO CI to this beta, so nothing wrong with the files. To early to report anything else.

  • 0
    Avatar
    Rajaish Taheem

    I have updated from beta 10 to beta 12 with 100% success. There was no issues uploaded and there appears to be no issues using the Ethernet or optical inputs.

    I use roonserver on a QNAP all is connected to a TP-LINK Archer VR900 router/switch via Postta CAT7 cables. Speakers are ProAc Studio 100s. SAM is at 50%. The connection from NAS to 220 Pro is via wired DevialetAIR.

    Most of all i think it sounds much better, the decay in transients is much more relaxed yet still highly detailed. Soundstage is more realistic, detail retrieval seams better yet smooth and open and tonal quality is first rate.

    Thank you. :)

    Edited by Rajaish Taheem
  • 0
    Avatar
    Fredrik Edfalk

    Just installed the new software. Works great. I also appreciate how you communicate what's been fixed and what you are working on, like direct IP address.

  • 1
    Avatar
    Garrett

    You write among the things to be fixed is

     

    "Roon “ Transport: Device in use”  with 2 Expert Pros on the same network"

     

    I only have one Expert Pro and I get the error after from 10 to 40 minutes of playing, so you need to fix it on one Expert Pro as well!

  • 0
    Avatar
    Rajaish Taheem

    You get 'transport: Device in use' in roon if you have more than one roon remote connected and if in the other remote you have paused the album. If you let it finish or stop the album it seams to not say any error message. It does have to wake the 220 pro which can take a few seconds.

  • 0
    Avatar
    Garrett

    No, I get it with only one Roon remote connected. 

  • 0
    Avatar
    Rajaish Taheem

    OK. will see if i can replicate the error too..  

  • 0
    Avatar
    Petri Kosonen

    Hopefully Devialet will also fix the Devialet AIR 3.0.4 driver on Windows, because it crashes the whole OS so easily.

  • 0
    Avatar
    Lite Viller

    Have now again wrong network name on Air App and Roon.

    It‘s shown as Expert 1000 Pro-9ca7-ETH

    Can‘t believe it. Using newest  offical software I solvent the prob diabling WIFi. 

    In this beta version I could not solve this way. Grrrrrrrrrre

     

  • 0
    Avatar
    Rajaish Taheem

    Why not simply rename your amp (click the cogs icon and give it a name you desire)  

  • 0
    Avatar
    Rajaish Taheem

    Maybe its just me but SAM does not seem as obvious as it was??

    Edited by Rajaish Taheem
  • 0
    Avatar
    Jan Kuneman

    Great sound and a good match with Roon version 298

  • 0
    Avatar
    Rajaish Taheem
    • roon 300 as well, can't find any fault or error messages via roon as some have reported. 
    • I am convinced that SAM is less effective than it was with beta 10.
    • When the 220 is sleeping i get a message in roon saying Devialet is waking up and it may take some time, but this is normal.
    Edited by Rajaish Taheem
  • 0
    Avatar
    Rajaish Taheem

    There's very little wrong with the software IMHO. a lot of issues i read from users seem to be network/IP/Mac address related... I bet if DHCP protocol was used throughout there'd be a lot less confusion.

    I'm running Beta 12 and roon 300 ATM and can't fault it...... then again i have everything switched off barr, Ethernet, optical and SAM.

    Whole network is wired through a TP-LINK VR900 router/switch, Postta Cat 7 cables, and all is DHCP bar the QNAP which I've fixed IP address within QNAPs configuration setting.

    Edited by Rajaish Taheem
  • 1
    Avatar
    Heine Streicher

    Loaded 12.2.6

    There are still 2 blank screens as you toggle through the info displays on the D220 (after pressing and holding the tone button on the remote). If I recall these 2 screens were used to display network info. There is currently no way I can see on the Devialet whether it is connected to my wifi network.

     

  • 0
    Avatar
    Alexsindalovsky
    I've observed the following behavior with both FW 11.x and 12.x beta version:
    if I play a number of tracks sequentially, there is complete silence after they finish (as it should be). However, if I then replay a track, or play a new one, when if finishes, there is a click/pop sound - clearly audible, and occasionally relatively loud. This had not been the case with the old board. Is this something that can be fixed?
    FYI: I stream from JRiver using AIR. I used my headphones to verify this sound is not a JRiver artifact.
    Edited by Alexsindalovsky
  • 2
    Avatar
    Markus Hübner

    Another news update would be very much appreciated.

    Edited by Markus Hübner
  • 0
    Avatar
    John

    Markus

     

    I wouldn't hold your breath if expecting Devialet to take much notice of what anyone asks/says on these threads. Out of the hundreds of posts on the multiple CI threads Devialet have answered in singular figures.

     

    Of the 20 posts on this thread Devialet have commented only once, and that was 1 month ago and nothing since!!!

     

    Edited by John
  • 0
    Avatar
    hiroshi miura

    Recently upgraded to Core Infinity (Epert pro 220). Preout doesn't work all. I think all configuration is OK (before upgrade it worked well). Something I noticed are that even though I set Sub/Preout is ON at start up, when I check on Remote Control , it shows always OFF. Another is that on Preout on configurator, I see COAX 1/2, does it mean that I have to use COAX cable, though my precut is connected to another small speaker in bath room.

  • 0
    Avatar
    Steven Segal

    As to replies from D, I’ve done a few posts here and sent error reports on the beta email. D has got back to me on some of them, asking for specific details of the circumstances for diagnostic purposes. They appear to on the case fixing things, but I would not expect them to reply to every post and email.

  • 1
    Avatar
    John

    Stevensegal

     

    Good on you for having 'D' get back to you, but not really understanding your comment "I would not expect them to reply to every post and email". There are 24 posts in this thread and only 1 reply from 'D', which happens to be 5 weeks ago.

     

    I'm also not expecting a reply to every post, but 1 in 24, and that was 5 weeks ago - you think that's good communication do you???

     

    Edited by John
  • 2
    Avatar
    Ian Goodwin

    And in total there have been 163 responses to these log reports but only 6 responses from Devialet. It is now 5 weeks since the last update.

    Assuming Olivier works full time (35 hours per week?) it is not unreasonable to expect a weekly update which might take 1% of his time. Even an update which says "no progress this week" is better than silence, and we have now had silence for 5 weeks.

    The detail at the start of this 5th February log was excellent, setting out what had been fixed, what partly fixed, and what being worked on, the latter being:

    • Roon “ Transport: Device in use”  with 2 Expert Pros on the same network
    • Default name on network not always the same (AirPlay / UPnP)
    • Analog inputs on companion not working
    • Fixed IP address mode
    • Network info not displayed on device screen
    • Devialet App not functional on streaming inputs when not streaming

    Surely we can have some sort of update on these after 5 weeks?

    I bought my OdA in January 2016 with a promise that the CI project would be delivered in June 2017 - 18 months was a long time to wait but it is now nearly 27 months which is far from ideal.

     

  • 0
    Avatar
    John

    Devialet

     

    Another 2 weeks has passed since Markus politely asked if you could provide another news update, and consistent as you are - nothing, zippo, zero, no info supplied.

     

    6 weeks since anyone from Devialet last commented on this website about the Core Infinity line.

      

    Hello, is anybody there??????

     

    Edited by John
  • 2
    Avatar
    Olivier

    Hello everyone,

    Sorry for the delay and not communicating more but we examine all your bug reports. Software and firmware teams have been working hard and we are now very close to a new release. We will post a new article here, with a detailed changelog, within a few days. 

    Have a nice day.

  • 0
    Avatar
    Garrett

    I'm really looking forward to some resolution of the Transport Device in use problem. When I sent my Pro in for the Infinity upgrade a little voice told me "Don't do it, everything is working great". I'm sure it will be worth having been done once the problem is resolved but at the moment I can't listen to Air for more than 15 minutes without the error.

  • 0
    Avatar
    Rajaish Taheem

    Thanks for the update Olivier.

    Good to know a new release is on its way. Can you confirm if this will be a beta release or an official certified version?

  • 1
    Avatar
    Ian Goodwin

    Good news.

    But surely it would be better to give a weekly update, even if "nothing to report" rather than leave us guessing for 6 weeks?

    Remember that delivery of a functioning CI board, promised at the Devialet Oxford Audio event in mid 2016 for delivery by the end of June 2017, is already almost 9 months late.

     

Please sign in to leave a comment.

Customer Service and Support will be close all Saturday during summer (July & August)