Notifications
Clear all

STANDALONE MODE SEQUENCER (Not sure why this works, but it does!!!) FOR BACKING TRACKS and Live Performance.

2 Posts
1 Users
0 Likes
562 Views
glenjdiamond
(@glenjdiamond)
Estimable Member
Joined: 1 year ago
Posts: 78
Topic starter  

I've been thinking about how to use Unify Standalone for Backing Tracks and I think I may have stumbled across something that appears to trigger embedded instrument layer MidiBox's using Upper Level MIDIBox's from a parent Unify layer  (Hopefully the pictures below will make more sense than my crude attempt at explaining this!!!).

 

1st Unify Layer - This has no sequencing in it.  It has an instrument layer set up for "Latch Mode" (and as we drill into it's layer we will reveal the sequencing trickery!!).

The other two instrument layers within the "1st Unify Layer" are nothing special - just a keyboard split for LOWER and UPPER for the live playing

 
The next screenshot is showing us how the LOWER live instrument layer is set up.  It has the "Follow Host" ticked in the transport layer just in case any LFO's are synchronised to the BPM.
 
It will be similar for the UPPER live layer.
 
The next screenshot is looking at the Latched Instrument Layer .  It is important that the "Follow Host" is NOT TICKED (leave it blank).  Manually set the BPM Tempo within the transport of this layer.  You will notice that there are two MIDIBOX's in the MIDI Layers.   These MIDI boxes are how we tell the instrument layers when to play  (one long note that lasts three bars , starting at bar one -- that will tell an instument layer to play it's own midi file for three bars and leave a break for the whole of the fourth bar).  So these SEQUENCER MIDI files act differently to instrument layer MIDIBOX MIDI files.  It doesn't matter what key is "note on" depressed, so long as a note is being played it will allow other MIDIBOX's further down the chain to play in sequence with the start of when the Latch was activated.
 
And the next two screenshots show how the MIDI files were set up.  One of them plays a long note from bar 1.1.1 to bar 3.4.68
The other MIDI file plays a shorter note lasting from bar 4.1.1 to 4.4.68
 

 

The next two screenshots show you how I use a drum machine to play the same set of drums.  Each layer has the same MIDI file (setup to only play one sound) to allow me to have different effects for each drum sound.

All the embedded instrument MIDI files are the same.  Except, that one pattern will play for bars 1/2/3  and a different pattern will play for bar 4.  This is because the previous layer had the sequencer MIDI files with the long notes.

 
 
So long as the initial "Latch" layer is activated,  the other MIDI files will keep looping.

I would think that you would need to expand the SEQUENCER MIDI files (the ones with the long notes in) to be the length of your composition.

If the SEQUENCER MIDI files are shorter than your compositional backing track,  they will just keep looping anyway until you press the Latch Key to stop and restart the backing track.

This technique isn't limited to drum tracks.  You could have other tracks for backing melodies.  And if you have a MIDI to DMX VSTi it will be possible to control DMX DJ lighting devices so that the lights react with your backing track.

 

   
Quote
glenjdiamond
(@glenjdiamond)
Estimable Member
Joined: 1 year ago
Posts: 78
Topic starter  

An Update...

If you look at the patches created for the ROLAND CR-78 DRUM MACHINE (in the section for sharing patches in this forum) you will find patches that do a similar job to the above, but instead of using MIDI files for the sequencing, they make use of BlueARP, then the lower level instrument layers have the actual MIDI files using MIDIBOX for each instrument layer with a macro knob for selecting tracks/patterns.


   
ReplyQuote
Share: