XXHighEnd

hey there Peter,

have just spent a frustrating afternoon trying to get the folder/back artwork displaying in unattended mode without the encumbent OSD TEXT or RUNNING TIME OSD, and I've not succeeded :(

The only way to get the coverart shown is if I tick the OSD TEXT box, but then that ugly font invades the screen.

In addition, if I tick the TIMER OSD, the new graphic extends the full width of the screen at the bottom, with the left hand side starting anywhere between 9 to 12 minutes, and the right side showing something like 30 odd minutes.

I initially installed 0.9z-6 on my fully tweaked system, and found the issue with the coverart there. Tried may things to no avail, so restored my C drive to an image prior to all the tweaking I had made, so in essence it was as plain as can be. Tried again with 0.9z-6 afresh and still no go.

Thinking it might be due to the unique screen res I use ( 1280 x 834 ), I reverted to a standard 1280 x 1024, but still no good.

I'm thinking there may be some glitch with ChangeWP, or something has got out of sync. Went searching in registry for anything to do with ChangeWP but found nothing. Is there a way to reset things back to zero ?

Also tried with a clean \XXDATA\ folder.

I'm outta ideas !!

Cheers,

Russ

PS. what i've heard so far sounds nice though :) 

Ok Russ. Let me first of all tell that I don't recognize any single bit of this all. This could help ... (I'm serious).

Skip the time bar for now. Just for better focus (BUT, the fact that it acts this weirs does sure tell something).

Before proceeding, can you let me know what you actually think this causes (caused) this ? And a major question would be : did this start under Minimized OS at first ? Do you maybe have this only under the Minimized OS ? Did you ever try that at all already ?

Then we'll proceed. I'll be waiting.

