XXHighEnd - The Ultra HighEnd Audio Player
July 30, 2015, 06:10:48 pm *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Dec. 31, 2012 : XXHighEnd + Phasure NOS1 DAC receive 6moons Blue Moon Award !
** "Lonely at the very top" **
Search current board structure only !!  
   Home   Help Search Login Register  
Pages: 1 2 3 4 5 6 7 [8] 9 10
 on: July 25, 2015, 03:28:33 pm 
Started by AlainGr - Last post by AlainGr
Hi Peter,

I just read your new topic "XXHighEnd PC with Windows 10 from RAM" here: http://www.phasure.com/index.php?topic=3295.0

Will you eventually make something available for those who do not have a XXHighEnd PC also or is it too complicated because of the different architectures ?



 on: July 25, 2015, 01:09:41 pm 
Started by PeterSt - Last post by PeterSt
Hi All,

Following up on this :
And now my sound is SCARY
I'd like to apply some changes to the XXHighEnd PC :

At this moment, and for the time being, the XXHighEnd PC will be shipped with :

- a 2.5" hdd with Windows 8 Pro + license;
- a 2.5" hdd with Windows 10 Pro Preview, build 10074, meant to fully operate from RAM.

The 500GB hdd as well as the 2.5" SSD will not be part of the shipment any more.

The (still silent) dedicated (and analog rev-controlled) chassis fans will not be electrically connected (hence won't be operative by default, but they can be connected when wanted).

Reason for this strategy change :

At first the XXHighEnd PC was meant to cover for all the needs for Audio Playback, including the housing of the music itself, by means of hdd or by means of USB connections. This strategy has changed (for the better SQ of course) into :

a. Connect as few as possible to the Audio PC (which means totally nothing);
b. Have the music somewhere behind the LAN (another PC or a NAS etc.).

Ad a.
The provided hdd with Windows, by default boots the Operating System into RAM. After that, the hdd can be removed from its removable (and hot-pluggable) bay.
Do notice that all the provisions are there to apply changes - now performed in RAM - to permanent storage (re-mount the W10 hdd and let XXHighEnd apply the changes).

The provided W8 hdd implies the more normal situation, but with still the strategy that as few as possible is to be connected to the PC. Thus, the only difference with the W10 hdd is that W10 is meant to run from RAM (but can also be used in normal fashion) while W8 is meant to run normally from the HDD.

The XXHighEnd PC will be shipped with XXHighEnd 2.03 (or higher) - needed to support the "Windows 10 from RAM";
You don't need to do anything to let this all work and booting will automatically be to/from RAM. Tutorials to let all work seamlessly with the music behind the LAN somewhere, are available.


 on: July 24, 2015, 09:05:13 am 
Started by jhmvl - Last post by jhmvl
Hi Peter,

I can tell what is was set to. It was set to: No Appoint.

I have to assume that it was set to that value by default because I did not touch any of that earlier   innocent.


 on: July 23, 2015, 07:30:47 pm 
Started by jhmvl - Last post by PeterSt
Hey, great !

Can you tell me - what was it set to ?
and did you do that (which XXHighEnd abusivley allows for) or was the default wrong ?

An answer "I don't know" also suffices. It's good enough that the problem was solved. yes


 on: July 23, 2015, 05:23:39 pm 
Started by jhmvl - Last post by jhmvl
Hi Peter,

I tested your options and selecting core 1-2 solves the problem. It now starts very quick (within 2 seconds even for tracks with diacritical symbols).

I close that closes this problem. I will open a separate thread for the cover art.


 on: July 23, 2015, 01:55:11 pm 
Started by jhmvl - Last post by PeterSt
Thank you for now, Hans.

No Coverart should deteriorate, nor should it show smaller than reality. However, Coverart has to fit "somewhere" always, so it is easy to run into something which was made smaller.
Notice that I do not recognize any issue with this at any time (forum).
One thing : If the coverart shows in the left pane and you then resize the size (like height) of the XXHighEnd screen, it deteriorates for that moment. But I'm confident you don't mean that.

Do not hesitate to open a new topic for this and post (attach) a picture which such an issue with it. So if this is so (deteriorates) then I explicitly want to solve this; I am too keen on good pics ...


 on: July 23, 2015, 11:07:28 am 
Started by jhmvl - Last post by jhmvl
Hi Peter,

What I mean with the example directory for ZZ Top is that there is a space in the name of the directory between ZZ and Top. But as far as I understood descriptions on the forum that should not be an issue but I mention it to be complete.

Coverart: I have coverart as a seperate file in the album directory and it is always called cover.jpg. I try to avoid having them as tags in the music file. My ideal set-up would be to work with a cue sheet and clean wav files but that is a separate project for a later time (any tips how to do that efficiently given that I have a very large collection of flac files now are appreciated but at a very low priority now).

Filesizes that I have tested so far vary between 33.6Mb (16bit 44.1kHz) up to around 190Mb (24bit, 192kHz). The issue is the same for all of them. Funnily enough the loading time is approximately the same for the 33.6Mb file as it is for the 190Mb file scratching

The coverart does come up ok in xxHighEnd but I will say that xxHighEnd does something to it, i.e. tries to make it smaller or less resolution or whatever. In one of the cases, a picture that when viewed in a seperate viewer has the size of a normal CD is shown in xxHE as a very small picture. It does that to only that album, in other cases it just deteriorates the quality of the picture for some reason (read something about that on the forum but didn't feel that that would apply here) but not the size. As a note: I do take care to not use huge files coverart. All files are smaller than 100Kb.

What do you see in the right most (3rd) pane when near the bottom - right hand side -"Show Coverart" is activated (Red) ? If that's "one million covers" then that is the problem ...

I will check this when I get home tonight. I would say though that it might say one million covers, but in actual fact there are no more than 20 covers in the test library that I use now.


 on: July 23, 2015, 10:08:39 am 
Started by jhmvl - Last post by PeterSt

There are however spaces used in pathnames, so an artist name like for example ZZ top means that all albums from these guys will be in that dierectory as new directories (one for each album).

I am sorry, but I don't understand what you're saying here. I mean, all fine with that, but how are the (btw allowed) spaces related ?

And :

I can wonder how your coverart is organized. Depending on your answer I may have more questions about it. Anyway :
As JPEG's etc. in the album folder ?
In a separate sub folder ?
As tags inside the music file ? if not, what's the size (just one example suffices, as long as it's an album with this issue).

Do you see anything of the Coverart in XXHighEnd ?
What do you see in the right most (3rd) pane when near the bottom - right hand side -"Show Coverart" is activated (Red) ? If that's "one million covers" then that is the problem ...


 on: July 23, 2015, 09:58:52 am 
Started by boleary - Last post by PeterSt
Maybe. But since Robert Harley only talks about the ringing aspect, "we" (and you too, Brian) better think about our NOS1(a)'s not ringing at all. Must be better to begin with.

But as usual (in my view) TAS doesn't know much about anything, so any real merits was not dealt with (which in between the lines was even announced).


 on: July 23, 2015, 09:42:59 am 
Started by jhmvl - Last post by jhmvl
Hi Peter,

Yes it is a Mac running win7 now.

I will do the tests you suggest when I get home from work tonight.


Pages: 1 2 3 4 5 6 7 [8] 9 10
Powered by MySQL Powered by PHP Powered by SMF 1.1 RC2 | SMF © 2001-2005, Lewis Media Valid XHTML 1.0! Valid CSS!
Page created in 0.261 seconds with 15 queries.