Re: [Bluemusic-users] Thoughts on upcoming changes

[Steven Yi <ste...@gm...>]

Hi Dave,

Thanks for your feedback!  Editor enhancements are certainly something
I'd like as well.  I think to do it properly I need to switch to using
the editor component within Netbeans RCP which also means making a
parser for Csound syntax.  It's on my list of things to get to, but
I'm not sure when I'll be scheduling it.

Thanks for the birthday cheers and happy new year!
steven

On Sat, Dec 31, 2011 at 12:39 PM, Dave Seidel <da...@su...> wrote:
> These all sound great, Steven, especially the mixer ideas. If I can
> throw my $0.02 into the mix, I wish for some editor enhancements:
> ability to set a font and control over tab size (and use of tabs vs.
> spaces).
>
> Also, happy birthday and happy New Year!
>
> - Dave
>
> On Friday, December 30, 2011 7:37:54 PM, Steven Yi wrote:
>> Hi All,
>>
>> I haven't communicated much lately as I've been very much occupied
>> with core Csound work.  However, I thought I'd review some plans of
>> mine to let you all know what's on my mind and get some feedback:
>>
>> * BSB: Update the UI altogether to make it "slicker"
>>     * Make option for Knobs without value display
>>     * Make Panel Groups, Panel can have auto-layouts
>>     * Panel Groups as a feature can lead to concept of "sub patches";
>> this would merge in some ideas from the Effects system, so that
>> effects could be come reusable as sub-patches in BSB
>>
>> * Theme
>>    * I've been looking at finally cleaning up the theme.  There's lot
>> of inconsistencies and cleanup to do, and I'd like to modernize the UI
>> to be very slick.  I'm currently doing some sketching out of the theme
>> now, but this is slow work for me (but in the works)
>>
>> * Mixer
>>    * Channels become more generic: for every instrument that has a
>> blueMixerOut, create n- number of channels that is equal to max
>> channels in the chain.  This allows unbalanced in/out for effects
>> (i.e. having 9 channels going to 2 channels for ambisonic decoding to
>> hrtf output). With the existing mixer, this would allow having the bsb
>> instrument be mono out, have effects which are mono, then have a
>> default panning knob on the mixer.  The panning knob would be optional
>> though for backwards compatibility.
>>    * Creating Mixer2 system: a different UI for a mixer, would be more
>> signal flow based.  This would handle the complexities of mixing a
>> little more visually rather than relying on the metaphors of a
>> hardware mixer system.
>>
>> * Libraries
>>    * I am planning a more generic model for storage of data.  This
>> means there would be a Library panel that has a tree. Each of the top
>> nodes would be of a type, i.e. SoundObject, Audio File, Analysis File,
>> Tuning, etc.  There would be three levels of data storage:
>> Application-wide, Project-wide, instance-based (i.e. with an
>> instrument).  The UI would change to have Libraries be it's own
>> secondary side component that can be moved, and likely would have two
>> trees, top for application-wide, below for project-wide.  The two
>> trees would allow easy moving between the two zones for storing data.
>>     * I am still trying to figure out patch storage for BSB.  I'd like
>> to have a means where patches for an instrument can be shared with
>> "like" instances of that instrument, such that you can save/load
>> patches from the instance of BSB, a project-wide store, or
>> application-wide store.  However, because you can change individual
>> instances of BSB, I need to figure out a system for making these
>> patches work with each other.  I have been leaning toward it being a
>> user setting for setting a set identifier, or perhaps generating a
>> UUID but having a user settable name for the store.
>>
>> * Plugin Layers
>>   * I have still not gotten around to this, but it is definitely still
>> in the works. This allows plugins to allow new types of layers.
>> Currently there is only soundLayers for soundObjects, but imagine
>> layers for Notation, Audiofiles, etc.
>>
>> Note too, I am working more and more on cleaning up the internals of
>> blue to make the architecture much more clean.  There are also some
>> other changes planned, but these are the bigger ones I can think of at
>> the moment.
>>
>> Otherwise, I've been enjoying making some new instruments lately, and
>> hope you all have been enjoying working with blue too.
>>
>> All best!
>> steven
>>
>> ------------------------------------------------------------------------------
>> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
>> infrastructure or vast IT resources to deliver seamless, secure access to
>> virtual desktops. With this all-in-one solution, easily deploy virtual
>> desktops for less than the cost of PCs and save 60% on VDI infrastructure
>> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
>> _______________________________________________
>> Bluemusic-users mailing list
>> Blu...@li...
>> https://lists.sourceforge.net/lists/listinfo/bluemusic-users
>>
>
> ------------------------------------------------------------------------------
> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
> infrastructure or vast IT resources to deliver seamless, secure access to
> virtual desktops. With this all-in-one solution, easily deploy virtual
> desktops for less than the cost of PCs and save 60% on VDI infrastructure
> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
> _______________________________________________
> Bluemusic-users mailing list
> Blu...@li...
> https://lists.sourceforge.net/lists/listinfo/bluemusic-users