jeremyb

Well I set the album title to something consistent that represents the box set, then have a disk or group for each 'album' in the set, each with their own sub-header.

Sorry no, that's not likely for some time at least.

Latest version of Muso supports inline conversion of ALAC (Apple Lossless) to .aiff on pushing to HQPlayer - may interest a few users here.

Muso treats tracks independently regardless of the album they are in, when pushing tracks to HQPlayer. So the behaviour you are seeing must be something HQPlayer is doing.

I seem to have later versions. Could you upgrade? Also, have you done anything to disable javascript on either? If so please re-enable. As with the other post on this thread, could I ask you to register on the Muso forums and continue discussing this issue there? Otherwise it becomes very difficult to keep up to date with issues. musoware forums • Index page After registering you'll need to post in the Introductions thread before you can start a topic.

I'll do my best! But as there are a few issues on the go in this thread, could I ask you to register on the Muso forums and post the details there? musoware forums • Index page After registering you'll need to post in the Introductions thread before you can start a topic.

NB. Here's how to turn diagnostics on (see the bug icon), and where it goes:

Yeah that's a bit freaky. Your blank hierarchy looks odd too - what shows if you click on Gallery? Can you let me know your versions of Edge and IE on your W10 environment - though I don't see IE on my menu I can invoke it from edge by choosing the menu option "Open with Internet Explorer" from any page.

I haven't been able to reproduce this. Could you post a similar screenshot? Please send me a muso2.log file too.

I have tested it on W10 without issue, that's why I thought perhaps the scroll issue was with the web remote, if you are not then you are using the full version of Muso - so I'll test it again - ALL screens fail to show a scroll-bar?

This is with remote, using an edge browser? musoware forums • View topic - Remote on Windows 10 Edge Browser

Please log specific bugs and make suggestions for enhancements on the Muso forum: musoware forums • Index page

Sorry not to get back to you on this. I think the delay is cause by the network traffic required to read the file tags. I had a similar issue today - it was taking up to 20 SECONDS per file (standard mp3 files) to read the tags for a new album. Network connection seemed to be OK, wireless rather than wired but the signal seemed to be strong. When all else failed I rebooted and this magically went down to under 2 seconds per file.

The difference in artist count is that the hierarchy view only shows artists who have albums in their name (i.e. they are a "titled" artist). The total artist count will include other artists that have contributed to compilations, but might not have albums in their own name.

I would need a diagnostic log (muso2.log) file to investigate the slowness of the import - to start one click on the bug icon top right to make it go red, run an import, then click it again to close it - then send me the file C:\Users\Public\Music\muso\muso2.log. Are you saying in other instances muso simply isn't importing media from some folders? The tag file scanner can't read tags from DFF though can from DSF, so yes either remove the DFF or manually edit the db for those entries.