Re: Foobar Ram Disk component interaction
Reply #1 – 2021-04-15 15:50:55
Most of your questions can be answered by testing.The ram disk is in fact using the app memory, so I presume it has the usual 32 bits limitation (?) Obviously.Is there a way to manually flush the ram disk? Using View->Ram-Disk content, then remove allCan it be manually flushed using contextual/main menus? (not opening the ram disk window) No.What happens if it reaches the memory limit? Does it simply crash or stop working without notice? It will stop copying files to Ram-disk and give out error like this:Could not process file "G:\blahblah.flac", reason: bad allocation Files that were succesfully copied to RAM-disk before error remain there and are available for playback.Is this fixed (memory not clearing)? Memory is cleared when removing RAM-Disk content from RAM-disk or when foobar2000 is closed.Are we supposed to send items to ram disk and then send them back to a playlist for playback? Yes.What happens with duplicates entries in the ram disk? Are they copied multiple times or just once (even if the list has multiple times the same track)? If you are trying to send multiple copies of exactly same physical file, it is copied only once. If files are identical but they are different physical copies on HDD, each file is copied to RAM-Disk. If you add new entries of the same file to RAM-disk, it creates new copies of files in RAM even this was exactly same physical file.