(hey ! I'm not used to anything like this from you, but I do realize that it must have been your birthday recently ... haha)

PS: A Picture about that strange font may help too !

When i first installed 0.9z-6 this morning it was on the same environment I had been using with 0.9z-5-2, and all I did was set up the parameters and ticked the Monitor OFF and Minimise OS boxes, then let it do the reboot. At first play at unattended I noticed the monitor shut down as expected, and a mouse movement brought the monitor back to life, but no coverart showing. It was a while before I figured the OSD TEXT box brought it to life.

After I had restored the C drive I did run into a re-occurring error that I thought was related to AutoHotKey, but I eventually got that sorted out and haven't seen it again. AutoHotKey is now working fine.

The message was ...

"Interrupt Mechanism Out of order; Notify XXHighEnd development. (Restart Playback)"

Perhaps I should have used the term LARGE font, instead of UGLY font. Regardless, I don't particularly want it cluttering up my screen.

Another FYI, when the TIMER OSD is active, the left and right limits change with each track change. IOW, it might start at 9 minutes and go across the screen fully, and the next track might start at say, 11 1/2 minutes.

While I was writing up this reply (on another PC) I had a further instance of that "Interrupt Mechanism" occur, so there's still an issue there.

Still think it's related to ChangeWP somehow, as that has caused issues in the past, but normally sorts itself out after a whle.

ta !

Russ

Ignore the text about a reoccurrence of the error message. I had "Paint" open showing the error code I captured earlier, and I had forgotten about it !! Trying to do too many things at once at the moment here. Need a good granny nap .. haha

Russ

Forget about the Interrupt thing for now (it is important, but we'll do one thing at a time).
... having said this ... does it happen always ? otherwise you won't be able to test any OSD stuff ...

Does it help when you exclude the service {FontCache} ?

Also, do you see this strange font anywhere else except as OSD text ?

I only see that large font when the OSD text is enabled, and I presume it's supposed to be that large. Also, I'm pretty sure I had the font cache disabled on my tweaked system, so maybe that helped there. Will go have a play now on music server.

back soon.

Russ

But careful here, because I don't even know how to do this for the most convenient proper sequence. What would work is :

Just obtain this service as "To Keep". Reboot into the normal OS situation; Reboot for Minimized.

Still, I'm somehow lacking the answers of what's actually going on. Like : when in Normal OS mode ... does this all happen too ?

The font cache service was set to Manual but was not Started. I set to disable and rebooted and tried again. No change. This was how I would have had that service set when i tweaked the system for 0.9z-5-2.

Happens both in the initial unMinimised OS and the Minimised OS mode.

I have taken a couple of quick, and somewhat blurry pictures, via phone, to show the screen.

error_01 shows the font size I'm talking about, and it's always been this big, so I suspect that's normal. (but ugly ;) )

error_02 shows a close up of the scale digits. Notice that for this track they are starting at the 101 minute mark (last red digit a little hard to see 'cus it's masked by the 1/4 symbol). Note: It's only a 10:10 length track and the whole album is only about 40 something minutes long i think.

Hope this helps a little.

Russ

Russ, I don't understand one thing of what you are saying.

What is exactly the matter with this ? that it is bigger than normal (you don't seem to say that *now*). Is it ugly - but normal ? (that's what you seem to tell).

Conclusion, all is right.
:swoon:

Besides that, all looks normal to me.
But will you now stop please about that time bar ? I want to solve your OSD stuff first. *IF* there's something to solve.

now what ??

I posted the first picture for you to give feedback as to whether it was normal size or not. Apparently it is supposed to be this big, so thanks for confirmation. It had been quite a few versions back since I last activated that feature.

While I had the camera out I wanted to show you the time bar extending right across the screen, as it may have some bearing on why the coverart isn't showing. Perhaps it IS unrelated but in my mind, introducing a new timer display function and then not having the coverart come up as it has on all other versions just seemed like too much of a co-incidence.

I can also tell you that in ATTENDED mode, the coverart will not display until the OSD TEXT box is ticked.

As a test, I removed the existing entry of Wallpaper.bmp from the z6 folder, and ticked the 'SHOW AS WALLPAPER' At Attended button. After pressing play, I looked in the z6 folder and the wallpaper.bmp had not been created. I then stopped playback, ticked the OSD TEXT box, and pressed play. This time the wallpaper.bmp was created and it appeared behind the XX GUI. I also noted that all desktop icons disappeared. I can't recall if this is normal though as I havent used unattended mode in ages.

Is this sounding like an issue with ChangeWP?

Would logs help?

I'm happy to scr*p the new z6 folder and start afresh (again) if you think that helps, but my only concern is that something may be still residing in the registry or in the USERS folder somewhere.

ta,

Russ

Ok Russ. I think that things become a bit more clear for me now; you relate all to the unknown - well, as it seems. :)

I *still* don't know much what to do or how to help. An additional proble, right at this moment is that I can't play anything myself, which prohibits OSD screenshots from this side to show you. But really that will look the same as your ugly characters. Btw, this must be in there for 2 years, now, so on that matter I still can't follow.

That time bar ? give up on it. It is an unfinished project, although overhere it would act strange 1 track per album maybe. And you may recall about yout own ideas about how to set it up differently - I quit right there. Unfinished or undone - the main thing is that it influences sound. Don't use it for that reason alone.

This leaves the *perceived* not showing up of the wallpaper. I would be careful about this. What I at least noticed is that it might take a while before it shows up. Like 1 minute. Unintentional, and possibly W7 Vanilla related, if you use that at all at this time.

What you seem to talk about is some combination with OSD Text and Wallpaper. What I seem to recognize is that you want to use a combination which does not exist (read : can't work), although it is on my todo list for maybe 1.5 years.

What I can tell you, is my settings regarding this :

- Monitor Off : Inactive (hey, gives you some chance to judge)
- Running time OSD : Inactive
- OSD Text : Active

- Don't do anything with Coverart : Inactive
- Show as Wallpaper - Active
- Show Back - Active
- At Attended - Inactive
- Show Mirror Back - Active

So just in case : this combination works. It should for you too.

but

There is one culprit : that interrupt stuff. To me it seems related, or it even will. But with that problem - no sound and no Wallpaper I think. Also - no further response from your side on this (question -> Do you have this all the time).

Sorry for your problems for now, and sorry it is difficult to help out fast this time. On that matter, might you have some juice left for tonight, please try some more. I am here now, but tomorrow not.

Peter


PS : Not ChangeWP related, but I hope you created a fresh folder for 0.9z-6 and did not merge. Well, you just said so (fresh), but this is important I think.

http://www.phasure.com/index.php?topic=1792.msg18265#msg18265

So you are not completely alone on this iterrupt issue. :)

Russ, I found this for you :

http://www.phasure.com/index.php?topic=1180.msg17289#msg17289

... about how the OSD looks like. Nothing changed to that, including the time bar which was pretty much left in the stage where "we" left off there.
I think.

oh ... i didn't realise it was still in progress. OK ... all forgotten :)

That will teach me to quickly scan the release notes on my phone while still in bed half awake, then jump straight to the lounge and play with a new version .. haha.

I shall have a further play tomorrow, and there is certainly no rush in getting this hiccup sorted. I'm sitting here about to head to bed listening to Allan Taylor and he sounds as if he's in the room with me :) I've finished fiddling for the day!

