Updated Windows installers

[Michael Gogins-2]

I have updated the Windows installers at SourceForge. This is mainly to fix
the incorrect version of QuteCsound in the float installer.

I have also included the signal flow opcodes and updated the manual for
them.

I believe my QuteCsound crashes were caused by my environment, not by the
QuteCsound code or the Csound code. Depending on my environment, I could (or
could not) render soundfiles using the Csound API in a separate thread, and
then edit the soundfile with the external editor without crashing.

I profiled the runs using the Dependency Checker program and found quite a
different sequence of library loads in the non-crashing environment as
opposed to the crashing environment. This is probably due to differences in
the PATH variable in my different environments.

I'd appreciate any feedback on this issue, either about crashes in this way
of using QuteCsound, or non-crashes.

Regards,
Mike



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

[RoryWalsh]

Some of my students have experienced strange crashes in Vista that
they can't seem to replicate, with the newest version of QuteCsound. I
think it's to do with their systems. Others are getting crashes on XP
but again they can't seem to replicate them. For what it's worth I'm
using qutecsound on XP and I'm not having any problems.

Rory.


2009/11/1  <michael.gogins@...>:

> I have updated the Windows installers at SourceForge. This is mainly to fix
> the incorrect version of QuteCsound in the float installer.
>
> I have also included the signal flow opcodes and updated the manual for
> them.
>
> I believe my QuteCsound crashes were caused by my environment, not by the
> QuteCsound code or the Csound code. Depending on my environment, I could (or
> could not) render soundfiles using the Csound API in a separate thread, and
> then edit the soundfile with the external editor without crashing.
>
> I profiled the runs using the Dependency Checker program and found quite a
> different sequence of library loads in the non-crashing environment as
> opposed to the crashing environment. This is probably due to differences in
> the PATH variable in my different environments.
>
> I'd appreciate any feedback on this issue, either about crashes in this way
> of using QuteCsound, or non-crashes.
>
> Regards,
> Mike
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe
> csound"
>

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

[Victor Lazzarini]

Time to move on either to Linux or OSX, huh?

Victor
----- Original Message -----
From: "Rory Walsh" <rorywalsh@...>
To: <csound@...>
Sent: Sunday, November 01, 2009 9:52 PM
Subject: [Csnd] Re: Updated Windows installers

> Some of my students have experienced strange crashes in Vista that
> they can't seem to replicate, with the newest version of QuteCsound. I
> think it's to do with their systems. Others are getting crashes on XP
> but again they can't seem to replicate them. For what it's worth I'm
> using qutecsound on XP and I'm not having any problems.
>
> Rory.
>
>
> 2009/11/1  <michael.gogins@...>:
>> I have updated the Windows installers at SourceForge. This is mainly to
>> fix
>> the incorrect version of QuteCsound in the float installer.
>>
>> I have also included the signal flow opcodes and updated the manual for
>> them.
>>
>> I believe my QuteCsound crashes were caused by my environment, not by the
>> QuteCsound code or the Csound code. Depending on my environment, I could
>> (or
>> could not) render soundfiles using the Csound API in a separate thread,
>> and
>> then edit the soundfile with the external editor without crashing.
>>
>> I profiled the runs using the Dependency Checker program and found quite
>> a
>> different sequence of library loads in the non-crashing environment as
>> opposed to the crashing environment. This is probably due to differences
>> in
>> the PATH variable in my different environments.
>>
>> I'd appreciate any feedback on this issue, either about crashes in this
>> way
>> of using QuteCsound, or non-crashes.
>>
>> Regards,
>> Mike
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@... with body "unsubscribe
>> csound"
>>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe
> csound"

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

[RoryWalsh]

Some of them are using linux already but others are stuck in their ways!

2009/11/1 victor <Victor.Lazzarini@...>:

> Time to move on either to Linux or OSX, huh?
>
> Victor
> ----- Original Message ----- From: "Rory Walsh" <rorywalsh@...>
> To: <csound@...>
> Sent: Sunday, November 01, 2009 9:52 PM
> Subject: [Csnd] Re: Updated Windows installers
>
>
>> Some of my students have experienced strange crashes in Vista that
>> they can't seem to replicate, with the newest version of QuteCsound. I
>> think it's to do with their systems. Others are getting crashes on XP
>> but again they can't seem to replicate them. For what it's worth I'm
>> using qutecsound on XP and I'm not having any problems.
>>
>> Rory.
>>
>>
>> 2009/11/1  <michael.gogins@...>:
>>>
>>> I have updated the Windows installers at SourceForge. This is mainly to
>>> fix
>>> the incorrect version of QuteCsound in the float installer.
>>>
>>> I have also included the signal flow opcodes and updated the manual for
>>> them.
>>>
>>> I believe my QuteCsound crashes were caused by my environment, not by the
>>> QuteCsound code or the Csound code. Depending on my environment, I could
>>> (or
>>> could not) render soundfiles using the Csound API in a separate thread,
>>> and
>>> then edit the soundfile with the external editor without crashing.
>>>
>>> I profiled the runs using the Dependency Checker program and found quite
>>> a
>>> different sequence of library loads in the non-crashing environment as
>>> opposed to the crashing environment. This is probably due to differences
>>> in
>>> the PATH variable in my different environments.
>>>
>>> I'd appreciate any feedback on this issue, either about crashes in this
>>> way
>>> of using QuteCsound, or non-crashes.
>>>
>>> Regards,
>>> Mike
>>>
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@... with body "unsubscribe
>>> csound"
>>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@... with body "unsubscribe
>> csound"
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe
> csound"
>

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

[Mike Moser-Booth]

I just installed the floats version and everything seems to be working
fine now. Thanks, Mike!

.mmb

michael.gogins@... wrote:

> I have updated the Windows installers at SourceForge. This is mainly
> to fix the incorrect version of QuteCsound in the float installer.
>
> I have also included the signal flow opcodes and updated the manual
> for them.
>
> I believe my QuteCsound crashes were caused by my environment, not by
> the QuteCsound code or the Csound code. Depending on my environment, I
> could (or could not) render soundfiles using the Csound API in a
> separate thread, and then edit the soundfile with the external editor
> without crashing.
>
> I profiled the runs using the Dependency Checker program and found
> quite a different sequence of library loads in the non-crashing
> environment as opposed to the crashing environment. This is probably
> due to differences in the PATH variable in my different environments.
>
> I'd appreciate any feedback on this issue, either about crashes in
> this way of using QuteCsound, or non-crashes.
>
> Regards,
> Mike
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body
> "unsubscribe csound"

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

[francibal]

