Followup to previous post:

5.07 works correctly, just like 5.06.

5.08 doesn't run at all (neither does the Lettuce standalone) due to the 
PortAudio issue in that version, which was fixed by Mike G. in 5.09. 
(Perhaps his fix is related to my issue, though that seems unlikely.)

Still mystified and seeking illumination -

Art Hunkins

----- Original Message ----- 
From: "Art Hunkins" 
To: 
Sent: Tuesday, February 24, 2009 7:18 PM
Subject: Csound 5.06 vs. 5.09 and 5.10


> This question concerns WinXP and realtime, MIDI-controlled performance 
> .csd's.
>
> I've three separate folders, one each containing the following files from 
> 5.06, 5.09 and 5.10:
>
> csound32.dll.5.1 (csound32.dll.5.2 in the case of 5.10)
> stdopcod.dll
> csound.exe
> libsndfile-1.dll
> pmidi.dll
> portaudio.dll
> portmidi.dll
> porttime.dll
> pthreadGC2.dll
> rtpa.dll
> rtwinmm.dll
>
> These are the only Csound files required to render my compositions. *No 
> environment variables are set* and .csd's are run from within these 
> folders. (Please note that the way I've set up things, multiple versions 
> of Csound can easily be run from unique directories on the same computer - 
> with no environment variables set. Just put everything for one version in 
> a single directory. You may need no more files than the above dozen or so, 
> plus your .csd's.
>
> Problem: Whereas standalone Lettuce executables run fine in each of the 
> three folders, only 5.06 runs *from the command line* correctly. 5.09 and 
> 5.10 issue the following error when Ctrl-C is pressed:
> Csound tidy up: Interrupt
> Csound tidy up: Segmentation violation (as always - *so* helpful!)
> pm_winmm_term called
> begin closing open devices...
>
> and the system hangs.
>
> Note there is no .csoundrc file, and that I'm defaulting to PortMIDI. My 
> CsOptions include -M11 (my MIDI device). All installations use files from 
> the float Windows installers.
>
> Everything worked so well in 5.06.
>
> Why should 5.09 and 5.10 fail (at the command line only)?
>
> Art Hunkins