I've been using QuteCsound more and more as time goes on because I
find the use of widgets to fine-tune instrument definition parameters
more effective than running a piece, tweaking the parameters in a text
editor, and re-running the piece.

However, I have some problems and some issues that I'd appreciate help
with, if anyone has any...

First, I have a large "patch library" of instrument definitions. In
one form my patch library is a big orchestra file (CsoundAC.csd), in
another form it is a directory with one instrument definition per
include file; I create arrangements by #Including the files and I wire
them into my orchestra using the signal flow graph opcodes.

I'd like to be able to use QuteCsound with my patch library, but there
are obvious difficulties. There is not enough screen real estate to
show widgets for all of the dozens of instruments in my library. Is
there any way to hide widgets, to have more than one widget window, or
to put widgets into an include file?

Second, over the years I've automated a whole bunch of
post-processing. When I run a piece, the following things happen
automatically: the soundfile is tagged, rescaled, translated to CD
audio, and translated to mp3. So, whenever I run a piece and I like
the way it sounds, it is "done" and I can just upload an mp3 or burn a
CD. How can I bring this post-production stuff into QuteCsound? Or,
alternatively, how can I get QuteCsound to edit one of my Lua scripts
that contains an embedded csd file without omitting or messing up the
enclosing Lua script?

Any help is appreciated...
Regards,
Mike

Mike,

What do you use to convert WAV files to MP3?

On 11/4/11, Michael Gogins  wrote:
> I've been using QuteCsound more and more as time goes on because I
> find the use of widgets to fine-tune instrument definition parameters
> more effective than running a piece, tweaking the parameters in a text
> editor, and re-running the piece.
>
> However, I have some problems and some issues that I'd appreciate help
> with, if anyone has any...
>
> First, I have a large "patch library" of instrument definitions. In
> one form my patch library is a big orchestra file (CsoundAC.csd), in
> another form it is a directory with one instrument definition per
> include file; I create arrangements by #Including the files and I wire
> them into my orchestra using the signal flow graph opcodes.
>
> I'd like to be able to use QuteCsound with my patch library, but there
> are obvious difficulties. There is not enough screen real estate to
> show widgets for all of the dozens of instruments in my library. Is
> there any way to hide widgets, to have more than one widget window, or
> to put widgets into an include file?
>
> Second, over the years I've automated a whole bunch of
> post-processing. When I run a piece, the following things happen
> automatically: the soundfile is tagged, rescaled, translated to CD
> audio, and translated to mp3. So, whenever I run a piece and I like
> the way it sounds, it is "done" and I can just upload an mp3 or burn a
> CD. How can I bring this post-production stuff into QuteCsound? Or,
> alternatively, how can I get QuteCsound to edit one of my Lua scripts
> that contains an embedded csd file without omitting or messing up the
> enclosing Lua script?
>
> Any help is appreciated...
> Regards,
> Mike
>
> --
> 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"
>
>


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"

My pieces these days are Lua scripts that embed Csound orchestras. The
Lua script shells out to run lame, the mp3 encoder. The other
post-production stuff is done by shelling out to run sox.

Regards,
Mike

On Fri, Nov 4, 2011 at 3:59 PM, Adam Puckett  wrote:
> Mike,
>
> What do you use to convert WAV files to MP3?
>
> On 11/4/11, Michael Gogins  wrote:
>> I've been using QuteCsound more and more as time goes on because I
>> find the use of widgets to fine-tune instrument definition parameters
>> more effective than running a piece, tweaking the parameters in a text
>> editor, and re-running the piece.
>>
>> However, I have some problems and some issues that I'd appreciate help
>> with, if anyone has any...
>>
>> First, I have a large "patch library" of instrument definitions. In
>> one form my patch library is a big orchestra file (CsoundAC.csd), in
>> another form it is a directory with one instrument definition per
>> include file; I create arrangements by #Including the files and I wire
>> them into my orchestra using the signal flow graph opcodes.
>>
>> I'd like to be able to use QuteCsound with my patch library, but there
>> are obvious difficulties. There is not enough screen real estate to
>> show widgets for all of the dozens of instruments in my library. Is
>> there any way to hide widgets, to have more than one widget window, or
>> to put widgets into an include file?
>>
>> Second, over the years I've automated a whole bunch of
>> post-processing. When I run a piece, the following things happen
>> automatically: the soundfile is tagged, rescaled, translated to CD
>> audio, and translated to mp3. So, whenever I run a piece and I like
>> the way it sounds, it is "done" and I can just upload an mp3 or burn a
>> CD. How can I bring this post-production stuff into QuteCsound? Or,
>> alternatively, how can I get QuteCsound to edit one of my Lua scripts
>> that contains an embedded csd file without omitting or messing up the
>> enclosing Lua script?
>>
>> Any help is appreciated...
>> Regards,
>> Mike
>>
>> --
>> 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"
>>
>>
>
>
> 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,

On Fri, Nov 4, 2011 at 4:39 PM, Michael Gogins  wrote:
> I'd like to be able to use QuteCsound with my patch library, but there
> are obvious difficulties. There is not enough screen real estate to
> show widgets for all of the dozens of instruments in my library. Is
> there any way to hide widgets, to have more than one widget window, or
> to put widgets into an include file?

This is not currently possible like that, as widgets are stored in
their own section in the csd file, and they are read and parsed by
CsoundQt, not Csound, so there are currently no facilities for this.
However, you could use the PythonQt API to dynamically create the
widgets you need and store those files as individual python scripts.
I'm not sure how practical that is, but it could be done.

