Using Reaper Under MacOs and Monitoring levels when you can't see the meters: Difference between pages

From Reaper Accessibility Wiki
(Difference between pages)
Jump to navigation Jump to search
(updating page migration)
 
(initial page migration)
 
Line 1: Line 1:
= introduction =
= Intro =


OSARA is a plugin which aims to work under Windows and Mac using the screen readers available for each platform. As has been [[Getting_Started#Mac_Osara_Installation|probably explained elsewhere]] and [[Chapter_1_Setting_Up_and_Getting_Started#1.9_REAPER_Selections.2C_Controls_and_Commands|in the reaper manual]], there are some [[Enabling_Midi_Devices#Mac_Instructions|differences]] for achieving [[Sidechaining_with_ReaComp#Some_Tips_for_Windows_and_Mac_users|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.
As a blind audio producer, maybe you've felt a level of uncertainty caused by the inability to see the meters on your equipment. Too high and things might clip at some point during the audio program, too low and it won't sound good along side other material. Reaper and Osara provide for us a way to monitor peaks in our audio levels. It isn't quite like watching a meter, but it gives us the pertinent information we need to structure the gain and keep things from clipping on the master.


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.
note that depending on your mixing needs or wants, you can have either post fader, or pre-fader levels be displayed and also announced. It depends on, and is simply a matter of [[Chapter 2: REAPER Project Basics#2.6 Track Controls|having a small preference set in the options menu]]. in other words, moving a track's volume fader in reaper with pre-fader levels enabled will not change what is being announced or shown on screen.


== VoiceOver tips and tricks ==
== Peak Watcher ==
The peak watcher is a tool which, when configured, allows you to monitor the peaks of your recordings.


=== VoiceOver talks too much/makes too much noise! ===
=== setting up the peak watcher ===


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.
By default, pressing ctrl-shift-w (OSARA: View Peak Watcher) opens the Peak Watcher dialog.
The first two options are to select the first and second tracks to be monitored. One sensible setup is to select "current track" from the dropdown for the first track, and "master" for the second track.
notify automatically: This option allows you to set things up so you are notified when the peak hits a certain level. Check the boxes for the alerts if you choose.
The next setting is to set the level at which you wish to be alerted. This is useful for knowing if your master goes over 0.0 db or what ever level you choose.
The next setting, "hold peaks until" has a default setting to hold until reset. This setting will cause the peak watcher to keep the highest peak registered until you reset it for each track. This is useful for knowing the highest level at which an audio source has peaked, after the fact.


==== Reducing Voice Over Sounds With VO Activities ====
== Using The Peak Watcher ==
To stop VO beeping each time OSARA provides feedback, setup a Voice-Over Activity for Reaper as described below:


#Press VO-F8 to open Voice-Over Utility.
There are at least two main uses for the peak watcher, to monitor incoming audio before or during recording, and to set levels during mixing.
#Press command-0 to go to activities.
#Now, find the "Add" button at the bottom of the window and press it.
#You are prompted to make a name for the activity. making the name application specific is recommended but this is a personal preference.
#Now press VO+right-arrow until you hear: Additional settings (or how it is shown for your language). And here press vo-spacebar.
#Now continue to press VO+right arrow until you hear: Audio checkbox unchecked. Check it using Vo-spacebar.
#Continue once more to the right, and you'll find the options button, which you press by using vo-spacebar on it.
#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.
#Now you are back to the activities window. We now need to tell Voiceover when to use this activity.
#Press VO+right until it says: Webpages and programs menu button, and press VO+spacebar.
#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.
==== Monitoring Input Levels ====


==== Reducing Speech Verbosity ====
After creating, arming, and setting the monitor on your track, create some source audio. Sing or speak in to the microphone, play your instrument, do what ever you do to make noise. Try your best to sing or play with approximately the same energy and gusto as you will when you are performing for the recording.
While setting up the activity as above, you can include verbosity settings.   
After you stop playing or singing, press alt-f9 and or alt-f10 to check the level on your currently selected track which should be "first track" in your peak watcher. Osara should report the peak level of your performance. This means that you will be told only the highest level your audio peaked at. You will not be told the lowest, or average peak.
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
To reset the meter for track one of your peak watcher, press alt-f8. At this point, you can either try again, resetting levels as needed, or adjusting your performance, or you can record!
==== Muting Voice Over ====
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 modifier keys depending on how you have set Voiceover on your Mac.
==== during mixing or playback ====


== other specific mac related concerns ==
During playback you might find it most useful to check your master peak by pressing alt-shift-f9 or alt-shift-f10. These are the keystrokes for checking the "second track" as defined in the Peak Watcher. Remember that your master track will reflect the combined level of all of the tracks in your project. So, if you determine that the peak on your master is too high, you can then adjust levels of individual tracks or other elements to reduce the master track level.


=== How to Allow OSARA, SWS and Other Reaper Extensions to run in Mac OS Catalina. ===
== real-time level monitoring ==


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:
The Peak Watcher lets you know the highest peak a track has reached, on demand. To know the "current" level of the currently selected track, press j or k. These will report the current levels of channel one and two of the currently selected track. Pressing shift-j and shift-k will report the current levels of both channels of the master track.


# 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). ====
== checking Levels in your rendered project ==
If you are working on project such as a podcast, (or any project) you can quickly check if the resulting rendered file has clipped,  (in other words, it went above 0 DB).
There are two methods:


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]
===== using the render dialog =====
*While rendering your file, uncheck the checkbox that says "automatically close when finished".
* At the end of the rendering process, review the render window with your screen reader's review commands.
*There will be just one number if you rendered mono audio or more if you rendered multi-channel audio. These numbers represent the highest peak value for the entire project for a specific channel.


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:
===== using Peakwatcher After Rendering =====
# Reboot your Mac into recovery mode by holding CMD+R as you press the power button.
* Set it up to monitor your master track until reset. In this example we will monitor the master track as second track.
# 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.
* Reset the peakwatcher before rendering by pressing shift+alt+F8 for resetting the second track.
# Select your language if prompted.
* Render your project as usual.
# 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.
* After rendering your project, check the values with alt+shift+F9.
# 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 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#Context_Menus|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:
# Press Voice-over+I to open the item-chooser.
# Type in 3 for track-number 3 and press enter.
# Make sure that quick-navigation-mode is off by pressing left and right arrow-keys simultaneously.
# 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.
# 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 [http://audio.pizza/tag/reaconsole/ ReaConsole] (follow the link for an audio tutorial by Garth Humphreys) or see its [[Reaper_plus!_the_power_of_sws_extensions#SWS_ReaConsole|corresponding documentation]].
 
=== adjusting effect parameters ===
 
Thanks to a recent osara update, there is the possibility, just  as is done in windows to open a  [[OSARA_readme#FX_Parameters|dialog which exposes all of the parameters that relate to a plug-in]]. Further, you can just as well press ctrl+tab and ctrl+shift+tab to cycle between parameters.
 
A couple of notes regarding Mac though
# In the most recent OSARA updates the actions to open Parameters dialogs are bound to "p" and "Option+p" keys. For example, to access effects for a particular track, simply focus on that track and press the letter "p". Similarly, to access the track parameters for a track, focus on it and press "Option+p".
# 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.
 
=== Accessing right-click menus with VoiceOver ===
It turns out that many UI controls on the Reaper toolbars have context menus associated with them. As of this writing, in order to access them though, one has to right-click on such controls. But how?
Fortunately, VoiceOver provides a "right-click  mouse" command in its list of commands and we can use it to perform the actual right-clicks on any control in Reaper. Here is one way to achieve this result:
# Open VoiceOver Utility by pressing VO+F8.
# In the list of categories choose the "Commanders" category, then tab to the list of various tab sheets available for it. Here VO+RightArrow to the "keyboard" tab and press VO+Space to activate it.
# In the "keyboard" sheet tab to the tab that contains currently-assigned keystrokes (they begin with Right Option by default but you can change this if you wish).
# Choose a single key which has not been taken, for example "r" for right-click.
# VO+RightArrow to the "add" button, then type "r" in the "keyboard key" edit field.. Then VO+RightArrow once to the "command menu" button (this is where you can choose the command to execute when the shortcut key is pressed).
# Activate the menu with VO+Space, then navigate to General > Right Click Mouse command and activate it by pressing VO+Space.
# You should now have a new entry in the table of shortcut keys listing the shortcut you just created.
# Exit out of this screen and try your new shortcut key by first routing the mouse pointer to VO cursor with VO+F5, followed by the key you assigned for performing the right-click.
You will discover a lot of hidden treasures inside Reaper context menus. For example, move through the toolbar of the track view and right-click on various buttons and other controls. See what you find!
With the right-click method described above, you are now able to set up your MIDI devices in Reaper Preferences much quicker and do other cool things!
In one of the upcoming versions of Reaper the standard VO+Shift+m will allow you to open context menus in many places inside Reaper, but the right-click trick might still be something you want to keep assigned, just in case!
 
If you enjoy the "right-click" tip above and plan on using it quite a bit, you can ask VoiceOver to always route the mouse pointer to the VO cursor when you navigate, thus saving you an extra step. To do so,
# Inside a VO utility, VO+F8, go to "Navigation" category.
# Tab to the "Mouse Pointer" menu and select the "Follow VO cursor" option.
You should now be all set!
 
==== One last tip! ====
If you like the right-click ability but would like to have it work in Reaper only, you can use the steps described above to add it to your "Reaper" activity. Simply add "Navigation" and "Keyboard" categories to the activity, then activate the settings described above.

Revision as of 22:42, 17 May 2023

Intro

As a blind audio producer, maybe you've felt a level of uncertainty caused by the inability to see the meters on your equipment. Too high and things might clip at some point during the audio program, too low and it won't sound good along side other material. Reaper and Osara provide for us a way to monitor peaks in our audio levels. It isn't quite like watching a meter, but it gives us the pertinent information we need to structure the gain and keep things from clipping on the master.

note that depending on your mixing needs or wants, you can have either post fader, or pre-fader levels be displayed and also announced. It depends on, and is simply a matter of having a small preference set in the options menu. in other words, moving a track's volume fader in reaper with pre-fader levels enabled will not change what is being announced or shown on screen.

Peak Watcher

The peak watcher is a tool which, when configured, allows you to monitor the peaks of your recordings.

setting up the peak watcher

By default, pressing ctrl-shift-w (OSARA: View Peak Watcher) opens the Peak Watcher dialog. The first two options are to select the first and second tracks to be monitored. One sensible setup is to select "current track" from the dropdown for the first track, and "master" for the second track. notify automatically: This option allows you to set things up so you are notified when the peak hits a certain level. Check the boxes for the alerts if you choose. The next setting is to set the level at which you wish to be alerted. This is useful for knowing if your master goes over 0.0 db or what ever level you choose. The next setting, "hold peaks until" has a default setting to hold until reset. This setting will cause the peak watcher to keep the highest peak registered until you reset it for each track. This is useful for knowing the highest level at which an audio source has peaked, after the fact.

Using The Peak Watcher

There are at least two main uses for the peak watcher, to monitor incoming audio before or during recording, and to set levels during mixing.

Monitoring Input Levels

After creating, arming, and setting the monitor on your track, create some source audio. Sing or speak in to the microphone, play your instrument, do what ever you do to make noise. Try your best to sing or play with approximately the same energy and gusto as you will when you are performing for the recording. After you stop playing or singing, press alt-f9 and or alt-f10 to check the level on your currently selected track which should be "first track" in your peak watcher. Osara should report the peak level of your performance. This means that you will be told only the highest level your audio peaked at. You will not be told the lowest, or average peak. To reset the meter for track one of your peak watcher, press alt-f8. At this point, you can either try again, resetting levels as needed, or adjusting your performance, or you can record!

during mixing or playback

During playback you might find it most useful to check your master peak by pressing alt-shift-f9 or alt-shift-f10. These are the keystrokes for checking the "second track" as defined in the Peak Watcher. Remember that your master track will reflect the combined level of all of the tracks in your project. So, if you determine that the peak on your master is too high, you can then adjust levels of individual tracks or other elements to reduce the master track level.

real-time level monitoring

The Peak Watcher lets you know the highest peak a track has reached, on demand. To know the "current" level of the currently selected track, press j or k. These will report the current levels of channel one and two of the currently selected track. Pressing shift-j and shift-k will report the current levels of both channels of the master track.


checking Levels in your rendered project

If you are working on project such as a podcast, (or any project) you can quickly check if the resulting rendered file has clipped, (in other words, it went above 0 DB). There are two methods:

using the render dialog
  • While rendering your file, uncheck the checkbox that says "automatically close when finished".
  • At the end of the rendering process, review the render window with your screen reader's review commands.
  • There will be just one number if you rendered mono audio or more if you rendered multi-channel audio. These numbers represent the highest peak value for the entire project for a specific channel.
using Peakwatcher After Rendering
  • Set it up to monitor your master track until reset. In this example we will monitor the master track as second track.
  • Reset the peakwatcher before rendering by pressing shift+alt+F8 for resetting the second track.
  • Render your project as usual.
  • After rendering your project, check the values with alt+shift+F9.