Hi,

Sorry for replying so late after 5.07.2 was released.

fluidOpcodes.dll is still causing "Access Violation" crashes for me.
  I'm using WinXP
SP2.  [csound~] still crashes after csoundReset() or csoundDestroy() is called and I
click on a non-MaxMSP window.
  Lettuce also pops up "Access Violation" messages under
similar circumstances.  blue,
 csoundapi~, and command line Csound work just fine.  

I downloaded the source code for fluidsynth 1.0.8 and compiled fluidsynth.dll with 
MSVC 8.  Commenting out the CreateWindow() related stuff in 
fluid_win32_create_window() in fluid_dll.c prevents the crashes.  

Supposedly, the window is needed in order for DirectSound to work.  But the 

problem is that the thread that called CreateWindow() must also call DestroyWindow().

If a different thread calls DestroyWindow(), then we get a crash.  The fluidsynth devs

decided to never call DestroyWindow(), but that's a crappy solution IMO. 

I successfully tested the fluid opcodes (using bolivianflute.SF2) after removing
the CreateWindow() related code.  No crashes.  

So I guess we could:

1) Remove the CreateWindow() code ourselves.

2) Ask the fluidsynth devs to do it for us.  

3) Ask the fluidsynth devs to provide some way to bypass the CreateWindow() 
   stuff.  Or better yet, just allow us to bypass the audio driver stuff since
   (if my understanding of fluidsynth is correct) it's not needed when used
   in Csound.

Any comments, suggestions, corrections are appreciated.  Thanks.


Davis

 

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net