Reading the headers it was build with BETA set.  In that case it defaults
to new-parser.  One should not build with BETA unless you expect oddities
==John ff

> Looks like you are using the new parser (I thought it was not the default
> for the release?).
> Anyway, you can add the option --old-parser to fix that for the moment.
>
> Victor
> ----- Original Message -----
> From: Aaron Krister Johnson 
> Date: Wednesday, January 19, 2011 4:55 am
> Subject: [Csnd] 5.13 breaks an orc that worked in 5.12
> To: Csound Mail 
>
>> here's the output, I have no idea what it means:
>>
>> time resolution is 0.601 ns
>> PortMIDI real time MIDI plugin for Csound
>> virtual_keyboard real time MIDI plugin for Csound
>> 0dBFS level = 32768.0
>> Csound version 5.13 beta (float samples) Jan 17 2011
>>  libsndfile-1.0.21
>> orchname:  /home/akj/audio_and_midi/csound_files/myzak.orc
>> scorename: /tmp/microcsound.sco
>> rtmidi: PortMIDI module enabled
>> rtaudio: ALSA module enabled
>> ********************
>> * USING NEW PARSER *
>>  ********************
>> csound_orcerror on line 12: syntax error, unexpected T_INTGR, expecting
>> S_COM or S_NL
>> Parsing failed due to invalid input!
>> Csound tidy up: Segmentation fault
>>
>>
>> AND--here's my orchestra up to line 12:
>>  __________________________________(begins after line)
>> sr = 44100
>> ksmps = 64
>> nchnls = 2
>> 0dbfs = 1
>>
>> zakinit 6,6
>> ziw  1, 0   ;;; init some mixer variables
>> ziw  0, 1
>> ziw  0, 2
>> ziw  0, 3
>> gitemp ftgen  1, 0, 65536, 10, 1 ;;; sine
>>  gitemp ftgen  3, 0, 65536, 10, 1, 0.006, 0.05, 0.006, 0.003 ; flute
>> wave?
>>
>>
>> --
>> Aaron Krister Johnson
>> http://www.akjmusic.com
>> http://www.untwelve.org
>  >
>
>
> Dr Victor Lazzarini, Senior Lecturer, Dept. of Music,
> National University of Ireland, Maynooth
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> 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 the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Isn't BETA default?  Every build I've seen has BETA set, and I've
never added it manually.  Maybe this would explain all the oddities =)

~ andy.f



On Wed, Jan 19, 2011 at 4:03 AM,   wrote:
> Reading the headers it was build with BETA set.  In that case it defaults
> to new-parser.  One should not build with BETA unless you expect oddities
> ==John ff
>
>> Looks like you are using the new parser (I thought it was not the default
>> for the release?).
>> Anyway, you can add the option --old-parser to fix that for the moment.
>>
>> Victor
>> ----- Original Message -----
>> From: Aaron Krister Johnson 
>> Date: Wednesday, January 19, 2011 4:55 am
>> Subject: [Csnd] 5.13 breaks an orc that worked in 5.12
>> To: Csound Mail 
>>
>>> here's the output, I have no idea what it means:
>>>
>>> time resolution is 0.601 ns
>>> PortMIDI real time MIDI plugin for Csound
>>> virtual_keyboard real time MIDI plugin for Csound
>>> 0dBFS level = 32768.0
>>> Csound version 5.13 beta (float samples) Jan 17 2011
>>>  libsndfile-1.0.21
>>> orchname:  /home/akj/audio_and_midi/csound_files/myzak.orc
>>> scorename: /tmp/microcsound.sco
>>> rtmidi: PortMIDI module enabled
>>> rtaudio: ALSA module enabled
>>> ********************
>>> * USING NEW PARSER *
>>>  ********************
>>> csound_orcerror on line 12: syntax error, unexpected T_INTGR, expecting
>>> S_COM or S_NL
>>> Parsing failed due to invalid input!
>>> Csound tidy up: Segmentation fault
>>>
>>>
>>> AND--here's my orchestra up to line 12:
>>>  __________________________________(begins after line)
>>> sr = 44100
>>> ksmps = 64
>>> nchnls = 2
>>> 0dbfs = 1
>>>
>>> zakinit 6,6
>>> ziw  1, 0   ;;; init some mixer variables
>>> ziw  0, 1
>>> ziw  0, 2
>>> ziw  0, 3
>>> gitemp ftgen  1, 0, 65536, 10, 1 ;;; sine
>>>  gitemp ftgen  3, 0, 65536, 10, 1, 0.006, 0.05, 0.006, 0.003 ; flute
>>> wave?
>>>
>>>
>>> --
>>> Aaron Krister Johnson
>>> http://www.akjmusic.com
>>> http://www.untwelve.org
>>  >
>>
>>
>> Dr Victor Lazzarini, Senior Lecturer, Dept. of Music,
>> National University of Ireland, Maynooth
>>
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> 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 the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> 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 the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

> Isn't BETA default?  Every build I've seen has BETA set, and I've
> never added it manually.  Maybe this would explain all the oddities =)
>
> ~ andy.f
>

If building for a release no

if commonEnvironment['buildRelease'] == '0':
    commonEnvironment.Prepend(CPPFLAGS = ['-DBETA'])

Never thought about it.  But I do have instruction to
"3.5: ensure no beta in builder" in making a release

==John ff


