XXHighEnd - The Ultra HighEnd Audio Player
October 19, 2017, 05:40:20 am *
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  
Pages: [1] 2 3 4 5 6 7 8 9 10
 1 
 on: October 19, 2017, 12:56:33 am 
Started by hvdh - Last post by acg
Yep, that message sits down in the bottom right of my screen as well during unattended playback.

 2 
 on: October 18, 2017, 07:40:28 pm 
Started by hvdh - Last post by hvdh
Nope.
UNattended...

 3 
 on: October 18, 2017, 07:06:25 pm 
Started by hvdh - Last post by PeterSt
Quote
It would be nice though if I could just boot the machine and start playing...

Yes Lazy You. That is why I never shut down any PC wherever I am. Happy

Best regards,
Peter

 4 
 on: October 18, 2017, 07:05:03 pm 
Started by hvdh - Last post by PeterSt
Hi Henk.

All normal.

Quote
still visible during Unattended Play.

Attended, I reckon.

Regards,
Peter

 5 
 on: October 18, 2017, 06:49:07 pm 
Started by hvdh - Last post by hvdh
The service taking care of these things won't run. Later it might start for other reasons (decision of XXHighEnd) and again later it will shut off again (XXHighEnd again). And then later it will start. And so on.
Good answer eh ?
haha

Peter, This was exactly the answer I was looking for. I had expected something like this.

So all I need to do is start my command file from the desktop after boot, and I am fine.

It would be nice though if I could just boot the machine and start playing...

 6 
 on: October 18, 2017, 06:42:33 pm 
Started by hvdh - Last post by hvdh
Peter,

After I "upgraded" from Win10 10586 to Win10 14393, I've noticed one small change that I did not expect:

The "Activate Windows" message is (sometimes) still visible during Unattended Play.

It's probably nothing to worry about, and I know I can get rid of it myself by killing Explorer in the Task Manager, but still.

Are you aware of this change in behaviour between 10586 and 14393?

Is it possible that this change is caused by my starting to use Imdisk?

Henk

 7 
 on: October 17, 2017, 02:13:09 pm 
Started by dsm - Last post by PeterSt
Arjan,

Hmm ...

In any event the shorter the SFS the sorther the burst. Coincidentally I changed mine from 0.9 to 1.5 yesterday, so maybe I can recognize it starts to happen to me too (it did once for 2.08 but I have it 1-2 times per year anyway (1 time will be closer to the truth)).

What is your Q1/xQ1 ? (mine is 14/1)

Peter

 8 
 on: October 17, 2017, 12:18:17 pm 
Started by dsm - Last post by Arjan
Hi Peter,

Had the same issue of burst of noise now 2 times with 2.08a.
The first time it was 2 bursts after each other. The second time was just one burst.
The second time (I do not recall the first time) the music stopped after the burst.
I just restarted the track and no issues.

It is a bit scary. Any clues on this issue? I have never heard this kind of noise burst before. I know of cracks and other short ticks but this is different.
My SFS is at 2 so not long but also not ultra short. Should it be longer, but the burst will be longer too. Or shorter?

regards, Arjan

 9 
 on: October 17, 2017, 09:30:14 am 
Started by hvdh - Last post by PeterSt
Hi Henk,

I was referring to the topic and the consistency plus the help in the .bat itself, so you could not make mistakes. That is all.

And that you very clearly do not at all what's in that texts, is also clear, right ?
In other words :

If you think you can automate things, which for a reason is not in any help or topic described, you are on your own. Also, might you be able to find the topics/posts of concern about automatic start etc., you will see that I explicitly NOT advise that. So you can do it, but now it is *you* who must know how. And strangely enough, there it goes wrong. Funny eh ?

Quote
If I reboot in MINos, my own .cmd file does not work as intended. It either never even starts copying files to the E:\ drive, or it does it way too late.

The service taking care of these things won't run. Later it might start for other reasons (decision of XXHighEnd) and again later it will shut off again (XXHighEnd again). And then later it will start. And so on.
Good answer eh ?
haha

In Normal OS all services just happily run, so there you can't have the problem.

Now, follow the procedure as I have written it, be a bit less lazy and all will be fine. OK ?
Happy
Peter

PS: Another advice : don't try to force that (whatever) service to run because it will be one big mess. I promise !


 10 
 on: October 17, 2017, 09:16:39 am 
Started by hvdh - Last post by hvdh
Hi Peter,

Thanks for the quick response. It's not exactly what I had hoped for though....

Of course I have read your Ramdisk topic, otherwise I would never have gotten it going.

And of course I used your rama.bat, it says so in my original post in this topic.
And if you compare your rama.bat with my command file, you will see that they are very similar.

The reason I am not using A:\ and B:\ is quite simple. Both these drive letters are used on my music PC, and shared on the network with the same drive letter on the audio PC.

Is the drive letter significant? If needed I can change them, but I never saw the point.

My only concern is:
- Use of Ramdisk, as you describe it works well, both in MAXos and in MINos.

However:
If I reboot in MINos, my own .cmd file does not work as intended. It either never even starts copying files to the E:\ drive, or it does it way too late.

Yesterday I rebooted the pc in MINos.
After 3 minutes I got fed-up, used your procedure to start up two RAMdisks manually, and started XXhighend in RAM, and had Music.

15 minutes later, a command window pops up, which shows files being copied to the E:\ disk and it too starts up XXhighend in RAM. This all happens while I'm playing music in MINos, with the Ram XXHighend that I had started manually.

So now I have XXHighend running twice, which obviously causes problems. I can not remember when exactly I got the error message in which I am asked if I want to keep running both or not, but of course that message also appears.

The only answer I am looking for is:
Why does it take 20 minutes for my command file to run, it is called in the same startup folder as your XXHighend Control Panel, so I expect it to run immediately after boot?

Could this be caused by a difference between MAXos and MINos which prevents all links in the startup folder to be executed?

Regards,

Henk

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.282 seconds with 15 queries.