That is what I am used to have not a big BANG...

DC is stable, every time I checked but perhaps this time it wasn't?

No problem anymore, the harmless tick is back again. 

Bert

Haven't heard this for a very long time... since W10074?


There was nothing changed here besides the Windows update and its related errors during the installation and configuration of XX...

One thing did change directly after the BANG though... the music sounds a whole lot more real now! Not after the update itself where the sound was as used before so there must have been something disturbing... or the system woke up suddenly?


Starting... 

Bert

EDIT: There is no Intona in the system here (has not been delivered yet)

At some point XX didn't start anymore, at all.

Turned the PC off (reboot didn't do anything useful) resulting in huge BANG through the speakers and again while booting...

Good to know that my speakers can handle such spikes well, a lot better than me! 

It did do the trick though... all seems to work normal now?

Next update will be for the long future, hopefully 10586.0 will stick for a very long time!

Now let's see what the Intona will bring when it has arrived and burned in properly.

Bert

Not here though... I am still running into similar problems with the 1.04b driver.

But only when trying to play unattended.

I can see the driver (opened panel) switching between sample rates which correct visible while playing attended but not when playing unattended. The error message come up...

The panel sticks to 96.000 or 88.200 depending on the track (wav, flac, MP3 all the same)

Today I have installed 10586.0 using the present date and related to that all seems to function normally even after many reboots...

No idea when or if it will expire but setting the date to 31st of januari seems to be no problem.

I will reset the renew date to today... or not ;-)

Bert

I have gotten them too and looked at the configuration and by selecting an option (somehow it was reset to standard) it connects without issues anymore... see image.

Bert

Haven't seen many complaints and weird errors floating by. Being too much at the front line before resulting in frustrations it seems wise to lean back and wait for a better moment.

Perhaps it is time for me to go ahead with the update as well then?

Any updates foreseen in the near future?

Bert

Apparently... Happy that I've waited with the 10565 install to find out that it should have been 10568.0...

I'll lean back and stick to 10240 for a while longer.

Cheers!

Bert

I can upload a copy through Wtransfer (the one I've downloaded 8 days ago) if anyone is interested?

Windows10_InsiderPreview_x64_EN-GB_10565.iso

EDIT: Oeps... only up to 2GB..

Bert

It is not the ultra low processor speed making things less interesting? I can have my processor lower in speed as well but to me this makes things lifeless..

We do have a different PC all together but still.. ;-)

Bert

Using that idea in mind then it will be slow in terms of digital responsiveness (all is DSP with common digital delay) but for the rest it will behave like any loudspeaker using the same drivers.

Not sure how well the DSP and amplification perform though...

The idea is pretty good, much better than trying to DSP a speaker in a room at the listening position. Still I prefer the one seat speaker like my latest design which is average evenly narrow at most important frequencies... and, no need to DSP the midrange as a bonus!

But you probably are suggesting other issues as well which is not my territory. ;-)

Bert

How fast? What IS fast...?

Bert

I am almost sure I did it like that but if needed to go back to normal OS then will unplug the network cable to be sure that there is NO communication with the windows server anyhow...

Bert

Perhaps it will work (new install W10) if you set the date of the PC a few months back before installing the OS?

It should not get any data from the internet anyhow for a minimalistic not updated OS...

Bert

Are you sure? Did you reboot after changing the date? I did and it did not work anymore... but changing the time in BIOS cured it again.

Better set it back a few months and make a batch-file to reset the date after you reboot.

Cheers,

Bert