[RWP] Recording inputs menu, meter readings, and contacting Reaper developers

[Chris Belle]

I think I got it to work once by moving the relevant accessibility files 
manually to different folders,
which is the way you have to do it if you want to install 32 bit reaper 
on a 64 bit os anyway.
   can't remember, I've slept since then on window-eyes particulars.

But I tend to use 32 bit versions even in a 64 bit environment, for 
running older plug-ins better,
and more compatibility
and more compatibility, there still isn't 64 bit replacements for some 
really good plugs out there, and especially for us with the nature of 
accessibility there's no real gain to go 64 bit unless you are running 
huge sample libraries that need the extra ram and even then with good 
disk streaming, it's not an issue.

64 bit is indeed technically better on principal, but you know how it 
goes in the real world.


On 8/5/2014 3:12 AM, Chris Belle wrote:
> Window-eyes has issues with 64 bit reaper.
>
>
> On 8/5/2014 2:58 AM, RoadRunner wrote:
>> it's really weird! Whenever I press alt P, it just says Ripple, 
>> Ripple, Ripple, I don't understand what could be going on. When I 
>> switched to window eyes, reaper doesn't even open. It's just crashes.
>>
>> Sent from my iPhone
>>
>>> On Aug 5, 2014, at 2:50 AM, Scott Chesworth 
>>> <scottchesworth at gmail.com> wrote:
>>>
>>> Same. Used an insane number of different Reaper installations on
>>> different systems with different versions of different screen readers
>>> here over the years, and I can honestly say I've never seen this
>>> behaviour yet. How weird!
>>>
>>> For what it's worth, the other way of toggling ripple editing lives in
>>> the Options menu. Not ideal, but that should still work.
>>>
>>> Scott
>>>
>>>> On 8/5/14, Jim Snowbarger <Snowman at snowmanradio.com> wrote:
>>>> I have several versions of jaws running with reaper here, and have no
>>>> problems hearing the state of this toggle with any of them. And, I 
>>>> think
>>>> this is a ReAccess function, not a screen reader function. And no 
>>>> scripts
>>>>
>>>> are required  for that keystroke to work.
>>>> So, something else is going on here.
>>>>
>>>>
>>>> ----- Original Message -----
>>>> From: "TheOreoMonster" <TheOreoMonster at reaperacc.es>
>>>> To: "Reapers Without Peepers" <rwp at reaaccess.com>
>>>> Sent: Monday, August 04, 2014 7:20 PM
>>>> Subject: Re: [RWP] Recording inputs menu, meter readings,and 
>>>> contacting
>>>> Reaper developers
>>>>
>>>>
>>>>> are there verbosity settings for ReaAccess? Maybe those need to be
>>>>> adjusted. Otherwise it may just be a difference in how the different
>>>>> screen readers relate the i nfo ReaAccess Feeds them. In which 
>>>>> case you
>>>>> may want to switch to NVDA when using reaper or just Use the menu 
>>>>> to see
>>>>> what ripple state is current and remember the order as you cycle.
>>>>>
>>>>>> On Aug 4, 2014, at 3:51 PM, RoadRunner <emccullough1 at nyc.rr.com> 
>>>>>> wrote:
>>>>>>
>>>>>> i've tried that keystroke using jaws 12 and Charles 14 and it still
>>>>>> doesn't announce the different states of ripple editing
>>>>>>
>>>>>> Sent from my iPhone
>>>>>>
>> _______________________________________________
>> 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
>