re. that Interrupt Mechanism message (for me), it occurred around the time I was getting AutoHotKey sorted. I had inadvertently left the AutoHK folder intact on the C drive, and somehow, whenever I ALT-X'd to get the GUI up, it was loading up 0.9z-5-2 instead, even after reloading the script. I renamed the old z-5-2 folder and everything sorted itself out. May be unrelated to the Interrupt message, but can't recall anything else I was doing at the time. Hasn't re-occurred (touch wood).

Was just about to hit send and saw last reply from you. Yes, I saw that timer layout here a couple of times initially, but then something "broke" and it's never been the same since. Should have mentioned that .. oops! I can't remember whether it was the first attempt at installing z6 on the tweaked system, or a subsequent install on the plain vanilla system after the restore.

Bon nuit,

Russ

Allright. Thank you for letting me know. And take it easy.

:grazy:

Hi Peter,

Another coverart issue with my machine, plus more important: volume level problem @ unattended.

- At unattended, screen remains black, no coverart/wallpaper during first track. When player jumps
  to second and further tracks wallpaper is generated ok.

- Not able to change volume up or down @ unattended >>> wallpaper not changing/showing correct dB level.

It started with z5-2 now same with z6. I thought it was 'minor bug' not bothered to report. It shows
the same with W7SP1 or 'Vanilla' W7. Now I use W7RTMx64ULT. First install did yesterday, today repeated it,
with full HDD format to avoid any 'old configuration file'. And today managed to get full error message
while before there was only 'OK' confirmation dialog saying "Something is wrong at remote command".
After clicking first message there was another: "Proper initialization FAILED, so further errors will occur"

BTW, volume error exist no matter XXHE settings or SFS value/type.

Thks in adv,
Brgds

Hi Nik,

I'm afraid I need quite some more info than you already so nicely provided. I'll try to get it out from you  :):


Here you say that the latter message followed the former. I don't think this can be correct;
If it were for me, this latter message can happen at the first install - not later. Btw, that this exactly may proove the issue is another thing, but as long as I say that this can't happen, I'll leave it (please) for you to proove the proper sequence of happenings.

