XXHighEnd - The Ultra HighEnd Audio Player
April 30, 2024, 09:01:07 pm *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: August 6, 2017 : Phasure Webshop open ! Go to the Shop
Search current board structure only !!  
  Home Help Search Login Register  
  Show Posts
Pages: 1 ... 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 [916] 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 ... 1047
13726  Ultimate Audio Playback / XXHighEnd Support / Re: Problem on 09-w6 on: January 07, 2009, 02:05:51 am
I heard of it before Glynn, and provisions are ... uhmm ... were in there for it. I guess I have overruled those provisions by the new setup somehow.

Please look for a very small track (like 30 seconds or so) where this happens, and email it to me or otherwise make it available for download (don't put a link in this topic to avoid "governmental" prolems).
Can you do that ?

Peter
13727  Ultimate Audio Playback / XXHighEnd Support / Re: Volume control w6 on: January 06, 2009, 12:38:51 pm
Yes it could. But since it is not available throughout it can't really ...
13728  Ultimate Audio Playback / XXHighEnd Support / Re: Volume control w6 on: January 06, 2009, 10:56:46 am
may I suggest an addition to the onboard volume control which may prevent shattered windows and bleeding ears. Within the settings area, would it be possible to set an explicit, user defined, upperlimit that the volume control cannot exceed, eg. -30dB. What this should then do is prevent the volume slider control from physically rising any further than that value.

Yes, this is a good idea. And just because it is a good idea I thought maybe I could have a better idea myself. swoon ...
And I just had ... (coming from outside at -12C hehe)

Somehow Russ's idea brought me the solution to a problem I have been seeking since the volume control is there ... how to prevent the huge blast which really really isn't something you ever want to meet again, once you had it unexpectedly. And it is so simple ...

When we set the digital volume to a certain level, this actually means that the output voltage is limited to "a" level. This has a 1:1 relation with the digital data. Thus, suppose we want to set the volume to a certain level, we actually decrease the numbers of the digital data which causes the output voltage to drop. Yeah yeah yeah, we all knew that. Happy sort of.
When we want to protect ourselves from accidentally setting the volume too high, indeed we could have a Settings Parameter, where we tell the system to not allow the Volume Slider to go above e.g. -24dB. Nice feature to jump to the maximum in one go too (just slide the Volume all the way up, where it will stop at the maximum set setting).

Because the whole idea is a kind of stupid (read : overdone) when we're working with the rough steps as we have currently (and because of which I shouldn't have mentioned the mouse wheel at all), I am merely thinking in the domain of the much higher resolution, like the 384 steps I have been testing with. These steps (if achieveable without loss and what I assume so far) imply a level of "detail" which wasn't in my mind before, and which now -in combination of Russ's idea- brought me to this :

When we are setting a maximum level, we should do this in dB. Or better : -dB. Or even better and for some more understandable : in SPL (Sound Pressure Level);
The output voltage is an absolute phenomenon, and e.g. 1.5V output will create an SPL in your room which is always the same, no matter what track you are playing. This is not competely true, or said differently : the SPL cannot be measured in advance because it is a stack of things happening, e.g. bass output creating more SPL than higher frequency output. But it is not about that. It is about setting a maximum voltage output of the DAC, mimicing very much the same as SPL, and probably the closest to that compared to other means.

Still with me ?

Other means ? yes, like the analogue volume knob, or the way the digital volume works now (and everywhere not accounting the losses other software implies). What I actually mean is this :
When you set the analogue volume knob to a so called absolute maximum, this is always relative to the track, and the percentage of the dynamic range it is using. Thus, modern recordings use 100% of the dynamic range (up to -0dB) and older recordings often not more than 60-70% (-30dB). This is why you actually don't have this absolute maximum on your analogue volume knob, and the latter recording requires a higher output volume to reach the "100%".
On a sidenote : this is how/why other software applies "Replay Gain", which actually levels everything (from a playlist to play or album) up to the same level of output.

Well, it took a longish introduction, but what it comes down to is that we should not set the volume slider to a value which is related to the total dynamic range we have (as is happening currently and everwhere, also the analogue volume) but it should be set related to the dynamic range used in the music data.
This actually must use the Replay Gain phenomenon (see below), but what it is about is that we set the volume according to the maximum level occurring in the Playlist, and not according to our perception of what our DAC->Preamp->Mainamp will output, without knowing the level of input (which varies).


