Hi, I'm using v0.9.4 beta 3 and must say, Foobar2000 Rocks! Great work guys. ;-)

That said, I noticed a little bug. You can attempt to convert a streaming audio source to .wav, and it appears to work, but records nothing. The stream I tried this with was: http://195.225.8.195:7090/

Obviously it would be great if we had the ability to record live streams, but if that's going to be too difficult to implement then some measure should be put in place to alert the user that this won't work (or just disallow trying to convert a stream to a file.) This is important because a person could spend hours thinking they are "recording" something, when in fact nothing was recorded.

Regards,
Mark

Since the latest Foobar version is 0.9.4.2 I suggest you update first, it may be fixed already.

It's always better to capture a stream in it's native format rather than recording the decoded (WAV) audio. The stream you reference is 64kbps MP3 PRO. You would be wasting many bit and bytes by storing the WAV file. There are many programs that do stream captures. I use Net Transport, and recommend it highly.

BTW, does foobar handle MP3PRO ok? I looked at it years ago and decided that it had nothing to offer over Winamp. I should probably look again.

are you sure? wav is a lossless format meaning that there should be 0 loss when converting from one format to wav. unless the decoder/writer does something to the wav, the data should be the same bit by bit.

I don't actually know if foobar allows stream ripping any more.


Aside from rounding errors/differences, I suppose that this is true. But this is not what the poster was saying: instead, they were asking (perfectly validly): why use more space when you could instead capture the raw ("native") stream? Save space and keep the file in the original format. A win/win!

my mistake. i misread his post and i believed that by wasting bits and bytes , he was refering to the quality and not the filesize.

No worries; we're both right, really