Re: [Bluemusic-users] Additional Project Options for Rendering to File

[Chuckk H. <bad...@gm...>]

No, don't do it.  Just kidding.
I think Program Settings would be the place, then maybe just a sister
button to "Use Default" to switch.  I never use CsOptions either, but
will the command options be included in a generated file otherwise?

That reminds me, does Blue support other utilities besides sndinfo and
lpanal?  I suppose the commandline is open for it, I've never tried.

Chuckk

On 7/19/05, Steven Yi <ste...@gm...> wrote:
> Hi All,
>=20
> Curious what everyone thought about this idea.  I am thinking to add
> an extra set of project properties for sr, kr, nsmps, and commandline
> to be used for rendering to File, which I would add as a menu item in
> the file menu.  The purpose of this is so that you can have your
> settings for when you render live in blue (the normal play button /
> F9), and you can also have an extra set of settings for when you
> render to disk.
>=20
> For me, I find myself copying and pasting in commands whenever I want
> to render to disk, then switching back.  Recently as I've been having
> more time to work on music, I find I'm doing this more often and
> thought adding an extra set of parameters would be nice.  For me, my
> laptop's soundcard only does 48000 and rendering anytihing besides
> that alters the quality of sound I'm hearing such that it no longer
> matches up to what is heard if I render to 44100 and put on a CD and
> play on a stereo.  I tend to render live while working at 48000 then
> render to 44100 wav and convert to mp3 to listen to while walking.
>=20
> What I am not sure yet is the UI for this.  I am thinking that for
> real estate purpose it might be best if I take the existing project
> options and put it in to a tab, then add a second tab.  The tabs would
> then be "Real-Time Options" and "Disk Options".  Hmm... maybe instead,
> I could have the two sets of options side by side, moving the command
> line setting to underneath the nchnls box, and then have two sets
> there.
>=20
> I am thinking of getting rid of CSOptions as well.  I never liked it
> and find I don't ever use it.  I think it doesn't do anyone any good
> is actually not good to use because people often put in system
> dependent settings there which don't work for everyone and should
> probably be put in .csoundrc files.  I could live with it though, so
> if anyone wants to keep it in just let me know.
>=20
> Thanks,
> steven
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&opclick
> _______________________________________________
> Bluemusic-users mailing list
> Blu...@li...
> https://lists.sourceforge.net/lists/listinfo/bluemusic-users
>=20


--=20
"It is not when truth is dirty, but when it is shallow, that the lover
of knowledge is reluctant to step into its waters."
-Friedrich Nietzsche, "Thus Spoke Zarathustra"