Csound Csound-dev Csound-tekno Search About

[Csnd] Upgrading from 6.06 to 6.12

Date2019-06-05 23:17
FromMichael Saunders
Subject[Csnd] Upgrading from 6.06 to 6.12
I've been using 6.06 since it came out (on Windows 7,CsoundQT).  I've
written reams of code for it, doing lots of fancy things.  It was all
working fine, very stable.  I tried upgrading to 6.12.  I can't get it
to run usefully.  My orchestra begins with a series of #include
statements.  I've been trying to add my old orchestra line by line,
just trying to get it to run, one #include line, then another.
Sometimes the very same code compiles, or locks, or crashes.  For a
while, I found that an included text file would cause CsoundQT to
crash until I opened it and saved it.  Then it would be accepted.
That doesn't always work, though.  I haven't gotten close to getting
my beloved old code running.

Right now I'd do anything to have my old installation back.  I've
tried re-installing 6.06 and I'm encountering the same problems.

-- m

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2019-06-05 23:35
FromJohn ff
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
Can you please send an example of the problem?  It is hard to fix issues without details.

Sent from TypeApp
On 5 Jun 2019, at 23:18, Michael Saunders <odradek5@gmail.com> wrote:
I've been using 6.06 since it came out (on Windows 7,CsoundQT).  I've
written reams of code for it, doing lots of fancy things. It was all
working fine, very stable. I tried upgrading to 6.12. I can't get it
to run usefully. My orchestra begins with a series of #include
statements. I've been trying to add my old orchestra line by line,
just trying to get it to run, one #include line, then another.
Sometimes the very same code compiles, or locks, or crashes. For a
while, I found that an included text file would cause CsoundQT to
crash until I opened it and saved it. Then it would be accepted.
That doesn't always work, though. I haven't gotten close to getting
my beloved old code running.

Right now I'd do anything to have my old installation back. I've
tried re-installing 6.06 and I'm encountering the same problems.

-- m

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2019-06-05 23:58
FromMichael Saunders
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
I've encountered many errors and strange behaviors so far.  I'm
struggling to find a minimal example that would be of any use.  I
think that the problem is probably that I haven't set up my
installation properly rather than some code having been broken by the
upgrade.  At the moment, my csd file is the first few lines of my old
orchestra.:





-m642 --expression-opt -+rtaudio=null -+rtmidi=null -o out.wav






sr = 96000

kr = 96000

ksmps = 1

nchnls = 2

0dbfs=1

;THE FOLLOWING UNFORTUNATE BLOCK IS TEMP. UNTIL pp/np FIXED

gitempo=60 ;and in the -t switch above, don't forget

gitempoF=60/gitempo

;THE ABOVE ONLY UNTIL pp/np FIXED


;global variables that have to happen before Init:

giaccord=50;where accordatura table numbers start

gichords=70;where the chord channel ftables start

gimodes=80;where the mode channel ftables start

giperf=100;where performer/style table numbers start

giinstr=300;where instrument characteristic table numbers start

giformants=600;instrumental formant table numbers start (+1000 for rnd eqs)

givformants=900;where vocal formant table numbers start

;includes that can go in a meta-include file?:

#include "inc\Init.txt"

#include "inc\instruments.txt"







e







-----When I run this in CsoundQT it locks up.  On the previous run, it
accepted the line:
#include "inc\Init.txt"
So I added the next one:
#include "inc\instruments.txt"
On other occasions, it has accepted a dozen further #include
statements.  On some occasions, it freezes on the first one.  I don't
think this is a consequence of anything in those files.  As far as I
know, the only syntactic changes I've had to make are two instances of
i(k[x]) which I changed to i(k,x).   Thanks for looking at this
problem.  I have a lot of work invested in my old code and I feel lost
at sea here.

-- m

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2019-06-06 00:06
FromDave Seidel
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
Keep in mind that what may not run in CsoundQT might run fine in Csound. They are entirely different programs. You should try running using the "Run in terminal" option in CsoundQT.

On Wed, Jun 5, 2019 at 6:58 PM Michael Saunders <odradek5@gmail.com> wrote:
I've encountered many errors and strange behaviors so far.  I'm
struggling to find a minimal example that would be of any use.  I
think that the problem is probably that I haven't set up my
installation properly rather than some code having been broken by the
upgrade.  At the moment, my csd file is the first few lines of my old
orchestra.:

<CsoundSynthesizer>

<CsOptions>

-m642 --expression-opt -+rtaudio=null -+rtmidi=null -o out.wav

</CsOptions>

<CsInstruments>


sr = 96000

kr = 96000

ksmps = 1

nchnls = 2

0dbfs=1

;THE FOLLOWING UNFORTUNATE BLOCK IS TEMP. UNTIL pp/np FIXED

gitempo=60 ;and in the -t switch above, don't forget

gitempoF=60/gitempo

;THE ABOVE ONLY UNTIL pp/np FIXED


;global variables that have to happen before Init:

giaccord=50;where accordatura table numbers start

gichords=70;where the chord channel ftables start

gimodes=80;where the mode channel ftables start

giperf=100;where performer/style table numbers start

giinstr=300;where instrument characteristic table numbers start

giformants=600;instrumental formant table numbers start (+1000 for rnd eqs)

givformants=900;where vocal formant table numbers start

;includes that can go in a meta-include file?:

#include "inc\Init.txt"

#include "inc\instruments.txt"


</CsInstruments>

<CsScore>


e


</CsScore>

</CsoundSynthesizer>


-----When I run this in CsoundQT it locks up.  On the previous run, it
accepted the line:
#include "inc\Init.txt"
So I added the next one:
#include "inc\instruments.txt"
On other occasions, it has accepted a dozen further #include
statements.  On some occasions, it freezes on the first one.  I don't
think this is a consequence of anything in those files.  As far as I
know, the only syntactic changes I've had to make are two instances of
i(k[x]) which I changed to i(k,x).   Thanks for looking at this
problem.  I have a lot of work invested in my old code and I feel lost
at sea here.

-- m

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here


--
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2019-06-06 00:24
FromMichael Saunders
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
Thank you, Dave.  I'm trying to figure out how to do that.  I opened a
command prompt and entered a line from a batch file that was working
this morning:

csound -Z -m642 --expression-opt -+rtaudio=null -+rtmidi=null -o
out64.wav testbed.csd

...and get some output, the significant line of which reads: "Reading
CSD failed (No such file or directory.)... stopping"

-- m

On Wed, Jun 5, 2019 at 7:07 PM Dave Seidel  wrote:
>
> Keep in mind that what may not run in CsoundQT might run fine in Csound. They are entirely different programs. You should try running using the "Run in terminal" option in CsoundQT.
>
> On Wed, Jun 5, 2019 at 6:58 PM Michael Saunders  wrote:
>>
>> I've encountered many errors and strange behaviors so far.  I'm
>> struggling to find a minimal example that would be of any use.  I
>> think that the problem is probably that I haven't set up my
>> installation properly rather than some code having been broken by the
>> upgrade.  At the moment, my csd file is the first few lines of my old
>> orchestra.:
>>
>> 
>>
>> 
>>
>> -m642 --expression-opt -+rtaudio=null -+rtmidi=null -o out.wav
>>
>> 
>>
>> 
>>
>>
>> sr = 96000
>>
>> kr = 96000
>>
>> ksmps = 1
>>
>> nchnls = 2
>>
>> 0dbfs=1
>>
>> ;THE FOLLOWING UNFORTUNATE BLOCK IS TEMP. UNTIL pp/np FIXED
>>
>> gitempo=60 ;and in the -t switch above, don't forget
>>
>> gitempoF=60/gitempo
>>
>> ;THE ABOVE ONLY UNTIL pp/np FIXED
>>
>>
>> ;global variables that have to happen before Init:
>>
>> giaccord=50;where accordatura table numbers start
>>
>> gichords=70;where the chord channel ftables start
>>
>> gimodes=80;where the mode channel ftables start
>>
>> giperf=100;where performer/style table numbers start
>>
>> giinstr=300;where instrument characteristic table numbers start
>>
>> giformants=600;instrumental formant table numbers start (+1000 for rnd eqs)
>>
>> givformants=900;where vocal formant table numbers start
>>
>> ;includes that can go in a meta-include file?:
>>
>> #include "inc\Init.txt"
>>
>> #include "inc\instruments.txt"
>>
>>
>> 
>>
>> 
>>
>>
>> e
>>
>>
>> 
>>
>> 
>>
>>
>> -----When I run this in CsoundQT it locks up.  On the previous run, it
>> accepted the line:
>> #include "inc\Init.txt"
>> So I added the next one:
>> #include "inc\instruments.txt"
>> On other occasions, it has accepted a dozen further #include
>> statements.  On some occasions, it freezes on the first one.  I don't
>> think this is a consequence of anything in those files.  As far as I
>> know, the only syntactic changes I've had to make are two instances of
>> i(k[x]) which I changed to i(k,x).   Thanks for looking at this
>> problem.  I have a lot of work invested in my old code and I feel lost
>> at sea here.
>>
>> -- m
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
>
>
> --
> http://mysterybear.net
> https://soundcloud.com/mysterybear
> https://mysterybear.bandcamp.com
> https://www.youtube.com/channel/UCo0--3uN5ycq_aupZXskBgA
>
> http://recordings.irritablehedgehog.com/album/dave-seidel-60-hz
> Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2019-06-06 00:43
FromDave Seidel
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
Select "Run in Terminal" from the CsoundQT Control menu. Otherwise you must either be in the directory where your CSD(s) reside, or you have to provide full paths to those files on the Csound command line.