Hi Mr. Gogins,
i am on win vista and i have csound 5.11.1 vst (last version of yesterday, if i am correct, but i don't find Your last message about it! Do I had a vision?), and i would report some problems that i had with qute.

More important thing is:
when i use run in terminal seems that csound don't know any opcodes nor csd format.
Sometimes, after that, qute exit automatically.

Minor things:
Play button don't work, anything happens.

I would try Moro_arpeggiate_at_will.csd, in D. Boulanger/algocomp folder.
This work well in scite and in winxsound, but qute report wrong ftable.


Like always could be my system, not well set, and i will try to understand why those things happens.

Hope helpful,
thanks for Your work,

ciao,
fran.

michael.gogins wrote:

I have updated the Windows installers at SourceForge. This is mainly to fix
the incorrect version of QuteCsound in the float installer.

I have also included the signal flow opcodes and updated the manual for
them.

I believe my QuteCsound crashes were caused by my environment, not by the
QuteCsound code or the Csound code. Depending on my environment, I could (or
could not) render soundfiles using the Csound API in a separate thread, and
then edit the soundfile with the external editor without crashing.

I profiled the runs using the Dependency Checker program and found quite a
different sequence of library loads in the non-crashing environment as
opposed to the crashing environment. This is probably due to differences in
the PATH variable in my different environments.

I'd appreciate any feedback on this issue, either about crashes in this way
of using QuteCsound, or non-crashes.

Regards,
Mike



Send bugs reports to this list.
To unsubscribe, send email [e-mail] with body "unsubscribe csound"

[Michael Gogins-2]

I will try to reproduce your problems this evening.

Thanks,
Mike

On 11/3/09, francibal <ilterzouomo@...> wrote:

>
> Hi Mr. Gogins,
> i am on win vista and i have csound 5.11.1 vst (last version of yesterday,
> if i am correct, but i don't find Your last message about it! Do I had a
> vision?), and i would report some problems that i had with qute.
>
> More important thing is:
> when i use run in terminal seems that csound don't know any opcodes nor csd
> format.
> Sometimes, after that, qute exit automatically.
>
> Minor things:
> Play button don't work, anything happens.
>
> I would try Moro_arpeggiate_at_will.csd, in D. Boulanger/algocomp folder.
> This work well in scite and in winxsound, but qute report wrong ftable.
>
>
> Like always could be my system, not well set, and i will try to understand
> why those things happens.
>
> Hope helpful,
> thanks for Your work,
>
> ciao,
> fran.
>
>
>
> michael.gogins wrote:
>>
>> I have updated the Windows installers at SourceForge. This is mainly to
>> fix
>> the incorrect version of QuteCsound in the float installer.
>>
>> I have also included the signal flow opcodes and updated the manual for
>> them.
>>
>> I believe my QuteCsound crashes were caused by my environment, not by the
>> QuteCsound code or the Csound code. Depending on my environment, I could
>> (or
>> could not) render soundfiles using the Csound API in a separate thread,
>> and
>> then edit the soundfile with the external editor without crashing.
>>
>> I profiled the runs using the Dependency Checker program and found quite a
>>
>> different sequence of library loads in the non-crashing environment as
>> opposed to the crashing environment. This is probably due to differences
>> in
>> the PATH variable in my different environments.
>>
>> I'd appreciate any feedback on this issue, either about crashes in this
>> way
>> of using QuteCsound, or non-crashes.
>>
>> Regards,
>> Mike
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@... with body "unsubscribe
>> csound"
>>
>>
>
> --
> View this message in context:
> http://old.nabble.com/Updated-Windows-installers-tp26155213p26160107.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe
> csound"
>

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


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

[Andres Cabrera]

Hi,

On Tue, Nov 3, 2009 at 1:10 PM, francibal <ilterzouomo@...> wrote:
> Minor things:
> Play button don't work, anything happens.
>

That's not so minor... =) Can you try any of the examples to see if
the play button works?

Cheers,
Andrés

> I would try Moro_arpeggiate_at_will.csd, in D. Boulanger/algocomp folder.
> This work well in scite and in winxsound, but qute report wrong ftable.
>
>
> Like always could be my system, not well set, and i will try to understand
> why those things happens.
>
> Hope helpful,
> thanks for Your work,
>
> ciao,
> fran.
>
>
>
> michael.gogins wrote:
>>
>> I have updated the Windows installers at SourceForge. This is mainly to
>> fix
>> the incorrect version of QuteCsound in the float installer.
>>
>> I have also included the signal flow opcodes and updated the manual for
>> them.
>>
>> I believe my QuteCsound crashes were caused by my environment, not by the
>> QuteCsound code or the Csound code. Depending on my environment, I could
>> (or
>> could not) render soundfiles using the Csound API in a separate thread,
>> and
>> then edit the soundfile with the external editor without crashing.
>>
>> I profiled the runs using the Dependency Checker program and found quite a
>> different sequence of library loads in the non-crashing environment as
>> opposed to the crashing environment. This is probably due to differences
>> in
>> the PATH variable in my different environments.
>>
>> I'd appreciate any feedback on this issue, either about crashes in this
>> way
>> of using QuteCsound, or non-crashes.
>>
>> Regards,
>> Mike
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@... with body "unsubscribe
>> csound"
>>
>>
>
> --
> View this message in context: http://old.nabble.com/Updated-Windows-installers-tp26155213p26160107.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>

--


Andrés


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

[francibal]

Hi Mr. Andres,
i was not so clear, but it is ONLY external player that don't work. And this
is minor thing!
Sorry for that.

Thanks,
ciao,

fran.

----- Original Message -----
From: "Andres Cabrera" <mantaraya36@...>
To: <csound@...>
Sent: Tuesday, November 03, 2009 3:10 PM
Subject: [Csnd] Re: Re: Updated Windows installers - double-vst


Hi,

On Tue, Nov 3, 2009 at 1:10 PM, francibal <ilterzouomo@...> wrote:
> Minor things:
> Play button don't work, anything happens.
>

That's not so minor... =) Can you try any of the examples to see if
the play button works?

Cheers,
Andrés

> I would try Moro_arpeggiate_at_will.csd, in D. Boulanger/algocomp folder.
> This work well in scite and in winxsound, but qute report wrong ftable.
>
>
> Like always could be my system, not well set, and i will try to understand
> why those things happens.
>
> Hope helpful,
> thanks for Your work,
>
> ciao,
> fran.
>
>
>
> michael.gogins wrote:
>>
>> I have updated the Windows installers at SourceForge. This is mainly to
>> fix
>> the incorrect version of QuteCsound in the float installer.
>>
>> I have also included the signal flow opcodes and updated the manual for
>> them.
>>
>> I believe my QuteCsound crashes were caused by my environment, not by the
>> QuteCsound code or the Csound code. Depending on my environment, I could
>> (or
>> could not) render soundfiles using the Csound API in a separate thread,
>> and
>> then edit the soundfile with the external editor without crashing.
>>
>> I profiled the runs using the Dependency Checker program and found quite
>> a
>> different sequence of library loads in the non-crashing environment as
>> opposed to the crashing environment. This is probably due to differences
>> in
>> the PATH variable in my different environments.
>>
>> I'd appreciate any feedback on this issue, either about crashes in this
>> way
>> of using QuteCsound, or non-crashes.
>>
>> Regards,
>> Mike
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@... with body "unsubscribe
>> csound"
>>
>>
>
> --
> View this message in context:
> http://old.nabble.com/Updated-Windows-installers-tp26155213p26160107.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe
> csound"
>

--


Andrés


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



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

[Andres Cabrera]

Oh OK good =) This has already been reported and has been fixed in the
sources (will be fixed in the next release)

Cheers,
Andés

On Tue, Nov 3, 2009 at 2:41 PM, ilterzouomo <ilterzouomo@...> wrote:

> Hi Mr. Andres,
> i was not so clear, but it is ONLY external player that don't work. And this
> is minor thing!
> Sorry for that.
>
> Thanks,
> ciao,
>
> fran.
>
> ----- Original Message ----- From: "Andres Cabrera" <mantaraya36@...>
> To: <csound@...>
> Sent: Tuesday, November 03, 2009 3:10 PM
> Subject: [Csnd] Re: Re: Updated Windows installers - double-vst
>
>
> Hi,
>
> On Tue, Nov 3, 2009 at 1:10 PM, francibal <ilterzouomo@...> wrote:
>>
>> Minor things:
>> Play button don't work, anything happens.
>>
>
> That's not so minor... =) Can you try any of the examples to see if
> the play button works?
>
> Cheers,
> Andrés
>
>> I would try Moro_arpeggiate_at_will.csd, in D. Boulanger/algocomp folder.
>> This work well in scite and in winxsound, but qute report wrong ftable.
>>
>>
>> Like always could be my system, not well set, and i will try to understand
>> why those things happens.
>>
>> Hope helpful,
>> thanks for Your work,
>>
>> ciao,
>> fran.
>>
>>
>>
>> michael.gogins wrote:
>>>
>>> I have updated the Windows installers at SourceForge. This is mainly to
>>> fix
>>> the incorrect version of QuteCsound in the float installer.
>>>
>>> I have also included the signal flow opcodes and updated the manual for
>>> them.
>>>
>>> I believe my QuteCsound crashes were caused by my environment, not by the
>>> QuteCsound code or the Csound code. Depending on my environment, I could
>>> (or
>>> could not) render soundfiles using the Csound API in a separate thread,
>>> and
>>> then edit the soundfile with the external editor without crashing.
>>>
>>> I profiled the runs using the Dependency Checker program and found quite
>>> a
>>> different sequence of library loads in the non-crashing environment as
>>> opposed to the crashing environment. This is probably due to differences
>>> in
>>> the PATH variable in my different environments.
>>>
>>> I'd appreciate any feedback on this issue, either about crashes in this
>>> way
>>> of using QuteCsound, or non-crashes.
>>>
>>> Regards,
>>> Mike
>>>
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@... with body "unsubscribe
>>> csound"
>>>
>>>
>>
>> --
>> View this message in context:
>> http://old.nabble.com/Updated-Windows-installers-tp26155213p26160107.html
>> Sent from the Csound - General mailing list archive at Nabble.com.
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@... with body "unsubscribe
>> csound"
>>
>
>
>
> --
>
>
> Andrés
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe
> csound"=
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe
> csound"
>

