Last post by boweasel -
Some great suggestions here! Thank you. And yes, j7n, the Wave Editor I've been using is by Abyss Media. I have also downloaded foobar2000, and although it seems like a nice enough player I miss the ability to right click a folder and select 'play using foobar2000. And if I play a file that came into my computer with gaps, foobar recognizes them and plays back the silence (sounds like a stupid sentence, but I'm sure you know what I mean).
I will investigate the 2 products mentioned for removing spaces at the beginning and end of tracks, although as I've already indicated, Audacity seems to work consistently to do just as well.
Last post by boweasel -
When I right-click any of my many music folders in Windows Explorer I'm presented with lots of options. Two of those are 'Play in Winamp' and 'Play using Windows Media Player'. How can I enable that same functionality for foobar2000?
Last post by jazzthieve -
Loving the sqlite idea. I'm doing that already using an ancient wsh script but it's more to store data and display graphs and not for searching. I often wondered why foobar doesn't go the more true database route.
Last post by Peter -
This was actually done as early as 2005 with 0.9 alpha series on Windows XP 64-bit but there were no interesting benefits beyond the potential ability to index larger libraries / load larger playlists - but the performance would still suck due to loading on startup and saving on shutdown.
The main problem with 64-bit build is that no existing component will work. Maintaining separate 64-bit and 32-bit builds of every single component would have created a huge mess, that's why I abandoned the idea.
There are other options for improving large media library search performance at cost of component compatibility, for an example replacing the ancient metadb design with a modern SQLite backend - which would solve slow search, slow startup, slow shutdown and large memory usage.
That said, every flavour of foobar2000 mobile does have a 64-bit compile available and even the experimental Mac version is 64-bit.
You are likely editing and re-saving .MP3 or another lossy format. This involves opening, decoding, then re-encoding the lossy material to a new .MP3. Your "Wave Editor" also likely does not support encoding gapless MP3s, or decoding them, for that matter. So there may not be any gaps on your files to begin with, and your editor is adding them, and possibly destroying the gapless information already encoded into the original files.
Stop re-saving MP3 files, you can't really edit them without losing more information than just the gaps. Save to FLAC, or WavPack, or another lossless format, but try to start with a lossless file to begin with, rather than any MP3 files.
Couldn't boweasel use MP3DirectCut (freeware) to edit the beginning and end of his MP3s without decoding/recoding?