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: :'( After 10ys of use I have to leave Foobar because "run out of memory"... (Read 3471 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

:'( After 10ys of use I have to leave Foobar because "run out of memory"...

Dear @Peter and Dev Team ALL,
I thank you so much for the 10 years during which I could enjoy your wonderful Foobar player.
It was the summer of 2011 when I start playing with it and after having evaluated and used also other products, I finally selected it.
Still today, for my type of use, Foobar2000 would be the best if it didn't run out of memory due to my large audio library.
Over these 10ys I went out of memory other times, and I all the times found a "work-around". This time I couldn't.
So, ... I am enforced to switch to another solution...
I already found 2 players that are capable to manage my large library, however it will take years for getting acquainted with...
So, please, if you will be able to change the current Album List subsystem and avoid so the "out of memory" problem, I will be very happy to get back.
If / when it will happen, kindly notify me.
All the best
Andrea

Re: :'( After 10ys of use I have to leave Foobar because "run out of memory"...

Reply #1
k, bye

Re: :'( After 10ys of use I have to leave Foobar because "run out of memory"...

Reply #2
I have a collection of over 18000 tracks across a lot of albums, 263GB of files, and it manages to fit in memory on my Linux server machine, which only has 8GB of RAM, and the app is not being forced to use Large Address Aware mode. So it's fitting in under 400MB of RAM actually. So what does your huge library have?

Re: :'( After 10ys of use I have to leave Foobar because "run out of memory"...

Reply #3
Bye.

Re: :'( After 10ys of use I have to leave Foobar because "run out of memory"...

Reply #4
So what does your huge library have?

IIRC from previous threads, they have multiple hundreds of thousands of tracks. All legally acquired I'm sure. :P



Re: :'( After 10ys of use I have to leave Foobar because "run out of memory"...

Reply #7
I have 900GB
This is not relevant for the memory usage of foobar2000. Relevant is how many tracks are in the media library, how many tracks are in the playlists and how much text is used in the tags, which are not excluded in LargeFieldsConfig.txt, of all these tracks.
/over 71k audio files
This normally far from becoming problematic.
Can't you just add more RAM?
This will not help as foobar2000 is a 32-bit application and can therefore use only a maximum of about 3.5 to 3.6GB of memory.
foobar2000 is not a database program anyway,
But it is using a database aka media library.
it's a player.
This might be the main functionality, but it is not the only functionality and I wouldn't use it without the database functionality.

Re: :'( After 10ys of use I have to leave Foobar because "run out of memory"...

Reply #8
Thanks for letting us know about your situation.
foobar2000 v2.0 will be both 64-bit and capable of handling extremely large libraries without overkill memory use.
We are the bork. Your software bugs will be added to our own. Resistance is futile.

Re: :'( After 10ys of use I have to leave Foobar because "run out of memory"...

Reply #9
Thanks for letting us know about your situation.
foobar2000 v2.0 will be both 64-bit and capable of handling extremely large libraries without overkill memory use.

Fantastic news Peter!

Re: :'( After 10ys of use I have to leave Foobar because "run out of memory"...

Reply #10
foobar2000 v2.0 will be both 64-bit and capable of handling extremely large libraries without overkill memory use.

does that mean all the add on components/plugins will have to be re-written or updated to work with the 64bit version?

i just ask because i use an oddball one that probably will never be updated but still works with the current version.

Re: :'( After 10ys of use I have to leave Foobar because "run out of memory"...

Reply #11
i use an oddball one that probably will never be updated but still works with the current version.

... pry foo_facets from my cold dead hands.
Last two months' worth of foobar2000.org ad revenue has been donated to support war refugees from Ukraine: https://www.foobar2000.org/

Re: :'( After 10ys of use I have to leave Foobar because "run out of memory"...

Reply #12
foo_facets could be replaced, assuming someone manages to code a suitable replacement for it. It just takes the effort to do it right.

Re: :'( After 10ys of use I have to leave Foobar because "run out of memory"...

Reply #13
An old post from Peter in a previous thread...

https://hydrogenaud.io/index.php?topic=115706.msg954701#msg954701

Quote
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.

Is this happening? How much work will it be to update existing components?

Re: :'( After 10ys of use I have to leave Foobar because "run out of memory"...

Reply #14
Since Peter is ok with jarsonicing I can reply that it is happening. Everything from configuration to database is SQLite backed. Old components also work in current 32-bit version as Peter was too nice to break the APIs. But if a component performs heavy titleformatting it may need some implementation changes for performance reasons.

Re: :'( After 10ys of use I have to leave Foobar because "run out of memory"...

Reply #15
Since Peter is ok with jarsonicing I can reply that it is happening. Everything from configuration to database is SQLite backed. Old components also work in current 32-bit version as Peter was too nice to break the APIs. But if a component performs heavy titleformatting it may need some implementation changes for performance reasons.
How nice is that!

Re: :'( After 10ys of use I have to leave Foobar because "run out of memory"...

