Yeah, currently the script only queries the last 1000 songs of a given artist (that'd be 5 last.fm requests) to avoid hammering last.fm and getting banned. If you've listened to an artist a lot more than 1000 times (I see 6k+ plays of Fear, and Loathing for you) then it won't get most of them.
If I get around to making the last.fm queries happen in a separate thread I can probably delay them and this won't be a problem. I haven't had much time to work on this lately though.
Last post by Case -
Sounds like you have true peak scanning enabled. It works by upsampling to higher sampling frequency so that actual waveform shape going to the DAC can be estimated. And the info line is a new addition introduced with the resampler service changes.
Last post by Case -
If you are brave you can test my Renamer component that allows defining custom rules for reserved character replacement. It's not as polished as File Operations and all its configuration has to be pre-set on the preferences page:
Note that this doesn't move files from one directory to another, it actually renames all the paths where needed.
The tool can be found under Utilities context menu. It will first show a preview of the results with all changes listed at the top and empty target names for tracks where there's nothing to do. The actual renaming is running without progress bar and can take a while if you have many playlists. It has to do some extra work to keep track of playlist changes due to its dir-by-dir operation.
Last post by davideleo -
I always tag new music before moving the files to the indexed library directory. I have a special "upload" playlist that I use for uploading non indexed music and I usually listen to it while tagging. Since I have my preferences set to resume playback on start-up, if by chance foobar2000 crashes after I moved the content of the upload playlist and before saving configuration, foobar2000 will get stuck forever on the next startup, stubbornly trying to play files that have been moved. There is no way to stop playback in this event, because foobar2000 becomes totally unresponsive. The only way I can exit this loop is by painfully bringing back to its previous location the playing file, which often means a whole artist-album folder and subfolder structure (provided folder names have not been changed in the meantime), stop playback and erase the upload playlist content before moving the file again to its final destination in the indexed library. Is there a way to prevent this, other than changing the resume playback option in the preferences? Is it possible, for example, to tell foobar2000 it should stop playback if the file is not found?
P.S. Actually this happens also without foobar2000 crashing, if I simply forget to erase the playlist after moving the files and distractedly try to play it.
Last post by Maurits -
It may feel counter-intuitive but it is much easier to encode lossless than lossy. The challenge is to encode to much smaller sizes than lossless could ever achieve and make it still sound good. That is why your MP3 encoder takes longer, it's much harder.
Last post by certaindamagedlemon -
In EAC, the FLAC encoding seems unusually fast for me. It rips to WAV normally, then in the FLAC.exe window it only takes 3 seconds for a 3 minute track. It takes about 5 times longer for LAME MP3. I'm not sure if that's normal.