Does "Auto" Input Quantization "apply" when recording MIDI into a Launcher Cell? (Like when recording a normal MIDI clip in the Arrange window)?

[Vocalpoint]

Anyone see anything odd with this function?

Does this functionality simply not apply to the Launcher (simply because it is v1.0.0) or it supposed to - but does not actually work.?

Would love any reports from the crew.

VP

 

[sintil8]

Tried with an external sequencer running at Q 1/32 beats with notes set at timing after the 1/4 beat.
Set SO1 to Q 1/4 input Q on, did not quantize for me, so from what I see *no* it does not Input Quantize. Notes recorded same position as the
external sequencer had them.
Maybe my methodology is wrong, if you have any thoughts/suggestions I could look at it again?
Hope someone else can pick up and try, see if they can get it working and say it's pilot error, or the best bet, it's as you say V1.0.0 in the making.
Regards

 

[Vocalpoint]

That is good enough for me Thank you.

I think this "restriction" should have been noted somewhere as a Known Issue. I would think this would be an important oversight if you are used to recording your MIDI with Input Quantize on.

As such - I can draw no other conclusion except that this must be Launcher v1.0.0 and none of the fancy stuff is yet connected.

If anyone else can comment - would be valuable.

VP

 

[lokeyfly]

I've recorded from the clip launcher outputting clips and such, but I've not recorded into the clip launcher, input quantize on or not. I didn't even know that was a thing. Sintil8 says he recorded off of an external sequencer, so I'm wondering were the tempos matched? I suspect they were. So then how does input quantize play in to something from an external sequencer into the clip launcher, unless the tempo wasn't the same. If the sequencer was completely external such as to an input track, was it clocked or tempo matched? Quantization can only do so much when tempo is off, anyway.

I guess I'll have to record using the clip launcher. Huh! (curous). I've only dragged track/arrangement events into the launcher, or recorded from the launcher.

 

[Vocalpoint]

I've recorded from the clip launcher outputting clips and such, but I've not recorded into the clip launcher, input quantize on or not. I didn't even know that was a thing. The OP says he recorded off of an external sequencer, so I'm wondering were the tempos matched? I suspect they were. So then how does input quantize play in to something from an external sequencer into the clip launcher, unless the tempo wasn't the same. If the sequencer was completely external such as to an input track, was it clocked or tempo matched? Quantization can only do so much, anyway.

I guess I'll have to record using the clip launcher. Huh! (curous).

You gotta get going . Recording INTO the Launcher is where the fun really starts.

VP

 

[lokeyfly]

You gotta get going . Recording INTO the Launcher is where the fun really starts.

VP

Ok, deal! Btw, I fixed in my comment that Sintil8 had external sequenced.

Looking forward to exploring that.

 

[sintil8]

I've recorded from the clip launcher outputting clips and such, but I've not recorded into the clip launcher, input quantize on or not. I didn't even know that was a thing. Sintil8 says he recorded off of an external sequencer, so I'm wondering were the tempos matched? I suspect they were. So then how does input quantize play in to something from an external sequencer into the clip launcher, unless the tempo wasn't the same. If the sequencer was completely external such as to an input track, was it clocked or tempo matched? Quantization can only do so much when tempo is off, anyway.

I guess I'll have to record using the clip launcher. Huh! (curous). I've only dragged track/arrangement events into the launcher, or recorded from the launcher.

OXI One hardware sequencer ... synced via Midi clock over usb from SO1 clock
The Oxi was set at 1/32 beats per bar the record Q input in SO1 set at 1/4.
I set the beats 1/32 after the 1/4 on the Oxi and expected SO1 to Q them to the 1/4 beat in SO1 but they were recorded in SO unquantized ?

As I said earlier if there is something I have missed some factor in what I did is off please advise. I am not infallable

For the curious, it's as a sketching tool i use.
Oxi One prototype reviewed by Loopop, Cut to the pro's and con's at around 25 mins for an overview.

Review: OXI ONE Sequencer // Generative features explained

Get the ideas, tips and insights from this video and all my others in my ever-expanding book of electronic music ideas, tips and tricks here: ► Patreon: ...

