Hi All,

After a long hiatus for releases, I am happy to announce blue 2.0.0 is
now available at:

http://www.csounds.com/stevenyi/blue

(Note: the above site is old and will be updated for 2.1.0.  The
download can also be retrieved from the sourceforge site at
http://sf.net/projects/bluemusic).

The big change is that blue 2.0.0 has been rewritten to use the
Nebeans Rich-Client Platform.  This has taken quite a bit of time but
I think the app has gained a lot of nice features in using the RCP
libraries, particularly a nicer window system that users can customize
the locations of windows of the app (i.e. move score side-by-side to
orchestra, detach orchestra into it's own window to pull to a separate
screen, etc.).  Also, there a number of nice UI things in RCP that I
have started to take advantage of.

This release is feature-equivalent to blue 0.125.0 and projects that
working 0.125.0 should work open up and work fine in blue 2.0.0.  I am
going to be ramping up my time on developing blue and moving forward
with now with new feature development. Initial aims are to improve the
PatternObject and to work on MIDI input for 2.1.0, as well as going
through and taking care of issues in the bug and feature request
databases on SourceForge.

Documentation was only partially updated for this release and most of
the documentation is still from 0.125.0.  In reviewing the
documentation I have decided that a larger reorganization of the
documentation is necessary and this work has been scheduled for 2.1.0.
 For any questions regarding 2.0.0, please either email the blue users
mailing list (preferred) or email me directly and I'll be happy to
answer questions.

A note on installation: for this release and for the foreseeable
future, the application is now simply bundled in a zip file.  Unzip
the file and go into the blue/bin folder and run either blue.exe or
the blue shell script to launch the application.

Thank you to all of the blue users on on the blue mailing list who
have provided feedback during the 2.0.0 beta releases: you have helped
tremendously in helping to find bugs and make this release possible!

Thanks an enjoy!
steven

p.s. - Thank you to Brian Wong for contributing new pieces for the
examples folder!  I know I have contacted a number of people for other
contributions and may have lost them in the time 2.0.0 was being
developed, my apologies!  If you have a piece you would like to
contribute, please email me and I would love to add them to blue for
all users to study and enjoy!

[CHANGE LOG]

>Notes for 2.0.0 <
[released 2010.01.07]

Steven Yi-----------------------------------------------------------------------

blue

    [new] - Converted application to use Netbeans Rich Client Platform to take
            advantage of new Window Manager and many libraries

    [new] - Added PulseAudio as driver option for Realtime Render settings on
            Linux

    [new] - Added pieces by Brian Wong to examples\pieces\brianWong folder

    [fix] - bug 2864419 - fixed importing multiline i- and f-statements when
            importing CSD or ORC/SCO; added multiline i-statment in score parser


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

Thanks Jason and everyone!

I'm hoping to also "reboot" blueShare by making a full website that
will be both the home of blue (blue's new website) as well as
blueShare as part of it.  Hopefully can make it more community
oriented, so things like seeing popularity of instruments/effects,
comments, etc.  I'm working on a design document now for MIDI and
probably will try be a little more formal with how releases and things
get put together.  Part of the future of blueShare I think will go
hand-in-hand with moving libraries from categories-based to tags-based
(or perhaps keeping categories and adding tags).

There's a lot on my mind now but it's going to take some time to get
it all going.  Hopefully we all benefit from it!

Thanks!
steven

On Fri, Jan 8, 2010 at 1:46 PM, Jason a  wrote:
> AWESOME!  just downloaded, gave it a good run-through and i'm impressed!  i
> installed it and whammo, it worked... no fiddling, no noodling with
> preferences, nothing!  it seems a lot more stable in it's normal, everyday
> functions too (button pushing, screen switching, etc).  i can't wait to
> start composing with it.  great job.  big up to you Steven, and all of your
> cohorts/minions/associates/assistants, great work.
>
> jAdams
>
> On Thu, Jan 7, 2010 at 10:36 PM, Steven Yi  wrote:
>>
>> Hi All,
>>
>> After a long hiatus for releases, I am happy to announce blue 2.0.0 is
>> now available at:
>>
>> http://www.csounds.com/stevenyi/blue
>>
>> (Note: the above site is old and will be updated for 2.1.0.  The
>> download can also be retrieved from the sourceforge site at
>> http://sf.net/projects/bluemusic).
>>
>> The big change is that blue 2.0.0 has been rewritten to use the
>> Nebeans Rich-Client Platform.  This has taken quite a bit of time but
>> I think the app has gained a lot of nice features in using the RCP
>> libraries, particularly a nicer window system that users can customize
>> the locations of windows of the app (i.e. move score side-by-side to
>> orchestra, detach orchestra into it's own window to pull to a separate
>> screen, etc.).  Also, there a number of nice UI things in RCP that I
>> have started to take advantage of.
>>
>> This release is feature-equivalent to blue 0.125.0 and projects that
>> working 0.125.0 should work open up and work fine in blue 2.0.0.  I am
>> going to be ramping up my time on developing blue and moving forward
>> with now with new feature development. Initial aims are to improve the
>> PatternObject and to work on MIDI input for 2.1.0, as well as going
>> through and taking care of issues in the bug and feature request
>> databases on SourceForge.
>>
>> Documentation was only partially updated for this release and most of
>> the documentation is still from 0.125.0.  In reviewing the
>> documentation I have decided that a larger reorganization of the
>> documentation is necessary and this work has been scheduled for 2.1.0.
>>  For any questions regarding 2.0.0, please either email the blue users
>> mailing list (preferred) or email me directly and I'll be happy to
>> answer questions.
>>
>> A note on installation: for this release and for the foreseeable
>> future, the application is now simply bundled in a zip file.  Unzip
>> the file and go into the blue/bin folder and run either blue.exe or
>> the blue shell script to launch the application.
>>
>> Thank you to all of the blue users on on the blue mailing list who
>> have provided feedback during the 2.0.0 beta releases: you have helped
>> tremendously in helping to find bugs and make this release possible!
>>
>> Thanks an enjoy!
>> steven
>>
>> p.s. - Thank you to Brian Wong for contributing new pieces for the
>> examples folder!  I know I have contacted a number of people for other
>> contributions and may have lost them in the time 2.0.0 was being
>> developed, my apologies!  If you have a piece you would like to
>> contribute, please email me and I would love to add them to blue for
>> all users to study and enjoy!
>>
>> [CHANGE LOG]
>>
>> >Notes for 2.0.0 <
>> [released 2010.01.07]
>>
>> Steven
>> Yi-----------------------------------------------------------------------
>>
>> blue
>>
>>    [new] - Converted application to use Netbeans Rich Client Platform to
>> take
>>            advantage of new Window Manager and many libraries
>>
>>    [new] - Added PulseAudio as driver option for Realtime Render settings
>> on
>>            Linux
>>
>>    [new] - Added pieces by Brian Wong to examples\pieces\brianWong folder
>>
>>    [fix] - bug 2864419 - fixed importing multiline i- and f-statements
>> when
>>            importing CSD or ORC/SCO; added multiline i-statment in score
>> parser
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>
>
>
> --
> ciao,
> jAdams
>
>
>
>


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

Hi Steven,

Nice work. Looks very polished.

I've always thought that blue share could be a platform for
collaboration even across frontends. What do you think of the widget
format proposal I showed some time ago? Do you think it's worth trying
to implement it to encourage collaboration in blue share?

Cheers,
Andrés

On Fri, Jan 8, 2010 at 7:29 PM, Steven Yi  wrote:
> Thanks Jason and everyone!
>
> I'm hoping to also "reboot" blueShare by making a full website that
> will be both the home of blue (blue's new website) as well as
> blueShare as part of it.  Hopefully can make it more community
> oriented, so things like seeing popularity of instruments/effects,
> comments, etc.  I'm working on a design document now for MIDI and
> probably will try be a little more formal with how releases and things
> get put together.  Part of the future of blueShare I think will go
> hand-in-hand with moving libraries from categories-based to tags-based
> (or perhaps keeping categories and adding tags).
>
> There's a lot on my mind now but it's going to take some time to get
> it all going.  Hopefully we all benefit from it!
>
> Thanks!
> steven
>
> On Fri, Jan 8, 2010 at 1:46 PM, Jason a  wrote:
>> AWESOME!  just downloaded, gave it a good run-through and i'm impressed!  i
>> installed it and whammo, it worked... no fiddling, no noodling with
>> preferences, nothing!  it seems a lot more stable in it's normal, everyday
>> functions too (button pushing, screen switching, etc).  i can't wait to
>> start composing with it.  great job.  big up to you Steven, and all of your
>> cohorts/minions/associates/assistants, great work.
>>
>> jAdams
>>
>> On Thu, Jan 7, 2010 at 10:36 PM, Steven Yi  wrote:
>>>
>>> Hi All,
>>>
>>> After a long hiatus for releases, I am happy to announce blue 2.0.0 is
>>> now available at:
>>>
>>> http://www.csounds.com/stevenyi/blue
>>>
>>> (Note: the above site is old and will be updated for 2.1.0.  The
>>> download can also be retrieved from the sourceforge site at
>>> http://sf.net/projects/bluemusic).
>>>
>>> The big change is that blue 2.0.0 has been rewritten to use the
>>> Nebeans Rich-Client Platform.  This has taken quite a bit of time but
>>> I think the app has gained a lot of nice features in using the RCP
>>> libraries, particularly a nicer window system that users can customize
>>> the locations of windows of the app (i.e. move score side-by-side to
>>> orchestra, detach orchestra into it's own window to pull to a separate
>>> screen, etc.).  Also, there a number of nice UI things in RCP that I
>>> have started to take advantage of.
>>>
>>> This release is feature-equivalent to blue 0.125.0 and projects that
>>> working 0.125.0 should work open up and work fine in blue 2.0.0.  I am
>>> going to be ramping up my time on developing blue and moving forward
>>> with now with new feature development. Initial aims are to improve the
>>> PatternObject and to work on MIDI input for 2.1.0, as well as going
>>> through and taking care of issues in the bug and feature request
>>> databases on SourceForge.
>>>
>>> Documentation was only partially updated for this release and most of
>>> the documentation is still from 0.125.0.  In reviewing the
>>> documentation I have decided that a larger reorganization of the
>>> documentation is necessary and this work has been scheduled for 2.1.0.
>>>  For any questions regarding 2.0.0, please either email the blue users
>>> mailing list (preferred) or email me directly and I'll be happy to
>>> answer questions.
>>>
>>> A note on installation: for this release and for the foreseeable
>>> future, the application is now simply bundled in a zip file.  Unzip
>>> the file and go into the blue/bin folder and run either blue.exe or
>>> the blue shell script to launch the application.
>>>
>>> Thank you to all of the blue users on on the blue mailing list who
>>> have provided feedback during the 2.0.0 beta releases: you have helped
>>> tremendously in helping to find bugs and make this release possible!
>>>
>>> Thanks an enjoy!
>>> steven
>>>
>>> p.s. - Thank you to Brian Wong for contributing new pieces for the
>>> examples folder!  I know I have contacted a number of people for other
>>> contributions and may have lost them in the time 2.0.0 was being
>>> developed, my apologies!  If you have a piece you would like to
>>> contribute, please email me and I would love to add them to blue for
>>> all users to study and enjoy!
>>>
>>> [CHANGE LOG]
>>>
>>> >Notes for 2.0.0 <
>>> [released 2010.01.07]
>>>
>>> Steven
>>> Yi-----------------------------------------------------------------------
>>>
>>> blue
>>>
>>>    [new] - Converted application to use Netbeans Rich Client Platform to
>>> take
>>>            advantage of new Window Manager and many libraries
>>>
>>>    [new] - Added PulseAudio as driver option for Realtime Render settings
>>> on
>>>            Linux
>>>
>>>    [new] - Added pieces by Brian Wong to examples\pieces\brianWong folder
>>>
>>>    [fix] - bug 2864419 - fixed importing multiline i- and f-statements
>>> when
>>>            importing CSD or ORC/SCO; added multiline i-statment in score
>>> parser
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>
>>
>>
>> --
>> ciao,
>> jAdams
>>
>>
>>
>>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"



-- 


Andrés


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

Hi Andres,

Just catching up on older emails now.  blueShare itself is open in
that anyone can talk to the API (it uses xml-rpc, though I guess I
should considering moving to JSON sometime).  However, the big issue
is that what is stored in blueShare is just the XML-serialized version
of the different instrument classes and the effects objects.  These
then map to objects which other applications would need to have some
concept for and support.  I think the best way to think of what is in
blueShare and in blue is thinking of VST instruments and effects. Like
VST, blue instruments and effects are--when coded
correctly--completely self-contained and can be inserted into any
project and automatically link into the audio-signal flow graph
through the mixer.

The issue with trying to reuse the data in blueShare in say,
QuteCsound, is that I see diferences in the model for how interfaces
are used.  An application like QuteCsound, MacCsound, or using FLTK
widgets has a view where it's like you're building with Csound a
standalone audio application. The single main interface then is
reference-able by multiple csound instruments and there is no
encapsulation into reusable parts.  Not to say one method is better
than the other, just that the purposes are different, and there's sort
of a cognitive dissonance in how to share information.

As another example, blue also communicates to the Csound UDO
repository over xml-rpc and is able to download UDO's directly from
the website into the project.  This is possible because blue has a UDO
object that it can wrap the incoming UDO with and then handle as a
separate object.  In terms of other programs, unless they have this
abstraction, the best they can do is download the UDO and directly
insert the text into a CSD.

If there is a desire to create a share-able respository for Csound
programs, I think we'd have to come to some agreement on what we are
sharing.  Would it be an instrument? An ftable definition?  (Could be
useful if it could contain an attachment, so that we could store
things like strike data for physical models...).  If we come up with
the concepts of what to share, then we could look at creating a
CsoundShare site.

steven


On Sat, Jan 9, 2010 at 5:33 AM, Andres Cabrera  wrote:
> Hi Steven,
>
> Nice work. Looks very polished.
>
> I've always thought that blue share could be a platform for
> collaboration even across frontends. What do you think of the widget
> format proposal I showed some time ago? Do you think it's worth trying
> to implement it to encourage collaboration in blue share?
>
> Cheers,
> Andrés
>
> On Fri, Jan 8, 2010 at 7:29 PM, Steven Yi  wrote:
>> Thanks Jason and everyone!
>>
>> I'm hoping to also "reboot" blueShare by making a full website that
>> will be both the home of blue (blue's new website) as well as
>> blueShare as part of it.  Hopefully can make it more community
>> oriented, so things like seeing popularity of instruments/effects,
>> comments, etc.  I'm working on a design document now for MIDI and
>> probably will try be a little more formal with how releases and things
>> get put together.  Part of the future of blueShare I think will go
>> hand-in-hand with moving libraries from categories-based to tags-based
>> (or perhaps keeping categories and adding tags).
>>
>> There's a lot on my mind now but it's going to take some time to get
>> it all going.  Hopefully we all benefit from it!
>>
>> Thanks!
>> steven
>>
>> On Fri, Jan 8, 2010 at 1:46 PM, Jason a  wrote:
>>> AWESOME!  just downloaded, gave it a good run-through and i'm impressed!  i
>>> installed it and whammo, it worked... no fiddling, no noodling with
>>> preferences, nothing!  it seems a lot more stable in it's normal, everyday
>>> functions too (button pushing, screen switching, etc).  i can't wait to
>>> start composing with it.  great job.  big up to you Steven, and all of your
>>> cohorts/minions/associates/assistants, great work.
>>>
>>> jAdams
>>>
>>> On Thu, Jan 7, 2010 at 10:36 PM, Steven Yi  wrote:
>>>>
>>>> Hi All,
>>>>
>>>> After a long hiatus for releases, I am happy to announce blue 2.0.0 is
>>>> now available at:
>>>>
>>>> http://www.csounds.com/stevenyi/blue
>>>>
>>>> (Note: the above site is old and will be updated for 2.1.0.  The
>>>> download can also be retrieved from the sourceforge site at
>>>> http://sf.net/projects/bluemusic).
>>>>
>>>> The big change is that blue 2.0.0 has been rewritten to use the
>>>> Nebeans Rich-Client Platform.  This has taken quite a bit of time but
>>>> I think the app has gained a lot of nice features in using the RCP
>>>> libraries, particularly a nicer window system that users can customize
>>>> the locations of windows of the app (i.e. move score side-by-side to
>>>> orchestra, detach orchestra into it's own window to pull to a separate
>>>> screen, etc.).  Also, there a number of nice UI things in RCP that I
>>>> have started to take advantage of.
>>>>
>>>> This release is feature-equivalent to blue 0.125.0 and projects that
>>>> working 0.125.0 should work open up and work fine in blue 2.0.0.  I am
>>>> going to be ramping up my time on developing blue and moving forward
>>>> with now with new feature development. Initial aims are to improve the
>>>> PatternObject and to work on MIDI input for 2.1.0, as well as going
>>>> through and taking care of issues in the bug and feature request
>>>> databases on SourceForge.
>>>>
>>>> Documentation was only partially updated for this release and most of
>>>> the documentation is still from 0.125.0.  In reviewing the
>>>> documentation I have decided that a larger reorganization of the
>>>> documentation is necessary and this work has been scheduled for 2.1.0.
>>>>  For any questions regarding 2.0.0, please either email the blue users
>>>> mailing list (preferred) or email me directly and I'll be happy to
>>>> answer questions.
>>>>
>>>> A note on installation: for this release and for the foreseeable
>>>> future, the application is now simply bundled in a zip file.  Unzip
>>>> the file and go into the blue/bin folder and run either blue.exe or
>>>> the blue shell script to launch the application.
>>>>
>>>> Thank you to all of the blue users on on the blue mailing list who
>>>> have provided feedback during the 2.0.0 beta releases: you have helped
>>>> tremendously in helping to find bugs and make this release possible!
>>>>
>>>> Thanks an enjoy!
>>>> steven
>>>>
>>>> p.s. - Thank you to Brian Wong for contributing new pieces for the
>>>> examples folder!  I know I have contacted a number of people for other
>>>> contributions and may have lost them in the time 2.0.0 was being
>>>> developed, my apologies!  If you have a piece you would like to
>>>> contribute, please email me and I would love to add them to blue for
>>>> all users to study and enjoy!
>>>>
>>>> [CHANGE LOG]
>>>>
>>>> >Notes for 2.0.0 <
>>>> [released 2010.01.07]
>>>>
>>>> Steven
>>>> Yi-----------------------------------------------------------------------
>>>>
>>>> blue
>>>>
>>>>    [new] - Converted application to use Netbeans Rich Client Platform to
>>>> take
>>>>            advantage of new Window Manager and many libraries
>>>>
>>>>    [new] - Added PulseAudio as driver option for Realtime Render settings
>>>> on
>>>>            Linux
>>>>
>>>>    [new] - Added pieces by Brian Wong to examples\pieces\brianWong folder
>>>>
>>>>    [fix] - bug 2864419 - fixed importing multiline i- and f-statements
>>>> when
>>>>            importing CSD or ORC/SCO; added multiline i-statment in score
>>>> parser
>>>>
>>>>
>>>> Send bugs reports to this list.
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>> csound"
>>>
>>>
>>>
>>> --
>>> ciao,
>>> jAdams
>>>
>>>
>>>
>>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
>
> --
>
>
> Andrés
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"


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

Hi Steven,

I understand the differences, but I think there is enough common
ground to enable sharing.

For example, for UDOs, QuteCsound can import from blueShare and paste
in the code. It could also export the UDOs by parsing the csd file,
looking for UDOs, and letting the user select which one he wants to
export. So here comes a question, what other information goes with
UDOs in blueShare. One thing I'm thinking that might go is Csound
version, as UDOs which depend on recent opcodes will fail in older
versions, but I'm not really sure if this is worth the trouble.

For instruments and effects, the situation would be somewhat similar.
When importing from blue, QuteCsound would simply paste the text into
the csd file. Exporting from QuteCsound would be a bit different, as
it would export the whole csd file, or just a particular instrument
according to the instructions by the user.

Of course it's not perfect, but I think this kind of collaboration
might be still be very good.

What do you think?

Can you give me some pointers as to where in your sources the
communication with blueshare is established, and the format which is
used to transmit the information?

Thanks,
Andrés

On Sat, Jan 16, 2010 at 5:32 PM, Steven Yi  wrote:
> Hi Andres,
>
> Just catching up on older emails now.  blueShare itself is open in
> that anyone can talk to the API (it uses xml-rpc, though I guess I
> should considering moving to JSON sometime).  However, the big issue
> is that what is stored in blueShare is just the XML-serialized version
> of the different instrument classes and the effects objects.  These
> then map to objects which other applications would need to have some
> concept for and support.  I think the best way to think of what is in
> blueShare and in blue is thinking of VST instruments and effects. Like
> VST, blue instruments and effects are--when coded
> correctly--completely self-contained and can be inserted into any
> project and automatically link into the audio-signal flow graph
> through the mixer.
>
> The issue with trying to reuse the data in blueShare in say,
> QuteCsound, is that I see diferences in the model for how interfaces
> are used.  An application like QuteCsound, MacCsound, or using FLTK
> widgets has a view where it's like you're building with Csound a
> standalone audio application. The single main interface then is
> reference-able by multiple csound instruments and there is no
> encapsulation into reusable parts.  Not to say one method is better
> than the other, just that the purposes are different, and there's sort
> of a cognitive dissonance in how to share information.
>
> As another example, blue also communicates to the Csound UDO
> repository over xml-rpc and is able to download UDO's directly from
> the website into the project.  This is possible because blue has a UDO
> object that it can wrap the incoming UDO with and then handle as a
> separate object.  In terms of other programs, unless they have this
> abstraction, the best they can do is download the UDO and directly
> insert the text into a CSD.
>
> If there is a desire to create a share-able respository for Csound
> programs, I think we'd have to come to some agreement on what we are
> sharing.  Would it be an instrument? An ftable definition?  (Could be
> useful if it could contain an attachment, so that we could store
> things like strike data for physical models...).  If we come up with
> the concepts of what to share, then we could look at creating a
> CsoundShare site.
>
> steven
>
>
> On Sat, Jan 9, 2010 at 5:33 AM, Andres Cabrera  wrote:
>> Hi Steven,
>>
>> Nice work. Looks very polished.
>>
>> I've always thought that blue share could be a platform for
>> collaboration even across frontends. What do you think of the widget
>> format proposal I showed some time ago? Do you think it's worth trying
>> to implement it to encourage collaboration in blue share?
>>
>> Cheers,
>> Andrés
>>
>> On Fri, Jan 8, 2010 at 7:29 PM, Steven Yi  wrote:
>>> Thanks Jason and everyone!
>>>
>>> I'm hoping to also "reboot" blueShare by making a full website that
>>> will be both the home of blue (blue's new website) as well as
>>> blueShare as part of it.  Hopefully can make it more community
>>> oriented, so things like seeing popularity of instruments/effects,
>>> comments, etc.  I'm working on a design document now for MIDI and
>>> probably will try be a little more formal with how releases and things
>>> get put together.  Part of the future of blueShare I think will go
>>> hand-in-hand with moving libraries from categories-based to tags-based
>>> (or perhaps keeping categories and adding tags).
>>>
>>> There's a lot on my mind now but it's going to take some time to get
>>> it all going.  Hopefully we all benefit from it!
>>>
>>> Thanks!
>>> steven
>>>
>>> On Fri, Jan 8, 2010 at 1:46 PM, Jason a  wrote:
>>>> AWESOME!  just downloaded, gave it a good run-through and i'm impressed!  i
>>>> installed it and whammo, it worked... no fiddling, no noodling with
>>>> preferences, nothing!  it seems a lot more stable in it's normal, everyday
>>>> functions too (button pushing, screen switching, etc).  i can't wait to
>>>> start composing with it.  great job.  big up to you Steven, and all of your
>>>> cohorts/minions/associates/assistants, great work.
>>>>
>>>> jAdams
>>>>
>>>> On Thu, Jan 7, 2010 at 10:36 PM, Steven Yi  wrote:
>>>>>
>>>>> Hi All,
>>>>>
>>>>> After a long hiatus for releases, I am happy to announce blue 2.0.0 is
>>>>> now available at:
>>>>>
>>>>> http://www.csounds.com/stevenyi/blue
>>>>>
>>>>> (Note: the above site is old and will be updated for 2.1.0.  The
>>>>> download can also be retrieved from the sourceforge site at
>>>>> http://sf.net/projects/bluemusic).
>>>>>
>>>>> The big change is that blue 2.0.0 has been rewritten to use the
>>>>> Nebeans Rich-Client Platform.  This has taken quite a bit of time but
>>>>> I think the app has gained a lot of nice features in using the RCP
>>>>> libraries, particularly a nicer window system that users can customize
>>>>> the locations of windows of the app (i.e. move score side-by-side to
>>>>> orchestra, detach orchestra into it's own window to pull to a separate
>>>>> screen, etc.).  Also, there a number of nice UI things in RCP that I
>>>>> have started to take advantage of.
>>>>>
>>>>> This release is feature-equivalent to blue 0.125.0 and projects that
>>>>> working 0.125.0 should work open up and work fine in blue 2.0.0.  I am
>>>>> going to be ramping up my time on developing blue and moving forward
>>>>> with now with new feature development. Initial aims are to improve the
>>>>> PatternObject and to work on MIDI input for 2.1.0, as well as going
>>>>> through and taking care of issues in the bug and feature request
>>>>> databases on SourceForge.
>>>>>
>>>>> Documentation was only partially updated for this release and most of
>>>>> the documentation is still from 0.125.0.  In reviewing the
>>>>> documentation I have decided that a larger reorganization of the
>>>>> documentation is necessary and this work has been scheduled for 2.1.0.
>>>>>  For any questions regarding 2.0.0, please either email the blue users
>>>>> mailing list (preferred) or email me directly and I'll be happy to
>>>>> answer questions.
>>>>>
>>>>> A note on installation: for this release and for the foreseeable
>>>>> future, the application is now simply bundled in a zip file.  Unzip
>>>>> the file and go into the blue/bin folder and run either blue.exe or
>>>>> the blue shell script to launch the application.
>>>>>
>>>>> Thank you to all of the blue users on on the blue mailing list who
>>>>> have provided feedback during the 2.0.0 beta releases: you have helped
>>>>> tremendously in helping to find bugs and make this release possible!
>>>>>
>>>>> Thanks an enjoy!
>>>>> steven
>>>>>
>>>>> p.s. - Thank you to Brian Wong for contributing new pieces for the
>>>>> examples folder!  I know I have contacted a number of people for other
>>>>> contributions and may have lost them in the time 2.0.0 was being
>>>>> developed, my apologies!  If you have a piece you would like to
>>>>> contribute, please email me and I would love to add them to blue for
>>>>> all users to study and enjoy!
>>>>>
>>>>> [CHANGE LOG]
>>>>>
>>>>> >Notes for 2.0.0 <
>>>>> [released 2010.01.07]
>>>>>
>>>>> Steven
>>>>> Yi-----------------------------------------------------------------------
>>>>>
>>>>> blue
>>>>>
>>>>>    [new] - Converted application to use Netbeans Rich Client Platform to
>>>>> take
>>>>>            advantage of new Window Manager and many libraries
>>>>>
>>>>>    [new] - Added PulseAudio as driver option for Realtime Render settings
>>>>> on
>>>>>            Linux
>>>>>
>>>>>    [new] - Added pieces by Brian Wong to examples\pieces\brianWong folder
>>>>>
>>>>>    [fix] - bug 2864419 - fixed importing multiline i- and f-statements
>>>>> when
>>>>>            importing CSD or ORC/SCO; added multiline i-statment in score
>>>>> parser
>>>>>
>>>>>
>>>>> Send bugs reports to this list.
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>>> csound"
>>>>
>>>>
>>>>
>>>> --
>>>> ciao,
>>>> jAdams
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>
>>
>>
>> --
>>
>>
>> Andrés
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"



-- 


Andrés


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

Hi Andres,

I think you've missed my point a bit regarding instruments/effects.
blueShare shares blue Instrument and Effects classes in XML format.
You can't just paste it because it is not valid csound code. If
QuteCsound or any other program downloads from blueShare, it will
*have* to interpret the XML.  Plus, since the instruments and effects
may have changed in their structure over time, they would have to
interpret the version that may be in the XML and handle differences in
versions.  This is not a trivial thing, you would have to have
comparable classes to each of blue's soundObjects complete with all
rendering code.

Another point is that blue instruments are designed in way's that make
sense for blue.  If other instruments are uploaded that aren't for
blue really, blue users will have to deal with instruments which may
not be useful to them for blue.

I would much rather have a separate sharing site that both blue and
any other program can work with.  That way, the issues with blue's
representation and object model go away.  Already the UDO repository
on Csounds.com is an example.  In blue, the "I" button on the UDO
manager grabs a list of UDO's from the UDO Repository, not blueShare.
Any program capable of communicating with xml-rpc is able to work with
this.  It would make more sense to me to create a a CsoundShare site
and incorporate the UDO repository into it rather than trying to open
up blueShare to non-blue related items.

If we do this, then I'd keep blueShare for blue and add a CsoundShare
browser in blue. How does a CsoundShare site sound to you?  If good,
would the following work:

1. Instruments - upload/download just what is within the instr/endin,
have author, date uploaded, date last modified, category (or tags),
and comments/documentation
2. UDO - use what is in the UDO repository now

If we do this, I'd probably opt to rewrite the UDO repository and
merge into a single site using RubyOnRails, as blueShare is currently
coded in Rails.  We could choose JSON or whatever format for
communications would be desirable by you and others.

Perhaps too we could use share.csounds.com as the site URL, with
share.csounds.com/api as the endpoint.

Thoughts?
steven




On Fri, Jan 22, 2010 at 5:17 AM, Andres Cabrera  wrote:
> Hi Steven,
>
> I understand the differences, but I think there is enough common
> ground to enable sharing.
>
> For example, for UDOs, QuteCsound can import from blueShare and paste
> in the code. It could also export the UDOs by parsing the csd file,
> looking for UDOs, and letting the user select which one he wants to
> export. So here comes a question, what other information goes with
> UDOs in blueShare. One thing I'm thinking that might go is Csound
> version, as UDOs which depend on recent opcodes will fail in older
> versions, but I'm not really sure if this is worth the trouble.
>
> For instruments and effects, the situation would be somewhat similar.
> When importing from blue, QuteCsound would simply paste the text into
> the csd file. Exporting from QuteCsound would be a bit different, as
> it would export the whole csd file, or just a particular instrument
> according to the instructions by the user.
>
> Of course it's not perfect, but I think this kind of collaboration
> might be still be very good.
>
> What do you think?
>
> Can you give me some pointers as to where in your sources the
> communication with blueshare is established, and the format which is
> used to transmit the information?
>
> Thanks,
> Andrés
>
> On Sat, Jan 16, 2010 at 5:32 PM, Steven Yi  wrote:
>> Hi Andres,
>>
>> Just catching up on older emails now.  blueShare itself is open in
>> that anyone can talk to the API (it uses xml-rpc, though I guess I
>> should considering moving to JSON sometime).  However, the big issue
>> is that what is stored in blueShare is just the XML-serialized version
>> of the different instrument classes and the effects objects.  These
>> then map to objects which other applications would need to have some
>> concept for and support.  I think the best way to think of what is in
>> blueShare and in blue is thinking of VST instruments and effects. Like
>> VST, blue instruments and effects are--when coded
>> correctly--completely self-contained and can be inserted into any
>> project and automatically link into the audio-signal flow graph
>> through the mixer.
>>
>> The issue with trying to reuse the data in blueShare in say,
>> QuteCsound, is that I see diferences in the model for how interfaces
>> are used.  An application like QuteCsound, MacCsound, or using FLTK
>> widgets has a view where it's like you're building with Csound a
>> standalone audio application. The single main interface then is
>> reference-able by multiple csound instruments and there is no
>> encapsulation into reusable parts.  Not to say one method is better
>> than the other, just that the purposes are different, and there's sort
>> of a cognitive dissonance in how to share information.
>>
>> As another example, blue also communicates to the Csound UDO
>> repository over xml-rpc and is able to download UDO's directly from
>> the website into the project.  This is possible because blue has a UDO
>> object that it can wrap the incoming UDO with and then handle as a
>> separate object.  In terms of other programs, unless they have this
>> abstraction, the best they can do is download the UDO and directly
>> insert the text into a CSD.
>>
>> If there is a desire to create a share-able respository for Csound
>> programs, I think we'd have to come to some agreement on what we are
>> sharing.  Would it be an instrument? An ftable definition?  (Could be
>> useful if it could contain an attachment, so that we could store
>> things like strike data for physical models...).  If we come up with
>> the concepts of what to share, then we could look at creating a
>> CsoundShare site.
>>
>> steven
>>
>>
>> On Sat, Jan 9, 2010 at 5:33 AM, Andres Cabrera  wrote:
>>> Hi Steven,
>>>
>>> Nice work. Looks very polished.
>>>
>>> I've always thought that blue share could be a platform for
>>> collaboration even across frontends. What do you think of the widget
>>> format proposal I showed some time ago? Do you think it's worth trying
>>> to implement it to encourage collaboration in blue share?
>>>
>>> Cheers,
>>> Andrés
>>>
>>> On Fri, Jan 8, 2010 at 7:29 PM, Steven Yi  wrote:
>>>> Thanks Jason and everyone!
>>>>
>>>> I'm hoping to also "reboot" blueShare by making a full website that
>>>> will be both the home of blue (blue's new website) as well as
>>>> blueShare as part of it.  Hopefully can make it more community
>>>> oriented, so things like seeing popularity of instruments/effects,
>>>> comments, etc.  I'm working on a design document now for MIDI and
>>>> probably will try be a little more formal with how releases and things
>>>> get put together.  Part of the future of blueShare I think will go
>>>> hand-in-hand with moving libraries from categories-based to tags-based
>>>> (or perhaps keeping categories and adding tags).
>>>>
>>>> There's a lot on my mind now but it's going to take some time to get
>>>> it all going.  Hopefully we all benefit from it!
>>>>
>>>> Thanks!
>>>> steven
>>>>
>>>> On Fri, Jan 8, 2010 at 1:46 PM, Jason a  wrote:
>>>>> AWESOME!  just downloaded, gave it a good run-through and i'm impressed!  i
>>>>> installed it and whammo, it worked... no fiddling, no noodling with
>>>>> preferences, nothing!  it seems a lot more stable in it's normal, everyday
>>>>> functions too (button pushing, screen switching, etc).  i can't wait to
>>>>> start composing with it.  great job.  big up to you Steven, and all of your
>>>>> cohorts/minions/associates/assistants, great work.
>>>>>
>>>>> jAdams
>>>>>
>>>>> On Thu, Jan 7, 2010 at 10:36 PM, Steven Yi  wrote:
>>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> After a long hiatus for releases, I am happy to announce blue 2.0.0 is
>>>>>> now available at:
>>>>>>
>>>>>> http://www.csounds.com/stevenyi/blue
>>>>>>
>>>>>> (Note: the above site is old and will be updated for 2.1.0.  The
>>>>>> download can also be retrieved from the sourceforge site at
>>>>>> http://sf.net/projects/bluemusic).
>>>>>>
>>>>>> The big change is that blue 2.0.0 has been rewritten to use the
>>>>>> Nebeans Rich-Client Platform.  This has taken quite a bit of time but
>>>>>> I think the app has gained a lot of nice features in using the RCP
>>>>>> libraries, particularly a nicer window system that users can customize
>>>>>> the locations of windows of the app (i.e. move score side-by-side to
>>>>>> orchestra, detach orchestra into it's own window to pull to a separate
>>>>>> screen, etc.).  Also, there a number of nice UI things in RCP that I
>>>>>> have started to take advantage of.
>>>>>>
>>>>>> This release is feature-equivalent to blue 0.125.0 and projects that
>>>>>> working 0.125.0 should work open up and work fine in blue 2.0.0.  I am
>>>>>> going to be ramping up my time on developing blue and moving forward
>>>>>> with now with new feature development. Initial aims are to improve the
>>>>>> PatternObject and to work on MIDI input for 2.1.0, as well as going
>>>>>> through and taking care of issues in the bug and feature request
>>>>>> databases on SourceForge.
>>>>>>
>>>>>> Documentation was only partially updated for this release and most of
>>>>>> the documentation is still from 0.125.0.  In reviewing the
>>>>>> documentation I have decided that a larger reorganization of the
>>>>>> documentation is necessary and this work has been scheduled for 2.1.0.
>>>>>>  For any questions regarding 2.0.0, please either email the blue users
>>>>>> mailing list (preferred) or email me directly and I'll be happy to
>>>>>> answer questions.
>>>>>>
>>>>>> A note on installation: for this release and for the foreseeable
>>>>>> future, the application is now simply bundled in a zip file.  Unzip
>>>>>> the file and go into the blue/bin folder and run either blue.exe or
>>>>>> the blue shell script to launch the application.
>>>>>>
>>>>>> Thank you to all of the blue users on on the blue mailing list who
>>>>>> have provided feedback during the 2.0.0 beta releases: you have helped
>>>>>> tremendously in helping to find bugs and make this release possible!
>>>>>>
>>>>>> Thanks an enjoy!
>>>>>> steven
>>>>>>
>>>>>> p.s. - Thank you to Brian Wong for contributing new pieces for the
>>>>>> examples folder!  I know I have contacted a number of people for other
>>>>>> contributions and may have lost them in the time 2.0.0 was being
>>>>>> developed, my apologies!  If you have a piece you would like to
>>>>>> contribute, please email me and I would love to add them to blue for
>>>>>> all users to study and enjoy!
>>>>>>
>>>>>> [CHANGE LOG]
>>>>>>
>>>>>> >Notes for 2.0.0 <
>>>>>> [released 2010.01.07]
>>>>>>
>>>>>> Steven
>>>>>> Yi-----------------------------------------------------------------------
>>>>>>
>>>>>> blue
>>>>>>
>>>>>>    [new] - Converted application to use Netbeans Rich Client Platform to
>>>>>> take
>>>>>>            advantage of new Window Manager and many libraries
>>>>>>
>>>>>>    [new] - Added PulseAudio as driver option for Realtime Render settings
>>>>>> on
>>>>>>            Linux
>>>>>>
>>>>>>    [new] - Added pieces by Brian Wong to examples\pieces\brianWong folder
>>>>>>
>>>>>>    [fix] - bug 2864419 - fixed importing multiline i- and f-statements
>>>>>> when
>>>>>>            importing CSD or ORC/SCO; added multiline i-statment in score
>>>>>> parser
>>>>>>
>>>>>>
>>>>>> Send bugs reports to this list.
>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>>>> csound"
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> ciao,
>>>>> jAdams
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> Send bugs reports to this list.
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>
>>>
>>>
>>> --
>>>
>>>
>>> Andrés
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
>
> --
>
>
> Andrés
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"


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

Hi Steven,

On Fri, Jan 22, 2010 at 4:12 PM, Steven Yi  wrote:
> Hi Andres,
>
> I think you've missed my point a bit regarding instruments/effects.
> blueShare shares blue Instrument and Effects classes in XML format.
> You can't just paste it because it is not valid csound code. If
> QuteCsound or any other program downloads from blueShare, it will
> *have* to interpret the XML.  Plus, since the instruments and effects
> may have changed in their structure over time, they would have to
> interpret the version that may be in the XML and handle differences in
> versions.  This is not a trivial thing, you would have to have
> comparable classes to each of blue's soundObjects complete with all
> rendering code.
>

Yes, I am aware of this, and was thinking support in QuteCsound would
not be dynamic, and if you import an instrument (by pasting it), it
would be now completely independent and if you paste it again, it's
your job to resolve confilicts...
I was thinking the XML structure could be parsed to know where each
part should be pasted, that's why I was asking you about where the
format is specified, to understand if what I am thinking is feasible.

> Another point is that blue instruments are designed in way's that make
> sense for blue.  If other instruments are uploaded that aren't for
> blue really, blue users will have to deal with instruments which may
> not be useful to them for blue.
>

Yes, I thought of that, and what I was planning was for not allowing
users to upload instruments which are not compatible with blue. but
what you mention below sounds better...

> I would much rather have a separate sharing site that both blue and
> any other program can work with.  That way, the issues with blue's
> representation and object model go away.  Already the UDO repository
> on Csounds.com is an example.  In blue, the "I" button on the UDO
> manager grabs a list of UDO's from the UDO Repository, not blueShare.
> Any program capable of communicating with xml-rpc is able to work with
> this.  It would make more sense to me to create a a CsoundShare site
> and incorporate the UDO repository into it rather than trying to open
> up blueShare to non-blue related items.
>
> If we do this, then I'd keep blueShare for blue and add a CsoundShare
> browser in blue. How does a CsoundShare site sound to you?  If good,
> would the following work:
>
> 1. Instruments - upload/download just what is within the instr/endin,
> have author, date uploaded, date last modified, category (or tags),
> and comments/documentation
> 2. UDO - use what is in the UDO repository now
>
> If we do this, I'd probably opt to rewrite the UDO repository and
> merge into a single site using RubyOnRails, as blueShare is currently
> coded in Rails.  We could choose JSON or whatever format for
> communications would be desirable by you and others.
>
> Perhaps too we could use share.csounds.com as the site URL, with
> share.csounds.com/api as the endpoint.
>
> Thoughts?

That seems a much better idea, actually. And less work for me as well
(but maybe a bit more work for you...). Do you think there should
there be a separate section for widget enabled csds?

Maybe you could also allow blue to import from that share site and
then a common xml widget format will be useful.

Can you give me some pointers about json and xml-rpc parsing and
usage? I would prefer the one that involves coding that is simpler and
easier to maintain.


Cheers,
Andrés

> steven
>
>
>
>
> On Fri, Jan 22, 2010 at 5:17 AM, Andres Cabrera  wrote:
>> Hi Steven,
>>
>> I understand the differences, but I think there is enough common
>> ground to enable sharing.
>>
>> For example, for UDOs, QuteCsound can import from blueShare and paste
>> in the code. It could also export the UDOs by parsing the csd file,
>> looking for UDOs, and letting the user select which one he wants to
>> export. So here comes a question, what other information goes with
>> UDOs in blueShare. One thing I'm thinking that might go is Csound
>> version, as UDOs which depend on recent opcodes will fail in older
>> versions, but I'm not really sure if this is worth the trouble.
>>
>> For instruments and effects, the situation would be somewhat similar.
>> When importing from blue, QuteCsound would simply paste the text into
>> the csd file. Exporting from QuteCsound would be a bit different, as
>> it would export the whole csd file, or just a particular instrument
>> according to the instructions by the user.
>>
>> Of course it's not perfect, but I think this kind of collaboration
>> might be still be very good.
>>
>> What do you think?
>>
>> Can you give me some pointers as to where in your sources the
>> communication with blueshare is established, and the format which is
>> used to transmit the information?
>>
>> Thanks,
>> Andrés
>>
>> On Sat, Jan 16, 2010 at 5:32 PM, Steven Yi  wrote:
>>> Hi Andres,
>>>
>>> Just catching up on older emails now.  blueShare itself is open in
>>> that anyone can talk to the API (it uses xml-rpc, though I guess I
>>> should considering moving to JSON sometime).  However, the big issue
>>> is that what is stored in blueShare is just the XML-serialized version
>>> of the different instrument classes and the effects objects.  These
>>> then map to objects which other applications would need to have some
>>> concept for and support.  I think the best way to think of what is in
>>> blueShare and in blue is thinking of VST instruments and effects. Like
>>> VST, blue instruments and effects are--when coded
>>> correctly--completely self-contained and can be inserted into any
>>> project and automatically link into the audio-signal flow graph
>>> through the mixer.
>>>
>>> The issue with trying to reuse the data in blueShare in say,
>>> QuteCsound, is that I see diferences in the model for how interfaces
>>> are used.  An application like QuteCsound, MacCsound, or using FLTK
>>> widgets has a view where it's like you're building with Csound a
>>> standalone audio application. The single main interface then is
>>> reference-able by multiple csound instruments and there is no
>>> encapsulation into reusable parts.  Not to say one method is better
>>> than the other, just that the purposes are different, and there's sort
>>> of a cognitive dissonance in how to share information.
>>>
>>> As another example, blue also communicates to the Csound UDO
>>> repository over xml-rpc and is able to download UDO's directly from
>>> the website into the project.  This is possible because blue has a UDO
>>> object that it can wrap the incoming UDO with and then handle as a
>>> separate object.  In terms of other programs, unless they have this
>>> abstraction, the best they can do is download the UDO and directly
>>> insert the text into a CSD.
>>>
>>> If there is a desire to create a share-able respository for Csound
>>> programs, I think we'd have to come to some agreement on what we are
>>> sharing.  Would it be an instrument? An ftable definition?  (Could be
>>> useful if it could contain an attachment, so that we could store
>>> things like strike data for physical models...).  If we come up with
>>> the concepts of what to share, then we could look at creating a
>>> CsoundShare site.
>>>
>>> steven
>>>
>>>
>>> On Sat, Jan 9, 2010 at 5:33 AM, Andres Cabrera  wrote:
>>>> Hi Steven,
>>>>
>>>> Nice work. Looks very polished.
>>>>
>>>> I've always thought that blue share could be a platform for
>>>> collaboration even across frontends. What do you think of the widget
>>>> format proposal I showed some time ago? Do you think it's worth trying
>>>> to implement it to encourage collaboration in blue share?
>>>>
>>>> Cheers,
>>>> Andrés
>>>>
>>>> On Fri, Jan 8, 2010 at 7:29 PM, Steven Yi  wrote:
>>>>> Thanks Jason and everyone!
>>>>>
>>>>> I'm hoping to also "reboot" blueShare by making a full website that
>>>>> will be both the home of blue (blue's new website) as well as
>>>>> blueShare as part of it.  Hopefully can make it more community
>>>>> oriented, so things like seeing popularity of instruments/effects,
>>>>> comments, etc.  I'm working on a design document now for MIDI and
>>>>> probably will try be a little more formal with how releases and things
>>>>> get put together.  Part of the future of blueShare I think will go
>>>>> hand-in-hand with moving libraries from categories-based to tags-based
>>>>> (or perhaps keeping categories and adding tags).
>>>>>
>>>>> There's a lot on my mind now but it's going to take some time to get
>>>>> it all going.  Hopefully we all benefit from it!
>>>>>
>>>>> Thanks!
>>>>> steven
>>>>>
>>>>> On Fri, Jan 8, 2010 at 1:46 PM, Jason a  wrote:
>>>>>> AWESOME!  just downloaded, gave it a good run-through and i'm impressed!  i
>>>>>> installed it and whammo, it worked... no fiddling, no noodling with
>>>>>> preferences, nothing!  it seems a lot more stable in it's normal, everyday
>>>>>> functions too (button pushing, screen switching, etc).  i can't wait to
>>>>>> start composing with it.  great job.  big up to you Steven, and all of your
>>>>>> cohorts/minions/associates/assistants, great work.
>>>>>>
>>>>>> jAdams
>>>>>>
>>>>>> On Thu, Jan 7, 2010 at 10:36 PM, Steven Yi  wrote:
>>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>>> After a long hiatus for releases, I am happy to announce blue 2.0.0 is
>>>>>>> now available at:
>>>>>>>
>>>>>>> http://www.csounds.com/stevenyi/blue
>>>>>>>
>>>>>>> (Note: the above site is old and will be updated for 2.1.0.  The
>>>>>>> download can also be retrieved from the sourceforge site at
>>>>>>> http://sf.net/projects/bluemusic).
>>>>>>>
>>>>>>> The big change is that blue 2.0.0 has been rewritten to use the
>>>>>>> Nebeans Rich-Client Platform.  This has taken quite a bit of time but
>>>>>>> I think the app has gained a lot of nice features in using the RCP
>>>>>>> libraries, particularly a nicer window system that users can customize
>>>>>>> the locations of windows of the app (i.e. move score side-by-side to
>>>>>>> orchestra, detach orchestra into it's own window to pull to a separate
>>>>>>> screen, etc.).  Also, there a number of nice UI things in RCP that I
>>>>>>> have started to take advantage of.
>>>>>>>
>>>>>>> This release is feature-equivalent to blue 0.125.0 and projects that
>>>>>>> working 0.125.0 should work open up and work fine in blue 2.0.0.  I am
>>>>>>> going to be ramping up my time on developing blue and moving forward
>>>>>>> with now with new feature development. Initial aims are to improve the
>>>>>>> PatternObject and to work on MIDI input for 2.1.0, as well as going
>>>>>>> through and taking care of issues in the bug and feature request
>>>>>>> databases on SourceForge.
>>>>>>>
>>>>>>> Documentation was only partially updated for this release and most of
>>>>>>> the documentation is still from 0.125.0.  In reviewing the
>>>>>>> documentation I have decided that a larger reorganization of the
>>>>>>> documentation is necessary and this work has been scheduled for 2.1.0.
>>>>>>>  For any questions regarding 2.0.0, please either email the blue users
>>>>>>> mailing list (preferred) or email me directly and I'll be happy to
>>>>>>> answer questions.
>>>>>>>
>>>>>>> A note on installation: for this release and for the foreseeable
>>>>>>> future, the application is now simply bundled in a zip file.  Unzip
>>>>>>> the file and go into the blue/bin folder and run either blue.exe or
>>>>>>> the blue shell script to launch the application.
>>>>>>>
>>>>>>> Thank you to all of the blue users on on the blue mailing list who
>>>>>>> have provided feedback during the 2.0.0 beta releases: you have helped
>>>>>>> tremendously in helping to find bugs and make this release possible!
>>>>>>>
>>>>>>> Thanks an enjoy!
>>>>>>> steven
>>>>>>>
>>>>>>> p.s. - Thank you to Brian Wong for contributing new pieces for the
>>>>>>> examples folder!  I know I have contacted a number of people for other
>>>>>>> contributions and may have lost them in the time 2.0.0 was being
>>>>>>> developed, my apologies!  If you have a piece you would like to
>>>>>>> contribute, please email me and I would love to add them to blue for
>>>>>>> all users to study and enjoy!
>>>>>>>
>>>>>>> [CHANGE LOG]
>>>>>>>
>>>>>>> >Notes for 2.0.0 <
>>>>>>> [released 2010.01.07]
>>>>>>>
>>>>>>> Steven
>>>>>>> Yi-----------------------------------------------------------------------
>>>>>>>
>>>>>>> blue
>>>>>>>
>>>>>>>    [new] - Converted application to use Netbeans Rich Client Platform to
>>>>>>> take
>>>>>>>            advantage of new Window Manager and many libraries
>>>>>>>
>>>>>>>    [new] - Added PulseAudio as driver option for Realtime Render settings
>>>>>>> on
>>>>>>>            Linux
>>>>>>>
>>>>>>>    [new] - Added pieces by Brian Wong to examples\pieces\brianWong folder
>>>>>>>
>>>>>>>    [fix] - bug 2864419 - fixed importing multiline i- and f-statements
>>>>>>> when
>>>>>>>            importing CSD or ORC/SCO; added multiline i-statment in score
>>>>>>> parser
>>>>>>>
>>>>>>>
>>>>>>> Send bugs reports to this list.
>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>>>>> csound"
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> ciao,
>>>>>> jAdams
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> Send bugs reports to this list.
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>>
>>>> Andrés
>>>>
>>>>
>>>> Send bugs reports to this list.
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>
>>
>>
>> --
>>
>>
>> Andrés
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"



-- 


Andrés


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