|
|
| Line 1: |
Line 1: |
| = introduction and a brief concept explanation = | | = introduction = |
|
| |
|
| In most digital audio workstations, midi can work alongside audio, or in conjunction with, audio. This is because there are a number of resources and tools available to produce great sounding arrangements using midi and you could probably want to record a live, real instrument to supplement the song you are producing. The user guide has got some of the common htings some folks are used to, some behaviors if you will, in other software based editors like qws, and you shoudl go [[Chapter 13: Manipulating and Editing MIDI Items#13.2 Monitoring an External Synthesizer|here if you want to hear your keyboard coming through as you play it]] and [[Chapter 13: Manipulating and Editing MIDI Items#13.3 Using Track Controls with MIDI|here if you want to control some basic parameters like pan and volume of a track]] . We will deal with patches and other things [[#patch and bank changes|in a little while]] . Lastly, [[Useful Links and Resources#using Yamaha SYXG 50 on modern machines|go here]] if you want to have a gm compatible synth (for the more tech-inclined users).
| | OSARA is a plug-in 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. 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. |
|
| |
|
| For now thtough, there are two main ways that midi is used into modern digital audio workstations.
| | == voiceover tips and tricks == |
| # by using an external synth or keyboard or midi module, any hardware that can produce sound based on midi and then recording the audio directly from that equipment. For Configuration basics to get your midi devices working in reaper, check out the article on [[Enabling Midi Devices]] if you haven't done so already and the one mentioned at the top of this section. Also check out [[Chapter 3: recording audio and midi#3.28 Recording a Track's Output|this procedure for recording the sound directly from your keyboard when using midi]]
| |
| # By using a virtual instrument inserted as an effect in a track. You need to have for this any kind of virtual instruments or instrument libraries as they are called and will still need any kind of midi device for input.
| |
|
| |
|
| Note. If you just want to have midi played back by using a system installed synthesizer (such as the default Microsoft gs wave table synth or an external keyboard) select the track that has midi in it, then press [[Useful Links and Resources#numpad emulation and applications key script|alt plus applications key]], and then arrow up once. You should have a submenu called midi output. From there you can select the hardware midi output to use.
| | === voiceover talks too much/makes too much noise! === |
|
| |
|
| The second option is becoming very popular nowadays because of the higher quality and flexibility of the libraries and instruments. Which means that a great majority of those instruments are no longer gm compatible and also usually have a few, very few or even just one kind of instrument, since they are usually specialized, responding to very specific needs. SO the more virtual instruments you might want to have per song, the more ram you will need.
| | 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. |
|
| |
|
| == recommended settings == | | ==== Reducing Voice Over Sounds With VO Activities ==== |
| | To stop VO beeping each time OSARA provides feedback, setup a Voice-Over Activity for Reaper as described below: |
|
| |
|
| Before continuing, make sure that the following is set.
| | #Press VO-F8 to open Voice-Over Utility. |
| *Under Editing Behavior>midi editor, the Behavior for "open items in built-in MIDI editor": should be: Open the clicked MIDI item only
| | #Press command-0 to go to activities. |
| *Active MIDI item follows selection changes in arrange view. Should be checked.
| | #Now, find the "Add" button at the bottom of the window and press it. |
| *Avoid automatically setting MIDI items from other tracks editable. Checked
| | #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. |
|
| |
|
| from the midi editor, you should set the following options too, by opening any midi item [[#Piano Roll View|as described on the first couple of steps here if you don't know how,]] and then pressing alt plus O once the editor is open.
| | 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. |
| * Allow MIDI note edit to extend the media item: checked.
| |
| *Sync editor transport to project transport : checked
| |
| *note preview submenu: all options checked
| |
|
| |
|
| == the grid concept == | | ==== Reducing Speech Verbosity ==== |
| | 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 ==== |
| | 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. |
|
| |
|
| one of the ways audio and especially midi is being edited in many modern programs uses what is called a grid, which is just a visual representation in timing. It looks just like a square grid , composed of vertical bar lines, which are the equivalent of.. you guessed it, musical bars. In reaper you have different grid divissions which will let you move notes, adjust their duration, or quantice them to different rhythm values. For this you must always set first the grid size (or grid unit), and then perform the desired operation. Common rhythm values follow. You will notice that they just divide musical bars by a certain ammount.
| |
| {|
| |
| ! grid unit size (division type
| |
| ! time signature
| |
| ! corresponding note value
| |
| |-
| |
| | 1/2
| |
| | 4/4
| |
| | half note, or minim
| |
| |-
| |
| | 1/4
| |
| | 4/4
| |
| | quarter note, or crotchet
| |
| |-
| |
| | 1/12
| |
| | 4/4
| |
| | one third of a quaver (useful for eight note triplets)
| |
| |-
| |
| | 1
| |
| | 6/8
| |
| | a whole bar in 6/8 time, which can be translated as a doted half note or a dotted minim.
| |
| |}
| |
| As you see, setting the grid to a certain ammount is always dependent on the time signature, not on the strict value that is mentioned or specified.
| |
| Whenever you set grid units to a specified size, any actions that depend on the grid (move audio items by grid size, move notes or cursor to next grid unit ETC) will perform and affect notes by that ammount. for example You could probably set the grid to 1/2 and move audio items by that distance sooner (left) or later (right) during playback, when editing.
| |
| You can set the midi grid to different sizes or divisions, by using the upper numeric row on the keyboard once you are in the midi editor. Those actions do have the equivalents already calculated for you. [[Chapter 5: Project Arrangement Basics#5.12 Displaying Grid Lines|you can also set them for audio separately]]
| |
|
| |
|
| = editing midi notes in reaper =
| | 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. |
|
| |
|
| == Piano Roll View == | | == other specific mac related concerns == |
|
| |
|
| Reaper comes with its built in midi editor. It has two usable views. This one which is described is called piano roll view. [[#using the event list|the event list view will be described later]]. You can work on one midi item at a time. To edit a midi item that you have recorded, follow this general procedure:
| | === How to Allow OSARA, SWS and Other Reaper Extensions to run in Mac OS Catalina. === |
| * First select the midi item with control left or right arrows, respectively.
| |
| *Bind or invoque the action named, Item: Open in built-in MIDI editor (set default behavior in preferences) (I have set this to control plus w)
| |
| *Once the midi item ahs been opened, you will be in the piano roll view by default.
| |
| *You can then use the actions (bound to the arrow keys and shift and the arrow keys) to move by chord or note. Osara makes a distinction between notes and chords since there can be many notes in the same place or beat, sounding simultaneously. And you can select or manipulate all of them or just some. Usually every isolated note is technically considered a chord. You should hear the notes or chords when you are moving being played through your keyboard, synth or virtual instrument. For more information on how all of this is handled you can consult the [[OSARA_readme#Notes_and_Chords_in_the_MIDI_Editor|specific section]] of the OSARA read me.
| |
| *you can then use any of the actions that perform the operation you want. Delete, move copy, ETC. selected notes, quantice. Don't forget to set the grid size first!
| |
| *When you are done editing, press escape to close the midi editor window, otherwise it will remain open and sometimes will make some midi items not be editable, plus take up some space!
| |
|
| |
|
| Normally, the midi editor will focus or be directly on the bar that you have last paused or placed the cursor. If this however is not the case, you can use the page up and down keys in the midi editor to move forward or backwards by measures respectively. You can also use OSARA: Report edit/play cursor position bound to command/control shift j to check where you are directly within the midi editor.
| | 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: |
|
| |
|
| Lastly, remember that reaper has different [[Chapter 3: recording audio and midi#3.31 Other MIDI Recording Modes|various midi recording modes]] that you can use to your advantage. For example, you can use the overdub mode to record fader movements, or pedal sustain events as the track is playing which are just midi control messages for situations on which you only have a portable, smaller midi controller available.
| | # 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. |
|
| |
|
| === changing propperties for one or more notes === | | ==== Alternative Method (for advanced users only). ==== |
|
| |
|
| there will be times when you wish to move a note to a very specific desired location, to extend or shorten its length, to even change the channel it is played on, or to change the pitch, or strength (velocity). Of course, all of those things can be done by using actions that you have bound to keys (usually and by default the [[Useful Links and Resources#numpad emulation and applications key script|numpad keys]]) to achieve all of this, but if for one you know the value, and wish to be very specific about it, you can select any note and then press control plus f2 on it to open the note properties dialog.
| | 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] |
| The [[Chapter 13: Manipulating and Editing MIDI Items#13.16 Using the Keyboard|guide ]] has more information on some useful actions. When clicking or dragging is mentioned on that section, you can usually accomplish the ssame by selecting all notes and then opening the note properties dialog instead, so yes you can absolutely select many notes (using shift and the arrows) and then open the properties dialog to change them all to the same length or put them all in the same position, or even use multiplier values like *2 for example, to double the current length of each note regardless of the value it has now.
| |
|
| |
|
| == using the event list ==
| | 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. |
|
| |
|
| Once inside the midi editor, pressing alt plus 3 will bring the [[Chapter 13: Manipulating and Editing MIDI Items#13.20.1 Note Modes|event list]] which will let you have a finer control when editing any note or parameter.
| | === there is no application key on mac === |
|
| |
|
| This list is accessible with NVDA. All columns will be read as they should. If you wish to move the focused NVDA selection to the current sounding note, or to the last place that you were on when editing in the piano roll view, you can use the action bound to the keystroke Ctrl+F, called OSARA: Focus event nearest edit cursor just after switching to the event list view and before startling to navigate through the list. When editing events this procedure requires that you navigate until you find the event you need to edit (like the piano sustain on message) however, it hopefully should not be too much of a problem because you could memorize the approximate position and you can also use the page up and down keys to quickly scroll through the list.
| | There are some situations in which you are advised to use the applications key, (for example, when setting inputs for recording). |
| Pressing the applications key on any item of that list will bring up a menu which will let you do a number of tasks including adjusting properties for midi cc's and notes (the dialog that comes up for notes is exactly the same one you can access from the piano roll view [[#Piano Roll View|described earlier]]). When you are done editing a cc event, you can go back to the default piano roll view by pressing alt plus number one of the upper numeric row.
| |
|
| |
|
| == Midi Step recording or step input in reaper ==
| | 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]] |
|
| |
|
| Many times it is desirable to input notes that consist of a complex rhythmic figure in step time rather than playing them in real time. This method can prevent the need to clean up sloppy playing that results from executing complex figures at high speed. Besides the [[Chapter 13: Manipulating and Editing MIDI Items#13.26 Step Recording|procedure described in the manual]], the following instructions are designed to let you enter a complex rhythmic figure in a short amount of time with a minimum of mistakes:
| | 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: |
|
| |
|
| # Make a time selection.
| | 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: |
| # Insert a midi Item which corresponds to that time selection on the desired track (can be a new or an existing armed one) by using the insert menu, then select the item you just inserted. | | # Press Voice-over+I to open the item-chooser. |
| # Enter the MIDI Editor with CTRL Alt E (assigned by default) for this track. | | # Type in 3 for track-number 3 and press enter. |
| # Use the Applications Key and choose Use All Inputs for Step Recording. Ensure you undo this choice after you are done with step recording. This is particularly important if you intend to continue entering MIDI data conventionally on the same track. | | # Make sure that quick-navigation-mode is off by pressing left and right arrow-keys simultaneously. |
| # Now, you use the upper numeric row keys to determine grid division and combine these with the CTRL key to determine note length. Having made those choices play the notes or chord you want. | | # 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. |
| # To join notes together, select the two notes with Shift and Arrow until the notes you want are selected and hit J.
| | # 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]]. |
|
| |
|
| To start a pattern with a rest on the initial downbeat of the first bar of your pattern you Set both note length and grid division to the same value. , then you advance by grid division using actions bound to either CTRL Shift Right Arrow, or CTR:L Numpad 6 with Numlock ON. For this example, we’ll say that the objective is to place an eighth rest on the first downbeat. In other words, beat one of the bar.
| |
| # Set both note length and grid division to an 8th note.
| |
| # Advance the cursor one eighth note by pressing either CTRL Shift Right Arrow or CTRL Numpad 6 with Numlock ON.
| |
| # Confirm your position by pressing CTRL Shift J. You should be at beat 1 50%. At this point, set your note length and grid division as desired to begin inserting notes or chords.
| |
| NOTE: You can copy and paste (for repetitions of a pattern) and can even transpose notes, chords or entire repetitions as desired.
| |
|
| |
|
| (Special thanks to Gianluca Apollaro for largely contributing to the information this section)
| | === adjusting effect parameters === |
|
| |
|
| = patch and bank changes =
| | 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]] |
|
| |
|
| (editors note: please clean this up, its from an old e-mail from the rwp list) | | A couple of notes regarding Mac though |
| | # 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. |
| | # 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. |
|
| |
|
| This procedure depends on the instrument. If you have a virtual instrument (vst) loaded, you can usually change patches straight from your keyboard, which is acting as
| | 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. |
| a controller in this case, assuming that your vst supports the standard program and bank change messages it will respond as it
| |
| should. For me this is the easiest setup. You simply load your vst and control everything from your midi keyboard or controller.
| |
| | |
| For the other way, which is using the sound from the external synth or keyboard itself, or for midi control messages when there is no external controller available the procedure is a bit more involved.
| |
| There are two ways to access a plug-in that allows you to change patches and banks but they show the same options. You can either:
| |
| #insert the effect called reaControl into the midi track or
| |
| #Press control applications on it, then select show/hide midi track controls
| |
| | |
| In both cases the effect called [[ReaEffects guide#3 ReaControlMIDI|reaControlMidi]] will be added to the track. And in the case of having a virtual instrument inserted that responds to the standard midi messages, the reaControlMidi effect should be the first one in the fx chain list, by moving it up or inserting it first, before the virtual instrument. Good news is that it is pretty accessible. This plug-in is used because reaper has | |
| no native support for sending control messages to external midi modules or hardware or vsts... and also because you can work with those parameters at will, changing patches or banks or parameters by [[Implementing accessible automation|using automation]]
| |
| | |
| == reaControlmIdi description ==
| |
| | |
| When ReaControlmIdi is inserted, opening the fx chain or fx dialog by pressing the f key on the selected track will bring a window with chekboxes that allow you to send control messages, bank and patch change messages. They have to be checked otherwise controls (such as sliders and combo boxes) will not move and even if you put values on the edit boxes those messages do not get sent. The rest of the options are just settings for the behavior of the reaControl vst.
| |
| (note: some of those checkboxes just say "enable" before the corresponding group of controls, or parameters and thus are not propperly labelled). However, you can get an idea because NVDA will read the group of parameters you are about to control, for example: "bank/program select grouping: Enable check box not checked"
| |
| | |
| You can also, load a patch list or reabank file or convert from a .ins file if you have one that is specific to your keyboard by using the "load file" button. You can look into the [https://stash.reaper.fm/tag/Bank-Patches reaper stash at the reaper website] for reaBank files. That way you can select things from combo boxes with patch names instead of having to type in all of those values. And that would be pretty much it.
| |
| Also, make sure that your keyboard has or is set to a multiTimbral mode, where it can send and receive data from every midi channel at the same time and that you select one midi channel per instrument. I say this because Korg has a way of working that I never liked. In program mode for instance, you have only two channels that respond to external midi messages, which are channel 2 I believe which plays the current program or patch you have selected at a given time. and another which is the drumtrack channel but I don't think it is 10 anymore. Then in combi mode you have just.. the same thing, plus another channel which is the arpeggiator channel and .. that option is a bit silly because it enables a channel to have two different patches into one, according to ranges you have set. The one that works is simply, sequencer mode. There everything responds as it really should.
| |
| You should make sure too that only one track is armed and monitoring, because you then can create double parts on instruments you did not intend when recording.
| |
| | |
| == editing of control messages ==
| |
| | |
| in reaper there are two main accessible ways to edit control change messages, or midi cc as reaper calls it. Those can be anything from volume or pan changes on a midi item, to piano sustain events and so on. Unfortunately, they are quite involved since osara does not yet report cc events as you select or move through them. There are also no real commands for moving to next or previous cc event. Still, you can get some use from reaper's cc editing features. One of these ways was hinted at earlier, when the [[#using the event list|use of the event list was described]]
| |
| | |
| === using the cc lane ===
| |
| | |
| once you open an item in reaper's built in midi editor, you can press f4 and bind the following (suggested) actions to keys:
| |
| *CC: Next CC lane
| |
| *CC: Previous CC lane
| |
| *Edit: Increase value a little bit for CC events
| |
| *Edit: Decrease value a little bit for CC events
| |
| *Edit: Move CC events left by grid, Edit: Move CC events right by grid
| |
| *pixel movement actions are also available, but they are not as reliable and would depend on your horizontal zoom levels. (note: apparently reliability and accuracy of these has improved on latest reaper version)
| |
| *Edit: Select all CC events under selected notes
| |
| *Edit: Select all CC events in time selection (in last clicked CC lane)
| |
| | |
| When you are back in the midi editor, you can use object nav and you will arrive at an unlabeled combo box (its the first one reported by NVDA). Clicking the combo box with the mouse and then using the arrow keys will let you quickly select a cc lane to edit or draw events on. If the lane does contain data already in it, a bullet sign, a • will be spoken before the name of the lane, for example: combo box •Velocity collapsed. Focusing the lane will unfortunately cause the main editor window to lose focus so when you are done selecting a lane, you have to alt tab away and then to reaper again. Even if you close the midi editor the last selected lane will be preserved, even across projects so you probably will not have to change it that often. You can insert cc events manually as well, even by using a controller as the file is playing which would be the equivalent of drawing. If you know which lane you are on at the time and do not want to use object navigation you can then use the previous and next cc lane commands.
| |
| | |
| Although really if you find that only a part of the song did not have sustain events at the right places, your best bet is to use the select cc events in time selection or select cc events under selected notes and either move them until you are satisfied, or change their values with the commands, or finally erase those events and record them again.
| |
| | |
| = usage tips for some midi tools =
| |
| | |
| In adition to using the midi editor for manipulation of midi data, reaper does ahve a few more tools you can use to generate or modify midi.
| |
| | |
| == accessing and using the midi filter window ==
| |
| | |
| Reaper has a [[Chapter 13: Manipulating and Editing MIDI Items#13.6 The MIDI Editor Window|midi filter]] (described on detail in the second paragraph). When using the NVDA screen reader focus is not automatically changed when the "filter events..." option from the view menu is used.
| |
| | |
| note: these instructions are becoming obsolete, since a recent osara update has attempted to address this issue (thanks to programmer Alexey Zhelezov)
| |
| | |
| There are two ways to get to that window:
| |
| #After you choose the option filter events from the view menu, do a physical move of your mouse or trackpad up and to the left and you should be able to hear the title of the filter window, or parts of the filter window being announced. Click once with the left button when you do and that should focus the window.
| |
| #If you are more comfortable using the object navigation functions of NVDA, when you choose the filter events... option from the view menu, you should move two times to the parent object. Press numpad shift 8 on your numeric pad if you are using a desktop, or NVDA shift up arrow if you are using a laptop. Then, move to the two previous objects by pressing NVDA+4 on the numeric pad if you are using a desktop, or NVDA shift left arrow if you are using a laptop. Then you can move focus to that window by pressing NVDA shift minus on the numeric pad if using a desktop or NVDA shift backSpace if using a laptop.
| |
| #make your changes or customizations to the filter, then press shift plus space bar or route the mouse (with NVDA slash on the numeric pad in desktops, or NVDA shift M in laptops) on the clear filter, add to selection, set selection buttons.
| |
| #press escape when you are finished to close the window.
| |
| | |
| == using the virtual midi keyboard==
| |
| | |
| Accessed by pressing alt plus b or from the view menu once inside a project, in other words, outside the midi editor, this keyboard will let you input midi notes by using the majority of the keys from your computer keyboard. However, its operation can be tricky at times because it sometimes offsets the range or scale you are using. So to set a range, you might try the following:
| |
| There's a text box labelled "Center note (right click a key to set):". If you get focus into that text box, you can delete what's there and type, for example, "c4". The tricky bit is getting focus into that text box and then getting it back into the keyboard. With NVDA:
| |
| #Ensure you have simple review enabled (default).
| |
| #With focus in the virtual MIDI keyboard, press NVDA's next object command twice (desktop: NVDA+numpad6, laptop: NVDA+shift+rightArrow).
| |
| #Press NVDA's move focus to review command (desktop: NVDA+shift+numpadMinus, laptop: NVDA+shift+backspace). This should focus the center note text box.
| |
| #Press control+a and delete to delete what's there, then type, for example, c4 to centre at note c4.
| |
| #Now, press NVDA's previous object command twice (desktop: NVDA+numpad4, laptop: NVDA+shift+leftArrow).
| |
| #Press NVDA's move focus to review command (desktop: NVDA+shift+numpadMinus, laptop: NVDA+shift+backspace). This should return focus to the MIDI keyboard.
| |
| | |
| Many thanks to Jamie (James Teh) for this information
| |
introduction
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
voiceover talks too much/makes too much noise!
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
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.
- 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.
Reducing Speech Verbosity
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
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
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 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 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:
- 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 ReaConsole (follow the link for an audio tutorial by Garth Humphreys) or see its corresponding documentation.
adjusting effect parameters
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
- 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.
- 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.