On windows hitting record creates a sound file but it doesn't play
properly. Sometimes it's silent and others time it's just noisey? Copy
and paste is still and issue with the latest binary version for
windows. Is it possible to add line numbers? Also, rendering to a
sound file without using QuteCsound options, i.e. -o rory.wav doesn't
place the rendered soundfile in the same folder as the .csd as Csound
normally does. I posted this info on the QuteCsound list but it's
seems quite slow. As QuteCsound is now being shipped with Csound I
guess it's just as relevant on this list. On the up side I'm now using
QuteCsound with all my undergrad and postgrad classes. It's great to
have a cross platform editor!

Rory.

I will also adopt QuteCsound in my courses alongside the classic  
command-line
version.

Victor
On 30 Sep 2009, at 14:57, Rory Walsh wrote:

> On windows hitting record creates a sound file but it doesn't play
> properly. Sometimes it's silent and others time it's just noisey? Copy
> and paste is still and issue with the latest binary version for
> windows. Is it possible to add line numbers? Also, rendering to a
> sound file without using QuteCsound options, i.e. -o rory.wav doesn't
> place the rendered soundfile in the same folder as the .csd as Csound
> normally does. I posted this info on the QuteCsound list but it's
> seems quite slow. As QuteCsound is now being shipped with Csound I
> guess it's just as relevant on this list. On the up side I'm now using
> QuteCsound with all my undergrad and postgrad classes. It's great to
> have a cross platform editor!
>
> Rory.
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"

On the Mac using CsOptions places the files in the same directory as  
the app bundle.
I suppose if SFDIR is set then it would place it there.

Victor


On 30 Sep 2009, at 14:57, Rory Walsh wrote:

> On windows hitting record creates a sound file but it doesn't play
> properly. Sometimes it's silent and others time it's just noisey? Copy
> and paste is still and issue with the latest binary version for
> windows. Is it possible to add line numbers? Also, rendering to a
> sound file without using QuteCsound options, i.e. -o rory.wav doesn't
> place the rendered soundfile in the same folder as the .csd as Csound
> normally does. I posted this info on the QuteCsound list but it's
> seems quite slow. As QuteCsound is now being shipped with Csound I
> guess it's just as relevant on this list. On the up side I'm now using
> QuteCsound with all my undergrad and postgrad classes. It's great to
> have a cross platform editor!
>
> Rory.
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"

Victor Lazzarini wrote:
> On the Mac using CsOptions places the files in the same directory as the 
> app bundle.


You don't really want it to write user files into the /Applications 
folder (permissions will probably get in the way anyway); a reasonable 
default would something like be $(HOME)/csound  (best selected at 
install stage).


Richard Dobson

I am not saying you want to do that, I am just reporting what happens  
by default. But
I see there are two solutions:

1. Set SFDIR in the options
2. Set 'ask for filename everytime' in the options

no... three

3. Set the filename in the options.

Victor



On 30 Sep 2009, at 15:15, Richard Dobson wrote:

> Victor Lazzarini wrote:
>> On the Mac using CsOptions places the files in the same directory  
>> as the app bundle.
>
>
> You don't really want it to write user files into the /Applications  
> folder (permissions will probably get in the way anyway); a  
> reasonable default would something like be $(HOME)/csound  (best  
> selected at install stage).
>
>
> Richard Dobson
>
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"

In fact setting SFDIR in the options does not seem to do anything. Could
you confirm that Andres?


On 30 Sep 2009, at 15:26, Victor Lazzarini wrote:

> I am not saying you want to do that, I am just reporting what  
> happens by default. But
> I see there are two solutions:
>
> 1. Set SFDIR in the options
> 2. Set 'ask for filename everytime' in the options
>
> no... three
>
> 3. Set the filename in the options.
>
> Victor
>
>
>
> On 30 Sep 2009, at 15:15, Richard Dobson wrote:
>
>> Victor Lazzarini wrote:
>>> On the Mac using CsOptions places the files in the same directory  
>>> as the app bundle.
>>
>>
>> You don't really want it to write user files into the /Applications  
>> folder (permissions will probably get in the way anyway); a  
>> reasonable default would something like be $(HOME)/csound  (best  
>> selected at install stage).
>>
>>
>> Richard Dobson
>>
>>
>>
>>
>> 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"

Would be nice if it defaulted to the same directory as the csd file as
it does when Csound is run from the command line without a SFDIR set.
Anyway, it's no biggy, I know where they go and if I put an explicit
path in there is no confusion.

Rory.


2009/9/30 Victor Lazzarini :
> In fact setting SFDIR in the options does not seem to do anything. Could
> you confirm that Andres?
>
>
> On 30 Sep 2009, at 15:26, Victor Lazzarini wrote:
>
>> I am not saying you want to do that, I am just reporting what happens by
>> default. But
>> I see there are two solutions:
>>
>> 1. Set SFDIR in the options
>> 2. Set 'ask for filename everytime' in the options
>>
>> no... three
>>
>> 3. Set the filename in the options.
>>
>> Victor
>>
>>
>>
>> On 30 Sep 2009, at 15:15, Richard Dobson wrote:
>>
>>> Victor Lazzarini wrote:
>>>>
>>>> On the Mac using CsOptions places the files in the same directory as the
>>>> app bundle.
>>>
>>>
>>> You don't really want it to write user files into the /Applications
>>> folder (permissions will probably get in the way anyway); a reasonable
>>> default would something like be $(HOME)/csound  (best selected at install
>>> stage).
>>>
>>>
>>> Richard Dobson
>>>
>>>
>>>
>>>
>>> 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"
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>

Another thing I forgot to mention is that default csd file does not
save so one has to set it each time.

2009/9/30 Rory Walsh :
> On windows hitting record creates a sound file but it doesn't play
> properly. Sometimes it's silent and others time it's just noisey? Copy
> and paste is still and issue with the latest binary version for
> windows. Is it possible to add line numbers? Also, rendering to a
> sound file without using QuteCsound options, i.e. -o rory.wav doesn't
> place the rendered soundfile in the same folder as the .csd as Csound
> normally does. I posted this info on the QuteCsound list but it's
> seems quite slow. As QuteCsound is now being shipped with Csound I
> guess it's just as relevant on this list. On the up side I'm now using
> QuteCsound with all my undergrad and postgrad classes. It's great to
> have a cross platform editor!
>
> Rory.
>