www.youtube.com

it's had numerous HW updates since the review and it's a bit of a Swiss army knife and can operate as a midi to CV hub. The developer is very responsive and active on his discord server. Fun stuff you can sorta do with it...

OXI ONE Ambient, Drone, Beats, Melodic Lines

Live Dawless Eurorack Jam: Ensemble Oscillator, Bastl Pizza, Vector Wave, Poly Cinematic, Basimilus and Knit with OXI ONE & Frap Tools USTA – alternate betwe...

www.youtube.com

Music is the best, regards.

 

[Trucky]

Anyone see anything odd with this function?

Does this functionality simply not apply to the Launcher (simply because it is v1.0.0) or it supposed to - but does not actually work.?

Would love any reports from the crew.

VP

It's been reported so hopefully they can get this working.

 

[sintil8]

Hi Trucky,
thank you,

I have been trying various combinations of Q settings in both the main window and the edit window, and I'm experiencing the disconnect between when the Launcher starts recording and where the midi time is in the bar.
There is the time lapse from when when the launcher starts and the H/W sequencer starts playing (to be expected) SO 1 being the master and the H/W slave.

The following might not be that easy to follow so bare with me on this...you can kick my RRR's later.
Clicking the record blob in the Launcher cell is (guessing here) not locked to a clock/bar or beat and looks like it has it's own clock running albeit synced in some way.

The Dev's might be able to glue this together by having a Launch play/record Quantize setting timer ?
Recording starts synced to a Q factor that folk can set. On the bar or 1/4, 1/8, 1/16 note whatever individual folk are comfortable with.
With a click running the rec input quantize clocks would have a chance to sync, in a similar fashion to a pre roll before the play/record head starts.
At the moment I am Launching the cell by mouse clicks so it's a bit hit and miss and most of what I am seeing could be my timing being off ?

Just some thoughts I had. Lets hope the Dev's can sprinkle some SO1 magic dust over this.

Regards

 

[lokeyfly]

OXI One hardware sequencer ... synced via Midi clock over usb from SO1 clock
The Oxi was set at 1/32 beats per bar the record Q input in SO1 set at 1/4.
I set the beats 1/32 after the 1/4 on the Oxi and expected SO1 to Q them to the 1/4 beat in SO1 but they were recorded in SO unquantized ?

Best I can tell, there's a limit on the quantization so having a sequencer with very stringent note on info at 1/32 beats per bar, and S1 having to then quantize to 1/4, it's likely not seeing stray notes of some other ticks to have to correct. S1 may be seeing the notes as already on unless they need to be corrected? Sort of like iterative quantize. I would still as you do, expect the notes to move to the nearest quarter. If I purposely set a few notes off, they will however correct. Only not to the position I would expect (more on that, below).

Ok, follow up. I ran stepic as a sequencer, driving a synth, at 1/32. Then created an audio track with input quantize set to quarter notes. I don't see correction taking place to the audio track. I will tell you, I'm no expert on Studio One's quantization. In fact, it's probably the one thing I dislike if I could pick one item. Even trying to purposely set notes off on the MIDI track (sometimes as much as over 1/16 to 1/8 , then highlight all notes (or not), quantize to 1/8 and Studio One quantize will even bump notes backward, instead of correcting to the closer one-eighth note. It's such a frustrating proposition that I don't even bother. In other DAW's quantize works the way I expect. It's truly been a puzzling experience.

So to assist in your question, I can't even get out of my own way with quantizing. Ugh. : )

Probably validates why I rarely if ever quantize with Studio One.

I see now Trucky's comment that it's being looked at. I hope they look thoroughly.

 

[sintil8]

So to assist in your question, I can't even get out of my own way with quantizing. Ugh. : )

Yes, me too, although it's too early in the life cycle of the Launcher to be overly critical and as you have said, I also hope they take a thorough look.
Just one coment. The oddity is the arrange widow can handle it, so my position at the mo' is record to the arrange window if I want or need timing to be on point. Other than that learn to live with the happy accidents that happen.

All the best, regards.