Hi Sean,
Exciting times indeed. To answer stefan’s smaller picture question, however, 
plug-in parameters are assigned to any control surface via a plug-in map. There 
are default maps for all supported control surfaces. Thus far, one has to make 
note of which parameters are assigned to each encoder knob or fader. Usually, 
one creates a text file of some sort to have a reference. There are a couple of 
things in the works that will eliminate this need. One solution is long-term 
and might be available perhaps next year. A different solution will be 
available shortly. Stay tuned to the list.
Best,
Slau

> On Oct 13, 2016, at 9:23 AM, Sean A. Cummins <seanacumm...@gmail.com> wrote:
> 
> Hi Slau and Listers,
> 
> Thus far the S3 is tightly integrated with Pro Tools.  That being
> said, the navigation using the S3 is the same as using a keyboard and
> track pad, but all in one place.  If Pro Tools talks with either of
> those devices, you will be satisfied using an S3.  But as far as any
> greater level of verbalization for plug-ins, that will have to be
> accomplished via either EuCon presenting the data for Voiceover to see
> directly, or a third party programmer creating an interface
> application that would allow us to custom define control code being
> passed back and forth from software and hardware.
> 
> There is exciting hope in both of these regards, but I am not the one
> to speak to these possibilities.  I myself have been quietly
> advocating for over 3 decades to both hardware and software
> manufacturers for greater access in the digital audio work field, and
> it’s the usual, 2 steps forward, 1 back,  three steps forward and 2
> back etc. etc.
> 
> However, I’d like to take this moment to encourage all DAW and control
> surface users, and future users, to understand that the HUI and Mackie
> protocols have a defined half-life, and will be phased out in the not
> too distance future as stated by the companies in the industry.  Many
> control surfaces such as the SSL Nucleus, S3, S6 and the list could go
> on, are already designed to utilize the EuCon protocol.  Therefore,
> many of your investments will not be lost and quickly become obsolete
> if they support the EuCon protocol.  EuCon is currently the most
> robust as far as system integration and is the future of many
> peripheral devices such as the new Avid MTRX I? O, and supported mic
> preamps like the Neve 4081.  The Neve 4081will allow for direct
> control of the preamps via EuCon directly from Pro Tools channel
> strips.  Won’t that be awesome if and when we can see and hear these
> controls from within the DAW?
> 
> All this to say, there can be more and more universal access if indeed
> EuCon is to become accessible just as Avid, Ilok and even Native
> Instruments have graciously implemented to date.
> 
> The big picture here for everyone to understand, if we are to gain
> this level of accessibility, a visually impaired person will be able
> to compete in the workforce with technology that is already in a
> worksite.  A potential employer would not have to purchase any
> additional and costly access technology in order to hire a visually
> impaired person.  It will all be present in the Mac operating system,
> DAW software, and the hardware supported by EuCon.
> 
> FYI, even Sonar 8.0 and the Tascam 1884 supported EuCon going back
> years ago!  Grin!
> 
> Take Care,
> 
> Sean
> 
> 
> 
> On 10/12/16, Slau Halatyn <slauhala...@gmail.com> wrote:
>> I’ll let Sean answer this as he’s an S3 user.
>> 
>>> On Oct 12, 2016, at 9:06 AM, Stefan Albertshauser <orgelste...@icloud.com>
>>> wrote:
>>> 
>>> Hi,
>>> 
>>> Does anyone have experience with the Avid S3? How do you deal with the
>>> assignment of plugin parameters? Do you have to make a chart for every
>>> plugin?
>>> 
>>> Thanks for an answer.
>>> 
>>> Best Stefan
>>> 
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to ptaccess+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>> 
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to