Thanks for your response.

If other Csound developers are in agreement, I will replace Csound5Gui in 
the installers with QuteCsound.

If you would make me a QuteCsound developer, I can look into running Python 
in QuteCsound. Either it will be easy, or it will be hard. If it is easy, I 
will do it. If it is hard, I will probably not do it, but I will let people 
know what I think could be done.

About recording, with QuteCsound, since you already are accessing the spout 
buffer, you obviously do have the option of ignoring Csound's I/O drivers 
and options and replacing them with QuteCsound options and drivers. But 
since you already provide recording, this is probably not necessary.

You probably could, however, add a QtOptions element to the CSD file format, 
and parse it to save and restore output filename and format, instead of 
keeping that in the Windows registry.

Regards,
Mike

----- Original Message ----- 
From: "Andres Cabrera" 
To: 
Sent: Thursday, January 29, 2009 7:44 PM
Subject: [Csnd] Re: Re: Re: [ann] QuteCsound 04.RC2 for Windows


Hi,

On Thu, Jan 29, 2009 at 7:22 PM,   wrote:
> I have installed several different versions of QuteCsound for Windows, but
> this is the first version that actually ran for me (doubles, Csound 5.10, 
> XP
> SP3), although it's still not totally reliable. I've had a chance to play
> around with it, try various views, run a few simple .csd files, and so on. 
> I
> like it!
>

Glad you like it! There are some issues with doubles, as I don't test
for that build. It would be great if you can provide some details of
the problems.

> In particular, I like:
>
> o Standard Windows look and feel, not as much distracting eye candy as
> Csound5Gui.
>
> o Ergonomic design - easy to show and hide windows.
>
> o I like the integrated help and especially the context-sensitive help.
>
> o I like that the widget code is embedded in its own element into the .csd
> file.
>
> o Using Qt makes sense, especially with the upcoming change in the Qt
> license to LGPLv2.
>
> Wishes:
>
> o I wish that the widget code was (optionally) editable as text in the csd
> edit panel, in addition to using the GUI designer.
>

This might actualy be too much trouble for the benefits...

> o I wish that QuteCsound would run Python code, and could treat a csd file
> embedded in a Python script the same way it currently treats a csd file --
>  I.e. edit the code, write edited GUI widgets back into the orchestra 
> code,
> etc.
>

I'm not sure I'll go that far either... You're welcome to dig in =)

> Questions:
>
> o Does QuteCsound manage its own I/O, so that it can write a soundfile at
> the same time as it plays real-time audio? If not, this is a wish.
>

It uses Csound's output modules, but it takes Csound's spout for the
Scope widget and for use with the Record button. I'm not sure how the
record button is working for the doubles build, though.

> Proposals:
>
> o Make QuteCsound the default Csound GUI in the Windows installers,
> replacing Csound5Gui.exe.
>
> o Move QuteCsound into the Csound license and into Csound CVS? (this 
> becomes
> possible under the new Qt license).
>

I'm not sure about this because it would add one more dependency to
the Csound tree. That's why I didn't push for that when I started
QuteCsound. I'd also like to keep QuteCsound GPLv3, and it uses svn,
which has some things that are better compared to cvs. I would like,
however that QuteCsound was included in the Csound installers, if
packagers want to take in this burden.

Cheers,
Andrés


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


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

Hi Michael,

On Thu, Jan 29, 2009 at 8:05 PM,   wrote:
> Thanks for your response.
>
> If other Csound developers are in agreement, I will replace Csound5Gui in
> the installers with QuteCsound.
>
> If you would make me a QuteCsound developer, I can look into running Python
> in QuteCsound. Either it will be easy, or it will be hard. If it is easy, I
> will do it. If it is hard, I will probably not do it, but I will let people
> know what I think could be done.
>

I've added you as a developer (are you OK with licencing contributions
by the GPLv3?). I would like the python features you add to be
transparent, and not complicate in any way the usage for newbies,
since QuteCsound is primarily aimed for beginners.

> About recording, with QuteCsound, since you already are accessing the spout
> buffer, you obviously do have the option of ignoring Csound's I/O drivers
> and options and replacing them with QuteCsound options and drivers. But
> since you already provide recording, this is probably not necessary.
>
> You probably could, however, add a QtOptions element to the CSD file format,
> and parse it to save and restore output filename and format, instead of
> keeping that in the Windows registry.
>

