The next DirectStream update?

It turns out there wasn’t a new bug. On the other hand Darren and Paul had noticed something(s) they thought could be improved in the release candidate and since the rest of the release wasn’t ready yet I sent them two newer release candidates. I did learn something: I really appreciated how much better control I had over the filters compared to the stock filters. I could now quiet down some use of memory by better controlling when it was read, the new upsampler uses the most memory so I could get now get the low hanging fruit pretty easily. I did a quick look thru the code for other opportunities to do the same, but it would take some serious work to quiet the next biggest use of memory. I’ll do future coding with the new tricks in mind.

11 Likes

Wishing you much luck and a wonderful time. Don’t forget pictures. Do you have a PSA badge or Flag?

1 Like

It would be nice if the new release came with a Release Notes file detailing what issues were fixed and what improvements were mode. They have started doing this with the DMP firmware updates, and it is appreciated.

1 Like

I’m pretty sure they will, but FWIW the non sound quality related change to the FPGA is to fix the Redcloud bug with loud/dynamic music at high volume causing burbles/distortions.

2 Likes

Ted,

Maybe you can help me out with my own FPGA… mine is 58 years old and clearly having memory leaks. The main bus not only can’t handle the volume and therefore constantly goes into thrashing, but sometimes the FPGA will actually time out and put itself into a quiesced state and can’t be woken no matter the interrupt. I am worried about a premature abend.

Ted, my 58 year old FPGA needs some help. What do you think?

Peace
Bruce in Philly

5 Likes

I resemble that remark, but I assure you there are worse issues possible :slight_smile:

5 Likes

Hey Bruce you think the memory leaks are bad now wait till you’re in your 60’s.

Odd

I’m 58 too. I feel your pain.

Recently I reached the 70th, but can‘t remember precisely when…

2 Likes

I have found repeatedly that both subtle and profound things that are easily understood via speech are frequently lost in written posts.

As well as inside jokes between members. Yesterday (think it was - maybe the day before) on PPosts, for example, I replied to Steven, from whom I bought his former Harbeths, that I had a “loathing” for Harbeth - which is the opposite of the truth, but it was an inside joke for him, and maybe anyone else who regularly reads the actual responses to Paul’s Posts (a subset of the actual readership of his blog).

Despite this, when I spoke with my brother on the phone later that day (who is BTW fully apprised of my preferences, including having a shared appreciation for and ownership of British speakers and monitors) he asked, “Did you really mean that?!”

1 Like

My sarcasm detector has always been broken. So I never know for sure which side of a discussion people are on :slight_smile:

1 Like

I think often they don’t know either…

I just remembered this in another context :wink:

But it always takes two.

:grin:

You’re afraid of loosing it, because you might lose it? ; )

2 Likes

:grin:

The quote is from a discussion of being unable to locate a previous thread. We put effort into finding it but the earlier thread appears lost to to the big pile of bits in the sky.

1 Like

Don’t forget Kindle users Paul!

This discussion led me to think about a point I would ask @tedsmith, hoping it has not already been asked.
Are each gate in the FPGA stable in the time, not in term of response (0 or 1) but in term of performance. Is there a possibility a program which reside since 1, 2 or 3 years on the FPGA would display a different S/N efficiency than a program freshly implanted (via a fresh re-flash) ?
So would we have to re-flash the Redcloud (and the futur jewel you will produce) at some time to get the best performance?

Thanks.

yes it is generosity. But seems a bit unfair. i hope he also can travel in plane for holidays…

That is an interesting question. FWIW: I have not noticed any burn-in process with new FPGA firmware myself. But there is a very long burn-in process for this DAC itself. I have no idea how much of this initial burn-in process might be due to the FPGA. However if it ever does become an issue, its it quite easy to re-load your firmware.

Although a newly loaded build will sound better after a couple of hours of listening than it does when it is first flashed. However I believe that this is due to the DAC effectively degaussing the transformer from the previous power-down.

1 Like