On Wed, Jun 5, 2019 at 7:24 PM Michael Saunders <odradek5@gmail.com> wrote:
Thank you, Dave.  I'm trying to figure out how to do that.  I opened a
command prompt and entered a line from a batch file that was working
this morning:

csound -Z -m642 --expression-opt -+rtaudio=null -+rtmidi=null -o
out64.wav testbed.csd

...and get some output, the significant line of which reads: "Reading
CSD failed (No such file or directory.)... stopping"

-- m

On Wed, Jun 5, 2019 at 7:07 PM Dave Seidel <dave.seidel@gmail.com> wrote:
>
> Keep in mind that what may not run in CsoundQT might run fine in Csound. They are entirely different programs. You should try running using the "Run in terminal" option in CsoundQT.
>
> On Wed, Jun 5, 2019 at 6:58 PM Michael Saunders <odradek5@gmail.com> wrote:
>>
>> I've encountered many errors and strange behaviors so far.  I'm
>> struggling to find a minimal example that would be of any use.  I
>> think that the problem is probably that I haven't set up my
>> installation properly rather than some code having been broken by the
>> upgrade.  At the moment, my csd file is the first few lines of my old
>> orchestra.:
>>
>> <CsoundSynthesizer>
>>
>> <CsOptions>
>>
>> -m642 --expression-opt -+rtaudio=null -+rtmidi=null -o out.wav
>>
>> </CsOptions>
>>
>> <CsInstruments>
>>
>>
>> sr = 96000
>>
>> kr = 96000
>>
>> ksmps = 1
>>
>> nchnls = 2
>>
>> 0dbfs=1
>>
>> ;THE FOLLOWING UNFORTUNATE BLOCK IS TEMP. UNTIL pp/np FIXED
>>
>> gitempo=60 ;and in the -t switch above, don't forget
>>
>> gitempoF=60/gitempo
>>
>> ;THE ABOVE ONLY UNTIL pp/np FIXED
>>
>>
>> ;global variables that have to happen before Init:
>>
>> giaccord=50;where accordatura table numbers start
>>
>> gichords=70;where the chord channel ftables start
>>
>> gimodes=80;where the mode channel ftables start
>>
>> giperf=100;where performer/style table numbers start
>>
>> giinstr=300;where instrument characteristic table numbers start
>>
>> giformants=600;instrumental formant table numbers start (+1000 for rnd eqs)
>>
>> givformants=900;where vocal formant table numbers start
>>
>> ;includes that can go in a meta-include file?:
>>
>> #include "inc\Init.txt"
>>
>> #include "inc\instruments.txt"
>>
>>
>> </CsInstruments>
>>
>> <CsScore>
>>
>>
>> e
>>
>>
>> </CsScore>
>>
>> </CsoundSynthesizer>
>>
>>
>> -----When I run this in CsoundQT it locks up.  On the previous run, it
>> accepted the line:
>> #include "inc\Init.txt"
>> So I added the next one:
>> #include "inc\instruments.txt"
>> On other occasions, it has accepted a dozen further #include
>> statements.  On some occasions, it freezes on the first one.  I don't
>> think this is a consequence of anything in those files.  As far as I
>> know, the only syntactic changes I've had to make are two instances of
>> i(k[x]) which I changed to i(k,x).   Thanks for looking at this
>> problem.  I have a lot of work invested in my old code and I feel lost
>> at sea here.
>>
>> -- m
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
>
>
> --
> http://mysterybear.net
> https://soundcloud.com/mysterybear
> https://mysterybear.bandcamp.com
> https://www.youtube.com/channel/UCo0--3uN5ycq_aupZXskBgA
>
> http://recordings.irritablehedgehog.com/album/dave-seidel-60-hz
> Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here


--
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2019-06-06 01:36
FromMichael Saunders
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
Thank you.  I can't seem to "Run in Terminal"---it stumbles on a space
in the directory name.  However, I got my batch files working again
(not from CsoundQT), and 6.12 now accepts my orchestra without
protest.  I'm trying exactly the same .csd that worked this morning.
It runs for a while, apparently expanding many macros (the last line
reads, "defining argument 'i''o as...#2#") and then I get the familiar
pop up: "Csound has stopped working".  It's very hard to get a minimal
example out of this.

On Wed, Jun 5, 2019 at 7:43 PM Dave Seidel  wrote:
>
> Select "Run in Terminal" from the CsoundQT Control menu. Otherwise you must either be in the directory where your CSD(s) reside, or you have to provide full paths to those files on the Csound command line.
>
> On Wed, Jun 5, 2019 at 7:24 PM Michael Saunders  wrote:
>>
>> Thank you, Dave.  I'm trying to figure out how to do that.  I opened a
>> command prompt and entered a line from a batch file that was working
>> this morning:
>>
>> csound -Z -m642 --expression-opt -+rtaudio=null -+rtmidi=null -o
>> out64.wav testbed.csd
>>
>> ...and get some output, the significant line of which reads: "Reading
>> CSD failed (No such file or directory.)... stopping"
>>
>> -- m
>>
>> On Wed, Jun 5, 2019 at 7:07 PM Dave Seidel  wrote:
>> >
>> > Keep in mind that what may not run in CsoundQT might run fine in Csound. They are entirely different programs. You should try running using the "Run in terminal" option in CsoundQT.
>> >
>> > On Wed, Jun 5, 2019 at 6:58 PM Michael Saunders  wrote:
>> >>
>> >> I've encountered many errors and strange behaviors so far.  I'm
>> >> struggling to find a minimal example that would be of any use.  I
>> >> think that the problem is probably that I haven't set up my
>> >> installation properly rather than some code having been broken by the
>> >> upgrade.  At the moment, my csd file is the first few lines of my old
>> >> orchestra.:
>> >>
>> >> 
>> >>
>> >> 
>> >>
>> >> -m642 --expression-opt -+rtaudio=null -+rtmidi=null -o out.wav
>> >>
>> >> 
>> >>
>> >> 
>> >>
>> >>
>> >> sr = 96000
>> >>
>> >> kr = 96000
>> >>
>> >> ksmps = 1
>> >>
>> >> nchnls = 2
>> >>
>> >> 0dbfs=1
>> >>
>> >> ;THE FOLLOWING UNFORTUNATE BLOCK IS TEMP. UNTIL pp/np FIXED
>> >>
>> >> gitempo=60 ;and in the -t switch above, don't forget
>> >>
>> >> gitempoF=60/gitempo
>> >>
>> >> ;THE ABOVE ONLY UNTIL pp/np FIXED
>> >>
>> >>
>> >> ;global variables that have to happen before Init:
>> >>
>> >> giaccord=50;where accordatura table numbers start
>> >>
>> >> gichords=70;where the chord channel ftables start
>> >>
>> >> gimodes=80;where the mode channel ftables start
>> >>
>> >> giperf=100;where performer/style table numbers start
>> >>
>> >> giinstr=300;where instrument characteristic table numbers start
>> >>
>> >> giformants=600;instrumental formant table numbers start (+1000 for rnd eqs)
>> >>
>> >> givformants=900;where vocal formant table numbers start
>> >>
>> >> ;includes that can go in a meta-include file?:
>> >>
>> >> #include "inc\Init.txt"
>> >>
>> >> #include "inc\instruments.txt"
>> >>
>> >>
>> >> 
>> >>
>> >> 
>> >>
>> >>
>> >> e
>> >>
>> >>
>> >> 
>> >>
>> >> 
>> >>
>> >>
>> >> -----When I run this in CsoundQT it locks up.  On the previous run, it
>> >> accepted the line:
>> >> #include "inc\Init.txt"
>> >> So I added the next one:
>> >> #include "inc\instruments.txt"
>> >> On other occasions, it has accepted a dozen further #include
>> >> statements.  On some occasions, it freezes on the first one.  I don't
>> >> think this is a consequence of anything in those files.  As far as I
>> >> know, the only syntactic changes I've had to make are two instances of
>> >> i(k[x]) which I changed to i(k,x).   Thanks for looking at this
>> >> problem.  I have a lot of work invested in my old code and I feel lost
>> >> at sea here.
>> >>
>> >> -- m
>> >>
>> >> Csound mailing list
>> >> Csound@listserv.heanet.ie
>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >> Send bugs reports to
>> >>         https://github.com/csound/csound/issues
>> >> Discussions of bugs and features can be posted here
>> >
>> >
>> >
>> > --
>> > http://mysterybear.net
>> > https://soundcloud.com/mysterybear
>> > https://mysterybear.bandcamp.com
>> > https://www.youtube.com/channel/UCo0--3uN5ycq_aupZXskBgA
>> >
>> > http://recordings.irritablehedgehog.com/album/dave-seidel-60-hz
>> > Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
>
>
> --
> http://mysterybear.net
> https://soundcloud.com/mysterybear
> https://mysterybear.bandcamp.com
> https://www.youtube.com/channel/UCo0--3uN5ycq_aupZXskBgA
>
> http://recordings.irritablehedgehog.com/album/dave-seidel-60-hz
> Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2019-06-06 05:07
FromTarmo Johannes
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
One reason might be, as you suggested that there is a mix of some old and new component  in your install. Did you try to already to delete or rename completely  Program Files/Csound_x64 and reinstall?
Tarmo

