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.



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

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

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

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

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

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

Peter tried those settings only got bad stuttering, back to old settings.

Sometimes with 2.08a startup getting regular ticks in playback music. Only fixed by crossing out XXhighend and restarting.

Aha Peter some new settings for 2.08a. What about Q10?

I'm finding a new level of detail, so much that a vinyl rip has been exposed as I hear a scratch never heard before.


Robert

Yes had to go to bed what with daylight saving kicking in.

2.08a working fine no glitches. Glad to help.

Robert

After 2.08 is loaded fresh into ram the first message is:

The first- Caller :J could not find the file.
Second- System IO. File not Found ( From ...unicode track0001.wav.)
Third- Not enough space on playback drive.

After this when playing more tracks only the Unicode track0001.wav message comes up and when shutting down xxhighend.

No MQA, no Tidal in fact no remote. Just 16/44 flac music files from my server.

No 2 the one you want. The message also comes up when deleting Xxhighend from screen.

Yes it is happening at attended the same. I've sent 3 files with one track engaged at attended.

I deleted XXEngine3.exe and AutoHotkey.exe from 2.07. Installed 2.08 over the top 2.07 files then restored AutoHotkey.exe to XX folder. All works so far.

Robert

I have the same errors. Clicking away errors, it plays music. But errors come up everytime a music file/album is loaded. The music files have all permissions.

XXhighend 2.08 certainly more stable after Ram boot. But needs two boots from first start to get all working.

Sound is improved more than slightly!!!

Robert