--


Andrés


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

[RoryWalsh]

Writing of soundfiles from out goes into the qutecsound directory and
not the current directory, same thing happens with -o soundfile.wav in
the csoptions. Hitting render and selecting a file name and directory
also places the resulting file in the QuteCsound directory. Just
thought I'd mention it..

2009/11/3 Andres Cabrera <mantaraya36@...>:

> Oh OK good =) This has already been reported and has been fixed in the
> sources (will be fixed in the next release)
>
> Cheers,
> Andés
>
> On Tue, Nov 3, 2009 at 2:41 PM, ilterzouomo <ilterzouomo@...> wrote:
>> Hi Mr. Andres,
>> i was not so clear, but it is ONLY external player that don't work. And this
>> is minor thing!
>> Sorry for that.
>>
>> Thanks,
>> ciao,
>>
>> fran.
>>
>> ----- Original Message ----- From: "Andres Cabrera" <mantaraya36@...>
>> To: <csound@...>
>> Sent: Tuesday, November 03, 2009 3:10 PM
>> Subject: [Csnd] Re: Re: Updated Windows installers - double-vst
>>
>>
>> Hi,
>>
>> On Tue, Nov 3, 2009 at 1:10 PM, francibal <ilterzouomo@...> wrote:
>>>
>>> Minor things:
>>> Play button don't work, anything happens.
>>>
>>
>> That's not so minor... =) Can you try any of the examples to see if
>> the play button works?
>>
>> Cheers,
>> Andrés
>>
>>> I would try Moro_arpeggiate_at_will.csd, in D. Boulanger/algocomp folder.
>>> This work well in scite and in winxsound, but qute report wrong ftable.
>>>
>>>
>>> Like always could be my system, not well set, and i will try to understand
>>> why those things happens.
>>>
>>> Hope helpful,
>>> thanks for Your work,
>>>
>>> ciao,
>>> fran.
>>>
>>>
>>>
>>> michael.gogins wrote:
>>>>
>>>> I have updated the Windows installers at SourceForge. This is mainly to
>>>> fix
>>>> the incorrect version of QuteCsound in the float installer.
>>>>
>>>> I have also included the signal flow opcodes and updated the manual for
>>>> them.
>>>>
>>>> I believe my QuteCsound crashes were caused by my environment, not by the
>>>> QuteCsound code or the Csound code. Depending on my environment, I could
>>>> (or
>>>> could not) render soundfiles using the Csound API in a separate thread,
>>>> and
>>>> then edit the soundfile with the external editor without crashing.
>>>>
>>>> I profiled the runs using the Dependency Checker program and found quite
>>>> a
>>>> different sequence of library loads in the non-crashing environment as
>>>> opposed to the crashing environment. This is probably due to differences
>>>> in
>>>> the PATH variable in my different environments.
>>>>
>>>> I'd appreciate any feedback on this issue, either about crashes in this
>>>> way
>>>> of using QuteCsound, or non-crashes.
>>>>
>>>> Regards,
>>>> Mike
>>>>
>>>>
>>>>
>>>> Send bugs reports to this list.
>>>> To unsubscribe, send email sympa@... with body "unsubscribe
>>>> csound"
>>>>
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://old.nabble.com/Updated-Windows-installers-tp26155213p26160107.html
>>> Sent from the Csound - General mailing list archive at Nabble.com.
>>>
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@... with body "unsubscribe
>>> csound"
>>>
>>
>>
>>
>> --
>>
>>
>> Andrés
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@... with body "unsubscribe
>> csound"=
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@... with body "unsubscribe
>> csound"
>>
>
>
>
> --
>
>
> Andrés
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe csound"

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

[Andres Cabrera]

Thanks for reminding me of this. This is now fixed in svn. Relative
path names in the csd now work relative to the csd path as well.

Cheers,
Andrés

On Tue, Nov 3, 2009 at 6:30 PM, Rory Walsh <rorywalsh@...> wrote:

> Writing of soundfiles from out goes into the qutecsound directory and
> not the current directory, same thing happens with -o soundfile.wav in
> the csoptions. Hitting render and selecting a file name and directory
> also places the resulting file in the QuteCsound directory. Just
> thought I'd mention it..
>
> 2009/11/3 Andres Cabrera <mantaraya36@...>:
>> Oh OK good =) This has already been reported and has been fixed in the
>> sources (will be fixed in the next release)
>>
>> Cheers,
>> Andés
>>
>> On Tue, Nov 3, 2009 at 2:41 PM, ilterzouomo <ilterzouomo@...> wrote:
>>> Hi Mr. Andres,
>>> i was not so clear, but it is ONLY external player that don't work. And this
>>> is minor thing!
>>> Sorry for that.
>>>
>>> Thanks,
>>> ciao,
>>>
>>> fran.
>>>
>>> ----- Original Message ----- From: "Andres Cabrera" <mantaraya36@...>
>>> To: <csound@...>
>>> Sent: Tuesday, November 03, 2009 3:10 PM
>>> Subject: [Csnd] Re: Re: Updated Windows installers - double-vst
>>>
>>>
>>> Hi,
>>>
>>> On Tue, Nov 3, 2009 at 1:10 PM, francibal <ilterzouomo@...> wrote:
>>>>
>>>> Minor things:
>>>> Play button don't work, anything happens.
>>>>
>>>
>>> That's not so minor... =) Can you try any of the examples to see if
>>> the play button works?
>>>
>>> Cheers,
>>> Andrés
>>>
>>>> I would try Moro_arpeggiate_at_will.csd, in D. Boulanger/algocomp folder.
>>>> This work well in scite and in winxsound, but qute report wrong ftable.
>>>>
>>>>
>>>> Like always could be my system, not well set, and i will try to understand
>>>> why those things happens.
>>>>
>>>> Hope helpful,
>>>> thanks for Your work,
>>>>
>>>> ciao,
>>>> fran.
>>>>
>>>>
>>>>
>>>> michael.gogins wrote:
>>>>>
>>>>> I have updated the Windows installers at SourceForge. This is mainly to
>>>>> fix
>>>>> the incorrect version of QuteCsound in the float installer.
>>>>>
>>>>> I have also included the signal flow opcodes and updated the manual for
>>>>> them.
>>>>>
>>>>> I believe my QuteCsound crashes were caused by my environment, not by the
>>>>> QuteCsound code or the Csound code. Depending on my environment, I could
>>>>> (or
>>>>> could not) render soundfiles using the Csound API in a separate thread,
>>>>> and
>>>>> then edit the soundfile with the external editor without crashing.
>>>>>
>>>>> I profiled the runs using the Dependency Checker program and found quite
>>>>> a
>>>>> different sequence of library loads in the non-crashing environment as
>>>>> opposed to the crashing environment. This is probably due to differences
>>>>> in
>>>>> the PATH variable in my different environments.
>>>>>
>>>>> I'd appreciate any feedback on this issue, either about crashes in this
>>>>> way
>>>>> of using QuteCsound, or non-crashes.
>>>>>
>>>>> Regards,
>>>>> Mike
>>>>>
>>>>>
>>>>>
>>>>> Send bugs reports to this list.
>>>>> To unsubscribe, send email sympa@... with body "unsubscribe
>>>>> csound"
>>>>>
>>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://old.nabble.com/Updated-Windows-installers-tp26155213p26160107.html
>>>> Sent from the Csound - General mailing list archive at Nabble.com.
>>>>
>>>>
>>>>
>>>> Send bugs reports to this list.
>>>> To unsubscribe, send email sympa@... with body "unsubscribe
>>>> csound"
>>>>
>>>
>>>
>>>
>>> --
>>>
>>>
>>> Andrés
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@... with body "unsubscribe
>>> csound"=
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@... with body "unsubscribe
>>> csound"
>>>
>>
>>
>>
>> --
>>
>>
>> Andrés
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe csound"