N, 6. juuni 2019 03:37 Michael Saunders <odradek5@gmail.com> kirjutas:
Thank you.  I can't seem to "Run in Terminal"---it stumbles on a space
in the directory name.  However, I got my batch files working again
(not from CsoundQT), and 6.12 now accepts my orchestra without
protest.  I'm trying exactly the same .csd that worked this morning.
It runs for a while, apparently expanding many macros (the last line
reads, "defining argument 'i''o as...#2#") and then I get the familiar
pop up: "Csound has stopped working".  It's very hard to get a minimal
example out of this.

On Wed, Jun 5, 2019 at 7:43 PM Dave Seidel <dave.seidel@gmail.com> wrote:
>
> Select "Run in Terminal" from the CsoundQT Control menu. Otherwise you must either be in the directory where your CSD(s) reside, or you have to provide full paths to those files on the Csound command line.
>
> On Wed, Jun 5, 2019 at 7:24 PM Michael Saunders <odradek5@gmail.com> wrote:
>>
>> Thank you, Dave.  I'm trying to figure out how to do that.  I opened a
>> command prompt and entered a line from a batch file that was working
>> this morning:
>>
>> csound -Z -m642 --expression-opt -+rtaudio=null -+rtmidi=null -o
>> out64.wav testbed.csd
>>
>> ...and get some output, the significant line of which reads: "Reading
>> CSD failed (No such file or directory.)... stopping"
>>
>> -- m
>>
>> On Wed, Jun 5, 2019 at 7:07 PM Dave Seidel <dave.seidel@gmail.com> wrote:
>> >
>> > Keep in mind that what may not run in CsoundQT might run fine in Csound. They are entirely different programs. You should try running using the "Run in terminal" option in CsoundQT.
>> >
>> > On Wed, Jun 5, 2019 at 6:58 PM Michael Saunders <odradek5@gmail.com> wrote:
>> >>
>> >> I've encountered many errors and strange behaviors so far.  I'm
>> >> struggling to find a minimal example that would be of any use.  I
>> >> think that the problem is probably that I haven't set up my
>> >> installation properly rather than some code having been broken by the
>> >> upgrade.  At the moment, my csd file is the first few lines of my old
>> >> orchestra.:
>> >>
>> >> <CsoundSynthesizer>
>> >>
>> >> <CsOptions>
>> >>
>> >> -m642 --expression-opt -+rtaudio=null -+rtmidi=null -o out.wav
>> >>
>> >> </CsOptions>
>> >>
>> >> <CsInstruments>
>> >>
>> >>
>> >> sr = 96000
>> >>
>> >> kr = 96000
>> >>
>> >> ksmps = 1
>> >>
>> >> nchnls = 2
>> >>
>> >> 0dbfs=1
>> >>
>> >> ;THE FOLLOWING UNFORTUNATE BLOCK IS TEMP. UNTIL pp/np FIXED
>> >>
>> >> gitempo=60 ;and in the -t switch above, don't forget
>> >>
>> >> gitempoF=60/gitempo
>> >>
>> >> ;THE ABOVE ONLY UNTIL pp/np FIXED
>> >>
>> >>
>> >> ;global variables that have to happen before Init:
>> >>
>> >> giaccord=50;where accordatura table numbers start
>> >>
>> >> gichords=70;where the chord channel ftables start
>> >>
>> >> gimodes=80;where the mode channel ftables start
>> >>
>> >> giperf=100;where performer/style table numbers start
>> >>
>> >> giinstr=300;where instrument characteristic table numbers start
>> >>
>> >> giformants=600;instrumental formant table numbers start (+1000 for rnd eqs)
>> >>
>> >> givformants=900;where vocal formant table numbers start
>> >>
>> >> ;includes that can go in a meta-include file?:
>> >>
>> >> #include "inc\Init.txt"
>> >>
>> >> #include "inc\instruments.txt"
>> >>
>> >>
>> >> </CsInstruments>
>> >>
>> >> <CsScore>
>> >>
>> >>
>> >> e
>> >>
>> >>
>> >> </CsScore>
>> >>
>> >> </CsoundSynthesizer>
>> >>
>> >>
>> >> -----When I run this in CsoundQT it locks up.  On the previous run, it
>> >> accepted the line:
>> >> #include "inc\Init.txt"
>> >> So I added the next one:
>> >> #include "inc\instruments.txt"
>> >> On other occasions, it has accepted a dozen further #include
>> >> statements.  On some occasions, it freezes on the first one.  I don't
>> >> think this is a consequence of anything in those files.  As far as I
>> >> know, the only syntactic changes I've had to make are two instances of
>> >> i(k[x]) which I changed to i(k,x).   Thanks for looking at this
>> >> problem.  I have a lot of work invested in my old code and I feel lost
>> >> at sea here.
>> >>
>> >> -- m
>> >>
>> >> Csound mailing list
>> >> Csound@listserv.heanet.ie
>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >> Send bugs reports to
>> >>         https://github.com/csound/csound/issues
>> >> Discussions of bugs and features can be posted here
>> >
>> >
>> >
>> > --
>> > http://mysterybear.net
>> > https://soundcloud.com/mysterybear
>> > https://mysterybear.bandcamp.com
>> > https://www.youtube.com/channel/UCo0--3uN5ycq_aupZXskBgA
>> >
>> > http://recordings.irritablehedgehog.com/album/dave-seidel-60-hz
>> > Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
>
>
> --
> http://mysterybear.net
> https://soundcloud.com/mysterybear
> https://mysterybear.bandcamp.com
> https://www.youtube.com/channel/UCo0--3uN5ycq_aupZXskBgA
>
> http://recordings.irritablehedgehog.com/album/dave-seidel-60-hz
> Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2019-06-06 05:17
FromMichael Saunders
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
Thanks, yes, I completely removed the old installation.

I've been tinkering with this all night.  I find that:
1. one of my output routines (binaural) works, but sounds different
than before and is about 10 times louder.
2. Sometimes innocuous changes to its parameters crash it.
3. My other output routine (transaural, ambisonic), produces only silence.
4. A large and important class of my instruments crash.

I've looked through the relevant "what's new" sections in the manual
and don't see any changes that could have broken my code, though I
could have missed something.  I'm wondering whether I should try to
find the source of all these problems (about which I have no leads) or
try to revert to 6.06 (I don't know where to find the appropriate
windows installers).  I thought the backwards compatibility was strong
with Csound.  I don't know what's going wrong here.

-- m