If it were so that this "further problems *will* occur" (I think the *'s are in the real message as well), this *will* be your problem. Please consider this seriously.
What happens why you get this message is another thing. But let's first sort out the proper sequence.


For me this is an easy one; your system just doesn't respond to parallel stuff needed, hence will be too busy with the playback itself. It is that simple, although it seems the most hard to guide anyone through the process of getting it right. It might be your luck that it happens to *you*, because the other occasions with the same problem seem unable to help me out in sorting this out. Sounds strange, but I can only (and still maybe) help out when it is clear (and believed) for the subject involved (you) that the culprit will be on your side. Ok, this for (hopefully) later. But to keep in mind : I am not saying at all that I won't be able to solve whatever it is what's happing to you. But I have to know the "what is". It will not be easy ...


FYI : not even a low level format is enough for this. I forgot what you'd needs to *really* get rid of it all. Sorry.
(if important at all !)

- You really must tell me what the screenshot is about. Ok, about a remote command (volume undoubtedly). But you are not playing anything there. That this by itself goes wrong, ok, to solve. But is there importance in the context of your problems (I don't say there won't, but please eloborate then).

Notice : Like I learned from another situation, this would be related to that volume slider buttons having that green colour. Is that always so for this "XX install", or is it a temporary thing somehow ? Also, looking at your screen, more seems to be wrong. It can well be related to that error message I talked about before ...

- What Priority Settings do you use ? Procesor Core Scheme ?


FYI (rather important) : All this tells is that the previous command is still pending. So, you issued another before, got tyred of waiting and tried again. The message now tells you that something is wrong - and it is. So, the knowledge of this is important for you to possibly tackle the problem, but this message by itself is just normal.


Also important : This will not be true. Think merely like : this started at a new XX install, but with even higher chances that it started after freshly installing the OS. For me this is a proven fact, and for you just important info in the leage "ok, so what can I have done differently from before". Also notice that I am not sure this is an explicit thing, meaning that during an install things may happen differently from another time without you being involved. This too seems prooven to me (just from reports of people !). Otoh, please don't think that you can solve it by just trying a couple of times; this would be non-sense.


As I said/implied earlier in this topic - I recognize this. Must be a W7 Vanilla quirk (which I recall from long ago). It looks rather similar as the Volume failing, but is not. It sure is an indication though that the volume will may if the Wallpaper fails. And FIY again : the sowing of the Wallpaper is a very (CPU) heavy internal Windows process. It may need more time than it ever gets. This is why the questions about the prio's are important. Don't start trying other settings; rather just tell me what your settings are regarding this.

There is one other thing which may be important, and this is the folder structure you use; this can be setup so (wrongly) that around all of your albums are scanned to find the Coverart properly; you won't notice this other than that the wrong track data may appear on the back cover of the Wallpaper (this needs the showing of the back.jpg to be shut off, and showing the mirror back to be on). Now things get tricky (or more easy for analysis), because the ChangeWP program involved here, may hold up the changing of the volume (I just made up this one for the first time). To this regard you may let Taskmanager running, and see whether ChangeWP is there all the time when waiting for the volume to change (or even for the first Wallpaper to show up).
When this is the case (ChangeWp is there) we'll see further about how to solve things.

Ok. Far too long story, and as usual I am 100% confident that when you sit down for it, you are the best in remembering sequences of things. Others may not recognize this strange expression (or even strange posting), but Nik will and know I'm right.

:drinks::):drinks:

A-HA !! The missing pieces of the puzzle. Don't you just love it when you forget to do the bleedin' obvious .. doh!!!

All I needed to do was ... WAIT ... a little, and up pops the coverart on the second track. Thanks Nik for the clue and to Peter for indicating there was a lot of CPU activity needed initially; apparently more than previous.

After spending the whole afternoon, reformatting the C drive, then taking copious notes on events sequence, I can now narrow my search to a solution. It may be time to upgrade my faithful 8086 PC ;)

Just now, after reading the above, I had task manager running over the top, and as anticipated, ChangeWP did not appear initially at first track commence, but did appear briefly at subsequent tracks.

I can go to bed tonight comfortable in the knowledge that there's basically nothing amiss from a software point of view, and I'm sure you , Peter, will like that too :)

Cheers for now,

Russ

BTW Peter, the settings you use, that you provided yesterday, (ie. with the OSD TEXT box ticked), always worked fine. Perhaps there was enough of a time window for ChangeWP to sneak in and do its thing while the OSD display is being prepared.

Hi Russ,

As I also said earlier (in the W7 Black Hole topic IIRC), W7 Vanilla is that OS where the internal priorities went wrong. This is nothing much for you as a user to remember, but I have been working months on things to get them right. This one I never did really (that I recall) and I am bothered with it just the same ... Not always a full track, but usually 10 or 20 seconds anyway.
For the volume this doesn't count though, although the base problem will be in the same area (but more general hence not W7 Vanilla related).

