2.08d settings and tick issue

[Robert]

Peter,
        I updated to 2.08d today and reloaded into Ram. Trying your new settings works now. I really don't know what I did other than reload DAC driver. These settings sure sound better more of everything.

Do have a problem with background ticks especially in first track of an album played, on second track disappears. Second or more albums it doesn't occur.

I tried this on W10 10586 - 2.06a and still the same tick. Don't think its a 2.08 issue possibly something I've had for a little while.

Robert

[PeterSt]

Hi Robert,

Is this 16/44.1 or 24/xxx ?

Is the interval of the tick related to the SFS ? -> it should. But you need to try it. So if you can easily perceive it and double the SFS, you should perceive it half of the time from the previous setting.

Do have a problem with background ticks especially in first track of an album played,

Windows 10 is somehow poor in something "first". Just think of the long time it takes for 14393.0 before the "Services Stop" screen disappears and you know what I mean; only happens once for the day's session (even when the PC is on 24/7).
So what happens if you start that first album, let it play for a second, stop, and restart playing it ?

Peter

[Robert]

Is this 16/44.1 or 24/xxx ?

Is the interval of the tick related to the SFS ? -> it should. But you need to try it. So if you can easily perceive it and double the SFS, you should perceive it half of the time from the previous setting.

So far 16/44.1 files.

Changed SFS up to 120/120 and Q settings back to old no difference in ticks. Restarted Ram OS no difference. Funny thing ticks seem to go when playing whole albums after first  track. Crossed out Xx in Ram OS still ticks.

Going back to new settings .9SFS and Q settings still ticks.

Robert

[PeterSt]

Robert,

Have you considered that it could be your new DAC ?
Can you prove that by means of another DAC, perhaps ?

On a side note : it is quite well possible that with 2.08 you suddenly perceive this (which it has been there prior to 2.08). This is a bit how 2.08 unveils "detail".

Regards,
Peter

[Robert]

Thanks I certainly feel the ticks were there before 2.08. It is intermittent, today I loaded Ram OS and screen only reset once and no ticks at all.

I have changed DAC to the Oppo 205 which can take 32/768 files. It has been ticking intermittently since this. Sold Benchmark Dac2 it only ran at 24/192(4x on slider) max.

Interesting from a process of elimination I have discovered that reducing the slider from 16x(705) to 8x(352) the ticking stops. Arc prediction is engaged. Does this mean the computer is running out of power?

Robert

[PeterSt]

Hey Robert,

Interesting from a process of elimination I have discovered that reducing the slider from 16x(705) to 8x(352) the ticking stops. Arc prediction is engaged. Does this mean the computer is running out of power?

No, that seems impossible to me. The playback itself virtually does not use CPU (you can check in Taskmanager). And with Arc Prediction (no Custom Filter) it can't be a bug in the filter programming either.

If it is so that the ticking is constant for its frequency/occurrence, regardless any XXHighEnd setting (but that sampling rate of course) I'd consider "electrical error" and a capacitor doing this to you. This is a bit tough to explain but think like a capacitor loading too much energy (if that would be possible in the first place) and that needing to escape. The loading builds up slowly until it bursts.
I am completely making this up and maybe it can't exist at all, but the lower sampling rate might draw just that little lesser of energy the capacitors must provide.

A software bug in the DAC is much more likely of course, but I think this won't express with the time period you imply (and rather each sample and then you will perceive it just as poor sound).

HTH
Peter

[Robert]

Where would you suggest to start to look for electrical error: Computer hardware ie: motherboard, power supply?

Could well be software bug in Dac. 

Robert

[PeterSt]

Robert,

I would ask the manufacturer (and learn a few new languages on the fly ).
(btw, I talked about the DAC and not PC or something)

Easiest would be to lend a DAC from someone (or a shop).

I am just thinking ... You will have a kind of strange problem, because you can not ask it to anyone (e.g. CA) because there will be nobody with 24/768 playback software. AFAIK only XXHighEnd and HQPlayer, but both do that explicitly for the NOS1 as there is no other DAC functioning like this. And your Oppo will have an AKM D/A chip (32 bit) I suppose.

But thinking further again ...

The Driver software you will be having for that, should be Chinese XMos stuff. Nothing about the Chinese, but it won't be much official.
Can I be right ?

Peter

[PeterSt]

Robert,

I must call back on my idea about the DAC. I mean, I suddenly recall "the first track only" and how could that be the DAC ...

Possibly it is the 32 bits which I *do* pass on to the DAC. So for me and most they are cut (to 24 bits), but not for your 32 bits DAC ...

Regards,
Peter

[Robert]

Well today I booted Oppo and computer/Ram OS into action and everything worked perfectly all day. Mind you I removed Intona before doing this. Need to repeat this.

The Oppo can definitely take 32/768 input.

Your new settings are better sounding.

Robert

[PeterSt]

Your new settings are better sounding.

Thank you Robert.
Peter

[Robert]

From above reply all went well until I tried to play a hires album 24/192 and ticking returned. Only stopped with reducing sample rate to 32/384 on slider. Going back to 16/44 files it continued to tick at 32/768 but also stopped at 32/384. This without Intona which I'm warming to now.

I rebooted Ram OS and it ticked from start even into subsequent tracks. Only stopped when reducing to 32/384.

This generally sounds like a bandwidth or buffer issue. Have you tried an alternative USB cable and port on the computer?

If you are using a Windows computer, have you tried adjusting the Buffer Size to see if there is an improvement in performance?

Got this reply from Oppo. Have tried another USB port and still ticking. No other cable at the moment. Then on second album ticking goes on second and the rest of the tracks. This with 16/44 and 32/768.

Think I might need to get the "Lush" now as a result of removing Intona.

Robert

[PeterSt]

Robert,

Can you try to elaborate on the frequency of the ticking ?
I think you said it is always constant. But what is the time interval between two ticks ? And are they always as loud when there ?
It starts to be intrigueing.

Peter

[Robert]

Late reply but it is now apparent that when I reboot the Oppo the ticking is stopped. I've removed the Intona now and it definitely sounds better without, especially with the current Xxhigh2.08 version.

I suspect its in the Oppo that's causing ticking. Interesting its not happening at all with 16/44 files only when I change to 24/96/192 in a listening session.

I was interested to see you suggest SFS 1.50. I have been feeling lately, the sound, in particular the treble has been subdued at .90 and 1. I do prefer SFS at 1.50 treble its more lively. Better balance with the bass.

Robert

[PeterSt]

Robert,

That other night I just changed the SFS to somewhat higher without having in mind to what exactly. Day before yesterday I found that I had set the SFS to 1.80 (so apparently I doubled it). This is also good for the volume change (hardly any stutter with this SFS setting) but it wasn't about that for me. A more friendly sound it was about (mostly related to MQA) and I think it helps for that.

Thank you for the feeback on the Oppo.
You could try to stop 16/44.1 playback, kill the Sound Engine (click blue led in the right hand border), select the 24/96 etc. and start playback.
This re-engages the DAC in a somewhat different way and it could be interesting to know whether this makes a difference (now no ticking).

Also revisit your own observation with the first track vs the second. You may have a different opinion on that now, which could be helpful, also to me.

Regards,
Peter