The final release of Massive for MK2 DAC

Audio Components DACs
383

Version 2.6.3

Date 08/09/2023
File image.bin

Description
USB audio driver should show as 3.2.a91f in the Version screen. If not, this load can be run to reprogram the USB audio driver. If running this load doesn’t fix the problem, go into Menus | Audio In |
Auto Power, and make sure USB is set to On (not Auto). After the USB is working properly, the USB
Auto Power mode can be set back to Auto.
This load only contains the fix for corrupt USB audio drivers. If your audio drivers are working, there is
no need to update. If you do update, it is fine to stay on this load (you don’t need to down-grade to
2.6.2 afterwards).

Fixes
• Fixes corrupt USB audio driver.

Version 2.6.2

Date 06/05/2023
File image.bin

Description
Firmware 2.6.2 adds intelligent muting to reduce noise issues.

Fixes
• DAC-613 Improve muting algorithm to help with noise issues

1 Like
384

Massive FPGA 233 came out with Firmware v3.1.0

The Beta Massive was FPGA 228. It came with Firmware v2.6.2

But v2.6.2 was already out for a couple months at least by then.

1 Like
385

Probably Yes, and you’ll probably hear the cold air too if you are impatient with the DAC. /cheers

386

Okay, I might need a bit more guidance before I… drop back a release level from Massive. I’m confused as to what I should be doing. (No surprises there.)

In the download archives, the top of the list shows “PerfectWave DirectStream DAC MK2 v2.6.2”. Opening the ZIP file, I see only Instructions, Release Notes, and a single image.bin file.

Any other available downloads seem to be older.

Is it safe to stick this in and choose from the installation screen? Or, would there be some mismatch between firmware loaded with my recent Massive installation, and FPGA. Is this image.bin file the FPGA, or the firmware?

Some guidance would be most welcomed.

After giving Massive a few days burn-in time, our session last night still seemed too bright and brash, leading to listening fatigue. I’d like to step back to see which is better, but I’ve never stepped back before.

387

The firmware is not part of the sound of the DAC. The fpga load is what is responsible for the sound. You can simply place another fpga code on the jump drive. Power off the back panel switch to insure the system sees the other load than go into the system menu and select the load you want to try. The process will erase the flash, copy the new load to the flash and than write the new load into the fpga. How long have you been breaking in Massive final? You may be hearing changes as the switches in the fpga break in.

2 Likes
388

I have also had times where it was too bright and others where it was bass heavy and it has gone between these more than once. Not sure how many hours you have on Massive but for what it’s worth here’s my experience.

I went through the frequency variations and some odd soundstage anomalies in the first 50 hours. Around 50 hrs everything locked in and there were small improvements until about 60 hrs. At this point a major improvement (clarity, resolution, soundstage) without any of the above problems. Then yesterday at about 65 hrs a slight emphasis in the presence region appeared and without any of the above problems.

I am hoping this will settle down soon and I’ll be “home free” regarding breakin, but Massive has bit my butt several times already.

1 Like
389

Let’s see… I installed Massive on Friday when I got back from a trip. I’ve been running close to 24x7 since then, so I’m about 110 hours now.

390

That’s actually comforting to know, thanks.

Some things sound great, but others have me diving for the volume-down button.

391

I had the brightness experience last night. I had thought I had it run in and had stopped running it constantly. Perhaps time to burn in more or just sinus congestion that set in today.

392

Sinus congestion ruins my hearing, I simply have to wait it out when I get it.

1 Like
393

My understanding is that PS Audio is aware something happened between firmwares that created losing the bitspeed/depth reading when the source, even playing fine, shows the red dot. We may be waiting a good while, but I believe they’ll attempt to fix this on a future firmware release.

394

Rob,
About 390 more hours and you should be good to go!
It takes a while when the code uses areas of the fpga that were formerly unused.

2 Likes
396

Then wait I shall.

397

So about 500 hours for you? When did things kind of stabilize with no more large swings in freq?

398

I seem to recall Ted saying something about 100 hours or so for FPGA gate burn in. That number (before he said it) was consistent with my experience. It’s the trannies that take the longest time in this architecture. YMMV.

1 Like
399

It has been stable for a while now. Hard to say when that actually occurred.

400

I’ve always thought that when something sounds better to me, it sounds slower.

401

I’ve also noticed that things sound slower when there’s not as much distracting information there. But I think it’s quite possible that things being more dynamic than one is used to might make it seem faster. Similarly, the above-mentioned better phase coherency may well add to a sense of speed (or at least a sense of better timing) since the transients are better defined in time.

10 Likes
402

Thanks Ted! Now if we can just get you to translate everything I hear to english we will be set. :slight_smile:
Lee

403

Am I the only one that strongly prefers the Antero 208 software vs the Massive ?

I have BHK 250, BHK preamp , PSAudio P20 power regenerator , Aurilic Aries G2.1 streamer, Upgraded crossovers on my Tekton Moab Soeakers and all Aucustic Zen cables except the dragon going to the P20.

5 of us audiophiles listened repeatedly ( it wasn’t even close)

Is it synergy specific?

1 Like