Theoretically the showing of the Wallpaper can also need more CPU or something. Or screen related stuff. Anyway, my remarks from back then about the speed of the forum pages (the graphics of them) showing, is again slow as it was back then (when W7 was first about).

Maybe when I dive into this all again "today", I can understand better what is happening. Learned more and such.

Regards,
Peter

I can't even begin to imagine how many hours you've spent on 09Z-6, but we all appreciate the mammoth effort, and it's paid off in spades. The sound is really "smooth" and easy to listen to. Great bass extensive and control, and wonderful clarity in the mids and highs.

I shall spend tomorrow listening rather than tinkering methinks :)

Ánágodziih doleel

Russ

Hi Russ,

Glad it helped solving your puzzle :)

Peter,  :drinks:

Hope log files will help a bit. A/m message poped out first time I started freshly installed/activated XXHE.
Unattended mode purpously, order to observe changes ref missing coverart. Have not experienced coverart missing earlier.
So,
Loaded just one WAV file. Same file was used for initial XXHE installation. While file was playing and w/ black
screen iof coverart I just hit Alt+S. At that moment unusual window and XXHE termination state showed and a/m error.
Made PrintScreeen before dismissing message. Could not capture second error message. Ok, description and settings:

z5  : all OK ref coverart display & vol change @ unattended. OS used W7SP1
z5-2: first version where "Something wrong with remote command" dialog poped up even I make pause 2-3 secs . OS used W7SP1
z6  : installed and run on 'Vanilla W7' only
---
Folder structure is standard one
C:/XXHighEnd/XXHEversion#xx  (presently only #z6 folder created)
C:/XXData
C:/XXGallery
C:/XXIntermed
Music on second HDD
E:/MUSIC/Author [year] - AlbumName/file 01 02 ... structure. 'Folder.jpg' - same dir as files
---
OS: Vanilla W7, no 3rd party drivers except Juli@ sndcrd drivers
XXHE settings*:
KS; eng#4; Special; DevBuf 512; Sch-3; BlwNrm; High; Clock 10ms; DAC24/384; isPhasure; DecodeHDCD;
ShowAsWallpaper; ShowBack; ShowMirrorBack; StopDesktop; StopRemainSvc; StopWasapi; SFS 120; SC; InclGarbage
ToolTips; LogActivities; Q1 512; Q2-3-4 0; Unattended
---
*Not claiming above settings 'best sounding' - goal was testing coverart behavior @ unattended.

Thank you very much for your efforts Nik !

Nou I must look into this ...

Peter

Last night after playing music for around four hours I suddenly had an issue when I attempted to play a high res file ( Dallas Wind Symphony, Crown Imperial). As soon as I hit play the desktop disappeared and then immediately reappeared but with no sound. Made several attempts to get it going, sometimes heard the first note, but then the desktop reappeared and music stopped. Finally my attempts resulted in a "Lower SFS" error message. Lowering the SFS didn't help. I then switched to MC and had the exact same problem. In short, I could get no music in any mode. I then used the minimize OS button to return the OS to original state and then hit it again to return to "Music server" state--thus had two reboots. All worked again--back to SC, SFS 350. I put this report here cause it seems to me that the issue has to do with the "Monitor Off/desktop/wallpaper reappearing" bug.

I had played high res previously and did not have any issues.

Ah, good that that happened;

This is "the" example of eating all the memory there is while Mr Windows wants some more. IOW, I recognize it.

The main subject of this Topic, "Wallpaper Coverart" has been solved for 0.9z-6-1.

bewdy Pete  :veryhappy:

Cheers,

Russ (currently groovin' away to Shota Osabe Piano Trio's "Happy Coat" on FIM label )

Happy to report that all is well here so far with cover art processing under 0.9z-6-1 :)

The 'unattended' running time progress bar also seems to be behaving itself now.

Cheers,

Russ