I tried to record a hi-hat using the auto-loop. I tried triggering the hat after recording started and and even before it started. No notes show up in the sequencer. I can hear the notes, but only during the first time I play it back.
I had that problem, too. The pattern had a note trigger (to start looping) at the beginning and a second note trigger (to stop looping) at the end. It worked for two times (when looping the song), but was completely out of sync after these two runs <!-- s:? --><img src="{SMILIES_PATH}/icon_e_confused.gif" alt=":?" title="Confused" /><!-- s:? -->
So for now I will only work with looped pads in live mode. As soon as I come to sequencing I switch back to one shot and trigger each event manually.
Quick question- (not at my iPad right now)
Is the auto looped pad sending midi out of the drum machine?
Until this is fixed we may need to use midi bridge to bring the midi data back into bm2 in order to record the auto looped pad.
Edit- just checked it out. Auto loop does not create midi data, nor does the auto loop seem to be in sync with the sequencer. It is obviously getting bpm info, but it needs to be synced withe actual sequencer. Intua?
I will clarify a bit how the auto-loop feature works in BM2.
The pad loops (ie: retriggers) internally, and no note messages are generated once auto-loop is started. So, if you record a pattern with a pad in auto-loop, only the Note ON messages are recorded. You will see one note; then, if you loop this pattern the pad will loop, stop, loop, etc.
Auto-loop mode was designed to be used while performing live.
On the other hand, for traditional sequencing, you can achieve the same result either by using the note repeat (transport->record settings), or by creating a pattern that will trigger the pad each time.
Also:
- Triggering an auto-loop will be quantized to the next sequencer position
- The "loop duration" settings also quantizes the stop duration
That is the design we have chosen, as it ruled out quite complex sequencing issues, and existing sequencer tools allows you to sequence as auto-loop would. This feature is definitely a live/performance solution <!-- s:) --><img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":)" title="Smile" /><!-- s:) -->
However, please do share your ideas to improve it in the future !
Also, I missed one important point ! Triggering of pads in auto-loop is dependent on global sequencer quantization. By default, we use 1/16th of a bar, and to change it, go into the "RECORD SETTINGS" via the transport bar, then change the "QUANTIZE" settings.
So, if you set it to 1 bar, the auto-loop pad will be trigger to the next bar.
I think you guys overcomplicated this auto-loop feature. It should work just like the one in Nanostudio. Also it should have more quantizing choices such as 1/32, 1/64, triplets, etc. that are available to choose from the drum machine module.
I love this new feature, and yes it is for performing LIVE.
My suggestion for improvement - Make the auto-loop quantize a separate setting from inputting midi notes. It can get a little hairy trying to remember to toggle between quantize settings, so a separate quantize value just for auto loops would be excellent. Also, one bar is almost always a good option for loop quantizing, but sometimes it's good to have 2, 4, 8 or even more bars so you can tweak FX during a build up and then the auto-loop finally drops. Make sense?
Comments
So for now I will only work with looped pads in live mode. As soon as I come to sequencing I switch back to one shot and trigger each event manually.
Is the auto looped pad sending midi out of the drum machine?
Until this is fixed we may need to use midi bridge to bring the midi data back into bm2 in order to record the auto looped pad.
Edit- just checked it out. Auto loop does not create midi data, nor does the auto loop seem to be in sync with the sequencer. It is obviously getting bpm info, but it needs to be synced withe actual sequencer. Intua?
I will clarify a bit how the auto-loop feature works in BM2.
The pad loops (ie: retriggers) internally, and no note messages are generated once auto-loop is started. So, if you record a pattern with a pad in auto-loop, only the Note ON messages are recorded. You will see one note; then, if you loop this pattern the pad will loop, stop, loop, etc.
Auto-loop mode was designed to be used while performing live.
On the other hand, for traditional sequencing, you can achieve the same result either by using the note repeat (transport->record settings), or by creating a pattern that will trigger the pad each time.
Also:
- Triggering an auto-loop will be quantized to the next sequencer position
- The "loop duration" settings also quantizes the stop duration
That is the design we have chosen, as it ruled out quite complex sequencing issues, and existing sequencer tools allows you to sequence as auto-loop would. This feature is definitely a live/performance solution <!-- s:) --><img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":)" title="Smile" /><!-- s:) -->
However, please do share your ideas to improve it in the future !
Cheers,
Mathieu
So, if you set it to 1 bar, the auto-loop pad will be trigger to the next bar.
Hope it's clear enough!
Cheers,
Mathieu.
My suggestion for improvement - Make the auto-loop quantize a separate setting from inputting midi notes. It can get a little hairy trying to remember to toggle between quantize settings, so a separate quantize value just for auto loops would be excellent. Also, one bar is almost always a good option for loop quantizing, but sometimes it's good to have 2, 4, 8 or even more bars so you can tweak FX during a build up and then the auto-loop finally drops. Make sense?
Thanks for bring us this awesome feature!