Hi Chris!
Do you already know if nexus and sylenth vsts works for blind users?
I install sylenth but just have one sound in the sound banc... I don't
understand why
Cheers
Daniel
--------------------------------------------------
From: "Chris Belle" <[email protected]>
Sent: Tuesday, July 19, 2011 9:00 PM
To: "JSonar -- JAWS Scripts for Sonar discussion list" <[email protected]>
Subject: Re: [Jsonar] Working with Sonar X1
hey Pete,
I'm working with x1 and window-eyes, and you can get more track inspector
stuff to show up if you click on some of the track tabs, it's similar to
the inspector in sonar 8.5 where you show and hide stuff with display and
modules options, but they're named a bit different in x1.
it's been a while, but I was able to get 4 parameters to show up, and even
better, 4 per track as I arowed down, didn't have to go to a menu to go to
another track.
But this behavior wasn't always reliable.
But with window-eyes, there is basic access with no scripts.
I realize we are speaking oranges and apples here in a way, but hope this
helps, I'll go back in and see if I can repeat my steps and tell you more
accurately what i did.
C
At 12:58 PM 7/19/2011, you wrote:
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_007A_01CC461B.F088A4D0"
Content-Language: en-us
Just wondering if anyone else has much experience working with Sonar X1.
I'm thinking about trying to modify the JSonar scripts to capture some of
the lost functionality in X1 but don't know what others might be doing
here.
Although some things obviously work, there is a lot that doesn't and a
bunch of UI changes. In particular, I can't seem to read anything when
the Track Inspector comes up (even using the JAWS cursor), in a new
project, many of the track fields are missing in the default template
(such as "input", "output", etc.). Presumably some of these fields can be
hidden or shown by going to the Track control manager, but there doesn't
seem to be a simple way of getting there.
We might be able to script the Control Tool bar pretty easily, but I haven't
done that yet.
Anyway, I thought it would be nice to follow the progress of Sonar if we
could so that we could take advantage of new functions and utilities as
they are added in the future, but I'm not sure where everyone wants to go
with this and don't want to duplicate or crash into work someone else
might be doing.
I did put a section in the SonarGlobals.jsl file to account for window
classes and ID's that might be specific to Sonar X1 so that we can
(hopefully) work off the same scripts, but I haven't gotten around to
putting in any custom values - just a skeleton for now.
So, what thoughts do people have?
--Pete
Check out ViewPoints
A weekly, half hour radio program for people living with low vision
Find out more about the show and links to the podcasts at:
<http://www.ViewPoints.torpey.info>www.ViewPoints.torpey.info
Send suggestions or comments to:
<mailto:[email protected]>[email protected]
_______________________________________________
Find JSonar and Sonar FAQs, articles, guides and downloads at jsonar.org.
Jsonar mailing list
[email protected]
http://jsonar.org/mailman/listinfo/jsonar_jsonar.org
For all your audio production needs and technology training, visit us at
www.affordablestudioservices.com
or contact
Chris Belle
[email protected]
or
Stephie Belle
[email protected]
for customized web design
_______________________________________________
Find JSonar and Sonar FAQs, articles, guides and downloads at jsonar.org.
Jsonar mailing list
[email protected]
http://jsonar.org/mailman/listinfo/jsonar_jsonar.org
_______________________________________________
Find JSonar and Sonar FAQs, articles, guides and downloads at jsonar.org.
Jsonar mailing list
[email protected]
http://jsonar.org/mailman/listinfo/jsonar_jsonar.org
