Hi all and sorry for crossposting...

I'm happy to announce a new version of QuteCsound (0.4.1). This
release is mostly a bug fix and usability enhancement release, but it
also contains a few minor useful features. One of the highlights is
localization in Spanish, German and French.

QuteCsound is a simple frontend for Csound featuring a highlighting
editor with autocomplete, interactive widgets and integrated help. It
is a cross-platform drop in replacement for MacCsound (it can open
files created in MacCsound), and aims to be a simple yet powerful and
complete development environment for Csound.

QuteCsound 0.4.1 has been tested on Windows, OS X, Linux and Solaris,
and it is free software released under the LGPLv2 or at your option GPLv3.

You can get it here:
http://sourceforge.net/project/showfiles.php?group_id=227265&package_id=275156&release_id=664354

There's more information here:
http://qutecsound.sourceforge.net/

You can download a Quick Reference pdf document in English, Spanish or
German here:
http://sourceforge.net/project/showfiles.php?group_id=227265&package_id=319704&release_id=677991

Questions, comments and suggestions can be posted to the main Csound
mailing list, or join the QuteCsound users mailing list at:
http://lists.sourceforge.net/lists/listinfo/qutecsound-users

Thanks to Joachim Heintz for continuous feedback, translation and
examples, François Pinot for the french translation and Andy
Fillebrown for the Windows installers and fixes for Windows issues.

Enjoy!
Andrés

New in 0.4.1:
-Many new examples
-Licenced under the LGPLv2 and GPLv3
-Print action in the menu (to print csd text)
-Spanish, German and French localization (many thanks to Joachim
Heintz and François Pinot)
-Line number display in status bar
-OK button is now the default button (activated with enter) for widget
preferences
-Quick Reference pdf in English, Spanish and French
-Improved indent/unindent and comment/uncomment

Fixed:
-Greatly improved performance for code highlighter
-Greatly improved performace for large graph display
-Highlighting of error line
-Open from finder on OS X
-Various permission problems for temporary files
-Fixed buttons showing correct status of panels on startup
-Improved console message handling
-Improved internal handling of values in slider and knob
-ScrollNumber widget now propagates its value correctly to other widgets
-Added xpm version of icon to reduce dependency on imagemagick for
Debian packaging
-Fixed external program launching on windows

Andres,

that is great. I meant to say I can help with the Portuguese translation,
sorry I forgot to mention it earlier. You can send me the strings.

Regards

Victor
----- Original Message ----- 
From: "Andres Cabrera" 
To: ; ; 
; ; 

Sent: Saturday, April 25, 2009 2:28 PM
Subject: [Csnd] [ann] QuteCsound 0.4.1


Hi all and sorry for crossposting...

I'm happy to announce a new version of QuteCsound (0.4.1). This
release is mostly a bug fix and usability enhancement release, but it
also contains a few minor useful features. One of the highlights is
localization in Spanish, German and French.

QuteCsound is a simple frontend for Csound featuring a highlighting
editor with autocomplete, interactive widgets and integrated help. It
is a cross-platform drop in replacement for MacCsound (it can open
files created in MacCsound), and aims to be a simple yet powerful and
complete development environment for Csound.

QuteCsound 0.4.1 has been tested on Windows, OS X, Linux and Solaris,
and it is free software released under the LGPLv2 or at your option GPLv3.

You can get it here:
http://sourceforge.net/project/showfiles.php?group_id=227265&package_id=275156&release_id=664354

There's more information here:
http://qutecsound.sourceforge.net/

You can download a Quick Reference pdf document in English, Spanish or
German here:
http://sourceforge.net/project/showfiles.php?group_id=227265&package_id=319704&release_id=677991

Questions, comments and suggestions can be posted to the main Csound
mailing list, or join the QuteCsound users mailing list at:
http://lists.sourceforge.net/lists/listinfo/qutecsound-users

Thanks to Joachim Heintz for continuous feedback, translation and
examples, François Pinot for the french translation and Andy
Fillebrown for the Windows installers and fixes for Windows issues.

Enjoy!
Andrés

New in 0.4.1:
-Many new examples
-Licenced under the LGPLv2 and GPLv3
-Print action in the menu (to print csd text)
-Spanish, German and French localization (many thanks to Joachim
Heintz and François Pinot)
-Line number display in status bar
-OK button is now the default button (activated with enter) for widget
preferences
-Quick Reference pdf in English, Spanish and French
-Improved indent/unindent and comment/uncomment

Fixed:
-Greatly improved performance for code highlighter
-Greatly improved performace for large graph display
-Highlighting of error line
-Open from finder on OS X
-Various permission problems for temporary files
-Fixed buttons showing correct status of panels on startup
-Improved console message handling
-Improved internal handling of values in slider and knob
-ScrollNumber widget now propagates its value correctly to other widgets
-Added xpm version of icon to reduce dependency on imagemagick for
Debian packaging
-Fixed external program launching on windows


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

Andres Cabrera wrote on 4/25/09 9:28 AM:

> New in 0.4.1:
> -Many new examples
> -Licenced under the LGPLv2 and GPLv3

Yay!

> -Line number display in status bar

Cool!

> -OK button is now the default button (activated with enter) for widget
> preferences

Bravo.

> Fixed:
> -Greatly improved performance for code highlighter
> -Greatly improved performace for large graph display
> -Highlighting of error line

Fantastic!

> -Open from finder on OS X

Woohooooo!!!

Thanks very much Andrés!  Downloaded and briefly tried out the new opening
from Finder feature.  Looking forward to working more easily with this new
version of QuteCsound!

Anthony Kozar
mailing-lists-1001 AT anthonykozar DOT net
http://anthonykozar.net/

Hi Andres. I just tried out the latest version and I still get a crash
every time I stop a performance. I also get a crash whenever Csound
comes to the end of a performance. I've updating my version of Csound
and I'm now running the latest version which I just built from the cvs
sources. I'm running winXP and using the float version of Csound. The
crash happens is I hit stop or re-hit the play button.

regards,
Rory.


2009/4/25 Andres Cabrera :
> Hi all and sorry for crossposting...
>
> I'm happy to announce a new version of QuteCsound (0.4.1). This
> release is mostly a bug fix and usability enhancement release, but it
> also contains a few minor useful features. One of the highlights is
> localization in Spanish, German and French.
>

Hi Rory,

What options for input and output are you using?

Cheers,
Andrés

On Sun, Apr 26, 2009 at 12:21 PM, Rory Walsh  wrote:
> Hi Andres. I just tried out the latest version and I still get a crash
> every time I stop a performance. I also get a crash whenever Csound
> comes to the end of a performance. I've updating my version of Csound
> and I'm now running the latest version which I just built from the cvs
> sources. I'm running winXP and using the float version of Csound. The
> crash happens is I hit stop or re-hit the play button.
>
> regards,
> Rory.
>
>
> 2009/4/25 Andres Cabrera :
>> Hi all and sorry for crossposting...
>>
>> I'm happy to announce a new version of QuteCsound (0.4.1). This
>> release is mostly a bug fix and usability enhancement release, but it
>> also contains a few minor useful features. One of the highlights is
>> localization in Spanish, German and French.
>>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>



-- 


Andrés

I've tried with using the CsOptions and using QuteCsound's options set
to 'portaudio -idac -iadc', neither seem to work. I can run things in
the terminal but I would like access to the GUI controls.

Rory.


2009/4/26 Andres Cabrera :
> Hi Rory,
>
> What options for input and output are you using?
>
> Cheers,
> Andrés
>
> On Sun, Apr 26, 2009 at 12:21 PM, Rory Walsh  wrote:
>> Hi Andres. I just tried out the latest version and I still get a crash
>> every time I stop a performance. I also get a crash whenever Csound
>> comes to the end of a performance. I've updating my version of Csound
>> and I'm now running the latest version which I just built from the cvs
>> sources. I'm running winXP and using the float version of Csound. The
>> crash happens is I hit stop or re-hit the play button.
>>
>> regards,
>> Rory.
>>
>>
>> 2009/4/25 Andres Cabrera :
>>> Hi all and sorry for crossposting...
>>>
>>> I'm happy to announce a new version of QuteCsound (0.4.1). This
>>> release is mostly a bug fix and usability enhancement release, but it
>>> also contains a few minor useful features. One of the highlights is
>>> localization in Spanish, German and French.
>>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>
>
>
>
> --
>
>
> Andrés
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

What about MIDI? Are you using -Ma?

Cheers,
Andrés

On Sun, Apr 26, 2009 at 4:01 PM, Rory Walsh  wrote:
> I've tried with using the CsOptions and using QuteCsound's options set
> to 'portaudio -idac -iadc', neither seem to work. I can run things in
> the terminal but I would like access to the GUI controls.
>
> Rory.
>
>
> 2009/4/26 Andres Cabrera :
>> Hi Rory,
>>
>> What options for input and output are you using?
>>
>> Cheers,
>> Andrés
>>
>> On Sun, Apr 26, 2009 at 12:21 PM, Rory Walsh  wrote:
>>> Hi Andres. I just tried out the latest version and I still get a crash
>>> every time I stop a performance. I also get a crash whenever Csound
>>> comes to the end of a performance. I've updating my version of Csound
>>> and I'm now running the latest version which I just built from the cvs
>>> sources. I'm running winXP and using the float version of Csound. The
>>> crash happens is I hit stop or re-hit the play button.
>>>
>>> regards,
>>> Rory.
>>>
>>>
>>> 2009/4/25 Andres Cabrera :
>>>> Hi all and sorry for crossposting...
>>>>
>>>> I'm happy to announce a new version of QuteCsound (0.4.1). This
>>>> release is mostly a bug fix and usability enhancement release, but it
>>>> also contains a few minor useful features. One of the highlights is
>>>> localization in Spanish, German and French.
>>>>
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>
>>
>>
>>
>> --
>>
>>
>> Andrés
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"



-- 


Andrés

Strange; here on Windows (damn Vista) it works well (I am using
csound from CVS). All examples I tested from the menu work OK.

I esp. like the scope. Students will love this. A spectrogram would be
nice too.

Victor
----- Original Message ----- 
From: "Rory Walsh" 
To: 
Sent: Sunday, April 26, 2009 6:21 PM
Subject: [Csnd] Re: [ann] QuteCsound 0.4.1


> Hi Andres. I just tried out the latest version and I still get a crash
> every time I stop a performance. I also get a crash whenever Csound
> comes to the end of a performance. I've updating my version of Csound
> and I'm now running the latest version which I just built from the cvs
> sources. I'm running winXP and using the float version of Csound. The
> crash happens is I hit stop or re-hit the play button.
>
> regards,
> Rory.
>
>
> 2009/4/25 Andres Cabrera :
>> Hi all and sorry for crossposting...
>>
>> I'm happy to announce a new version of QuteCsound (0.4.1). This
>> release is mostly a bug fix and usability enhancement release, but it
>> also contains a few minor useful features. One of the highlights is
>> localization in Spanish, German and French.
>>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
> csound" 

I'm not using any midi module. It's obviously not a problem with
QuteCsound as no one else has reported these issues. Csound runs fine
from the command line and in my other frontends. Any other ideas?

2009/4/26 victor :
> Strange; here on Windows (damn Vista) it works well (I am using
> csound from CVS). All examples I tested from the menu work OK.
>
> I esp. like the scope. Students will love this. A spectrogram would be
> nice too.

Victor, there is a way of displaying spectra. Look at the graph widget example.

Rory.


