Difference between revisions of "Using Reaper Under MacOs"

From Reaper Accessibility Wiki
Jump to navigation Jump to search
(updating effects manipulation information)
(added info from the user mailing list on how to alllow plug ins to run in notarized versions of mac os)
 
Line 37: Line 37:
  
 
== other specific mac related concerns ==
 
== other specific mac related concerns ==
 +
 +
=== How to Allow OSARA, SWS and Other Reaper Extensions to run in Mac OS Catalina. ===
 +
 +
When Mac OS Catalina was released in October 2019, users found that OSARA, SWS and other extensions were not allowed to run. Catalina users receive an error message complaining that the extensions they're attempting to run aren't confirmed to be from a known source/developer. But fear not, you can manually allow OSARA and other extensions to run by following these steps:
 +
 +
# Press cancel the first time you see the error message. If you get a second warning where the extension name is different. Do not press cancel a second time.
 +
# Open System Preferences, then choose Security.
 +
# Navigate to the bottom of the screen by pressing VoiceOver+End.
 +
# Navigate using VoiceOver+LeftArrow until you hear VoiceOver say "Click the lock to make changes", press VoiceOver+Space on that lock button and enter your password if prompted.
 +
# To the left of the lock button, you'll find a button labeled "Allow". You can confirm which extension you're allowing by hitting VoiceOver+LeftArrow once more, so be sure to verify that, then when you're ready, move back to the "Allow" button and click it using VoiceOver+Space.
 +
# Here's where you'll need to use a little screen reader trickery. You now need to press VoiceOver+F1 twice quickly to bring up the application chooser menu. The first item in that menu should be "System dialogs", and VoiceOver will likely say "1 item". Press VoiceOver+Space twice there (the first press will open the system dialogs submenu, the second press will move VoiceOver focus into the system dialog itself).
 +
# You should now find yourself re-focused back in the same warning described in step 1. Repeat steps 5 and 6 again until there are no more system dialogs to attend to.
 +
After allowing each of your extensions this way, they should work as expected when you next launch Reaper.
 +
 +
==== Alternative Method (for advanced users only). ====
 +
 +
The method described below may result in your system being easier to attack because it involves disabling Apple's system integrity protection (a setting which is turned on by default). There are multiple articles online outlining this method in detail, such as [https://www.imore.com/how-turn-system-integrity-protection-macos this guide from iMore]
 +
 +
Please research the ramifications of disabling system integrity protection and make certain that you're comfortable before attempting this alternative method. It may seem easier than the steps above at a glance, but remember that security is paramount nowadays. OK, you've made it through the warning so you're clearly a determined sort. Here are the steps:
 +
# Reboot your Mac into recovery mode by holding CMD+R as you press the power button.
 +
# Wait for about 30 seconds, then launch VoiceOver either by pressing CMD+F5 or pressing three times on the Touch ID button if your Mac has one of those.
 +
# Select your language if prompted.
 +
# On the screen that offers such options as "Install Mac OS" and "Restore from Time Machine backup", move to the menu bar by pressing VoiceOver+M, open the Utilities menu and choose Terminal.
 +
# Type in the following command and press Enter when you are done: csrutil disable
 +
# Type reboot and hit Enter again. Once done, your Mac will restart with system integrity protection disabled, and - though your system may now be a perilous void of vulnerability - your extensions should work as expected.
  
 
===  there is no application key on mac ===
 
===  there is no application key on mac ===

Latest revision as of 15:25, 11 January 2020

introduction[edit]

OSARA is a plug-in which aims to work under Windows and Mac using the screen readers available for each platform. As has been probably explained elsewhere and in the reaper manual, there are some differences for achieving some procedures (like setting up track sends for instance). This article will attempt to bring them all in one place. it also will most likely be helpful for users of both platforms. note that due to the development of reaper and osara advancing simultaneously for some time now, possibilities are growing for accomplishing tasks so the information present on this article, while still relevant and applicable, is subject to change from time to time.

