Skip to main content

Notice

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.
Topic: Automatic update feature, will fb2k ever support it? (Read 1609 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Automatic update feature, will fb2k ever support it?

AIMP has automatic updates (at least in portable mode, not sure if it's also the case with ordinary installation, haven't tried that), so that we don't have to download the latest installation exe and redo the installation process just to get the latest version of AIMP, you know, like Chrome and Firefox. Any possibility of foobar2000 also getting this feature in the years to come? That would be cool. I realize I may sound like a spoiled brat here, lol, but I find it a bit tedious of having to install fb2k manually every time there's a new version.
Codec enthusiast!

Re: Automatic update feature, will fb2k ever support it?

Reply #1
No.

Use Microsoft Store version of foobar2000 if you want automatic updates. It's slightly delayed compared to normal releases, but you get releases that are more thoroughly tested since you can't revert to an older version.
Microsoft Windows: We can't script here, this is bat country.

Re: Automatic update feature, will fb2k ever support it?

Reply #2
No.

Use Microsoft Store version of foobar2000 if you want automatic updates. It's slightly delayed compared to normal releases, but you get releases that are more thoroughly tested since you can't revert to an older version.
Oh okay. I only run portable installations if it's available as an option, as I don't like screwing around with the registry if it's not necessary, plus I like to just resume running the programs I have installed after a clean install of Windows, by having them installed in a different partition than C: to begin with, so after a clean install of Windows, I don't have to reinstall everything all over again and redo all the settings and so on. Portable installation is awesome and I'm glad that fb2k supports it. Why can't foobar2000 support automatic updates though, for those of us who prefer portable? Is it too complicated code-wise?

I appreciate the quick reply in any case, and btw, please have a look at this other thread I started about two weeks ago, it would be great if you could send out a quick fix for this Android issue:

https://hydrogenaud.io/index.php?topic=119832.0

I understand you're busy and all but this one shouldn't be too much work to solve.
Codec enthusiast!

Re: Automatic update feature, will fb2k ever support it?

Reply #3
I assume you are aware that simply re-running the installation exe on your portable directory updates the files to the newest version without having to reconfigure anything?

Re: Automatic update feature, will fb2k ever support it?

Reply #4
I assume you are aware that simply re-running the installation exe on your portable directory updates the files to the newest version without having to reconfigure anything?
Of course I'm aware of that ;) Still, it would be cooler if I could just start fb2k, get a notice about a new version being available, press yes for an update, let foobar do its thing and then just restart foobar. Again, AIMP can do this in portable mode, so why can't foobar?
Codec enthusiast!

Re: Automatic update feature, will fb2k ever support it?

Reply #5
Again, AIMP can do this in portable mode, so why can't foobar?

I guess it would be possible to implement that but maybe developer just doesn't want to. Simple as that.
Somewhere, there's someone dying in a foreign land
Meanwhile, the world is crying stupidity of man
Tell me why, tell me why

 

Re: Automatic update feature, will fb2k ever support it?

Reply #6
Again, AIMP can do this in portable mode, so why can't foobar?

I guess it would be possible to implement that but maybe developer just doesn't want to. Simple as that.
Peter doesn't have a reason for not wanting to? I assume it's a matter of priority and that Peter thinks it's a low priority feature.
Codec enthusiast!