Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
wiki:hosting_atom_2_in_ns2 [2021/05/03 03:24] – MisplacedDevelopment | wiki:hosting_atom_2_in_ns2 [2021/05/14 22:55] (current) – MisplacedDevelopment | ||
---|---|---|---|
Line 17: | Line 17: | ||
{{ : | {{ : | ||
- | If you intend on recording MIDI rather than manually adding notes in Atom then I recommend that you create a second instance of Atom 2 for each track. | + | If you intend on recording MIDI rather than manually adding notes in Atom then I recommend that you create a second instance of Atom 2 for each track. This will be explained in more detail later on but you will use the second instance for recording and the first for triggering: |
{{ : | {{ : | ||
+ | |||
+ | **Edit/ | ||
===== Initial setup ===== | ===== Initial setup ===== | ||
Line 68: | Line 70: | ||
The second pattern switch note added is C#2 (49). This will cause “Pattern 2” to be switched to for the second instance of the trigger note C4 (72). Having the second trigger note C4 (72) forces the playhead to return to the start after switching to “Pattern 2”. | The second pattern switch note added is C#2 (49). This will cause “Pattern 2” to be switched to for the second instance of the trigger note C4 (72). Having the second trigger note C4 (72) forces the playhead to return to the start after switching to “Pattern 2”. | ||
+ | |||
+ | **Important** If a pattern change is not happening as expected then try removing the pattern change note and re-add it, or move it forward one step and then back to its original point in the timeline. | ||
**Note** The pattern switch notes mark state changes and so the length of those notes is not significant. | **Note** The pattern switch notes mark state changes and so the length of those notes is not significant. | ||
Line 247: | Line 251: | ||
===== Advanced Topics ===== | ===== Advanced Topics ===== | ||
+ | ==== Recording MIDI ==== | ||
+ | To record MIDI from Atom you will need the excellent MIDI Tools app https:// | ||
+ | |||
+ | Decide where you want the recorded notes to be sent to. This might be a new track which sends to the instrument track, or might be the instrument track itself. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Add the MIDI Route plugin **after** the Atom instance that you want to record: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | I think by default the plugin will point to NanoStudio 2 so all you need to do is ensure that the MIDI channel that is being sent to matches the MIDI channel of the track you set up above. | ||
+ | |||
+ | Hit record in NS2 and the output of Atom will be routed by MIDI Route to the NS2 channel and recorded into the track listening on this channel. | ||
+ | |||
+ | If you are using an iPhone then MIDI Route is not available but you may be able to use this workaround: | ||
+ | |||
+ | https:// | ||
+ | |||
+ | ==== Alternative (better?) workflow ==== | ||
+ | Since writing the initial version of this guide I have changed my workflow so that every instrument has a control track which contains a single Atom instance - no secondary Atom instance is used for recording. | ||
+ | |||
+ | To record I set up a blank pattern in the control track Atom instance and loop the part of the song I want to record over. I then open AUM and record into Helium or Atom attached to the NS2 port for the instrument I want to record for, which lets me hear exactly how the recording will sound and has the advantage of being able to hear the lead in bars for that instrument. | ||
+ | |||
+ | **Tip:** To quickly get a recording from Helium to NS2/Atom - save to the Media Bay, long press on the new MIDI clip and with your finger held down, use the other hand to navigate to the Atom instance in NS2 containing the empty pattern you set up earlier. | ||
+ | |||
==== Using Slate to trigger patterns ==== | ==== Using Slate to trigger patterns ==== | ||
- | As you saw earlier, Slate kits allow you to name pads and these names appear in the piano roll. Using this information we can create a simple Slate kit that does not actually contain any sound but can be used to more easily add patterns to controller clips. The downside to this approach is that you end up with double the number of tracks and I’m not sure it is really worth the hassle but some may find it useful, especially if you create an NS2 template which has all of this set up by default. | + | As you saw earlier, Slate kits allow you to name pads and these names appear in the piano roll. Using this information we can create a simple Slate kit that does not actually contain any sound but can be used to more easily add patterns to controller clips. |
Create a Slate track and then create an Init kit in the Slate editor: | Create a Slate track and then create an Init kit in the Slate editor: | ||
Line 258: | Line 288: | ||
{{ : | {{ : | ||
- | Now you can assign useful names to the notes. | + | Now you can assign useful names to the notes, or just label the controller as the others will automatically be numbered. Pad 25 should be labelled as the controller note as this is by default C4 (72). If you used the suggested default “Root Offset” setting then you will find that this starts at pad 1 which defaults to C2 (48): |
{{ : | {{ : |