Re: [Csnd] Realtime Csound6 on Windows System 7

Date	2014-07-16 01:42
From	"Art Hunkins"
Subject	Re: [Csnd] Realtime Csound6 on Windows System 7
	Hi Michael, I have followed up on your suggestions, on my Windows 7 desktop. 1) No competing libsndfile or portaudio DLLs exist. 2) Changing PATH to what you suggest made no difference. 3) Going the depends.exe route yielded results. The image yielded by profiling Test.csd within Csound is attached (if does not come through to you, please advise; the list will receive this message without the sizeable attachment). There appear to be multiple problems (in red type). Probably they will indicate to you what has been going on. Two additional observations: 4) I notice that previously I had installed your 6.02 edition (I found this Setup download still among my files - though 6.02 had been thoroughly uninstalled before installing 6.03.2.) I don't this this matters, but who knows . . . 5) A curious thing happened when I downloaded and attempted to unzip (with WinZip) the depends archive (depends32_x86). I wasn't authorized to extract it (though I'm the admin). Tried multiple times to several locations; I ended up running it from within WinZip, which seemed to work just fine. This particular machine seems to have some peculiar quirks about it, and I am not the original owner. So, another "who knows" . . . Please let me know of any diagnosis! Thanks so much - Art Hunkins ----- Original Message ----- From: Michael Gogins To: Csound Sent: Monday, July 14, 2014 7:15 PM Subject: Re: [Csnd] Realtime Csound6 on Windows System 7 I just tried Art's test CSD on my Windows 8 machine where I built it, but in the installation environment. It worked fine. I'm afraid I don't have a clear idea what's going on here. Possibly there is some DLL conflict. You can try to get a handle on this by using depends.exe from here: http://www.dependencywalker.com/ First try just loading csound.exe into depends. Then try running your file using the "profile" menu. I have seen DLL conflicts with Reaper, which uses different builds of some of the same DLLs that Csound uses. Another, perhaps easier way of getting a handle on this is to temporarily change your Windows PATH environment variable to include only the Csound bin directory. If the problem goes away in that case, it means that either Csound, or one of Csound's DLLs, tried to load a DLL that conflicted with one that was already loaded, or that was built wrong for Csound. Another idea is to look and see if some other program has installed its own portaudio DLL or libsndfile DLL which conflicts. Some of the mingw or gtk DLLs (in the Csound bin directory) may also conflict. Hope this helps, Mike ----------------------------------------------------- Michael Gogins Irreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com On Mon, Jul 14, 2014 at 6:51 PM, Steven Yi <stevenyi@gmail.com> wrote: Hi Art, The only things I can imagine are: 1. Could you uninstall csound6, then install to the default location (in C:\Program Files) 2. Could you also try with nchnls=2? Other than that, I'm not really sure what to check. Perhaps Michael might have some ideas. steven On Mon, Jul 14, 2014 at 6:42 PM, Art Hunkins <abhunkin@uncg.edu> wrote: > Steven, > > Thanks for the suggestions. > > Csound 5.19 is not installed (perhaps never was, I don't recall). It, and > any other Csound has been long uninstalled. I'm always particularly careful > to doublecheck environment variables, and clean where necessary.) Just to be > absolutely sure, a few minutes ago I did a complete cleaning of my Windows 7 > machine of everything Csound, and did a clean reinstall (from Michael's > 6.03.2 installer). Results are the same, and the complete console output is > attached. The single apparently relevent line of a verbose output is > referenced in my previous email (this output is otherwise horrendously > long). > > I much appreciate your feedback. > > Art Hunkins > > ----- Original Message ----- From: "Steven Yi" <stevenyi@gmail.com> > To: "Csound" <csound@lists.bath.ac.uk> > Sent: Saturday, July 12, 2014 9:24 AM > Subject: Re: [Csnd] Realtime Csound6 on Windows System 7 > > > >> Hi Art, >> >> Do you have both Csound 5.19 and Csound 6 installed? If so, what >> order did you install them in? I wonder if a library from 5.19 is >> getting picked up when running CS6. Also, could you give the full >> output from when running the CSD? >> >> steven >> >> On Thu, Jul 10, 2014 at 10:12 PM, Art Hunkins <abhunkin@uncg.edu> wrote: >>> >>> I've been unable to run realtime Csound6.03.2 (or any Csound6 for that >>> matter) on my desktop Windows System 7. (All my installations are from >>> the >>> Windows installers.) >>> >>> The compile seems OK, but runtime ends (verbose mode) with: >>> SECTION 1: >>> new event: 0.0000000000000 0.0000000000000 >>> Csound tidy up: Illegal instruction >>> >>> I'm running from the console in the \bin directory where the following >>> file >>> is located (and command line is: csound Test.csd): >>> --------------------------------------------------- >>> <CsoundSynthesizer> >>> <CsOptions> >>> >>> -odac >>> >>> </CsOptions> >>> <CsInstruments> >>> >>> sr = 44100 >>> kr = 4410 >>> ksmps = 10 >>> nchnls = 1 >>> >>> instr 1 >>> >>> a1 lfo 5000, 440 >>> out a1 >>> >>> endin >>> >>> </CsInstruments> >>> <CsScore> >>> >>> i 1 0 3 >>> >>> e >>> >>> </CsScore> >>> </CsoundSynthesizer> >>> ----------------------------------------------------- >>> Can someone suggest what might be going wrong? The file runs fine with >>> Csound5.19. >>> >>> Art Hunkins >>> >>> >>> Send bugs reports to >>> https://github.com/csound/csound/issues >>> Discussions of bugs and features can be posted here >>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe >>> csound" >>> >>> >>> >> >> >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here >> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe >> csound" >> >> >> > > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe > csound" > > > Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Date	2014-07-16 02:23
