On Fri, Apr 24, 2009 at 3:55 AM, Scott Wilson <
s.d.wilson.1@...> wrote:
> Making audio busses mappable definitely makes the existing semantics murkier
> if we're going to allow integers in map. So I think we have two choices:
> Either we go back to the idea of separate mapa method, or do as James
> suggests below and just make it crystal clear that ints always become
> control busses.
Third option for the future:
Part of the SynthDef refactoring could be to retain metadata in memory
for EVERY synthdef (without having to explicitly store them in the
SynthDescLib). Then we would know the rate for each control name. If
the integer is associated with an AudioControl, map it as audio etc.
SynthDesc probably doesn't (yet) track controlname rates. It should.
Probably too late to do that for 3.3.
The typical throwaway use of SynthDefs in the client (by which I mean,
build>send>garbage collect) imposes some limitations that would not be
issues if the client retained more intelligence about the available
defs.
Josh's comment:
>This wouldn't work. Even if there is an AudioControl as a SynthDefs arg, you can still map a control bus to it (and the values are linearly interpolated for you).
Cross-mapping buses could be considered a special case. The assumption
would be, if you give an integer bus number and no other information,
then match the rate. If you want to map a kr bus to an ar input, you
need to be explicit about it.
hjh
--
James Harkins /// dewdrop world
jamshark70@...
http://www.dewdrop-world.net"Come said the Muse,
Sing me a song no poet has yet chanted,
Sing me the universal." -- Whitman
_______________________________________________
sc-dev mailing list
info (subscription, etc.):
http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtmlarchive:
http://www.listarc.bham.ac.uk/marchives/sc-dev/search:
http://www.listarc.bham.ac.uk/lists/sc-dev/search/