2009/4/27 Rory Walsh :
> I'm not using any midi module. It's obviously not a problem with
> QuteCsound as no one else has reported these issues. Csound runs fine
> from the command line and in my other frontends. Any other ideas?
>
> 2009/4/26 victor :
>> Strange; here on Windows (damn Vista) it works well (I am using
>> csound from CVS). All examples I tested from the menu work OK.
>>
>> I esp. like the scope. Students will love this. A spectrogram would be
>> nice too.
>

Hi,

On Sun, Apr 26, 2009 at 6:10 PM, Rory Walsh  wrote:
> I'm not using any midi module. It's obviously not a problem with
> QuteCsound as no one else has reported these issues. Csound runs fine
> from the command line and in my other frontends. Any other ideas?
>

It's a particular issue with the way you've got things configured. Do
you have the same problem if you render to disk instead of running in
realtime?

Cheers,
Andrés

Also, can you try unchecking the run in separate thread button to rule
out threading problems?

Cheers,
Andrés

On Sun, Apr 26, 2009 at 9:56 PM, Andres Cabrera  wrote:
> Hi,
>
> On Sun, Apr 26, 2009 at 6:10 PM, Rory Walsh  wrote:
>> I'm not using any midi module. It's obviously not a problem with
>> QuteCsound as no one else has reported these issues. Csound runs fine
>> from the command line and in my other frontends. Any other ideas?
>>
>
> It's a particular issue with the way you've got things configured. Do
> you have the same problem if you render to disk instead of running in
> realtime?
>
> Cheers,
> Andrés
>



-- 


Andrés

Hi,
I have also had some problems with the new Qute release crashing, 
especially when closing tabs that I have recently worked with. Moreover, 
I can only get  copy - paste to work once after I have opened the 
program - afterwards nothing happens. I am running on WinXP and floats.
Best,
andreas bergsland
> I'm not using any midi module. It's obviously not a problem with
> QuteCsound as no one else has reported these issues. Csound runs fine
> from the command line and in my other frontends. Any other ideas?
>
> 2009/4/26 victor :
>   
>> Strange; here on Windows (damn Vista) it works well (I am using
>> csound from CVS). All examples I tested from the menu work OK.
>>
>> I esp. like the scope. Students will love this. A spectrogram would be
>> nice too.
>>     
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>   


-- 
Andreas Bergsland,
universitetslektor / PhD-kandidat

Musikkteknologiseksjonen
Institutt for musikk
Olavskvartalet
NTNU
7491 Trondheim

Besøksadresse: Fjordgt.1 (3.etg.)
e-post: andreas.bergsland@hf.ntnu.no
Tlf: 7359 0096
Mob: 4566 3316

Turning off the 'run in separate thread' sorted the problem. Thanks Andres,

Rory.


2009/4/27 Andres Cabrera :
> Also, can you try unchecking the run in separate thread button to rule
> out threading problems?
>
> Cheers,
> Andrés
>
> On Sun, Apr 26, 2009 at 9:56 PM, Andres Cabrera  wrote:
>> Hi,
>>
>> On Sun, Apr 26, 2009 at 6:10 PM, Rory Walsh  wrote:
>>> I'm not using any midi module. It's obviously not a problem with
>>> QuteCsound as no one else has reported these issues. Csound runs fine
>>> from the command line and in my other frontends. Any other ideas?
>>>
>>
>> It's a particular issue with the way you've got things configured. Do
>> you have the same problem if you render to disk instead of running in
>> realtime?
>>
>> Cheers,
>> Andrés
>>
>
>
>
> --
>
>
> Andrés
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hi Andres,

I like your implementation of graphs and esp. the dispfft support. One thing
that would be useful would be to allow for multiple dispfft instances. At 
the
moment, I can do that with two graphs widgets, provided they are from
two separate instruments. Even then there is some cross-wiring in the
refreshing of the graphs (I get some interference from one dispfft to 
another),
but it more or less works.
If I have 2 dispffts in the same instr I seem to only be able to see one. 
This
might be a Csound graph issue, I don't know.

I am thinking I  might use QuteCsound in class next semester, so I am 
starting
to check it more carefully now. Great work, Andres.

Regards

Victor

Several spectrograms would be nice too. This can be done in Cabbage,
albeit only as a proof of concept through the use of Victor's pvs
channel IO opcodes. Cabbage also sends a-rate data via the channel
opcodes to its scope widget, in that way it can display any signal. I
just realised that invalue/outvalue does not have an a-rate version, I
thought it had one, perhaps one should be added?

Rory.


2009/4/27 victor :
> Hi Andres,
>
> I like your implementation of graphs and esp. the dispfft support. One thing
> that would be useful would be to allow for multiple dispfft instances. At
> the
> moment, I can do that with two graphs widgets, provided they are from
> two separate instruments. Even then there is some cross-wiring in the
> refreshing of the graphs (I get some interference from one dispfft to
> another),
> but it more or less works.
> If I have 2 dispffts in the same instr I seem to only be able to see one.
> This
> might be a Csound graph issue, I don't know.
>
> I am thinking I  might use QuteCsound in class next semester, so I am
> starting
> to check it more carefully now. Great work, Andres.
>
> Regards
>
> Victor
>
>
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>

Hi Andreas,

On Mon, Apr 27, 2009 at 2:52 AM, Andreas Bergsland
 wrote:
> Hi,
> I have also had some problems with the new Qute release crashing, especially
> when closing tabs that I have recently worked with. Moreover, I can only get
>  copy - paste to work once after I have opened the program - afterwards
> nothing happens. I am running on WinXP and floats.

Is the csd running? When you change tabs while the csd is running,
QuteCsound will crash. I need to fix that.
The copy paste issue has been reported, but I can't reproduce it since
it happens on Windows only....

Cheers,
Andrés


> Best,
> andreas bergsland
>>
>> I'm not using any midi module. It's obviously not a problem with
>> QuteCsound as no one else has reported these issues. Csound runs fine
>> from the command line and in my other frontends. Any other ideas?
>>
>> 2009/4/26 victor :
>>
>>>
>>> Strange; here on Windows (damn Vista) it works well (I am using
>>> csound from CVS). All examples I tested from the menu work OK.
>>>
>>> I esp. like the scope. Students will love this. A spectrogram would be
>>> nice too.
>>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>
>
> --
> Andreas Bergsland,
> universitetslektor / PhD-kandidat
>
> Musikkteknologiseksjonen
> Institutt for musikk
> Olavskvartalet
> NTNU
> 7491 Trondheim
>
> Besøksadresse: Fjordgt.1 (3.etg.)
> e-post: andreas.bergsland@hf.ntnu.no
> Tlf: 7359 0096
> Mob: 4566 3316
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>



-- 


Andrés

OK,

Then it's a threading problem. I need to look at this. If you could
produce a backtrace, it would be great....


Cheers,
Andrés

On Mon, Apr 27, 2009 at 3:21 AM, Rory Walsh  wrote:
> Turning off the 'run in separate thread' sorted the problem. Thanks Andres,
>
> Rory.
>
>
> 2009/4/27 Andres Cabrera :
>> Also, can you try unchecking the run in separate thread button to rule
>> out threading problems?
>>
>> Cheers,
>> Andrés
>>
>> On Sun, Apr 26, 2009 at 9:56 PM, Andres Cabrera  wrote:
>>> Hi,
>>>
>>> On Sun, Apr 26, 2009 at 6:10 PM, Rory Walsh  wrote:
>>>> I'm not using any midi module. It's obviously not a problem with
>>>> QuteCsound as no one else has reported these issues. Csound runs fine
>>>> from the command line and in my other frontends. Any other ideas?
>>>>
>>>
>>> It's a particular issue with the way you've got things configured. Do
>>> you have the same problem if you render to disk instead of running in
>>> realtime?
>>>
>>> Cheers,
>>> Andrés
>>>
>>
>>
>>
>> --
>>
>>
>> Andrés
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"



-- 


Andrés

> Then it's a threading problem. I need to look at this. If you could
> produce a backtrace, it would be great....

Let me know how and I'll try, don't I have to build QuteCsound first
however? If so I will try but I'm very busy at present so I don't know
exactly when I'll get around to it.

Rory.


>
> Cheers,
> Andrés
>
> On Mon, Apr 27, 2009 at 3:21 AM, Rory Walsh  wrote:
>> Turning off the 'run in separate thread' sorted the problem. Thanks Andres,
>>
>> Rory.
>>
>>
>> 2009/4/27 Andres Cabrera :
>>> Also, can you try unchecking the run in separate thread button to rule
>>> out threading problems?
>>>
>>> Cheers,
>>> Andrés
>>>
>>> On Sun, Apr 26, 2009 at 9:56 PM, Andres Cabrera  wrote:
>>>> Hi,
>>>>
>>>> On Sun, Apr 26, 2009 at 6:10 PM, Rory Walsh  wrote:
>>>>> I'm not using any midi module. It's obviously not a problem with
>>>>> QuteCsound as no one else has reported these issues. Csound runs fine
>>>>> from the command line and in my other frontends. Any other ideas?
>>>>>
>>>>
>>>> It's a particular issue with the way you've got things configured. Do
>>>> you have the same problem if you render to disk instead of running in
>>>> realtime?
>>>>
>>>> Cheers,
>>>> Andrés
>>>>
>>>
>>>
>>>
>>> --
>>>
>>>
>>> Andrés
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
>
> --
>
>
> Andrés
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Ye
> Is the csd running? 
Yes, it must have. When I stop csd before closing, everything is fine:)
Apart from that I think that Qute aspires to being THE GUI for csound 
for me, at least once the windows issues are solved and it becomes 
stable. I love the ease of making and editing widgets. Actually I just 
used it in class demonstrating formant synthesis - it worked great!
It would also have been great to have a widget that could display krate 
signals - almost like printk, only  in graphics. Maybe one could choose 
whether to have one single or several k-variables in the same widget, 
with different colours???
And, of course the table editing option that have been mentioned earlier.
Keep up the good work.
Best,
Andreas Bergsland
> When you change tabs while the csd is running,
> QuteCsound will crash. I need to fix that.
> The copy paste issue has been reported, but I can't reproduce it since
> it happens on Windows only....
>
> Cheers,
> Andrés
>
>
>   
>> Best,
>> andreas bergsland
>>     
>>> I'm not using any midi module. It's obviously not a problem with
>>> QuteCsound as no one else has reported these issues. Csound runs fine
>>> from the command line and in my other frontends. Any other ideas?
>>>
>>> 2009/4/26 victor :
>>>
>>>       
>>>> Strange; here on Windows (damn Vista) it works well (I am using
>>>> csound from CVS). All examples I tested from the menu work OK.
>>>>
>>>> I esp. like the scope. Students will love this. A spectrogram would be
>>>> nice too.
>>>>
>>>>         
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>>       
>> --
>> Andreas Bergsland,
>> universitetslektor / PhD-kandidat
>>
>> Musikkteknologiseksjonen
>> Institutt for musikk
>> Olavskvartalet
>> NTNU
>> 7491 Trondheim
>>
>> Besøksadresse: Fjordgt.1 (3.etg.)
>> e-post: andreas.bergsland@hf.ntnu.no
>> Tlf: 7359 0096
>> Mob: 4566 3316
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>     
>
>
>
>   

Hi Rory,

It would be enough to run it in gdb (if you have it installed), and
produce a backtrace from it when it crashes. I the think release
version wont have debugging symbols, but the information provided
should still be enough to know what´s going on.

Cheers,
Andrés

On Mon, Apr 27, 2009 at 6:52 AM, Rory Walsh  wrote:
>> Then it's a threading problem. I need to look at this. If you could
>> produce a backtrace, it would be great....
>
> Let me know how and I'll try, don't I have to build QuteCsound first
> however? If so I will try but I'm very busy at present so I don't know
> exactly when I'll get around to it.
>
> Rory.
>
>
>>
>> Cheers,
>> Andrés
>>
>> On Mon, Apr 27, 2009 at 3:21 AM, Rory Walsh  wrote:
>>> Turning off the 'run in separate thread' sorted the problem. Thanks Andres,
>>>
>>> Rory.
>>>
>>>
>>> 2009/4/27 Andres Cabrera :
>>>> Also, can you try unchecking the run in separate thread button to rule
>>>> out threading problems?
>>>>
>>>> Cheers,
>>>> Andrés
>>>>
>>>> On Sun, Apr 26, 2009 at 9:56 PM, Andres Cabrera  wrote:
>>>>> Hi,
>>>>>
>>>>> On Sun, Apr 26, 2009 at 6:10 PM, Rory Walsh  wrote:
>>>>>> I'm not using any midi module. It's obviously not a problem with
>>>>>> QuteCsound as no one else has reported these issues. Csound runs fine
>>>>>> from the command line and in my other frontends. Any other ideas?
>>>>>>
>>>>>
>>>>> It's a particular issue with the way you've got things configured. Do
>>>>> you have the same problem if you render to disk instead of running in
>>>>> realtime?
>>>>>
>>>>> Cheers,
>>>>> Andrés
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>>
>>>> Andrés
>>>>
>>>>
>>>> Send bugs reports to this list.
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>
>>
>>
>> --
>>
>>
>> Andrés
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"



-- 


Andrés

HI Andreas,

On Mon, Apr 27, 2009 at 8:28 AM, Andreas Bergsland
 wrote:
> Ye
>>
>> Is the csd running?
>
> Yes, it must have. When I stop csd before closing, everything is fine:)
> Apart from that I think that Qute aspires to being THE GUI for csound for
> me, at least once the windows issues are solved and it becomes stable. I
> love the ease of making and editing widgets. Actually I just used it in
> class demonstrating formant synthesis - it worked great!

Nice. Can you share the csd?

> It would also have been great to have a widget that could display krate
> signals - almost like printk, only  in graphics. Maybe one could choose
> whether to have one single or several k-variables in the same widget, with
> different colours???

Not really sure what you mean, but you can use the value widget to
display k-rate variables or strings.

Cheers,
Andrés

I've download gdb for windows. Can you give me the commands I should
use? If I try run with file set to QuteCsound I get the following:

(gdb) file qutecsound-f.exe
Reading symbols from C:\Program Files\QuteCsound-f/qutecsound-f.exe...(no debugg
ing symbols found)...done.
(gdb) run

Starting program: C:\Program Files\QuteCsound-f/qutecsound-f.exe traget-exec=qut
ecsound-f.exe
[New thread 5052.0x1670]
warning: Can not parse XML library list; XML support was disabled at compile tim
e

Program received signal SIGSEGV, Segmentation fault.
0x100153cc in ?? ()
(gdb)

Sorry but I've no idea how to use gdb!

Rory.





2009/4/27 Andres Cabrera :
> Hi Rory,
>
> It would be enough to run it in gdb (if you have it installed), and
> produce a backtrace from it when it crashes. I the think release
> version wont have debugging symbols, but the information provided
> should still be enough to know what´s going on.
>
> Cheers,
> Andrés
>
> On Mon, Apr 27, 2009 at 6:52 AM, Rory Walsh  wrote:
>>> Then it's a threading problem. I need to look at this. If you could
>>> produce a backtrace, it would be great....
>>
>> Let me know how and I'll try, don't I have to build QuteCsound first
>> however? If so I will try but I'm very busy at present so I don't know
>> exactly when I'll get around to it.
>>
>> Rory.
>>
>>
>>>
>>> Cheers,
>>> Andrés
>>>
>>> On Mon, Apr 27, 2009 at 3:21 AM, Rory Walsh  wrote:
>>>> Turning off the 'run in separate thread' sorted the problem. Thanks Andres,
>>>>
>>>> Rory.
>>>>
>>>>
>>>> 2009/4/27 Andres Cabrera :
>>>>> Also, can you try unchecking the run in separate thread button to rule
>>>>> out threading problems?
>>>>>
>>>>> Cheers,
>>>>> Andrés
>>>>>
>>>>> On Sun, Apr 26, 2009 at 9:56 PM, Andres Cabrera  wrote:
>>>>>> Hi,
>>>>>>
>>>>>> On Sun, Apr 26, 2009 at 6:10 PM, Rory Walsh  wrote:
>>>>>>> I'm not using any midi module. It's obviously not a problem with
>>>>>>> QuteCsound as no one else has reported these issues. Csound runs fine
>>>>>>> from the command line and in my other frontends. Any other ideas?
>>>>>>>
>>>>>>
>>>>>> It's a particular issue with the way you've got things configured. Do
>>>>>> you have the same problem if you render to disk instead of running in
>>>>>> realtime?
>>>>>>
>>>>>> Cheers,
>>>>>> Andrés
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>>
>>>>> Andrés
>>>>>
>>>>>
>>>>> Send bugs reports to this list.
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>
>>>>
>>>> Send bugs reports to this list.
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>
>>>
>>>
>>> --
>>>
>>>
>>> Andrés
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
>
> --
>
>
> Andrés
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Just use the command "bt" to produce the backtrace.

Cheers,
Andrés

On Mon, Apr 27, 2009 at 10:39 AM, Rory Walsh  wrote:
> I've download gdb for windows. Can you give me the commands I should
> use? If I try run with file set to QuteCsound I get the following:
>
> (gdb) file qutecsound-f.exe
> Reading symbols from C:\Program Files\QuteCsound-f/qutecsound-f.exe...(no debugg
> ing symbols found)...done.
> (gdb) run
>
> Starting program: C:\Program Files\QuteCsound-f/qutecsound-f.exe traget-exec=qut
> ecsound-f.exe
> [New thread 5052.0x1670]
> warning: Can not parse XML library list; XML support was disabled at compile tim
> e
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x100153cc in ?? ()
> (gdb)
>
> Sorry but I've no idea how to use gdb!
>
> Rory.
>
>
>
>
>
> 2009/4/27 Andres Cabrera :
>> Hi Rory,
>>
>> It would be enough to run it in gdb (if you have it installed), and
>> produce a backtrace from it when it crashes. I the think release
>> version wont have debugging symbols, but the information provided
>> should still be enough to know what´s going on.
>>
>> Cheers,
>> Andrés
>>
>> On Mon, Apr 27, 2009 at 6:52 AM, Rory Walsh  wrote:
>>>> Then it's a threading problem. I need to look at this. If you could
>>>> produce a backtrace, it would be great....
>>>
>>> Let me know how and I'll try, don't I have to build QuteCsound first
>>> however? If so I will try but I'm very busy at present so I don't know
>>> exactly when I'll get around to it.
>>>
>>> Rory.
>>>
>>>
>>>>
>>>> Cheers,
>>>> Andrés
>>>>
>>>> On Mon, Apr 27, 2009 at 3:21 AM, Rory Walsh  wrote:
>>>>> Turning off the 'run in separate thread' sorted the problem. Thanks Andres,
>>>>>
>>>>> Rory.
>>>>>
>>>>>
>>>>> 2009/4/27 Andres Cabrera :
>>>>>> Also, can you try unchecking the run in separate thread button to rule
>>>>>> out threading problems?
>>>>>>
>>>>>> Cheers,
>>>>>> Andrés
>>>>>>
>>>>>> On Sun, Apr 26, 2009 at 9:56 PM, Andres Cabrera  wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> On Sun, Apr 26, 2009 at 6:10 PM, Rory Walsh  wrote:
>>>>>>>> I'm not using any midi module. It's obviously not a problem with
>>>>>>>> QuteCsound as no one else has reported these issues. Csound runs fine
>>>>>>>> from the command line and in my other frontends. Any other ideas?
>>>>>>>>
>>>>>>>
>>>>>>> It's a particular issue with the way you've got things configured. Do
>>>>>>> you have the same problem if you render to disk instead of running in
>>>>>>> realtime?
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Andrés
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>>
>>>>>> Andrés
>>>>>>
>>>>>>
>>>>>> Send bugs reports to this list.
>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>>
>>>>>
>>>>> Send bugs reports to this list.
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>>
>>>> Andrés
>>>>
>>>>
>>>> Send bugs reports to this list.
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>
>>
>>
>> --
>>
>>
>> Andrés
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"



-- 


Andrés

Ok, here's what I got, still not sre I'm doing this right??

(gdb) run
Starting program: C:\Program Files\QuteCsound-f/qutecsound-f.exe
[New thread 1612.0x2e0]
warning: Can not parse XML library list; XML support was disabled at compile tim
e

Program received signal SIGSEGV, Segmentation fault.
0x100153cc in ?? ()
(gdb) c
Continuing.
[New thread 1612.0x1228]
[New thread 1612.0x16e0]
[New thread 1612.0x810]
warning: DocumentPage::getMacOption() Option Options:  not found!
warning: DocumentPage::getMacOption() Option Options:  not found!
warning: DocumentPage::getMacOption() Option Options:  not found!
warning: DocumentPage::getMacOption() Option Options:  not found!

[New thread 1612.0x1774]
[New thread 1612.0x10b8]

Program received signal SIGSEGV, Segmentation fault.
0x697e8176 in ?? ()
(gdb) bt
#0  0x697e8176 in ?? ()
#1  0x697e8160 in ?? ()
#2  0x00000000 in ?? ()
(gdb)

Not sure that's right so I tried continuing after teh second segfault too:

(gdb) file qutecsound-f.exe
Reading symbols from C:\Program Files\QuteCsound-f/qutecsound-f.exe...(no debugg
ing symbols found)...done.
(gdb) run
Starting program: C:\Program Files\QuteCsound-f/qutecsound-f.exe
[New thread 5976.0x11a4]
warning: Can not parse XML library list; XML support was disabled at compile tim
e

Program received signal SIGSEGV, Segmentation fault.
0x100153cc in ?? ()
(gdb) c
Continuing.
[New thread 5976.0x1710]
[New thread 5976.0x1214]
[New thread 5976.0xe28]
warning: DocumentPage::getMacOption() Option Options:  not found!

warning: DocumentPage::getMacOption() Option Options:  not found!

warning: DocumentPage::getMacOption() Option Options:  not found!

warning: DocumentPage::getMacOption() Option Options:  not found!

[New thread 5976.0x564]
[New thread 5976.0xf50]

Program received signal SIGSEGV, Segmentation fault.
0x697e8176 in ?? ()
(gdb) c
Continuing.
warning: Command Line args:

warning: csound

warning: C:\DOCUME~1\Rory\LOCALS~1\Temp\Ciara_Mc_Entee_Pitch_shifting.csd

warning: -+rtaudio=portaudio

warning: -iadc

warning: -odac

warning: --env:CSNOSTOP=yes

[New thread 5976.0x968]
[New thread 5976.0x9b0]
[New thread 5976.0x1698]
[New thread 5976.0xd54]
[New thread 5976.0x164c]
[New thread 5976.0x13f8]
[New thread 5976.0x13b0]
[New thread 5976.0x1498]
[New thread 5976.0x11a0]
[New thread 5976.0x109c]
[New thread 5976.0x15a8]
[New thread 5976.0x1760]
warning: Csound compiled 0


Program received signal SIGSEGV, Segmentation fault.
0x62483a28 in ?? ()
(gdb) c
Continuing.

Program received signal SIGSEGV, Segmentation fault.
0x62483a28 in ?? ()
(gdb) c
Continuing.

