Real time sequencer AUM?

RajahP

@midiSequencer said:

@Samu said:

@midiSequencer said:

Bpm is curious - I can record host BPM but I'm not sure I can alter the host bpm from an AU - probably can from Link.

Tempo Division / Multiplication per pad might be an option here?

for playback yes (so you can play x2 speed say) - but my question above relates to recording bpm changes in realtime and playing them back - I can record them but not play them back to AUM say. Need to investigate some more

Patterning 2 is supposed to send out tempo change and control host tempo thru Ableton Link... (well, that’s what they told me...)
Maybe Ableton Link is the key here..

Edit... but then Patterning 2 is not AU..

Will

@midiSequencer said:

@Samu said:

@midiSequencer said:

Bpm is curious - I can record host BPM but I'm not sure I can alter the host bpm from an AU - probably can from Link.

Tempo Division / Multiplication per pad might be an option here?

for playback yes (so you can play x2 speed say) - but my question above relates to recording bpm changes in realtime and playing them back - I can record them but not play them back to AUM say. Need to investigate some more

A version 2 or 3 problem if'n you asked me. Of course, you didn't.

Will

@midiSequencer said:

@breilly said:
Awesome! Totally gonna help the work flow, and thx for including “without fixed length”, fantastic for ambient jammin off the grid👍🏼

yeah unlimited will just act as a recording - you press the record button to start/stop it(or automate it).