On Thu, Jun 6, 2019 at 12:08 AM Tarmo Johannes  wrote:
>
> One reason might be, as you suggested that there is a mix of some old and new component  in your install. Did you try to already to delete or rename completely  Program Files/Csound_x64 and reinstall?
> Tarmo
>
> N, 6. juuni 2019 03:37 Michael Saunders  kirjutas:
>>
>> Thank you.  I can't seem to "Run in Terminal"---it stumbles on a space
>> in the directory name.  However, I got my batch files working again
>> (not from CsoundQT), and 6.12 now accepts my orchestra without
>> protest.  I'm trying exactly the same .csd that worked this morning.
>> It runs for a while, apparently expanding many macros (the last line
>> reads, "defining argument 'i''o as...#2#") and then I get the familiar
>> pop up: "Csound has stopped working".  It's very hard to get a minimal
>> example out of this.
>>
>> On Wed, Jun 5, 2019 at 7:43 PM Dave Seidel  wrote:
>> >
>> > Select "Run in Terminal" from the CsoundQT Control menu. Otherwise you must either be in the directory where your CSD(s) reside, or you have to provide full paths to those files on the Csound command line.
>> >
>> > On Wed, Jun 5, 2019 at 7:24 PM Michael Saunders  wrote:
>> >>
>> >> Thank you, Dave.  I'm trying to figure out how to do that.  I opened a
>> >> command prompt and entered a line from a batch file that was working
>> >> this morning:
>> >>
>> >> csound -Z -m642 --expression-opt -+rtaudio=null -+rtmidi=null -o
>> >> out64.wav testbed.csd
>> >>
>> >> ...and get some output, the significant line of which reads: "Reading
>> >> CSD failed (No such file or directory.)... stopping"
>> >>
>> >> -- m
>> >>
>> >> On Wed, Jun 5, 2019 at 7:07 PM Dave Seidel  wrote:
>> >> >
>> >> > Keep in mind that what may not run in CsoundQT might run fine in Csound. They are entirely different programs. You should try running using the "Run in terminal" option in CsoundQT.
>> >> >
>> >> > On Wed, Jun 5, 2019 at 6:58 PM Michael Saunders  wrote:
>> >> >>
>> >> >> I've encountered many errors and strange behaviors so far.  I'm
>> >> >> struggling to find a minimal example that would be of any use.  I
>> >> >> think that the problem is probably that I haven't set up my
>> >> >> installation properly rather than some code having been broken by the
>> >> >> upgrade.  At the moment, my csd file is the first few lines of my old
>> >> >> orchestra.:
>> >> >>
>> >> >> 
>> >> >>
>> >> >> 
>> >> >>
>> >> >> -m642 --expression-opt -+rtaudio=null -+rtmidi=null -o out.wav
>> >> >>
>> >> >> 
>> >> >>
>> >> >> 
>> >> >>
>> >> >>
>> >> >> sr = 96000
>> >> >>
>> >> >> kr = 96000
>> >> >>
>> >> >> ksmps = 1
>> >> >>
>> >> >> nchnls = 2
>> >> >>
>> >> >> 0dbfs=1
>> >> >>
>> >> >> ;THE FOLLOWING UNFORTUNATE BLOCK IS TEMP. UNTIL pp/np FIXED
>> >> >>
>> >> >> gitempo=60 ;and in the -t switch above, don't forget
>> >> >>
>> >> >> gitempoF=60/gitempo
>> >> >>
>> >> >> ;THE ABOVE ONLY UNTIL pp/np FIXED
>> >> >>
>> >> >>
>> >> >> ;global variables that have to happen before Init:
>> >> >>
>> >> >> giaccord=50;where accordatura table numbers start
>> >> >>
>> >> >> gichords=70;where the chord channel ftables start
>> >> >>
>> >> >> gimodes=80;where the mode channel ftables start
>> >> >>
>> >> >> giperf=100;where performer/style table numbers start
>> >> >>
>> >> >> giinstr=300;where instrument characteristic table numbers start
>> >> >>
>> >> >> giformants=600;instrumental formant table numbers start (+1000 for rnd eqs)
>> >> >>
>> >> >> givformants=900;where vocal formant table numbers start
>> >> >>
>> >> >> ;includes that can go in a meta-include file?:
>> >> >>
>> >> >> #include "inc\Init.txt"
>> >> >>
>> >> >> #include "inc\instruments.txt"
>> >> >>
>> >> >>
>> >> >> 
>> >> >>
>> >> >> 
>> >> >>
>> >> >>
>> >> >> e
>> >> >>
>> >> >>
>> >> >> 
>> >> >>
>> >> >> 
>> >> >>
>> >> >>
>> >> >> -----When I run this in CsoundQT it locks up.  On the previous run, it
>> >> >> accepted the line:
>> >> >> #include "inc\Init.txt"
>> >> >> So I added the next one:
>> >> >> #include "inc\instruments.txt"
>> >> >> On other occasions, it has accepted a dozen further #include
>> >> >> statements.  On some occasions, it freezes on the first one.  I don't
>> >> >> think this is a consequence of anything in those files.  As far as I
>> >> >> know, the only syntactic changes I've had to make are two instances of
>> >> >> i(k[x]) which I changed to i(k,x).   Thanks for looking at this
>> >> >> problem.  I have a lot of work invested in my old code and I feel lost
>> >> >> at sea here.
>> >> >>
>> >> >> -- m
>> >> >>
>> >> >> Csound mailing list
>> >> >> Csound@listserv.heanet.ie
>> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >> >> Send bugs reports to
>> >> >>         https://github.com/csound/csound/issues
>> >> >> Discussions of bugs and features can be posted here
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > http://mysterybear.net
>> >> > https://soundcloud.com/mysterybear
>> >> > https://mysterybear.bandcamp.com
>> >> > https://www.youtube.com/channel/UCo0--3uN5ycq_aupZXskBgA
>> >> >
>> >> > http://recordings.irritablehedgehog.com/album/dave-seidel-60-hz
>> >> > Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
>> >>
>> >> Csound mailing list
>> >> Csound@listserv.heanet.ie
>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >> Send bugs reports to
>> >>         https://github.com/csound/csound/issues
>> >> Discussions of bugs and features can be posted here
>> >
>> >
>> >
>> > --
>> > http://mysterybear.net
>> > https://soundcloud.com/mysterybear
>> > https://mysterybear.bandcamp.com
>> > https://www.youtube.com/channel/UCo0--3uN5ycq_aupZXskBgA
>> >
>> > http://recordings.irritablehedgehog.com/album/dave-seidel-60-hz
>> > Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
> Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2019-06-06 07:58
FromOeyvind Brandtsegg
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
Hello Michael,

This sounds like a frustrating situation indeed. It also sounds as if it is hard to be 100% sure of what causes the problems.
As one who have been stuck in similar situations many times, I thought I could offer some hints.
For this kind of "black box" debugging I find it useful to be very systematic and incremental in what I test. Otherwise the process become very unwieldy.

Running the process on the command line is essential to eliminate unneccessary clutter. If at all possible, I would try to run a simple csd (as simple as at all possible) directly on the command line as the first thing. Not "run in terminal" inside CsoundQt or any other front end. Just open the command line (command prompt in windows, if you hold down the windows key and press R, then you get the "run" dialog, here you type "cmd" (without the quotes) and press enter). Use "cd" (change directory) to move around your directory structure until you get to the directory where the csd file is. Then type "csound name-of-the-test-file.csd" (still without the quotes) and press enter. 

In some cases I would start top-down, with the whole project (csd) slashing it in half by removing the latter part of the code and see if that compiles without problems. Then continue up/down from there, depending on if it compiles and runs or not. It can be helpful to add a single sine oscillator somewhere in the code, with direct audio output, so that you can hear that the code runs and process audio normally. 

Then again, you case seems more severe, so a bottom-up approach might be more appropriate. Then, start with a simple csd containing just one sine oscillator, test run and listen to the audio, then add components from you problem orchestra one by one. Start with the elements from the beginning of the code. Later elements (later in the file) might depend on things defined earlier, so it can create problems if you try to go the other way around. First, add just the globals, test run. Then add instrument 1, test, and so on. When you get comfortable you can add larger chunks. 

In both cases, always write down the Csound version and what part of the code you have tested, and in what order the tests were made.
If you change the Csound version at some point, you have to start over with the testing.
If at any point you get confused, go back one step and test again. Keep track of what works and what does not.
If you get too confused and you are unsure about the hard facts, start over from the beginning.
Take breaks, look at it with "fresh eyes"
Do not assume anything (like "of course *that* does not cause a problem"...), just test blindly.
If you manage to not get frustrated by the slow progress, but take each confirmed step as a reward, then it can actually be quite satisfying when you inch toward a solution to a confusing problem. You might find there was a problem with Csound, your code, the install, or other parts of your system. Likely a combination.

Hope this can be a small amount of help that get you up and running again.
All best
Oeyvind

tor. 6. jun. 2019 kl. 06:17 skrev Michael Saunders <odradek5@gmail.com>:
Thanks, yes, I completely removed the old installation.

I've been tinkering with this all night.  I find that:
1. one of my output routines (binaural) works, but sounds different
than before and is about 10 times louder.
2. Sometimes innocuous changes to its parameters crash it.
3. My other output routine (transaural, ambisonic), produces only silence.
4. A large and important class of my instruments crash.

I've looked through the relevant "what's new" sections in the manual
and don't see any changes that could have broken my code, though I
could have missed something.  I'm wondering whether I should try to
find the source of all these problems (about which I have no leads) or
try to revert to 6.06 (I don't know where to find the appropriate
windows installers).  I thought the backwards compatibility was strong
with Csound.  I don't know what's going wrong here.

-- m