--


Andrés


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

[RoryWalsh]

That's great Andres, thanks for this.

2009/11/5 Andres Cabrera <mantaraya36@...>:

> Thanks for reminding me of this. This is now fixed in svn. Relative
> path names in the csd now work relative to the csd path as well.
>
> Cheers,
> Andrés
>
> On Tue, Nov 3, 2009 at 6:30 PM, Rory Walsh <rorywalsh@...> wrote:
>> Writing of soundfiles from out goes into the qutecsound directory and
>> not the current directory, same thing happens with -o soundfile.wav in
>> the csoptions. Hitting render and selecting a file name and directory
>> also places the resulting file in the QuteCsound directory. Just
>> thought I'd mention it..
>>
>> 2009/11/3 Andres Cabrera <mantaraya36@...>:
>>> Oh OK good =) This has already been reported and has been fixed in the
>>> sources (will be fixed in the next release)
>>>
>>> Cheers,
>>> Andés
>>>
>>> On Tue, Nov 3, 2009 at 2:41 PM, ilterzouomo <ilterzouomo@...> wrote:
>>>> Hi Mr. Andres,
>>>> i was not so clear, but it is ONLY external player that don't work. And this
>>>> is minor thing!
>>>> Sorry for that.
>>>>
>>>> Thanks,
>>>> ciao,
>>>>
>>>> fran.
>>>>
>>>> ----- Original Message ----- From: "Andres Cabrera" <mantaraya36@...>
>>>> To: <csound@...>
>>>> Sent: Tuesday, November 03, 2009 3:10 PM
>>>> Subject: [Csnd] Re: Re: Updated Windows installers - double-vst
>>>>
>>>>
>>>> Hi,
>>>>
>>>> On Tue, Nov 3, 2009 at 1:10 PM, francibal <ilterzouomo@...> wrote:
>>>>>
>>>>> Minor things:
>>>>> Play button don't work, anything happens.
>>>>>
>>>>
>>>> That's not so minor... =) Can you try any of the examples to see if
>>>> the play button works?
>>>>
>>>> Cheers,
>>>> Andrés
>>>>
>>>>> I would try Moro_arpeggiate_at_will.csd, in D. Boulanger/algocomp folder.
>>>>> This work well in scite and in winxsound, but qute report wrong ftable.
>>>>>
>>>>>
>>>>> Like always could be my system, not well set, and i will try to understand
>>>>> why those things happens.
>>>>>
>>>>> Hope helpful,
>>>>> thanks for Your work,
>>>>>
>>>>> ciao,
>>>>> fran.
>>>>>
>>>>>
>>>>>
>>>>> michael.gogins wrote:
>>>>>>
>>>>>> I have updated the Windows installers at SourceForge. This is mainly to
>>>>>> fix
>>>>>> the incorrect version of QuteCsound in the float installer.
>>>>>>
>>>>>> I have also included the signal flow opcodes and updated the manual for
>>>>>> them.
>>>>>>
>>>>>> I believe my QuteCsound crashes were caused by my environment, not by the
>>>>>> QuteCsound code or the Csound code. Depending on my environment, I could
>>>>>> (or
>>>>>> could not) render soundfiles using the Csound API in a separate thread,
>>>>>> and
>>>>>> then edit the soundfile with the external editor without crashing.
>>>>>>
>>>>>> I profiled the runs using the Dependency Checker program and found quite
>>>>>> a
>>>>>> different sequence of library loads in the non-crashing environment as
>>>>>> opposed to the crashing environment. This is probably due to differences
>>>>>> in
>>>>>> the PATH variable in my different environments.
>>>>>>
>>>>>> I'd appreciate any feedback on this issue, either about crashes in this
>>>>>> way
>>>>>> of using QuteCsound, or non-crashes.
>>>>>>
>>>>>> Regards,
>>>>>> Mike
>>>>>>
>>>>>>
>>>>>>
>>>>>> Send bugs reports to this list.
>>>>>> To unsubscribe, send email sympa@... with body "unsubscribe
>>>>>> csound"
>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> View this message in context:
>>>>> http://old.nabble.com/Updated-Windows-installers-tp26155213p26160107.html
>>>>> Sent from the Csound - General mailing list archive at Nabble.com.
>>>>>
>>>>>
>>>>>
>>>>> Send bugs reports to this list.
>>>>> To unsubscribe, send email sympa@... with body "unsubscribe
>>>>> csound"
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>>
>>>> Andrés
>>>>
>>>>
>>>> Send bugs reports to this list.
>>>> To unsubscribe, send email sympa@... with body "unsubscribe
>>>> csound"=
>>>>
>>>>
>>>> Send bugs reports to this list.
>>>> To unsubscribe, send email sympa@... with body "unsubscribe
>>>> csound"
>>>>
>>>
>>>
>>>
>>> --
>>>
>>>
>>> Andrés
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>
>
>
> --
>
>
> Andrés
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe csound"

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

[RoryWalsh]

One other thing, did you get my request about having an option to
disable the most recent file list? I'm not sure if my mails to
qutecsound users requests are getting through? If not let me know and
I'll explain the reason for my requesting it..

2009/11/5 Rory Walsh <rorywalsh@...>:

