Re: [Bluemusic-users] blue - 0.106.0 beta

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

Hi Andres,

Thanks for your reply; I'll comment below:

> -Maybe in front of Audio and Midi, there can be slots where you can type
> in device numbers or identifiers (maybe in the future a pop up menu
> =) ), so you don't have to add -i adc in the advanced options. These
> could be pre-filled with sensible defaults according to platform.

Is this for the project settings or program options?  The idea behind
all of this is that you set the following four devices in program
options:

-Audio In
-Audio Out
-Midi In
-Midi Out

And in your project, you enable any of those four you want to use.
Now, if I give that project to someone else, the project settings
won't have to be redone just for a different set of hardware. For
example, if I give a CSD with CsOptions "-+rtaudio=alsa -d dac:hw:2,0"
this would be useless to everyone without Linux and a third sound
card.  Now with the blue render system, my blue install has the
devices defined locally and I give you a project that has "Audio Out"
enabled, if you have your audio output settings set, you can just run
it and it will use your settings (device settings are very system
dependent anyways).  Also, if you upgrade your comptuer and your
hardware settings change, you won't have to change all of your project
settings, just once in the program settings.

For me this is very useful as I'll often move projects between Linux
and Windows and the only way to configure so I don't have to change
the render settings is to use .csoundrc set default to render in
realtime and use no realtime flags in the blue commandline, which
means if I give it someone else, they'd have problems to run without
using .csoundrc in the same way.  Now with this, there''s no
confusion.

I think that this new system sort of closely parallels what users of
most other MIDI Sequencing and DAW software experience, i.e. they
configure their system once and don't worry about hardware settings on
a per project basis.

Now, if for some reason you do need to use a very specific version of
csound, you can use advanced flags with complete override to get the
same behavior as the old blue rendersystem of setting a commandline by
hand.


> -It would be nice if the command line used to call csound was printed,
> so you really know how you called csound

The commandline gets printed in the system console window that opens
up when you run blue.  If you changed that so you don't see the system
console window, then you won't see it.  I can look to see about adding
it to the Csound Output Dialog as well..

> -Would you think -b and -B are important here as choices as well.

Again, these really are tied down to your system's devices so I think
should be in the Program options and not project settings.


> -How about a button which opens a window containing a larger number of
> choices, maybe covering most of the available falgs?

For advanced options?  There are so many I wouldn't know which ones to
show.  I remember someone suggesting to look at CSEdit or WinXound for
something like this but I've forgotten what program.  Any suggestions?
 (Does MacCsound have anything for advanced flags beyond  a text
field?)

> Anyway, thanks for this nice improvement.

Thanks for the feedback!
steven