[Rwp] SWS/S&M keys stopped working
James Teh
jamie at nvaccess.org
Sun Jun 5 18:27:03 EDT 2016
It's actually impossible for a 64 bit SWS to work in a 32 bit REAPER or
vice versa. It's not like VST plug-ins; there's no bridge for REAPER
extensions. That means you either accidentally installed a 32 bit REAPER
instead of a 64 bit or you have an old 32 bit install lying around which
you're opening instead of the 64 bit.
On 5/06/2016 11:05 AM, Andrew Downie wrote:
> I have been pondering the issue since Scott confirmed that the 64 bit
> version of SWS works on his machine. From my limited knowledge, the
> 32 bit version should work.
>
>
> The file that works is:
>
> sws-v2.8.3.0-install.exe
>
> The one that does not work on this machine is
>
> sws-v2.8.3.0-x64-install.exe
>
>
> Given that all systems are go, it isn't a crucial issue but I am left
> wondering what is causing it.
>
>
>
> Thanks
>
>
>
> Andrew
>
>
>
>
> On 4/06/2016 11:02 PM, theoreomonster at reaperaccess.com wrote:
>> Confirm the file name for the version of reaper you
>> downloaded/Installed. The way the website is laid out i wonder if you
>> accidentally grabbed the 32bit version of Reaper instead of the 64Bit
>> version.
>>> On Jun 3, 2016, at 7:21 AM, Andrew Downie
>>> <access_tech at iprimus.com.au> wrote:
>>>
>>> Well Gianluca, your comment about the right version had merit. I am
>>> very interested in comments from people who know much more about
>>> this stuff than me. Summary follows.
>>>
>>>
>>> I have a 64 bit version of Windows 10 and therefore installed a 64
>>> bit version of Reaper. Recently I found a newer version of SWS and
>>> installed the 64 bit version. Subsequently I found that the SWS
>>> shortcut keys were not happening. Last night I replaced the 64 bit
>>> SWS with the 32 bit version. Now the SWS keys work again.
>>>
>>>
>>> I have also found that Reaper doesn't recognise the 64 bit version
>>> of the Lame mp3 encoder but is more than happy to play ball with the
>>> 32 bit version.
>>>
>>>
>>> I discussed all this with a vastly more knowledgeable colleague. He
>>> was as bemused as I am.
>>>
>>>
>>> Can anyone provide feedback on why Reaper doesn't like these plugins
>>> in 64 bit form?
>>>
>>>
>>>
>>> Thanks
>>>
>>>
>>>
>>>
>>> Andrew
>>>
>>>
>>>
>>> On 1/06/2016 5:41 PM, Gianluca Apollaro wrote:
>>>> Hi,
>>>>
>>>> they totally work here.
>>>>
>>>> Try to reinstall sws and make sure it's the correct version.
>>>>
>>>> Hth,
>>>>
>>>> Gianluca from Italy.
>>>>
>>>> SkypeID: gianluca8815 or access4music
>>>>
>>>>
>>>> Il 31/05/2016 23:54, Andrew Downie ha scritto:
>>>>> But before doing all that my question is whether others have
>>>>> noticed that SWS keys no longer work in version 5.201. Not much
>>>>> point doing reinstalls if something broke with that version.
>>>>> Reverting to an earlier versionwould almost certainly fix the
>>>>> issue in the short term, but not in the long term.
>>>>>
>>>>>
>>>>>
>>>>> Andrew
>>>>>
>>>>>
>>>>>
>>>>> On 1/06/2016 12:13 AM, Darion Jaikaran wrote:
>>>>>> Try removing everything using revo uninstaller, opting for the
>>>>>> advanced scan +removal of leftover files and registry
>>>>>>
>>>>>> items and reinstall the affected software.
>>>>>> On 31/05/2016 06:12 AM, Andrew Downie wrote:
>>>>>>> On this Windows 10 machine, having upgraded to Reaper 5.201 (64
>>>>>>> bit), the SWS/S&M keys no longer work. Nor do they appear in
>>>>>>> the list of keys generated by Reaper. I can't be sure that
>>>>>>> their disappearance is related to the new version, but will
>>>>>>> blame it for now.
>>>>>>>
>>>>>>> I tried uninstalling and reinstalling Reaper along with SWS/S&M
>>>>>>> and osara but didn't clear out the stuff in my appdata folder
>>>>>>> due to laziness. In my tenuous defence, a couple of plugins I
>>>>>>> had put there disappeared and I was disinclined at this stage to
>>>>>>> put them back again. I also noticed that the Lame encoder
>>>>>>> disappeared, presumably when the upgrade to 5.201 happened.
>>>>>>>
>>>>>>> Enough rambling. Has anyone else noticed that SWS/S&M keys no
>>>>>>> longer do their thing?
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Andrew
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> RWP mailing list
>>>>>>> RWP at bluegrasspals.com
>>>>>>> http://bluegrasspals.com/mailman/listinfo/rwp
>>>>>> _______________________________________________
>>>>>> RWP mailing list
>>>>>> RWP at bluegrasspals.com
>>>>>> http://bluegrasspals.com/mailman/listinfo/rwp
>>>>>>
>>>>> _______________________________________________
>>>>> RWP mailing list
>>>>> RWP at bluegrasspals.com
>>>>> http://bluegrasspals.com/mailman/listinfo/rwp
>>>>>
>>>> _______________________________________________
>>>> RWP mailing list
>>>> RWP at bluegrasspals.com
>>>> http://bluegrasspals.com/mailman/listinfo/rwp
>>>>
>>> _______________________________________________
>>> RWP mailing list
>>> RWP at bluegrasspals.com
>>> http://bluegrasspals.com/mailman/listinfo/rwp
>>
>> _______________________________________________
>> RWP mailing list
>> RWP at bluegrasspals.com
>> http://bluegrasspals.com/mailman/listinfo/rwp
>>
>
> _______________________________________________
> RWP mailing list
> RWP at bluegrasspals.com
> http://bluegrasspals.com/mailman/listinfo/rwp
--
James Teh
Executive Director, NV Access Limited
Ph +61 7 3149 3306
www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess
SIP: jamie at nvaccess.org
More information about the RWP
mailing list