> That's great Andres, thanks for this.
>
> 2009/11/5 Andres Cabrera <mantaraya36@...>:
>> Thanks for reminding me of this. This is now fixed in svn. Relative
>> path names in the csd now work relative to the csd path as well.
>>
>> Cheers,
>> Andrés
>>
>> On Tue, Nov 3, 2009 at 6:30 PM, Rory Walsh <rorywalsh@...> wrote:
>>> Writing of soundfiles from out goes into the qutecsound directory and
>>> not the current directory, same thing happens with -o soundfile.wav in
>>> the csoptions. Hitting render and selecting a file name and directory
>>> also places the resulting file in the QuteCsound directory. Just
>>> thought I'd mention it..
>>>
>>> 2009/11/3 Andres Cabrera <mantaraya36@...>:
>>>> Oh OK good =) This has already been reported and has been fixed in the
>>>> sources (will be fixed in the next release)
>>>>
>>>> Cheers,
>>>> Andés
>>>>
>>>> On Tue, Nov 3, 2009 at 2:41 PM, ilterzouomo <ilterzouomo@...> wrote:
>>>>> Hi Mr. Andres,
>>>>> i was not so clear, but it is ONLY external player that don't work. And this
>>>>> is minor thing!
>>>>> Sorry for that.
>>>>>
>>>>> Thanks,
>>>>> ciao,
>>>>>
>>>>> fran.
>>>>>
>>>>> ----- Original Message ----- From: "Andres Cabrera" <mantaraya36@...>
>>>>> To: <csound@...>
>>>>> Sent: Tuesday, November 03, 2009 3:10 PM
>>>>> Subject: [Csnd] Re: Re: Updated Windows installers - double-vst
>>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>> On Tue, Nov 3, 2009 at 1:10 PM, francibal <ilterzouomo@...> wrote:
>>>>>>
>>>>>> Minor things:
>>>>>> Play button don't work, anything happens.
>>>>>>
>>>>>
>>>>> That's not so minor... =) Can you try any of the examples to see if
>>>>> the play button works?
>>>>>
>>>>> Cheers,
>>>>> Andrés
>>>>>
>>>>>> I would try Moro_arpeggiate_at_will.csd, in D. Boulanger/algocomp folder.
>>>>>> This work well in scite and in winxsound, but qute report wrong ftable.
>>>>>>
>>>>>>
>>>>>> Like always could be my system, not well set, and i will try to understand
>>>>>> why those things happens.
>>>>>>
>>>>>> Hope helpful,
>>>>>> thanks for Your work,
>>>>>>
>>>>>> ciao,
>>>>>> fran.
>>>>>>
>>>>>>
>>>>>>
>>>>>> michael.gogins wrote:
>>>>>>>
>>>>>>> I have updated the Windows installers at SourceForge. This is mainly to
>>>>>>> fix
>>>>>>> the incorrect version of QuteCsound in the float installer.
>>>>>>>
>>>>>>> I have also included the signal flow opcodes and updated the manual for
>>>>>>> them.
>>>>>>>
>>>>>>> I believe my QuteCsound crashes were caused by my environment, not by the
>>>>>>> QuteCsound code or the Csound code. Depending on my environment, I could
>>>>>>> (or
>>>>>>> could not) render soundfiles using the Csound API in a separate thread,
>>>>>>> and
>>>>>>> then edit the soundfile with the external editor without crashing.
>>>>>>>
>>>>>>> I profiled the runs using the Dependency Checker program and found quite
>>>>>>> a
>>>>>>> different sequence of library loads in the non-crashing environment as
>>>>>>> opposed to the crashing environment. This is probably due to differences
>>>>>>> in
>>>>>>> the PATH variable in my different environments.
>>>>>>>
>>>>>>> I'd appreciate any feedback on this issue, either about crashes in this
>>>>>>> way
>>>>>>> of using QuteCsound, or non-crashes.
>>>>>>>
>>>>>>> Regards,
>>>>>>> Mike
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Send bugs reports to this list.
>>>>>>> To unsubscribe, send email sympa@... with body "unsubscribe
>>>>>>> csound"
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> View this message in context:
>>>>>> http://old.nabble.com/Updated-Windows-installers-tp26155213p26160107.html
>>>>>> Sent from the Csound - General mailing list archive at Nabble.com.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Send bugs reports to this list.
>>>>>> To unsubscribe, send email sympa@... with body "unsubscribe
>>>>>> csound"
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>>
>>>>> Andrés
>>>>>
>>>>>
>>>>> Send bugs reports to this list.
>>>>> To unsubscribe, send email sympa@... with body "unsubscribe
>>>>> csound"=
>>>>>
>>>>>
>>>>> Send bugs reports to this list.
>>>>> To unsubscribe, send email sympa@... with body "unsubscribe
>>>>> csound"
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>>
>>>> Andrés
>>>>
>>>>
>>>> Send bugs reports to this list.
>>>> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>>
>>
>>
>> --
>>
>>
>> Andrés
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>

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

[Andres Cabrera]

Hi,

No, thery're not getting through...
Can you explain why you would need this?

Cheers,
Andrés

El vie, 06-11-2009 a las 10:54 +0000, Rory Walsh escribió:

> One other thing, did you get my request about having an option to
> disable the most recent file list? I'm not sure if my mails to
> qutecsound users requests are getting through? If not let me know and
> I'll explain the reason for my requesting it..
>
> 2009/11/5 Rory Walsh <rorywalsh@...>:
> > That's great Andres, thanks for this.
> >
> > 2009/11/5 Andres Cabrera <mantaraya36@...>:
> >> Thanks for reminding me of this. This is now fixed in svn. Relative
> >> path names in the csd now work relative to the csd path as well.
> >>
> >> Cheers,
> >> Andrés
> >>
> >> On Tue, Nov 3, 2009 at 6:30 PM, Rory Walsh <rorywalsh@...> wrote:
> >>> Writing of soundfiles from out goes into the qutecsound directory and
> >>> not the current directory, same thing happens with -o soundfile.wav in
> >>> the csoptions. Hitting render and selecting a file name and directory
> >>> also places the resulting file in the QuteCsound directory. Just
> >>> thought I'd mention it..
> >>>
> >>> 2009/11/3 Andres Cabrera <mantaraya36@...>:
> >>>> Oh OK good =) This has already been reported and has been fixed in the
> >>>> sources (will be fixed in the next release)
> >>>>
> >>>> Cheers,
> >>>> Andés
> >>>>
> >>>> On Tue, Nov 3, 2009 at 2:41 PM, ilterzouomo <ilterzouomo@...> wrote:
> >>>>> Hi Mr. Andres,
> >>>>> i was not so clear, but it is ONLY external player that don't work. And this
> >>>>> is minor thing!
> >>>>> Sorry for that.
> >>>>>
> >>>>> Thanks,
> >>>>> ciao,
> >>>>>
> >>>>> fran.
> >>>>>
> >>>>> ----- Original Message ----- From: "Andres Cabrera" <mantaraya36@...>
> >>>>> To: <csound@...>
> >>>>> Sent: Tuesday, November 03, 2009 3:10 PM
> >>>>> Subject: [Csnd] Re: Re: Updated Windows installers - double-vst
> >>>>>
> >>>>>
> >>>>> Hi,
> >>>>>
> >>>>> On Tue, Nov 3, 2009 at 1:10 PM, francibal <ilterzouomo@...> wrote:
> >>>>>>
> >>>>>> Minor things:
> >>>>>> Play button don't work, anything happens.
> >>>>>>
> >>>>>
> >>>>> That's not so minor... =) Can you try any of the examples to see if
> >>>>> the play button works?
> >>>>>
> >>>>> Cheers,
> >>>>> Andrés
> >>>>>
> >>>>>> I would try Moro_arpeggiate_at_will.csd, in D. Boulanger/algocomp folder.
> >>>>>> This work well in scite and in winxsound, but qute report wrong ftable.
> >>>>>>
> >>>>>>
> >>>>>> Like always could be my system, not well set, and i will try to understand
> >>>>>> why those things happens.
> >>>>>>
> >>>>>> Hope helpful,
> >>>>>> thanks for Your work,
> >>>>>>
> >>>>>> ciao,
> >>>>>> fran.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> michael.gogins wrote:
> >>>>>>>
> >>>>>>> I have updated the Windows installers at SourceForge. This is mainly to
> >>>>>>> fix
> >>>>>>> the incorrect version of QuteCsound in the float installer.
> >>>>>>>
> >>>>>>> I have also included the signal flow opcodes and updated the manual for
> >>>>>>> them.
> >>>>>>>
> >>>>>>> I believe my QuteCsound crashes were caused by my environment, not by the
> >>>>>>> QuteCsound code or the Csound code. Depending on my environment, I could
> >>>>>>> (or
> >>>>>>> could not) render soundfiles using the Csound API in a separate thread,
> >>>>>>> and
> >>>>>>> then edit the soundfile with the external editor without crashing.
> >>>>>>>
> >>>>>>> I profiled the runs using the Dependency Checker program and found quite
> >>>>>>> a
> >>>>>>> different sequence of library loads in the non-crashing environment as
> >>>>>>> opposed to the crashing environment. This is probably due to differences
> >>>>>>> in
> >>>>>>> the PATH variable in my different environments.
> >>>>>>>
> >>>>>>> I'd appreciate any feedback on this issue, either about crashes in this
> >>>>>>> way
> >>>>>>> of using QuteCsound, or non-crashes.
> >>>>>>>
> >>>>>>> Regards,
> >>>>>>> Mike
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> Send bugs reports to this list.
> >>>>>>> To unsubscribe, send email sympa@... with body "unsubscribe
> >>>>>>> csound"
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> View this message in context:
> >>>>>> http://old.nabble.com/Updated-Windows-installers-tp26155213p26160107.html
> >>>>>> Sent from the Csound - General mailing list archive at Nabble.com.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> Send bugs reports to this list.
> >>>>>> To unsubscribe, send email sympa@... with body "unsubscribe
> >>>>>> csound"
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>>
> >>>>>
> >>>>> Andrés
> >>>>>
> >>>>>
> >>>>> Send bugs reports to this list.
> >>>>> To unsubscribe, send email sympa@... with body "unsubscribe
> >>>>> csound"=
> >>>>>
> >>>>>
> >>>>> Send bugs reports to this list.
> >>>>> To unsubscribe, send email sympa@... with body "unsubscribe
> >>>>> csound"
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>>
> >>>>
> >>>> Andrés
> >>>>
> >>>>
> >>>> Send bugs reports to this list.
> >>>> To unsubscribe, send email sympa@... with body "unsubscribe csound"
> >>>
> >>>
> >>> Send bugs reports to this list.
> >>> To unsubscribe, send email sympa@... with body "unsubscribe csound"
> >>
> >>
> >>
> >> --
> >>
> >>
> >> Andrés
> >>
> >>
> >> Send bugs reports to this list.
> >> To unsubscribe, send email sympa@... with body "unsubscribe csound"
> >
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe csound"

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

