09-z1 issues

[PeterSt]

My dac is 24/96. With a proprietary connection between the source and the dac it can play sample rates up to 192. I do not have this connection so I should only be able to play 24/96.

With z1, if I 2x the sample rate of a 24/96 file, XX shows 192 in the display and the file plays. ( how can that be!) If I then tick arc prediction the slider at the bottom of xx moves but I get no sound. This is with scheme 2. If I try scheme 3, I get many "Engine 3 stopped working" errors, but about 1 in 6 times I get the same results with scheme 2.

Because I have playlists that have both redbook and high rez files, z1, in its present configuration doesn't work for me, cause I use arc prediction for all the redbook stuff. Is there a plan to be able to choose what type of file gets upsampled?

It is my conclusion that this just can't be solved otherwise than specifying an output rate. So, this time not for conveniency (Release Notes), but because otherwise the Slider Setting will just be non-sense.

Hmm ...

[jarek]

Peter,

Version 8 and 9zb plays well with dCS on double AES. Version 09z1 is different. On my DAC it plays only 1x.

By the way - dCS accepts only 32bit transmission, swiching to 24bit I have message "Device allocated, but cannot play. Check...." not only on 9z1 but also on previous versions of XXHighEnd. So this is not the case...

At least latest version displays what intended to do correctly, that means, set to 4x, dispalys 32 bit 176400Hz which is correct. But DAC does not play displaying the message.

[boleary]

It is my conclusion that this just can't be solved otherwise than specifying an output rate. So, this time not for conveniency (Release Notes), but because otherwise the Slider Setting will just be non-sense.

Hmm ...

Thanks Peter, I wouldn't worry too much about it. At some point a new dac will just have to happen......

[jarek]

Peter,

my default configuration is PC with LYNX working in slave mode, accepting clock from external source, as well as DAC. To check things up, and identify the problem, I set PC to master and DAC to slave passing the external clock by. Now I understand why new version does not play 2x and 4x with external clock.

When I play 16/44.1 track and specify 2x, it plays 24 bit/44,1kHz, if I choose 4x, it plays exactly the same : 24bit/44.1kHz, instead of 24bit/88,2 and 24bit/176,4 kHz accordingly. Strangely, XXHighEnd shows 176,4kHz when set to 4x, but dCS dac identifies this as 44,1kHz. It must be true, because dCS does not accept anything more than 96kHz on single AES, so when XXHighEnd dpsplays 176400 - this must be the false value.

[PeterSt]

Jarek, this certainly will be true. The display is redundant to reality. The question is : why does this happen to you ?

OF COURSE (hehe) you are alone - well, so far.

Can't this be related to the double AES connection somehow ?

So :

1. The display *is* redundant;
2. It can happen that something the display allows, is not allowed at the "real playing side". But :

This would lead to your first post about this, not to "and I (XX) do what I want anyway".
So in the end I don't recognize this at all.

If others do, please let us know !!


Jarek, important : If you take 16/44.1 as the base, I can't think of anything that has changed *there*. So, are you very sure this didn't go wrong work in 0.9z(b) ? Not that I refuse to believe you, but I must have some clue to what is happening. If it changed from 0.9zb, I do NOT have any clues.

Thanks as always,
Peter

[jarek]

That is why I changed to single AES to be sure.
So, 16/44.1 tracks (I tried a loooot of them) plays :
1x -> XXHIghEnd shows 24bit/44.1kHz, LYNX MIXER shows clock 44.1kHz, dCS shows 24/44.1kHz
2x -> XXHIghEnd shows 24bit/88.2kHz, LYNX MIXER shows clock 44.1kHz, dCS shows 24/44.1kHz
4x -> XXHIghEnd shows 24bit/176.4kHz, LYNX MIXER shows clock 44.1kHz, dCS shows 24/44.1kHz
so, changing 1x, 2x, 4x does NOTHING except display in XXHighEnd.
Just checked.

