XXHighEnd

Hi Peter,

Thanks for getting 0.9u-7 out - I suspect the pre-processing code must have been a bit of a nightmare.

I'd rather not comment on the SQ just yet - need more quality listening time.

But I have a quick question: why does the Mem box not change the RAM used for 24/96 FLAC files? 0.9u-6 used less RAM for these files and I expected checking the Mem box to revert to this.

Is this what you would expect?

Mani.

PS. FWIW, with quad upsampling of 16/44.1 wav files (Mem unckecked), I can only play tracks of max length 15 mins or so. These take my RAM usage up to 2.5 GB. Playing larger files gives me the 'XXEngine3.exe has stopped working' error message.

Hi Mani,

If all is right, this is related to your own remarks about 96/24 being preprocessed (IIRC it was about just this), which never has been different. So, no "old code" exists for this ... (hence the Mem box can't change anything to that).

Of course this is inconsistent with my own remarks about it in the Release Notes ...
Peter

Yes, that was my understanding.

But I don't understand why more RAM is being taken up now... if the code remains the same.

Mani.

Oops. Missed that phrase.

Ok, I just looked, and things appear to be a little different ...

a.
There *is* old (and new) code for 24 bit files. Indeed the old code pre-processed already, but very minor stuff still had to be done in real time (coming down to expanding the bits). This has been changed into "all pre-processed" with the penalty of additional memory useage. Can this be worth it ? probably not.

b.
Since I apparently forgot about this myself (see previous post :() I *also* forget to let this be subjective to the Mem checkbox.
So you are just 100% correct. Again ... :good:

:whistle:



PS: I only now understand that the dedicated topic as originally created by you was just justified. So I put it back in its own topic.

If it not already was, then it will be ... :)

I just found the comment as shown below, which makes my last post not being the truth either. :no:

What it now comes down to is that this part of the pre-processing code has to be split into half-pre-processing (as how it was before) and full pre-processing (as how it currently unconditionally is).

Oh well ... :swoon:

Soo
now that we have Solid State Drives, take a 32 Gig SSD and use it as ram?  I'm just saying, shoot for what's best for the wav files.  If that takes lots of mem to achieve then tech will catch up (with our wallets) soon enough.  I know I'm waiting.

IMHHHO useless.
Ok, for installing the OS (and swap file) on it. :grazy:
And *then* it is up to me to shut down the hdd the music came from. :yes:

Well just thinking in terms of new amounts of ram that could be viable in the future.  How much ram would you like to see available to fully do the XXHighEnd thing in the future?...32/384 anyone?... or, (god he's going to bring it up again...) enough to handle a few wav/cue albumS for changing the rate any way you feel fit in XXHE? (although I wonder if I would just end up NOS in the end any way?)

There is a limit in Vista of 3GB RAM.... or are there possibilities to increase this?

Well, I guess I'm learning something new everyday... I had no idea it was limited to 3??? That seems low, I thought people were buying systems now aday with 4 gigs in em? and thought surely windows would handle more.

hmm sucks for me and my huge single album files... back to thinking about splitting them into single wav files again? bleh....


HEY PETER!!!! how about adding something into XXHE that splits my album wav/cue file into single songs with info taken from the cue and displayed in XXHE?  then they can be preprocessed... (or how about i just give up and start ripping my cds into song files...what do you think).

No, of course not Dave. That would be stupid. It all can be solved and it's just a matter of time, priority and some air. :)
And it is not so easy. That's all.

Hi Dave,

Edit: in case you decide to try multiple files instead of single.

there's this freeware tool
http://www.medieval.it/content/view/28/70/

It has batch processing too. I use it time after time. With 2 or 3 hiccups on couple of files out of 200.

Andrey

Stupid is as stupid does... andz i's done a lot of stupid...

hehe
carry on

Hey Andy!
Thanks, I've known about medival for awhile now and started using it... then stopped once Peter supported cue files.  It seemed to work well... but I wasn't confident in it enough to drop my whole wav/cue files, and I didn't want to double my inventory of music.... but I have medival Cue Splitter at the ready in case that's the way to go.  Have you ever done an abx of it?

The only test I did was I joined the files back in again by some freeware joiner and the size of the joined file was the same as the original wav.
I didn't care to compare its contents though. I believe the cue splitter does not mess with the data it just splits them.

Sorry for hijacking and offtopic.