picmixer
Jul 21 2003, 05:00
QUOTE(zZzZzZz @ Jul 17 2003, 02:23 AM)
Beta22 posted.
Unfortunately I can't do anything about "buzzing" because it simply doesn't happen here (tried on different machines).
Found out something new about this issue today. Might be a windows issue after all. Somehow the settings in the windows Advanced Audio properties seem to have quite some influence here.
Here is what I found sonsidering the hardware acceleration settings in both :B and windows.
Foobar (HA enabled) - Windows (HA set to full) - no cracking noise when pressing pause.
Foobar (HA enabled) - Windows (HA less then full or off) - cracking
Foobar (HA disabled) - Windows (HA enabled) - cracking
Foobar (disabled) - Windows (disabled) - no cracking
Tried this a few times over again and seem to get consistent results. Although sometimes it seems to be necessary to restart :B and to reactivate the SixPack driver in the preferences to get exactly those results.
AstralStorm
Jul 22 2003, 02:32
Foobar2000 0.7b22 doesn't buffer up to the threshold
when it gets an underrun while receiving MP3 stream.
It just plays the incoming data...
Mike Giacomelli
Jul 22 2003, 17:17
QUOTE(kode54 @ Jul 19 2003, 10:07 PM)
Share one of these crashing files with me and I'll try to fix it. (PM link or something.)
Thanks but so far I haven't been able to duplicate it after the first few times. I will keep trying.
complex
Jul 24 2003, 08:33
One thing I'd like...
In the playlist search window, show all the files currently in the playlist (narrowing it as you type a search string), and allow the up/down arrow keys to scroll through the list without needing to first tab into the results area. Basically, function just like Winamp's jump feature.
Otherwise, I have no problems or annoyances. Keep up the great work!
Edit: actually, one other minor thing... Giving focus back to another window works when foobar is minimized to the system tray - but if it's open normally, after closing the playlist search window, focus goes to the main foobar window regardless of where it was before.
Btw..previus bettas are ok with it...but this one b22 cant play wma???Wmp9 plays it ok...and fbar has played it before??
Curi0us_George
Jul 24 2003, 10:55
QUOTE(zver @ Jul 24 2003, 08:12 AM)
Btw..previus bettas are ok with it...but this one b22 cant play wma???Wmp9 plays it ok...and fbar has played it before??
foobar has never supported wma. You must have had the 3rd party wma plugin. You could ask the author to support 0.7.
kode54
Jul 24 2003, 11:00
Beta23 uploaded. Component compatibility was broken so all components require recompiling.
The console window is popping up for almost every new song that is being played since beta23.
Messages are:
WARNING (foo_input_std) : too many frames
WARNING (foo_input_std) : mpeg stream error at 6570 bytes, attempting resync
This wasn't the case in previous versions
thetrivialstuff
Jul 24 2003, 15:15
I'd like some way of dealing with those (rare) mp3's with incorrect CRC's -- foobar2000 seems to completely ignore all CRC's (which is good, cuz it means those messed files play instead of being silence like they do with Winamp|MAD)... maybe a report of them in the console would be good? The only reason I want this is because for some reason Nero does use CRC's to check files before burning, but doesn't warn you of them (and I just made a CD with a blank track because of it). Actually, what'd be really nice is if the masstagger had an option for either recalculating or removing CRC data :)
PS: Also want presets in the title formatting department please :)
foosion
Jul 24 2003, 15:21
A problem with the installer on Win98: the ANSI version of utf8api.dll in installer seems to be broken. Foobar crashes when starting (access violation). When I compile the ANSI version from the SDK and put that one into the Foobar2000 folder, everything works fine.
Buzzing on pause should be workedaround now (someone confirm, I can't reproduce).
Gapless MP3 playback is back, apparently plain "lame.exe <file.wav>" stores correct values, it only breaks with some frontends. You can use new "fix mp3 header" rightclick to enter correct length in samples (either guess or read from .cue) and make any MP3 file play gaplessly. "Fix mp3 header" rightclick also fixes length/seeking info on VBR files (like all those "vbrfix" tools do).
MyAdviceIha
Jul 24 2003, 19:08
Not sure if this is intended behavior or not.
I just downloaded beta 25 and added several folders that contained 2 or more sub-directories. Such as the albums Mellon Collie and The Infinite Sadness and Machina II by The Smashing Pumpkins.
On older betas (ie beta 22 and before), when adding a folder that has two or more sub-directories, it would load the tracks in the order in wich they are listed. And example would be that all the tracks in the first folder would be listed and then all tracks in the second folder would be listed. That way all files play thru from track 1 on CD1 to the last track of CD 2.
However, with beta 25 it lists track 1 from CD1 then track 1 from CD2. Then track 2 from CD1 then track 2 from CD2. I can go to Playback > Sort > Sort by File Path and it will correct the current playlist. When another folder is added it list the files as just stated, and to correct them so they are displayed correctly, I have to go back to the Sort option.
Folders are named this way:
04 - MCIS > 01 - CD1 and 02 - CD2
09 - Machina II > 01 - CD1 and 02 - CD2
*wipes brow* Sorry for the long message. I explained it as simply as possible.
System setup: windows xp sp1. creative sound blaster audio card. nvidia video card. no dsps applied in foobar. flac files being used.
QUOTE(MyAdviceIha @ Jul 25 2003, 04:08 AM)
Not sure if this is intended behavior or not.
I just downloaded beta 25 and added several folders that contained 2 or more sub-directories. Such as the albums Mellon Collie and The Infinite Sadness and Machina II by The Smashing Pumpkins.
On older betas (ie beta 22 and before), when adding a folder that has two or more sub-directories, it would load the tracks in the order in wich they are listed. And example would be that all the tracks in the first folder would be listed and then all tracks in the second folder would be listed. That way all files play thru from track 1 on CD1 to the last track of CD 2.
However, with beta 25 it lists track 1 from CD1 then track 1 from CD2. Then track 2 from CD1 then track 2 from CD2. I can go to Playback > Sort > Sort by File Path and it will correct the current playlist. When another folder is added it list the files as just stated, and to correct them so they are displayed correctly, I have to go back to the Sort option.
Folders are named this way:
04 - MCIS > 01 - CD1
02 - CD2
09 - Machina II > 01 - CD1
02 - CD2
*wipes brow* Sorry for the long message. I explained it as simply as possible.
System setup: windows xp sp1. creative sound blaster audio card. nvidia video card. no dsps applied in foobar. flac files being used.
preferences / core / adding new files / sort incoming files: <%blah% blah blah>
AtaqueEG
Jul 24 2003, 21:10
QUOTE(zZzZzZz @ Jul 24 2003, 06:54 PM)
Buzzing on pause should be workedaround now (someone confirm, I can't reproduce).
Gapless MP3 playback is back, apparently plain "lame.exe <file.wav>" stores correct values, it only breaks with some frontends. You can use new "fix mp3 header" rightclick to enter correct length in samples (either guess or read from .cue) and make any MP3 file play gaplessly. "Fix mp3 header" rightclick also fixes length/seeking info on VBR files (like all those "vbrfix" tools do).
Working very fine so far.
Thank you very much.
picmixer
Jul 25 2003, 02:22
QUOTE(zZzZzZz @ Jul 25 2003, 02:54 AM)
Buzzing on pause should be workedaround now (someone confirm, I can't reproduce).
Seems to work fine. I don't seem to get any cracking noises when pressing pause anymore.
QUOTE(picmixer @ Jul 25 2003, 11:22 AM)
Seems to work fine. I don't seem to get any cracking noises when pressing pause anymore.
So it was a MS issue after all (reported with different soundcards/drivers but gone after moving all DirectSound calls to one thread).
Meh.
MSDN should mention that all calls made to one instance of DirectSound/waveOut/whateverelse API must be made from same thread (doesn't matter if they're synced not to make multiple API calls at the same time). I know that they have lame shit in implementation of DirectMusic (completely fails to pause/seek if thread starting playback doesn't have a GetMessage() loop), and serious issues in some kind of low-level sound playback code working below win2k/xp waveOut/DirectSound (playback always dies when thread that started it dies, etc etc; this problem didn't occur in win9x apparently).
Polymorph
Jul 25 2003, 04:49
Beta 25 is popping up the console close to the start of virtually every track, with "clipping detected" (never had this problem with earlier betas, though I haven't used any of the 20's till now).
INFO (CORE) : opening file for playback : file://D:\Media\MP3\Albums\Matrix Reloaded\[CD1] 06. The Passportal.mp3
INFO (foo_output_std) : attempting to create DirectSound buffer : 44100Hz 16bps 2ch fixed-point
INFO (foo_output_std) : DirectSound initialized successfully, using software mixing
WARNING (CORE) : Clipping detected.
Using Direct Sound with onboard sound on my work PC, a P450 with 128Mb ram and Win2K. Virtually all of my MP3's are LAME encoded variable bitrate from Exact Audio Copy. Foobar has been fresh installed into an empty directory, with effectively default settings apart from jump-to-time added in.
QUOTE(Polymorph @ Jul 25 2003, 01:49 PM)
Beta 25 is popping up the console close to the start of virtually every track, with "clipping detected" (never had this problem with earlier betas, though I haven't used any of the 20's till now).
INFO (CORE) : opening file for playback : file://D:\Media\MP3\Albums\Matrix Reloaded\[CD1] 06. The Passportal.mp3
INFO (foo_output_std) : attempting to create DirectSound buffer : 44100Hz 16bps 2ch fixed-point
INFO (foo_output_std) : DirectSound initialized successfully, using software mixing
WARNING (CORE) : Clipping detected.
Using Direct Sound with onboard sound on my work PC, a P450 with 128Mb ram and Win2K. Virtually all of my MP3's are LAME encoded variable bitrate from Exact Audio Copy. Foobar has been fresh installed into an empty directory, with effectively default settings apart from jump-to-time added in.
Already changed that for next beta (option to disable popup on warning in the console).
I wouldn't like to listen to what comes out of your speakers though, if every file you play triggers that.
Neogenic
Jul 25 2003, 05:31
zZzZzZz are there any (f.e. resampler) quality improvements coming up soon or are the new (beta)releases only about bugfixes etc?
AstralStorm
Jul 25 2003, 05:57
MP3 resyncing while streaming from Shoutcast is still broken (0.7b25),
doesn't prebuffer on underrun, only plays incoming data.
Not to mention it circles on DirectSound!
(I've tried 128kbps stream on 128kbps link
)
CODE
INFO (CORE) : opening file for playback : http://205.188.209.193:80/stream/1003
WARNING (foo_input_std) : mpeg stream error at 164942 bytes, attempting resync
INFO (foo_input_std) : mpeg stream resync successful
WARNING (foo_input_std) : mpeg stream error at 166446 bytes, attempting resync
INFO (foo_input_std) : mpeg stream resync successful
WARNING (foo_input_std) : mpeg stream error at 169539 bytes, attempting resync
INFO (foo_input_std) : mpeg stream resync successful
WARNING (foo_input_std) : mpeg stream error at 170626 bytes, attempting resync
INFO (foo_input_std) : mpeg stream resync successful
WARNING (foo_input_std) : mpeg stream error at 177898 bytes, attempting resync
INFO (foo_input_std) : mpeg stream resync successful
Pausing allows the buffer to fill and that's what foobar should do when it gets an underrun
untill the buffer is filled up to the threshold.
Xenion
Jul 25 2003, 06:49
font for the volume control doesn't use the "status bar font" but some standard font
Xenion
Jul 25 2003, 07:03
console always comes to the front:
WARNING (CORE) : Clipping detected.
i think in older betas it didn't came to the front on every song
b25
I've got these messages on couple of mp3's:
one file (4394542b):
QUOTE
WARNING (foo_input_std) : mpeg stream error at 4394213 bytes, attempting resync
WARNING (foo_input_std) : mpeg resync failed
another one (5568799b):
QUOTE
WARNING (foo_input_std) : mpeg stream error at 5568470 bytes, attempting resync
WARNING (foo_input_std) : mpeg resync failed
Those 329 bytes are apev2 tags in both cases.
I wiped them/retagged, errors are gone. But during replaygaining in foobar afterwards (album mode), same errors popped up.
So in sum: (tag + album rg) give errors, (tag + track rg) and (no tag + album rg) both don't. For those files naturally, other tracks from same album aren't affected.
Couple of other things:
Bring to front when adding files doesn't seem to work.
'Play' always starts selected song, dependless on 'follow cursor' is disabled.
//edit: I mean when fb2k minimized and 'play' through global hotkey. In 0.6 it used to restart currently playing track.
QUOTE(Xenion @ Jul 25 2003, 02:49 PM)
font for the volume control doesn't use the "status bar font" but some standard font
Same with total time display in status bar.
QUOTE(ak @ Jul 25 2003, 04:45 PM)
Bring to front when adding files doesn't seem to work.
You mean it always brings to front no matter what that option is set to ? Seems to be some kind of f#ckedup windows behavior with DDE, I can't track down what activates the window, and it doesn't go away if I ignore incoming data. Minimizing to system tray seems to workaround the problem though.
No, it doesn't bring to front (wheter from minimized or unfocused), although the option is enabled.
DocterD
Jul 25 2003, 09:05
got something strange in the new beta.
QUOTE
INFO (CORE) : startup time: 561 ms
INFO (CORE) : opening file for playback : file://F:\Music\Red Hot Chili Pepper s-By the Way Advance-2002\16-red_hot_chili_peppers-venice_queen-just.mp3
INFO (CORE) : opening file for playback : file://F:\Music\Red Hot Chili Pepper s-By the Way Advance-2002\11-red_hot_chili_peppers-cabron-just.mp3
INFO (foo_ui_std) : 408 31
INFO (foo_ui_std) : 408 31
INFO (foo_ui_std) : 408 31
INFO (foo_ui_std) : 408 31
INFO (foo_ui_std) : 408 31
INFO (foo_ui_std) : 408 31
INFO (foo_ui_std) : 408 31
//
INFO (foo_ui_std) : 422 32
INFO (foo_ui_std) : 422 32
INFO (foo_ui_std) : 422 32
INFO (CORE) : opening file for playback : file://F:\Music\red hot chilli peppers - californication\Red Hot Chilli Peppers - Californication.mp3
INFO (foo_ui_std) : 43 3
INFO (foo_ui_std) : 43 3
INFO (foo_ui_std) : 46 3
//
INFO (foo_ui_std) : 434 32
INFO (foo_ui_std) : 434 32
INFO (foo_ui_std) : 434 32
INFO (foo_ui_std) : 434 32
WARNING (foo_input_std) : too many frames
don' t really know what that means.
I also have a strange error message when playing some files :
WARNING (foo_input_std) : too many frames
(this message appears near the end of the song...)
What does it mean ?
Skates
Jul 25 2003, 09:18
QUOTE
I also have a strange error message when playing some files :
WARNING (foo_input_std) : too many frames
(this message appears near the end of the song...)
I get that too....
Very Good !! The problem I had before is now gone... nor more too many frames warning.
I found a little seeking bug... when I seek too much with the "right" key, it sometimes seeks beyond the song length. And when I don't press the key anymore, it plays logically the next song...
Is this really a bug or not ?
patchiee
Jul 25 2003, 11:18
dont know what this is actually, but when i play some songs with beta 26 i get this:
QUOTE
INFO (CORE) : startup time: 141 ms
INFO (CORE) : opening file for playback : file://D:\Downloads\mp3\- tmp\Cauterize_-_So_Far_From_Heaven-(Promo_Sampler)-2003-TN\01_cauterize_-_something_beautiful_(album_version)-tn.mp3
INFO (foo_output_std) : attempting to create DirectSound buffer : 44100Hz 16bps 2ch fixed-point
INFO (foo_output_std) : DirectSound initialized successfully, using software mixing
WARNING (CORE) : Clipping detected.
used beta 22 before, and never got that error.. what does "Clipping" mean exactly?
what sort of "error" is it?
ozzimark
Jul 25 2003, 11:34
clipping is when the top of the wave form gets cut off, just picture a sine wave that gets cut off when it goes above 3/4 and turns into a flat peak... depending on how much it is clipped, it can sound distorted.
***nRaecheR***
Jul 25 2003, 12:04
The new console behavior (since 0.7 beta 23) is really annoying. Now each warning (clipping, frames etc.) let the console window pop up, for previous versions only errors forced this. I think the old behavior was much better....
QUOTE(***nRaecheR*** @ Jul 25 2003, 08:04 PM)
The new console behavior (since 0.7 beta 23) is really annoying. Now each warning (clipping, frames etc.) let the console window pop up, for previous versions only errors forced this. I think the old behavior was much better....
Why don't you try out the latest beta ? This problem has already been solved in beta26...
there's a popup on warning option... and "too many frames" error seems to have disappeared with good files...
ilikedirtthe2nd
Jul 25 2003, 12:48
this file:
Artful Dodger ft Craig David - Re-Rewind [Club Remix] [6:58] mp3
which can be found in the appropriative sources gets a astronomic high (645,...) track peak value when scanned in foobar 0.7 beta 26
regards; ilikedirt
spookshow
Jul 25 2003, 13:06
when i try and load my whole mp3 dir (worked fine up till beta22) the program just hangs
there is 7848 files in there
what happened to the "adding files,, current file [ ] thing?
edit: started to really notice it on beta25, and then big time on 26
RIV@NVX
Jul 25 2003, 15:13
A little graphical issue:
Regression, somewhere between b22 and b26.
Killmaster
Jul 25 2003, 16:04
This is an error that I've had for quite some time, but I guess it counts... sometimes when I open fb2k from the system tray the window won't show, but the taskbar item will be there. If I right click and press "maximize" it'll pop up, but unmaximizing it will go back to it's current state. The only way I've found to fix this is to close/reopen the program, after which it'll show up in the upper right corner of the screen in the smallest possible window size.
QUOTE(ak @ Jul 25 2003, 04:45 PM)
I've got these messages on couple of mp3's:
one file (4394542b):
QUOTE
WARNING (foo_input_std) : mpeg stream error at 4394213 bytes, attempting resync
WARNING (foo_input_std) : mpeg resync failed
another one (5568799b):
QUOTE
WARNING (foo_input_std) : mpeg stream error at 5568470 bytes, attempting resync
WARNING (foo_input_std) : mpeg resync failed
Those 329 bytes are apev2 tags in both cases.
I wiped them/retagged, errors are gone. But during replaygaining in foobar afterwards (album mode), same errors popped up.
So in sum: (tag + album rg) give errors, (tag + track rg) and (no tag + album rg) both don't. For those files naturally, other tracks from same album aren't affected.
Fixed for next beta, it's actually affected by total length (in bytes) of tag, not by fields you used.
The problem was harmless (function searching for last frame getting confused) and couldn't have possibly affected your files or decoded data.
That's what I thought initially.
I just meant that when foobar writes album gain value and tag reaches same size as it was, error appears again.
Anyway, thanks for fixing it.
upNorth
Jul 26 2003, 09:20
A cosmetic bug.
If both
Show volume and
Show total time of selected tracks are unchecked there is a "repaint" problem in the status bar when resizing the window. This is most obvious if you press pause. I show 'PAUSED' in the lower right corner when playback is paused, and after a resize it looks like this:
I simply can't live with it
Beta27 with SDK posted, some components will need recompiling (visualization and playlist_loader APIs changed), thanks for feedback everyone.
Atlantis
Jul 26 2003, 12:49
fb2k 0.7 beta27 clean install with default settings
When I try to open a m3u playlist or just "add directory" fb hangs (i've got over 4000 files in the directory)
seems to hangs around 1000 files
edit = winxp sp1, p4 2,66, 2gb ram, 20 gb hd, audigy2
Can't reproduce any of "hang" problems when adding files, sounds more like you don't have enough patience to wait for it to finish adding files and kill process as soon as windows puts up "not responding" notice.
Atlantis
Jul 26 2003, 13:03
fb2k 0.667 takes less than a minute to scan all files and the "processing file" windows is always readable
beta27 takes more than half an hour (and doesn't finish) and both fb2k windows are white empty
no hd activity (confirmed by diskmon)
Try to isolate a file which causes it then ?
Atlantis
Jul 26 2003, 13:18
Uhm...
seems to hang on 1071th file, which is a 128kbps xing mp3
fb2k is opening this file alone correctly
i'm going to have a full chkdsk to make sure partition is consistent...
btw, fbk2 refuses to open Procol Harum - a whiter shade of pale
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.