From	Michael Gogins
Subject	Re: [Csnd] Realtime Csound6 on Windows System 7
	I see two potential problems. One is that according to the Dependency Walker, py.dll, which contains the Csound Python opcodes, is looking for Python 2.7. Either remove the py.dll file, or install Python 2.7 32 bit version. The other potential problem is that you are running the following operating system: Microsoft Windows NT/2000/XP/2003/Vista based Media Center (32-bit), version 6.01.7601 Service Pack 1. This appears to be a 32 bit operating system. I think it might be the "personal edition" of Windows 7, which isn't really Windows 7 at all. Windows 7 and 8 are normally 64 bit/32 bit operating systems. I don't think this is the problem in your case however, I think your OS should be able to run this build of Csound. I think the warnings about files whose names start with API-MS-WIN- can safely be ignored. But I could be wrong. Try moving the py.dll file away first. Regards, Mike On Jul 15, 2014 8:42 PM, "Art Hunkins" <abhunkin@uncg.edu> wrote: Hi Michael, I have followed up on your suggestions, on my Windows 7 desktop. 1) No competing libsndfile or portaudio DLLs exist. 2) Changing PATH to what you suggest made no difference. 3) Going the depends.exe route yielded results. The image yielded by profiling Test.csd within Csound is attached (if does not come through to you, please advise; the list will receive this message without the sizeable attachment). There appear to be multiple problems (in red type). Probably they will indicate to you what has been going on. Two additional observations: 4) I notice that previously I had installed your 6.02 edition (I found this Setup download still among my files - though 6.02 had been thoroughly uninstalled before installing 6.03.2.) I don't this this matters, but who knows . . . 5) A curious thing happened when I downloaded and attempted to unzip (with WinZip) the depends archive (depends32_x86). I wasn't authorized to extract it (though I'm the admin). Tried multiple times to several locations; I ended up running it from within WinZip, which seemed to work just fine. This particular machine seems to have some peculiar quirks about it, and I am not the original owner. So, another "who knows" . . . Please let me know of any diagnosis! Thanks so much - Art Hunkins ----- Original Message ----- From: Michael Gogins To: Csound Sent: Monday, July 14, 2014 7:15 PM Subject: Re: [Csnd] Realtime Csound6 on Windows System 7 I just tried Art's test CSD on my Windows 8 machine where I built it, but in the installation environment. It worked fine. I'm afraid I don't have a clear idea what's going on here. Possibly there is some DLL conflict. You can try to get a handle on this by using depends.exe from here: http://www.dependencywalker.com/ First try just loading csound.exe into depends. Then try running your file using the "profile" menu. I have seen DLL conflicts with Reaper, which uses different builds of some of the same DLLs that Csound uses. Another, perhaps easier way of getting a handle on this is to temporarily change your Windows PATH environment variable to include only the Csound bin directory. If the problem goes away in that case, it means that either Csound, or one of Csound's DLLs, tried to load a DLL that conflicted with one that was already loaded, or that was built wrong for Csound. Another idea is to look and see if some other program has installed its own portaudio DLL or libsndfile DLL which conflicts. Some of the mingw or gtk DLLs (in the Csound bin directory) may also conflict. Hope this helps, Mike ----------------------------------------------------- Michael Gogins Irreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com On Mon, Jul 14, 2014 at 6:51 PM, Steven Yi <stevenyi@gmail.com> wrote: Hi Art, The only things I can imagine are: 1. Could you uninstall csound6, then install to the default location (in C:\Program Files) 2. Could you also try with nchnls=2? Other than that, I'm not really sure what to check. Perhaps Michael might have some ideas. steven On Mon, Jul 14, 2014 at 6:42 PM, Art Hunkins <abhunkin@uncg.edu> wrote: > Steven, > > Thanks for the suggestions. > > Csound 5.19 is not installed (perhaps never was, I don't recall). It, and > any other Csound has been long uninstalled. I'm always particularly careful > to doublecheck environment variables, and clean where necessary.) Just to be > absolutely sure, a few minutes ago I did a complete cleaning of my Windows 7 > machine of everything Csound, and did a clean reinstall (from Michael's > 6.03.2 installer). Results are the same, and the complete console output is > attached. The single apparently relevent line of a verbose output is > referenced in my previous email (this output is otherwise horrendously > long). > > I much appreciate your feedback. > > Art Hunkins > > ----- Original Message ----- From: "Steven Yi" <stevenyi@gmail.com> > To: "Csound" <csound@lists.bath.ac.uk> > Sent: Saturday, July 12, 2014 9:24 AM > Subject: Re: [Csnd] Realtime Csound6 on Windows System 7 > > > >> Hi Art, >> >> Do you have both Csound 5.19 and Csound 6 installed? If so, what >> order did you install them in? I wonder if a library from 5.19 is >> getting picked up when running CS6. Also, could you give the full >> output from when running the CSD? >> >> steven >> >> On Thu, Jul 10, 2014 at 10:12 PM, Art Hunkins <abhunkin@uncg.edu> wrote: >>> >>> I've been unable to run realtime Csound6.03.2 (or any Csound6 for that >>> matter) on my desktop Windows System 7. (All my installations are from >>> the >>> Windows installers.) >>> >>> The compile seems OK, but runtime ends (verbose mode) with: >>> SECTION 1: >>> new event: 0.0000000000000 0.0000000000000 >>> Csound tidy up: Illegal instruction >>> >>> I'm running from the console in the \bin directory where the following >>> file >>> is located (and command line is: csound Test.csd): >>> --------------------------------------------------- >>> <CsoundSynthesizer> >>> <CsOptions> >>> >>> -odac >>> >>> </CsOptions> >>> <CsInstruments> >>> >>> sr = 44100 >>> kr = 4410 >>> ksmps = 10 >>> nchnls = 1 >>> >>> instr 1 >>> >>> a1 lfo 5000, 440 >>> out a1 >>> >>> endin >>> >>> </CsInstruments> >>> <CsScore> >>> >>> i 1 0 3 >>> >>> e >>> >>> </CsScore> >>> </CsoundSynthesizer> >>> ----------------------------------------------------- >>> Can someone suggest what might be going wrong? The file runs fine with >>> Csound5.19. >>> >>> Art Hunkins >>> >>> >>> Send bugs reports to >>> https://github.com/csound/csound/issues >>> Discussions of bugs and features can be posted here >>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe >>> csound" >>> >>> >>> >> >> >> Send bugs reports to >> https://github.com/csound/csound/issues >> Discussions of bugs and features can be posted here >> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe >> csound" >> >> >> > > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe > csound" > > > Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"