On Thu, Jun 6, 2019 at 12:08 AM Tarmo Johannes <trmjhnns@gmail.com> wrote:
>
> One reason might be, as you suggested that there is a mix of some old and new component  in your install. Did you try to already to delete or rename completely  Program Files/Csound_x64 and reinstall?
> Tarmo
>
> N, 6. juuni 2019 03:37 Michael Saunders <odradek5@gmail.com> kirjutas:
>>
>> Thank you.  I can't seem to "Run in Terminal"---it stumbles on a space
>> in the directory name.  However, I got my batch files working again
>> (not from CsoundQT), and 6.12 now accepts my orchestra without
>> protest.  I'm trying exactly the same .csd that worked this morning.
>> It runs for a while, apparently expanding many macros (the last line
>> reads, "defining argument 'i''o as...#2#") and then I get the familiar
>> pop up: "Csound has stopped working".  It's very hard to get a minimal
>> example out of this.
>>
>> On Wed, Jun 5, 2019 at 7:43 PM Dave Seidel <dave.seidel@gmail.com> wrote:
>> >
>> > Select "Run in Terminal" from the CsoundQT Control menu. Otherwise you must either be in the directory where your CSD(s) reside, or you have to provide full paths to those files on the Csound command line.
>> >
>> > On Wed, Jun 5, 2019 at 7:24 PM Michael Saunders <odradek5@gmail.com> wrote:
>> >>
>> >> Thank you, Dave.  I'm trying to figure out how to do that.  I opened a
>> >> command prompt and entered a line from a batch file that was working
>> >> this morning:
>> >>
>> >> csound -Z -m642 --expression-opt -+rtaudio=null -+rtmidi=null -o
>> >> out64.wav testbed.csd
>> >>
>> >> ...and get some output, the significant line of which reads: "Reading
>> >> CSD failed (No such file or directory.)... stopping"
>> >>
>> >> -- m
>> >>
>> >> On Wed, Jun 5, 2019 at 7:07 PM Dave Seidel <dave.seidel@gmail.com> wrote:
>> >> >
>> >> > Keep in mind that what may not run in CsoundQT might run fine in Csound. They are entirely different programs. You should try running using the "Run in terminal" option in CsoundQT.
>> >> >
>> >> > On Wed, Jun 5, 2019 at 6:58 PM Michael Saunders <odradek5@gmail.com> wrote:
>> >> >>
>> >> >> I've encountered many errors and strange behaviors so far.  I'm
>> >> >> struggling to find a minimal example that would be of any use.  I
>> >> >> think that the problem is probably that I haven't set up my
>> >> >> installation properly rather than some code having been broken by the
>> >> >> upgrade.  At the moment, my csd file is the first few lines of my old
>> >> >> orchestra.:
>> >> >>
>> >> >> <CsoundSynthesizer>
>> >> >>
>> >> >> <CsOptions>
>> >> >>
>> >> >> -m642 --expression-opt -+rtaudio=null -+rtmidi=null -o out.wav
>> >> >>
>> >> >> </CsOptions>
>> >> >>
>> >> >> <CsInstruments>
>> >> >>
>> >> >>
>> >> >> sr = 96000
>> >> >>
>> >> >> kr = 96000
>> >> >>
>> >> >> ksmps = 1
>> >> >>
>> >> >> nchnls = 2
>> >> >>
>> >> >> 0dbfs=1
>> >> >>
>> >> >> ;THE FOLLOWING UNFORTUNATE BLOCK IS TEMP. UNTIL pp/np FIXED
>> >> >>
>> >> >> gitempo=60 ;and in the -t switch above, don't forget
>> >> >>
>> >> >> gitempoF=60/gitempo
>> >> >>
>> >> >> ;THE ABOVE ONLY UNTIL pp/np FIXED
>> >> >>
>> >> >>
>> >> >> ;global variables that have to happen before Init:
>> >> >>
>> >> >> giaccord=50;where accordatura table numbers start
>> >> >>
>> >> >> gichords=70;where the chord channel ftables start
>> >> >>
>> >> >> gimodes=80;where the mode channel ftables start
>> >> >>
>> >> >> giperf=100;where performer/style table numbers start
>> >> >>
>> >> >> giinstr=300;where instrument characteristic table numbers start
>> >> >>
>> >> >> giformants=600;instrumental formant table numbers start (+1000 for rnd eqs)
>> >> >>
>> >> >> givformants=900;where vocal formant table numbers start
>> >> >>
>> >> >> ;includes that can go in a meta-include file?:
>> >> >>
>> >> >> #include "inc\Init.txt"
>> >> >>
>> >> >> #include "inc\instruments.txt"
>> >> >>
>> >> >>
>> >> >> </CsInstruments>
>> >> >>
>> >> >> <CsScore>
>> >> >>
>> >> >>
>> >> >> e
>> >> >>
>> >> >>
>> >> >> </CsScore>
>> >> >>
>> >> >> </CsoundSynthesizer>
>> >> >>
>> >> >>
>> >> >> -----When I run this in CsoundQT it locks up.  On the previous run, it
>> >> >> accepted the line:
>> >> >> #include "inc\Init.txt"
>> >> >> So I added the next one:
>> >> >> #include "inc\instruments.txt"
>> >> >> On other occasions, it has accepted a dozen further #include
>> >> >> statements.  On some occasions, it freezes on the first one.  I don't
>> >> >> think this is a consequence of anything in those files.  As far as I
>> >> >> know, the only syntactic changes I've had to make are two instances of
>> >> >> i(k[x]) which I changed to i(k,x).   Thanks for looking at this
>> >> >> problem.  I have a lot of work invested in my old code and I feel lost
>> >> >> at sea here.
>> >> >>
>> >> >> -- m
>> >> >>
>> >> >> Csound mailing list
>> >> >> Csound@listserv.heanet.ie
>> >> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >> >> Send bugs reports to
>> >> >>         https://github.com/csound/csound/issues
>> >> >> Discussions of bugs and features can be posted here
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > http://mysterybear.net
>> >> > https://soundcloud.com/mysterybear
>> >> > https://mysterybear.bandcamp.com
>> >> > https://www.youtube.com/channel/UCo0--3uN5ycq_aupZXskBgA
>> >> >
>> >> > http://recordings.irritablehedgehog.com/album/dave-seidel-60-hz
>> >> > Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
>> >>
>> >> Csound mailing list
>> >> Csound@listserv.heanet.ie
>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> >> Send bugs reports to
>> >>         https://github.com/csound/csound/issues
>> >> Discussions of bugs and features can be posted here
>> >
>> >
>> >
>> > --
>> > http://mysterybear.net
>> > https://soundcloud.com/mysterybear
>> > https://mysterybear.bandcamp.com
>> > https://www.youtube.com/channel/UCo0--3uN5ycq_aupZXskBgA
>> >
>> > http://recordings.irritablehedgehog.com/album/dave-seidel-60-hz
>> > Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
> Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here


--
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2019-06-06 11:11
FromJohn ff
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
If you use the -v option on the command line it spews out a lot of debugging information.  May be hard to decide but it should give some indication of where things stopped.  I think between 6.06 and 6.12 there was a change on Windows of the compiler used.

⁣Sent from TypeApp ​

