Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
I noticed that if you sort by date, you have 2 components from 2022 (Stereo Convolution DSP and Taskbar Playback Progress Bar). It seems they are also compiled with the wrong FOOBAR2000_TARGET_VERSION like the issue I reported with foo_pd_aac recently.
Last post by Case -
Despite being earlier against this, I have now uploaded hopefully all of the 64-bit conversions I have made of the seemingly abandoned components. The conversions can be found at the bottom of my personal component site here: https://foobar.hyv.fi/.
The external tags were stored in the files you deleted. foobar2000 caches metadata and it will only automatically read the tags from files again if it sees the file has changed. If you want to handle things manually you'll need to manually force foobar to reload info from files. You can for example do that by holding down shift when you right click a file, then choose 'Tagging' -> 'Reload info from file(s)'.
If you had removed the external tags with the component, it would have done the metadata refresh for you. But if there is nothing for it to remove, it will not do anything.
That makes sense, changing the external tags doesn't change the files like it happens with internal tags so foobar sees no reason to reload the files. I tried what you said and it worked, thanks.
Last post by Case -
The external tags were stored in the files you deleted. foobar2000 caches metadata and it will only automatically read the tags from files again if it sees the file has changed. If you want to handle things manually you'll need to manually force foobar to reload info from files. You can for example do that by holding down shift when you right click a file, then choose 'Tagging' -> 'Reload info from file(s)'.
If you had removed the external tags with the component, it would have done the metadata refresh for you. But if there is nothing for it to remove, it will not do anything.
Hi all. I can't wait to use this addon. As a new user to foobar2000, i have encountered an error on loading. i have the 64bit version installed and am receiving this error on launch Failed to load DLL: foo_musical_spectrum.dll Reason: Not a valid Win32 application.
Am i correct in assuming it will only run on the 32bit version? TIA
Last post by aelklirion -
I've got a question about where the external tags are stored cause they're not behaving as I expected: when I use only the SQLite mode (settings I used shown in picture 1), add external tags to some files, and then delete the external-tags.db file that is created in AppData\Roaming\foobar2000-v2, the external tags are still on the files. Same thing with the folder tags mode (picture 2): when I delete the folder.tag file the external tags remain. Shift right-clicking and selecting Remove external tags also doesn't revert the files to their pre-external tags state. I have confirmed that the audio files are not altered so I didn't accidentally change their internal tags, so why aren't the external tags removed when I delete the SQLite database file or the .tag files? Where is foobar getting them from? Does External Tags have a cache somewhere I should delete?
Last post by Case -
Speed comparison. The source file is a CD image, stereo, 16 bps, 44100 Hz. Duration reported by foobar2000: 55:41.150 (147 344 700 samples). Conversion run untimed first so the source file gets cached in memory. C: is a fast NVMe SSD too, so not a bottleneck.
$ del C:\temp\out.wav & timer64 ffmpeg -i c:\temp\image.wav -af "ardftsrc=48000,atrim=start=0" -acodec pcm_f32le c:\temp\out.wav - timed conversion ran three times, fastest run took 2.027 seconds. Average 2.065 s - the conversion speed for the fastest run is 1648x realtime
$ del C:\temp\out.wav & timer64 ffmpeg7 -i c:\temp\image.wav -af "aresample=48000:resampler=soxr" -acodec pcm_f32le c:\temp\out.wav - timed conversion ran three times, fastest run took 1.711 seconds. Average 1.711 s - the conversion speed for the fastest run is 1953x realtime
The ardftsrc produced output length is still incorrect: 55:41.153 (160 375 360 samples) Sox length is correct: 55:41.150 (160 375 184 samples) 147 344 700 / 44100 * 48000 = 160 375 183,67..., which rounds up to 160 375 184
Last post by Case -
If you only want to do that seldomly, you could use the built-in ABX component for that. It's meant for doing double blind listening tests, but it allows switching seamlessly between two tracks.
Last post by Case -
It's not enough. The string in preferences is checked for each track and if running the query against current track returns true value, the entire track is skipped.
Right click an MP3 file in foobar2000, click 'Properties', then click '+ add new'. Enter the partial skip information here and save the changes with 'OK'. Below is a screenshot showing what it will look like. Notice that I left the hours away from the timestamp, it's not necessary to type them if they aren't needed.