With a length dialled in it will record that many beats (or maybe bars I'm thinking) then auto load into the AU render part that can output the midi.

It also pads out the length to that recorded (so its a fixed beat length even if you only record 1 note). This way its easier to sync & easier to just drop into your tracks in other apps.

If you record without a fixed length and have it loop after recording, does it pad the recording? Or will it just loop what it has recorded?

jaymoreaya

Looking through this thread again, I think it’s planned that this will also include cc value recording and “one shot” playback option?

This would then allow me to trigger prerecorded midi drum fills & filter sweeps on fly. All this on top of being the key to turning iPad from a groove machine to a spontaneous song creation machine.

Could be the app of 2018 right here.

wim

@jaymoreaya said:
Looking through this thread again, I think it’s planned that this will also include cc value recording and “one shot” playback option?

Oh yeah, definitely +1 for “one shot”playback option. Or, even better, a loop count selector or chaining option similar to Rozeta.

Scope creep.

Korakios

@midiSequencer
Is it possible to add a slider for speed control (going wild up to x8!) including negative values (reverse) ?

The free rec sounds great ! Most apps make you waste time to set a fixed length before recording.... Will it be quantized so it loops perfectly?

[Deleted User]

@midiSequencer said:
AUV3 midi recorder.
You can record midi (notes, ccs, sysex etc) - quantise it as you are recording, filter by channel into a buffer.
You can trigger recording from first note or first midi message.
Save it to the app documents folder as a .mid file (standard type 0).
Share it using airplay to apps like Mail or Audioshare.
Load it from the documents folder to the buffer.

The above is all completed.....

I then have some pads ready (just 4 for now, lit when populated) - you will be able to load tracks to these and trigger them (they play out of the AUv3 midi along with your input) - so you can use this as a looper (there will be some looping options).

So basically this gives you the ability to record, playback & manage your recordings as midi files to share with other apps.

I little late but I just wanted to appreciate this. Looking forward to it.
I downloaded Quantum yesterday and I'm impressed.

midiSequencer

@RajahP said:

@midiSequencer said:

@Samu said:

@midiSequencer said:

Bpm is curious - I can record host BPM but I'm not sure I can alter the host bpm from an AU - probably can from Link.

Tempo Division / Multiplication per pad might be an option here?

for playback yes (so you can play x2 speed say) - but my question above relates to recording bpm changes in realtime and playing them back - I can record them but not play them back to AUM say. Need to investigate some more

Patterning 2 is supposed to send out tempo change and control host tempo thru Ableton Link... (well, that’s what they told me...)
Maybe Ableton Link is the key here..

Edit... but then Patterning 2 is not AU..

@RajahP said:
Maybe Ableton Link is the key here..

Edit... but then Patterning 2 is not AU..

Link is great as it is cross application and keeps things in sync. The host transport is not always running

SpookyZoo

@midiSequencer said:
does it need to be in the fx slot? What about auv3 midi - I have something nearly completed.....

Awesome! How did I miss this whole thread!?

You have my test flight!

midiSequencer

@syrupcore said:

If you record without a fixed length and have it loop after recording, does it pad the recording? Or will it just loop what it has recorded?

At the moment it doesn't pad (out to the beat or bar) mainly as it will be used more for quick take recording than looping.
Also, read midi files can odd lengths too - so having a clip thats not rounded off implies that the best way to handle this is in the pad (where you load a midi track).

Pads (with their assigned midi clip of any length) will have functions to quantise(note start, duration), non-destructively truncate/extend (e.g. it plays only a portion of the clip or repeats the clip until your defined length is reached), loop (in interesting ways like backwards).

This way the app is first an foremost a quick recorder and secondary (where I intend to add most of the functionality) a pad playing clip looper.

There wil be options to set for record (start on any midi key, start on any midi event, start now, loop when recorded, quantise during record etc).

midiSequencer

@jaymoreaya said:
Looking through this thread again, I think it’s planned that this will also include cc value recording and “one shot” playback option?

This would then allow me to trigger prerecorded midi drum fills & filter sweeps on fly. All this on top of being the key to turning iPad from a groove machine to a spontaneous song creation machine.

Could be the app of 2018 right here.

Anything midi sent by the host to my app should be recorded (namely midi note on/off, cc, nrpn, rpn, Program changes, aftertouch maybe even sysex) and also host bpm changes. So midi CC values will be recorded too.

The one-shot playback option will be an option of playing back pads (midi loaded into the app & assigned to a pad). I see a lot of cool functions I can offer on pad playing (#times, transpose etc). Playback will include any midi message in the midi track (notes, ccs etc).

midiSequencer

@wim said:
Oh yeah, definitely +1 for “one shot”playback option. Or, even better, a loop count selector or chaining option similar to Rozeta.

Scope creep.

Record & loop will be the main functions so yes I'm intending to give you control over how a pad plays back. Chaining will be possible, maybe not at the initial launch - but yes a row of pads would then naturally pass play onto the next in the row. I will add this when I increase the number of pads.

midiSequencer

@tiantong said:
I little late but I just wanted to appreciate this. Looking forward to it.
I downloaded Quantum yesterday and I'm impressed.

thx - I'm known for adding a lot of functionality in my apps especially where midi is concerned!

midiSequencer

@SpookyZoo said:

@midiSequencer said:
does it need to be in the fx slot? What about auv3 midi - I have something nearly completed.....

Awesome! How did I miss this whole thread!?

You have my test flight!

I do. Hoping to get a beta out later in the week. Not taking any more beta testers at the moment though.

espiegel123

When you implement the clip looper, please make it possible to loop arbitrary clip lengths , independent of the master tempo so that one can have multiple instances that can play unsynched loops.

[Deleted User]

@midiSequencer said:

@syrupcore said:

If you record without a fixed length and have it loop after recording, does it pad the recording? Or will it just loop what it has recorded?

At the moment it doesn't pad (out to the beat or bar) mainly as it will be used more for quick take recording than looping.
Also, read midi files can odd lengths too - so having a clip thats not rounded off implies that the best way to handle this is in the pad (where you load a midi track).

Pads (with their assigned midi clip of any length) will have functions to quantise(note start, duration), non-destructively truncate/extend (e.g. it plays only a portion of the clip or repeats the clip until your defined length is reached), loop (in interesting ways like backwards).

This way the app is first an foremost a quick recorder and secondary (where I intend to add most of the functionality) a pad playing clip looper.

There wil be options to set for record (start on any midi key, start on any midi event, start now, loop when recorded, quantise during record etc).

🤤🤤🤤

[Deleted User]

Looking at the screenshot, the MIDI files are called quicksave1, 2, etc. Just point out AudioBus' great auto-name function. I don't know if it's been mentioned here before but to me it proves how small things make a difference.

Korakios

@midiSequencer said:

@syrupcore said:

If you record without a fixed length and have it loop after recording, does it pad the recording? Or will it just loop what it has recorded?

At the moment it doesn't pad (out to the beat or bar) mainly as it will be used more for quick take recording than looping.
Also, read midi files can odd lengths too - so having a clip thats not rounded off implies that the best way to handle this is in the pad (where you load a midi track).

Pads (with their assigned midi clip of any length) will have functions to quantise(note start, duration), non-destructively truncate/extend (e.g. it plays only a portion of the clip or repeats the clip until your defined length is reached), loop (in interesting ways like backwards).

This way the app is first an foremost a quick recorder and secondary (where I intend to add most of the functionality) a pad playing clip looper.

There wil be options to set for record (start on any midi key, start on any midi event, start now, loop when recorded, quantise during record etc).

Reverse sounds great
But I think I did not understand the free recording mode . Let’s say I hit rec and start recording , if I press rec again will the recording stops immediately or it will stop to the closest beat ? (Hope for the second)
And will the recorded midi ,play immediately?

[Deleted User]

We are obviously all very excited....lets let
https://forum.audiob.us/profile/midiSequencer
do his thing and take it from there.

j_liljedahl

@midiSequencer said:

@Samu said:

@midiSequencer said:

Bpm is curious - I can record host BPM but I'm not sure I can alter the host bpm from an AU - probably can from Link.

Tempo Division / Multiplication per pad might be an option here?

for playback yes (so you can play x2 speed say) - but my question above relates to recording bpm changes in realtime and playing them back - I can record them but not play them back to AUM say. Need to investigate some more

There's no part of the AUv3/IAA API to set the host BPM. For IAA there's RemoteControl events, where the standard lists toggle play, rewind, toggle record.

However, a built-in MIDI player in a host could of course make use of a "tempo track" in the MIDI file.

midiSequencer

@espiegel123 said:
When you implement the clip looper, please make it possible to loop arbitrary clip lengths , independent of the master tempo so that one can have multiple instances that can play unsynched loops.

yes tempo sync will be off, host or Link. With off you can launch your clips as soon as you touch the pad, other sync options wait.

midiSequencer

@tiantong said:
Looking at the screenshot, the MIDI files are called quicksave1, 2, etc. Just point out AudioBus' great auto-name function. I don't know if it's been mentioned here before but to me it proves how small things make a difference.

those were names I typed in - you can pick your own. I'm also going to allow naming of pads too so we know whats in them.

midiSequencer

@Korakios said:
Reverse sounds great
But I think I did not understand the free recording mode . Let’s say I hit rec and start recording , if I press rec again will the recording stops immediately or it will stop to the closest beat ? (Hope for the second)
And will the recorded midi ,play immediately?

Yeah I have a list of midi messages & a known length of the clip, so its simple to play the clip in reverse or even alternate (fwd/back etc).

I've just changed 'free record' to extend the clip to the nearest beat rather than have odd lengths like 7.56784 - it will make looping much better.

Yes the order is:
1) setup the recording options you want (if not already)
2) tap Rec button - with three options (rec immediately, wait for midi key, wait for midi event) then it starts recording into the buffer
3) tap record again - it stops recording, tidies up, makes it available to the AU
4) If a pad is selected before record thats where it goes & it plays asap (it needs to copy to an efficient buffer in the AU as midi files don't have note off - just noteon+duration).

There will be options on the pad about how it plays (e.g. to truncate/extend it, loop options, play immediately or not etc). I'm working on these next.

My performance tuning is to ensure the AU can output the midi asap.

midiSequencer

@j_liljedahl said:
There's no part of the AUv3/IAA API to set the host BPM. For IAA there's RemoteControl events, where the standard lists toggle play, rewind, toggle record.

However, a built-in MIDI player in a host could of course make use of a "tempo track" in the MIDI file.

thats a shame - Link would allow this though by 'proposing a bpm' but yes I can't influence AUM host tempo myself.

I'm recording AUM host tempo changes directly into the midi tempo track so any app (IOS or pc etc) that can act on the tempo track could use it.
I might be able to replay these back via Link.

ttk

@midiSequencer said:

@Korakios said:
Reverse sounds great
But I think I did not understand the free recording mode . Let’s say I hit rec and start recording , if I press rec again will the recording stops immediately or it will stop to the closest beat ? (Hope for the second)
And will the recorded midi ,play immediately?

Yeah I have a list of midi messages & a known length of the clip, so its simple to play the clip in reverse or even alternate (fwd/back etc).

I've just changed 'free record' to extend the clip to the nearest beat rather than have odd lengths like 7.56784 - it will make looping much better.

Yes the order is:
1) setup the recording options you want (if not already)
2) tap Rec button - with three options (rec immediately, wait for midi key, wait for midi event) then it starts recording into the buffer
3) tap record again - it stops recording, tidies up, makes it available to the AU
4) If a pad is selected before record thats where it goes & it plays asap (it needs to copy to an efficient buffer in the AU as midi files don't have note off - just noteon+duration).

There will be options on the pad about how it plays (e.g. to truncate/extend it, loop options, play immediately or not etc). I'm working on these next.

My performance tuning is to ensure the AU can output the midi asap.

Hello @midiSequencer ,

Out of curiosity, how do you see your idea, compared to the existing Infinite looper?

I personally struggle with its limitations regarding the recording of cc messages, maybe your app can add something new, indeed.

Mayo

@midiSequencer said:

I've just changed 'free record' to extend the clip to the nearest beat rather than have odd lengths like 7.56784 - it will make looping much better.

But how does this work as a phrase / or idea looper without being chained to a BPM?
If it rounds it off to the nearest beat, then the recording needs to be done to a specific BPM.

It would be a joy to have the option to cycle patterns that are free of being locked on the grid

Korakios

@Mayo said:

@midiSequencer said:

I've just changed 'free record' to extend the clip to the nearest beat rather than have odd lengths like 7.56784 - it will make looping much better.

But how does this work as a phrase / or idea looper without being chained to a BPM?
If it rounds it off to the nearest beat, then the recording needs to be done to a specific BPM.

It would be a joy to have the option to cycle patterns that are free of being locked on the grid

I don’t understand the question ....

j_liljedahl

@midiSequencer said:

@j_liljedahl said:
There's no part of the AUv3/IAA API to set the host BPM. For IAA there's RemoteControl events, where the standard lists toggle play, rewind, toggle record.

However, a built-in MIDI player in a host could of course make use of a "tempo track" in the MIDI file.

thats a shame - Link would allow this though by 'proposing a bpm' but yes I can't influence AUM host tempo myself.

I'm recording AUM host tempo changes directly into the midi tempo track so any app (IOS or pc etc) that can act on the tempo track could use it.
I might be able to replay these back via Link.

IMHO, AU plugins should only use host sync, not Link. Leave Link up to the host! Otherwise confusion will be there, also it's better to keep plugins as lightweight as possible. A plugin is not supposed to be able to control the host in any way more than sending it audio and MIDI. We could figure something out for controlling AUMs tempo via MIDI, maybe there's some standard SysEx message for that, for example.

david_2017

I think this question is regarding some quantizing options? e.g. NO quantizing?

Mayo

Exactly - loops with no quantizing, and loops with.
To be able to mix the two would really be the best (like you can on any DAW).