[RoryWalsh]

Here's my original post:

Would it be possible to add an option so that QTCsound doesn't open
the most recent files but a template file by default? It's stupid I
know but a lot of my students end up inadvertently saving over their
colleagues work! I'm getting a lot of 'here's something I prepared
before' from the students after they magically find one of their
colleagues attempt at an exercise and pawn it off as their own!

Rory.




2009/11/6 Andrés Cabrera <mantaraya36@...>:

> Hi,
>
> No, thery're not getting through...
> Can you explain why you would need this?
>
> Cheers,
> Andrés
>
> El vie, 06-11-2009 a las 10:54 +0000, Rory Walsh escribió:
>> One other thing, did you get my request about having an option to
>> disable the most recent file list? I'm not sure if my mails to
>> qutecsound users requests are getting through? If not let me know and
>> I'll explain the reason for my requesting it..
>>
>> 2009/11/5 Rory Walsh <rorywalsh@...>:
>> > That's great Andres, thanks for this.
>> >
>> > 2009/11/5 Andres Cabrera <mantaraya36@...>:
>> >> Thanks for reminding me of this. This is now fixed in svn. Relative
>> >> path names in the csd now work relative to the csd path as well.
>> >>
>> >> Cheers,
>> >> Andrés
>> >>
>> >> On Tue, Nov 3, 2009 at 6:30 PM, Rory Walsh <rorywalsh@...> wrote:
>> >>> Writing of soundfiles from out goes into the qutecsound directory and
>> >>> not the current directory, same thing happens with -o soundfile.wav in
>> >>> the csoptions. Hitting render and selecting a file name and directory
>> >>> also places the resulting file in the QuteCsound directory. Just
>> >>> thought I'd mention it..
>> >>>
>> >>> 2009/11/3 Andres Cabrera <mantaraya36@...>:
>> >>>> Oh OK good =) This has already been reported and has been fixed in the
>> >>>> sources (will be fixed in the next release)
>> >>>>
>> >>>> Cheers,
>> >>>> Andés
>> >>>>
>> >>>> On Tue, Nov 3, 2009 at 2:41 PM, ilterzouomo <ilterzouomo@...> wrote:
>> >>>>> Hi Mr. Andres,
>> >>>>> i was not so clear, but it is ONLY external player that don't work. And this
>> >>>>> is minor thing!
>> >>>>> Sorry for that.
>> >>>>>
>> >>>>> Thanks,
>> >>>>> ciao,
>> >>>>>
>> >>>>> fran.
>> >>>>>
>> >>>>> ----- Original Message ----- From: "Andres Cabrera" <mantaraya36@...>
>> >>>>> To: <csound@...>
>> >>>>> Sent: Tuesday, November 03, 2009 3:10 PM
>> >>>>> Subject: [Csnd] Re: Re: Updated Windows installers - double-vst
>> >>>>>
>> >>>>>
>> >>>>> Hi,
>> >>>>>
>> >>>>> On Tue, Nov 3, 2009 at 1:10 PM, francibal <ilterzouomo@...> wrote:
>> >>>>>>
>> >>>>>> Minor things:
>> >>>>>> Play button don't work, anything happens.
>> >>>>>>
>> >>>>>
>> >>>>> That's not so minor... =) Can you try any of the examples to see if
>> >>>>> the play button works?
>> >>>>>
>> >>>>> Cheers,
>> >>>>> Andrés
>> >>>>>
>> >>>>>> I would try Moro_arpeggiate_at_will.csd, in D. Boulanger/algocomp folder.
>> >>>>>> This work well in scite and in winxsound, but qute report wrong ftable.
>> >>>>>>
>> >>>>>>
>> >>>>>> Like always could be my system, not well set, and i will try to understand
>> >>>>>> why those things happens.
>> >>>>>>
>> >>>>>> Hope helpful,
>> >>>>>> thanks for Your work,
>> >>>>>>
>> >>>>>> ciao,
>> >>>>>> fran.
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> michael.gogins wrote:
>> >>>>>>>
>> >>>>>>> I have updated the Windows installers at SourceForge. This is mainly to
>> >>>>>>> fix
>> >>>>>>> the incorrect version of QuteCsound in the float installer.
>> >>>>>>>
>> >>>>>>> I have also included the signal flow opcodes and updated the manual for
>> >>>>>>> them.
>> >>>>>>>
>> >>>>>>> I believe my QuteCsound crashes were caused by my environment, not by the
>> >>>>>>> QuteCsound code or the Csound code. Depending on my environment, I could
>> >>>>>>> (or
>> >>>>>>> could not) render soundfiles using the Csound API in a separate thread,
>> >>>>>>> and
>> >>>>>>> then edit the soundfile with the external editor without crashing.
>> >>>>>>>
>> >>>>>>> I profiled the runs using the Dependency Checker program and found quite
>> >>>>>>> a
>> >>>>>>> different sequence of library loads in the non-crashing environment as
>> >>>>>>> opposed to the crashing environment. This is probably due to differences
>> >>>>>>> in
>> >>>>>>> the PATH variable in my different environments.
>> >>>>>>>
>> >>>>>>> I'd appreciate any feedback on this issue, either about crashes in this
>> >>>>>>> way
>> >>>>>>> of using QuteCsound, or non-crashes.
>> >>>>>>>
>> >>>>>>> Regards,
>> >>>>>>> Mike
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> Send bugs reports to this list.
>> >>>>>>> To unsubscribe, send email sympa@... with body "unsubscribe
>> >>>>>>> csound"
>> >>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>> --
>> >>>>>> View this message in context:
>> >>>>>> http://old.nabble.com/Updated-Windows-installers-tp26155213p26160107.html
>> >>>>>> Sent from the Csound - General mailing list archive at Nabble.com.
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> Send bugs reports to this list.
>> >>>>>> To unsubscribe, send email sympa@... with body "unsubscribe
>> >>>>>> csound"
>> >>>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> --
>> >>>>>
>> >>>>>
>> >>>>> Andrés
>> >>>>>
>> >>>>>
>> >>>>> Send bugs reports to this list.
>> >>>>> To unsubscribe, send email sympa@... with body "unsubscribe
>> >>>>> csound"=
>> >>>>>
>> >>>>>
>> >>>>> Send bugs reports to this list.
>> >>>>> To unsubscribe, send email sympa@... with body "unsubscribe
>> >>>>> csound"
>> >>>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>>
>> >>>>
>> >>>> Andrés
>> >>>>
>> >>>>
>> >>>> Send bugs reports to this list.
>> >>>> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>> >>>
>> >>>
>> >>> Send bugs reports to this list.
>> >>> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>> >>
>> >>
>> >>
>> >> --
>> >>
>> >>
>> >> Andrés
>> >>
>> >>
>> >> Send bugs reports to this list.
>> >> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>> >
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>

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

[Andres Cabrera]

Hi,

That's already there. In the configuration, uncheck "Remember open
files from previous session".

Cheers,
Andrés

On Fri, Nov 6, 2009 at 6:39 PM, Rory Walsh <rorywalsh@...> wrote:

