minor update
happy new year 2008~
foo_dsp_crossfader 0.3.3.5 (2/1/2008)
- fixed one menu item status shown incorrectly when the menu group is locked
it is recommended updating to this version to avoid future crash of incompatibility with newer version of foobar2000.
also, starting from this update, I’m using visual studio 2008.
in other words, my newer components or updates will require vc9 runtime libraries, the download link is in my component post.
the vc9 runtime libraries is backward compatible to vc8.1/vc8 runtime libraries, so you only need that for all my components.
and I’m still waiting for an update version of intel compiler that supports vs2008, so for the moment, the components will be compiled with the normal vc compiler.
Jonas said,
June 4, 2008 @ 4:47 pm
Hey!
It works with foobar2000 v0.9.5.3 but it always priduces an error when you start foobar2000.
But then it works…
When comes a new version?
Thanks
Aesthetic said,
May 31, 2008 @ 5:15 pm
Hey, unfortunately it’s not working with foobar2000 v0.9.5.3. ;/
ritchan said,
January 7, 2008 @ 11:50 pm
Hey, I got your masstag_addons, installed the vc2008 redistributable, but it still says:
foo_masstag_addons.dll, reason: The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail.
What’s going on? Apparently it’s got something to do with newer versions of VStudio?
Alex said,
January 7, 2008 @ 2:34 am
I copied the DLL into the components folder for foobar v 0.9.5. I got the following error. Any idea what is giong on?
Failed to load DLL: foo_dsp_crossfader.dll
Reason: This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.
cweihuang said,
December 29, 2007 @ 10:57 am
how to install
cweihuang said,
December 29, 2007 @ 10:57 am
need
treehyrax said,
December 24, 2007 @ 9:28 am
Right, thank you. That did it. Sorry about the extra trouble.
Acropolis said,
December 24, 2007 @ 9:15 am
no, you did it wrongly.
what I meant was: in the dsp preference page, remove crossfader from the dsp chain list, then click the save all button.
then put crossfader back to the list, click save all again.
then try to play now, I think should resolve the problem.
treehyrax said,
December 24, 2007 @ 8:27 am
Removing other components didn’t help. BTW, I can use the gapless feature – it’s just enabling crossfade that gives me the error. A couple of times I _have_ managed to play one track after startup, then it’s started throwing me that error.
treehyrax said,
December 24, 2007 @ 8:10 am
I think I did – the version I used to have didn’t have gapless feature (which, by the way, was much anticipated. Thank you).
Well, I just removed crossfader, restarted foobar, and when it asked me, I opted to save the settings (did you really intend to say I _should_ save them?). Then I reinstalled crossfader – still getting the same error. I tried the same procedure without saving the settings, too; didn’t help.
I’ll try removing some of the other components and see if that helps.
Acropolis said,
December 24, 2007 @ 7:44 am
ok, at first I thought it was a problem of a removed feature.
did you update from quite old version of crossfader (e.g. before 0.3.3)?
I suggest you to remove crossfader from the dsp chain, and save the setting, and load crossfader again, because there were some config changes starting from 0.3.3.
treehyrax said,
December 24, 2007 @ 7:24 am
What precisely could be wrong there? The device is Realtek AC97, buffer length 1000 ms (default), 16 bit (which is correct). The “Null Output” obviously produces no sound at all… yet I get the same error with your plugin enabled.
Acropolis said,
December 24, 2007 @ 6:56 am
check your output device setting.
treehyrax said,
December 24, 2007 @ 6:09 am
Hi, I get an “Unrecoverable playback error: bad allocation” with this release. Posted about it on the Hydrogenaudio forums.