No VI Labs acreditamos que alguns instrumentos verdadeiramente pode inspirar e levar a sua criatividade para novos níveis. No cross-fading is necessary.O conceito e a tecnologia por trás do Ravenscroft 275 What is important, everything is controlled by MIDI, preserving natural behavior of all patches. Beside of this, Motif allows to modify the arpeggio patterns and tempos in real time using special buttons and wheel-style controllers. For me this a very inspiring way of combining many instruments, especially if some pre-defined arpeggios are simultaneously controlled using a second keyboard.
Ravenscroft 275 recording performance Patch#
You can make several such patch reassignments in one second. Steps (a,b,c) can be combined and recombined very quickly. One may argue that this is a limited way of patch control. In this way you can easily get co-sounding of 4 patches. Motif supports the following scenario for a single keyboard:Ī) You activate (connect to the MIDI controller by pressing one of 16 channel buttons) a Strings patch, play a chord, and sustain it by a pedal ī) While holding the pedal you activate a Piano patch, play anything using the keyboard and another sustain pedal, then, while holding both pedals, you activate Oboe patch Ĭ) You play some Oboe phrase and then, holding some Oboe note, you activate Clarinet patch and play something (using another hand or non-occupied fingers).
to control two sounds I use two keyboards with independent patch selection.ġ: Agree, this may require more than 2 processor cores.Ģ: Yamaha Motif MULTI/Seq mode provides a deeply thought-of interface for creating live co-sounding of more than 2 instrument patches from a set of 16 prepared patches (out of thousands available for Yamaha S90XF or MOXF8). I am very happy with LiveConfigs, that simply does a fade-out and then fade-in to avoid cracks when switching patches. OTOH, I don't see how I should be able to control more that two instruments within a short period of time. Of course if you need multiple instruments at the same time in a live situation, you need to provide the CPU power to run all of them, concurrently. This solution would make unnecessary the crossfaders, which may unnaturally affect the VSTi functionality. Esc), which works as follows: "Send Release Pedal message to all tracks but that which currently is connected to the MIDI controller". The solution would be assigning a special pedal or computer keyboard button (e.g. Since current MIDI controller assignment is piano, we cannot send Pedal Off message to violin track by using the pedal. Here is the difficulty and the room for elegant solution. However, when playing the piano part, the user may wish to stop the sustained violin note (release the pedal for violin only). They allow to press a violin note, sustain it by pedal, then activate piano and play an unconstrained piano part which co-sounds with the sustained violin note. I analyzed some multi-instrument DPs by Roland, Yamaha and Kawai. Row tracks should be linked/unlinked to the MIDI controller by pressing computer keyboard button P (for piano) and V (for violin).Īn interesting moment here is the usage of sustain pedal.
The showcase would help to better understand LiveConfigs for many users who wish to control two or more VSTi-s simultaneously in a live performance. LiveConfigs seems to be a powerful tool, but to tell you the truth, figuring out what it is by reading current docs is a difficult task, at least for me. Will it be too daring if I ask you to showcase cfillion's idea in the doc as the example - including all menu clicks and text-box filling details?
Ravenscroft 275 recording performance update#
That is why on request of "Pipe" I developed a set JSFXes and ReaScripts that works similar to LiveConfigs, but (while needing more effort for configuring the system and providing a lot less versatility) allows for smoothly switching between multiple tracks, providing "spillover" by doing an appropriately delayed mute to the now unused track.ĭue to the incomplete documentation, I never understand the concept of "Input Track" in LiveConfigs.Ĭan you give a complete definition of this, so that I can update the enhanced documentation I id for LiveConfigs ? In fact LiveConfigs introduces a small fade-out / fade-in gap to prevent a harsh crack. That is why I can have lots of tracks with lots of plugins in "standby" and can activate them by pushing a button.Ī potential problem is that this results in not to be able to ever hear both the to-be-unarmed and the to-be-armed track at the same time, preventing "spillover" and cross-fading. In Reaper, mute can be configured to stop the track's plugins from using any CPU time. I happily use LiveConfigs to mute / unmute tracks for patch selection when performing live. I don't understand why you want to arm / unarm tracks.