Program exited with code 030000000005.
(gdb) bt
No stack.
(gdb)

Hope some of this info helps...

Rory.




2009/4/27 Andres Cabrera :
> Just use the command "bt" to produce the backtrace.
>
> Cheers,
> Andrés
>
> On Mon, Apr 27, 2009 at 10:39 AM, Rory Walsh  wrote:
>> I've download gdb for windows. Can you give me the commands I should
>> use? If I try run with file set to QuteCsound I get the following:
>>
>> (gdb) file qutecsound-f.exe
>> Reading symbols from C:\Program Files\QuteCsound-f/qutecsound-f.exe...(no debugg
>> ing symbols found)...done.
>> (gdb) run
>>
>> Starting program: C:\Program Files\QuteCsound-f/qutecsound-f.exe traget-exec=qut
>> ecsound-f.exe
>> [New thread 5052.0x1670]
>> warning: Can not parse XML library list; XML support was disabled at compile tim
>> e
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> 0x100153cc in ?? ()
>> (gdb)
>>
>> Sorry but I've no idea how to use gdb!
>>
>> Rory.
>>
>>
>>
>>
>>
>> 2009/4/27 Andres Cabrera :
>>> Hi Rory,
>>>
>>> It would be enough to run it in gdb (if you have it installed), and
>>> produce a backtrace from it when it crashes. I the think release
>>> version wont have debugging symbols, but the information provided
>>> should still be enough to know what´s going on.
>>>
>>> Cheers,
>>> Andrés
>>>
>>> On Mon, Apr 27, 2009 at 6:52 AM, Rory Walsh  wrote:
>>>>> Then it's a threading problem. I need to look at this. If you could
>>>>> produce a backtrace, it would be great....
>>>>
>>>> Let me know how and I'll try, don't I have to build QuteCsound first
>>>> however? If so I will try but I'm very busy at present so I don't know
>>>> exactly when I'll get around to it.
>>>>
>>>> Rory.
>>>>
>>>>
>>>>>
>>>>> Cheers,
>>>>> Andrés
>>>>>
>>>>> On Mon, Apr 27, 2009 at 3:21 AM, Rory Walsh  wrote:
>>>>>> Turning off the 'run in separate thread' sorted the problem. Thanks Andres,
>>>>>>
>>>>>> Rory.
>>>>>>
>>>>>>
>>>>>> 2009/4/27 Andres Cabrera :
>>>>>>> Also, can you try unchecking the run in separate thread button to rule
>>>>>>> out threading problems?
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Andrés
>>>>>>>
>>>>>>> On Sun, Apr 26, 2009 at 9:56 PM, Andres Cabrera  wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> On Sun, Apr 26, 2009 at 6:10 PM, Rory Walsh  wrote:
>>>>>>>>> I'm not using any midi module. It's obviously not a problem with
>>>>>>>>> QuteCsound as no one else has reported these issues. Csound runs fine
>>>>>>>>> from the command line and in my other frontends. Any other ideas?
>>>>>>>>>
>>>>>>>>
>>>>>>>> It's a particular issue with the way you've got things configured. Do
>>>>>>>> you have the same problem if you render to disk instead of running in
>>>>>>>> realtime?
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Andrés
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>>
>>>>>>> Andrés
>>>>>>>
>>>>>>>
>>>>>>> Send bugs reports to this list.
>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>>>
>>>>>>
>>>>>> Send bugs reports to this list.
>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>>
>>>>> Andrés
>>>>>
>>>>>
>>>>> Send bugs reports to this list.
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>
>>>>
>>>> Send bugs reports to this list.
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>
>>>
>>>
>>> --
>>>
>>>
>>> Andrés
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
>
> --
>
>
> Andrés
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hi,
Here is the csd. Nothing fancy or complicated, but works OK. As I said I 
was delighted by the ease of use for the widgets.
But where can I find the value widget that you mention?
Andreas
> HI Andreas,
>
> On Mon, Apr 27, 2009 at 8:28 AM, Andreas Bergsland
>  wrote:
>   
>> Ye
>>     
>>> Is the csd running?
>>>       
>> Yes, it must have. When I stop csd before closing, everything is fine:)
>> Apart from that I think that Qute aspires to being THE GUI for csound for
>> me, at least once the windows issues are solved and it becomes stable. I
>> love the ease of making and editing widgets. Actually I just used it in
>> class demonstrating formant synthesis - it worked great!
>>     
>
> Nice. Can you share the csd?
>
>   
>> It would also have been great to have a widget that could display krate
>> signals - almost like printk, only  in graphics. Maybe one could choose
>> whether to have one single or several k-variables in the same widget, with
>> different colours???
>>     
>
> Not really sure what you mean, but you can use the value widget to
> display k-rate variables or strings.
>
> Cheers,
> Andrés
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Thanks Rory. It seems you would need to build with debugging enabled...

Cheers,
Andrés

On Mon, Apr 27, 2009 at 1:03 PM, Rory Walsh  wrote:
> Ok, here's what I got, still not sre I'm doing this right??
>
> (gdb) run
> Starting program: C:\Program Files\QuteCsound-f/qutecsound-f.exe
> [New thread 1612.0x2e0]
> warning: Can not parse XML library list; XML support was disabled at compile tim
> e
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x100153cc in ?? ()
> (gdb) c
> Continuing.
> [New thread 1612.0x1228]
> [New thread 1612.0x16e0]
> [New thread 1612.0x810]
> warning: DocumentPage::getMacOption() Option Options:  not found!
> warning: DocumentPage::getMacOption() Option Options:  not found!
> warning: DocumentPage::getMacOption() Option Options:  not found!
> warning: DocumentPage::getMacOption() Option Options:  not found!
>
> [New thread 1612.0x1774]
> [New thread 1612.0x10b8]
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x697e8176 in ?? ()
> (gdb) bt
> #0  0x697e8176 in ?? ()
> #1  0x697e8160 in ?? ()
> #2  0x00000000 in ?? ()
> (gdb)
>
> Not sure that's right so I tried continuing after teh second segfault too:
>
> (gdb) file qutecsound-f.exe
> Reading symbols from C:\Program Files\QuteCsound-f/qutecsound-f.exe...(no debugg
> ing symbols found)...done.
> (gdb) run
> Starting program: C:\Program Files\QuteCsound-f/qutecsound-f.exe
> [New thread 5976.0x11a4]
> warning: Can not parse XML library list; XML support was disabled at compile tim
> e
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x100153cc in ?? ()
> (gdb) c
> Continuing.
> [New thread 5976.0x1710]
> [New thread 5976.0x1214]
> [New thread 5976.0xe28]
> warning: DocumentPage::getMacOption() Option Options:  not found!
>
> warning: DocumentPage::getMacOption() Option Options:  not found!
>
> warning: DocumentPage::getMacOption() Option Options:  not found!
>
> warning: DocumentPage::getMacOption() Option Options:  not found!
>
> [New thread 5976.0x564]
> [New thread 5976.0xf50]
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x697e8176 in ?? ()
> (gdb) c
> Continuing.
> warning: Command Line args:
>
> warning: csound
>
> warning: C:\DOCUME~1\Rory\LOCALS~1\Temp\Ciara_Mc_Entee_Pitch_shifting.csd
>
> warning: -+rtaudio=portaudio
>
> warning: -iadc
>
> warning: -odac
>
> warning: --env:CSNOSTOP=yes
>
> [New thread 5976.0x968]
> [New thread 5976.0x9b0]
> [New thread 5976.0x1698]
> [New thread 5976.0xd54]
> [New thread 5976.0x164c]
> [New thread 5976.0x13f8]
> [New thread 5976.0x13b0]
> [New thread 5976.0x1498]
> [New thread 5976.0x11a0]
> [New thread 5976.0x109c]
> [New thread 5976.0x15a8]
> [New thread 5976.0x1760]
> warning: Csound compiled 0
>
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x62483a28 in ?? ()
> (gdb) c
> Continuing.
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x62483a28 in ?? ()
> (gdb) c
> Continuing.
>
> Program exited with code 030000000005.
> (gdb) bt
> No stack.
> (gdb)
>
> Hope some of this info helps...
>
> Rory.
>
>
>
>
> 2009/4/27 Andres Cabrera :
>> Just use the command "bt" to produce the backtrace.
>>
>> Cheers,
>> Andrés
>>
>> On Mon, Apr 27, 2009 at 10:39 AM, Rory Walsh  wrote:
>>> I've download gdb for windows. Can you give me the commands I should
>>> use? If I try run with file set to QuteCsound I get the following:
>>>
>>> (gdb) file qutecsound-f.exe
>>> Reading symbols from C:\Program Files\QuteCsound-f/qutecsound-f.exe...(no debugg
>>> ing symbols found)...done.
>>> (gdb) run
>>>
>>> Starting program: C:\Program Files\QuteCsound-f/qutecsound-f.exe traget-exec=qut
>>> ecsound-f.exe
>>> [New thread 5052.0x1670]
>>> warning: Can not parse XML library list; XML support was disabled at compile tim
>>> e
>>>
>>> Program received signal SIGSEGV, Segmentation fault.
>>> 0x100153cc in ?? ()
>>> (gdb)
>>>
>>> Sorry but I've no idea how to use gdb!
>>>
>>> Rory.
>>>
>>>
>>>
>>>
>>>
>>> 2009/4/27 Andres Cabrera :
>>>> Hi Rory,
>>>>
>>>> It would be enough to run it in gdb (if you have it installed), and
>>>> produce a backtrace from it when it crashes. I the think release
>>>> version wont have debugging symbols, but the information provided
>>>> should still be enough to know what´s going on.
>>>>
>>>> Cheers,
>>>> Andrés
>>>>
>>>> On Mon, Apr 27, 2009 at 6:52 AM, Rory Walsh  wrote:
>>>>>> Then it's a threading problem. I need to look at this. If you could
>>>>>> produce a backtrace, it would be great....
>>>>>
>>>>> Let me know how and I'll try, don't I have to build QuteCsound first
>>>>> however? If so I will try but I'm very busy at present so I don't know
>>>>> exactly when I'll get around to it.
>>>>>
>>>>> Rory.
>>>>>
>>>>>
>>>>>>
>>>>>> Cheers,
>>>>>> Andrés
>>>>>>
>>>>>> On Mon, Apr 27, 2009 at 3:21 AM, Rory Walsh  wrote:
>>>>>>> Turning off the 'run in separate thread' sorted the problem. Thanks Andres,
>>>>>>>
>>>>>>> Rory.
>>>>>>>
>>>>>>>
>>>>>>> 2009/4/27 Andres Cabrera :
>>>>>>>> Also, can you try unchecking the run in separate thread button to rule
>>>>>>>> out threading problems?
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Andrés
>>>>>>>>
>>>>>>>> On Sun, Apr 26, 2009 at 9:56 PM, Andres Cabrera  wrote:
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> On Sun, Apr 26, 2009 at 6:10 PM, Rory Walsh  wrote:
>>>>>>>>>> I'm not using any midi module. It's obviously not a problem with
>>>>>>>>>> QuteCsound as no one else has reported these issues. Csound runs fine
>>>>>>>>>> from the command line and in my other frontends. Any other ideas?
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> It's a particular issue with the way you've got things configured. Do
>>>>>>>>> you have the same problem if you render to disk instead of running in
>>>>>>>>> realtime?
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>> Andrés
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>>
>>>>>>>> Andrés
>>>>>>>>
>>>>>>>>
>>>>>>>> Send bugs reports to this list.
>>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>>>>
>>>>>>>
>>>>>>> Send bugs reports to this list.
>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>>
>>>>>> Andrés
>>>>>>
>>>>>>
>>>>>> Send bugs reports to this list.
>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>>
>>>>>
>>>>> Send bugs reports to this list.
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>>
>>>> Andrés
>>>>
>>>>
>>>> Send bugs reports to this list.
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>
>>
>>
>> --
>>
>>
>> Andrés
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"