>
>
> On Wed, Jan 19, 2011 at 4:03 AM,   wrote:
>> Reading the headers it was build with BETA set.  In that case it
>> defaults
>> to new-parser.  One should not build with BETA unless you expect
>> oddities
>> ==John ff
>>
>>> Looks like you are using the new parser (I thought it was not the
>>> default
>>> for the release?).
>>> Anyway, you can add the option --old-parser to fix that for the moment.
>>>
>>> Victor
>>> ----- Original Message -----
>>> From: Aaron Krister Johnson 
>>> Date: Wednesday, January 19, 2011 4:55 am
>>> Subject: [Csnd] 5.13 breaks an orc that worked in 5.12
>>> To: Csound Mail 
>>>
>>>> here's the output, I have no idea what it means:
>>>>
>>>> time resolution is 0.601 ns
>>>> PortMIDI real time MIDI plugin for Csound
>>>> virtual_keyboard real time MIDI plugin for Csound
>>>> 0dBFS level = 32768.0
>>>> Csound version 5.13 beta (float samples) Jan 17 2011
>>>>  libsndfile-1.0.21
>>>> orchname:  /home/akj/audio_and_midi/csound_files/myzak.orc
>>>> scorename: /tmp/microcsound.sco
>>>> rtmidi: PortMIDI module enabled
>>>> rtaudio: ALSA module enabled
>>>> ********************
>>>> * USING NEW PARSER *
>>>>  ********************
>>>> csound_orcerror on line 12: syntax error, unexpected T_INTGR,
>>>> expecting
>>>> S_COM or S_NL
>>>> Parsing failed due to invalid input!
>>>> Csound tidy up: Segmentation fault
>>>>
>>>>
>>>> AND--here's my orchestra up to line 12:
>>>>  __________________________________(begins after line)
>>>> sr = 44100
>>>> ksmps = 64
>>>> nchnls = 2
>>>> 0dbfs = 1
>>>>
>>>> zakinit 6,6
>>>> ziw  1, 0   ;;; init some mixer variables
>>>> ziw  0, 1
>>>> ziw  0, 2
>>>> ziw  0, 3
>>>> gitemp ftgen  1, 0, 65536, 10, 1 ;;; sine
>>>>  gitemp ftgen  3, 0, 65536, 10, 1, 0.006, 0.05, 0.006, 0.003 ; flute
>>>> wave?
>>>>
>>>>
>>>> --
>>>> Aaron Krister Johnson
>>>> http://www.akjmusic.com
>>>> http://www.untwelve.org
>>>  >
>>>
>>>
>>> Dr Victor Lazzarini, Senior Lecturer, Dept. of Music,
>>> National University of Ireland, Maynooth
>>>
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> 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 the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> 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 the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> 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 the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Are all the windows releases are considered beta?



On Wed, Jan 19, 2011 at 6:03 AM,   wrote:
>> Isn't BETA default?  Every build I've seen has BETA set, and I've
>> never added it manually.  Maybe this would explain all the oddities =)
>>
>> ~ andy.f
>>
>
> If building for a release no
>
> if commonEnvironment['buildRelease'] == '0':
>    commonEnvironment.Prepend(CPPFLAGS = ['-DBETA'])
>
> Never thought about it.  But I do have instruction to
> "3.5: ensure no beta in builder" in making a release
>
> ==John ff
>
>
>>
>>
>> On Wed, Jan 19, 2011 at 4:03 AM,   wrote:
>>> Reading the headers it was build with BETA set.  In that case it
>>> defaults
>>> to new-parser.  One should not build with BETA unless you expect
>>> oddities
>>> ==John ff
>>>
>>>> Looks like you are using the new parser (I thought it was not the
>>>> default
>>>> for the release?).
>>>> Anyway, you can add the option --old-parser to fix that for the moment.
>>>>
>>>> Victor
>>>> ----- Original Message -----
>>>> From: Aaron Krister Johnson 
>>>> Date: Wednesday, January 19, 2011 4:55 am
>>>> Subject: [Csnd] 5.13 breaks an orc that worked in 5.12
>>>> To: Csound Mail 
>>>>
>>>>> here's the output, I have no idea what it means:
>>>>>
>>>>> time resolution is 0.601 ns
>>>>> PortMIDI real time MIDI plugin for Csound
>>>>> virtual_keyboard real time MIDI plugin for Csound
>>>>> 0dBFS level = 32768.0
>>>>> Csound version 5.13 beta (float samples) Jan 17 2011
>>>>>  libsndfile-1.0.21
>>>>> orchname:  /home/akj/audio_and_midi/csound_files/myzak.orc
>>>>> scorename: /tmp/microcsound.sco
>>>>> rtmidi: PortMIDI module enabled
>>>>> rtaudio: ALSA module enabled
>>>>> ********************
>>>>> * USING NEW PARSER *
>>>>>  ********************
>>>>> csound_orcerror on line 12: syntax error, unexpected T_INTGR,
>>>>> expecting
>>>>> S_COM or S_NL
>>>>> Parsing failed due to invalid input!
>>>>> Csound tidy up: Segmentation fault
>>>>>
>>>>>
>>>>> AND--here's my orchestra up to line 12:
>>>>>  __________________________________(begins after line)
>>>>> sr = 44100
>>>>> ksmps = 64
>>>>> nchnls = 2
>>>>> 0dbfs = 1
>>>>>
>>>>> zakinit 6,6
>>>>> ziw  1, 0   ;;; init some mixer variables
>>>>> ziw  0, 1
>>>>> ziw  0, 2
>>>>> ziw  0, 3
>>>>> gitemp ftgen  1, 0, 65536, 10, 1 ;;; sine
>>>>>  gitemp ftgen  3, 0, 65536, 10, 1, 0.006, 0.05, 0.006, 0.003 ; flute
>>>>> wave?
>>>>>
>>>>>
>>>>> --
>>>>> Aaron Krister Johnson
>>>>> http://www.akjmusic.com
>>>>> http://www.untwelve.org
>>>>  >
>>>>
>>>>
>>>> Dr Victor Lazzarini, Senior Lecturer, Dept. of Music,
>>>> National University of Ireland, Maynooth
>>>>
>>>>
>>>>
>>>> Send bugs reports to the Sourceforge bug tracker
>>>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> 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 the Sourceforge bug tracker
>>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> 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 the Sourceforge bug tracker
>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> 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 the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> 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 the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

scons buildRelease=1

to build non-beta releases. I assume Mike uses this option.

Victor

On 19 Jan 2011, at 11:10, andy fillebrown wrote:

> Are all the windows releases are considered beta?
>
>
>
> On Wed, Jan 19, 2011 at 6:03 AM,   wrote:
>>> Isn't BETA default?  Every build I've seen has BETA set, and I've
>>> never added it manually.  Maybe this would explain all the  
>>> oddities =)
>>>
>>> ~ andy.f
>>>
>>
>> If building for a release no
>>
>> if commonEnvironment['buildRelease'] == '0':
>>    commonEnvironment.Prepend(CPPFLAGS = ['-DBETA'])
>>
>> Never thought about it.  But I do have instruction to
>> "3.5: ensure no beta in builder" in making a release
>>
>> ==John ff
>>
>>
>>>
>>>
>>> On Wed, Jan 19, 2011 at 4:03 AM,   wrote:
>>>> Reading the headers it was build with BETA set.  In that case it
>>>> defaults
>>>> to new-parser.  One should not build with BETA unless you expect
>>>> oddities
>>>> ==John ff
>>>>
>>>>> Looks like you are using the new parser (I thought it was not the
>>>>> default
>>>>> for the release?).
>>>>> Anyway, you can add the option --old-parser to fix that for the  
>>>>> moment.
>>>>>
>>>>> Victor
>>>>> ----- Original Message -----
>>>>> From: Aaron Krister Johnson 
>>>>> Date: Wednesday, January 19, 2011 4:55 am
>>>>> Subject: [Csnd] 5.13 breaks an orc that worked in 5.12
>>>>> To: Csound Mail 
>>>>>
>>>>>> here's the output, I have no idea what it means:
>>>>>>
>>>>>> time resolution is 0.601 ns
>>>>>> PortMIDI real time MIDI plugin for Csound
>>>>>> virtual_keyboard real time MIDI plugin for Csound
>>>>>> 0dBFS level = 32768.0
>>>>>> Csound version 5.13 beta (float samples) Jan 17 2011
>>>>>>  libsndfile-1.0.21
>>>>>> orchname:  /home/akj/audio_and_midi/csound_files/myzak.orc
>>>>>> scorename: /tmp/microcsound.sco
>>>>>> rtmidi: PortMIDI module enabled
>>>>>> rtaudio: ALSA module enabled
>>>>>> ********************
>>>>>> * USING NEW PARSER *
>>>>>>  ********************
>>>>>> csound_orcerror on line 12: syntax error, unexpected T_INTGR,
>>>>>> expecting
>>>>>> S_COM or S_NL
>>>>>> Parsing failed due to invalid input!
>>>>>> Csound tidy up: Segmentation fault
>>>>>>
>>>>>>
>>>>>> AND--here's my orchestra up to line 12:
>>>>>>  __________________________________(begins after line)
>>>>>> sr = 44100
>>>>>> ksmps = 64
>>>>>> nchnls = 2
>>>>>> 0dbfs = 1
>>>>>>
>>>>>> zakinit 6,6
>>>>>> ziw  1, 0   ;;; init some mixer variables
>>>>>> ziw  0, 1
>>>>>> ziw  0, 2
>>>>>> ziw  0, 3
>>>>>> gitemp ftgen  1, 0, 65536, 10, 1 ;;; sine
>>>>>>  gitemp ftgen  3, 0, 65536, 10, 1, 0.006, 0.05, 0.006, 0.003 ;  
>>>>>> flute
>>>>>> wave?
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Aaron Krister Johnson
>>>>>> http://www.akjmusic.com
>>>>>> http://www.untwelve.org
>>>>>  >
>>>>>
>>>>>
>>>>> Dr Victor Lazzarini, Senior Lecturer, Dept. of Music,
>>>>> National University of Ireland, Maynooth
>>>>>
>>>>>
>>>>>
>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>> 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 the Sourceforge bug tracker
>>>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> 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 the Sourceforge bug tracker
>>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> 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 the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/? 
>> group_id=81968&atid=564599
>> 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 the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> 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 the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

And also...  i took time off fixing thje new parser to clear bugs for the
releaase.  The actual error that sparked all this is one I have seen in my
own music, but until after ICMC deadline rather busy (plus examinatio
marking).  I thought that the problem had been fixed so need to work out
why it reverted

