On Wed, Nov 11, 2009 at 10:32:40PM +0100, Karl Hammar
wrote:
[ about OSC ]
One problem
though, one has to define the semantics och the data send.
- Can someone point to some wellrocognized doc for that?
- What are the conventions?
OSC info, including specs, is here:
http://opensoundcontrol.org/
Oh, I wasn't specific enough. It ([1,2]) only defines the "on the
wire" format. For it to be useful the "OSC Address Patterns" mapping
to real controls must be defined.
So what is the consensus among the applications, is it e.g. "/mixer/1/
volume", "/mixer/a/vol", or what?
I suggested it for control/status data, i.e. to
configure the sound
card, choose sample rates and channel configurations, etc. It's used
by some Linux softsynths to communicate with their GUIs.
Yes, since it is supported by the applications, it seems to be
something we must have. And it should not take much to make it work.
I would not suggest OSC for shuffling ADC data back
and forth. For
that, either NetJack or some lightweight homegrown int/longint-based
protocol would be better.
No, I didn't think so either.
I am very excited to see so much progress on this.
That ATMEL dev
board also seems like a fast way to get something up and running.
Yes it is, but the processor on the cheap (~80USD) AT32NGW100 [3] is
AT32AP7000 [4], which has a BGA [5] package only, which puts it out
of the home hw hacker domain (special equipment is required to solder
it).
Regards,
/Karl
[1]
http://opensoundcontrol.org/spec-1_0
[2]
http://cnmat.berkeley.edu/system/files/attachments/Nime09OSCfinal.pdf
[3]
http://www.atmel.com/dyn/products/tools_card.asp?tool_id=4102
[4]
http://www.atmel.com/dyn/products/product_card.asp?part_id=3903
[5]
http://en.wikipedia.org/wiki/Ball_grid_array
-----------------------------------------------------------------------
Karl Hammar Aspö Data karl(a)aspodata.se
Lilla Aspö 148 Networks
S-742 94 Östhammar +46 173 140 57 Computers
Sweden +46 70 511 97 84 Consulting
-----------------------------------------------------------------------