-- 


Andrés

Hi Andreas,

Thanks, nice example. Would you mind if I add it to the examples?

It's not called value, sorry, it's called display. I've attached an example.

Cheers,
Andrés

On Mon, Apr 27, 2009 at 1:58 PM, Andreas Bergsland
 wrote:
> Hi,
> Here is the csd. Nothing fancy or complicated, but works OK. As I said I was
> delighted by the ease of use for the widgets.
> But where can I find the value widget that you mention?
> Andreas
>>
>> HI Andreas,
>>
>> On Mon, Apr 27, 2009 at 8:28 AM, Andreas Bergsland
>>  wrote:
>>
>>>
>>> Ye
>>>
>>>>
>>>> Is the csd running?
>>>>
>>>
>>> Yes, it must have. When I stop csd before closing, everything is fine:)
>>> Apart from that I think that Qute aspires to being THE GUI for csound for
>>> me, at least once the windows issues are solved and it becomes stable. I
>>> love the ease of making and editing widgets. Actually I just used it in
>>> class demonstrating formant synthesis - it worked great!
>>>
>>
>> Nice. Can you share the csd?
>>
>>
>>>
>>> It would also have been great to have a widget that could display krate
>>> signals - almost like printk, only  in graphics. Maybe one could choose
>>> whether to have one single or several k-variables in the same widget,
>>> with
>>> different colours???
>>>
>>
>> Not really sure what you mean, but you can use the value widget to
>> display k-rate variables or strings.
>>
>> Cheers,
>> Andrés
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
> ;************************************************************
> ;                       FORMANT SYNTHESIZER WITH GLOTTAL PARAMETERS
> ;                                       Andreas Bergsland, 2009
> ;************************************************************
>
> 
>
>
> 
> --displays -odac -b2048 -B4096
> ;-odac
> 
>
>
> 
>
>        sr     = 44100
>        kr     = 4410
>        ksmps  = 10
>        nchnls = 2
>
> ; *****************************************************
> ;                               TRIGGER INSTRUMENT
> ;******************************************************
> instr   1
>
> ;               Get value for global source
> kOpenQ  invalue "OQ"
> kSpeedQ invalue "SQ"
> ;               On value
> kon             invalue "on"
>
> ;               Trigger play instrument
> schedkwhen      kon, 2, 1, 10, 0, 3, kOpenQ, kSpeedQ
> kon=1
>
> endin
>
>
> ; *************************************************************
> ;                       FORMANT SYNTHESIZER INSTRUMENT
> instr   10
>
> ;                       Get formant parameters
> kcutoff1        invalue "Cutoff1"
> kreson1 invalue "Reson1"
> kcutoff2        invalue "Cutoff2"
> kreson2 invalue "Reson2"
> kcutoff3        invalue "Cutoff3"
> kreson3 invalue "Reson3"
> kcutoff4        invalue "Cutoff4"
> kreson4 invalue "Reson4"
>
>
> iflen   =       4096
>
> ;               Get glottal parameters
> iOpenQ  =       p4
> iSQ             =       p5 * 12/14              ; Speed quotient -
> compensate for the number of open vs closed segments in the ftable linseg
>
> iOpen   =       iOpenQ * iflen
> iClose  =       iflen - iOpen
> ip              =       iOpen/26                        ; Calculate duration
> for segments in the open phase
> iO              =       ip * iSQ                        ; Apply speed
> quotient for opening
> iC              =       ip / iSQ                        ; and closing phase
>
> iOp     =       14*iO                           ; Scale so that values fits
> the open phase
> iCl     =       12*iC
> iT      =       (iOp + iCl)/iOpen
>
> iO      =       iO / iT                         ; Calulate open
> iC      =       iC / iT                         ; and closed segments
>
> ;       Values for a glottal waveform taken from Inger Karlsson (1988),
> "Glottal waveform parameters for different speaker types" (Could be mapped
> more accurately)
> i0      =       0       ;t1
> i1      =       .02
> i2      =       .05
> i3      =       .1
> i4      =       .15
> i5      =       .24
> i6      =       .33
> i7      =       .45
> i8      =       .575
> i9      =       .645
> i10     =       .775
> i11     =       .845
> i12     =       .945
> i13     =       .985
> i14     =       .99     ; ca.t2
> i15     =       .95
> i16     =       .8
> i17     =       .57
> i18     =       .3      ;ca.t3
> i19     =       .11
> i20     =       .06
> i21     =       .04
> i22     =       .02
> i23     =       .01
> i24     =       .002
> i25     =       .001
> i26     =       0       ;t4
>
> ;               Make ftable for glottal waveform
> isource ftgen   0, 0, iflen, 7, i0, iO, i1, iO, i2, iO, i3, iO, i4, iO, i5,
> iO, i6, iO, i7, iO, i8, \
>                                        iO, i9,
> iO,i10,iO,i11,iO,i12,iO,i13,iO,i14,iC,i15, iC, i16, iC, i17,\
>
>  iC,i18,iC,i19,iC,i20,iC,i21,iC,i22,iC,i23,iC,i24,iC,i25,iC, i26, iClose, 0
>
> kf0     invalue "f0"
> kamp    linen   4000, .2, p3, .35
>
>
> ;***************************************************************
> ;                       JITTER, three different opcodes
> kcpsMin =       8
> kcpsMax =       20
> kjitamp =       .025
> kjit1 jspline kjitamp, kcpsMin, kcpsMax
>
> kjitamp =       .027
> kcpsMin =       2
> kcpsMax =       20
> kjit2   jitter  2.7, 2, 20
>
> ktotamp =       .027
> kamp1   =       .2
> kcps1   =       1.5
> kamp2   =       .25
> kcps2   =       4.5
> kamp3   =       .3
> kcps3   =       15.5
> kjit3   jitter2 ktotamp, kamp1, kcps1, kamp2, kcps2, kamp3, kcps3
>
> kjitOn  invalue "JitOn"
> kjit            =       kjit3 * kjitOn
>
> ;***************************************************************
> ;               VIBRATO
>
> iSine   ftgen   0, 0, 1024, 10, 1
> kvibamp expseg  0.001, p3*.3, 1.5, p3*.7, 2.5
> ivibfrek        =               5.6
> kvibrand        randh   .1, ivibfrek
> kvibfrek        =               ivibfrek + kvibrand
>
> kvibOn  invalue "Vib"
> kvib            oscil   kvibamp * kvibOn, kvibfrek, iSine
>
>
>
> ;***************************************************************
> ;                       SHIMMER
>
> kShimOn invalue "ShimOn"
> iavgshim        =       (ampdb(0.39)/ampdb(0))-1
> print   iavgshim
> kshimamp        =       kamp * iavgshim * kShimOn
> kcpsMin =       8
> kcpsMAx =       20
> kshim jspline kshimamp, kcpsMin, kcpsMax
> ;*****************************************************************
>
> ;*****************************************************************
> ;               Overshoot
>
> kOShoot invalue "OShoot"
> if0             =       i(kf0)
> iOShoot =       i(kOShoot)
> iamount =       .08 * if0 * iOShoot
>
> kOShoot linseg  iamount, .06, 0, p3-.05, 0
> ;******************************************************************
>
> ; *****************************************************************
> ;               MAKE SOURCE SOUND
>
> ; Noise
> kNoise  invalue "Noise"
> anoise  rand    kamp * kNoise
> anoise  butbp   anoise, 4500, 4000
>
> ; Glottal pulses
> avoiced oscili  kamp + kshim, kf0 + (kjit*kf0) + kvib + kOShoot, isource
>
> alyd    =       avoiced  + anoise
> ;******************************************************************
> ;               FORMANT FILTERS - reson with double filtering
>
> aform1  reson   alyd,   kcutoff1, kreson1 * kcutoff1 / 100
> aform1  reson   aform1, kcutoff1, kreson1 * kcutoff1 / 100
> aform2  reson   alyd,   kcutoff2, kreson2 * kcutoff2 / 100
> aform2  reson   aform2, kcutoff2, kreson2 * kcutoff2 / 100
> aform3  reson   alyd,   kcutoff3, kreson3 * kcutoff3 / 100
> aform3  reson   aform3, kcutoff3, kreson3 * kcutoff3 / 100
> aform4  reson   alyd,   kcutoff4, kreson4 * kcutoff4 / 100
> aform4  reson   aform4, kcutoff4, kreson4 * kcutoff4 / 100
>
> ;               add formant jitter (experimental)
> kcutoff1        =       kcutoff1 + kcutoff1*kjit3*.3
> kcutoff2        =       kcutoff2 + kcutoff2*kjit3*.3
> kcutoff3        =       kcutoff3 + kcutoff3*kjit3*.3
> kcutoff4        =       kcutoff4 + kcutoff4*kjit3*.3
>
> ;aform4 reson   alyd,   kcutoff4, kreson4 * kcutoff4 / 100
> ;aform3 reson   aform4, kcutoff3, kreson3 * kcutoff3 / 100
> ;aform2 reson   aform3, kcutoff2, kreson2 * kcutoff2 / 100
> ;aform1 reson   aform2, kcutoff1, kreson1 * kcutoff1 / 100
>
> ;               balance
> abal1   balance aform1, alyd
> abal2   balance aform2, alyd
> abal3   balance aform3, alyd
> abal4   balance aform4, alyd
>
> ;               get formant amps
> kFamp1  invalue "FormAmp1"
> kFamp2  invalue "FormAmp2"
> kFamp3  invalue "FormAmp3"
> kFamp4  invalue "FormAmp4"
>
>
> ;               Mix
> afilt   =       abal1 * kFamp1 +abal2 * kFamp2 +abal3 * kFamp3 +
> abal4*kFamp4
>
> ;               Master Volume
> kMasterVol invalue      "Vol"
> aout            =       afilt * kMasterVol
>
> ;               View spectrum
> dispfft afilt, 1, 2048 , .05, 0
>
> outs    aout, aout
>
> endin
>
>
> 
>
>
> 
>
> i1 0 3000
> 
>
>
> 
> 
> Version: 3
> Render: Real
> Ask: Yes
> Functions: ioObject
> Listing: Window
> WindowBounds: 799 71 641 603
> CurrentView: io
> IOViewEdit: On
> Options:
> 
> 
> ioView background {54484, 50886, 40092}
> ioGraph {6, 4} {780, 228} table 0.000000 1.000000
> ioButton {451, 331} {100, 30} event 1.000000 "on" "Play" "/" i2  0 10
> ioSlider {7, 249} {120, 20} 0.010000 0.990000 0.532667 OQ
> ioText {128, 242} {42, 32} display 0.000000 0.00100 "OQ" left "MS Shell Dlg
> 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 0.5327
> ioSlider {5, 290} {120, 20} 0.800000 4.000000 2.160000 SQ
> ioText {128, 284} {44, 32} display 0.000000 0.00100 "SQ" left "MS Shell Dlg
> 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 2.1600
> ioText {172, 242} {171, 31} display 0.000000 0.00100 "" left "MS Shell Dlg
> 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border Open Quotient (OQ)
> ioText {173, 284} {171, 31} display 0.000000 0.00100 "" left "MS Shell Dlg
> 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border Speed Quotient
> (SQ)
> ioSlider {34, 424} {20, 100} 250.000000 1000.000000 857.500000 Cutoff1
> ioText {14, 389} {52, 30} display 0.000000 0.00100 "Cutoff1" left "MS Shell
> Dlg 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 857.5000
> ioSlider {84, 425} {20, 100} 0.500000 30.000000 6.400000 Reson1
> ioText {74, 387} {42, 33} display 0.000000 0.00100 "Reson1" left "MS Shell
> Dlg 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 6.4000
> ioSlider {216, 422} {20, 100} 800.000000 3200.000000 1280.000000 Cutoff2
> ioText {198, 387} {49, 31} display 0.000000 0.00100 "Cutoff2" left "MS Shell
> Dlg 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 1280.0000
> ioSlider {273, 422} {20, 100} 0.500000 30.000000 4.040000 Reson2
> ioText {260, 387} {43, 33} display 0.000000 0.00100 "Reson2" left "MS Shell
> Dlg 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 4.6300
> ioSlider {404, 423} {20, 100} 2400.000000 3500.000000 3016.000000 Cutoff3
> ioText {390, 388} {49, 32} display 0.000000 0.00100 "Cutoff3" left "MS Shell
> Dlg 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 3016.0000
> ioSlider {456, 425} {20, 100} 0.500000 30.000000 4.040000 Reson3
> ioText {444, 387} {44, 33} display 0.000000 0.00100 "Reson3" left "MS Shell
> Dlg 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 4.0400
> ioSlider {135, 424} {20, 100} 0.000000 1.000000 0.460000 FormAmp1
> ioText {121, 388} {43, 32} display 0.000000 0.00100 "FormAmp1" left "MS
> Shell Dlg 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 0.4800
> ioSlider {327, 423} {20, 100} 0.000000 1.000000 0.670000 FormAmp2
> ioText {313, 387} {43, 33} display 0.000000 0.00100 "FormAmp2" left "MS
> Shell Dlg 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 0.6700
> ioSlider {514, 426} {20, 100} 0.000000 1.000000 0.230000 FormAmp3
> ioText {497, 388} {44, 33} display 0.000000 0.00100 "FormAmp3" left "MS
> Shell Dlg 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 0.2300
> ioKnob {649, 246} {80, 80} 0.000000 1.000000 0.010000 0.797980 Vol
> ioSlider {588, 422} {20, 100} 3500.000000 4500.000000 4030.000000 Cutoff4
> ioText {574, 387} {49, 32} display 0.000000 0.00100 "Cutoff4" left "MS Shell
> Dlg 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 4030.0000
> ioSlider {640, 424} {20, 100} 0.500000 50.000000 10.400000 Reson4
> ioText {628, 386} {44, 33} display 0.000000 0.00100 "Reson4" left "MS Shell
> Dlg 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 10.4000
> ioSlider {698, 425} {20, 100} 0.000000 1.000000 0.280000 FormAmp4
> ioText {681, 387} {44, 33} display 0.000000 0.00100 "FormAmp4" left "MS
> Shell Dlg 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 0.2900
> ioText {24, 368} {37, 26} label 0.000000 0.00100 "" left "MS Shell Dlg 2" 16
> {0, 0, 0} {65280, 65280, 65280} nobackground noborder Frek
> ioText {77, 367} {37, 26} label 0.000000 0.00100 "" left "MS Shell Dlg 2" 16
> {0, 0, 0} {65280, 65280, 65280} nobackground noborder BW
> ioText {129, 367} {37, 26} label 0.000000 0.00100 "" left "MS Shell Dlg 2"
> 16 {0, 0, 0} {65280, 65280, 65280} nobackground noborder Amp
> ioText {211, 369} {37, 26} label 0.000000 0.00100 "" left "MS Shell Dlg 2"
> 16 {0, 0, 0} {65280, 65280, 65280} nobackground noborder Frek
> ioText {264, 368} {37, 26} label 0.000000 0.00100 "" left "MS Shell Dlg 2"
> 16 {0, 0, 0} {65280, 65280, 65280} nobackground noborder BW
> ioText {316, 368} {37, 26} label 0.000000 0.00100 "" left "MS Shell Dlg 2"
> 16 {0, 0, 0} {65280, 65280, 65280} nobackground noborder Amp
> ioText {397, 368} {37, 26} label 0.000000 0.00100 "" left "MS Shell Dlg 2"
> 16 {0, 0, 0} {65280, 65280, 65280} nobackground noborder Frek
> ioText {450, 367} {37, 26} label 0.000000 0.00100 "" left "MS Shell Dlg 2"
> 16 {0, 0, 0} {65280, 65280, 65280} nobackground noborder BW
> ioText {502, 367} {37, 26} label 0.000000 0.00100 "" left "MS Shell Dlg 2"
> 16 {0, 0, 0} {65280, 65280, 65280} nobackground noborder Amp
> ioText {579, 368} {37, 26} label 0.000000 0.00100 "" left "MS Shell Dlg 2"
> 16 {0, 0, 0} {65280, 65280, 65280} nobackground noborder Frek
> ioText {632, 367} {37, 26} label 0.000000 0.00100 "" left "MS Shell Dlg 2"
> 16 {0, 0, 0} {65280, 65280, 65280} nobackground noborder BW
> ioText {684, 367} {37, 26} label 0.000000 0.00100 "" left "MS Shell Dlg 2"
> 16 {0, 0, 0} {65280, 65280, 65280} nobackground noborder Amp
> ioText {49, 527} {96, 31} display 0.000000 0.00100 "" left "MS Shell Dlg 2"
> 20 {0, 0, 0} {65280, 65280, 65280} nobackground border Formant 1¬
> ioText {232, 528} {96, 31} display 0.000000 0.00100 "" left "MS Shell Dlg 2"
> 20 {0, 0, 0} {65280, 65280, 65280} nobackground border Formant 2
> ioText {423, 529} {96, 31} display 0.000000 0.00100 "" left "MS Shell Dlg 2"
> 20 {0, 0, 0} {65280, 65280, 65280} nobackground border Formant 3
> ioText {609, 529} {96, 31} display 0.000000 0.00100 "" left "MS Shell Dlg 2"
> 20 {0, 0, 0} {65280, 65280, 65280} nobackground border Formant 4
> ioText {678, 321} {39, 30} display 0.000000 0.00100 "" left "MS Shell Dlg 2"
> 16 {0, 0, 0} {65280, 65280, 65280} nobackground noborder Vol
> ioKnob {551, 246} {80, 80} 90.000000 500.000000 0.010000 197.676768 f0
> ioText {582, 320} {39, 30} display 0.000000 0.00100 "" left "MS Shell Dlg 2"
> 16 {0, 0, 0} {65280, 65280, 65280} nobackground noborder f0
> ioText {498, 246} {52, 29} display 0.000000 0.00100 "f0" left "MS Shell Dlg
> 2" 16 {0, 0, 0} {65280, 65280, 65280} nobackground border 197.6768
> ioCheckbox {351, 242} {20, 20} off Vib
> ioText {373, 240} {35, 25} display 0.000000 0.00100 "" left "MS Shell Dlg 2"
> 16 {0, 0, 0} {65280, 65280, 65280} nobackground border Vibr
> ioCheckbox {350, 267} {20, 20} on JitOn
> ioCheckbox {351, 291} {20, 20} on ShimOn
> ioText {374, 265} {35, 25} display 0.000000 0.00100 "" left "MS Shell Dlg 2"
> 16 {0, 0, 0} {65280, 65280, 65280} nobackground border Jit
> ioText {374, 288} {41, 25} display 0.000000 0.00100 "" left "MS Shell Dlg 2"
> 16 {0, 0, 0} {65280, 65280, 65280} nobackground border Shim
> ioCheckbox {351, 315} {20, 20} on OShoot
> ioText {374, 313} {70, 25} display 0.000000 0.00100 "" left "MS Shell Dlg 2"
> 16 {0, 0, 0} {65280, 65280, 65280} nobackground border Overshoot
> ioSlider {5, 330} {120, 20} 0.000000 0.200000 0.041667 Noise
> ioText {128, 322} {44, 32} display 0.000000 0.00100 "Noise" left "MS Shell
> Dlg 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 0.0450
> ioText {174, 323} {171, 31} display 0.000000 0.00100 "" left "MS Shell Dlg
> 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border Aspiration noise
> 
>
>
>