On Jun 6, 2019, 01:38, at 01:38, Michael Saunders  wrote:
>Thank you.  I can't seem to "Run in Terminal"---it stumbles on a space
>in the directory name.  However, I got my batch files working again
>(not from CsoundQT), and 6.12 now accepts my orchestra without
>protest.  I'm trying exactly the same .csd that worked this morning.
>It runs for a while, apparently expanding many macros (the last line
>reads, "defining argument 'i''o as...#2#") and then I get the familiar
>pop up: "Csound has stopped working".  It's very hard to get a minimal
>example out of this.
>
>On Wed, Jun 5, 2019 at 7:43 PM Dave Seidel 
>wrote:
>>
>> Select "Run in Terminal" from the CsoundQT Control menu. Otherwise
>you must either be in the directory where your CSD(s) reside, or you
>have to provide full paths to those files on the Csound command line.
>>
>> On Wed, Jun 5, 2019 at 7:24 PM Michael Saunders 
>wrote:
>>>
>>> Thank you, Dave.  I'm trying to figure out how to do that.  I opened
>a
>>> command prompt and entered a line from a batch file that was working
>>> this morning:
>>>
>>> csound -Z -m642 --expression-opt -+rtaudio=null -+rtmidi=null -o
>>> out64.wav testbed.csd
>>>
>>> ...and get some output, the significant line of which reads:
>"Reading
>>> CSD failed (No such file or directory.)... stopping"
>>>
>>> -- m
>>>
>>> On Wed, Jun 5, 2019 at 7:07 PM Dave Seidel 
>wrote:
>>> >
>>> > Keep in mind that what may not run in CsoundQT might run fine in
>Csound. They are entirely different programs. You should try running
>using the "Run in terminal" option in CsoundQT.
>>> >
>>> > On Wed, Jun 5, 2019 at 6:58 PM Michael Saunders
> wrote:
>>> >>
>>> >> I've encountered many errors and strange behaviors so far.  I'm
>>> >> struggling to find a minimal example that would be of any use.  I
>>> >> think that the problem is probably that I haven't set up my
>>> >> installation properly rather than some code having been broken by
>the
>>> >> upgrade.  At the moment, my csd file is the first few lines of my
>old
>>> >> orchestra.:
>>> >>
>>> >> 
>>> >>
>>> >> 
>>> >>
>>> >> -m642 --expression-opt -+rtaudio=null -+rtmidi=null -o out.wav
>>> >>
>>> >> 
>>> >>
>>> >> 
>>> >>
>>> >>
>>> >> sr = 96000
>>> >>
>>> >> kr = 96000
>>> >>
>>> >> ksmps = 1
>>> >>
>>> >> nchnls = 2
>>> >>
>>> >> 0dbfs=1
>>> >>
>>> >> ;THE FOLLOWING UNFORTUNATE BLOCK IS TEMP. UNTIL pp/np FIXED
>>> >>
>>> >> gitempo=60 ;and in the -t switch above, don't forget
>>> >>
>>> >> gitempoF=60/gitempo
>>> >>
>>> >> ;THE ABOVE ONLY UNTIL pp/np FIXED
>>> >>
>>> >>
>>> >> ;global variables that have to happen before Init:
>>> >>
>>> >> giaccord=50;where accordatura table numbers start
>>> >>
>>> >> gichords=70;where the chord channel ftables start
>>> >>
>>> >> gimodes=80;where the mode channel ftables start
>>> >>
>>> >> giperf=100;where performer/style table numbers start
>>> >>
>>> >> giinstr=300;where instrument characteristic table numbers start
>>> >>
>>> >> giformants=600;instrumental formant table numbers start (+1000
>for rnd eqs)
>>> >>
>>> >> givformants=900;where vocal formant table numbers start
>>> >>
>>> >> ;includes that can go in a meta-include file?:
>>> >>
>>> >> #include "inc\Init.txt"
>>> >>
>>> >> #include "inc\instruments.txt"
>>> >>
>>> >>
>>> >> 
>>> >>
>>> >> 
>>> >>
>>> >>
>>> >> e
>>> >>
>>> >>
>>> >> 
>>> >>
>>> >> 
>>> >>
>>> >>
>>> >> -----When I run this in CsoundQT it locks up.  On the previous
>run, it
>>> >> accepted the line:
>>> >> #include "inc\Init.txt"
>>> >> So I added the next one:
>>> >> #include "inc\instruments.txt"
>>> >> On other occasions, it has accepted a dozen further #include
>>> >> statements.  On some occasions, it freezes on the first one.  I
>don't
>>> >> think this is a consequence of anything in those files.  As far
>as I
>>> >> know, the only syntactic changes I've had to make are two
>instances of
>>> >> i(k[x]) which I changed to i(k,x).   Thanks for looking at this
>>> >> problem.  I have a lot of work invested in my old code and I feel
>lost
>>> >> at sea here.
>>> >>
>>> >> -- m
>>> >>
>>> >> Csound mailing list
>>> >> Csound@listserv.heanet.ie
>>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> >> Send bugs reports to
>>> >>         https://github.com/csound/csound/issues
>>> >> Discussions of bugs and features can be posted here
>>> >
>>> >
>>> >
>>> > --
>>> > http://mysterybear.net
>>> > https://soundcloud.com/mysterybear
>>> > https://mysterybear.bandcamp.com
>>> > https://www.youtube.com/channel/UCo0--3uN5ycq_aupZXskBgA
>>> >
>>> > http://recordings.irritablehedgehog.com/album/dave-seidel-60-hz
>>> > Csound mailing list Csound@listserv.heanet.ie
>https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>https://github.com/csound/csound/issues Discussions of bugs and
>features can be posted here
>>>
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>         https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>
>>
>>
>> --
>> http://mysterybear.net
>> https://soundcloud.com/mysterybear
>> https://mysterybear.bandcamp.com
>> https://www.youtube.com/channel/UCo0--3uN5ycq_aupZXskBgA
>>
>> http://recordings.irritablehedgehog.com/album/dave-seidel-60-hz
>> Csound mailing list Csound@listserv.heanet.ie
>https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>https://github.com/csound/csound/issues Discussions of bugs and
>features can be posted here
>
>Csound mailing list
>Csound@listserv.heanet.ie
>https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>Send bugs reports to
>        https://github.com/csound/csound/issues
>Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2019-06-06 12:08
FromMichael Saunders
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
Thank you both.  I'm busy today, but I will try to proceed testing as
you suggest.  My code represents at least a solid year of full-time
work done over the past 6--7 years, so you can imagine the feeling.
It's hard to pick apart where my score goes wrong because the
orchestra is so interconnected.  The idea for it was this:  I give it
a score that can be quite simple, no more than the information
contained in standard notation, and it produces a recording that
sounds like real people playing real instruments in a real room.  In
between, a controlling instrument analyzes the score, enacts different
fuzzy logic directives which interpret the score (different sets of
directives for different virtual "performers"), and then generates
control signals in the shape of human gestures, sending them to
interchangeable instruments of different types that actually play the
notes and legato phrases.  It also does many fancy things, e.g.,
adaptive tuning and localization with moving sources, generating all
the psychoacoustic cues.  Yesterday I was fully satisfied with its
performance and was in the middle of composing a long piece.  There's
a lot of work in there to loose.

Yes, one of the first things I tried was to run the "Hello world"
beep example from the tutorial.  Indeed, I can make 6.12 go beep.  If
I can't get my code working in 6.12, it would be comforting to know I
could at least revert to 6.06 (and hope that works!).  Is there still
a Windows installer for those versions somewhere?

Thanks Oeyvind and John.  Tomorrow I'll go over your advice again and
try to take it step-by-step, as much as linear stepping is possible
for this thing.

-- m

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2019-06-06 12:39
FromOeyvind Brandtsegg
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
All good.

Here's a link to 6.06
(hm, actually, the windows installer in that folder says 6.07)
Overview of access to older versions is here

best
Oeyvind
 

tor. 6. jun. 2019 kl. 13:09 skrev Michael Saunders <odradek5@gmail.com>:
Thank you both.  I'm busy today, but I will try to proceed testing as
you suggest.  My code represents at least a solid year of full-time
work done over the past 6--7 years, so you can imagine the feeling.
It's hard to pick apart where my score goes wrong because the
orchestra is so interconnected.  The idea for it was this:  I give it
a score that can be quite simple, no more than the information
contained in standard notation, and it produces a recording that
sounds like real people playing real instruments in a real room.  In
between, a controlling instrument analyzes the score, enacts different
fuzzy logic directives which interpret the score (different sets of
directives for different virtual "performers"), and then generates
control signals in the shape of human gestures, sending them to
interchangeable instruments of different types that actually play the
notes and legato phrases.  It also does many fancy things, e.g.,
adaptive tuning and localization with moving sources, generating all
the psychoacoustic cues.  Yesterday I was fully satisfied with its
performance and was in the middle of composing a long piece.  There's
a lot of work in there to loose.

Yes, one of the first things I tried was to run the "Hello world"
beep example from the tutorial.  Indeed, I can make 6.12 go beep.  If
I can't get my code working in 6.12, it would be comforting to know I
could at least revert to 6.06 (and hope that works!).  Is there still
a Windows installer for those versions somewhere?

Thanks Oeyvind and John.  Tomorrow I'll go over your advice again and
try to take it step-by-step, as much as linear stepping is possible
for this thing.

-- m

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here


--
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2019-06-06 16:20
Fromjohn
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
Just asmall note:

--expression-opt does nothing and hasnot for some time.  Expression 
optimisation is always on.  Been that way for ages (April 2014)

==John


> 
> On Wed, Jun 5, 2019 at 6:58 PM Michael Saunders  wrote:
>
>       
>
>       -m642 --expression-opt -+rtaudio=null -+rtmidi=null -o out.wav
>

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2019-06-06 16:27
FromMichael Saunders
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
Thank you!

-- m

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2019-06-08 02:39
FromMichael Saunders
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
print izakch
ii1 zir izakch
print ii1,izakch

The first print statement executes (izakch=101).  The second does not.
The instrument appears to stop without an error or warning when it
reaches the zir statement. The zak channels have been allocated with
zakinit previously in another instrument.  I see no mentions of
changes to the zak system since version 6.06.

-- m

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2019-06-08 03:12
FromMichael Gogins
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
Thanks for the info. I'll look into it.

Regards, 
Mike

On Fri, Jun 7, 2019, 21:39 Michael Saunders <odradek5@gmail.com> wrote:
print izakch
ii1 zir izakch
print ii1,izakch

The first print statement executes (izakch=101).  The second does not.
The instrument appears to stop without an error or warning when it
reaches the zir statement. The zak channels have been allocated with
zakinit previously in another instrument.  I see no mentions of
changes to the zak system since version 6.06.

-- m

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2019-06-08 13:34
FromMarcelo Carneiro de Lima
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
I don’t know if it’s the same, but I have been writing in this list about similar problems I’m having on Mac (csoundqt 0.9.5.1, os 10.13). I sometimes can run my codes via terminal, sometimes I cannot. Csoundqt crashes almost all the time with simple changes on the code: a p content, just changing the content from 1 to 2, for instance. Also tried to downgrade but the problem persists.
Best
Marcelo 

Em sex, 7 de jun de 2019 às 23:12, Michael Gogins <michael.gogins@gmail.com> escreveu:
Thanks for the info. I'll look into it.

