DENAFRIPS FPGA Firmware Update (12TH Anniv.)

[Remd]

My support from Denafrips themselves is opposite that of jhnpennington. Also take into account we only know his side of the story; add the fact the item in question was NOT sold by Denafrips, nor Vinshine audio, so who knows what was done with the unit before it got the OP or if the unit is even registered with Denafrips...

Also interesting this question was never answered by jhnpennington...

Instead...


Anway...

Have you contacted them > support@denafrips.com ???

I know when I contacted them my questions were answered the next day. And I've spoken to them a few times here's but one...

I'm in contact with Denafrips support too and I confirm that they reply fast and contact is very good
When working on a specific bug, there isn't a lot of resolution advance information during long time (like it was from winshine support getting they information from denafrips). But, as soon I send them an email about current debug status, the reply is fast.

 

[sygnus21]

I'm in contact with Denafrips support too and I confirm that they reply fast and contact is very good
When working on a specific bug, there isn't a lot of resolution advance information during long time (like it was from winshine support getting they information from denafrips). But, as soon I send them an email about current debug status, the reply is fast.

I would add they can only answer what's given them in the form of a question. I'll also remind, Denafrips, Vinshine Audio, and many others can't/won't support a product not sold by an "authorized distributor"; whether the dealer is high end or not has zero to do with "authorized distributor".

Yeah, I know this is controversial for some, but it doesn't matter our opinion, it matters what Denafrips says per their rights under their Authorized distributor policy. And it's NOT just Denafrips, many companies have had this policy for ages. It's why I only deal with authorized dealers where electronics are concerned.

BTW, if you have an "authorized" product from Deanfrips you'd have a warranty card with the item. I bought 3 items (DAC, Headphone amp, Iris DDC) from VInshine Audio (blue cards), and my Hermes direct from Denafrips (black card)...

Where you buy is where you buy but understand if not from authorized you risk support issues. And yes, warranties can be transferred.

The balance of the warranty is transferable from the original owner to the second owner. We need the original owner to initiate the warranty transfer to validate the warranty transfer.

And yes, I'm fully aware you can save money going the non-authorized route (I ain't mad), just be aware of the other costs.... support.

 

[NehPets]

I think that just telling them you have a lot of glitches since 1.6 was installed and ask for a correction, you'll get an other answer !
What is the firmware level on new 15th products ?

Are you sure 1.8 was a GA build (for your DAC / Year released) or a build used to resolve specific problems ?
( 1.8 not tested ! may be it was fully tested on newer products but not on previous one )
Denafrips (developer) is able to tell which firmware is the right GA and then, the latest GA is the latest official firmware for a DAC model / year released

Newer GA are probably tested on latest product releases e.g. 12h or 15th only...

GA = General availability (only firmware having got a General Availability status by Denafrips are official builds)

There's been a change of nomenclature since Ares II; Ares 15th comes with A15.1.0

 

[Rikkipuu]

Be careful, with a given named DAC like Ares II, Denafrips used different chips in the same model over time without changing the name on the DAC , so if you have an early release you might brick the DAC by adding the latest firmware released as they may have had to change to another chip for either improvements or supply chain issues which were common during the bad COVID years. Just having the manufacture date/year does not specify the correct firmware.

I had this issue with my Terminator Plus, Vinshine had me open the DAC and take a picture of the chip number and send it to them before they would send me the correct firmware. Apparently not all the Terminator Plus DACs had the same chip so different firmware versions were released for the different chips.

After I upgraded the firmware on the TP, it did not work with my Denafrips Iris so I ended up selling both, .

 

[sygnus21]

I had this issue with my Terminator Plus, Vinshine had me open the DAC and take a picture of the chip number and send it to them before they would send me the correct firmware. Apparently not all the Terminator Plus DACs had the same chip so different firmware versions were released for the different chips.

I don't think this is particular to the Terminator as this was also required of the Pontus and Venus and why as soon as I got my Pontus 12th-1, I opened it and took a photo of the FPGA chip for future use in case I need it.

Also, wouldn't advise putting an older firmware on a newer model - if your model came with 1.4 (mine did), I wouldn't put 1.1 on it. Yeah, I know someone is going to say, "I had no issues", but I still wouldn't do it, nor recommend it.

 

[szore]

I don't think this is particular to the Terminator as this was also required of the Pontus and Venus and why as soon as I got my Pontus 12th-1, I opened it and took a photo of the FPGA chip for future use in case I need it.

Also, wouldn't advise putting an older firmware on a newer model - if your model came with 1.4 (mine did), I wouldn't put 1.1 on it. Yeah, I know someone is going to say, "I had no issues", but I still wouldn't do it, nor recommend it.

My Ares II needed chip photo approval too.

 

