new alloc for instr 1: B 0.400 .. 0.500 T 0.500 TT 0.500 M: 10808.9 8250.4 new alloc for instr 1: [CTRL + C is pressed] Csound tidy up: Interrupt Csound tidy up: Segmentation violation inactive allocs returned to freespace end of score. overall amps: 13746.9 13640.7 overall samples out of range: 0 0 0 errors in performance # Hi, # I have the halting problem too. I just run the xanadu.csd. When I run it offline I only get the "Csound tidy up" messages and return to command line. But when I run it in realtime with "csound xanadu.csd -odac" and stop the rendering with CTRL+C after the tidy up messages the command prompt does not respond and I should force the window to close by myself. # But I do not know whether this is a problem related to Csound or Portaudio. -ugur guney- On Thu, Mar 20, 2008 at 3:28 AM, Art Hunkins wrote: > > > Mike (and other interested folk), > > I just ran my first .csd with the new 5.08.2 Csound installation described > below - starting with everything as it natively installed. Here's a report. > (The installation is on my XP laptop. All runs were from the commandline, > within csound\bin, where my .csd was also located.) > > First, I want to say that a straightforward stereo ambisonic setup worked > perfectly. (I've yet to test 4- and 8-channels.) > > I got, right off, the two "Python 2.5 not found" popups (which I rather > expected), and three WARNINGS: 1 each about csnd.dll, py.dll and maxmin.dll > not found. (Incidentally, this is with the -m0 flag; I guess the WARNING > message flag is indeed still unchanged.) Nevertheless, the realtime MIDI > performance proceded flawlessly except at the end - where there was a Csound > tidy up: Segmentation Violation message (always extremely helpful!) followed > by these lines: > > pm_winmm_term called > begin closing open devices. . . > > and the run halts (with cursor blinking) - does not respond to CTRL-C. > Attempt to close window fails, except when Windows "program cannot close" > window appears and you force a stop. > > I next removed csd.dll from csound\bin. Nothing changed. > > I then removed both csd.dll and py.dll from csound\plugins. At that point > the two Python popups disappeared, as did two of the three WARNING messages > (about csd.dll and py.dll). The program closing problems persist. > > Finally, I removed minmax.dll from csound\plugins, and the final WARNING > (regarding minmax.dll) disappeared. The closing problems remain. > > My are: > -odac0 -m0d -M9 --expression-opt -b128 -B2048 -+raw_controller_mode=1 > The MIDI and audio device numbers are correct, as the live performance > attests. FLTK and Lettuce, both of which present exit issues, were not > involved here. I was also using my laptop's builtin sound, so as not to > complicate that variable. > > Does "pm_winmm_term" indicate some kind of MIDI driver issue? (My MIDI > interface is an Edirol UM-1S MIDI-to-USB converter, which has worked > problem-free in the past - with earlier Csounds on this same laptop.) > > Thanks for the help - Mike (and anyone else). > > Art Hunkins > > ----- Original Message ----- > > From: Michael Gogins > To: csound@lists.bath.ac.uk > > Sent: Wednesday, March 19, 2008 8:44 PM > Subject: [Csnd] Re: Re: Version 5.08 now released > > > Thanks for the information, I will make sure this is fixed. > > Regards, > Mike > > ----- Original Message ----- > From: Art Hunkins > To: csound@lists.bath.ac.uk > Sent: Wednesday, March 19, 2008 8:13 PM > Subject: [Csnd] Re: Version 5.08 now released > > > Michael and Ugur, > > This evening I downloaded and installed Csound5.08.2-gnu-win32-f.exe , and > can report the following: > > After making sure everything else (Csound-wise) was out of the way, I > installed, and was met by the Python popup. I do not have Python installed, > and the message recognized that correctly. I must admit, however, to needing > to ponder, for several minutes, whether to hit Yes or No - to go on without > Python. I think the wording is confusing.I'd suggest something like this: > "You do not have Python installed and cannot currently run Python scripts > (or whatever). Do you wish to Continue without Python, or Abort (to first > install Python)?" The buttons would be labled Continue and Abort. > > (The larger question is whether neophytes should be asked about Python *at > all*. As a noobee, I'd be in a complete quandry, and not know which way to > go. It might be good to add another line to the message box: "If you're > unfamilar with Python, just hit Continue.") > > The installation otherwise proceded without incident, except that I noticed > that a PYTHONPATH environment variable was set - pointing to csound\bin. I > should think this again somewhat misleading, as well as potentially > problematic. However, I'm out of my depth here and perhaps there is good > reason. (Again my concern is confusion for all except advanced users. And > there, you see where that leaves me!) > > Most importantly, I found csnd.dll and py.dll located here: > in csound\bin: csnd.dll > in csound\plugins: csnd.dll and py.dll > in csound\python_backup\plugins: py.dll > > I assume only the last placement is correct. > > Art Hunkins