AtaqueEG
Jul 15 2003, 00:59
QUOTE(zZzZzZz @ Jul 14 2003, 09:38 PM)
On a side note, I've been experimenting with gapless playback of LAME-encoded MP3s...unfortunately results aren't 100% accurate
doesn't look like correct gapless playback of those files is really possible).
Working really good here.
Has not failed yet.
Thank you very much on putting hard work into an issue considered "lost cause" by so many.
I hope you continue developing it.
It might sound like it's working on most of files but it's not perfect; decoded length doesn't match length of source file and more or less noticeable glitches happen (exact results seem to depend on file).
greeny
Jul 15 2003, 06:23
QUOTE
.CUE format doesn't support international characters (should be using your ANSI codepage), you should expect more or less trouble when you try to do this.
Hmm, then why did it always work before v0.7?
Edit:
Nevermind, it works again in beta21. Thanks for fixing the problem.
This should be reproducible.
I have some really long mp3's. Like almost 2 hours which are radio programs.
Start one up and hold down ctl and the 6 on the num pad and try and fast forward to near the end of the program.
It crashes and closes the program as a result.
Atleast it's a "clean crash".
I got an mp3 album (78mins) as a single file. I didn't rip it muself, but mp3trim has no complains when it opens it. Encspot has no problems either, but refuses to copy the info (abnormal program termination).
0.667 reports 20335kbps as bitrate, but seems to play fine nevertheless
0.7 beta 21 only plays 44 seconds, weirdly enough. If I try and push it any further, foobar locks up.
I'm thinking embedded cuesheet maybe? (because the 1st tune is a 44second Intro)
<start log>
file://j:\mp3\BT_-_Emotional_Technology-CD_Promo-2003-btnorg\01_bt_-_emotional_technology-btnorg.cue
INFO (foo_input_std) : got encoder delay: 576
INFO (foo_input_std) : got encoder padding: 1681
WARNING (CORE) : Clipping detected.
WARNING (foo_input_std) : too many frames
<end log>
and then it stops responding (and also playing)
if you want/need me to prepare a sample it's no problem.
Edit: changed faulty playing time.
boojum
Jul 15 2003, 23:46
Buzz - I get a buzz when I click on pause from the system tray using the right mouse button to get the menu. I closed beta20, reopened it and could not reproduce it. This has also happened when the beta was playing (Joe Frank) and just started buzzing on its own. I am running a Dell Dimension 2350, PIIII 2.0 Gig Celeron, WXP SP1. Just ran an WXP repair to eliminate glitches in everything. No programs installed after the WXP repair.
I wish I could reproduce it regularly. The buzz is different tones depending on when the pause is clicked. Maybe it traps the last sound bit and loops on it?
QUOTE(boojum @ Jul 16 2003, 08:46 AM)
Buzz - I get a buzz when I click on pause from the system tray using the right mouse button to get the menu. I closed beta20, reopened it and could not reproduce it. This has also happened when the beta was playing (Joe Frank) and just started buzzing on its own. I am running a Dell Dimension 2350, PIIII 2.0 Gig Celeron, WXP SP1. Just ran an WXP repair to eliminate glitches in everything. No programs installed after the WXP repair.
I wish I could reproduce it regularly. The buzz is different tones depending on when the pause is clicked. Maybe it traps the last sound bit and loops on it?
With which output, DirectSound ? Does it still happen when you disable visualisation processing in preferences ?
QUOTE(pike @ Jul 16 2003, 06:22 AM)
I got an mp3 album (78mins) as a single file. I didn't rip it muself, but mp3trim has no complains when it opens it. Encspot has no problems either, but refuses to copy the info (abnormal program termination).
0.667 reports 20335kbps as bitrate, but seems to play fine nevertheless
0.7 beta 21 only plays 44 seconds, weirdly enough. If I try and push it any further, foobar locks up.
I'm thinking embedded cuesheet maybe? (because the 1st tune is a 44second Intro)
<start log>
file://j:\mp3\BT_-_Emotional_Technology-CD_Promo-2003-btnorg\01_bt_-_emotional_technology-btnorg.cue
INFO (foo_input_std) : got encoder delay: 576
INFO (foo_input_std) : got encoder padding: 1681
WARNING (CORE) : Clipping detected.
WARNING (foo_input_std) : too many frames
<end log>
and then it stops responding (and also playing)
if you want/need me to prepare a sample it's no problem.
Edit: changed faulty playing time.
Broken file (bad VBR header), and it probably keeps skipping samples ahead till the end of file rather than actually locks up.
QUOTE(rtz @ Jul 16 2003, 04:48 AM)
This should be reproducible.
I have some really long mp3's. Like almost 2 hours which are radio programs.
Start one up and hold down ctl and the 6 on the num pad and try and fast forward to near the end of the program.
It crashes and closes the program as a result.
Atleast it's a "clean crash".
Tried almost 3 hours long mp3 (128kbps cbr), no crash.
DocterD
Jul 16 2003, 01:28
Bug(?)
My Foobar2k runed over the night in Repeat mode. After i woke up it was hanging somewhere.Its the second time that it happend. Don`t ask me more i`m to tired
QUOTE(DocterD @ Jul 16 2003, 10:28 AM)
Bug(?)
My Foobar2k runed over the night in Repeat mode. After i woke up it was hanging somewhere.Its the second time that it happend. Don`t ask me more i`m to tired
Standard reply.
Full system specs ? File types being played ? DSP/output settings ? Installed components ?
DocterD
Jul 16 2003, 04:59
System: AMD 2000+ XP
512MB Ram 266
2xHDD
WinXP SP1
Soundblaster Audigy2 Player with newest driver .383
Played File: MP3
was a fresh install of Foobar2k with all components. Output was DirectSound with Hardware Acc.
DSP: Resampler(48000hz) without slowmode and the Advanced Limiter.
DocterD, sound card model would help too (can be driver problem).
Sounds like a driver issue because Audigy series have been famous for that and "nothing like this happens on any of my machines".
i tried the same thing last night, leaving songs running ... and nothing like that occured :/
boojum
Jul 16 2003, 07:59
QUOTE(zZzZzZz @ Jul 15 2003, 10:15 PM)
Does it still happen when you disable visualisation processing in preferences ?
It happens with DirectSound through an Extigy. Visualization was enabled but not running. I will try later today with Visualtion disabled.
It also happened last night about 12:30 AM. I had fb2k playing and it shifted to "buzz." Woke me up and the gal in the apartment above me. Hoowee!
QUOTE(boojum @ Jul 16 2003, 04:59 PM)
QUOTE(zZzZzZz @ Jul 15 2003, 10:15 PM)
Does it still happen when you disable visualisation processing in preferences ?
It happens with DirectSound through an Extigy. Visualization was enabled but not running. I will try later today with Visualtion disabled.
It also happened last night about 12:30 AM. I had fb2k playing and it shifted to "buzz." Woke me up and the gal in the apartment above me. Hoowee!
Probably doesn't matter if visualisation is running or not, visualisation manager is still processing data (and using a little bit of CPU time) if there's any visualisation installed, unless you manually disable it.
Sounds like an issue with extigy drivers to me ("nothing like this happens on any of my machines" again).
It might help to try using waveOut (or even Kernel Streaming) instead (assuming that they don't have more obvious issues), or toggling hardware mixing in DirectSound config page.
QUOTE(zZzZzZz @ Jul 16 2003, 07:17 AM)
QUOTE(pike @ Jul 16 2003, 06:22 AM)
I got an mp3 album (78mins) as a single file. I didn't rip it muself, but mp3trim has no complains when it opens it. Encspot has no problems either, but refuses to copy the info (abnormal program termination).
0.667 reports 20335kbps as bitrate, but seems to play fine nevertheless
0.7 beta 21 only plays 44 seconds, weirdly enough. If I try and push it any further, foobar locks up.
I'm thinking embedded cuesheet maybe? (because the 1st tune is a 44second Intro)
<start log>
file://j:\mp3\BT_-_Emotional_Technology-CD_Promo-2003-btnorg\01_bt_-_emotional_technology-btnorg.cue
INFO (foo_input_std) : got encoder delay: 576
INFO (foo_input_std) : got encoder padding: 1681
WARNING (CORE) : Clipping detected.
WARNING (foo_input_std) : too many frames
<end log>
and then it stops responding (and also playing)
if you want/need me to prepare a sample it's no problem.
Edit: changed faulty playing time.
Broken file (bad VBR header), and it probably keeps skipping samples ahead till the end of file rather than actually locks up.
Sorry for quoting everything, but I wanna keep it simple for you Peter.
It's a 192kbps CBR scene release, so I dont think there's any VBR headers in it? And if 0.667 dont crash and 0.7b21 does, something cant be right?
According to console log, the file does contain VBR header (or rather LAME tag), and the header contains invalid info (claims the file to be shorter than it actually is). I've workedaround the problem for next beta so you can stop (but it refuse to play the file longer than the header says).
picmixer
Jul 16 2003, 16:11
Am getting a strange cracking again when pressing pause. However it only happens when hardware mixing is disabled. When it is enabled everything works fine. I can always reproduce this as soon as hardware mixing is disabled. (actually thought enabling HM should cause more problems then not enabling it, but it seems the other way around here).
Does not happen when using Wave Out or Kernel Streaming.
Happens with 0.7 beta 21
Sys Specs:
Win XP SP1
AMD XP 2200
512 MB DDR-333
Gigabyte 7VAXP Ultra (Via KT 333)
2* 80 MB Maxtor (Raid 0)
1* 44 MB IBM DTLA
Terratec Six Pack
Prophet 8500LE
Playback settings:
16 bit fixed-point
strong ATH noise shaping
direct sound output
Doesn't bother me that much, since I can simply work around it by using hardware mixing. Thought I'd post it anyway to inform you about it. So just ignore or delete this post in case it's not such an issue.
QUOTE(picmixer @ Jul 17 2003, 01:11 AM)
Am getting a strange cracking again when pressing pause. However it only happens when hardware mixing is disabled. When it is enabled everything works fine. I can always reproduce this as soon as hardware mixing is disabled. (actually thought enabling HM should cause more problems then not enabling it, but it seems the other way around here).
Does not happen when using Wave Out or Kernel Streaming.
Happens with 0.7 beta 21
Sys Specs:
Win XP SP1
AMD XP 2200
512 MB DDR-333
Gigabyte 7VAXP Ultra (Via KT 333)
2* 80 MB Maxtor (Raid 0)
1* 44 MB IBM DTLA
Terratec Six Pack
Prophet 8500LE
Playback settings:
16 bit fixed-point
strong ATH noise shaping
direct sound output
Doesn't bother me that much, since I can simply work around it by using hardware mixing. Thought I'd post it anyway to inform you about it. So just ignore or delete this post in case it's not such an issue.
Now that's more interesting; perhaps it would help to change playback thread priority settings or something like that.
[edit] WTF!! your computer is almost exact clone of mine - same CPU/RAM, same OS, same mobo chipset, exactly same videocard and soundcard ^_^
Perhaps it can be reproduced on mine after all.
picmixer
Jul 16 2003, 16:38
Just did some further testing and is also happens in 0.667.
Also forgot to mention no 3rd party plugins installed and no active dsps except attenuator (volume, or whatever).
Realized a while ago in on of your posts that we almost have the same setup found it quite funny as well. Hope you can reproduce.
Beta22 posted.
Unfortunately I can't do anything about "buzzing" because it simply doesn't happen here (tried on different machines).
entrylevel
Jul 17 2003, 00:06
gapless mp3 (lame encoded) playback seems doesn't work with 0.7beta22 anymore. beta21 works perfectly.
Works perfectly ? Don't make me laugh.
It (incorrectly) removes samples from Xing-encoded files, and amounts of samples removed from the end of file are wrong almost all the time.
This feature is getting removed, because it's a non-working piece of shit, tends to remove too many samples, damaging decoded data and preventing Case's gap remover from working correctly.
DocterD
Jul 17 2003, 06:04
Hmm i will test this hang problem again with kX drivers.
btw can you pls add ability to skip Replayscan of MP3 that already have replaygain infos?
Pretty harmless, but it seems System menu items are locked at their default position. Moving them up and down in the preferences doesn't change anything. I tried restarting Foobar to no avail.
All the other "Main menu items" are movable.
Windows XP SP1 and beta 22.
Intentional, otherwise they would get sorted in alphabetical order by default and I don't want that.
QUOTE(zZzZzZz @ Jul 17 2003, 06:02 PM)
Intentional, otherwise they would get sorted in alphabetical order by default and I don't want that.
I don't get it. If you don't mind me asking; why not just change the default configuration then (foobar2000.cfg)? Isn't it possible?
QUOTE(Gaffa @ Jul 17 2003, 07:10 PM)
QUOTE(zZzZzZz @ Jul 17 2003, 06:02 PM)
Intentional, otherwise they would get sorted in alphabetical order by default and I don't want that.
I don't get it. If you don't mind me asking; why not just change the default configuration then (foobar2000.cfg)? Isn't it possible?
If I did so, any new items I add there later would pop up at the end for people not using fresh configs.
AtaqueEG
Jul 17 2003, 10:28
QUOTE(zZzZzZz @ Jul 17 2003, 03:28 AM)
Works perfectly ? Don't make me laugh.
It (incorrectly) removes samples from Xing-encoded files, and amounts of samples removed from the end of file are wrong almost all the time.
This feature is getting removed, because it's a non-working piece of shit, tends to remove too many samples, damaging decoded data and preventing Case's gap remover from working correctly.
I don't have the smallest clue about foobar2000's code, so if I am suggesting something absurd, I apologize.
Could this "piece of shit" feature be optional? I mean, with a switch and a short warning, like the one for KS. Something that told the user that feature is experimental, innacurate on Xing-decoded files and whatever, USE AT OWN RISK!
I'm saying this because with my LAME -aps files there are no audible flaws (and I have tried with some tracks I know backwards and forwards). Case's plugin failed occasionally on those.
Thanks.
QUOTE(AtaqueEG @ Jul 17 2003, 07:28 PM)
I don't have the smallest clue about foobar2000's code, so if I am suggesting something absurd, I apologize.
Could this "piece of shit" feature be optional? I mean, with a switch and a short warning, like the one for KS. Something that told the user that feature is experimental, innacurate on Xing-decoded files and whatever, USE AT OWN RISK!
I'm saying this because with my LAME -aps files there are no audible flaws (and I have tried with some tracks I know backwards and forwards). Case's plugin failed occasionally on those.
Thanks.
Case has been working on some kind of hack to guess correct padding values from lame headers and said that he managed to figure a formula that works correctly for all of files he tried so far (assuming that each source song length was a multiply of 588 samples, which is true for all tracks ripped from a CD).
Then again, that solution won't even be fully compatible with actual lame header specs.
I will possibly put it back (togglable, yes), when a version that behaves decently is developed.
Still, it's all fault of LAME developers that they didn't even bother testing their code; what they write to headers is far from accurate because of bugs on their side.
QUOTE(AtaqueEG @ Jul 17 2003, 07:28 PM)
Case's plugin failed occasionally on those.
I made some major improvements for Gap killer yesterday, still not perfect always but it's much better than old versions. Please try
latest version.
upNorth
Jul 17 2003, 11:34
I'm not sure if this is a bug or intended behavior, but at least it's bugging me. Problem is that I use icons on my toolbar (taskbar/quick launch) to control playback. E.g. "C:\...\foobar2000\foobar2000.exe" /playpause
IIRC this work fine untill some time recently. Now foobar start flashing on my taskbar every time I use these buttons/shortcuts. If it is minimized to system tray, it will be restored to taskbar and start the flashing. Commands work, but I find this behavior annoying. If there is a reason for this that I'm not aware of, please let me know.
Btw: It's not a matter of life and death because I will remove the shortcuts as soon as v0.7 reaches final and foo_WSGUI is released for it.
Specs:
foobar2000 v0.7 BETA22 (clean install, did not change a thing)
WinXP SP1
If it matter: Directsound and onboard sound chip
QUOTE(upNorth @ Jul 17 2003, 08:34 PM)
I'm not sure if this is a bug or intended behavior, but at least it's bugging me. Problem is that I use icons on my toolbar (taskbar/quick launch) to control playback. E.g. "C:\...\foobar2000\foobar2000.exe" /playpause
IIRC this work fine untill some time recently. Now foobar start flashing on my taskbar every time I use these buttons/shortcuts. If it is minimized to system tray, it will be restored to taskbar and start the flashing. Commands work, but I find this behavior annoying. If there is a reason for this that I'm not aware of, please let me know.
Btw: It's not a matter of life and death because I will remove the shortcuts as soon as v0.7 reaches final and foo_WSGUI is released for it.
Specs:
foobar2000 v0.7 BETA22 (clean install, did not change a thing)
WinXP SP1
If it matter: Directsound and onboard sound chip
Most likely a bug, I'll look into it, thanks.
AtaqueEG
Jul 17 2003, 13:43
QUOTE(zZzZzZz @ Jul 17 2003, 10:39 AM)
I will possibly put it back (togglable, yes), when a version that behaves decently is developed.
Fair, enough.
Thanks.
BTW: I tried beta22 with Case`s improved plugin and seems to do the job. Thanks also.
upNorth
Jul 17 2003, 17:06
(1) When i right click on files and choose "Play in foobar2000" or "Enqueue in foobar2000" it will only work if no more than one file is selected. When I select more than one it starts processing/thinking, but when it's finished nothing shows up in playlist.
(2) An earlier feature I miss, is the ability to use the foobar shortcut on my taskbar to bring foobar to front when it's already running. Can't remember when it went away, but I think it was handy.
Specs:
foobar2000 v0.7 BETA22 (clean install, didn't change a thing)
WinXP SP1, Directsound and onboard sound chip
[off topic]Maybe I'm pushing my luck, but would it be much hassle to add the ability to move already assigned shortcuts up and down, in the shortcut assignment window?. It would be nice to be able to sort them. I'm thinking of buttons like the ones in "Main menu items".
(1) Some kind of issue with registry corruption, has been mentioned somewhere else.
(2) Launching foobar2000.exe with no commandline should be doing that, but it doesn't at the moment because of some kind of bug (will be fixed for next beta).
When I click "add directory", it seems to "add" the mp3's alphabetically. How about run 2 threads and have one start at 1 and the other at z and have them meet in the middle?
Would speed it up twice as fast? For dir's with ~1,000+ mp3's..
Both useless and pain to implement. I don't know where some of you people get those ideas from. HDD access speed (and I mean random access speed not raw speed) is bottlenecking adding new files because of info reading, can't be helped. Multithreading that could actually be even slower.
upNorth
Jul 17 2003, 18:33
QUOTE(upNorth @ Jul 18 2003, 01:06 AM)
(1) When i right click on files and choose "Play in foobar2000" or "Enqueue in foobar2000" it will only work if no more than one file is selected. When I select more than one it starts processing/thinking, but when it's finished nothing shows up in playlist.
It now works again after running a Norton Utilities system clean up.
boojum
Jul 18 2003, 02:21
QUOTE(zZzZzZz @ Jul 15 2003, 10:15 PM)
With which output, DirectSound ? Does it still happen when you disable visualisation processing in preferences ?
Yes. it occurs when Visualization is disabled. I will try another option, like WaveOut to see how that affects it. This does not happen with 0.667 FWIW
B)
I think I've got some ideas, I can try cloning certain behaviors from other DirectSound outputs I wrote earlier, I'm starting to think that pause issue is some kind of broken multithreading behavior on MS side (I documented a few of those before).
Regarding buzz-when-pausing issue again - which DirectX version do you have ? I'm running latest DX9 here, with all updates; it's very likely that the problem got fixed somewhere between DX8 and DX9.
Soff: please eat a flaming bag of hell, fix your server configs, and learn to find your posts in
threads that have been split, thanks
boojum
Jul 18 2003, 11:31
QUOTE(zZzZzZz @ Jul 18 2003, 02:52 AM)
Regarding buzz-when-pausing issue again - which DirectX version do you have ? I'm running latest DX9 here, with all updates; it's very likely that the problem got fixed somewhere between DX8 and DX9.
Peter - I am attached to MSUpdate now d/l'ing the latest DirectX updates. Two seperate issues: 1) does not happen with 0.667. 2) WXP flaky as hell, crashes on everything including IE. I have run the WXP "repair" a few times to no avail. Re-install WXP? Does that blow away everything else? I should have stuck with OS/2.
picmixer
Jul 18 2003, 13:59
DX 9.0a
Mike Giacomelli
Jul 19 2003, 22:38
I've had Foobar2000 crash on me several times while replaygaining the same (LAME encoded) album. Then once I finally got it calculated it, the numbers vanished once I restarted. I regained it and it crashed again.
If I can get it to crash again, what info would be useful? I tried grabbing the NT memory dump thing but it deleted itself as I tried to open it.
I've noticed gain information vanish from foobar several times. Any idea why this would be?
For reference:
Beta 21.
XP Pro SP1.
nForce 415, onboard sound on my A7N266-c.
Kernel Streaming, no additional plugins aside from ID3v2 (which is enabled).
DX9.
Thanks for your time.
Edit: Ok happened a third time tonight and gave me this:
CODE
<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="foobar2000.exe" FILTER="GRABMI_FILTER_PRIVACY">
<MATCHING_FILE NAME="bass.dll" SIZE="102196" CHECKSUM="0x20A8BDB8" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x10008" LINK_DATE="06/19/2003 12:31:38" UPTO_LINK_DATE="06/19/2003 12:31:38" />
<MATCHING_FILE NAME="fooassoc.exe" SIZE="43651" CHECKSUM="0x6BE9A593" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/10/2003 00:21:32" UPTO_LINK_DATE="07/10/2003 00:21:32" />
<MATCHING_FILE NAME="foobar2000.exe" SIZE="109056" CHECKSUM="0xAF6377AC" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/14/2003 23:41:12" UPTO_LINK_DATE="07/14/2003 23:41:12" />
<MATCHING_FILE NAME="uninstall.exe" SIZE="39794" CHECKSUM="0xF55687B6" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/13/2003 22:31:43" UPTO_LINK_DATE="07/13/2003 22:31:43" />
<MATCHING_FILE NAME="utf8api.dll" SIZE="13312" CHECKSUM="0xB5554E3F" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/13/2003 22:46:32" UPTO_LINK_DATE="07/13/2003 22:46:32" />
<MATCHING_FILE NAME="components\foo_abx.dll" SIZE="16384" CHECKSUM="0x3093E667" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="05/29/2003 00:34:55" UPTO_LINK_DATE="05/29/2003 00:34:55" />
<MATCHING_FILE NAME="components\foo_albumlist.dll" SIZE="14848" CHECKSUM="0x2A342EC3" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/13/2003 22:46:43" UPTO_LINK_DATE="07/13/2003 22:46:43" />
<MATCHING_FILE NAME="components\foo_ape.dll" SIZE="45056" CHECKSUM="0x74BDA5DC" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/13/2003 22:46:42" UPTO_LINK_DATE="07/13/2003 22:46:42" />
<MATCHING_FILE NAME="components\foo_cdda.dll" SIZE="17408" CHECKSUM="0x58C5DBC1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/13/2003 22:46:44" UPTO_LINK_DATE="07/13/2003 22:46:44" />
<MATCHING_FILE NAME="components\foo_console.dll" SIZE="6656" CHECKSUM="0xD26EB5C7" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/13/2003 22:46:44" UPTO_LINK_DATE="07/13/2003 22:46:44" />
<MATCHING_FILE NAME="components\foo_diskwriter.dll" SIZE="16896" CHECKSUM="0x6981AA16" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/13/2003 22:46:45" UPTO_LINK_DATE="07/13/2003 22:46:45" />
<MATCHING_FILE NAME="components\foo_dsp_extra.dll" SIZE="36352" CHECKSUM="0xD2B30E7B" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/14/2003 23:55:21" UPTO_LINK_DATE="07/14/2003 23:55:21" />
<MATCHING_FILE NAME="components\foo_flac.dll" SIZE="39424" CHECKSUM="0x19297B67" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/07/2003 11:42:58" UPTO_LINK_DATE="07/07/2003 11:42:58" />
<MATCHING_FILE NAME="components\foo_id3v2.dll" SIZE="131072" CHECKSUM="0xD3ADA09A" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/05/2003 18:25:52" UPTO_LINK_DATE="07/05/2003 18:25:52" />
<MATCHING_FILE NAME="components\foo_input_std.dll" SIZE="141312" CHECKSUM="0x23C7B84B" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/14/2003 23:41:10" UPTO_LINK_DATE="07/14/2003 23:41:10" />
<MATCHING_FILE NAME="components\foo_masstag.dll" SIZE="16896" CHECKSUM="0x7913DAB4" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/13/2003 22:46:43" UPTO_LINK_DATE="07/13/2003 22:46:43" />
<MATCHING_FILE NAME="components\foo_mod.dll" SIZE="11264" CHECKSUM="0x61EA897F" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/05/2003 18:31:15" UPTO_LINK_DATE="07/05/2003 18:31:15" />
<MATCHING_FILE NAME="components\foo_mp4.dll" SIZE="113664" CHECKSUM="0xB7BBE5EB" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/09/2003 12:51:24" UPTO_LINK_DATE="07/09/2003 12:51:24" />
<MATCHING_FILE NAME="components\foo_output_std.dll" SIZE="12800" CHECKSUM="0xDB1BE38C" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/13/2003 22:46:43" UPTO_LINK_DATE="07/13/2003 22:46:43" />
<MATCHING_FILE NAME="components\foo_out_ks.dll" SIZE="16384" CHECKSUM="0xF8C7DE06" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/13/2003 22:46:43" UPTO_LINK_DATE="07/13/2003 22:46:43" />
<MATCHING_FILE NAME="components\foo_read_http.dll" SIZE="13312" CHECKSUM="0x58F1965F" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/13/2003 22:46:46" UPTO_LINK_DATE="07/13/2003 22:46:46" />
<MATCHING_FILE NAME="components\foo_rgscan.dll" SIZE="19968" CHECKSUM="0x9DC1C555" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/14/2003 23:04:00" UPTO_LINK_DATE="07/14/2003 23:04:00" />
<MATCHING_FILE NAME="components\foo_spc.dll" SIZE="22528" CHECKSUM="0x47001365" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/13/2003 22:46:42" UPTO_LINK_DATE="07/13/2003 22:46:42" />
<MATCHING_FILE NAME="components\foo_speex.dll" SIZE="51200" CHECKSUM="0x56E8436C" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/15/2003 00:37:24" UPTO_LINK_DATE="07/15/2003 00:37:24" />
<MATCHING_FILE NAME="components\foo_ui_std.dll" SIZE="25088" CHECKSUM="0x23C662FC" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/14/2003 02:06:27" UPTO_LINK_DATE="07/14/2003 02:06:27" />
<MATCHING_FILE NAME="components\foo_unpack.dll" SIZE="45056" CHECKSUM="0xB19FB1CC" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/13/2003 22:46:42" UPTO_LINK_DATE="07/13/2003 22:46:42" />
<MATCHING_FILE NAME="components\foo_vis_manager.dll" SIZE="9216" CHECKSUM="0x8596FC3A" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/13/2003 22:46:46" UPTO_LINK_DATE="07/13/2003 22:46:46" />
<MATCHING_FILE NAME="components\foo_wavpack.dll" SIZE="15360" CHECKSUM="0x939CD45F" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/13/2003 22:46:47" UPTO_LINK_DATE="07/13/2003 22:46:47" />
</EXE>
<EXE NAME="foo_id3v2.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="foo_id3v2.dll" SIZE="131072" CHECKSUM="0xD3ADA09A" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/05/2003 18:25:52" UPTO_LINK_DATE="07/05/2003 18:25:52" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="kernel32.dll" SIZE="930304" CHECKSUM="0xCBCCF8A9" BIN_FILE_VERSION="5.1.2600.1106" BIN_PRODUCT_VERSION="5.1.2600.1106" PRODUCT_VERSION="5.1.2600.1106" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.1106 (xpsp1.020828-1920)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xE7ED3" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.1106" UPTO_BIN_PRODUCT_VERSION="5.1.2600.1106" LINK_DATE="08/29/2002 10:40:40" UPTO_LINK_DATE="08/29/2002 10:40:40" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
</DATABASE>
Is that of any use? Guessing from the "ModName: foo_id3v2.dll" part listed in the error signiture field, I'm guessing its not a foobar problem.
kode54
Jul 20 2003, 00:07
Share one of these crashing files with me and I'll try to fix it. (PM link or something.)
Hi,
Had problems with beta 22, but I fixed them by reinstalling. This time I selected normal installation rather than custom and it works perfectly. Sorry to be a waste of server space! -Elliott
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.