> Here's my original post:
>
> Would it be possible to add an option so that QTCsound doesn't open
> the most recent files but a template file by default? It's stupid I
> know but a lot of my students end up inadvertently saving over their
> colleagues work! I'm getting a lot of 'here's something I prepared
> before' from the students after they magically find one of their
> colleagues attempt at an exercise and pawn it off as their own!
>
> Rory.
>
>
>
>
> 2009/11/6 Andrés Cabrera <mantaraya36@...>:
>> Hi,
>>
>> No, thery're not getting through...
>> Can you explain why you would need this?
>>
>> Cheers,
>> Andrés
>>
>> El vie, 06-11-2009 a las 10:54 +0000, Rory Walsh escribió:
>>> One other thing, did you get my request about having an option to
>>> disable the most recent file list? I'm not sure if my mails to
>>> qutecsound users requests are getting through? If not let me know and
>>> I'll explain the reason for my requesting it..
>>>
>>> 2009/11/5 Rory Walsh <rorywalsh@...>:
>>> > That's great Andres, thanks for this.
>>> >
>>> > 2009/11/5 Andres Cabrera <mantaraya36@...>:
>>> >> Thanks for reminding me of this. This is now fixed in svn. Relative
>>> >> path names in the csd now work relative to the csd path as well.
>>> >>
>>> >> Cheers,
>>> >> Andrés
>>> >>
>>> >> On Tue, Nov 3, 2009 at 6:30 PM, Rory Walsh <rorywalsh@...> wrote:
>>> >>> Writing of soundfiles from out goes into the qutecsound directory and
>>> >>> not the current directory, same thing happens with -o soundfile.wav in
>>> >>> the csoptions. Hitting render and selecting a file name and directory
>>> >>> also places the resulting file in the QuteCsound directory. Just
>>> >>> thought I'd mention it..
>>> >>>
>>> >>> 2009/11/3 Andres Cabrera <mantaraya36@...>:
>>> >>>> Oh OK good =) This has already been reported and has been fixed in the
>>> >>>> sources (will be fixed in the next release)
>>> >>>>
>>> >>>> Cheers,
>>> >>>> Andés
>>> >>>>
>>> >>>> On Tue, Nov 3, 2009 at 2:41 PM, ilterzouomo <ilterzouomo@...> wrote:
>>> >>>>> Hi Mr. Andres,
>>> >>>>> i was not so clear, but it is ONLY external player that don't work. And this
>>> >>>>> is minor thing!
>>> >>>>> Sorry for that.
>>> >>>>>
>>> >>>>> Thanks,
>>> >>>>> ciao,
>>> >>>>>
>>> >>>>> fran.
>>> >>>>>
>>> >>>>> ----- Original Message ----- From: "Andres Cabrera" <mantaraya36@...>
>>> >>>>> To: <csound@...>
>>> >>>>> Sent: Tuesday, November 03, 2009 3:10 PM
>>> >>>>> Subject: [Csnd] Re: Re: Updated Windows installers - double-vst
>>> >>>>>
>>> >>>>>
>>> >>>>> Hi,
>>> >>>>>
>>> >>>>> On Tue, Nov 3, 2009 at 1:10 PM, francibal <ilterzouomo@...> wrote:
>>> >>>>>>
>>> >>>>>> Minor things:
>>> >>>>>> Play button don't work, anything happens.
>>> >>>>>>
>>> >>>>>
>>> >>>>> That's not so minor... =) Can you try any of the examples to see if
>>> >>>>> the play button works?
>>> >>>>>
>>> >>>>> Cheers,
>>> >>>>> Andrés
>>> >>>>>
>>> >>>>>> I would try Moro_arpeggiate_at_will.csd, in D. Boulanger/algocomp folder.
>>> >>>>>> This work well in scite and in winxsound, but qute report wrong ftable.
>>> >>>>>>
>>> >>>>>>
>>> >>>>>> Like always could be my system, not well set, and i will try to understand
>>> >>>>>> why those things happens.
>>> >>>>>>
>>> >>>>>> Hope helpful,
>>> >>>>>> thanks for Your work,
>>> >>>>>>
>>> >>>>>> ciao,
>>> >>>>>> fran.
>>> >>>>>>
>>> >>>>>>
>>> >>>>>>
>>> >>>>>> michael.gogins wrote:
>>> >>>>>>>
>>> >>>>>>> I have updated the Windows installers at SourceForge. This is mainly to
>>> >>>>>>> fix
>>> >>>>>>> the incorrect version of QuteCsound in the float installer.
>>> >>>>>>>
>>> >>>>>>> I have also included the signal flow opcodes and updated the manual for
>>> >>>>>>> them.
>>> >>>>>>>
>>> >>>>>>> I believe my QuteCsound crashes were caused by my environment, not by the
>>> >>>>>>> QuteCsound code or the Csound code. Depending on my environment, I could
>>> >>>>>>> (or
>>> >>>>>>> could not) render soundfiles using the Csound API in a separate thread,
>>> >>>>>>> and
>>> >>>>>>> then edit the soundfile with the external editor without crashing.
>>> >>>>>>>
>>> >>>>>>> I profiled the runs using the Dependency Checker program and found quite
>>> >>>>>>> a
>>> >>>>>>> different sequence of library loads in the non-crashing environment as
>>> >>>>>>> opposed to the crashing environment. This is probably due to differences
>>> >>>>>>> in
>>> >>>>>>> the PATH variable in my different environments.
>>> >>>>>>>
>>> >>>>>>> I'd appreciate any feedback on this issue, either about crashes in this
>>> >>>>>>> way
>>> >>>>>>> of using QuteCsound, or non-crashes.
>>> >>>>>>>
>>> >>>>>>> Regards,
>>> >>>>>>> Mike
>>> >>>>>>>
>>> >>>>>>>
>>> >>>>>>>
>>> >>>>>>> Send bugs reports to this list.
>>> >>>>>>> To unsubscribe, send email sympa@... with body "unsubscribe
>>> >>>>>>> csound"
>>> >>>>>>>
>>> >>>>>>>
>>> >>>>>>
>>> >>>>>> --
>>> >>>>>> View this message in context:
>>> >>>>>> http://old.nabble.com/Updated-Windows-installers-tp26155213p26160107.html
>>> >>>>>> Sent from the Csound - General mailing list archive at Nabble.com.
>>> >>>>>>
>>> >>>>>>
>>> >>>>>>
>>> >>>>>> Send bugs reports to this list.
>>> >>>>>> To unsubscribe, send email sympa@... with body "unsubscribe
>>> >>>>>> csound"
>>> >>>>>>
>>> >>>>>
>>> >>>>>
>>> >>>>>
>>> >>>>> --
>>> >>>>>
>>> >>>>>
>>> >>>>> Andrés
>>> >>>>>
>>> >>>>>
>>> >>>>> Send bugs reports to this list.
>>> >>>>> To unsubscribe, send email sympa@... with body "unsubscribe
>>> >>>>> csound"=
>>> >>>>>
>>> >>>>>
>>> >>>>> Send bugs reports to this list.
>>> >>>>> To unsubscribe, send email sympa@... with body "unsubscribe
>>> >>>>> csound"
>>> >>>>>
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>> --
>>> >>>>
>>> >>>>
>>> >>>> Andrés
>>> >>>>
>>> >>>>
>>> >>>> Send bugs reports to this list.
>>> >>>> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>>> >>>
>>> >>>
>>> >>> Send bugs reports to this list.
>>> >>> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >>
>>> >>
>>> >> Andrés
>>> >>
>>> >>
>>> >> Send bugs reports to this list.
>>> >> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>>> >
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>>
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe csound"

--


Andrés


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

[RoryWalsh]

thanks Andres! I'm a numpty!

2009/11/6 Andres Cabrera <mantaraya36@...>:

> Hi,
>
> That's already there. In the configuration, uncheck "Remember open
> files from previous session".
>
> Cheers,
> Andrés
>
> On Fri, Nov 6, 2009 at 6:39 PM, Rory Walsh <rorywalsh@...> wrote:
>> Here's my original post:
>>
>> Would it be possible to add an option so that QTCsound doesn't open
>> the most recent files but a template file by default? It's stupid I
>> know but a lot of my students end up inadvertently saving over their
>> colleagues work! I'm getting a lot of 'here's something I prepared
>> before' from the students after they magically find one of their
>> colleagues attempt at an exercise and pawn it off as their own!
>>
>> Rory.
>>
>>
>>
>>
>> 2009/11/6 Andrés Cabrera <mantaraya36@...>:
>>> Hi,
>>>
>>> No, thery're not getting through...
>>> Can you explain why you would need this?
>>>
>>> Cheers,
>>> Andrés
>>>
>>> El vie, 06-11-2009 a las 10:54 +0000, Rory Walsh escribió:
>>>> One other thing, did you get my request about having an option to
>>>> disable the most recent file list? I'm not sure if my mails to
>>>> qutecsound users requests are getting through? If not let me know and
>>>> I'll explain the reason for my requesting it..
>>>>
>>>> 2009/11/5 Rory Walsh <rorywalsh@...>:
>>>> > That's great Andres, thanks for this.
>>>> >
>>>> > 2009/11/5 Andres Cabrera <mantaraya36@...>:
>>>> >> Thanks for reminding me of this. This is now fixed in svn. Relative
>>>> >> path names in the csd now work relative to the csd path as well.
>>>> >>
>>>> >> Cheers,
>>>> >> Andrés
>>>> >>
>>>> >> On Tue, Nov 3, 2009 at 6:30 PM, Rory Walsh <rorywalsh@...> wrote:
>>>> >>> Writing of soundfiles from out goes into the qutecsound directory and
>>>> >>> not the current directory, same thing happens with -o soundfile.wav in
>>>> >>> the csoptions. Hitting render and selecting a file name and directory
>>>> >>> also places the resulting file in the QuteCsound directory. Just
>>>> >>> thought I'd mention it..
>>>> >>>
>>>> >>> 2009/11/3 Andres Cabrera <mantaraya36@...>:
>>>> >>>> Oh OK good =) This has already been reported and has been fixed in the
>>>> >>>> sources (will be fixed in the next release)
>>>> >>>>
>>>> >>>> Cheers,
>>>> >>>> Andés
>>>> >>>>
>>>> >>>> On Tue, Nov 3, 2009 at 2:41 PM, ilterzouomo <ilterzouomo@...> wrote:
>>>> >>>>> Hi Mr. Andres,
>>>> >>>>> i was not so clear, but it is ONLY external player that don't work. And this
>>>> >>>>> is minor thing!
>>>> >>>>> Sorry for that.
>>>> >>>>>
>>>> >>>>> Thanks,
>>>> >>>>> ciao,
>>>> >>>>>
>>>> >>>>> fran.
>>>> >>>>>
>>>> >>>>> ----- Original Message ----- From: "Andres Cabrera" <mantaraya36@...>
>>>> >>>>> To: <csound@...>
>>>> >>>>> Sent: Tuesday, November 03, 2009 3:10 PM
>>>> >>>>> Subject: [Csnd] Re: Re: Updated Windows installers - double-vst
>>>> >>>>>
>>>> >>>>>
>>>> >>>>> Hi,
>>>> >>>>>
>>>> >>>>> On Tue, Nov 3, 2009 at 1:10 PM, francibal <ilterzouomo@...> wrote:
>>>> >>>>>>
>>>> >>>>>> Minor things:
>>>> >>>>>> Play button don't work, anything happens.
>>>> >>>>>>
>>>> >>>>>
>>>> >>>>> That's not so minor... =) Can you try any of the examples to see if
>>>> >>>>> the play button works?
>>>> >>>>>
>>>> >>>>> Cheers,
>>>> >>>>> Andrés
>>>> >>>>>
>>>> >>>>>> I would try Moro_arpeggiate_at_will.csd, in D. Boulanger/algocomp folder.
>>>> >>>>>> This work well in scite and in winxsound, but qute report wrong ftable.
>>>> >>>>>>
>>>> >>>>>>
>>>> >>>>>> Like always could be my system, not well set, and i will try to understand
>>>> >>>>>> why those things happens.
>>>> >>>>>>
>>>> >>>>>> Hope helpful,
>>>> >>>>>> thanks for Your work,
>>>> >>>>>>
>>>> >>>>>> ciao,
>>>> >>>>>> fran.
>>>> >>>>>>
>>>> >>>>>>
>>>> >>>>>>
>>>> >>>>>> michael.gogins wrote:
>>>> >>>>>>>
>>>> >>>>>>> I have updated the Windows installers at SourceForge. This is mainly to
>>>> >>>>>>> fix
>>>> >>>>>>> the incorrect version of QuteCsound in the float installer.
>>>> >>>>>>>
>>>> >>>>>>> I have also included the signal flow opcodes and updated the manual for
>>>> >>>>>>> them.
>>>> >>>>>>>
>>>> >>>>>>> I believe my QuteCsound crashes were caused by my environment, not by the
>>>> >>>>>>> QuteCsound code or the Csound code. Depending on my environment, I could
>>>> >>>>>>> (or
>>>> >>>>>>> could not) render soundfiles using the Csound API in a separate thread,
>>>> >>>>>>> and
>>>> >>>>>>> then edit the soundfile with the external editor without crashing.
>>>> >>>>>>>
>>>> >>>>>>> I profiled the runs using the Dependency Checker program and found quite
>>>> >>>>>>> a
>>>> >>>>>>> different sequence of library loads in the non-crashing environment as
>>>> >>>>>>> opposed to the crashing environment. This is probably due to differences
>>>> >>>>>>> in
>>>> >>>>>>> the PATH variable in my different environments.
>>>> >>>>>>>
>>>> >>>>>>> I'd appreciate any feedback on this issue, either about crashes in this
>>>> >>>>>>> way
>>>> >>>>>>> of using QuteCsound, or non-crashes.
>>>> >>>>>>>
>>>> >>>>>>> Regards,
>>>> >>>>>>> Mike
>>>> >>>>>>>
>>>> >>>>>>>
>>>> >>>>>>>
>>>> >>>>>>> Send bugs reports to this list.
>>>> >>>>>>> To unsubscribe, send email sympa@... with body "unsubscribe
>>>> >>>>>>> csound"
>>>> >>>>>>>
>>>> >>>>>>>
>>>> >>>>>>
>>>> >>>>>> --
>>>> >>>>>> View this message in context:
>>>> >>>>>> http://old.nabble.com/Updated-Windows-installers-tp26155213p26160107.html
>>>> >>>>>> Sent from the Csound - General mailing list archive at Nabble.com.
>>>> >>>>>>
>>>> >>>>>>
>>>> >>>>>>
>>>> >>>>>> Send bugs reports to this list.
>>>> >>>>>> To unsubscribe, send email sympa@... with body "unsubscribe
>>>> >>>>>> csound"
>>>> >>>>>>
>>>> >>>>>
>>>> >>>>>
>>>> >>>>>
>>>> >>>>> --
>>>> >>>>>
>>>> >>>>>
>>>> >>>>> Andrés
>>>> >>>>>
>>>> >>>>>
>>>> >>>>> Send bugs reports to this list.
>>>> >>>>> To unsubscribe, send email sympa@... with body "unsubscribe
>>>> >>>>> csound"=
>>>> >>>>>
>>>> >>>>>
>>>> >>>>> Send bugs reports to this list.
>>>> >>>>> To unsubscribe, send email sympa@... with body "unsubscribe
>>>> >>>>> csound"
>>>> >>>>>
>>>> >>>>
>>>> >>>>
>>>> >>>>
>>>> >>>> --
>>>> >>>>
>>>> >>>>
>>>> >>>> Andrés
>>>> >>>>
>>>> >>>>
>>>> >>>> Send bugs reports to this list.
>>>> >>>> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>>>> >>>
>>>> >>>
>>>> >>> Send bugs reports to this list.
>>>> >>> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>>>> >>
>>>> >>
>>>> >>
>>>> >> --
>>>> >>
>>>> >>
>>>> >> Andrés
>>>> >>
>>>> >>
>>>> >> Send bugs reports to this list.
>>>> >> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>>>> >
>>>>
>>>>
>>>> Send bugs reports to this list.
>>>> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>>>
>>>
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>
>
>
> --
>
>
> Andrés
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe csound"

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