Regards, 
Mike


On Fri, Jun 7, 2019, 21:39 Michael Saunders <odradek5@gmail.com> wrote:
print izakch
ii1 zir izakch
print ii1,izakch

The first print statement executes (izakch=101).  The second does not.
The instrument appears to stop without an error or warning when it
reaches the zir statement. The zak channels have been allocated with
zakinit previously in another instrument.  I see no mentions of
changes to the zak system since version 6.06.

-- m

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
--
Marcelo Carneiro
(21) 9382-3621
(21) 3497-0193
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2019-06-08 15:53
Fromjohn
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
There ws an internal change in ZAK that moved it out out the main system 
into a separate place.  It should not have had any external affect -- diid 
not in the tests.

==John ff

On Fri, 7 Jun 2019, Michael Saunders wrote:

> print izakch
> ii1 zir izakch
> print ii1,izakch
>
> The first print statement executes (izakch=101).  The second does not.
> The instrument appears to stop without an error or warning when it
> reaches the zir statement. The zak channels have been allocated with
> zakinit previously in another instrument.  I see no mentions of
> changes to the zak system since version 6.06.
>
> -- m
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2019-06-08 16:01
Fromjohn
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
PS.  I tried constructing a program with those lines and it ran completely 
correctly.  So either my program is not what you did or the problem is in 
the build or your machine

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2019-06-08 16:10
Fromjohn
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
On Wed, 5 Jun 2019, Michael Saunders wrote:

> ;includes that can go in a meta-include file?:
>
> #include "inc\Init.txt"
>
> #include "inc\instruments.txt"
>

I am slightly concerned about the \ separator.  Quick look at the code 
does not seem to treat \ as special in any way.  Does it work on Windows? 
Sorry I cannot test as have no microsoft kit

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2019-06-08 17:53
FromMichael Saunders
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
Yes, it works on Windows.  I remember having to use \ rather than / to
make it work.

About the zak problem:  at first I thought that the zak channel wasn't
being initialized properly, but I've verified that the other
instrument is running and that enough channels are initialized (I even
tried an over-abundance).  I also thought the zak channels might need
to be explicitly initialized now, so I tried filling them with zeros
in the initializing instrument---no change.  The instrument with the
print statements is running for only .1ms (9 control periods) at .1ms
after the initializing instrument, so I tried running it for longer
later---no change.  The second print statement never executes.  And,
of course, all of this worked in 6.06.   I'll try making a separate
test instrument that does both initialization and read and testing
only this.

Thank you.

-- m

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2019-06-08 18:03
FromMichael Saunders
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
The following csd:



-m642 -+rtaudio=null -+rtmidi=null -o out.wav



sr = 96000
kr = 96000
ksmps = 1
nchnls = 2
0dbfs=1

instr 1
zakinit 3,112
print p2,p3
ii1 zir 101
print ii1,p2,p3
endin




i1 0 0
e





...prints:
...p2=0.000, p3=0.000
score finished in csoundPerform()....
It never executes the second print statement.

-- m

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2019-06-08 19:45
Fromjohn
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
I get
SECTION 1:
new alloc for instr 1:
instr 1:  p2 = 0.000  p3 = 0.000
instr 1:  ii1 = 0.000  p2 = 0.000  p3 = 0.000
Score finished in csoundPerform().

which look right.  The eansit is going to be hard to fix from here..


If I add the -v option I get

SECTION 1:
new event:  0.0000000000000  0.0000000000000
activating instr 1 at 0
new alloc for instr 1:
instance(): tp->act_instance = 0x10942e0
instr 1 allocated at 0x10942e0
         lclbas 0x1094478, opds 0x10944a8
op (zakinit) allocated at 0x10944a8
op (print) allocated at 0x10944e8
op (zir) allocated at 0x1098390
op (print) allocated at 0x10983e0
insert(): tp->act_instance = 0x10942e0
psave beg at 0x1094450
    ending at 0x1094450
init zakinit:
init print:
instr 1:  p2 = 0.000  p3 = 0.000
init zir:
init print:
instr 1:  ii1 = 0.000  p2 = 0.000  p3 = 0.000
removed instance of instr 1
Score finished in csoundPerform().
removed instance of instr 0

showing the opcodes.



On Sat, 8 Jun 2019, Michael Saunders wrote:

> The following csd:
>
> 
> 
> -m642 -+rtaudio=null -+rtmidi=null -o out.wav
> 
> 
>
> sr = 96000
> kr = 96000
> ksmps = 1
> nchnls = 2
> 0dbfs=1
>
> instr 1
> zakinit 3,112
> print p2,p3
> ii1 zir 101
> print ii1,p2,p3
> endin
>
> 
> 
>
> i1 0 0
> e
>
> 
> 
>
>
> ...prints:
> ...p2=0.000, p3=0.000
> score finished in csoundPerform()....
> It never executes the second print statement.
>
> -- m
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2019-06-08 19:53
FromMichael Saunders
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
On Sat, Jun 8, 2019 at 2:45 PM john  wrote:
>
> I get
> SECTION 1:
> new alloc for instr 1:
> instr 1:  p2 = 0.000  p3 = 0.000
> instr 1:  ii1 = 0.000  p2 = 0.000  p3 = 0.000
> Score finished in csoundPerform().
>
> which look right.  The eansit is going to be hard to fix from here..
>
>
> If I add the -v option I get
>
> SECTION 1:
> new event:  0.0000000000000  0.0000000000000
> activating instr 1 at 0
> new alloc for instr 1:
> instance(): tp->act_instance = 0x10942e0
> instr 1 allocated at 0x10942e0
>          lclbas 0x1094478, opds 0x10944a8
> op (zakinit) allocated at 0x10944a8
> op (print) allocated at 0x10944e8
> op (zir) allocated at 0x1098390
> op (print) allocated at 0x10983e0
> insert(): tp->act_instance = 0x10942e0
> psave beg at 0x1094450
>     ending at 0x1094450
> init zakinit:
> init print:
> instr 1:  p2 = 0.000  p3 = 0.000
> init zir:
> init print:
> instr 1:  ii1 = 0.000  p2 = 0.000  p3 = 0.000
> removed instance of instr 1
> Score finished in csoundPerform().
> removed instance of instr 0
>
> showing the opcodes.
>
>
>
> On Sat, 8 Jun 2019, Michael Saunders wrote:
>
> > The following csd:
> >
> > 
> > 
> > -m642 -+rtaudio=null -+rtmidi=null -o out.wav
> > 
> > 
> >
> > sr = 96000
> > kr = 96000
> > ksmps = 1
> > nchnls = 2
> > 0dbfs=1
> >
> > instr 1
> > zakinit 3,112
> > print p2,p3
> > ii1 zir 101
> > print ii1,p2,p3
> > endin
> >
> > 
> > 
> >
> > i1 0 0
> > e
> >
> > 
> > 
> >
> >
> > ...prints:
> > ...p2=0.000, p3=0.000
> > score finished in csoundPerform()....
> > It never executes the second print statement.
> >
> > -- m
> >
> > Csound mailing list
> > Csound@listserv.heanet.ie
> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> > Send bugs reports to
> >        https://github.com/csound/csound/issues
> > Discussions of bugs and features can be posted here
> >
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2019-06-08 19:55
FromMichael Saunders
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
Sorry about that repetition.

Eansit?  I tried it with -v and right after the first print I get:
init zir:
removed instance of instr 1
...which baffles me.  The complete output is:

sd">
 
 
 
 


 
 
 
 


 
 
 
 


 
 
 
 


 
 
 
  
  
  
  
 
 
  
  
  
  
 
 
  
  
  
  
 
 
  
  
  
  
  
  
 


Folded


 
 
 
 


 
 
 
 


 
 
 
 


 
 
 
 


 
 
 
 


 
 
 
  
  
  
  
 
 
  
  
  
  
 
 
  
  
  
  
 
 
  
  
  
  
  
  
 


-> $$ = nterm orcfile ()
Stack now 0
Entering state 21
Now at end of input.
Shifting token $end ()
Entering state 74
Stack now 0 21 74
Cleanup: popping token $end ()
Cleanup: popping nterm orcfile ()
Semantic Analysis
(00000000005D0D90)Instr: 1
  read(0000000002221D10): {  }
  write:(0000000002221C50) { ##wri }
  read_write(0000000002221590): {  }
Semantic Analysis Ends
Parsing successful!
csound_orc_semantics(2041) line = 0

esr = 96000.0, ekr = 96000.0, ksmps = 1, nchnls = 2 0dbfs = 1.0
Arg: ii1

zakinit args:   3       112
print args:     p2      p3
zir args:       ii1     101
print args:     ii1     p2      p3
Compile State:
String Pool:
    0) ii1
    1) instr
    2) zir
    3) print
    4) p3
    5) p2
    6) zakinit
    7) 101
    8) 112
    9) ""
    10) endin
    11) 3
    12) 1
    13) 0
