[RWP] Windoweyes Still Can't Run Reaper 64

Tue Jul 3 10:58:04 EDT 2012

it's a dll called Reaper-Access , located in the Reaper (or Reaper x64) 
folder , in the plugins subdirectory.
hope this helps
Roy.
http://elephant-dolphin.bandcamp.com
----- Original Message ----- 
From: "Indigo" <33indigo at charter.net>
To: "Reapers Without Peepers" <rwp at reaaccess.com>
Sent: Tuesday, July 03, 2012 4:48 PM
Subject: Re: [RWP] Windoweyes Still Can't Run Reaper 64


> Patrick, when you say you copied all the 32 bit files necessary for 
> ReaAccess to work, can you list what those files are
>
> Last night I noticed that when I open Reaper with NVDA, there is a single 
> file called Reaper X64 running in Windows Task Manager, but when I open 
> Reaper with Wineyes there are two files running in Windows Task Manager: 
> Reaper 1 and Reaper 2.
> When opened by NVDA, the task manager entry says Reaper x64, but when 
> opened by Windoweyes neither of the 2 entries say x64.
>
> Some interaction of Wineyes Win7 and ReaAccess is opening 2 files, or 
> maybe it's an erroneous display in Windows Task Manager.
> I tried the usual method in Task Manager of ending one of the files, but 
> only succeeded in exiting Reaper.
> I changed a few cursorrrrr settings in Wineyes, thinking there's a setting 
> that might open Reaper with only a single instance running, no luck so 
> far.
>
> The fact that Wineyes can run Reaper 64 just fine, as long as ReaAccess is 
> not installed, must indicate it's not a problem of how Wineyes opens 
> Reaper, but some interaction between Wineyes and ReaAccess that doesn't 
> occur in 32 bits.
> I tried to locate an actual reaAccess.exe to run Win7's troubleshoot 
> compatibility mode on it, but can't find reaAccess.exe.
>
> I feel that the clue will be there, by comparing what is there in the 
> Reaper folder in Program Files; with and without ReaAccess installed; and 
> comparing what NVDA is doing with those files compared to what Wineyes is 
> doing with them.
> This level of computer science is a mystery to me, though; I'll defer to 
> you and Roy to hopefully discover something that will solve this.
>
> I notice in Reaper's installed data .ini file, whatever its proper title 
> is, there is an entry Reaper 32 host equals 1, as well as Reaper 64 Host 
> equals 1.
> I think I'll change that 1 for a zero on the 32 host entry, and see what 
> happens.
>  Indigo L
>
> On 7/3/2012 12:34 AM, Patrick Perdue wrote:
>> I believe ReaAccess uses the same files regardless of if you're running
>> 32 or 64-bit Reaper. If you install the 64-bit version of Reaper on a
>> 64-bit system, it will install properly. If, however, you install a
>> 32-bit version of Reaper on a 64-bit system, where that is the only
>> installed version of Reaper, the ReaAccess installer will look for a
>> 64-bit Reaper that doesn't exist, complain loudly, and not work at all.
>> If you have both the 32 and 64-bit Reaper installed, ReaAccess may only
>> work with the 64-bit version by default.
>>
>> I use the 32-bit version of Reaper on my 64-bit system to have access to
>> some old 32-bit DirectX plugins, which don't show up on any 64-bit DAW.
>> 32-bit bridging only works with VST plugins, not DirectX ones. I also
>> have the 64-bit version installed. However, to make Reaper32 and
>> ReaAccess play nice together on the two Windows 7 64 systems I put it
>> on, I had to copy all the files necessary for ReaAccess to work from
>> another working 32-bit Reaper directory, which was installed on a
>> Windows XP machine.
>>
>> On 7/2/2012 10:37 PM, Indigo wrote:
>>> You're right, I should insert several tracks, to be sure the method
>>> works in Windows 7 with NVDA.
>>> However, it's the same method I've been using with Wineyes 6.1 in XP,
>>> and there it always changes track properties for the selected track.
>>>
>>> meanwhile, I think I found a possible clue as to what's different when
>>> Reaper is opened with Wineyes as opposed to being opened with NVDA.
>>>
>>> If I start Reaper with NVDA, then press ctrl+shift+escape to open the
>>> Windows task manager, in the applications list I find Reaper X64 
>>> running.
>>>
>>> But, if i open Reaper with Windoweyes, it locks up, and in the Windows
>>> Task Manager there are 2 instances of Reaper shown as running.
>>>
>>> I tried ending one of the instances with E button, but only the top
>>> Reaper running 1 would close, no response when I tried closing Reaper
>>> running 2.
>>>
>>> I have no idea how two instances could show when Wineyes opens Reaper,
>>> and only one when NVDA opens it, but maybe it's a clue as to what's
>>> going on.
>>> You know, Reaper opens just fine in Win7 64 with ReaAccess not
>>> installed, so it's something going on between Wineyes and ReaAccess, but
>>> only in Win7 64.
>>> Is there a special 64 bit version of ReaAccess, or only the one version?
>>>
>>> I tried to find the .exe file for ReaAccess, in hopes of running windows
>>> 7's troubleshoot compatibility on it; but couldn't find anything called
>>> reaAccess.exe.
>>> Indigo L
>>>
>>> On 7/2/2012 7:26 PM, Roy Shtupler wrote:
>>>> this method really works.
>>>> if however , you have multiple tracks in a project , there might be a
>>>> difference between what you're told , and which track actually got
>>>> altered.
>>>> e.g insert 3 or 4 tracks.
>>>> change something in the first track e.g record mode , input , etc.
>>>> now , go down to another track and try the same method; do you still 
>>>> get
>>>> a report on which track's properties got altered?
>>>> thanks a bunch
>>>> Roy.
>>>> http://elephant-dolphin.bandcamp.com
>>>> ----- Original Message ----- From: "Indigo" <33indigo at charter.net>
>>>> To: "Reapers Without Peepers" <rwp at reaaccess.com>
>>>> Sent: Tuesday, July 03, 2012 1:58 AM
>>>> Subject: Re: [RWP] Windoweyes Still Can't Run Reaper 64
>>>>
>>>>
>>>>> Roy, I just looked at Reaper 4.22 again with NVDA.
>>>>> I inserted an empty track, armed it, pressed ctrl+up arrow to make the
>>>>> applications menu display.
>>>>> Then i selected the item with ctrl+shift+right arrow, even there was
>>>>> no actual item, then pressed the applications key, then down arrowed
>>>>> quickly.
>>>>> I got the correct track options menu that begins Monitor input M.
>>>>> You can arrow down to click on monitor input midi, or monitor input
>>>>> audio.
>>>>> You can also select stereo there, instead of the default mono
>>>>> recording, plus many other track options not offered in ReaAccess from
>>>>> the tab key.
>>>>>
>>>>> i find that if I don't do that little nonsense step of selecting the
>>>>> non existent item; when I press the applications key and down arrow; I
>>>>> get another menu that begins with Jump to Marker J
>>>>> Once the monitorr input M menu displays, it displays every time after
>>>>> that, no problem.
>>>>> This behaveor is exactly the same for me in NVDA or Wineyes; any later
>>>>> Reaper version; in XP or Win7 64.
>>>>> Indigo L.
>>>>>
>>>>>
>>>>> On 7/2/2012 3:37 PM, Roy Shtupler wrote:
>>>>>> I suspect yes , maybe it's a tiny little fix , but we don't have the
>>>>>> source code , and the developers vanished for some odd reason.
>>>>>> well ... on to learning Python and re-writing ReaAccess.
>>>>>> best
>>>>>> Roy.
>>>>>> http://elephant-dolphin.bandcamp.com
>>>>>> ----- Original Message ----- From: "Patrick Perdue"
>>>>>> <patrick at pdaudio.net>
>>>>>> To: "Reapers Without Peepers" <rwp at reaaccess.com>
>>>>>> Sent: Monday, July 02, 2012 1:46 AM
>>>>>> Subject: Re: [RWP] Windoweyes Still Can't Run Reaper 64
>>>>>>
>>>>>>
>>>>>>> I can get to that from the track context menu. Is this now broken
>>>>>>> with
>>>>>>> later versions of reaper? This is actually the main reason I am 
>>>>>>> still
>>>>>>> using 3.7.x.
>>>>>>> On 7/1/2012 6:29 PM, Roy Shtupler wrote:
>>>>>>>> for instance , the button that , when right-clicked on , brings the
>>>>>>>> menu
>>>>>>>> that assigns a track to a particular input; either midi or audio.
>>>>>>>> best
>>>>>>>> Roy.
>>>>>>>> http://elephant-dolphin.bandcamp.com
>>>>>>>> ----- Original Message ----- From: "Indigo" <33indigo at charter.net>
>>>>>>>> To: "Reapers Without Peepers" <rwp at reaaccess.com>
>>>>>>>> Sent: Sunday, July 01, 2012 11:34 PM
>>>>>>>> Subject: Re: [RWP] Windoweyes Still Can't Run Reaper 64
>>>>>>>>
>>>>>>>>
>>>>>>>>> A while back; just to understand if; and how; it could be done, I
>>>>>>>>> installed a fresh copy of Reaper 4X plus ReaAccess, then assigned
>>>>>>>>> the
>>>>>>>>> audio and midi interface settings, plus tried as many usual
>>>>>>>>> actions as
>>>>>>>>> I could think of, all with NVDA, and found work arounds for
>>>>>>>>> everything.
>>>>>>>>> The part that concerned me was getting the midi portss enabled,
>>>>>>>>> which
>>>>>>>>> ; when I did them in Wineyes and Jaws; required Wineyes mouse
>>>>>>>>> pointer/jaws PC cursor moves at the numPad, but a little
>>>>>>>>> experimentation with NVDA +flat review, move to focus, move
>>>>>>>>> navigator
>>>>>>>>> object to mouse, and I got all midi ports enabled with NVDA.
>>>>>>>>> I don't remember trying NVDA in Reaper's IO dialog, but I can't
>>>>>>>>> think
>>>>>>>>> of anything in there that NVDA can't accomplish.
>>>>>>>>> Right click menus seem very similar to what I get with Wineyes.
>>>>>>>>>
>>>>>>>>> I still have Reaper 4.22 on this Win7 64 machine, so if you want
>>>>>>>>> me to
>>>>>>>>> try some particular move with NVDA, let me know.
>>>>>>>>>
>>>>>>>>> I'll go to the midi editor and see if it's as easy to edit midi
>>>>>>>>> events as with Wineyes.
>>>>>>>>> If NVDA will do your midi quantization work arounds; Roy, I think
>>>>>>>>> nothing is lacking.
>>>>>>>>> I was going to uninstall Reaper, from this computer; since it's
>>>>>>>>> totally impossible to run with Wineyes 7.5.22.
>>>>>>>>> I prefer Wineyes 6.1 to NVDA; in my XP daw; because I like to
>>>>>>>>> look at
>>>>>>>>> the whole screen with wineyes num pad navigation keys, and feel
>>>>>>>>> half
>>>>>>>>> blinded by NVDA's lack of the same entire screen review facility.
>>>>>>>>> I don't doubt that very skilled NVDA user can find anything on a
>>>>>>>>> screen, it just frustrates me to get only bits and pieces; here 
>>>>>>>>> and
>>>>>>>>> there; with various shortcuts; instead of the entire screen all at
>>>>>>>>> once.
>>>>>>>>> If NVDA ever gets easy screen navigation at the number pad, look
>>>>>>>>> out
>>>>>>>>> Jaws and Window-Eyes.
>>>>>>>>> My greatest frustration with NVDA lately is; on Win7; that it
>>>>>>>>> doesn't
>>>>>>>>> pop up Win7's U A C dialog for me.
>>>>>>>>> Instead it goes silent.
>>>>>>>>> I have poked around with the spacebar and pressing Y for yes, and
>>>>>>>>> actually got programs to run, but it's just guessing; no
>>>>>>>>> confirmation
>>>>>>>>> speech during the U A C dialog.
>>>>>>>>> Indigo L
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 7/1/2012 11:17 AM, Patrick Perdue wrote:
>>>>>>>>>> I haven't actually needed to access those controls in that way,
>>>>>>>>>> since
>>>>>>>>>> I can do all that through ReaAccess. I am still using Reaper
>>>>>>>>>> 3.7.x by
>>>>>>>>>> choice. Maybe things are different now, not sure.
>>>>>>>>>> Case in point though. NVDA sometimes won't see stuff like that,
>>>>>>>>>> but
>>>>>>>>>> it reads the Izotope RX stand-alone stuff better than System
>>>>>>>>>> Access
>>>>>>>>>> does, or Jaws, for that matter.
>>>>>>>>>>
>>>>>>>>>> This entire discussion is kind of ironic, since all but one of 
>>>>>>>>>> the
>>>>>>>>>> SeroTalk podcasts are produced with Reaper... using NVDA. Oops!
>>>>>>>>>>
>>>>>>>>>> On Jul 1, 2012, at 10:08 AM, Roy wrote:
>>>>>>>>>>
>>>>>>>>>>> hi Patrick
>>>>>>>>>>> do you succeed in reading and right-clicking all the track
>>>>>>>>>>> control
>>>>>>>>>>> panel buttons using NVDA? e.g the i/o button , monitoring etc;
>>>>>>>>>>> these
>>>>>>>>>>> seem to read just with System Access's virtual mouse mode.
>>>>>>>>>>> cheers
>>>>>>>>>>> Roy.
>>>>>>>>>>> -----Original Message----- From: Patrick Perdue
>>>>>>>>>>> Sent: Sunday, July 01, 2012 4:54 PM
>>>>>>>>>>> To: Reapers Without Peepers
>>>>>>>>>>> Subject: Re: [RWP] Windoweyes Still Can't Run Reaper 64
>>>>>>>>>>>
>>>>>>>>>>> Yep, System Access does, indeed, work fine with ReaAccess. It
>>>>>>>>>>> uses
>>>>>>>>>>> the same API NVDA does. I prefer using it with NVDA though, as 
>>>>>>>>>>> it
>>>>>>>>>>> reads some of the plugin interfaces a bit better than System
>>>>>>>>>>> Access
>>>>>>>>>>> does. Functionality is basically the same with all the stock
>>>>>>>>>>> Reaper
>>>>>>>>>>> stuff.
>>>>>>>>>>> But, as is always the case, SA occasionally gets things that 
>>>>>>>>>>> NVDA
>>>>>>>>>>> misses, and the other way around.
>>>>>>>>>>> It hasn't been a one screenreader world for a while now.
>>>>>>>>>>>
>>>>>>>>>>> On Jul 1, 2012, at 9:41 AM, Roy wrote:
>>>>>>>>>>>
>>>>>>>>>>>> yeh , system access works with no problems also on 64-bit with
>>>>>>>>>>>> Reaper 64-bit.
>>>>>>>>>>>> cheers
>>>>>>>>>>>> Roy.
>>>>>>>>>>>> -----Original Message----- From: Kevin Brown
>>>>>>>>>>>> Sent: Friday, June 29, 2012 2:08 PM
>>>>>>>>>>>> To: rwp at reaaccess.com
>>>>>>>>>>>> Subject: Re: [RWP] Windoweyes Still Can't Run Reaper 64
>>>>>>>>>>>>
>>>>>>>>>>>> Have you tryed system access?,...system access runs reaper
>>>>>>>>>>>> with no
>>>>>>>>>>>> problems,...I've been using it for 6 years now...
>>>>>>>>>>>>
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> 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
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> 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
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> 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
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> 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
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>
>>
>>
>> _______________________________________________
>> 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
>