New Firmware 10.1.0

[yabaVR]

I agree. I really like 7.1.3 but use 8.1 so I can use SAM which has clear benefits in my system.  I have tried all the subsequent FW releases and find them too bright with over-emphasised treble which increases the sense of airiness and apparent detail but makes recording hiss intrusive and increases listening fatigue. I also find the later releases less warm.

Seems like FW preferences are still system-dependent, which I don't find particularly surprising.

Hey Philip,
the recording hiss you mentioned actually is (in most cases of good recordings) out of phase audio signal informations (or simply put jitter) induced into the audio signal at some section of your system. I read in your signature that you are streaming from a MacBook. Unfortunately I'm not familiar with tuning software for Apple but what I can say about my journey on the PC side is that I was unhappy to stream from a PC until I tried some special tuning software like 'Audiophile Optimizer', 'jPlay' and the like to cut down all unnessesary processes that're running in the background of the OS. This, and only this, lowered the jitter of my PC as my source to a minimum level so that it is now pure bliss for me to listen to it.

Beforehand I couldn't get rid of the underlying digital sound pattern in the music and it's my thinking that you're hearing this digital sound pattern originating from your MacBook to a larger extension with the newer firmware versions. I also read somewhere that Apple OS have even more processes/services running in background than Windows...so that could make sense.
Downside to intensively tuning the PC is that it's now solely dedicated to audio, but if I look at it like a CD-Player it is a bargain for an audio source. If you can ever make it to get hands on a highly tuned audio PC it could be worth to install AIR on it and give it a try in your system.

I can say from my tuning experience that it is not more brightness or over-emphasised treble the new firmware produces rather than very high resolution of details and this results in more 'audio informations/time frame' that is then messed up by jitter patterns leading to more hiss and digital sounding. Increased Resolution of the signal is, in my thinking, nothing more than just more micro details that now come thru that were blocked on the signal path before. More signal informations equals more energy coming thru equals more level (higher dynamics) on particular frequencies/time frame equals hiss and over-emphasise when impured with jitter. Just my 2cents.

gui

Hi gui,

thanks for taking time to write your detailed post. I will certainly think about what you say. Worth more than 2 cents!

It's difficult to provide all background info in posts but my signal path is quite simple: MacBook Pro/Audirvana+/AIR > wireless router > D200

The 'hiss' I mentioned only appears on old recordings where it was probably tape-derived or some modern recordings where its been added to make the recordings sound more like vinyl ?!   The hiss is there with earlier versions of the FW but is increased with later versions - 8.1.3 onwards. Plus cymbals are emphasised.

My understanding is that computer clock jitter shouldn't be an issue in TCP/IP based transfer (as the signal is re-clocked in the router and again in the D200) and the issues that need attention are minimising common mode noise and RFI interference. As I'm running wireless connections common mode noise isn't an issue and there's not much I can do about RFI other than make sure I have a strong wireless signal - which I do.  If any of this is wrong please let me know!  

[EDIT: now you might well be correct that increased resolution has highlighted a problem elsewhere in the system - the one area I haven't looked at recently is the quality of the mains power feed. It's maybe time to experiment in that area.]

Sadly, I seem to have a more pressing problem as AIR 3.0.4 has just stuttered and replay stopped. This has only happened since upgrading to OS X 10.12.4 yesterday... AIR/Audirvana+ has always worked perfectly for me so far in all previous versions.

Thanks again,

Philip

Hey Philip,
I was referring to my PC and the problem that I came about was not only the signal transfer to my D200 (USB-Cable has a BIG sound impact, yes) but rather the process of reading the audio data from disk/SSD transferring it to the Soft-Player, then transferring it to AIR (in my case to USB-Port) and AIR getting it to D200 over TCP/IP.

Up from the data output of the disk/SSD the data can be compromised by jitter...and it is. The more processes/services are running in background of the OS and the more devices are running like fans/HDDs/DVD-CD-RW or else the more you have bad EMF and Power Contamination inside your PC/MAC that induce jitter to the audio signal. AIR over TCP/IP is then transmitting this already jitter impured audio signal bitperfect to the D200...but it's already corrupted with jitter before that.

The next problem here is that all PCs/MACs/Laptops are differently configured. There is no reference base to start from until you dedicate your computer to audio and strip the OS down to a minimum. Then there seems to be consensus between people doing this. There are still differences though because you can use some renderer or a 2PC constellation and more but you will have a source you can highly depend on is not sounding digital harsh or the like anymore. Up from there improvements are in the area of 3D mapping, realism, naturalness and for sure it will get smoother too but not to the amount that you couldn't enjoy it before and have to switch to a former firmware to compensate.

edit: There is one thing you can have a look at. It's the SMPS (power supplies of your mobile, LED/Halogen lamps, turntabel and any electric device) in your audio room. Especially those stickin in the power strip of your audio system. They are contaminating the power line and have a big impact on sound (Devialets get mad on these). If you are curious about the effect pull them all out at once and listen to your music again.

gui