Please be aware that much of the software linked to or mentioned on this forum is niche and therefore infrequently downloaded. Lots of anti-virus scanners and so-called malware detectors like to flag infrequently downloaded software as bad until it is either downloaded enough times, or its developer actually bothers with getting each individual release allow listed by every single AV vendor. You can do many people a great favor when encountering such a "problem" example by submitting them to your AV vendor for examination. For almost everything on this forum, it is a false positive.
I have a decent collection of live tracks from a few of my favorite bands. Since they're all identically tagged with regard to artist and track, I want to have one copy of the lyrics which applies to all of those tracks. So, a very simple test case: The Allman Brothers Band - Statesboro Blues (Live). I've got quite a few of those, all with identical artist and title tags.
In my lyric searching preferences, artist is simply %artist%, and title %title%. "No preference" selected for type of lyric. Only local file and associations are enabled. Under lyric saving, automatic save is enabled, the filename format is %artist%\%title% and the custom directory is T:\Music\Lyrics. In the local file search properties, I have box boxes checked, with custom filename format of %artist%\%title% and custom search path of T:\Music\Lyrics\
The file exists, "T:\Music\Lyrics\The Allman Brothers Band\Statesboro Blues (Live).txt" is ready to go. It just does not read the file.
Curiously, I can play a copy of the song and edit the lyrics in, and it'll save that file for me, and in the right directory. And it'll even create the file association *for that one track*, and lyrics will show each time I come back to it. But if I play any of the other copies of the song I have, it doesn't find the file. The intent would obviously not be to have to manually edit lyrics for each copy of Statesboro Blues, rather for it to pull that file out of T:\Music\Lyrics\ each time that artist and song is played.
One last thing, just to drive home that I'm sure it's at least looking in the right location for a file. I can play 1 version of Statesboro, and edit in the right lyrics and it creates the text file. I play version 2, it finds nothing, so I edit in an entirely different (wrong) lyric. It updates the same text file. I then go back to play version 1 again, and it will now display the lyrics from version 2. Therefore, I know it's looking at that file once the file association is made, I just can't get it to find the file on its own.
Long winded post I know, but I wanted to be thorough? Any help please?
Basically, to illustrate the issue again:
#1 - This is the Album List component, with the view set to "by folder structure" (not visible). So far so good. Sorting is correct there as "Florence" < "Florence (Remixes)".
#2 - This is the Playlist View component, showing the Library Viewer Selection build-in playlist. It is grouped using one of the built-in groups, "By artist/date/album".
#3 - Library Viewer Selection showing the sorting. Obviously the groups are sorted incorrectly as once again "Florence" < "Florence (Remixes)".
Here's what's even more annoying:
Using the built-in "Album/artist" column (which I presume has a pattern of "%album% - %artist%"), if you sort using that column, the group sorting is correct.
Realistically it should be possible to have the groups sort correctly by using the group pattern.
Per Yirkha, "The Album List sorts the entries by the whole pattern when putting them to a playlist".
Using the terminology from Microsoft's site regarding tree views: sounds like the remedy is for the Album List to sort sort not by the whole pattern, which includes the pipes (to separate containers in the tree view) that causes the issue, but rather by the container nodes hierarchy first, then the leaf nodes. A nice and easy recursive node sort.
Quoteaking a 320 kbps MP3 and converting it to 256 KBPS AAC would not result in quality loss because the AAC conversion wouldn’t redundantly remove high and low frequencies again and the algorithm wouldn’t need to compress more than it already has. That sounds very wrong to me.It's quite as simple as throwing-away frequencies you (hopefully) can't hear.
With MP3 "damage" accumulates with every generation of re-compression, and MP3 is actually one of the worst formats for this! AAC is pretty-much immune from accumulated damage.
But, I don't know if transcoding from MP3 to AAC is better than compressing MP3 twice... I don't know if you get the best of both or the worst of both.
Nine different codecs 100-pass recompression test
Thanks a lot for that link. I’d be interested to see it done on more passages, but of course I should be the one to do it then. I had no idea about AAC being immune to multiple transcodes. It’s little consequence to me as when I’m listening wireless, high fidelity isn’t the point anyways but it seems that it’s likely that it may not make a difference anyways. MP3 to AAC is I’ll bet how most people who listen to Bluetooth audio on Apple devices do it.
A better question is this: If you have a track that's mixed, mastered, etc, and issued onto a commercial CD. You (to simplify *everything*) have to either increase the whole track by +3db, or decrease it by -3db, then save that in place of the original, and that's it, that's what you're left with...
Which of these two options could do more harm to the integrity, and quality, of the original file?
That is the question I was addressing above. To reiterate, the question doesn't make a lot of sense, but neither is better or worse, it just depends what level you want the final file to be at.
In Adobe Audition 3 I use amplitude statistics to get the average RMS power in the -15dB to -16dB range for consistent levels.