voiceover tips and tricks[edit]

voiceover talks too much/makes too much noise![edit]

One of the first things (and most frequently described problems) users notice, is the excess speech and feedback being given by voiceover. For example, since macOS High Sierra, VO beeps every time OSARA provides feedback. This not only makes working in reaper tedious, it can also potentially become distracting and slow down the workflow. There are some things you can do to reduce these issues.

Reducing Voice Over Sounds With VO Activities[edit]

To stop VO beeping each time OSARA provides feedback, setup a Voice-Over Activity for Reaper as described below:

  1. Press VO-F8 to open Voice-Over Utility.
  2. Press command-0 to go to activities.
  3. Now, find the "Add" button at the bottom of the window and press it.
  4. You are prompted to make a name for the activity. making the name application specific is recommended but this is a personal preference.
  5. Now press VO+right-arrow until you hear: Additional settings (or how it is shown for your language). And here press vo-spacebar.
  6. Now continue to press VO+right arrow until you hear: Audio checkbox unchecked. Check it using Vo-spacebar.
  7. Continue once more to the right, and you'll find the options button, which you press by using vo-spacebar on it.
  8. Now you have to locate and check the box: Mute sound effects and go to the end of the window and close it by pressing either close or OK.
  9. Now you are back to the activities window. We now need to tell Voiceover when to use this activity.
  10. Press VO+right until it says: Webpages and programs menu button, and press VO+spacebar.
  11. Select Reaper from the list of applications. That's it, no more sound effects from Voiceover.

Note, many other options around verbosity can also be customized for the Reaper Activity you have created, including any Keyboard Commander assignments you have made. Below is another recommended Activity customization. Also, the above Muting of VO sound effects can also be added to a Keyboard Commander, key in the VO Utility.

Reducing Speech Verbosity[edit]

While setting up the activity as above, you can include verbosity settings. Press the "Set… Verbosity" button. and then expand the additional speech verbosity options. at the very bottom of the table of options which you can customize, there is an option called "Window". Customize the verbosity for this setting and uncheck the “Name” field. You will still need to have either status or type checked but this will stop Voice Over from telling you about your particular version of reaper and who it is licensed to, whenever you return to the main Reaper window. This reduces some of the extraneous speech

Muting Voice Over[edit]

Another option is to assign a Keyboard Commander shortcut key that will mute Voiceover completely. This is especially helpful when you don't want to be distracted while doing some precise edits. You can do this from within the Voice Over Utility accessed by pressing VO+F8, and then pressing Command+8 to access the commander options. Pick the Keyboard tab, and then Add an additional key and assign it to the Mute Voice Over toggle command.


note: VO is a short form for the Voiceover word. Remember you can use either caps lock or control-option keys as Voiceover mmodifier keys depending on how you have set Voiceover on your Mac.

other specific mac related concerns[edit]

How to Allow OSARA, SWS and Other Reaper Extensions to run in Mac OS Catalina.[edit]

When Mac OS Catalina was released in October 2019, users found that OSARA, SWS and other extensions were not allowed to run. Catalina users receive an error message complaining that the extensions they're attempting to run aren't confirmed to be from a known source/developer. But fear not, you can manually allow OSARA and other extensions to run by following these steps:

  1. Press cancel the first time you see the error message. If you get a second warning where the extension name is different. Do not press cancel a second time.
  2. Open System Preferences, then choose Security.
  3. Navigate to the bottom of the screen by pressing VoiceOver+End.
  4. Navigate using VoiceOver+LeftArrow until you hear VoiceOver say "Click the lock to make changes", press VoiceOver+Space on that lock button and enter your password if prompted.
  5. To the left of the lock button, you'll find a button labeled "Allow". You can confirm which extension you're allowing by hitting VoiceOver+LeftArrow once more, so be sure to verify that, then when you're ready, move back to the "Allow" button and click it using VoiceOver+Space.
  6. Here's where you'll need to use a little screen reader trickery. You now need to press VoiceOver+F1 twice quickly to bring up the application chooser menu. The first item in that menu should be "System dialogs", and VoiceOver will likely say "1 item". Press VoiceOver+Space twice there (the first press will open the system dialogs submenu, the second press will move VoiceOver focus into the system dialog itself).
  7. You should now find yourself re-focused back in the same warning described in step 1. Repeat steps 5 and 6 again until there are no more system dialogs to attend to.

