XXHighEnd - The Ultra HighEnd Audio Player
May 23, 2019, 07:24:52 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] 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
1  Ultimate Audio Playback / XXHighEnd Support / Re: INVALID ARG with 705.6kHz WASAPI on: April 28, 2019, 03:35:45 pm
Additional data:

If I load a 96/24 track first, then 44.1 tracks after that and hit play, then after unattended starts playing if I hit Alt-N, xxEngine3 moves to the 44.1 track and plays it okay at 705K.

If I try the same in attended mode, clicking on Next I get the "INVALIDARG" message and it doesn't play at all.
2  Ultimate Audio Playback / XXHighEnd Support / w/ WASAPI, XXHE plays 705.6 and 768 no problem, unless 44.1 source is first on: April 27, 2019, 05:21:55 pm
Hi Peter

Notice that I changed the subject line to better reflect the problem.

It could have taken years to stumbling into this nugget of gold, but last night I was lucky to open my eyes and read 705K displaying on my DAC.  I had to confirm that in fact I was using XXHE.  I was.  How can this be?

Well it turns out I was playing a Pretenders album.  This album starts with 96/24 material, but at about track 6 and onwards, the tracks become 44.1/16.  Well,  XX happily played the 96/24 of course and when it came to the 44/16 is just kept on playing without problem.   Unattended.  I've not checked attended just yet.

Another way of saying this, it appears, is that XXHighend.exe can't play 705, but XXEngine3.exe can.

As it appears, w/ WASAPI, XXHE plays 705.6 and 768 no problem, unless a 44.1KHz source is first in the list of tracks to be played.

I presume this will work for anyone: 
  • Choose WASAPI as the driver
  • Create a playlist with the first track a 96/24 track
  • Add 44.1/16 tracks after that track
  • Click play in unattended
  • Enjoy 705 material

So clearly this is not about the stream or its compatibility.  Instead, initialization?  handshaking?

I will try a few more iterations today.

Thanks,

Charlie

[Edit]  In case it matters, I was using the 2nd Custom Filter listed under [F], the 705/768 High filter
3  Ultimate Audio Playback / XXHighEnd Support / Re: Alt-D doesn't lower volume on: April 25, 2019, 07:15:39 pm
Thanks Peter.

I need the fast volume change now so maybe I'll stick to attended after I've run unattended once and control volume from attended mode.   That, at least for now until 2.11 comes out.

Off topic: I'm hoping that 2.11 will have a functioning Pause in unattended.  Thank you !

Thanks,
Charlie
4  Ultimate Audio Playback / XXHighEnd Support / Alt-D doesn't lower volume on: April 23, 2019, 03:53:24 pm
XXHE 2.10

If I'm running unattended and playing at 1x (44.1 source material @44.1), Alt-D on the keyboard does not affect the volume.

If I started that session at -15db prior to entering unattended mode, and enter unattended and experience the above, when I hit Alt-X to return to attended mode to use the slider to lower the volume, I see that the slider is set to -18db as I'd expect after hitting Alt-D twice.  However, the volume was never affected.

And by now I can tell this is going to happen in advance by noticing that the time display at the top of the screen in unattended mode stays red and never turns white.  It normally turns white between the time I hit Alt-D and when the volume is affected.

I've also noticed this happening at 2x (88.2), but not always. 
I've not noticed this at 4x or 8x, yet.

I believe that in general Alt-U tends to work, but not 100% at most at 1x.

Other factors:  I have custom filter selected for when I set the rates to higher than 1x, but I don't bother to uncheck it when I set the rate to 1x.

Thanks,
Charlie
5  Ultimate Audio Playback / XXHighEnd Support / Re: INVALID ARG with 705.6kHz WASAPI on: April 20, 2019, 05:11:51 pm
''INVALID ARG device can not play'' error pops up when trying to play any file at 705.6kHz with WASAPI, i though it was WASAPI limited to 352.8kHz but Jriver MC will upsample and play at 705.6 with WASAPI. also 768kHz does work in XXHE and it sounds great.
what could the problem be with 705.6?

I'm having a similar problem with the Holo Spring 2 DAC.  768 (16x) works with 46, 96, etc. source material but 705 does not. 

Has anyone had any luck running XXHighEnd with the Holo at 705K?

Much appreciated. 

Thanks,
Charlie
6  Ultimate Audio Playback / Your thoughts about the Sound Quality / AI = Good on: August 29, 2018, 03:03:56 pm
Hi Peter

From time to time you mention retiring AI upscaling.

I say, please don't get rid of AI.  Apparently, it is the best sounding "standard" algorithm of any I've heard right now. 

HQPlayer had always had a few really good ones, and have usually been better or at least good enough to avoid AI.  But lately your AI appears to be better than even HQPlayer's best.  At least, this appears to be true with the other changes you've made to 2.10.