[Rikkipuu]

Yes, I’m saying priced with due caution. Alvin at Vinshine did all he could to avoid self inflicted pain and suffering. He warned installing the incorrect firmware would brick the DAC. Fixing a bricked DAC is way above most users ability and needs to be done in house.

 

[sygnus21]

Yes, I’m saying priced with due caution. Alvin at Vinshine did all he could to avoid self inflicted pain and suffering.

I can assure you Denafrips will do the same if you give them a chance.

He warned installing the incorrect firmware would brick the DAC. Fixing a bricked DAC is way above most users ability and needs to be done in house.

And yes, installing a firmware update designed for an older model on a newer model revision is not a wise move. Do so at your own risk.

 

[jhnpennington]

I think that just telling them you have a lot of glitches since 1.6 was installed and ask for a correction, you'll get an other answer !
What is the firmware level on new 15th products ?

Are you sure 1.8 was a GA build (for your DAC / Year released) or a build used to resolve specific problems ?
( 1.8 not tested ! may be it was fully tested on newer products but not on previous one )
Denafrips (developer) is able to tell which firmware is the right GA and then, the latest GA is the latest official firmware for a DAC model / year released

Newer GA are probably tested on latest product releases e.g. 12h or 15th only...

GA = General availability (only firmware having got a General Availability status by Denafrips are official builds)

The equivalent version on newer products was 1.3. For the FPGA on my dac it's 1.8.

 

[Remd]

It is now more than 17 months denafrips is telling me working hard on the firmware to correct the bug !
From my point of view, they don't work on the firmware and are just trying to win time and like they wrote previously, products above 2 years are old products and dev works on news products.

Can Denafrips products be recommanded ? (despite its very marvelous sound) when they do not respect they legal garanty having reported the firmware problem months before end of legal denafrips garanty (they know the bug is within the firmware and I sent them many details and videos showing the bug). They do not provide feedbacks and have to request some to them each time (one per 2 monts). I've got some information from previous W. support that the firmware has to be fully rewrittent starting from december 2023 (to much correctives added above main code?)

 

[sygnus21]

What are you talking about?

Firmware for what bug? What DAC?

 

[Remd]

What are you talking about?

Firmware for what bug? What DAC?

Terminator II (firmware v3.7 - doesn't exist under v1.0 but v1.0 is far below in terms of quality)

USB disk connected to streamer which is I2S connected to the DAC (COAX has the same issue - issue reported immediatly after V3.7 was available - start of June 2023)

Problem was identified been into the firmware (I've got a beta firmware test on january 2024 which corrected this bug but the sound was auwfull, sound quality not implemented under beta - since then, nothing else except a may 2024 GA firmware based on a fully new code (Therminator 15th same FPGA shipset) whish provided no analog output when I2S or Coax or USB, nor analog output if PCM or DSD) proposed to test if this one could resolve the problem - my Terminator was told been an OLD product and development is focused on new products !

(playing a DSF64 track while playing a PCM track puts the DAC into bug - DSD input not selected, left on to a strange PCM mode. Have to switch input to an other entry and then back to get DSD correctely on. Other bypass found is to switch to a DSD track after the PCM plaied about 50s but not more than 1 minute !. DSD to PCM works well)

 

[Weissenborn]

What's the latest firmware for a Denafrips Venus II 12th-1 ?

 

[Remd]

Terminator II (firmware v3.7 - doesn't exist under v1.0 but v1.0 is far below in terms of quality)

USB disk connected to streamer which is I2S connected to the DAC (COAX has the same issue - issue reported immediatly after V3.7 was available - start of June 2023)

Problem was identified been into the firmware (I've got a beta firmware test on january 2024 which corrected this bug but the sound was auwfull, sound quality not implemented under beta - since then, nothing else except a may 2024 GA firmware based on a fully new code (Therminator 15th same FPGA shipset) whish provided no analog output when I2S or Coax or USB, nor analog output if PCM or DSD) proposed to test if this one could resolve the problem - my Terminator was told been an OLD product and development is focused on new products !

(playing a DSF64 track while playing a PCM track puts the DAC into bug - DSD input not selected, left on to a strange PCM mode. Have to switch input to an other entry and then back to get DSD correctely on. Other bypass found is to switch to a DSD track after the PCM plaied about 50s but not more than 1 minute !. DSD to PCM works well)

Do you know what !

Start of december (3rd), I received an email suggesting me to reload the v3.7 firmware and if not ok, they will inform development...
The v3.7 which has the bug and which was reloaded several times at they request and for which a beta test was provided in january which corrected the bug but the sound wasn't optimized and bad compared to v3.7
This means that nothing was done since nearly one year ! Support doesn't no more exist !