After allowing each of your extensions this way, they should work as expected when you next launch Reaper.

Alternative Method (for advanced users only).[edit]

The method described below may result in your system being easier to attack because it involves disabling Apple's system integrity protection (a setting which is turned on by default). There are multiple articles online outlining this method in detail, such as this guide from iMore

Please research the ramifications of disabling system integrity protection and make certain that you're comfortable before attempting this alternative method. It may seem easier than the steps above at a glance, but remember that security is paramount nowadays. OK, you've made it through the warning so you're clearly a determined sort. Here are the steps:

  1. Reboot your Mac into recovery mode by holding CMD+R as you press the power button.
  2. Wait for about 30 seconds, then launch VoiceOver either by pressing CMD+F5 or pressing three times on the Touch ID button if your Mac has one of those.
  3. Select your language if prompted.
  4. On the screen that offers such options as "Install Mac OS" and "Restore from Time Machine backup", move to the menu bar by pressing VoiceOver+M, open the Utilities menu and choose Terminal.
  5. Type in the following command and press Enter when you are done: csrutil disable
  6. Type reboot and hit Enter again. Once done, your Mac will restart with system integrity protection disabled, and - though your system may now be a perilous void of vulnerability - your extensions should work as expected.

there is no application key on mac[edit]

There are some situations in which you are advised to use the applications key, (for example, when setting inputs for recording).

The good news is that you don’t need an application-key on the mac. Recent  changes in osara development and reaper allow users to access the menus reliably, regardless of system. This is because Rather than using various hacks to access context menus, osara now uses a new REAPER API function explicitly designed for this purpose. 

This basically means that On Mac, you can now press control+1, control+2 and control+3 to open the first, second and third context menus, respectively. More detailed information is available in the osara readme

As for setting track inputs, the info that follows is out of date, but might be of use for some people. there is a simple trick to open the track-input-menu:

For example, lets say, you have an interface with 8 inputs and want to assign the first microphone-input to track 3, because track 1 and 2 contain virtual instruments. Then you could do the following:

  1. Press Voice-over+I to open the item-chooser.
  2. Type in 3 for track-number 3 and press enter.
  3. Make sure that quick-navigation-mode is off by pressing left and right arrow-keys simultaneously.
  4. Press voice-over+left once. That should bring you to an entry called „Track-input-record, followed by a number, which will depend on how many channels your interface has.
  5. Pressing voice-over+space will open the track-inputs-menu. Here you can assign the appropriate input.

You can also assign inputs on the Mac or Windows with ReaConsole (follow the link for an audio tutorial by Garth Humphreys) or see its corresponding documentation.

adjusting effect parameters[edit]

Thanks to a recent osara update, there is the possibility, just as is done in windows to open a dialog which exposes all of the parameters that relate to a plug-in

A couple of notes regarding Mac though

  1. The actions to open Parameters dialogs aren't bound to keys on the Mac yet. You'll need to bind yourself or execute from the Actions dialog.
  2. The slider should support keyboard interaction (arrow keys, page up/down, home/end). However, it won't work if you try to use VO commands to interact with it. For now there isn't either a possibility, nor plans to try to fix this.

In the case of other effects that do not expose very helpful values from this dialog, you can try and access the native or generic effects UI, depending on the particular effect you are using. the accessibility of the native dialogs vary between manufacturers; however, if you are using the default settings, then when you add an effect you will be in the native UI. First check this out and see if you can access the parameters, most of the included Reaper effects are accessible. For third party effects, it varies. If the native UI is not accessible, then press VO + space on the UI button and you will have some access to the parameters.