-- 


Andrés

Hi Victor,

On Mon, Apr 27, 2009 at 4:07 AM, victor  wrote:
> Hi Andres,
>
> I like your implementation of graphs and esp. the dispfft support. One thing
> that would be useful would be to allow for multiple dispfft instances. At
> the
> moment, I can do that with two graphs widgets, provided they are from
> two separate instruments. Even then there is some cross-wiring in the
> refreshing of the graphs (I get some interference from one dispfft to
> another),
> but it more or less works.
> If I have 2 dispffts in the same instr I seem to only be able to see one.
> This
> might be a Csound graph issue, I don't know.
>

I haven't looked into it, but it seems to be a csound issue, since
QuteCsound doesn't even know which instrument created the graph, it
only obeys the callback (but bear in mind that many times I've thought
this it ended up being my mistake...)

Cheers,
Andrés

Hi Rory,

That's a very interesting idea. I'll look into it.

Cheers,
Andrés

On Mon, Apr 27, 2009 at 4:32 AM, Rory Walsh  wrote:
> Several spectrograms would be nice too. This can be done in Cabbage,
> albeit only as a proof of concept through the use of Victor's pvs
> channel IO opcodes. Cabbage also sends a-rate data via the channel
> opcodes to its scope widget, in that way it can display any signal. I
> just realised that invalue/outvalue does not have an a-rate version, I
> thought it had one, perhaps one should be added?
>
> Rory.
>
>
> 2009/4/27 victor :
>> Hi Andres,
>>
>> I like your implementation of graphs and esp. the dispfft support. One thing
>> that would be useful would be to allow for multiple dispfft instances. At
>> the
>> moment, I can do that with two graphs widgets, provided they are from
>> two separate instruments. Even then there is some cross-wiring in the
>> refreshing of the graphs (I get some interference from one dispfft to
>> another),
>> but it more or less works.
>> If I have 2 dispffts in the same instr I seem to only be able to see one.
>> This
>> might be a Csound graph issue, I don't know.
>>
>> I am thinking I  might use QuteCsound in class next semester, so I am
>> starting
>> to check it more carefully now. Great work, Andres.
>>
>> Regards
>>
>> Victor
>>
>>
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"



-- 


Andrés

> Hi Andreas,
>
> Thanks, nice example. Would you mind if I add it to the examples?
>   
No, sure, go ahead:)  If I ever make a somewhat cleaner and neater 
version I can post it.
> It's not called value, sorry, it's called display. I've attached an example.
>   
Ok, then I'm in. Well, actually what I would like to suggest was a 
graphical display of k-rate values, that is, much like the scope so that 
one can monitor how the values behave (or perhaps like multislider in 
Max/MSP). I have often missed that when tuning / calibrating 
instruments, especially with some kind of live control input. Maybe that 
could also include some kind of y-axis with value-reference points that 
could be customized.

Best, Andreas

