Skip to main content

Topic: Foobar 1.1.11 Ramdisk plugin problems. Thanks. (Read 4308 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.
  • johnnyz
  • [*]
Foobar 1.1.11 Ramdisk plugin problems. Thanks.
Thanks the Ramdisk plugin ok for lags audio on higher disk active time. but , I test(foobar portable mode) has some problems. please check and fix:

1. Not support cue, when I add or send to ram with (flac and cue)-I also try play on Ram-disk content. show me the error box:
Unable to open item for playback (Unsupported format or corrupted file):
"RAM-Disk:Audio_Test.cue" / index: 2

2.
when i closed the foobar program, Ram-disk content auto remove the song on ram. i known that for release the ram. but hope the option , let user keep the content. and next time open foobar, 'auto' add back the song/music. that may delay the software open. so, has a 'option' let user choice is better.

3.
memory leak. I check the ram-disk not full release back the ram after remove the content or close the problems. please test and check about this.

ramdisk important for me. hope can fix the problems as soon as possible

many thanks the ramdisk plugin again. very nice.

sorry my bad english.
  • Last Edit: 08 February, 2012, 05:01:44 AM by johnnyz

  • johnnyz
  • [*]
Foobar 1.1.11 Ramdisk plugin problems. Thanks.
Reply #1
Sorry Add one:
hope has a option, don't pop up the Ram-disk content windows when send/add track to ram. thanks.

Hope can fix the problems.
  • Last Edit: 10 February, 2012, 02:41:30 PM by db1989

  • johnnyz
  • [*]
Foobar 1.1.11 Ramdisk plugin problems. Thanks.
Reply #2
ANybody can tell me is a bugs or not ? need improve or fix or not ? thanks. hope reply.

  • Forfit
  • [*][*][*][*]
Foobar 1.1.11 Ramdisk plugin problems. Thanks.
Reply #3
Where is the this Ramdisk plugin in Foobar 1.1.11?

  • db1989
  • [*][*][*][*][*]
  • Global Moderator
Foobar 1.1.11 Ramdisk plugin problems. Thanks.
Reply #4
The official components repository is a good place to start; there is a page for foo_ramdisk therein. Or you can read the thread that started it all.