Was no sound no track given error - now no sound and out of memory error

[bhobba]

Hi

Just downloaded the demo version XXHighEnd to check it out on my desktop PC (not my audio pc which I haven't set up yet).  Got around the 8.3 name error by changing the registry.  However whenever I play anything I get no sound then after a while a no track given error appears.  Since this is just for checking out purposes I have not connected a dac or anything like that; simply using the motherboards soundcard.  Anyway hoping someone can help with whats going on.  The main thing I want to do at the moment is check it out.  I am trying to decide whether to go for a Windows or a Mac as my music server.  Personally I prefer a Windows set up, but the posts I read all seem to say get a mac mini.  I am not 100% convinced about this.

Noticed someone else had a similar problem and it seems to be associated with nothing appearing in the KS Mode box.  I have nothing there and it does not matter what I try I cant get anything to appear there.

Tried using an older version of the software.  Still got the same problems.  So reinstalled the latest version.  Now I still have no sound but now get out of memory error.

Thanks
Bill

[Calibrator]

Hi

Just downloaded the demo version XXHighEnd to check it out on my desktop PC (not my audio pc which I haven't set up yet).  Got around the 8.3 name error by changing the registry.  However whenever I play anything I get no sound then after a while a no track given error appears.  Since this is just for checking out purposes I have not connected a dac or anything like that; simply using the motherboards soundcard.  Anyway hoping someone can help with whats going on.  The main thing I want to do at the moment is check it out.  I am trying to decide whether to go for a Windows or a Mac as my music server.  Personally I prefer a Windows set up, but the posts I read all seem to say get a mac mini.  I am not 100% convinced about this.

Noticed someone else had a similar problem and it seems to be associated with nothing appearing in the KS Mode box.  I have nothing there and it does not matter what I try I cant get anything to appear there.

Tried using an older version of the software.  Still got the same problems.  So reinstalled the latest version.  Now I still have no sound but now get out of memory error.

Thanks
Bill

Bill,

can you give us a quick rundown on your desktop PC's components? O/S , CPU type , Ram , Motherboard's sound device should be sufficient for the moment.

In case you haven't read it yet, the "Installation Guide for Dummies" ( http://www.phasure.com/index.php?topic=833.0 ) is a must read initially. I would presume you have but thought it necessary to check.

The lack of entries for KS in the setup page is likely due to limitations of the on-board sound device ( or drivers ).

We'll get you going before too long

Russ

[bhobba]

Hi

Thanks for the prompt response.

I have an I7 860 on a P7P55DLE motherboard and am using the motherboards inbuilt sound-card which the manual says is an absolute pitch BD 192/24 (whatever that is - of course I know what 192/24 means I just don't know what absolute pitch BD is).  I have two Falcon 64gb SSD drives raid-0 as my boot drive and a 320gb hard drive for my D drive.  I have 4gb ram and am running windows 7 home edition.

Oh and I forgot to mention when I installed the older version and had the same problems then reverted back to the latest version the KS box is now populated - but I am now getting an out of memory error. 

Now I know it is a 192/24 DAC I set that as the dac and that seems to have stopped the out of memory error but still no sound.  BTW foobar works perfectly.

Getting out of memory exception error again now.

Thanks
Bill

[PeterSt]

Hi Bill,

In the Settings Area (towards the bottom) there's a field "Split File at size". Set this to a low value (like 60) and let me know what happens.
Also, do not use any Doubling or Upsampling for the moment and use a normal CD (16/44.1) at trying.

I can't tell whether the internal soundcard can cope with even 44.1 (you can see that in the device properties (start at the loudspeaker icon) in the advanced tabm and the combobox in there <- no need to change anything there because it doesn't do anything). But if not, you'd have to tick the box "96/192 only" in the Settins Area and next use Anti Imaging filtering.

Let me know if this is not clear enough (I'm known for being not clear )
Peter



PS: Not much MAC-Mini provocers in here, I can tell you ! And keep in mind there's not much playback software for it either (that's why each new found piece of MAC software is a hype immedietaly; try to see through it !)

[bhobba]

Hi Peter

You are perfectly clear to me mate - no problemo.

Tried that - makes no difference - but the out of memory exception error comes up earlier now.  Still no sound.  Foobar still works perfectly.

Yea I take with a little bit of salt claims that the mac mini bests a windows machine.  Even though they claimed double blind tests to prove it.  I wonder exactly what windows machine they were using.  It was made by the makers of the tranquility DAC which by all accounts is actually a very good DAC and developed using (supposedly anyway) double blind tests by ex bell engineers.  But they make the claim that even the USB cable makes an audible difference.  I must admit I find that hard to believe - but if they are telling the truth double blind test can't really be faked.  But they also say there is no reason technically why a windows machine should not sound as good or even better.  Anyway we can all have a longer chat abut it once we get it working.

Thanks
Bill

[PeterSt]

Hi Bill - about the latter, what they forget is that software already sounds (VERY) different, not matter all output is "bit perfect". So how can they have compared decently, knowing that the playback software could not be the same.

About your problem ... I can't think of what this is. I mean, with that parameter set to 60 (but you can go as low as 12, you might try it), there is no way I know of you can go out of memory. Thus, it must be something in the driver ...

If you say Foobar works ... with what means of sound did you try it ? WASAPI ? KS ?
And for XX actually the same, did you try WASAPI as well ? (these are the devices without the KS: prefix)

[bhobba]

Hi Peter

Foobar works with and without WAPSI.

I dont quite know what you mean by 'And for XX actually the same, did you try WASAPI as well ? (these are the devices without the KS: prefix)'

Anyway heading off to get a bit of dinner and sit down to watch a bit of TV.  Will let it regurgitate overnight and read the idiots guide again.  Might be some silly thing I am doing.  Will do another post tomorrow (Aus time) about what eventuates.

Thanks
Bill

[PeterSt]

G'day once again !

I dont quite know what you mean by 'And for XX actually the same, did you try WASAPI as well ?

As kind of said : Choose an output device (Settings Area) that is NOT prefixed with "KS:"
This will be WASAPI.

It looks like you tried Foobar with WASAPI and XXHighEnd with Kernel Streaming. This is apples and oranges !
But as far as I can expect now, WASAPI will work, and you will have a problem with the KS driver (don't bother with the latter, and get along with the former).

Have a nice evening !
Peter

[bhobba]

Hi Peter

Now I think we are getting to the heart of the problem.  In Foobar I had to download WASAPI as a dll I put in my component directory - foo_out_wapsi_dll.  After doing that I had twice the number of devices output devices available for me to select - the previous 3 devices with DS in front of them and 3 new devices with WASAPI in front of them but exactly the same name after.  I do not see any name for me to select from in XXHighend what has WASAPI in front of them.  Could this be the problem?

I also have to mention I tried uninstalling and reinstalling it but after doing that I lost any info in the KS mode box.  I suspect I could get it back again by uninstalling the current version, installing an older version, and installing the current version.  I am loathe to do this however for a few reasons.  First I want to get this WASAPI thing sorted out.  Secondly I don't have any ability to actually select anything in those boxes even though they are drop down.  That may also have something to do with it.  An lastly I think it it is in fact related my problems.

Thanks
Bill 

[PeterSt]

Hey Bill,

I now wonder whether you ever tried Foobar WASAPI. I mean, it looks like you're telling you just downloaded that dll for it. Or ?
Anyway, if you say "In Foobar it works", it should work with WASAPI. Does it ?

Next, in XXHighEnd you have to choose any device not preceeded with "KS:". So, there's no WASAPI mentioned, but it is as long as it is no Kernel Streaming (KS:) device.

The empty KS Mode box is unintentional and my fault. But, it is no problem for now, because that is Kernel Streaming while right now we are focusing on WASAPI (one thing at a time).

And keep in mind Bill, the fact Foobar does or does not play (WASAPI !) is key here. If XXHighEnd works, fine, but if not and Foobar does, it's my turn to find out why.

Peter

[bhobba]

Hi Peter

Thanks for you perseverance in this matter.  It is appreciated.

Yes I not only have used WASAPI in foobar but since I downloaded it it is all I use.  I have just now checked it and confirmed the device I am using is WASAPI Speakers - High Definition Output Device - exactly the same as the option I am using in XXHighend - except it does not have WASAPI in front of it.  And I am certain foobar is using WASAPI as well since programs that do not use it output no sound when I am playing foobar.  I actually rather like this feature because it stops the programs annoying me while I am listening.  Rest assured I am not playing foobar when I am using XXHighend.

Out of curiosity I tried to play XXHighend while Foobar was playing.  It wouldn't let me saying the device was in use.  I don't know if that helps at all.

Thanks
Bill

[PeterSt]

I just don't get it.

Would it be possible for you to create a new folder for XX, install the original 0.9y-8 in there and over that paste the 0.9y-8c ?
(I only want to be sure you don't have mixed two versions).

Also I wonder where actually the out of memory comes from. Can you post a screen copy of the error ?

Lastly, you may turn on your logging (at the bottom in the Settings Area) and post the XX, X3 and X3PB log file (in the TemporaryData folder under your XX folder). Thus, let the error appear, then get the log files an attach them here.


PS: It won't be a coveart picture erroring out ?

[boleary]

So I assume your output device selection  in XX is "Speakers/Headphones" since you are using the mobo sound device? This automatically selects engine 3 (wasapi) here. If so, have you tried ticking 32 bits in the dac settings? Just wondering.

[bhobba]

Hi Peter

As explained in a previous post I am not getting the out of memory error any more - I am getting the track wont play error because the KS mode box is not populated.  To force it to get the out of memory error I need to install a previous version then reinstall the current version which I will now do.  Your work around for the KS box error will not work for me because I don't have any devices with KS in front of them to select.

After installing an earlier version I will reinstall the latest version exactly as you describe it by creating a new folder and overwriting it with the C version

As for posting the screen I don't really know how to do that because in all the years I have been using PC I have never had reason to do it.

I will post the logging information.

Thanks
Bill

[bhobba]

So I assume your output device selection  in XX is "Speakers/Headphones" since you are using the mobo sound device? This automatically selects engine 3 (wasapi) here. If so, have you tried ticking 32 bits in the dac settings? Just wondering.

The output device I selected in XXHighend is (and this is an exact copy) Speakers - High Definition Output Device.  The output device I selected in Foobar is (again exact copy) WASAPI Speakers - High Definition Output Device.

I have tries ticking the 32 bit dac settings and heaps of other stuff.  I will try them again.

Thanks
Bill

[Calibrator]

As for posting the screen I don't really know how to do that because in all the years I have been using PC I have never had reason to do it.

This should help Bill ...

http://www.phasure.com/index.php?topic=768.msg5610#msg5610

Cheers,

Russ

[bhobba]

Hi Peter and All

OK here is what I did.  As mentioned previously I have nothing in the KS-Mode box and nothing I seem to be able to do will put something in there.  So with the latest version of the sotware I get no osund and the no tracks given error.  Previously I managed to get something in this box by installing a previous version and then installing the new version.  This fixed it previously.  However now for some reason it does not seem to be the case.  I cant get anything to appear in the KS-mode box it does not matter what I try.  So obviously it is of no value in me giving screen shots or anything like that.

However while I had version 9-1 installed for the first time ever I managed to get some sounds out of it - sometimes it didn't play at all, sometimes it played by very softly, and sometimes it played at normal volume.  However the volume control in XX seems to have no effect - only the windows 7 volume control did anything.  Also after a while I got the following error - Unexpected Situation at Remote Command - Playback Must Stop.  It may have been my imagination but it seemed to me that playing with the XX volume control caused the error to occur faster.  I cant be 100% sure of this however - as I said it may have just been my imagination.

I did however run it with the log switched on and have attached the logs.

Thanks
Bill

[PeterSt]

It may have been my imagination but it seemed to me that playing with the XX volume control caused the error to occur faster.

Correct. But I'd leave the volume in XX at max all the time.

Bill, to make life easier for you (if I ever can ) ... you are obsessed about that KS box somehow ... this is totally UNrelated !!!
If you are trying Engine#3 devices (those without KS: prefix) that box does nothing.

I hate to ask it, but can you also post the X3PB log file from the earlier situation ? (just look at the date/time of the file).

I am so sorry for your troubles, but I also don't know what you are doing or what is happening ...

Cheers,
Peter

[bhobba]

Hi Peter

Unfortunately I cant post the logs from the previous situation because I deleted it when I deleted the files and reinstalled it as per your suggestion.  Sorry about that.

The reason I keep mentioning the KS Box is not because I believe it is related, it is because it prevents me from running the latest version of the software to get at the bottom of what my problem really is.  As I said I was able to get it working previously by installing an earlier version but it didn't seem to work this time for some reason.  I will be quite happy to run it and post the logs as soon as you can tell me how to get it running without getting the no track error.

I also want to add since I was able to get sounds out of it I am quite happy to buy the software a bit later.  I would like to wait until after the 18th of next month to get on that months credit card since I had a big expense this month.  My bed broke and I had to get a new one - $570 - ouch.

Since I have not set up my system yet there is no real hurry about getting it working for me.  I am confident once you have released a version that solves the KS Box issue I can run the program and we can get to the bottom on why I am having problems.  If you still want to look into it now - no problemo - I am happy to assist.  But from my perspective there is no real hurry.  I am just really happy to have come across a group of guys on my wavelength.

Thanks
Bill

[PeterSt]

Hi again Bill,

Let me first tell you that on my part this is not about you or anyone buying the software. The crazy thing should just work for everyone. But sometimes it is hard to get what is going on.

Ok, as you say it now, while attempting to get Engine#3 (= WASAPI) running, without something in that KS Mode combobox it won't work. If *that* is the plain cause, well that is something I can work on of course. As I said before, I recognize it can happen (per a bug), but never knew it would disturb Engine#3 playback.
And please keep in mind that we only later started about Engine#3, while for me there's only logic in having that box filled for Engine#4.

So, if you can confirm that this is defenitely it I'm sure I can work it out.

Be careful with your new bed now !

Thanks for all your time.
Peter

[PeterSt]

Man, if you only would have pointed me to my own text in the latest Release Notes :

Edit2 :
This version contains a bug causing a "No track given" error in some situations, which can be worked around like this :
The KS Mode and Device Buffer Size (settings Areas) comboboxes will initially show empty. When this is the case, the error message will follow.
To make something show in those boxes, choose a hopefully present KS: device, and next choose something for each of the boxes.
Note : If you want to use Kernel Streaming (Engine#4) you will be doing this automatically anyway. When not (Engine#3 instead) after you made the selections you will want to choose a non-KS: device again.
After this is applied (fill those two boxes), all should play.

What a I am.
Anyway, I had forgotten that one ... ('No tracks given' error )

Peter

[bhobba]

Hi Peter and All

Let me first tell you that on my part this is not about you or anyone buying the software. The crazy thing should just work for everyone. But sometimes it is hard to get what is going on.

Sorry if I gave you that impression.  All I meant by it was I am very happy with the way you and others have been so helpful and seem to have many of the same ideas I do about audio.  Because of that I get a good felling, so good I want to join you ranks by purchasing the product.  Thats all.  Big pat to everyone for making feel so welcome.

So, if you can confirm that this is defenitely it I'm sure I can work it out.

Yep - that all it is.  For the time being anyway.  When you get it fixed who knows what else will pop up.  But the fact I got it to work with an earlier version - admittedly with another problem - shows me for the time being this is all that needs to be done.

Thanks for all your time.
Peter

It has been a pleasure.

Thanks
Bill