> Are all the windows releases are considered beta?
>
>
>
> On Wed, Jan 19, 2011 at 6:03 AM,   wrote:
>>> Isn't BETA default?  Every build I've seen has BETA set, and I've
>>> never added it manually.  Maybe this would explain all the oddities =)
>>>
>>> ~ andy.f
>>>
>>
>> If building for a release no
>>
>> if commonEnvironment['buildRelease'] == '0':
>>    commonEnvironment.Prepend(CPPFLAGS = ['-DBETA'])
>>
>> Never thought about it.  But I do have instruction to
>> "3.5: ensure no beta in builder" in making a release
>>
>> ==John ff
>>
>>
>>>
>>>
>>> On Wed, Jan 19, 2011 at 4:03 AM,   wrote:
>>>> Reading the headers it was build with BETA set.  In that case it
>>>> defaults
>>>> to new-parser.  One should not build with BETA unless you expect
>>>> oddities
>>>> ==John ff
>>>>
>>>>> Looks like you are using the new parser (I thought it was not the
>>>>> default
>>>>> for the release?).
>>>>> Anyway, you can add the option --old-parser to fix that for the
>>>>> moment.
>>>>>
>>>>> Victor
>>>>> ----- Original Message -----
>>>>> From: Aaron Krister Johnson 
>>>>> Date: Wednesday, January 19, 2011 4:55 am
>>>>> Subject: [Csnd] 5.13 breaks an orc that worked in 5.12
>>>>> To: Csound Mail 
>>>>>
>>>>>> here's the output, I have no idea what it means:
>>>>>>
>>>>>> time resolution is 0.601 ns
>>>>>> PortMIDI real time MIDI plugin for Csound
>>>>>> virtual_keyboard real time MIDI plugin for Csound
>>>>>> 0dBFS level = 32768.0
>>>>>> Csound version 5.13 beta (float samples) Jan 17 2011
>>>>>>  libsndfile-1.0.21
>>>>>> orchname:  /home/akj/audio_and_midi/csound_files/myzak.orc
>>>>>> scorename: /tmp/microcsound.sco
>>>>>> rtmidi: PortMIDI module enabled
>>>>>> rtaudio: ALSA module enabled
>>>>>> ********************
>>>>>> * USING NEW PARSER *
>>>>>>  ********************
>>>>>> csound_orcerror on line 12: syntax error, unexpected T_INTGR,
>>>>>> expecting
>>>>>> S_COM or S_NL
>>>>>> Parsing failed due to invalid input!
>>>>>> Csound tidy up: Segmentation fault
>>>>>>
>>>>>>
>>>>>> AND--here's my orchestra up to line 12:
>>>>>>  __________________________________(begins after line)
>>>>>> sr = 44100
>>>>>> ksmps = 64
>>>>>> nchnls = 2
>>>>>> 0dbfs = 1
>>>>>>
>>>>>> zakinit 6,6
>>>>>> ziw  1, 0   ;;; init some mixer variables
>>>>>> ziw  0, 1
>>>>>> ziw  0, 2
>>>>>> ziw  0, 3
>>>>>> gitemp ftgen  1, 0, 65536, 10, 1 ;;; sine
>>>>>>  gitemp ftgen  3, 0, 65536, 10, 1, 0.006, 0.05, 0.006, 0.003 ; flute
>>>>>> wave?
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Aaron Krister Johnson
>>>>>> http://www.akjmusic.com
>>>>>> http://www.untwelve.org
>>>>>  >
>>>>>
>>>>>
>>>>> Dr Victor Lazzarini, Senior Lecturer, Dept. of Music,
>>>>> National University of Ireland, Maynooth
>>>>>
>>>>>
>>>>>
>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>            
>>>>> https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>> 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 the Sourceforge bug tracker
>>>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> 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 the Sourceforge bug tracker
>>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> 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 the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> 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 the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> 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 the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Yes, my mistake.

Cheers,
~ andy.f



On Wed, Jan 19, 2011 at 6:16 AM, Victor Lazzarini
 wrote:
> scons buildRelease=1
>
> to build non-beta releases. I assume Mike uses this option.
>
> Victor
>
> On 19 Jan 2011, at 11:10, andy fillebrown wrote:
>
>> Are all the windows releases are considered beta?
>>
>>
>>
>> On Wed, Jan 19, 2011 at 6:03 AM,   wrote:
>>>>
>>>> Isn't BETA default?  Every build I've seen has BETA set, and I've
>>>> never added it manually.  Maybe this would explain all the oddities =)
>>>>
>>>> ~ andy.f
>>>>
>>>
>>> If building for a release no
>>>
>>> if commonEnvironment['buildRelease'] == '0':
>>>   commonEnvironment.Prepend(CPPFLAGS = ['-DBETA'])
>>>
>>> Never thought about it.  But I do have instruction to
>>> "3.5: ensure no beta in builder" in making a release
>>>
>>> ==John ff
>>>
>>>
>>>>
>>>>
>>>> On Wed, Jan 19, 2011 at 4:03 AM,   wrote:
>>>>>
>>>>> Reading the headers it was build with BETA set.  In that case it
>>>>> defaults
>>>>> to new-parser.  One should not build with BETA unless you expect
>>>>> oddities
>>>>> ==John ff
>>>>>
>>>>>> Looks like you are using the new parser (I thought it was not the
>>>>>> default
>>>>>> for the release?).
>>>>>> Anyway, you can add the option --old-parser to fix that for the
>>>>>> moment.
>>>>>>
>>>>>> Victor
>>>>>> ----- Original Message -----
>>>>>> From: Aaron Krister Johnson 
>>>>>> Date: Wednesday, January 19, 2011 4:55 am
>>>>>> Subject: [Csnd] 5.13 breaks an orc that worked in 5.12
>>>>>> To: Csound Mail 
>>>>>>
>>>>>>> here's the output, I have no idea what it means:
>>>>>>>
>>>>>>> time resolution is 0.601 ns
>>>>>>> PortMIDI real time MIDI plugin for Csound
>>>>>>> virtual_keyboard real time MIDI plugin for Csound
>>>>>>> 0dBFS level = 32768.0
>>>>>>> Csound version 5.13 beta (float samples) Jan 17 2011
>>>>>>>  libsndfile-1.0.21
>>>>>>> orchname:  /home/akj/audio_and_midi/csound_files/myzak.orc
>>>>>>> scorename: /tmp/microcsound.sco
>>>>>>> rtmidi: PortMIDI module enabled
>>>>>>> rtaudio: ALSA module enabled
>>>>>>> ********************
>>>>>>> * USING NEW PARSER *
>>>>>>>  ********************
>>>>>>> csound_orcerror on line 12: syntax error, unexpected T_INTGR,
>>>>>>> expecting
>>>>>>> S_COM or S_NL
>>>>>>> Parsing failed due to invalid input!
>>>>>>> Csound tidy up: Segmentation fault
>>>>>>>
>>>>>>>
>>>>>>> AND--here's my orchestra up to line 12:
>>>>>>>  __________________________________(begins after line)
>>>>>>> sr = 44100
>>>>>>> ksmps = 64
>>>>>>> nchnls = 2
>>>>>>> 0dbfs = 1
>>>>>>>
>>>>>>> zakinit 6,6
>>>>>>> ziw  1, 0   ;;; init some mixer variables
>>>>>>> ziw  0, 1
>>>>>>> ziw  0, 2
>>>>>>> ziw  0, 3
>>>>>>> gitemp ftgen  1, 0, 65536, 10, 1 ;;; sine
>>>>>>>  gitemp ftgen  3, 0, 65536, 10, 1, 0.006, 0.05, 0.006, 0.003 ; flute
>>>>>>> wave?
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Aaron Krister Johnson
>>>>>>> http://www.akjmusic.com
>>>>>>> http://www.untwelve.org
>>>>>>
>>>>>>  >
>>>>>>
>>>>>>
>>>>>> Dr Victor Lazzarini, Senior Lecturer, Dept. of Music,
>>>>>> National University of Ireland, Maynooth
>>>>>>
>>>>>>
>>>>>>
>>>>>> Send bugs reports to the Sourceforge bug tracker
>>>>>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>>> 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 the Sourceforge bug tracker
>>>>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>>> 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 the Sourceforge bug tracker
>>>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> 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 the Sourceforge bug tracker
>>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> 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 the Sourceforge bug tracker
>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> 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 the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> 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 the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hi all,


