9z-5 AutoHK problems

[Scroobius]

I took care to install AutoHK correctly having had problems in the past. Anyway AutoHK points to the correct directory and the message confirms that when I start up AutoHK. I then start up XX and with the XX UI on the desktop but no music file playing I can change volume (alt U and alt D) and it works fine. But when I start XX in unattended mode and then try to use alt u and alt d they do not work or i get an error message Alt S works though shutting down XX and returning desktop correctly. My set up is in my signature area below.

All the best

PC

[PeterSt]

What is the error message ?

Does it work with an SFS of, say, 40 ?
If it does, think about you are putting too much constraint on the PC in order to keep playback going (all your buffers being at 48 samples which is rather low at 384). If this indeed helps, I may be able to improve on things in the next version.

Peter

[Scroobius]

I set SFS to 40 and also set buffers to 512 - makes no difference to the problem. I tried Alt u/d a few times with these settings and it really screwed XX which locked  - required a reboot XX lost its settings and needed two more reboots before I could actually get XX to load properly.

No error messages this time when I was pressing alt u/d but the "spinning circle" came for a few seconds as it tried to execute a command (I guess!!).

Previously (to try and fix the problem) I deleted XX registry entry and XX completely the re-installed. But that made no difference to the problem.

Al the best
PC

[PeterSt]

I really have noooo clue.

But please look here, maybe that helps in giving me some hints ... : XXHighEnd Model 0.9z-4-1 problems. Try to skip the unrelated posts ...

Peter

[Scroobius]

Hi again Peter

Well it appears resource is not causing the problem. So I operated XX in Unattended (services NOT selected to shut down) and attempted Alt U which did NOT work within some time. So then I used Alt S to close XX THEN the volume reduced by 1.5db I then pressed Alt S again and XX shut down. This is very repeatable - tried it a few times. So I took a log of events (attached) which shows (possibly?) a security access problem (see attached XX log file).

So this is most likely a problem with my security settings (damn microsoft!!!!). I also appreciate this is my problem and not yours but if there is some help you can give me to help me on my way it would be appreciated but if not no problem :-).

Looking at the security settings of the folder (see "1" attached) the XX folder is "read only". I have tried to change this but it will not allow me to - specifically I change the settings then apply them but when I check the folder nothing has changed.

All the best

PC

[PeterSt]

That seems strange - unless you first burned XX to a CD and copied it from there or something.

Did you try

- Open command prompt (cmd from Run);
- Go to your XX folder (with CD commands, like CD \MyXXFolder)
- ATTRIB *.* -R (the R is from Read Only)

You can check with ATTRIB *.* for the status of all the files.

Thanks for your help, and let me know ...
Peter

[Scroobius]

No nothing fancy about the install - XX was downloaded unzipped and installed in the usual way.

I did try ATTRIB cmd but just tried again anyway. Actually checking the security of xx directory again the blue indicates that some of the files are read only - there is a tick option for all the files in directory to be read only so maybe that's OK anyway. I checked my XP other PC and it is the same.

So for the moment I am stumped but do you agree that it does seem to be a security/access problem?

The computer is new the O/S is a fresh install and I have not made any significant changes to any of the config.

PC

[PeterSt]

Actually it must be about the folder itself. So, all the files are "allowed" to be read only (well, by heart I wouldn't know of any that should be over-writeable as how they come from the install), but new files must be able to create and next change. Also, if files can't be created, I can't even imagine that anything goes. So, I guess the folder should have the create rights in the first place ...

I can't make screen copies at this time, but if you go to the XX folder, rightclick on it, ask for the properties, and next ask for the security tab, you have a list of users;
Do they all show "full access" ? If not, that will be your problem, and maybe you can change it (you should be able to). Apply this for the Verified Users and for the Administrators should be sufficient, but you can try to do all of them.

Of course yuor User Account Control (UAC) must be off (for W7 slider all the way down, and reboot after changing it !).

I'll be off in a short while ...
Peter

[PeterSt]

PC, I also wanted to add this :

Your Alt-S descriptions don't seem right to me. Normal Unattended sequence would be (not having activated "Don't start playback at all") :

- Click Play (XX GUI will vanish in the end);
- Apply Alt-U or Alt-D;
when you want to stop playback :
- Bring up XX with Alt-X;
- Click Stop.

I don't see any Alt-S in this sequence, although the "Click Stop" could be replaced by that. But this is not how *you* apply it ...

Maybe this changes things ?

[Scroobius]

OK - Alt-S closes down XX and returns to the desktop - well thats another/related problem I guess. I will use alt x but it does not change the problem of alt u / d not working. Using Alt X correctly does not change the Alt U/D problem (unfortunately).

UAC was set down to zero right from the start and I checked and it is still at zero so no problem there.

Admin privileges were at "Full Control" for me as administrator anyway but now I have set all the listed users (as shown in the attached) to have "Full Control" access anyway but the problem remains. The log file is still showing the same error message

    path 'C:\XXHighEnd-09-z5\XXRequestPending.dat' is denied

Overall its not a major problem if this does not work because unattended does work but I would like to sort it if I can.

Just a question - does XX create the above file as a temporary file? because I cannot see it in the directory anywhere so wondered if XX just cannot actually create the file in the first place.

By the way I can create files in the XX directory (no surprise really but just thought I would check).

Also I seem to remember having a similar problem before on my laptop but I don't think it was fixed as such just that with updates to XX and other non related changes it started to work at some time.

All the best

Paul

[PeterSt]

Just a question - does XX create the above file as a temporary file?

Yes.

Sorry for the lateish answer ....
Peter

[boleary]

I have the exact same problem here with alt U or D. i have full administrative priviledges. Whats interesting is that in unattended when I hit alt U I do not hear a sound change; however, when I then alt X and the GUI reappears, the sound db # has changed correctly, (lower by 1.5 db). When I then alt p the sound is then increased by the alt u command from the last unattended request! So it seems that the software only partially responds ( the db # changes) to the Alt U command in unattended. Hope this helps.