Hi,
Yes, indeed I can understand, it takes too much time to see every special combination.
At present I use more "Arc Prediction", but it can change again in the future.
With a rate of 44,1, 48, 88,2 or 176,4  I need to turn on the Sample Rate Converter of my "Power" DAC (or digital amplifier) but OK, it works not bad.
Here, I like to explain an other problem, but it's not not a problem with high priority.
It happend when reading some 48k files, with arc prediction.
      - fs * 1 : XX displays "input 48k, output 48k" and my DAC displays 48k
      - fs * 2 : XX displays "input 48k, output 96k" and my DAC displays 96k
      - fs * 4 : XX displays "input 48k, output 192k" and my DAC displays 176k ; the music is 10% slower with a tone shift.
I use a M2TECH Hiface.

Hi Peter

When reading a 88,2 file with antiimage and "96 or 192 k only" checked, will it be possible in a near future to get a 96k or at least 192k output ?
Today the output rate is forced to 88,2 or 176,4 (96k only is ignored).
Other point : it is not possible to play a 48k file with arc prediction when "96k only" is checked. Or here, arc prediction should be able to output 96k.

Best regards

Having strongly increased the size of memory allocated to Ram Disc I can now play XX on RamDisc. As you told it, Peter, it is not easy to share the limited RAM memory between windows (and XX through windows) and the RamDisc.  But I really prefer the sound of XX on RamDisc, even if it is difficult to find a rational explanation.

An other problem (also with XX on HDD) :
Especially when I use Anti Image sample rate conversion from 44,1 to 96 kHz.   When going from one track to the next one XX creates a UnicodeTrack0002a.wav file, begins to read it and creates at the same time a UnicodeTrack0002.wav file.   But the cursor begins only to move when UnicodeTrack0002.wav is finished. It causes a gap at the end of the track, can lead to a crash of engine #4, and sometimes to a crash of Hiface's driver.

A very positive point to finish : I measured the file resulting from sample rate conversion with XX and compared it with a file resulting from a conversion with foobar and SRC. The residual components above 21 kHz are lower with XX, and it uses less computing power.   
(as I tried several sample rate converters, there seems to be a correlation between high frequency components and sound quality)

It seems to be much better now after setting thread priority as RealTime.

Yes, the original problem is linked to RamDisc.
Now, evething is nice when XX runs alone from HDD. I have more problems when Firefox is running at the same time. I will explain it later.

Thanks Boleary.

I found some thing else on my one core computer.
I put usualy XX 09-y4 on a RamDisc drive. Do I have a problem of memory space with 09-y8?  Only 50 MB are free.
When I put the XX 09-y8 folder on my HDD it is OK.  I tried XX 09-y8 on RamDisc with "Data Folder" on HDD. It is not better.

The next question is ...  What can I do if I like to use XX 09-8 on RamDisc ?

Regards

Peter,

It was a .wav file.
I tried later a 44 kHz 16 bit .wav file.    The first time I had a few seconds of sound, and then the message "Too many buffer errors".
I tried then to play it again. This time I had the message in picture 1.  Since that, it doesn't work any more with foobar (picture 2). OK I think if I restart my computer.

Thanks

I am trying to use a newly arrived M2Tech hiFace on my XP desktop.
Sadly, I have the following messages (see pictures)
I have no problem to play this 96 kHz 24 bit file with 09y-4 and engine #2.

Best regards.

Hi,

Yes, 0.9y-7 works much better than 0.9y-6, no more memory overload.
I have netherveless some remaining problems.
The transition from one track to the next one dosn't work when the next track lasts longer than 6 minutes. There is a 100% CPU load lasting 25 seconds, and after that there is the message "Engine 3 stopped"
I can also have a sound loop (as before) when I press "Pause". And it takes a lot of time to start a long track.

Greetings

Hi,

You can find here some pictures.
You can notice the high memory load, much higher than without resampling. The problem occurs mainly at the end, or near the end of a track. It can occur sometimes in the middle of a track, when there is a peak of CPU load.
About my computer : it is my second computer, the main computer is working with XP - another story.
It is a 2 to 3 years old laptop with Vista, one core. I use here the SPDIF output of the mother board's sound card, feeding a TACT amplifier with digital input (and only digital inputs).

Regards

Thanks for your answer, Peter.
I have the small text "Undemo".  So, what can I do ?
More precision about my crashes : there is no message, but I have noise instead of music, and there is sometimes a high processor load.
More precision about this noise : it is a sound loop, it repeats unendly a very small music sequence .

My problems ... part 1
An important concern is perhaps that I don't know if I fall back into demo mode or not (I have also this concern with y-5.6). It is not possible to set core appointment.
When using Anti image double rate, the memory and processor allocation seems to be much less smooth with y-6 than with y-5.1. And using 96 k only setting and 44.1 k tracks causes many crashes. Using y-6 with arc prediction double rate and 48 k tracks is allmost OK. But there is nothing new...

Good news !

Hello
Since the prefered sampling rate of my DAC is 96kHz I do often an "offline" conversion (saving the output file on flash memory) with foobar and the "Secret Rabit Code" sample rate converter. So, there is some preparation before a listening session...