AI is slow to load tracks but I manage it by using only 2X and I now have an SSD OS disk so it is acceptably fast for loading tracks in unattended mode.

Please consider keeping it and even improving it.

Thanks,

Charlie
7  Ultimate Audio Playback / XXHighEnd Support / Re: File tagging? Or what? on: August 29, 2018, 02:56:12 pm
Hi Peter and Fralippo

I've had all of these problems for a long time.  Sorry I did not report them.

I can make the Windows overlay go away 100% of the time by just going back into the library area and then back to the playlist.  Banner gone.  Hope that helps.

I also get the double tracks selected.   Yes,  I use double click as well. 

8  Ultimate Audio Playback / Music Storage and convenient playback / SSD as OS drive made a big difference in sound on: May 19, 2018, 08:29:59 pm
Hi All

Just here to report an important finding.  After running without a backup of my system for years I decided to back it up.  I bought an SSD drive 500GB to back up my 320GB spinning 2.5" disk.

Well after I cloned the disk with CloneZilla I tried it.  This is easy to do because with the XXHighEnd PC the OS disk is on a removable tray.  I was going to make periodic backups to this drive but instead I found that it sounds much better than the spinning drive.   So now I'm using it as my main and will need to buy another to do rotating backups.

Anyway,  in case it matters,  it is a Crucial, about $114 USD.
     Crucial MX500 500GB 2.5 inch SSD

I thought I had read that the opposite was true.   That's the way it is with audio I guess.
9  Ultimate Audio Playback / XXHighEnd Support / How to Shift-Click in 2.10? on: May 19, 2018, 08:16:48 pm
Hi Peter

2.10 sounds great.  Thanks.

I use a traditional keyboard with a track-pad on it as my method of UI.  So the keyboard has mouse-click buttons and I can Ctrl-click on various tracks or alternatively click first on one track and Shift-click on a later track to get a range.

Prior to v2.10,  clicking on track 1 and then Shift-click on track 7 plays tracks 1-7 in order.
Now with 2.10, clicking on track 1 and then Shift-click on track 7 plays tracks in this odd order: 1,7,2,3,4,5,6.

Congratulations!

How do I get the standard behavior back?

Thanks

P.S.  I wouldn't bother you with this except that Ctrl-clicking each individual track in order is hard with my particular keyboard/pad.
10  Ultimate Audio Playback / XXHighEnd Support / Re: xxHE with xxPC and Wyred 4 Sound DAC2 DSDse on: January 14, 2018, 06:29:48 pm
Thanks Peter.  Thank you !

Also, ASIO appears to work with WASAPI turned off.  That helps me and this info could help others.

Charlie

P.S. Can you believe that I never turned off LAN?  I did that now after creating a new restore point and, wow , there's a big improvement for me.
11  Ultimate Audio Playback / XXHighEnd Support / Re: xxHE with xxPC and Wyred 4 Sound DAC2 DSDse on: December 31, 2017, 11:11:09 pm
Hi Peter

All of the Christmas music was JRiver,  if that matters.   ...And without an xxHE invocation first.

Other updates:
1)  Starting with less than good news, even though Stop WASAPI was checked, I got the dreaded "This should not happen just restart xx" message.  So that negates a previous report that stopping wasapi solves this one.

2). Continuing with good news,  a third night without playback stopping after first track, or other stoppage in odd situations.   This is enough confidence now that I started playing with settings to improve SQ.   Now at 20,1,1,1, 3-5, system max for clock, e.g.

The only down side now besides the "should not happen , restart" message and hassle, is that I can't run WASAPI on my system.  Hopefully I can run it if I reboot.  

I can run like this if you want,  or I can try to continue to help for others.  

Thanks,

Charlie
12  Ultimate Audio Playback / XXHighEnd Support / Re: xxHE with xxPC and Wyred 4 Sound DAC2 DSDse on: December 30, 2017, 12:48:25 am
Another hint:  The last two nights there were no problems.  What do the two night sessions have in common?  Answer: the xxPC was on all day playing Christmas music.
13  Ultimate Audio Playback / XXHighEnd Support / Re: xxHE with xxPC and Wyred 4 Sound DAC2 DSDse on: December 28, 2017, 11:48:08 pm
Hi Peter

Thanks.

And status:  last night's session had zero problems.  No changes whatsoever from the night before, which after about two hours I used that to start playing with different filters.  Still no problems as I said.  I'll try to run as I'm running until problems show up again, and then make changes at that point, well at least that's the plan if I can stick to it.

Quote
When you run into that problem, did you just select the tracks for a first time, or was it a left over of a previous attempt (or playback which you stopped for other reasons) ?
I ask, because I feel this can make a difference.