>
> Second, over the years I've automated a whole bunch of
> post-processing. When I run a piece, the following things happen
> automatically: the soundfile is tagged, rescaled, translated to CD
> audio, and translated to mp3. So, whenever I run a piece and I like
> the way it sounds, it is "done" and I can just upload an mp3 or burn a
> CD. How can I bring this post-production stuff into QuteCsound? Or,
> alternatively, how can I get QuteCsound to edit one of my Lua scripts
> that contains an embedded csd file without omitting or messing up the
> enclosing Lua script?
>

Files that are not csd, orc or sco should not be mangled in any way by
CsoundQt. If they are, it is a bug. I just made a simple test, and
opening and editing a lua file works fine. You can also do this in
python directly within CsoundQt. Unfortunately, lua files are not run
by CsoundQt. Maybe I should add that possibility...


Cheers,
Andrés


> Any help is appreciated...
> Regards,
> Mike
>
> --
> 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"

On a sort of design level, this is one of the things that has
prevented blue/CsoundQT interaction for widgets, as blue encapsulated
widgets together with instruments or effects, but does not have a
global UI, and CsoundQT is the reverse.  One thing I was planning to
do last week before getting sidetracked was building a global UI area
for blue.  A result of that would be that blue would be able to read
CsoundQT projects.

I think if CsoundQT starts to do this kind of encapsulation, it will
start to evolve into something like blue. :P

steven

On Mon, Nov 7, 2011 at 4:04 PM, Andres Cabrera  wrote:
> Hi,
>
> On Fri, Nov 4, 2011 at 4:39 PM, Michael Gogins  wrote:
>> I'd like to be able to use QuteCsound with my patch library, but there
>> are obvious difficulties. There is not enough screen real estate to
>> show widgets for all of the dozens of instruments in my library. Is
>> there any way to hide widgets, to have more than one widget window, or
>> to put widgets into an include file?
>
> This is not currently possible like that, as widgets are stored in
> their own section in the csd file, and they are read and parsed by
> CsoundQt, not Csound, so there are currently no facilities for this.
> However, you could use the PythonQt API to dynamically create the
> widgets you need and store those files as individual python scripts.
> I'm not sure how practical that is, but it could be done.
>
>>
>> Second, over the years I've automated a whole bunch of
>> post-processing. When I run a piece, the following things happen
>> automatically: the soundfile is tagged, rescaled, translated to CD
>> audio, and translated to mp3. So, whenever I run a piece and I like
>> the way it sounds, it is "done" and I can just upload an mp3 or burn a
>> CD. How can I bring this post-production stuff into QuteCsound? Or,
>> alternatively, how can I get QuteCsound to edit one of my Lua scripts
>> that contains an embedded csd file without omitting or messing up the
>> enclosing Lua script?
>>
>
> Files that are not csd, orc or sco should not be mangled in any way by
> CsoundQt. If they are, it is a bug. I just made a simple test, and
> opening and editing a lua file works fine. You can also do this in
> python directly within CsoundQt. Unfortunately, lua files are not run
> by CsoundQt. Maybe I should add that possibility...
>
>
> Cheers,
> Andrés
>
>
>> Any help is appreciated...
>> Regards,
>> Mike
>>
>> --
>> 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"
>
>


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 encapsulation is a great feature of Blue and i sure CsoundQt will take a good benefit to use this concept !!
stf

Le 13 nov. 2011 à 19:10, Steven Yi a écrit :

> On a sort of design level, this is one of the things that has
> prevented blue/CsoundQT interaction for widgets, as blue encapsulated
> widgets together with instruments or effects, but does not have a
> global UI, and CsoundQT is the reverse.  One thing I was planning to
> do last week before getting sidetracked was building a global UI area
> for blue.  A result of that would be that blue would be able to read
> CsoundQT projects.
> 
> I think if CsoundQT starts to do this kind of encapsulation, it will
> start to evolve into something like blue. :P
> 
> steven
> 
> On Mon, Nov 7, 2011 at 4:04 PM, Andres Cabrera  wrote:
>> Hi,
>> 
>> On Fri, Nov 4, 2011 at 4:39 PM, Michael Gogins  wrote:
>>> I'd like to be able to use QuteCsound with my patch library, but there
>>> are obvious difficulties. There is not enough screen real estate to
>>> show widgets for all of the dozens of instruments in my library. Is
>>> there any way to hide widgets, to have more than one widget window, or
>>> to put widgets into an include file?
>> 
>> This is not currently possible like that, as widgets are stored in
>> their own section in the csd file, and they are read and parsed by
>> CsoundQt, not Csound, so there are currently no facilities for this.
>> However, you could use the PythonQt API to dynamically create the
>> widgets you need and store those files as individual python scripts.
>> I'm not sure how practical that is, but it could be done.
>> 
>>> 
>>> Second, over the years I've automated a whole bunch of
>>> post-processing. When I run a piece, the following things happen
>>> automatically: the soundfile is tagged, rescaled, translated to CD
>>> audio, and translated to mp3. So, whenever I run a piece and I like
>>> the way it sounds, it is "done" and I can just upload an mp3 or burn a
>>> CD. How can I bring this post-production stuff into QuteCsound? Or,
>>> alternatively, how can I get QuteCsound to edit one of my Lua scripts
>>> that contains an embedded csd file without omitting or messing up the
>>> enclosing Lua script?
>>> 
>> 
>> Files that are not csd, orc or sco should not be mangled in any way by
>> CsoundQt. If they are, it is a bug. I just made a simple test, and
>> opening and editing a lua file works fine. You can also do this in
>> python directly within CsoundQt. Unfortunately, lua files are not run
>> by CsoundQt. Maybe I should add that possibility...
>> 
>> 
>> Cheers,
>> Andrés
>> 
>> 
>>> Any help is appreciated...
>>> Regards,
>>> Mike
>>> 
>>> --
>>> 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"
>> 
>> 
> 
> 
> 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"