What is the situation for QuteCsound in Windows at present? I have been 
hoping to use it as part of the LHCsound project imminently about to go 
into schools. I am developing a cross-platform app that generates a csd 
file from various types of particle collision data. The Mac version of 
QuteCsound (6.0) is working fine, but the Windows version (tested on two 
machines, one XP and one Vista) quits frequently and unpredictably, 
sometimes while attempting playback, at other times when just working in 
a dialog. Note these are not crashes as such - it just shuts down instantly.

For schools it is especially important that any packages supplied can 
install simply and run reliably "out of the box" i.e. with preferably no 
configuration needed.  If QuteCsound on Windows could work as well as 
the Mac verison now does it would be the app of choice (though I would 
prefer a couple of alternative default settings), but the current 
propensity to quit is a game-stopper at the moment. I do not want to 
provide different tools on different platforms. If there are  other 
cross-platform single-install alternatives that will do the job 
(primarily real-time and offline render  - a sort of "Csound Media 
Player" really) I will be grateful for all and any recommendations.

When it is at a sufficient stage of development, the app (built using 
wxWidgets) will be made available open source (runs on Linux too 
needless to say); as will be data files to explore. The interest for 
Csounders will be principally in creating alternative instruments to 
render a given score (a case where the old orc/sco separation is 
actually rather useful).

In due course I would naturally look to adding direct Csound rendering 
internally via the API etc; but time is against me with so much else to 
do, so relying on an external "csd player" is the only option in the 
short term. While the remit for the project is specifically (and 
strictly) "outreach" with regard to the LHC, the ATLAS detector (the 
hunt for the Higgs etc etc etc) and the sonification of collision data, 
there is clearly some scope for introducing the wonders of Csound to 
enterprising schools; but I do need to be able to supply it (plus 
front-end) in as painless and reliable a form as possible.

Richard Dobson






Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hello,

It should be very eay to put together a maxmsp based frontend. It
would run on os x and windows and the stanalode build (maxmsp runtime
included) would requite no extra installation or setup.

Otherwise I'd highly recommend winXound if no widgets are needed.

Best,

Peiman


On 20 January 2011 01:27, Richard Dobson  wrote:
>
>
> Hi all,
>
>
> What is the situation for QuteCsound in Windows at present? I have been
> hoping to use it as part of the LHCsound project imminently about to go into
> schools. I am developing a cross-platform app that generates a csd file from
> various types of particle collision data. The Mac version of QuteCsound
> (6.0) is working fine, but the Windows version (tested on two machines, one
> XP and one Vista) quits frequently and unpredictably, sometimes while
> attempting playback, at other times when just working in a dialog. Note
> these are not crashes as such - it just shuts down instantly.
>
> For schools it is especially important that any packages supplied can
> install simply and run reliably "out of the box" i.e. with preferably no
> configuration needed.  If QuteCsound on Windows could work as well as the
> Mac verison now does it would be the app of choice (though I would prefer a
> couple of alternative default settings), but the current propensity to quit
> is a game-stopper at the moment. I do not want to provide different tools on
> different platforms. If there are  other cross-platform single-install
> alternatives that will do the job (primarily real-time and offline render  -
> a sort of "Csound Media Player" really) I will be grateful for all and any
> recommendations.
>
> When it is at a sufficient stage of development, the app (built using
> wxWidgets) will be made available open source (runs on Linux too needless to
> say); as will be data files to explore. The interest for Csounders will be
> principally in creating alternative instruments to render a given score (a
> case where the old orc/sco separation is actually rather useful).
>
> In due course I would naturally look to adding direct Csound rendering
> internally via the API etc; but time is against me with so much else to do,
> so relying on an external "csd player" is the only option in the short term.
> While the remit for the project is specifically (and strictly) "outreach"
> with regard to the LHC, the ATLAS detector (the hunt for the Higgs etc etc
> etc) and the sonification of collision data, there is clearly some scope for
> introducing the wonders of Csound to enterprising schools; but I do need to
> be able to supply it (plus front-end) in as painless and reliable a form as
> possible.
>
> Richard Dobson
>
>
>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> 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 the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hi Richard,

This is a known problem which stems from problems with FLTK
(unfortunately, it can be solved within QuteCsound currently). If you
remove all the FLTK plugins (libvirtual, libwidgets and
libfluidSynth), you should be fine. The latest version of QuteCsound
combined with the latest version of Csound should be able to disable
this correctly when you select disable FLTK in the options. I also
suspect that the problem with FLTK might have been fixed for the
latest release.
The windows release should appear shortly for you to try, as soon as
Michael is done.

Cheers,
Andres

On Thu, Jan 20, 2011 at 1:27 AM, Richard Dobson
 wrote:
>
>
> Hi all,
>
>
> What is the situation for QuteCsound in Windows at present? I have been
> hoping to use it as part of the LHCsound project imminently about to go into
> schools. I am developing a cross-platform app that generates a csd file from
> various types of particle collision data. The Mac version of QuteCsound
> (6.0) is working fine, but the Windows version (tested on two machines, one
> XP and one Vista) quits frequently and unpredictably, sometimes while
> attempting playback, at other times when just working in a dialog. Note
> these are not crashes as such - it just shuts down instantly.
>
> For schools it is especially important that any packages supplied can
> install simply and run reliably "out of the box" i.e. with preferably no
> configuration needed.  If QuteCsound on Windows could work as well as the
> Mac verison now does it would be the app of choice (though I would prefer a
> couple of alternative default settings), but the current propensity to quit
> is a game-stopper at the moment. I do not want to provide different tools on
> different platforms. If there are  other cross-platform single-install
> alternatives that will do the job (primarily real-time and offline render  -
> a sort of "Csound Media Player" really) I will be grateful for all and any
> recommendations.
>
> When it is at a sufficient stage of development, the app (built using
> wxWidgets) will be made available open source (runs on Linux too needless to
> say); as will be data files to explore. The interest for Csounders will be
> principally in creating alternative instruments to render a given score (a
> case where the old orc/sco separation is actually rather useful).
>
> In due course I would naturally look to adding direct Csound rendering
> internally via the API etc; but time is against me with so much else to do,
> so relying on an external "csd player" is the only option in the short term.
> While the remit for the project is specifically (and strictly) "outreach"
> with regard to the LHC, the ATLAS detector (the hunt for the Higgs etc etc
> etc) and the sonification of collision data, there is clearly some scope for
> introducing the wonders of Csound to enterprising schools; but I do need to
> be able to supply it (plus front-end) in as painless and reliable a form as
> possible.
>
> Richard Dobson
>
>
>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> 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 the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

> I do not want to
> provide different tools on different platforms. If there are  other
> cross-platform single-install alternatives that will do the job
> (primarily real-time and offline render  - a sort of "Csound Media
> Player" really) I will be grateful for all and any recommendations.

Emacs + Csound-x works identically on all platforms. Once started, just 
drop a csd in the Emacs window and hit a button to play the file. Can be 
configured in any way you like to look simpler, although it will always 
be ugly in the view of most people :)

Best,

Stef


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I do indeed like the look of WinXound very much. The one thing that 
makes QuteCsound attractive from the point of view of this project 
(getting kids involved, minimum number of steps between setting 
parameters and hearing results, etc) is the presence of a nice big 
"play" button ready to use. With WinXound I have to add the "-o dac" 
flag manually to the csound command options in Preferences.

I have found I can modify the flags inside the app bundle itself for the 
mac verison. If I can do the same on the Windows version (so I can 
package it up for schools in that form) it is a viable contender. But 
having to go to Preferences each time to toggle between real-time and 
file is not so convenient (and too much danger of users fiddling with 
stuff they shouldn't!).  I really want both options (real-time play and 
render-to-file) available and visible, and QuteCsound offers that in the 
middle of the toolbar - absolutely no setup needed. So at present it is 
still the favourite ~if~ is is stable on Windows.

Richard Dobson


On 20/01/2011 02:10, peiman khosravi wrote:
> Hello,
>
> It should be very eay to put together a maxmsp based frontend. It
> would run on os x and windows and the stanalode build (maxmsp runtime
> included) would requite no extra installation or setup.
>
> Otherwise I'd highly recommend winXound if no widgets are needed.
>



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hi Richard,
if you (or anyone) have some suggestions or requests about features to include 
inside WinXound, please feel free to contact me directly (or within this list).
My mails are: stefano_bonetti@tin.it or stefano_bonetti@alice.it

... I will be very happy to include new useful features inside WinXound...

Thanks and let me know,
Stefano




Il giorno 20/gen/2011, alle ore 10.57, Richard Dobson ha scritto:

> I do indeed like the look of WinXound very much. The one thing that makes QuteCsound attractive from the point of view of this project (getting kids involved, minimum number of steps between setting parameters and hearing results, etc) is the presence of a nice big "play" button ready to use. With WinXound I have to add the "-o dac" flag manually to the csound command options in Preferences.
> 
> I have found I can modify the flags inside the app bundle itself for the mac verison. If I can do the same on the Windows version (so I can package it up for schools in that form) it is a viable contender. But having to go to Preferences each time to toggle between real-time and file is not so convenient (and too much danger of users fiddling with stuff they shouldn't!).  I really want both options (real-time play and render-to-file) available and visible, and QuteCsound offers that in the middle of the toolbar - absolutely no setup needed. So at present it is still the favourite ~if~ is is stable on Windows.
> 
> Richard Dobson
> 
> 
> On 20/01/2011 02:10, peiman khosravi wrote:
>> Hello,
>> 
>> It should be very eay to put together a maxmsp based frontend. It
>> would run on os x and windows and the stanalode build (maxmsp runtime
>> included) would requite no extra installation or setup.
>> 
>> Otherwise I'd highly recommend winXound if no widgets are needed.
>> 
> 
> 
> 
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> 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 the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

At present there i sno such option and my immediate thought is that it is
not very easy to do.....  I guess SConstruct could create a header file
with the optiond as a string, and incorporate.  Bprobably not VERY hard.
Will add to the list

==John ff

> Aaron Krister Johnson  escribió:
>
>> The manual has a "building Csound" page which explains many of the
>> options.
>> Also, 'scons -h' will list them for you.
>
> i see i didn't phrase my question correctly... i know about scons -h,
> but i was referring to something different: if i have the csound
> binaries (compiled by myself or by other), how do i know which
> configuration options were used in the compilation?
>
> many applications have an option to show this information, like "gcc
> -v", or "vim --version" or whatever.
>
> i don't know that csound has such an option, i for one wish it had.
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> 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 the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

For Windows, the "Building Csound" page is superseded by the
How_to_Build_Csound_on_Windows.doc file. The page should be updated to
reflect this.

Regards,
Mike

On Thu, Jan 20, 2011 at 6:23 AM,   wrote:
> At present there i sno such option and my immediate thought is that it is
> not very easy to do.....  I guess SConstruct could create a header file
> with the optiond as a string, and incorporate.  Bprobably not VERY hard.
> Will add to the list
>
> ==John ff
>
>> Aaron Krister Johnson  escribió:
>>
>>> The manual has a "building Csound" page which explains many of the
>>> options.
>>> Also, 'scons -h' will list them for you.
>>
>> i see i didn't phrase my question correctly... i know about scons -h,
>> but i was referring to something different: if i have the csound
>> binaries (compiled by myself or by other), how do i know which
>> configuration options were used in the compilation?
>>
>> many applications have an option to show this information, like "gcc
>> -v", or "vim --version" or whatever.
>>
>> i don't know that csound has such an option, i for one wish it had.
>>
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> 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 the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>



-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hi Richard,

The instabilities in QuteCsound on Windows have been identified and
fixed upstream in the fluidsynth and fltk development branches, so the
forthcoming Csound/QuteCsound release should be stable.

Cheers,
~ andy.f



On Thu, Jan 20, 2011 at 4:57 AM, Richard Dobson
 wrote:
> I do indeed like the look of WinXound very much. The one thing that makes
> QuteCsound attractive from the point of view of this project (getting kids
> involved, minimum number of steps between setting parameters and hearing
> results, etc) is the presence of a nice big "play" button ready to use. With
> WinXound I have to add the "-o dac" flag manually to the csound command
> options in Preferences.
>
> I have found I can modify the flags inside the app bundle itself for the mac
> verison. If I can do the same on the Windows version (so I can package it up
> for schools in that form) it is a viable contender. But having to go to
> Preferences each time to toggle between real-time and file is not so
> convenient (and too much danger of users fiddling with stuff they
> shouldn't!).  I really want both options (real-time play and render-to-file)
> available and visible, and QuteCsound offers that in the middle of the
> toolbar - absolutely no setup needed. So at present it is still the
> favourite ~if~ is is stable on Windows.
>
> Richard Dobson
>
>
> On 20/01/2011 02:10, peiman khosravi wrote:
>>
>> Hello,
>>
>> It should be very eay to put together a maxmsp based frontend. It
>> would run on os x and windows and the stanalode build (maxmsp runtime
>> included) would requite no extra installation or setup.
>>
>> Otherwise I'd highly recommend winXound if no widgets are needed.
>>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> 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 the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

They both had ref-counting issues during library loading and
unloading.  Fluidsynth was dangling a hidden window, and FLTK was
unloading the OLE/COM system prematurely.  The csound-dev thread from
September can be viewed at
http://csound.1045644.n5.nabble.com/Problem-plugins-tt2828100.html --
The posts starting on September 20th detail the bugs.

~ andy.f



On Thu, Jan 20, 2011 at 2:45 PM,   wrote:
> What were they? I'm curious!
>
> ----- Original Message -----
> From: andy fillebrown 
> Date: Thursday, January 20, 2011 6:42 pm
> Subject: Re: [Csnd] QuteCsound Windows issues
> To: csound@lists.bath.ac.uk
>
>> Hi Richard,
>>
>> The instabilities in QuteCsound on Windows have been identified and
>> fixed upstream in the fluidsynth and fltk development branches,
>> so the
>> forthcoming Csound/QuteCsound release should be stable.
>>
>> Cheers,
>> ~ andy.f
>>
>>
>>
>> On Thu, Jan 20, 2011 at 4:57 AM, Richard Dobson
>>  wrote:
>> > I do indeed like the look of WinXound very much. The one thing
>> that makes
>> > QuteCsound attractive from the point of view of this project
>> (getting kids
>> > involved, minimum number of steps between setting parameters
>> and hearing
>> > results, etc) is the presence of a nice big "play" button
>> ready to use. With
>> > WinXound I have to add the "-o dac" flag manually to the
>> csound command
>> > options in Preferences.
>> >
>> > I have found I can modify the flags inside the app bundle
>> itself for the mac
>> > verison. If I can do the same on the Windows version (so I can
>> package it up
>> > for schools in that form) it is a viable contender. But having
>> to go to
>> > Preferences each time to toggle between real-time and file is
>> not so
>> > convenient (and too much danger of users fiddling with stuff they
>> > shouldn't!).  I really want both options (real-time play and
>> render-to-file)
>> > available and visible, and QuteCsound offers that in the
>> middle of the
>> > toolbar - absolutely no setup needed. So at present it is
>> still the
>> > favourite ~if~ is is stable on Windows.
>> >
>> > Richard Dobson
>> >
>> >
>> > On 20/01/2011 02:10, peiman khosravi wrote:
>> >>
>> >> Hello,
>> >>
>> >> It should be very eay to put together a maxmsp based
>> frontend. It
>> >> would run on os x and windows and the stanalode build (maxmsp
>> runtime>> included) would requite no extra installation or setup.
>> >>
>> >> Otherwise I'd highly recommend winXound if no widgets are needed.
>> >>
>> >
>> >
>> >
>> > Send bugs reports to the Sourceforge bug tracker
>> >
>> https://sourceforge.net/tracker/?group_id=81968&atid=564599>
>> 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 the Sourceforge bug tracker
>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>> "unsubscribe csound"
>>
>
> Dr Victor Lazzarini, Senior Lecturer, Dept. of Music,
> National University of Ireland, Maynooth
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

ditto on crashes on XP with 5.11.  Didn't install on 5.12
Bob Foose

On 13:59, Richard Dobson wrote:
>
>
> Hi all,
>
>
> What is the situation for QuteCsound in Windows at present? I
> have been hoping to use it as part of the LHCsound project
> imminently about to go into schools. I am developing a
> cross-platform app that generates a csd file from various types
> of particle collision data. The Mac version of QuteCsound (6.0)
> is working fine, but the Windows version (tested on two
> machines, one XP and one Vista) quits frequently and
> unpredictably, sometimes while attempting playback, at other
> times when just working in a dialog. Note these are not crashes
> as such - it just shuts down instantly.
>
> For schools it is especially important that any packages
> supplied can install simply and run reliably "out of the box"
> i.e. with preferably no configuration needed. If QuteCsound on
> Windows could work as well as the Mac verison now does it would
> be the app of choice (though I would prefer a couple of
> alternative default settings), but the current propensity to
> quit is a game-stopper at the moment. I do not want to provide
> different tools on different platforms. If there are other
> cross-platform single-install alternatives that will do the job
> (primarily real-time and offline render - a sort of "Csound
> Media Player" really) I will be grateful for all and any
> recommendations.
>
> When it is at a sufficient stage of development, the app (built
> using wxWidgets) will be made available open source (runs on
> Linux too needless to say); as will be data files to explore.
> The interest for Csounders will be principally in creating
> alternative instruments to render a given score (a case where
> the old orc/sco separation is actually rather useful).
>
> In due course I would naturally look to adding direct Csound
> rendering internally via the API etc; but time is against me
> with so much else to do, so relying on an external "csd player"
> is the only option in the short term. While the remit for the
> project is specifically (and strictly) "outreach" with regard to
> the LHC, the ATLAS detector (the hunt for the Higgs etc etc etc)
> and the sonification of collision data, there is clearly some
> scope for introducing the wonders of Csound to enterprising
> schools; but I do need to be able to supply it (plus front-end)
> in as painless and reliable a form as possible.
>
> Richard Dobson
>
>
>
>
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

The pre-Net version of winxound used to open a player for the 
rendered file automatically, as well as naming the file with the 
orc/sco filename.  I miss that feature, but I've worked around 
it by using a csoptions entry in the csd to render to 'test' on 
the desktop.  It's easy to find, play, and rename there (at 
least for me).
Bob

On 13:59, Richard Dobson wrote:
> I do indeed like the look of WinXound very much. The one thing
> that makes QuteCsound attractive from the point of view of this
> project (getting kids involved, minimum number of steps between
> setting parameters and hearing results, etc) is the presence of
> a nice big "play" button ready to use. With WinXound I have to
> add the "-o dac" flag manually to the csound command options in
> Preferences.
>
> I have found I can modify the flags inside the app bundle itself
> for the mac verison. If I can do the same on the Windows version
> (so I can package it up for schools in that form) it is a viable
> contender. But having to go to Preferences each time to toggle
> between real-time and file is not so convenient (and too much
> danger of users fiddling with stuff they shouldn't!). I really
> want both options (real-time play and render-to-file) available
> and visible, and QuteCsound offers that in the middle of the
> toolbar - absolutely no setup needed. So at present it is still
> the favourite ~if~ is is stable on Windows.
>
> Richard Dobson
>
>
> On 20/01/2011 02:10, peiman khosravi wrote:
>> Hello,
>>
>> It should be very eay to put together a maxmsp based frontend. It
>> would run on os x and windows and the stanalode build (maxmsp
>> runtime
>> included) would requite no extra installation or setup.
>>
>> Otherwise I'd highly recommend winXound if no widgets are needed.
>>
>
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Wow..thanks Stefano.  I'm glad someone mentioned the other 
things you're planning to include.  Several were things I've 
thought would be nice, but forgot to mention in my email to you. 
  Winxound now seems like it will be my tool of choice!
Bob

On 13:59, Stefano Bonetti wrote:
> Thanks Robert for your suggestions ...
>
> About the player I haven't initially included it in the .net
> version for
> crossplattform reasons (in this new version I've used the player of
> the operating system to open the file) ...
> but, at this time, this is no more a big pain to implement it,
> so for the next
> forthcoming release (3.4.0) I will re-include it on all platforms.
> Other new features (for the moment) will be:
> - reimplementation of the orc/sco file separation and usage (and
> of course
> the ability to convert them to the csd format will remain)
> - the new untitled file will be automatically saved in a
> temporary directory
> (so if someone just want to try some things and after don't save
> the file,
> he can do it)
> - the double compiler button (as suggested by Richard)
>
> If you (or others) have suggestions, don't hesitate to contact me...
>
> Best,
> Stefano
>
>
> Il giorno 21/gen/2011, alle ore 01.46, Robert or Gretchen Foose
> ha scritto:
>
>> The pre-Net version of winxound used to open a player for the
>> rendered file automatically, as well as naming the file with
>> the orc/sco filename. I miss that feature, but I've worked
>> around it by using a csoptions entry in the csd to render to
>> 'test' on the desktop. It's easy to find, play, and rename
>> there (at least for me).
>> Bob
>>
>> On 13:59, Richard Dobson wrote:
>>> I do indeed like the look of WinXound very much. The one thing
>>> that makes QuteCsound attractive from the point of view of this
>>> project (getting kids involved, minimum number of steps between
>>> setting parameters and hearing results, etc) is the presence of
>>> a nice big "play" button ready to use. With WinXound I have to
>>> add the "-o dac" flag manually to the csound command options in
>>> Preferences.
>>>
>>> I have found I can modify the flags inside the app bundle itself
>>> for the mac verison. If I can do the same on the Windows version
>>> (so I can package it up for schools in that form) it is a viable
>>> contender. But having to go to Preferences each time to toggle
>>> between real-time and file is not so convenient (and too much
>>> danger of users fiddling with stuff they shouldn't!). I really
>>> want both options (real-time play and render-to-file) available
>>> and visible, and QuteCsound offers that in the middle of the
>>> toolbar - absolutely no setup needed. So at present it is still
>>> the favourite ~if~ is is stable on Windows.
>>>
>>> Richard Dobson
>>>
>>>
>>> On 20/01/2011 02:10, peiman khosravi wrote:
>>>> Hello,
>>>>
>>>> It should be very eay to put together a maxmsp based
>>>> frontend. It
>>>> would run on os x and windows and the stanalode build (maxmsp
>>>> runtime
>>>> included) would requite no extra installation or setup.
>>>>
>>>> Otherwise I'd highly recommend winXound if no widgets are
>>>> needed.
>>>>
>>>
>>>
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>> https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> 
>> 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 the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"