Personally I can't deal with Accuraterip. Half of the time all checksums are different, with my "easy" conclusion : the CD is different.
I just don't know how to judge the results.

Hi Klaus, All,

What I intend with this board, is pointing out absolute references which everybody can check with him/herself. Altough currently unprepared, I'll try to give an example (Bert, don't laugh) :

There's a CD "Lise & Gertrud - Live På Nalen", Track #2, "Life on Mars";

There are two major parts within this track; the first part the one woman is singing, and the second part the other.
Now, the first woman spits all over the place, say, right into your face.

When you have things kind of wrong, you will not hear the spitting at all, even if I tell you it's there.

This gives me a kind of opportunity to tell how XXHighEnd got to its current stage, but *also* how the Orphean/BD15 got improved (like I tell in general here);

This is one of the tracks Bert and me ran a zillion more times than I liked, just because there's a contra bass (or what it is) which can go wrong and can go right during playback, and it was an important "measuring device" mainly for Bert.
Then I came up with the native Vista Engine (#3), and the woman suddenly started spitting, something we didn't notice a zillion++ times. But, this spitting was so loud, it was disgusting. Really. So from that time on, I really couldn't listen to that track anymore.

In the end this brought the rejection of Engine#3, because it was overdoing things. Well, in that consistent situation back then.

At one day, I sat sown unprepaired at Bert's place, and he ran the track once again. He did not have Engine#3 (never had), and within 0.3 secs I heard the spitting; Bert drove himself to squeeze out the spitting without the Vista Engine ... (and in the end created the MKII Orphean (/BD15) of it).

The big fun is, that now the #3 Engine isn't overdoing things that much anymore, just because the Orphean got better.

So this is how we did it and still do it, and that is what this board is for : Pointing out this spitting, is a very easy thing, and ready for absolute measurement at the same time. Don't you have the spitting ? then you are in for improvement somewhere. XX can do it (today with #1 and #2 just the same). If you have it ? compare it with the player you're used to. Is it not there ? then it's less.

So note that "spitting" is far from the only thing to measure, hence it can never be a single "thing"; all must come together. Example : the spitting will reveil when the highest frequencies are uplevelled (think in xover terms). But if the result is hissing cymbals ... then it's wrong all together.
#3 could do it on its own (and too much of it), but at the same time it created the crazy dynamics as known from Bert's forum. Each smash on a drum would make you scared. It is a nice feature, but a wrong one. It unveils detail you never heard before in your life, but it's wrong.
At that time, we couldn't think of what was wrong, except for that it was. Today we know it was the Orphean which was ready for improvement, and in the very end currently I don't know the status of #3 for that matter, because I had to give up temporarily on the complex matter of integrating the engine with the functionality of the player. It took me 4 months, and XX had to be launched ...

So again, this board is for pointing out mainly the anomalies. One could say something like : I know this woman, and she has a crackle in her voice, and I don't hear it. Can you hear it ? ... and then work it out.

The other way around can happen just the same : after an upgrade of XX, someone says : I now hear bells which I never heard before in this track, do you hear it too ?

Or I could say : Please listen to track x, you now hear a brush there which in the old version was inaudible. However, I think the bass is kind of booming, listen to track y please.

All 'n all it is about improvement, which is my personal objective.
And yours, I'm sure.

Peter


PS: I imagine to post pieces of tracks to share. Whether it's allowed or not, I don't care. I'll be responsible.
No complete tracks, and no pieces which can be glued together to reform the original track.

I talk about re-ripping with EAC again, and then they are gone. So in the end everything is OK on the CD, but EAC doesn't read it properly.
I have the example of tracks being "in the middle" of a CD not being ripped properlt (and EAC reports all is okay), but in the mean time it's quite a mess. Never mind it's because of something else wrong in my system;
Rip the track on its own, and then it's okay. Sometimes it needs more attempts.

Oh, Cache is off.

Yes Marco, this is related to this :


... which you apparently already have arranged for.

Please be careful here;
In the past you may have put a lot of effort to get it that far (implying KMixer to get out of the way), and if you don't like XXHighEnd you might want to do it again.

Since I hardly care about this (I don't need it because of XP bitperfect RME (Fireface) drivers or Vista where all just doesn't apply), I am a bad advisor here.
You might want to go to Bert's site to re-find what you did before (and undo it by that means), or otherwise I sure hope others can help you out.
Whatever you do, try to write it down, so you can reverse it when you think it is needed.

Btw, of course in the end you would just want to have it like you have it now (see my quote), but then including the device being the primary device.
Also note that the fact that it in the end is greyed out is not a problem, as long as you get it there (at first place hence Primary Device).

As soon as I see something to help out a bit, I'll jump in !

Peter

As it now appears, with Engine#2 the loading speed of a track (SATA/IDE/USB Network) connection speed combined with its length) may cause the track not producing sound.
So this is what happens when the player stays on the screen, but the sound stops.

Note that the loading time is *also* related to the memory being at its limit, therewith causing -in a certain stage- swapping (virtual memory) getting active, implying a much longer load time (see also the subject Memory needed).

In a next release this will be solved (hence ASAP, although it is rather complicated).

(continued from here : http://www.phasure.com/index.php?topic=24.msg105#msg105)

Haha, thank you Klaus !

But I am interested in that just the same. So I tried to say with care that this should just be allowed.
For that matter it is a general subject, so please continue it.

What I can add to it :

I have created a "Glitch" checker. Something similar as is contained in Wavelab (5.1 anyway), but a bit more "intelligent" and dedicated to what we do with audio here. Well, I detect many in many CDs (many means : hundreds of pieces of glitches of, say, 1000 samples per subsequent piece).

Rip such a track again until the glitches have gone, and you're done. So much for EAC ...

It will be part of the player, and when time comes I will create a separate topic on this.

Peter

Thank you for sharing Jack. Happy playtimes !

Look for the Speaker icon in (Configuration) Settings (Sounds and Audio Devices). Start it.

Go to the Audio tab and click the top combobox in there. From there select your USB device.

Note though, that that will select your DAC for general computer sounds as well. Never mind those for now.

Peter

Leo, and the very first in the list is not "Primary Sounddevice" (or something like that, but the "Primary" is literal).

So ... that one is always the first, and the second one is always the same;
Since the first is dummy, I call the second one the first.

How about you ? 

Note that XXHighEnd does not make use of ASIO drivers.

For those currently using the USB.DE (USB.COM) USB ASIO driver, in order to let XXHighEnd work over USB, that driver must be uninstalled;
When the DAC stays connected, reboot the PC, and then the MS USB Audio (legacy) Driver will self-install.

As far as I know there is no way of keeping the USB ASIO driver installed (e.g. on another USB port), and making use of the USB Audio Driver at the same time.
It is very easy to reinstall the USB ASIO driver though.

Please keep in mind that Engine#2 kan operate the Primary Device only (as set in Windows Sound Properties).
If another device is selected, there will be no sound.

Note that XX implies that you can select another device for Engine#2, which is wrong and will be removed in a next version.

If you are not sure which device Engine#2 will be using : click the combobox at the top, and look for the first device listed.

No Steve, it's my own fault. Although it's in the Help.htm, it's there as a kind of sidenote. I must make this more explicit, which I will do right now.

Hi both of you,

Would you please respect the fact that all this in here is about XXHighEnd, and that it is not much useful to that respect if we are going to outlay very unrelated setups.

I know, it was me who is interested in other findings, which btw is perfectly allright. I mean, if I challenge JRiver, XMPlay, etc. by means of XX, there's no reason why a Linux based setup isn't challenged just the same. If someone would say "XX is serious BS", I wouldn't remove the post, but I would be interested in why instead. That is, say, the competition.

But please hold back a bit on getting very much offtopic.

If we from now on must start ripping our CDs on a Linux machine, this of course *is* very much related. So happily continue that in its own thread.

Please look at the topic title (and what is coming from it )

Marco, did you select your USB device as the Primary Device in Windows ?
Note that it should be at the top when you click the top combobox in XX. If it's not at the top, it's not the Primary Device, and Engine#2 requires that ...

Steve,

For Engine#2 it will be the Primary Device (which always is the first one in the list if you click on the top combobox in XX.
So it is a matter of choosing "a" device of which you know it gives sound. It is up to you whether the one sounds better than the other (which for sure is important if you have two soundcards, which btw would be the same as the difference between the RME-MME drivers and the RME-non-MME drivers.

I hope you get it to work ...