BSB instrument clones do not update with parent

[Rob Canning]

ok so i create a BSB instrument with instr ID 1 then i create multiple
instances of that instrument with ID 2 - 9
when i edit the orchestra file of instrument ID 1 it would be nice to
have the option for all the other clones to also change.

at the moment i have to delete the clones an re add them after i have
made the changes- this deletes all automation data of the clones.

any solutions?

thanks

rob

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Bluemusic-users mailing list
Bluemusic-users@...
https://lists.sourceforge.net/lists/listinfo/bluemusic-users

[Rob Canning]

thanks steven,
i have created an account and added feature requests on the blue tracker.
just wondering should i file a feature request about the mail below or
is this more a flaw in my usage of blue?
cheers
rob

Rob Canning wrote:

> ok so i create a BSB instrument with instr ID 1 then i create multiple
> instances of that instrument with ID 2 - 9
> when i edit the orchestra file of instrument ID 1 it would be nice to
> have the option for all the other clones to also change.
>
> at the moment i have to delete the clones an re add them after i have
> made the changes- this deletes all automation data of the clones.
>
> any solutions?
>
> thanks
>
> rob
>
> -------------------------------------------------------------------------
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
> _______________________________________________
> Bluemusic-users mailing list
> Bluemusic-users@...
> https://lists.sourceforge.net/lists/listinfo/bluemusic-users
>
>
>  

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Bluemusic-users mailing list
Bluemusic-users@...
https://lists.sourceforge.net/lists/listinfo/bluemusic-users

[Steven Yi]

Hi Rob,

For this case, I'm not sure blue can support what you are talking
about.  There's a real advantage in my opinion of instruments each
being their own encapsulated item.  It becomes somewhat impossible to
allow each instrument to have their own configuration values but share
code and parameters, as the configurations values and automation data
is stored with the parameters.  So for this case unfortunately, I
think it'd be near impossible to support what you are asking for.

Thanks!
steven

On Mon, Jul 7, 2008 at 10:12 AM, Rob Canning <robcanning@...> wrote:

> thanks steven,
> i have created an account and added feature requests on the blue tracker.
> just wondering should i file a feature request about the mail below or
> is this more a flaw in my usage of blue?
> cheers
> rob
>
> Rob Canning wrote:
>> ok so i create a BSB instrument with instr ID 1 then i create multiple
>> instances of that instrument with ID 2 - 9
>> when i edit the orchestra file of instrument ID 1 it would be nice to
>> have the option for all the other clones to also change.
>>
>> at the moment i have to delete the clones an re add them after i have
>> made the changes- this deletes all automation data of the clones.
>>
>> any solutions?
>>
>> thanks
>>
>> rob
>>
>> -------------------------------------------------------------------------
>> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
>> Studies have shown that voting for your favorite open source project,
>> along with a healthy diet, reduces your potential for chronic lameness
>> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
>> _______________________________________________
>> Bluemusic-users mailing list
>> Bluemusic-users@...
>> https://lists.sourceforge.net/lists/listinfo/bluemusic-users
>>
>>
>>
>
>
> -------------------------------------------------------------------------
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
> _______________________________________________
> Bluemusic-users mailing list
> Bluemusic-users@...
> https://lists.sourceforge.net/lists/listinfo/bluemusic-users
>

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Bluemusic-users mailing list
Bluemusic-users@...
https://lists.sourceforge.net/lists/listinfo/bluemusic-users

[Michael Bechard]

I agree about the advantage of being able to edit each instrument copy independent of each other and independent of the same instrument in your library. However, I can identify with the problem he's speaking of. What might be a nice half-way solution might be the ability to paste an instrument in the place of another, completely overwriting its code but retaining all automation and channel settings. Then, if you make a change in instrument #1, at least you could just copy and paste it over the other eight instances and be done with it.

Michael



----- Original Message ----
From: Steven Yi <stevenyi@...>
To: info@...; blue users mailing list <bluemusic-users@...>
Sent: Monday, July 7, 2008 12:42:49 PM
Subject: Re: [Bluemusic-users] BSB instrument clones do not update with parent

Hi Rob,

For this case, I'm not sure blue can support what you are talking
about.  There's a real advantage in my opinion of instruments each
being their own encapsulated item.  It becomes somewhat impossible to
allow each instrument to have their own configuration values but share
code and parameters, as the configurations values and automation data
is stored with the parameters.  So for this case unfortunately, I
think it'd be near impossible to support what you are asking for.

Thanks!
steven

On Mon, Jul 7, 2008 at 10:12 AM, Rob Canning <robcanning@...> wrote:

> thanks steven,
> i have created an account and added feature requests on the blue tracker.
> just wondering should i file a feature request about the mail below or
> is this more a flaw in my usage of blue?
> cheers
> rob
>
> Rob Canning wrote:
>> ok so i create a BSB instrument with instr ID 1 then i create multiple
>> instances of that instrument with ID 2 - 9
>> when i edit the orchestra file of instrument ID 1 it would be nice to
>> have the option for all the other clones to also change.
>>
>> at the moment i have to delete the clones an re add them after i have
>> made the changes- this deletes all automation data of the clones.
>>
>> any solutions?
>>
>> thanks
>>
>> rob
>>
>> -------------------------------------------------------------------------
>> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
>> Studies have shown that voting for your favorite open source project,
>> along with a healthy diet, reduces your potential for chronic lameness
>> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
>> _______________________________________________
>> Bluemusic-users mailing list
>> Bluemusic-users@...
>> https://lists.sourceforge.net/lists/listinfo/bluemusic-users
>>
>>
>>
>
>
> -------------------------------------------------------------------------
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
> _______________________________________________
> Bluemusic-users mailing list
> Bluemusic-users@...
> https://lists.sourceforge.net/lists/listinfo/bluemusic-users
>

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Bluemusic-users mailing list
Bluemusic-users@...
https://lists.sourceforge.net/lists/listinfo/bluemusic-users



     

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Bluemusic-users mailing list
Bluemusic-users@...
https://lists.sourceforge.net/lists/listinfo/bluemusic-users