Reply #16
foo_facets could be replaced, assuming someone manages to code a suitable replacement for it. It just takes the effort to do it right.
Facets so far is the single most important component for me...

Re: :'( After 10ys of use I have to leave Foobar because "run out of memory"...

Reply #17
Well, this is great news. Personally, I would not bother to maintain a 32bit code now. Kill that off, kill off all the old components. No place for legacy

Re: :'( After 10ys of use I have to leave Foobar because "run out of memory"...

Reply #18
I also have a +70K library and caching some tags (like chromaprint raw fingerprints) totally breaks the player due to memory overkill use, so that's a welcomed change which opens new possibilities (already reached memory limits for some advanced scripts in SMP).

Don't get the point of discussing the legal status of the user's library or if the program is a database or a player (it has both so...); didn't know foobar was a law enforcement software ::)


Re: :'( After 10ys of use I have to leave Foobar because "run out of memory"...

Reply #20
Thanks for letting us know about your situation.
foobar2000 v2.0 will be both 64-bit and capable of handling extremely large libraries without overkill memory use.

alright! I can't wait till you get a beta out @Peter..
I am so excited!!
as long as the following vgm components are either included right out of the box like with your android version or recompiled for 64bit..
I will be good to go..

must have vgm(video game music) components:
SNES, Genesis, etc - https://www.foobar2000.org/components/view/foo_gep
Sony PlayStation 1 & 2  - https://www.foobar2000.org/components/view/foo_psf    
Sega Saturn          - https://www.foobar2000.org/components/view/foo_input_ht 


optional but kinda wanted in the v2.0 of FB2K:
----
Kode54's  midi support - https://www.foobar2000.org/components/view/foo_midi

https://www.foobar2000.org/components/view/foo_openmpt54

vgmstream plugin but Kode54 removed it from the official component repository.

Feature Watcher still works, even though no update since its release in 2014
 - https://www.foobar2000.org/components/view/foo_whatsnew

https://www.foobar2000.org/components/view/foo_input_qsf
https://www.foobar2000.org/components/view/foo_input_usf
----
https://www.foobar2000.org/components/view/foo_input_qsf

the only other real issue is being able to install and update over the 32bit version seamlessly  ^_^
by moving old 32bit components into a backup folder or something...

thx so much Kode54 for your vgm components they mean so much to me...
and help me get going...

It is quite exciting to hear about fb2k 2.0. will the 2.0 version take into account windows 11 design principles? Like this: (https://www.reddit.com/r/foobar2000/comments/otj3z3/what_if_foobar2000_was_made_using_windows_11/)
I happen to like Foobar2000's GUI just the way it is perfect as is...
No need to reinvent this wheel..  lol ;)

Re: :'( After 10ys of use I have to leave Foobar because "run out of memory"...

Reply #21
Thanks for letting us know about your situation.
foobar2000 v2.0 will be both 64-bit and capable of handling extremely large libraries without overkill memory use.
Don't forget to notify Andrea when you get this done, it's very important we get her back before it's too late.

Re: :'( After 10ys of use I have to leave Foobar because "run out of memory"...

Reply #22
Thanks for letting us know about your situation.
foobar2000 v2.0 will be both 64-bit and capable of handling extremely large libraries without overkill memory use.

Excited to see what's coming for v2.0!

I really hope to see, one day, some sort of client/server mode, or some sort of way to integrate with network DAC's. I'm increasingly wanting to play music back on my hi-fi system with my dedicated HTPC, but have the full playback control, library, statistics and user interface of foobar2000. A linux based foobar2000 daemon that can be run on a headless server and controlled via a desktop front end would be the bee's knees!

Also, some sort of integration between the desktop and android app would be nice. Android app , by the way, is extremely under-rated. It's nearly perfect.

edit: a good example of what I'm talking about would be the Roon Optimized Core Kit. I really don't care for roon as a front end, but the client/server model is very useful and flexible.
https://help.roonlabs.com/portal/en/kb/articles/roon-optimized-core-kit

 

Re: :'( After 10ys of use I have to leave Foobar because "run out of memory"...

Reply #23
Also, some sort of integration between the desktop and android app would be nice.
Yeah, integration with Android app would be awesome. My dream is just connect my mobile foobar2000 to desktop foobar2000 and listen to the desktop music library. My computer is always on and has static external IP address, so it could be like a personal music cloud where desktop foobar2000 streams Opus 128kbps to its mobile counterpart =)

Re: :'( After 10ys of use I have to leave Foobar because "run out of memory"...

Reply #24
Thanks for letting us know about your situation.
foobar2000 v2.0 will be both 64-bit and capable of handling extremely large libraries without overkill memory use.
YES THANK YOU
I have been growing increasingly frustrated with using plugins through foobar. The 32bit RAM limitation has been quite inconvenient. I'm so glad 64 bit is in the works, especially since the last mention I saw of it was basically "no reason to make the switch"