Constants Pool:
  14) 96000.000000
  15) 101.000000
  16) 112.000000
  17) 3.000000
  18) 2.000000
  19) 1.000000
  20) 0.000000
Global Variables:
  0) sr:r
  1) kr:r
  2) ksmps:r
  3) nchnls:r
  4) nchnls_i:r
  5) 0dbfs:r
  6) A4:r
  7) $sr:r
  8) $kr:r
  9) $ksmps:r
Instrument 0 000000000054A710 000000000054A810
Variables
Instrument 1 000000000054A810 0000000000000000
Variables
  0) ii1:i
  1) ksmps:r
  2) kr:r
Elapsed time at end of orchestra compile: real: 0.368s, CPU: 0.369s
sorting score ...
yielding >>

i1 0 0
e


e
<<

        ... done
Elapsed time at end of score sort: real: 0.369s, CPU: 0.369s
setting dummy interface
Creating search path cache for 'SNAPDIR':
Creating search path cache for 'SFDIR;SSDIR;INCDIR':
    1: "C:\0\work\The Odradek Camerata\Csound\csd\"
Creating search path cache for 'SFDIR':
Creating search path cache for 'SADIR':
    1: "C:\0\work\The Odradek Camerata\Csound\csd\"
Creating search path cache for 'SFDIR;SSDIR':
    1: "C:\0\work\The Odradek Camerata\Csound\csd\"
graphics suppressed, ascii substituted
0dBFS level = 1.0
instance(): tp->act_instance = 0000000002241B50
instr 0 allocated at 0000000002241B50
        lclbas 0000000002241CE8, opds 0000000002241CE8
orch now loaded
audio buffered in 4096 sample-frame blocks
writing 16384-byte blks of shorts to test.wav (WAV)
SECTION 1:
new event:  0.0000000000000  0.0000000000000
activating instr 1 at 0
new alloc for instr 1:
instance(): tp->act_instance = 000000000225F0C0
instr 1 allocated at 000000000225F0C0
        lclbas 000000000225F258, opds 000000000225F288
op (zakinit) allocated at 000000000225F288
op (print) allocated at 000000000225F2C8
op (zir) allocated at 0000000002263170
op (print) allocated at 00000000022631C0
insert(): tp->act_instance = 000000000225F0C0
psave beg at 000000000225F230
   ending at 000000000225F230
init zakinit:
init print:
instr 1:  p2 = 0.000  p3 = 0.000
init zir:
removed instance of instr 1
Score finished in csoundPerform().
removed instance of instr 0
inactive allocs returned to freespace
end of score.              overall amps:  0.00000  0.00000
           overall samples out of range:        0        0
0 errors in performance
Elapsed time at end of performance: real: 0.375s, CPU: 0.375s
8192 16384 sample blks of shorts written to test.wav (WAV)
signalflowgraph: csoundModuleDestroy(0000000000298C80)

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2019-06-08 20:43
Fromjohn
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
That shows tha zir failed in some way at init passand so the instrunent is 
in error and gets removed.

That points directly to the implementation of zir.  Looking at te code I 
cannot see anyway it could give an error retiurn without a message.  If it 
broke for me I would know what I would do next but really it needs running 
under a debugger or adding additional trace statements.

Does anyone have a suitable Windows environment to chase this?  it needs 
to be single stepped through the function zir to see where ii stops.


As an unlikely experiment coul you try with the zakinit in strument 0?

Oh dear!

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2019-06-08 21:11
FromMichael Saunders
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
I tried the following (I think this is what you mean):


instr 0
zakinit 3,112
endin

instr 1
print p2,p3
ii1 zir 101
print ii1,p2,p3
endin

...and got:

error: instr 0 redefined
cannot compile orchestra

If I put the zakinit outside of any instrument block, before instr 1,
I get the same result as before.

-- m

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2019-06-08 21:22
Fromjohn
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
Thanks.  I just meant outsie instrx 1

So that eliminates a collection of ideas I had.  I keep reading the source 
and cannot see anyway if an error witout a essage.

I am looking at the -m 642
Cukd you hange this to -m 646 and try again?  I think you are surpressing 
some messages

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2019-06-08 21:27
FromMichael Saunders
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
Thank you.  Okay.  This is:  csound -Z -m646 -v -+rtaudio=null
-+rtmidi=null  -o test.wav test.csd
on:

zakinit 3,112

instr 1
print p2,p3
ii1 zir 101
print ii1,p2,p3
endin

results in:



sd">
 
 
 
 


 
 
 
 


 
 
 
 


 
 
 
 


 
 
 
 


 
 
 
  
  
  
  
 
 
  
  
  
  
 
 
  
  
  
  
  
  
 


Folded


 
 
 
 


 
 
 
 


 
 
 
 


 
 
 
 


 
 
 
 


 
 
 
 


 
 
 
  
  
  
  
 
 
  
  
  
  
 
 
  
  
  
  
  
  
 


-> $$ = nterm orcfile ()
Stack now 0
Entering state 21
Now at end of input.
Shifting token $end ()
Entering state 74
Stack now 0 21 74
Cleanup: popping token $end ()
Cleanup: popping nterm orcfile ()
Semantic Analysis
(0000000000580EE0)Instr: 1
  read(0000000002181D10): {  }
  write:(0000000002181C50) { ##wri }
  read_write(00000000021816B0): {  }
Semantic Analysis Ends
Parsing successful!
csound_orc_semantics(2041) line = 0

esr = 96000.0, ekr = 96000.0, ksmps = 1, nchnls = 2 0dbfs = 1.0
Arg: ii1

zakinit args:   3       112
print args:     p2      p3
zir args:       ii1     101
print args:     ii1     p2      p3
Compile State:
String Pool:
    0) ii1
    1) instr
    2) zir
    3) print
    4) p3
    5) p2
    6) zakinit
    7) 101
    8) 112
    9) ""
    10) endin
    11) 3
    12) 1
    13) 0
Constants Pool:
  14) 96000.000000
  15) 101.000000
  16) 112.000000
  17) 3.000000
  18) 2.000000
  19) 1.000000
  20) 0.000000
Global Variables:
  0) sr:r
  1) kr:r
  2) ksmps:r
  3) nchnls:r
  4) nchnls_i:r
  5) 0dbfs:r
  6) A4:r
  7) $sr:r
  8) $kr:r
  9) $ksmps:r
Instrument 0 00000000004FA710 00000000004FA810
Variables
Instrument 1 00000000004FA810 0000000000000000
Variables
  0) ii1:i
  1) ksmps:r
  2) kr:r
Elapsed time at end of orchestra compile: real: 0.400s, CPU: 0.401s
sorting score ...
yielding >>


i1 0 0
e


e
<<

        ... done
Elapsed time at end of score sort: real: 0.403s, CPU: 0.403s
setting dummy interface
Creating search path cache for 'SNAPDIR':
Creating search path cache for 'SFDIR;SSDIR;INCDIR':
    1: "C:\0\work\The Odradek Camerata\Csound\csd\"
Creating search path cache for 'SFDIR':
Creating search path cache for 'SADIR':
    1: "C:\0\work\The Odradek Camerata\Csound\csd\"
Creating search path cache for 'SFDIR;SSDIR':
    1: "C:\0\work\The Odradek Camerata\Csound\csd\"
graphics suppressed, ascii substituted
0dBFS level = 1.0
instance(): tp->act_instance = 00000000021A1B50
instr 0 allocated at 00000000021A1B50
        lclbas 00000000021A1CE8, opds 00000000021A1CE8
op (zakinit) allocated at 00000000021A1CE8
orch now loaded
audio buffered in 4096 sample-frame blocks
writing 16384-byte blks of shorts to test.wav (WAV)
SECTION 1:
new event:  0.0000000000000  0.0000000000000
activating instr 1 at 0
new alloc for instr 1:
instance(): tp->act_instance = 00000000021BF0C0
instr 1 allocated at 00000000021BF0C0
        lclbas 00000000021BF258, opds 00000000021BF288
op (print) allocated at 00000000021BF288
op (zir) allocated at 00000000021C3130
op (print) allocated at 00000000021C3180
insert(): tp->act_instance = 00000000021BF0C0
psave beg at 00000000021BF230
   ending at 00000000021BF230
init print:
instr 1:  p2 = 0.000  p3 = 0.000
init zir:
removed instance of instr 1
Score finished in csoundPerform().
removed instance of instr 0
inactive allocs returned to freespace
end of score.              overall amps:  0.00000  0.00000
           overall samples out of range:        0        0
0 errors in performance
Elapsed time at end of performance: real: 0.408s, CPU: 0.408s
8192 16384 sample blks of shorts written to test.wav (WAV)
signalflowgraph: csoundModuleDestroy(00000000003E8C80)


-- m

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2019-06-08 21:33
Fromjohn
SubjectRe: [Csnd] Upgrading from 6.06 to 6.12
Oh botheration!  Another idea is shown to be wrong.

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here