XXHighEnd

Hi,

I had this issue. After all the wait, unattend started only for couple of second than no sound. Any suggestion? I have tried 5-6 times and even with just single track same same result.

(i'm on a Trial Version)

Thanks,
Adrian

Hi Adrian,

What do you mean "after all the wait" ?
Does it take that long before the loading is finished ?

Peter

Hi Peter,

I have about 30 songs on the playlist, it take about 1 min to load.


Thanks,
Adrian

At least this is mot about the Demo version. First suspect is the Split File Size (SFS). What do you have it at ? If you set it to 4.00, what is the change ?

If you activate (in Settings) "Don't do anything with Coverart", does it make a difference ?

Is Attended fine ?

What processor do you have in there ?

Otherwise 1 minute for 30 tracks is quite (very) long. So my general perception is that this PC is very underrated ? (small laptop ?). This doesn't mean it nothing can play, but it does mean that it is more difficult to find the proper combination of settings. But let's start with above small questions.

Regards,
Peter

Peter, the other question is if they are WAV files...they take considerably longer to load than FLAC because only one core is used at a time to upsample/convert them.  I just loaded a random 30 tracks of mixed WAV and FLAC into a playlist and the time from when I pressed play to sound coming out was 1m25s.

Hi Anthony,

Then you seriously do/have something wrong.

4-5 seconds here (FLAC ~3). Audio PC at 430MHz.
Look at my Sig; that should do it.

Open a new topic for it, if you like.

Regards,
Peter

Hi Adrian,


Set the Max to 120 or so (and best is to reboot after that). Otherwise all your free memory is eaten right away.


Uhm, I intended to ask you to try this.


That too was a question. ;)


If all other settings changes don't help, then it is the most obvious that another Core Appointment setting will help. But you can't change that in Demo Mode.
What now instead could help (but it is a long shot) is :
setting Q3, Q4 and Q5 all to 0
or
setting Q3, Q4 and Q5 all to 1
(this is under the [ Q ] button near the bottom of the main screen.

Q1 will be defaulted to 14. Try 20 and try 7 (have xQ1 at 1).

So the most crucial it is to watch for changes in the behavior and tell me about it. A change in behavior could be :
- Now no sound comes from it at all;
- Now the sound lasts for a couple of seconds longer.

Peter

Hi Adrian,

Hey, good !

The 400 Max is close to the limits of some internal memory part (regard the 400 as a number which expands a couple of times and which implies ~2GB of internal memory usage which is the limit for one thread <- never mind the who or what).
Normally this can work but it depends on other things as well.

Theoretically it can also be the 20 you set and used (the 20 is the part which you really use, the 400 is the part which is reserved for you and which you can use in ad-hoc fashion when you want). If that is so, set it back to 20 and you will know. It is almost more logical that this 20 was the culprit as it implies a larger chunk of data (compare to the 4 you set currently) to process at one time (think about the few secs of music you heard came from one chunk, implied by the 20).

There will also be Help in the Tooltips on the fields.

Good that it is solved !
Regards,
Peter

Thanks Peter and everyone else who helped. Happy Listening. :P