Ok, before everybody thinks I am way off topic ... I am not. I am not because the single thing *I* thought about with the idea of Russ in my mind, is that we shouldn't set the maximum volume to a volume slider setting, but to a DAC voltage setting. Why ?
Because it will for once and for all prevent the shattered windows and blown tweeters. IOW, if we tell the DAC not to output more than 1.2V (it being capable of 2V), each single sample exceeding the 1.2V will incur for an "Out of Range Detect" situation and music will just stop.
This is completely justified, because of the digital data having a 1:1 relation to the voltage output. And I never thought of tackling the shattered windows problem this super simple way ...


Replay Gain ?

This never has been my objection because it molests the data. However, and obviously, if the Replay Gain could work in the (stepped) range of the volume steps we are using right now, it would just be justified. As obviously however, these steps are far too rough to let this be workable.
But not if I can create the steps much smaller ...

Please note this part is not related to the Digital Volume only, and it applies just the same when you are using analogue volume only.

Replay Gain normally is used to level out the maximum output of a selected bunch of tracks. Say, those in the Playlist Area to play;
To me this would be the most wrong, because if you level out all the tracks from one album, the intended differences in output per track will be vanished. Thus, if one track uses the full 100% and all the others 70% only, this is intended, and the others should not play at 100%.

The above is different over different albums. One is receorded using (at least one track) 100%, and the other using 70%, and it is most probable that we want to perceive those two albums as loud. Normally this is the time when we start running to our volume knob, and with the current most rough digital volume this is the time when we get unsatisfied when a next album is way louder than a previous one, but notching down the volume one step makes it too soft related to what we were just used to from the other album.
Note that this implies that any album reaching e.g. 80% only (observing all the tracks) the volume of that album will be uplevelled to 100% (otherwise the whole Replay Gain thing can't work), and that this 100% will be related to the set Digital Volume again.

Concluded : If you have followed the above, and assuming I can get the detailed volume steps in without losses (a 100% prerequisite) XXHighEnd will be setting the maximum required output voltage of the DAC. No, we will not be told "what is the voltage" because it will just be a slider with relative positions, with two known things only : minimum has an output of 0 voltage, and maximum has an output of the maximum output voltage of your DAC, whatever that is.
So this is Russ's parameter.
Besides that the Digital Volume will work in the range as implied by the parameter. This will not imply that it's physical maximum will be at the top always, but it will just not slider up any further than the parameter told (otherwise granularity must change). Thus, the number of steps are limited at the upper boundary.
Completely separated to this, we will be able to say "replay gain please", which will output the different albums at the same level, as described.

Lastly for newcommers here :
The digital volume in XXHighEnd does not operate in any 48 or 64 bit float whatever domain requiering dithering and all. Instead it operates in the domain of the output bitdepth itself, which is the one and only way not creating roundings and losses knowing that in the end this output bit depth *will* be used by the DAC. It intelligently uses digital volume steps of which is known in advance that no roundings etc. will occur, and while the steps used so far are very rough, I thought of another method allowing for much finer steps. This method works in a simulation model (program), but I couldn't get it to work in practice so far;
If my theories are right this is just a matter of the complexity and the dozens of thinking errors one can make in a real life program, and if my theories are wrong all of the above is never going to work.
In the latter case the Settings Parameter of the Maximum Volume seems overdone to me BUT will come off handy once remote control is in action.
Happy
Peter
13729  Ultimate Audio Playback / XXHighEnd Support / Re: Problem on 09-w6 on: January 06, 2009, 03:58:26 am
A first question :

Crack detect switched Off ? why ?
And what happens if it is switched On ?

An answer "otherwise playback stops in between tracks because of a message 'Crack Detect'" is not allowed, hahaha
13730  Ultimate Audio Playback / XXHighEnd Support / Re: Volume control w6 on: January 05, 2009, 10:32:22 pm
Oh yes (and many more steps). But on a half a day of working on it, it failed so far. But theoretically it must be possible.
Btw, only for native 16/44.1 files and with a 24 bits DAC !! oops

Peter
13731  Ultimate Audio Playback / XXHighEnd Support / Re: Problem on 09-w6 on: January 05, 2009, 10:05:15 pm
What ?!? hmm ...
Now I'm in trouble, because I don't have that at all ...

Can you please eleborate on what exactly do you play (bitdepth and samplerate), and (I hope you don't mind) *all* of your settings with this ?

Besides that, please mention your playback means in your signature (take mine as a rough example). This is as important.

Thanks !
Peter


PS: When you're at it anyway, please tick "Log Activities" in the Settings Area, make it happen once more, and send me both the XX and X3 files from the TemporaryData subfolder to your XX folder. Please watch the modified times of those files, and more than one X3 file could apply to that one session. Better send too many files than too few.
scratching
13732  Ultimate Audio Playback / XXHighEnd Support / Re: Volume control w6 on: January 05, 2009, 10:04:10 pm
Ah, that's true. I forgot. Better shouldn't have mentioned it at all. Happy
This is a setting for your Mouse in the Configuration settings. Same as the number of lines which will browse in Explorer etc.

Edit : The scroll wheel comes handy when the resolution of the volume is much finer than now ... which I have been working on, but failed so far (without losses that is yes).
13733  Ultimate Audio Playback / Download Area and Release Notes / XXHighEnd Model 09w-6 (solves repeated etc. tracks) on: January 05, 2009, 07:55:51 pm

This should about complete (but see at the bottom) the new memory management as was introduced per the 0.9w version.

  • If all is right the repeating of a track -after which playback stopped- has been eliminated.

  • At the end of a track a piece of it's beginning could be heared sometimes. Solved.

  • The "Split file at size" settings parameter now has a default of 100MB. This should cover for all means of (also hires) playback, and doesn't harm the "memory player" features at the same time.

  • Per this version now officially two subsequent DXD (24/352800) will play.
    Important : This only works at Unattended Playback !

  • Since a few versions back MP3 files would show "UnicodeTrack0001" at the Wallpaper Coverart followed by a ChangeWP error. Solved.

  • Cue Files with a track name of one position (e.g. : I) would error out on loading into the Playlist Area. Solved.

  • Albums without track numbers in their first positions which also couldn't get track numbers applied by XXHighEnd would error and not load into the Playlist Area. Solved.

  • With a click on the "V" label above the Digital Volume slider now the volume will go up with one notch.
    Note that the mousewheel can also be used to change the volume (after the slider has been clicked to make it the "active control").

  • The DAC Test (last option of the "DAC Is" combobox in the Settings Area) did not work anymore. Solved.

  • When XXEngine3 runs out of memory now in most of the cases a normal message about that is provided. In more rare cases still an "XXEngine3 stopped working" can appear.


Issue left : Upsampled tracks from Cue File albums may end with an "XXEngine3 stopped working".
Similar might happen in general with Upsampling (hence something is not right in this area).

Edit : Rips with DBPowerAmp cause Crack Detect messages in between tracks. See Problem on 09-w6
13734  Ultimate Audio Playback / XXHighEnd Support / Re: XXHighEnd wont work on: January 05, 2009, 01:25:48 pm
Hi Paul,

Quote
If in Foobar I turned SRC off then 16/44.1 native files are passed on to Vista which then upsample to 24/96 - that is my understanding.

That is correct.

The "Speakers Properties" screen you showed is the one I referred to. The selection you can make (like for 24/96 as the screen shows) does nothing for Exclusive Mode (watch the remark at the top -> "... in shared mode"). It will say though what the native possibilities of the sound device are (with still no guarantee that they will work. But those not listed 100% sure won;t work hehe). So, does that combobox show 16/44.1 as well ?

For your testing, indeed think carefully about the resampling facility from Vista, which makes it very hard to determine what the software actually outputs. For example, try Engine#1 and that will work. But Vista will have resampled to *anything* that works. This is not what Engine#3 will do, because it won't allow "not bit perfect".


I looked at the Empirical website, and *everything* is directing you to 24/96 under the cover of that sounding best (which is non-sense to me, or at least generally that is). Furthermore there is this quote from in there :

For Best PC Audio Quality:
We recommend using Foobar2000 0.8.3 to upsample the data to 24/96 on a PC. You will need a
DAC that will operate in 24/96 mode, such as the P-3A, The Benchmark DAC-1, the
Northstar 192 or the dAck!. If you do not upsample, then set the player to 24/44.1 with the new
firmware version of Off-Ramp. If you have the older m-audio firmware version, then you can set
16/44.1.

Mind the last two sentences ...

Lastly there's this post : Re: 09.U-0a setup with external USB DAC and in there a quote from Steve N : "All of my USB converters do only 24-bit".
I tend to believe that ...  Happy

This doesn't mean that you can't play, but together with the other issues (like the driver) it all becomes a kind of difficult for you.
Anyway I hope you can make something of it !

Best,
Peter

13735  Ultimate Audio Playback / XXHighEnd Support / Re: XXHighEnd wont work on: January 05, 2009, 09:14:59 am
Yep, that's better. Uhhmm scratching
This is what I have too, and this must be since one of the later versions.
Will try to solve that today.

Quote
Definitely the OffRamp accepts 16/44.1

Do you have any information on this ?
What I would do (just because my info says it accepts 24 bits only ... ignorant me) is :

1. Set "Dac Is" to 24/96 (with "needs 32 bits").
2. Run a native 24/96 or check "Double" an run a 16/44.1

In this case you will be outputting something the DAC sure is able to understand in theory.

But :

I am near to wanting to bet that this is about the laptop, and it outputting 48K only. You can check this with the device properties (starting at the loudspeaker icon in the taskbar tray), and finding that combobox that shows all the supported formats (note that selecting in there won't change anything).
If so, an 24/48KHz file should work.


By now there are many resons for things not to work, and the first theoretical reason is a wrong driver;
Please note that "Speakers" which pass through SPDIF under Vista are actually XP drivers. You should find an "SPDIF" device in there. As long as that is not there, all is bound to fail. On that matter, keep in mind that Engine3 uses Vista-specific means (WASAPI) *and* in a special way (Exclusive Use only).

Peter
13736  Ultimate Audio Playback / XXHighEnd Support / Re: OutOfMemoryException error in 09w-5 on: January 04, 2009, 11:54:05 pm
No Johan, I am sorry ...
It must be related to how you use the Favorites. Something like clicking when things are being worked out from the previous click or something.

Can't you find out just when it happens ? IOW, how I can repeat your behaviour ?
Peter
13737  Ultimate Audio Playback / XXHighEnd Support / Re: Error on 09-w5 on: January 04, 2009, 11:48:58 pm
Pwew, solved ... (in 0.9w-6, most probably up tomorrow).

It appeared to be a stack of problems. But generally it is kind of strange or inconvenient to have the track number right in the middle.

Thanks for your patience.
Peter



13738  Ultimate Audio Playback / XXHighEnd Support / Re: XXHighEnd wont work on: January 04, 2009, 09:01:20 pm
No ... you should load a 16/44.1 file in the playlist area, select that for playback, and then run the Dac test ...

But I just found that here it doesn't work either anymore. So never mind. Happy

Furthermore, you should set "At > 16 bits" to 32 bits, not 24. Maybe that helps you for normal playback ?

Peter
13739  Ultimate Audio Playback / XXHighEnd Support / Re: XXHighEnd wont work on: January 04, 2009, 05:24:09 pm
Hmm, I heard it before about the DAC Test not working anymore. Thought it was an accident with "someone", since here it still works.
Must look into that ...

Wait a minute ... Paul, I see that you are (DAC) testing with a 24 bit file. This should always be done with a normal 16/44.1 file.

And Paul, are you saying that it all works now ?
13740  Ultimate Audio Playback / XXHighEnd Support / Re: XXHighEnd wont work on: January 04, 2009, 03:01:56 pm
Hi Paul,

Sorry you are having problems.
Before we continue, can you please check whether the OffRamp really accepts 16 bits ?
FYI : Re: Engine #3 & Vista: No sound

Note that in the Settings Area the "Dac is" combobox has a "Dac Test" option at the bottom. Please try that and show me the output.

Also, don't forget to put up the Volume Slider (which is unrelated to the error message of course).

About loosing the settings ... there might be a question in the beginning (right after start up). Try to answer it differently than before (yes instead of no etc.).

Edit : I now see that your Sound Device is "Speakers Empirical". This is not right, and you won't be having the drivers installed properly.
OR
Or you didn't make the SPDIF driver the default audio device (which is what Engine3 currently needs -> sorry).

Peter
Pages: 1 ... 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 [916] 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 ... 1047
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.454 seconds with 12 queries.