However, while you might not need to think about timeline sync, you do need to be aware of audio latency when using Reason as an external sound source. The audio buffer in Audio Preferencess determines how quickly you'll hear a sound from Reason after it's triggered from your external sequencer or controller. If this delay is a noticeable amount, sounds triggered in Reason will be out of time with other stuff you're sequencing. The simplest way to fix this is to set the latency of your audio driver as low as possible I try to never go above samples.
Your hardware sequencer may also have some way to offset MIDI timing to different outputs, but this doesn't help with live playing. However, because patching via the Rack interface is not part of the Remote system, you can't simply map learn any MIDI source to a device control with the usual Remote Override option.
The KeyStep Pro has a dedicated controller bank of five encoders. I configured the first of these to send on controller 79, and I set its MIDI channel to 4 to match the note track patched to the Malstrom. Now I can both sequence and automate the synth from my hardware.
Traditionally, the External Control buses have also been used to trigger Reason from other software apps running on the same computer, especially if they didn't support Rewire. Screen 4: As an alternative to using the Advanced MIDI Hardware Interface, single-channel sources can be locked to a specific device from the right-click menu.
The port will subsequently only communicate with that device, regardless of Rack or track selection in Reason. In fact, there's a couple of notable advantages to working this way. Firstly, you can take advantage of the MIDI control learning, in other words use the Remote Override Mapping feature to control parameters without having to look up and configure CC values on your hardware.
Secondly, you can record into Reason tracks. So why not go this route all the time? Connections via Remote and the Control Surface setup page are port-based. So you can direct or lock any MIDI port to a specific device, but can't specify a channel.
The External Control interface splits out each port to multiple channels and makes them available in the Rack. I suspect I could set up some clever filtering by connecting via a Retrokits host like their new RK In many cases this could mean routing it back into Reason, in which case you need to create a new audio track. With these steps completed you should find that sending MIDI from the EMI or its sequencer track triggers the hardware and the resulting sound plays through the audio channel you just created.
You will probably be able to hear the audio from the instrument without creating an audio track for it since it is playing through your interface, but to actually capture its output you will need to create a track to record it.
What you now have is an external instrument effectively integrated into your Reason Rack. The EMI has a few more tricks up its sleeve apart from simple triggering, pitch and mod wheels. To the right-hand side you will see a row of buttons, the first of which is for sending Program Changes.
Click on the up and down arrows here and you can cycle through presets on your external kit without having to leave your chair. As well as being useful for auditioning sounds, this can be automated like pretty much everything else, which can be very handy. Imagine that you want your drum machine to use one patch for one part of a song but a different one for another part.
Simply automate the Program Change control by [Alt]-clicking on it and changing the Program number at the relevant point during playback. The EMI gets a new automation lane in the sequencer, and you can use the Pen tool to manually draw in Program Changes or to edit existing ones.
Here we have told Reason to send a Program Change from preset 5 to 48 at a specific point. This means that on opening a project, Reason will automatically set any connected external instruments to the correct patch for the current song position. The next option down is CC Assign, and the knob is contextual depending on which of the available CCs you choose, meaning it can be set independently for each one.
Control messages like these are used for all MIDI kit to send various types of changes, such as sustain, velocity, breath and all manner of other parameters that can be controlled.
In order to see what each CC corresponds to you can try hovering the mouse over the knob with a specific CC number selected; alternatively, go to the Track Parameter Automation dropdown menu in the sequencer and click on it to see more clearly. You can customise CC assignment on your hardware by mapping specific CC numbers to parameters and so set up custom maps to automate anything you like from within Reason. Automation of CCs works in a very similar way to Program Changes, except that here you automate the knob when a specific CC number is selected.
Any changes that you enter while recording are now recorded as automation and can be edited as usual. Since each CC can have its own automation lane, you can theoretically have more than parameters being automated for each EM1.
0コメント