Always a fresh selection.   I agree that previous selections are not totally reliable.  

Quote
Click the [ P ] from Playback Area (selection), which clears the selection completely.
BUT and ALSO :
I recall that you don't use a Tablet etc. for control. This will mean that you are the by now more rare occasion of NOT using the "Touch Facilities" (see Services and OSD section in Settings). And *now* suddenly we might have a good reason of
a. me never seeing this behavior;
b. it possibly being wrongly working just because of the normal mouse operation.
Ad b.
The "Touch Facilities"  ...


Hey Peter you are right, I don't use Tablet control.  I'm under the presumption that I need a network to use a tablet for control.  No?   Remember, on purpose, I try to avoid the LAN or the Wifi  to quiet the system and avoid Windows OS updates and virus scans, mostly the OS related issues.  It is a true joy to not hassle with PC stuff; it just works like a toaster oven.

a. and b. above are very pragmatic.  Although it is hard to believe that all of your active users have gone to tablets for control.

Thanks,

Charlie

[Edit: Also, I have no means of running a LAN cable to my xxPC without creating a trip hazard via a very long LAN cable.]
14  Ultimate Audio Playback / XXHighEnd Support / Re: xxHE with xxPC and Wyred 4 Sound DAC2 DSDse on: December 28, 2017, 02:02:32 am
Hi Peter

Yes,  already, "Always clear Proxy before Playback" is selected / enabled.

BTW, status for yesterday:  Clicked "Stop WASAPI" in settings and I had only half of my problem.  Second half is gone, this one: "This shouldn't happen. Please just restart xxHE"

The first half of my problem is still with me:  Three times in 4 hours playback stopped on the first song.  The first time it stoped while the track was playing, but toward the end.  That is a first.  The two other times were as before, namely after the first track plays, xxHE stops and comes back.

In all cases I noticed what we suspect, playback started too quickly, almost in 2 seconds.  In all cases, when xx came back, all tracks were selected as if they had not played.  (Because when one plays normally, that track comes back unselected and the unplayed tracks come selected.

Thanks,

Charlie
15  Ultimate Audio Playback / XXHighEnd Support / Re: xxHE with xxPC and Wyred 4 Sound DAC2 DSDse on: December 26, 2017, 04:50:40 pm
Thanks Peter.   I'll get on these to get to the bottom of it all.

Quote
The problem of stopped playback after the first or any other track never happened.  BIG WIN.

It should be clear that you actually solved the problem. But it also should be clear that by means of something you brought back the problem. So the obvious : try to think of what it can have been.


Absolutely nothing was changed from the previous session in terms of settings.  I've been very careful about changes.  No changes.  The only difference is that it was another day and a new boot.  That's all.  I didn't even change "copy to XX drive by standard" until after the problem arrived.
       One thing I can say is that I encountered several "this error should not happen, just restart xx" message before the "stop problem" first resurfaced (in case that matters).  And the stop problem.

Quote
W7 Settings (amazing that I saved them) :


Thanks.  That helps.

Quote
Quote
Over years I've spent many nights reading this / these forums and somehow I missed it.  
So all these years I didn't have exclusive access to the audio device?

I can't tell about others, but I don't think you have missed it.


Yes I remember all of that.  Well,  I missed it in the sense that my windows sounds were enabled.

Quote
Quote
Alternatively, would it be more effective to chose the default sound device to be the motherboard audio device.  Then it is just bits going to another DAC.

You are correct. Still it is better to just shut off all the WASAPI (WDM) audio devices, which is all what you can see when being in Normal OS. Just disable them. Btw, I have the hint that this matters for your "This message should not occur" issue. So try it. Otherwise do know that when WASAPI is shut off (do that in Normal OS) in MinOS there just isn't another choice for Sound Device but your KS device.


Before I do this I had better check: This implies that I have to reboot into normal OS and manually disable all sound devices that I see INCLUDING MY DAC.  Then reboot into minOS and proceed.

Wouldn't it be easier to simply disable WASAPI from within xxHE in settings?   Or does this not sufficiently accomplish what you want?

Quote
Quote
so xxHE probably already sends the data to the C drive.

No. When it is .WAV is stays where it is and is played from that location.


Most of my collection is .AIF, from ripped CDs.  Is AIF treated like wave?   (Maybe the problem surfaces when I eventually play a .WAV track)

Quote
can't play DSD for the while that you are in this "test mode"


Of course, yes, I will disable WASAPI in one form or another and lose DSD for a while.   No problem.

Also,  I'll play close attention to when playback starts quicker than expected, and the file type as I select it.

Thanks again Peter.

Much appreciated.

Charlie
Pages: [1] 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
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.091 seconds with 12 queries.