[sonarblindbeta] Re: Sonar blind control surface progress

  • From: Steve Matzura <number6@xxxxxxxxxxxxxx>
  • To: sonarblindbeta@xxxxxxxxxxxxx
  • Date: Tue, 19 May 2015 23:40:15 -0400

That's what I figured, but I never thought of that concept as being
applicable to automation. I suppose anything *could* be that's not
just an on-or-off choice, yes.

On Mon, 18 May 2015 21:19:07 -0500, you wrote:

Think of a volume or pan change associated with a bus instead of a track.
People who can see. Can't look at the arc of this volume or pan change. That
is an automation shape. Whether it's on a bus or a track.

Sent from my iPhone

On May 18, 2015, at 9:08 PM, Steve Matzura <number6@xxxxxxxxxxxxxx> wrote:

Pardon my ignorance, but what's a bus automation shape?

On Mon, 18 May 2015 08:55:13 -0500, you wrote:

Forgot to ask one thing. Will you be able to edit MIDI events using the
event list? Also, will it be possible to edit bus automation shapes?
Previously, the only automation events we even could find would be in the
event list for individual tracks. If you found such an event you could move
it in time but could not edit it per se. With respect to bus automation,
you couldn't even find it. You could simply remove via the undo command.
The ability to have greater control over event automation and bus
automation shapes would really be cool.

Sent from my iPhone

On May 18, 2015, at 8:17 AM, John Martyn DoItBlind <John@xxxxxxxxxxxxx>
wrote:

Hi all,
As you know I’ve been putting in long hours figuring out this C++ stuff.
On the final two files which are the critical part of this, I’ve had to
start over 3 times to get it right. Converting things from c code to c++
is not easy and to maintain the code integrity is extremely difficult to
do. I’m about 70% complete on the last two files. The code is very complex
and was structured in a way that made certain things impossible and I’ve
had to create my own code to deal with the issues. This week should be
good and I hope to finish before Friday. If you’d like to know, you can
control the synths through this thing. You know what this means? You won’t
have to fiddle with knobs, sliders, buttons, etc in the plugin window
anymore. You’ll do it through a list. Technically this should work as I’ve
seen the code and see what it can do so this is just the solution we were
looking for. Mixed with the UIA these languages put together in natively
working environments are going to put to rest
a
lot of accessibility concerns. What this control surface can do is far
beyond how it was used in the past so this should be interesting to see.
Mixed with HSC, UIA, control surface in native C++, and using the com API
this thing is going to be a beast of a program. More to come….
John



Other related posts: