[Ardour-Dev] gain-mapping - was Re: OSC next

Melanie Bernkopf melaniebernkopf at gmail.com
Thu May 19 10:17:44 PDT 2016

Bigger is better in that case.

Meters are done with led matrixes with either shift registers going over
fets or transistors to drive a led or whatever or dedicated drivers for
them. If for example a meter has 16 led I would take a MAX7221 which would
give ma total of 64 led´s makes 4 meters so for 32 channels it would take 8
of these. The dump controller actually could do 16 with 800 refreshes per
second but if you don´t send enough data for the matrix it would not do
anything. The value to gain is actually predefined fixed number of led
known gain that can come in so just shift out.

7 segment displays are nothing more than that before so same thing number
is known comes in and shit it out.

Also in these cases predefined could be better than some other way.

For prototyping this I would take an Arduino micro just because it is

2016-05-18 22:21 GMT+02:00 Len Ovens <len at ovenwerks.net>:

> On Wed, 18 May 2016, Felix Homann wrote:
> Len Ovens <len at ovenwerks.net> schrieb am Mi., 18. Mai 2016 um 20:30 Uhr:
>>       On Wed, 18 May 2016, Felix Homann wrote:
>>       >       On Sat, 14 May 2016, Felix Homann wrote:
>>       >
>>       >
>>       >       I like the: send any message with no value means send me an
>>       update.
>>       Does this include meter values, timecode values or beat/bar values?
>> No, for meter values you send a subscription message to the mixer. You can
>> subscribe to a couple of different predefined sets of meter values. You
>> have to
>> refresh that subscription every 8 seconds or so. Meter values are send as
>> blobs
>> containing up to 100 values (that's for the RTA).
> Yuck. Predefined... ok, I do that effectively. You get the bank you have
> set. This could be costly if you have banksize 0 (infinite) and a whole lot
> of tracks, but with a whole lot of tracks, banking just makes more sense.
> (Len reminds self some surfaces would prefer to go to bank starting at
> rather than next/last) Lots of refreshes is not nice for dumb surfaces
> where metering will be turned on manually or at surface start and expected
> to be there till shutdown or bank change. (or turned off) Blobs of even 8
> values (more useful size) are not so easy to spread out to meters on a dumb
> surface even though they are less traffic.
> All of these always on feedback types will need a timer. We can't send a
> meter value for every sample or every meter calc I think. (same with
> TC/bars)
> --
> Len Ovens
> www.ovenwerks.net
> _______________________________________________
> ardour-dev mailing list
> ardour-dev at lists.ardour.org
> http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ardour.org/pipermail/ardour-dev-ardour.org/attachments/20160519/245c22a9/attachment-0001.htm>

More information about the Ardour-Dev mailing list