Just to be sure. I returned back to b version, and it plays just right:
2x -> XXHighEnd shows 24bit/88.2kHz, LYNX MIXER shows clock 88.2kHz, dCS shows 24/88.2kHz
4x -> XXHighEnd shows 24bit/176.4kHz, LYNX MIXER shows clock 176.4kHz, dCS shows 24/174.4kHz
Cannot do anything wrong here.

Jarek

[PeterSt]

Ok ... It is my conclusion that you didn't denote any filtering means. So, just 2x / 4x without any of the filter buttons active. *Then* indeed the output sample rate stays the same ... (and this is NOT intended, hence a bug).
I hope you can confirm this.

About what the dCS accepts ... if that is 32, why does XX shows 24 ? I don't think it can. It can allright, if DAC Needs is set to 24.
Furthermore, what happened to your earlier posts about the DAC doesn't accept etc. ? ... I don't hear that back now ? Or is that related to the two AES lines ?
Besides, notice that it is the Lynx which determines what is accepted, not the dCS (unless you connect it USB).

?

[jarek]

Peter,

truly I do not try to use any filtering, since on previous versions I did not touch it. Any kind of filtereing in my setup destroyed the sound.

You are right about 24/32 bit. My mistake - I should have written 32 bit and not 24 bit in the post. Of course XXHighEnd displays 32bit instead of 24bit, and dCS does not accept 24 bit comunication.

LYNX is producing output on single AES when sample frequency is < 176 kHz. Only on 176/192 it uses double AES. So when I said that I'd switched to single AES = switched DAC to single AES, because second AES does not play at all when <176kHz. This is the main reason I used to play always on 4x and wanted 88.2 or 96 tracks to be upsampled 2x when XXHighEnd is set to 4x.

So, will you enable upsampling 2x and 4x without filtering ?

[PeterSt]

So, will you enable upsampling 2x and 4x without filtering ?

Hahaha, I am afraid you are getting crazy now ...

... There is no such thing as upsampling without filtering ...

If you apply the 2x or 4x and don't use any *upsampling* (which is the same as filtering !!) button, you're only doubling or quadrupuling the samples. It does nothing, but may have implications on jitter at the DAC side.
So try to understand : this is *not* upsampling, and there is no way this can incur for higher (fake) resolution, as there is no way it will filter harmonic distortion. It only sets the DAC to the higher sample rate and feeds more samples of the same.

But I will solve the bug that Double/Quad/etc. without upsampling works again.

Regards,
Peter

[glynnw]

Very good, Peter.  I have latest version on both my computers, working well.  Only thing I have noticed (a VERY small thing) is the OSD time display doesn't reset the far right digit at each tick of a second.  The new number is superimposed over the last one, so by the time all 10 digits have ticked by, there is just a red square there.  This is on both computers.  I can live with this problem pretty much forever.   Thanks for all your hard work.

[PeterSt]

Hey Glynn, thanks. I guess not many people use the counter anymore (including me). Ok, will look into it !

[jarek]

Peter,

I have found some tracks (non-HDCD) that does not play properly when using 4x IntiImage upsampling. I do not know if it is already known issue.

On attended the problematic track plays till specific point but seams to omit some data then - skips some data in the track.

On unattended, this track plays to specific point and then track is skipped to the next track. Looks like some data recorded on the track causes problems. I can forward the sample track if you want.

Thank you
Jarek

[PeterSt]

Jarek, thank you.

From your description I knew this already, but I couldn't place anymore where it went wrong like this. But now I know again : HDCD.
I already knew it from before 0.9z, but I just couldn't find the problem anymore !

So as said, thanks !
Peter

[jarek]

Peter,

I have found a track that does not want to play at all on AntiImage 4x. When you press play, XXHighEnd does not react. This is 6-th track, Coming back to life, Pulse, Pink Floyd. Maybe this will help you to track the problem.

[PeterSt]

Ok, I have that album, assuming it's not an extract from the DVD. I'll look into it.