[RWP] Tiny Baby Steps

[Indigo]

Jim, I don't think there are capchas anywhere in the Cockos forums.
I usually don't log in, just google with a few words expressing my 
problem then scan the forums for answers.
I only joined the forums to ask about a problem that I eventually solved 
on my own.
There's a user handle and password for log in, that's all unless capcha 
has been added recently.
I don't think I could do justice in wording your question, or I'd 
volunteer to ask on the forums.
What is it, do you need to know how speech was added to Ivan's custom 
actions that begin with Say?
I'm just guessing, but maybe it's only required to peek into those Say 
actions and borrow the lines related to Say.
Is that de compiling, I don't even know, so I'm not guilty of de 
compiling; but I confess to renaming jaws scripts as .txt to lift the 
screen coordinates from them.
Is something as simple as renaming to text  also possible with .py files?
Thanks,
Indi

On 6/13/2013 10:08 PM, Jim Snowbarger wrote:
> Alex,
> Yes,  you can run any combination of reaper actions, like the ones you
> see in the f4 list, including the SWS actions.  Chain them together
> until the cows come home.
> Plus there are other things you can call that return values.  I don't
> know much about the complete list of things you can do yet.   But, that
> list exists somewhere.  I borrowed from an example.
> What I wanted to do was to modify the track volume by 1 db, rather than
> the stupid .05 db nudges.
> So, what I will need to do is find the companion call that sets the
> track volume.  Then, I can read it,  add a certain amount to it,, then
> write it back to the parameter.  I'll write an almost identical script
> to subtract.
> All that should be manageable.  And, I would think would be applicable
> to any parameter.
> But, just as with the hundreds and hundreds of reaper actions, the
> secret lies in finding that complete list of  API calls, and deciding
> what you want to do.
> But, Most things like that dont' require speech output.  I was also
> thinking that we might be able to get things to speak that don't
> presently speak, or at least, don't speak correctly.  That part requires
> speech output, which is the current hang up.   I might have to venture
> into the dreaded Cockos Forums, which is not a place I really want to
> go, just to find a Reaper Python guru who can help solve the problem.
> I'll probably get hit straight in the face with some stupid CAPTCHA that
> I can't solve and be blown totally out of the water.  Those things are
> horrible obstacles for half deaf people like me.
>
> BTW, what happened to my guy who was going to add NVDA-independent
> speech to HotSpotKnockoff.
>
>
> ----- Original Message ----- From: "Alex H." <linuxx64.bashsh at gmail.com>
> To: "Reapers Without Peepers" <rwp at reaaccess.com>
> Sent: Wednesday, June 12, 2013 11:40 PM
> Subject: Re: [RWP] Tiny Baby Steps
>
>
>> Hahaha. Well, there's at least one guy who can interface with nvda
>> controller client, as he did the hotspot knockoff mods for speech
>> output.
>>
>> I know this is entirely pipedream/fantasizing at this stage, but does
>> ReaScript allow any effect param to be changed? I imagine there's IDs
>> that get mapped to effects and their parameters, and then you'd have
>> to figure out how much to change the value. Speaking in very
>> simplified terms of course, but is that kinda what's gotta happen?
>>
>> Man, if we can get speech output, it's pretty much possible, or at
>> least I think so, that we could fill in the gaps where reaAccess is
>> breaking or falling short using reaScript.
>>
>> Encouraging even if it is tiny.
>> Thanks,
>>
>> Alex
>>
>> On 6/12/13, Jim Snowbarger <Snowman at snowmanradio.com> wrote:
>>> Oh man, what a quest, pulling hairs from wherever they grow.And some
>>> where
>>> they don't.
>>> But, I finally got a ReaScript to run in python.  It's kind of a pain
>>> to get
>>>
>>> this set up.  And, I'm gathering the files and steps needed, so I can
>>> consolidate for you.
>>> I'm excited to have achieved  the smallest of steps, but it's a
>>> glimmer of
>>> hope.
>>> I can actually now press a hot key that runs a  script, that writes the
>>> track pan and volume to a file.
>>> Yep, totally useless, I know.  But, it's abreak through.
>>> I have found the interface to speak it through SAPI, and it works in
>>> stand
>>> alone python. but there is some conflict when I marry that up with
>>> reaper,
>>> still looking into that.
>>> If anybody knows anything about this stuff, and can help me get screen
>>> reader independent speech output from a Python script, in the reaper
>>> environment, speak up.
>>> Once I get that part working, then I'll have a frame work that we can
>>> modify
>>>
>>> to add our own action and api calls to do stuff.
>>> I think I have engendered every error message python can generate.
>>> I feel like I'm eating an elephant.  Drinking at a fire hose.  Riding a
>>> tiger.
>>>
>>>
>>
>> _______________________________________________
>> RWP mailing list
>> RWP at reaaccess.com
>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>>
>
>
>
> _______________________________________________
> RWP mailing list
> RWP at reaaccess.com
> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com