> Cheers,
> Andrés
>
> On Mon, Apr 27, 2009 at 1:58 PM, Andreas Bergsland
>  wrote:
>   
>> Hi,
>> Here is the csd. Nothing fancy or complicated, but works OK. As I said I was
>> delighted by the ease of use for the widgets.
>> But where can I find the value widget that you mention?
>> Andreas
>>     
>>> HI Andreas,
>>>
>>> On Mon, Apr 27, 2009 at 8:28 AM, Andreas Bergsland
>>>  wrote:
>>>
>>>       
>>>> Ye
>>>>
>>>>         
>>>>> Is the csd running?
>>>>>
>>>>>           
>>>> Yes, it must have. When I stop csd before closing, everything is fine:)
>>>> Apart from that I think that Qute aspires to being THE GUI for csound for
>>>> me, at least once the windows issues are solved and it becomes stable. I
>>>> love the ease of making and editing widgets. Actually I just used it in
>>>> class demonstrating formant synthesis - it worked great!
>>>>
>>>>         
>>> Nice. Can you share the csd?
>>>
>>>
>>>       
>>>> It would also have been great to have a widget that could display krate
>>>> signals - almost like printk, only  in graphics. Maybe one could choose
>>>> whether to have one single or several k-variables in the same widget,
>>>> with
>>>> different colours???
>>>>
>>>>         
>>> Not really sure what you mean, but you can use the value widget to
>>> display k-rate variables or strings.
>>>
>>> Cheers,
>>> Andrés
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>       
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>> ;************************************************************
>> ;                       FORMANT SYNTHESIZER WITH GLOTTAL PARAMETERS
>> ;                                       Andreas Bergsland, 2009
>> ;************************************************************
>>
>> 
>>
>>
>> 
>> --displays -odac -b2048 -B4096
>> ;-odac
>> 
>>
>>
>> 
>>
>>        sr     = 44100
>>        kr     = 4410
>>        ksmps  = 10
>>        nchnls = 2
>>
>> ; *****************************************************
>> ;                               TRIGGER INSTRUMENT
>> ;******************************************************
>> instr   1
>>
>> ;               Get value for global source
>> kOpenQ  invalue "OQ"
>> kSpeedQ invalue "SQ"
>> ;               On value
>> kon             invalue "on"
>>
>> ;               Trigger play instrument
>> schedkwhen      kon, 2, 1, 10, 0, 3, kOpenQ, kSpeedQ
>> kon=1
>>
>> endin
>>
>>
>> ; *************************************************************
>> ;                       FORMANT SYNTHESIZER INSTRUMENT
>> instr   10
>>
>> ;                       Get formant parameters
>> kcutoff1        invalue "Cutoff1"
>> kreson1 invalue "Reson1"
>> kcutoff2        invalue "Cutoff2"
>> kreson2 invalue "Reson2"
>> kcutoff3        invalue "Cutoff3"
>> kreson3 invalue "Reson3"
>> kcutoff4        invalue "Cutoff4"
>> kreson4 invalue "Reson4"
>>
>>
>> iflen   =       4096
>>
>> ;               Get glottal parameters
>> iOpenQ  =       p4
>> iSQ             =       p5 * 12/14              ; Speed quotient -
>> compensate for the number of open vs closed segments in the ftable linseg
>>
>> iOpen   =       iOpenQ * iflen
>> iClose  =       iflen - iOpen
>> ip              =       iOpen/26                        ; Calculate duration
>> for segments in the open phase
>> iO              =       ip * iSQ                        ; Apply speed
>> quotient for opening
>> iC              =       ip / iSQ                        ; and closing phase
>>
>> iOp     =       14*iO                           ; Scale so that values fits
>> the open phase
>> iCl     =       12*iC
>> iT      =       (iOp + iCl)/iOpen
>>
>> iO      =       iO / iT                         ; Calulate open
>> iC      =       iC / iT                         ; and closed segments
>>
>> ;       Values for a glottal waveform taken from Inger Karlsson (1988),
>> "Glottal waveform parameters for different speaker types" (Could be mapped
>> more accurately)
>> i0      =       0       ;t1
>> i1      =       .02
>> i2      =       .05
>> i3      =       .1
>> i4      =       .15
>> i5      =       .24
>> i6      =       .33
>> i7      =       .45
>> i8      =       .575
>> i9      =       .645
>> i10     =       .775
>> i11     =       .845
>> i12     =       .945
>> i13     =       .985
>> i14     =       .99     ; ca.t2
>> i15     =       .95
>> i16     =       .8
>> i17     =       .57
>> i18     =       .3      ;ca.t3
>> i19     =       .11
>> i20     =       .06
>> i21     =       .04
>> i22     =       .02
>> i23     =       .01
>> i24     =       .002
>> i25     =       .001
>> i26     =       0       ;t4
>>
>> ;               Make ftable for glottal waveform
>> isource ftgen   0, 0, iflen, 7, i0, iO, i1, iO, i2, iO, i3, iO, i4, iO, i5,
>> iO, i6, iO, i7, iO, i8, \
>>                                        iO, i9,
>> iO,i10,iO,i11,iO,i12,iO,i13,iO,i14,iC,i15, iC, i16, iC, i17,\
>>
>>  iC,i18,iC,i19,iC,i20,iC,i21,iC,i22,iC,i23,iC,i24,iC,i25,iC, i26, iClose, 0
>>
>> kf0     invalue "f0"
>> kamp    linen   4000, .2, p3, .35
>>
>>
>> ;***************************************************************
>> ;                       JITTER, three different opcodes
>> kcpsMin =       8
>> kcpsMax =       20
>> kjitamp =       .025
>> kjit1 jspline kjitamp, kcpsMin, kcpsMax
>>
>> kjitamp =       .027
>> kcpsMin =       2
>> kcpsMax =       20
>> kjit2   jitter  2.7, 2, 20
>>
>> ktotamp =       .027
>> kamp1   =       .2
>> kcps1   =       1.5
>> kamp2   =       .25
>> kcps2   =       4.5
>> kamp3   =       .3
>> kcps3   =       15.5
>> kjit3   jitter2 ktotamp, kamp1, kcps1, kamp2, kcps2, kamp3, kcps3
>>
>> kjitOn  invalue "JitOn"
>> kjit            =       kjit3 * kjitOn
>>
>> ;***************************************************************
>> ;               VIBRATO
>>
>> iSine   ftgen   0, 0, 1024, 10, 1
>> kvibamp expseg  0.001, p3*.3, 1.5, p3*.7, 2.5
>> ivibfrek        =               5.6
>> kvibrand        randh   .1, ivibfrek
>> kvibfrek        =               ivibfrek + kvibrand
>>
>> kvibOn  invalue "Vib"
>> kvib            oscil   kvibamp * kvibOn, kvibfrek, iSine
>>
>>
>>
>> ;***************************************************************
>> ;                       SHIMMER
>>
>> kShimOn invalue "ShimOn"
>> iavgshim        =       (ampdb(0.39)/ampdb(0))-1
>> print   iavgshim
>> kshimamp        =       kamp * iavgshim * kShimOn
>> kcpsMin =       8
>> kcpsMAx =       20
>> kshim jspline kshimamp, kcpsMin, kcpsMax
>> ;*****************************************************************
>>
>> ;*****************************************************************
>> ;               Overshoot
>>
>> kOShoot invalue "OShoot"
>> if0             =       i(kf0)
>> iOShoot =       i(kOShoot)
>> iamount =       .08 * if0 * iOShoot
>>
>> kOShoot linseg  iamount, .06, 0, p3-.05, 0
>> ;******************************************************************
>>
>> ; *****************************************************************
>> ;               MAKE SOURCE SOUND
>>
>> ; Noise
>> kNoise  invalue "Noise"
>> anoise  rand    kamp * kNoise
>> anoise  butbp   anoise, 4500, 4000
>>
>> ; Glottal pulses
>> avoiced oscili  kamp + kshim, kf0 + (kjit*kf0) + kvib + kOShoot, isource
>>
>> alyd    =       avoiced  + anoise
>> ;******************************************************************
>> ;               FORMANT FILTERS - reson with double filtering
>>
>> aform1  reson   alyd,   kcutoff1, kreson1 * kcutoff1 / 100
>> aform1  reson   aform1, kcutoff1, kreson1 * kcutoff1 / 100
>> aform2  reson   alyd,   kcutoff2, kreson2 * kcutoff2 / 100
>> aform2  reson   aform2, kcutoff2, kreson2 * kcutoff2 / 100
>> aform3  reson   alyd,   kcutoff3, kreson3 * kcutoff3 / 100
>> aform3  reson   aform3, kcutoff3, kreson3 * kcutoff3 / 100
>> aform4  reson   alyd,   kcutoff4, kreson4 * kcutoff4 / 100
>> aform4  reson   aform4, kcutoff4, kreson4 * kcutoff4 / 100
>>
>> ;               add formant jitter (experimental)
>> kcutoff1        =       kcutoff1 + kcutoff1*kjit3*.3
>> kcutoff2        =       kcutoff2 + kcutoff2*kjit3*.3
>> kcutoff3        =       kcutoff3 + kcutoff3*kjit3*.3
>> kcutoff4        =       kcutoff4 + kcutoff4*kjit3*.3
>>
>> ;aform4 reson   alyd,   kcutoff4, kreson4 * kcutoff4 / 100
>> ;aform3 reson   aform4, kcutoff3, kreson3 * kcutoff3 / 100
>> ;aform2 reson   aform3, kcutoff2, kreson2 * kcutoff2 / 100
>> ;aform1 reson   aform2, kcutoff1, kreson1 * kcutoff1 / 100
>>
>> ;               balance
>> abal1   balance aform1, alyd
>> abal2   balance aform2, alyd
>> abal3   balance aform3, alyd
>> abal4   balance aform4, alyd
>>
>> ;               get formant amps
>> kFamp1  invalue "FormAmp1"
>> kFamp2  invalue "FormAmp2"
>> kFamp3  invalue "FormAmp3"
>> kFamp4  invalue "FormAmp4"
>>
>>
>> ;               Mix
>> afilt   =       abal1 * kFamp1 +abal2 * kFamp2 +abal3 * kFamp3 +
>> abal4*kFamp4
>>
>> ;               Master Volume
>> kMasterVol invalue      "Vol"
>> aout            =       afilt * kMasterVol
>>
>> ;               View spectrum
>> dispfft afilt, 1, 2048 , .05, 0
>>
>> outs    aout, aout
>>
>> endin
>>
>>
>> 
>>
>>
>> 
>>
>> i1 0 3000
>> 
>>
>>
>> 
>> 
>> Version: 3
>> Render: Real
>> Ask: Yes
>> Functions: ioObject
>> Listing: Window
>> WindowBounds: 799 71 641 603
>> CurrentView: io
>> IOViewEdit: On
>> Options:
>> 
>> 
>> ioView background {54484, 50886, 40092}
>> ioGraph {6, 4} {780, 228} table 0.000000 1.000000
>> ioButton {451, 331} {100, 30} event 1.000000 "on" "Play" "/" i2  0 10
>> ioSlider {7, 249} {120, 20} 0.010000 0.990000 0.532667 OQ
>> ioText {128, 242} {42, 32} display 0.000000 0.00100 "OQ" left "MS Shell Dlg
>> 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 0.5327
>> ioSlider {5, 290} {120, 20} 0.800000 4.000000 2.160000 SQ
>> ioText {128, 284} {44, 32} display 0.000000 0.00100 "SQ" left "MS Shell Dlg
>> 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 2.1600
>> ioText {172, 242} {171, 31} display 0.000000 0.00100 "" left "MS Shell Dlg
>> 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border Open Quotient (OQ)
>> ioText {173, 284} {171, 31} display 0.000000 0.00100 "" left "MS Shell Dlg
>> 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border Speed Quotient
>> (SQ)
>> ioSlider {34, 424} {20, 100} 250.000000 1000.000000 857.500000 Cutoff1
>> ioText {14, 389} {52, 30} display 0.000000 0.00100 "Cutoff1" left "MS Shell
>> Dlg 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 857.5000
>> ioSlider {84, 425} {20, 100} 0.500000 30.000000 6.400000 Reson1
>> ioText {74, 387} {42, 33} display 0.000000 0.00100 "Reson1" left "MS Shell
>> Dlg 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 6.4000
>> ioSlider {216, 422} {20, 100} 800.000000 3200.000000 1280.000000 Cutoff2
>> ioText {198, 387} {49, 31} display 0.000000 0.00100 "Cutoff2" left "MS Shell
>> Dlg 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 1280.0000
>> ioSlider {273, 422} {20, 100} 0.500000 30.000000 4.040000 Reson2
>> ioText {260, 387} {43, 33} display 0.000000 0.00100 "Reson2" left "MS Shell
>> Dlg 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 4.6300
>> ioSlider {404, 423} {20, 100} 2400.000000 3500.000000 3016.000000 Cutoff3
>> ioText {390, 388} {49, 32} display 0.000000 0.00100 "Cutoff3" left "MS Shell
>> Dlg 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 3016.0000
>> ioSlider {456, 425} {20, 100} 0.500000 30.000000 4.040000 Reson3
>> ioText {444, 387} {44, 33} display 0.000000 0.00100 "Reson3" left "MS Shell
>> Dlg 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 4.0400
>> ioSlider {135, 424} {20, 100} 0.000000 1.000000 0.460000 FormAmp1
>> ioText {121, 388} {43, 32} display 0.000000 0.00100 "FormAmp1" left "MS
>> Shell Dlg 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 0.4800
>> ioSlider {327, 423} {20, 100} 0.000000 1.000000 0.670000 FormAmp2
>> ioText {313, 387} {43, 33} display 0.000000 0.00100 "FormAmp2" left "MS
>> Shell Dlg 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 0.6700
>> ioSlider {514, 426} {20, 100} 0.000000 1.000000 0.230000 FormAmp3
>> ioText {497, 388} {44, 33} display 0.000000 0.00100 "FormAmp3" left "MS
>> Shell Dlg 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 0.2300
>> ioKnob {649, 246} {80, 80} 0.000000 1.000000 0.010000 0.797980 Vol
>> ioSlider {588, 422} {20, 100} 3500.000000 4500.000000 4030.000000 Cutoff4
>> ioText {574, 387} {49, 32} display 0.000000 0.00100 "Cutoff4" left "MS Shell
>> Dlg 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 4030.0000
>> ioSlider {640, 424} {20, 100} 0.500000 50.000000 10.400000 Reson4
>> ioText {628, 386} {44, 33} display 0.000000 0.00100 "Reson4" left "MS Shell
>> Dlg 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 10.4000
>> ioSlider {698, 425} {20, 100} 0.000000 1.000000 0.280000 FormAmp4
>> ioText {681, 387} {44, 33} display 0.000000 0.00100 "FormAmp4" left "MS
>> Shell Dlg 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 0.2900
>> ioText {24, 368} {37, 26} label 0.000000 0.00100 "" left "MS Shell Dlg 2" 16
>> {0, 0, 0} {65280, 65280, 65280} nobackground noborder Frek
>> ioText {77, 367} {37, 26} label 0.000000 0.00100 "" left "MS Shell Dlg 2" 16
>> {0, 0, 0} {65280, 65280, 65280} nobackground noborder BW
>> ioText {129, 367} {37, 26} label 0.000000 0.00100 "" left "MS Shell Dlg 2"
>> 16 {0, 0, 0} {65280, 65280, 65280} nobackground noborder Amp
>> ioText {211, 369} {37, 26} label 0.000000 0.00100 "" left "MS Shell Dlg 2"
>> 16 {0, 0, 0} {65280, 65280, 65280} nobackground noborder Frek
>> ioText {264, 368} {37, 26} label 0.000000 0.00100 "" left "MS Shell Dlg 2"
>> 16 {0, 0, 0} {65280, 65280, 65280} nobackground noborder BW
>> ioText {316, 368} {37, 26} label 0.000000 0.00100 "" left "MS Shell Dlg 2"
>> 16 {0, 0, 0} {65280, 65280, 65280} nobackground noborder Amp
>> ioText {397, 368} {37, 26} label 0.000000 0.00100 "" left "MS Shell Dlg 2"
>> 16 {0, 0, 0} {65280, 65280, 65280} nobackground noborder Frek
>> ioText {450, 367} {37, 26} label 0.000000 0.00100 "" left "MS Shell Dlg 2"
>> 16 {0, 0, 0} {65280, 65280, 65280} nobackground noborder BW
>> ioText {502, 367} {37, 26} label 0.000000 0.00100 "" left "MS Shell Dlg 2"
>> 16 {0, 0, 0} {65280, 65280, 65280} nobackground noborder Amp
>> ioText {579, 368} {37, 26} label 0.000000 0.00100 "" left "MS Shell Dlg 2"
>> 16 {0, 0, 0} {65280, 65280, 65280} nobackground noborder Frek
>> ioText {632, 367} {37, 26} label 0.000000 0.00100 "" left "MS Shell Dlg 2"
>> 16 {0, 0, 0} {65280, 65280, 65280} nobackground noborder BW
>> ioText {684, 367} {37, 26} label 0.000000 0.00100 "" left "MS Shell Dlg 2"
>> 16 {0, 0, 0} {65280, 65280, 65280} nobackground noborder Amp
>> ioText {49, 527} {96, 31} display 0.000000 0.00100 "" left "MS Shell Dlg 2"
>> 20 {0, 0, 0} {65280, 65280, 65280} nobackground border Formant 1¬
>> ioText {232, 528} {96, 31} display 0.000000 0.00100 "" left "MS Shell Dlg 2"
>> 20 {0, 0, 0} {65280, 65280, 65280} nobackground border Formant 2
>> ioText {423, 529} {96, 31} display 0.000000 0.00100 "" left "MS Shell Dlg 2"
>> 20 {0, 0, 0} {65280, 65280, 65280} nobackground border Formant 3
>> ioText {609, 529} {96, 31} display 0.000000 0.00100 "" left "MS Shell Dlg 2"
>> 20 {0, 0, 0} {65280, 65280, 65280} nobackground border Formant 4
>> ioText {678, 321} {39, 30} display 0.000000 0.00100 "" left "MS Shell Dlg 2"
>> 16 {0, 0, 0} {65280, 65280, 65280} nobackground noborder Vol
>> ioKnob {551, 246} {80, 80} 90.000000 500.000000 0.010000 197.676768 f0
>> ioText {582, 320} {39, 30} display 0.000000 0.00100 "" left "MS Shell Dlg 2"
>> 16 {0, 0, 0} {65280, 65280, 65280} nobackground noborder f0
>> ioText {498, 246} {52, 29} display 0.000000 0.00100 "f0" left "MS Shell Dlg
>> 2" 16 {0, 0, 0} {65280, 65280, 65280} nobackground border 197.6768
>> ioCheckbox {351, 242} {20, 20} off Vib
>> ioText {373, 240} {35, 25} display 0.000000 0.00100 "" left "MS Shell Dlg 2"
>> 16 {0, 0, 0} {65280, 65280, 65280} nobackground border Vibr
>> ioCheckbox {350, 267} {20, 20} on JitOn
>> ioCheckbox {351, 291} {20, 20} on ShimOn
>> ioText {374, 265} {35, 25} display 0.000000 0.00100 "" left "MS Shell Dlg 2"
>> 16 {0, 0, 0} {65280, 65280, 65280} nobackground border Jit
>> ioText {374, 288} {41, 25} display 0.000000 0.00100 "" left "MS Shell Dlg 2"
>> 16 {0, 0, 0} {65280, 65280, 65280} nobackground border Shim
>> ioCheckbox {351, 315} {20, 20} on OShoot
>> ioText {374, 313} {70, 25} display 0.000000 0.00100 "" left "MS Shell Dlg 2"
>> 16 {0, 0, 0} {65280, 65280, 65280} nobackground border Overshoot
>> ioSlider {5, 330} {120, 20} 0.000000 0.200000 0.041667 Noise
>> ioText {128, 322} {44, 32} display 0.000000 0.00100 "Noise" left "MS Shell
>> Dlg 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border 0.0450
>> ioText {174, 323} {171, 31} display 0.000000 0.00100 "" left "MS Shell Dlg
>> 2" 20 {0, 0, 0} {65280, 65280, 65280} nobackground border Aspiration noise
>> 
>>
>>
>>
>>     
>
>
>
>   


-- 
Andreas Bergsland,
universitetslektor / PhD-kandidat

Musikkteknologiseksjonen
Institutt for musikk
Olavskvartalet
NTNU
7491 Trondheim

Besøksadresse: Fjordgt.1 (3.etg.)
e-post: andreas.bergsland@hf.ntnu.no
Tlf: 7359 0096
Mob: 4566 3316

It does indeed look like a Csound issue. I'll see what I can find out.
I'll switch this conversation to the cs-dev list.

Victor
----- Original Message ----- 
From: "Andres Cabrera" 
To: 
Sent: Tuesday, April 28, 2009 2:50 AM
Subject: [Csnd] Re: dispfft in QuteCsound


Hi Victor,

On Mon, Apr 27, 2009 at 4:07 AM, victor  wrote:
> Hi Andres,
>
> I like your implementation of graphs and esp. the dispfft support. One 
> thing
> that would be useful would be to allow for multiple dispfft instances. At
> the
> moment, I can do that with two graphs widgets, provided they are from
> two separate instruments. Even then there is some cross-wiring in the
> refreshing of the graphs (I get some interference from one dispfft to
> another),
> but it more or less works.
> If I have 2 dispffts in the same instr I seem to only be able to see one.
> This
> might be a Csound graph issue, I don't know.
>

I haven't looked into it, but it seems to be a csound issue, since
QuteCsound doesn't even know which instrument created the graph, it
only obeys the callback (but bear in mind that many times I've thought
this it ended up being my mistake...)

Cheers,
Andrés


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

Hi,

On Tue, Apr 28, 2009 at 2:49 AM, Andreas Bergsland
 wrote:

> Ok, then I'm in. Well, actually what I would like to suggest was a graphical
> display of k-rate values, that is, much like the scope so that one can
> monitor how the values behave (or perhaps like multislider in Max/MSP). I
> have often missed that when tuning / calibrating instruments, especially
> with some kind of live control input. Maybe that could also include some
> kind of y-axis with value-reference points that could be customized.
>

Now I see what you mean. There's currently no way to do this directly
but you could hack it with several "Controller" widgets or writing the
k-rate values to a table and using a Graph widget.
It would be nice to add something like this, but it would need to
extend the MacCsound widget format. I don't want to do this, I prefer
to design a new format, probably based on or compatible with blue,
when I extend these posibilities.

Cheers,
Andrés

Hi Andres, I'm having no luck with that link, it just waits and waits
but no download appears..

2009/4/28 Andy Fillebrown :
>
> Hi Rory,
>
> There is a debug version of QuteCsound 0.4.1 (floats) for Windows up at
> https://sourceforge.net/project/showfiles.php?group_id=227265&package_id=289578&release_id=678952
>

Hi Rory,

Just tried it now and its working.

Cheers,
Andrés

On Wed, Apr 29, 2009 at 3:47 AM, Rory Walsh  wrote:
> Hi Andres, I'm having no luck with that link, it just waits and waits
> but no download appears..
>
> 2009/4/28 Andy Fillebrown :
>>
>> Hi Rory,
>>
>> There is a debug version of QuteCsound 0.4.1 (floats) for Windows up at
>> https://sourceforge.net/project/showfiles.php?group_id=227265&package_id=289578&release_id=678952
>>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>



-- 


Andrés