121–130 of 179 posts
Earlier quoted context omitted.
Eh? I don't think there are any issue with finding download section on foobar homepage and installer link.
You're probably right but in general it's a problem with downloading windows software
http://www.foobar2000.org/ however is a pretty straight forward site.
Earlier quoted context omitted.
Maybe it's because you're on a high speed SSD. Spinning rust suffers greatly from Windows 10's bloat.
No offense intended by who in their right mind would boot off spinning rust in 2020? You can get a brand new 240GB SSD for $30 and a 1TB for $90. That’s ignoring the used market where you can get a solid used Intel for $10. If you need more storage buy a spinning disk for bulk storage - even if it’s a laptop, usb-3.1 is faster than the drive.
Earlier quoted context omitted.
choco install -y foobar2000
Are people actually using chocolately? I never could get over the way they get you to install it with the equivalent of piping curl into. Or the way it kept advertising the paid version, which is really disconcerting when something has become effectively the only way to manage what software you have installed (or will be eventually).
Winamp for Windows 10 is called Foobar.
Wait, winamp didn't work on Windows 10? Why is that? I've been using it -version 2.91- in Windows 7 without problems (in fact I'm currently listening to it right now). I thought that it was solidly programmed and that it could work with any Windows as long as the underlying OS API was compatible. Is that not the case? EDIT: Ok, after reading the comments, it seems that Winamp does indeed work in W10. So I guess that…
I use version v5.666 Build 3516 everyday on Windows 10 and it works perfectly... But I'm happy to see Winamp is going to be officially supported!
I had used Winamp since its original release, but when development on it seemed to die off and it looked like it was becoming abandonware, I switched to MusicBee, which I thoroughly love. Maybe there's better software out there, but I've yet to find it.
Anyone remember Songbird?
I remember the XULRunner meetups with them, in Mozilla HQ where the Moz people were basically saying:
- OK, our product is Firefox. We focus on fixing bugs that affect Firefox, so if the bug in XULRunner doesn't affect it you're on your own. Feel free to send a patch.
- Yeah we did that, the patch have been sitting in Bugzilla for 2 years
- ... shrug
Anyway even with full support of Mozilla they probably wouldn't have survived to iTunes+iPod, but clearly using a technology that the vendor has no interest in didn't help them.
Earlier quoted context omitted.
Noting that I don't use winamp, and haven't since I found foobar2000 back in ~2004... I would not even notice that as an issue. The last time I had a .WAV I needed to play was in Windows 95.
Yeah there is little reason to use WAV anymore. Admittedly, I still use it frequently when I am too lazy to convert my CD rips to FLAC. (Another fellow FB2k user here.)
All other image formats get parsed to recreate either an identical or approximate bitmap as would have been encoded into the BMP file, but usually with more features or smaller size, or both.
All other audio formats get parsed to recreate either an identical or approximate audiowave as would have been encoded into the WAV file, but usually with more features or smaller size, or both.
Earlier quoted context omitted.
choco install -y foobar2000
Are people actually using chocolately? I never could get over the way they get you to install it with the equivalent of piping curl into. Or the way it kept advertising the paid version, which is really disconcerting when something has become effectively the only way to manage what software you have installed (or will be eventually).
We use it via the ChocolateyGet PS provider. I.e. installing most software (but not all) is now just 'Find-Package foobar' and 'Install-Package winamp' etc.
Winamp 5.8 Beta was indeed first leaked and then officially released over at the official website https://www.winamp.com/
Among other things, it has better support for Windows 10.
And this happened two years ago.