Re: [Bluemusic-users] Tooltips

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

Hi All,

Sorry for the late reply (BACSUG today!).  Regarding Michael's idea
about a global project isn't really the way to go, or better I should
phrase it that I can't see a good way to implement it and make it
easily usable to the user.  For default projects with settings one
uses, one can always use a $userHome/.blue/default.blue file which, if
blue finds, will create new projects using the default.blue file as a
template.  (BTW: should we put in a template feature/wizard where a
bank of templates can be distributed with blue, so that you can save
your own templates as well as create projects from them?)

As for table numbers, I no longer use score style table statements in
favor of ftgen statements as instrument can then have all of their
required ftables encapsulated with them.  This technique may not be
well known; I had been meaning to put together a tutorial for that but
have not gotten around to it.  I've attached a copy of a draft of a
piece I'm working on that has instrument that demonstrate that
functionality.  You can check out that I don't have any ftable
statements in the ftable tab.  The ftables that instruments use are
held within their "global sco" tabs in their editor, encapsulated in
"once" blocks to make sure that they only get generated once. (Not
sure if this file will render for everyone as I think I might have
made some changes to the python orchestra library in CVS; if it
doesn't work, you can at least check out the instruments. =3Do )

As for instruments being interchangable, I find that as long as their
pfield signature (for lack of better term) is the same, they can be
made to be interchangable to some degree.  I use the python orchestra
library for all of my pieces and they have use a standardized 8 pfield
plus extra optional pfields signatures (instrID, start, dur, pch1,
pch2, ampInDb, space, articulation [optional fields]).  Standardizing
on a set signature has allowed for interchangability for the most part
for me, though the signature and features I have used are tailored for
what I require in my pieces.  Not sure if this will apply to everyone
else's needs though.

As for auditioning instruments, still haven't figure it out.  I will
try to get back on this after tonight's BACSUG meeting.

Hope this helps!
steven



On 4/15/05, Francisco Vila <fra...@hi...> wrote:
> El vie, 15 de abr de 2005, a las 05:56:35 -0700, Michael Bechard dijo:
> > Yeah, I was thinking of the same issues yesterday.
> > Along with what you wrote, there are possible table
> > conflict issues as well. i.e. project A has a sine
> > wave for table 1 while project B has a square wave.
>=20
> In general, the issue with Csound is that even the simplest
> instruments are not interchangeable at all.
>=20
> So, the instrument seems to be a inherent property of the score and
> not only a number in p1.
>=20
> --
> Francisco Vila Doncel. Badajoz (Spain)
> http://www.paconet.org
>=20
>=20
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick
> _______________________________________________
> Bluemusic-users mailing list
> Blu...@li...
> https://lists.sourceforge.net/lists/listinfo/bluemusic-users
>