Csound Csound-dev Csound-tekno Search About

[Csnd] Re: Re: Re: Version 5.08 now released

Date2008-03-20 01:28
From"Art Hunkins"
Subject[Csnd] Re: Re: Re: Version 5.08 now released
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 <CsOptions> 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 -----
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 -----
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
----- Original Message -----
Sent: Wednesday, March 19, 2008 3:33 AM
Subject: [Csnd] Re: Re: Re: Re: Re: ++SPAM++ Re: Version 5.08 now released

On Wed, Mar 19, 2008 at 2:47 AM, Michael Gogins <gogins@pipeline.com> wrote:
I did not find csnd.dll and py.dll in the wrong directory, but I will check
again. Is there any possiblity you have some left over from an earlier
installation (such as a beta installer)?

# No, I uninstalled the old version, and make sure nothing has left. I even deleted the system environment variables.
# Best,
-ugur-

Regards,
Mike

----- Original Message -----
From: "Uğur Güney" <ugurguney@gmail.com>
To: <csound@lists.bath.ac.uk>
Sent: Tuesday, March 18, 2008 5:53 PM
Subject: [Csnd] Re: Re: Re: ++SPAM++ Re: Version 5.08 now released


># I just installed Csound 5.08.2 under Xp.
>
> On Tue, Mar 18, 2008 at 7:36 PM, Michael Gogins <gogins@pipeline.com>
> wrote:
>>  Regarding Python, I repeat (note that the current installer does not
>> attempt to install Python):
>>
>>  The current installer tests for Python 2.5 in the Windows registry. If
>> Python is
>>  found in the registry, then the Python features of Csound are installed.
>
> # I can not say anything about this, because do not have Python installed.
>
>>  If Python is not found in the registry, then the installer gives the
>> user a choice to abort
>>  installation in order to install Python, or to proceed with installation
>> but to
>>  put the Python features in a secluded directory.
>
> # Yes, a option message appeared for yes aborting installation and no
> for continuing to installation. I chose no and csound is installed.
> But when I type just "csound" I'm getting again the warning windows I
> attached this morning.
>
>>  I have verified that this behavior does occur on my computer. I would
>> like to know
>>  if it is working for other installations. "Yes" or "No" plus
>>  some details would be appreciated.
>
> # I looked at the csound folder. There is a folder named
> "python_backup", which has some .pyd and .py files under
> "python_backup\bin" folder and py.dll under "python_backup\plugin64"
> folder. But the csnd.dll and py.dll files who are responsible from
> pop-ups (one warning window for one .dll) are still under
> "csound\plugin64" folder, so they are not secluded.
> # I think we are getting close to the solution! Have a nice day!
> -ugur guney-
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"



Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"


Date2008-03-20 08:06
FromUğur Güney
Subject[Csnd] Re: Re: Re: Re: Version 5.08 now released
AttachmentsNone