I think the MacCsound secion contains this, so I might use it. I've
tried to reuse existing stuff as much as possible...

Cheers,
Andrés

I'd suggest to add QuteCsound to the installers, not to replace  
Csound5GUI, as there are still some issues in QuteCsound, for example  
in the utilities. As reported, there is for example a problem in the  
PVOC analysis:
"util pvanal:
soundin cannot open ... " (though the file exists and there is no  
problem with Csound5GUI to analyse it)
So I think it's bit too early to remove Csound5GUI, because for some  
tasks it's the simpliest way to do (especially for students who are  
not familiar with the command line).

	joachim



Am 30.01.2009 um 02:05 schrieb michael.gogins@gmail.com:

> Thanks for your response.
>
> If other Csound developers are in agreement, I will replace  
> Csound5Gui in the installers with QuteCsound.
>
> If you would make me a QuteCsound developer, I can look into running  
> Python in QuteCsound. Either it will be easy, or it will be hard. If  
> it is easy, I will do it. If it is hard, I will probably not do it,  
> but I will let people know what I think could be done.
>
> About recording, with QuteCsound, since you already are accessing  
> the spout buffer, you obviously do have the option of ignoring  
> Csound's I/O drivers and options and replacing them with QuteCsound  
> options and drivers. But since you already provide recording, this  
> is probably not necessary.
>
> You probably could, however, add a QtOptions element to the CSD file  
> format, and parse it to save and restore output filename and format,  
> instead of keeping that in the Windows registry.
>
> Regards,
> Mike
>
> ----- Original Message ----- From: "Andres Cabrera"  >
> To: 
> Sent: Thursday, January 29, 2009 7:44 PM
> Subject: [Csnd] Re: Re: Re: [ann] QuteCsound 04.RC2 for Windows
>
>
> Hi,
>
> On Thu, Jan 29, 2009 at 7:22 PM,   wrote:
>> I have installed several different versions of QuteCsound for  
>> Windows, but
>> this is the first version that actually ran for me (doubles, Csound  
>> 5.10, XP
>> SP3), although it's still not totally reliable. I've had a chance  
>> to play
>> around with it, try various views, run a few simple .csd files, and  
>> so on. I
>> like it!
>>
>
> Glad you like it! There are some issues with doubles, as I don't test
> for that build. It would be great if you can provide some details of
> the problems.
>
>> In particular, I like:
>>
>> o Standard Windows look and feel, not as much distracting eye candy  
>> as
>> Csound5Gui.
>>
>> o Ergonomic design - easy to show and hide windows.
>>
>> o I like the integrated help and especially the context-sensitive  
>> help.
>>
>> o I like that the widget code is embedded in its own element into  
>> the .csd
>> file.
>>
>> o Using Qt makes sense, especially with the upcoming change in the Qt
>> license to LGPLv2.
>>
>> Wishes:
>>
>> o I wish that the widget code was (optionally) editable as text in  
>> the csd
>> edit panel, in addition to using the GUI designer.
>>
>
> This might actualy be too much trouble for the benefits...
>
>> o I wish that QuteCsound would run Python code, and could treat a  
>> csd file
>> embedded in a Python script the same way it currently treats a csd  
>> file --
>> I.e. edit the code, write edited GUI widgets back into the  
>> orchestra code,
>> etc.
>>
>
> I'm not sure I'll go that far either... You're welcome to dig in =)
>
>> Questions:
>>
>> o Does QuteCsound manage its own I/O, so that it can write a  
>> soundfile at
>> the same time as it plays real-time audio? If not, this is a wish.
>>
>
> It uses Csound's output modules, but it takes Csound's spout for the
> Scope widget and for use with the Record button. I'm not sure how the
> record button is working for the doubles build, though.
>
>> Proposals:
>>
>> o Make QuteCsound the default Csound GUI in the Windows installers,
>> replacing Csound5Gui.exe.
>>
>> o Move QuteCsound into the Csound license and into Csound CVS?  
>> (this becomes
>> possible under the new Qt license).
>>
>
> I'm not sure about this because it would add one more dependency to
> the Csound tree. That's why I didn't push for that when I started
> QuteCsound. I'd also like to keep QuteCsound GPLv3, and it uses svn,
> which has some things that are better compared to cvs. I would like,
> however that QuteCsound was included in the Csound installers, if
> packagers want to take in this burden.
>
> 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"