XXHighEnd

Hi Peter. Whenever I am in my "classiscal" directory and try to navigate out of that directory via the "arrow pointer" at the top left of the scroll bar of the embedded library explorer window (see screen shot cause, well, a picture is worth a thousand words!), I get an "xx has stopped working" error. This also happens if I try to leave that directory by typing an artist's name with the keyboard. It mostly happens just with this directory. My general structure is: Music/Artist/ Album; classical may have several intervening folders: (Music/classical/composer/artist/album) as shown in the screen shot. If I don't use the "arrow pointer" and just scroll to an album outside of the classical directory I'm usually okay. Is this caused by too many subdirectories? If so, is it possible to adjust things so that that many subdirectories can be made to work?

Difficult to say, but certainly not too many sub folders or something ...

If that "Folder" file which is showing doesn't have an extension, please rename it to Folder.jpg and see whether it makes a difference.

With such a structure, I can imagine that things are not in "balance" somehow, and at (me) working through the structure, unexpected things happen. So, in general there is a deepest level of where the track data is, and the only thing allowed under that (deeper again) is coverart folders. Thus, suppose there's track data in your Anne-Sophie folder (I can't see that), things will go wrong because you also have album folders in that same folder.
Otherwise I really don't know.

Since you know where you have this issue, and it seems to be at one place only (?), it would be great if you can find yourself what causes this. After that I can adjust the program to that, unless you do something "illegal" (like the before example with track data and album folders mixed).

I know, not much helpful, apart maybe from the fact that what I see is just allowed.


I don't think that can happen (the "leaving"). So, that it goes wrong I sure believe, but this must always be something in the chosen folder folder itself. Now, if you recognize this is the same problem, it may be easier to drill down to the folder having the issue (if one (only) at all).
So, if you see E:\Music I\Classical\Bach\ at the bottom, and you type "best of", only the \Bach\ structure (all the way down) will be examined, and not e.g. \Antonio Vivaldi\. Unless :
Unless you mean you type c:\Music I\Chuck at the bottom, and force to "leave" the Bach structure by this means. But if so, does this go wrong only at clicking Search ? or also without clicking Search ?
I hope I am clear a bit ...

I hope you can find what causes this !
Peter


PS: When does that cyan color at the top of the form emerge ? It indicates somethingis wrong (it should be transparent).

Will work on the file issue and let you know. Regarding that cyan bar, that happened when I took the screen shot; cyan has never shown up with xx open on the desktop. However; in unattended, every once in a while, that same bar stays on the top of the desktop screen after the GUI disappears. Its color, to me, is gray. Its so infrequent that I haven't posted about it.

The file extension, .jpg, was hidden by Windows 7 default "folder view" for common file extensions, so that's not an issue.


There is nothing in the Anne-Sophie folder. That folder is the "Artist" folder created when I ripped the cd with dbpoweramp.


I'm not sure what you mean here. Whenever I rip a cd, I secure rip with dbpoweramp. The cover art automatically is placed in the folder with the tracks. Is there another way to do this?



That's not the way it works here. If I just type on the keyboard "Bob" from the directory as shown below, it automatically leaves all four subdirectories (Johann/Ann-Sohie/Bach/ and Classical) and goes to the Bob Dylan Directory. I don't type anything in the search box. That's the way I've been doing it from the beginning.

Never mind, it's okay (or should be anyway).


Aha, so you just let Windows search in the tree for your typed "bob", right ?
I now see that this just works (never knew it).
Ok, if you type character for character (not all that fast, but fast enough to let it search for "bo" instead of "Olivia"), can't you where (at which character) it goes wrong ? And next find what it can't cope with ? Of course if I try it overhere, all goes allright.

Difficult, because it is data related !