Clip Launch - Randomize, and other needed features

[Vocalpoint]

I'm basically collecting feature requests so "Crop to Content" was an idea for a possible implementation. If this will be called "Consolidate" or "Crop to Content" and if it's a range selection or the loop range shouldn't really make a difference, workflow-wise.

If you are collecting suggestions - that is VERY exciting news to me.

"Crop to Loop Range" makes more sense if we are talking S1/Launcher specific parlance.

Logically - if I was designing this - "Crop to Content" would be instantly confusing to me since a cell can be filled with a bunch of "content" and I (usually) only want a very specific piece of it.

"Crop to Content" - has no implied start/end point (as in which "content" are we actually talking about?)

VP

 

[lokeyfly]

Updated 10/29/25 8:30 pm EST

Studio One - Recommended Additions.for Clip Launcher
by the Studio One User Forum members.
To: The Presonus Studio One Development Team

Scope: By adding the following features to Studio One's Clip Launcher. These items (and even some not listed here) would ensure the user experience is greatly enhanced. Providing more choices that include additional dedicated recording functionality through the clip launcher itself. Thereby allowing more ways for clips, scenes, and playlists to interact with each other. This list can and should be an exciting path to utilize Studio One's superior drag and drop virtues, via Control Link, and superior in-line workflow. Only now, with greater choices through the Clip Launch panel.

Existing items in clip launch in Studio One:
-Play Mode
•Loop
•One Shot
-Launch Mode
•Global
•Global trigger
•Gate
•Toggle
-Quantize
-Cut/Copy/Paste

Newly requested items for clip launch in Studio One: (please locate where they pertain)
•Randomize (with %, # of skips, scale enhanced, etc.)
•Set Clip Size (X times)
•Half Clip Size (includes 1/8, 3/4, etc)
•Stop ALL, and Return To (specify X)
•Do nothing (X times)
•Play Previous clip (X times)
•Play Next clip (X times)
•Play Next group (jump X times)
•Play Previous Group (jump X times)
•Consolidate (see note 1)
•Color/symbol I.D. (see note 2)
•Set active ready record button to all clips, scenes, playlists (next to play button)
•Set Clip record length (per grid, loop start & end points, or takes to layers)
•Record control (see note 3)
•Trigger notes, CC's send/recv (see note 4)

Notes: (unless otherwise specified)
1. Consolidate - by either [crop to content], or [range select]

2. Color Identifier - User can add a color to the interior look of the clip. A 16 color swatch should be enough. The outer border color of the clip remains as per same event color as its origin. (no color change).
Or, clip contains some related symbol as is the case with events (at bottom left). Color, or symbol is to enhance visualization of the clip launch matrix. Note: Even templates could be furnished for suggested or user preference.

3. Record control on each clip allows for active punch-in / punch-out recording to takes, or passes of that clip. Very expressive and exists in competing clip launchers from others. Resultant recording is printed to the recorded event, and may (if selected), create takes to layers from loop limits, or clip length size.

4. Trigger notes, or send/recieve MIDI controller data would likely require some panel (selection dropdowns) for selecting the necessary data to send or recieve on. It would also be potentially useful (workflow wise) to include the Control Link to speed up intended selections. The ability to trigger clips via external controller, mouse select, or automation are enormous. Note: Competing clip launchers from others are utilizing this.

Final thoughts:
It's with passion, and supporting input by many Studio One users to add substantial clip launch enhancement as listed above. We, [participants] at the Studio One User Forum, have witnessed countless requests for clip launch development.

Perhaps some of these features such as randomization, percentage and skip (jump) could be implemented into other tools such as the Arpegiator, and Chorder. A huge thanks for consideration and in the hopes that these and other features find their way into Studio One. Making a great DAW, even better given its already many attributes. Thank you.

 

[Vocalpoint]

Will also add "post recording actions" to the list.

To see what sort of mayhem is possible - check this vid starting at around 3:48 to get a feel for what Mattias does with this:

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

Bitwig allows the user to set a Post Recording Action AND a post recording delay - so when he hits Record on a cell - the cell records for 4 bars and then automatically switches to Play mode - putting the user into this cool non-stop creation mode where cell after cell is recorded and then plays back - adding layer upon layer to the proceedings - live and as fast as one can play an idea in.

Cooler than cool - for me anyway.

VP

 

[sintil8]

Something for the generative randomness of it all. Lokeyfly. food for thought.

Taches doing his thing, the 1st 10 minutes gives an alternative way of generating controlled randomness.

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

The later half is about capturing that randomness, so you regain control of your artistic license of the final cuts and outcomes.

Regards to all

Edit: Addendum
Just to give you a bit of insight to what is going on as it can be a little chaotic to understand if you are not familiar with Bitwig.
Bitwig can display it's Clip/Launcher grid in both Track view and also a vertical view (track view SO1 style seen later at 12-00 min)

Pause at 4-08 and again at 12-34 to see a list of functions for clip follow actions.

At 13-22 all the grouped cells are editable together as a stack ( Which confuses me no end but there ya go thats Bitwig )

I'm sure you can grasp this next one but just in case.
At 18-10 there is an operator engaged at 44 % notes in a chord are being randomized so the notes in the chord are diffrent combinations of notes.
This I find interesting as it makes a ground or atmospheric sound move in a subtle way.

Hope this helps you engage with what is going on. I do like the Midi routing in Bitwig it's very versatile.

Regards

 

[lokeyfly]

Will also add "post recording actions" to the list.

To see what sort of mayhem is possible - check this vid starting at around 3:48 to get a feel for what Mattias does with this:

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

Bitwig allows the user to set a Post Recording Action AND a post recording delay - so when he hits Record on a cell - the cell records for 4 bars and then automatically switches to Play mode - putting the user into this cool non-stop creation mode where cell after cell is recorded and then plays back - adding layer upon layer to the proceedings - live and as fast as one can play an idea in.

Cooler than cool - for me anyway.

VP

Ok, helpful.
The Project Panel makes for a lot of added possibilities. How that is implemented can be up for discussion, but that's a logical path
That, and of course a record button avaliable per clip.

I'll add that for the purpose of additional capabilities.

Funny, but in my earlier comment, with the arrangement being what I described as a chart recorder, a lot of that functionality is available that way. Even recording on the fly. Trim, then re insert back as a new clip. Of course in a linear way, but if record is selected, I think I could have performed every nuance that Mattias did in his video. Perhaps not. Because its probably possible to rehearse parts (by playing them first, then select record on the fly. That would be a benefit from working solely off of the clip launcher.

Good display of the possibilities.
I like it. I think others will as well.

The question will be, how much Studio One holds to clip launch improvents, and still maintain its own lean identity. But there's a lot of room for growth going down this road.
Let's continue ideas and give Lukas something that resonates with the group.
Very nice.

 

[Davey]

Add support for more pad controllers and the ability to map clips to MIDI notes, CCs etc.

 

[lokeyfly]

Add support for more pad controllers and the ability to map clips to MIDI notes, CCs etc.

Thanks! I think sending notes and MIDI cc's would be something dev's would look at, and I was already adding that CC item. I saw this recently in a similar launcher from another DAW.

As to more pad controllers, that could be positioned somewhere along "controllers" which wouldn't be reduced to pads, but numerous trigger types.

I'll add this as
Included with Panel.....
Note trigger, MIDI CC, and hardware related controllers (pads, CVs', etc.).

 

[Vocalpoint]

The question will be, how much Studio One holds to clip launch improvents, and still maintain its own lean identity. But there's a lot of room for growth going down this road..

My question is a little more pointed. More like - what is the point of introducing a Clip Launcher at all if all it does is play loops?

Because right now - this S1 implementation is just a slight nicer looking version of Sony Acid Pro (with playlists) if you really think about it.

VP

 

[lokeyfly]

Currently, clips from the launcher encapsulate the body of events (notes and CC's, but of course, take on their own set of instructions/choices.

With that, I'm curious about something that Studio One does very well in its superior drag & drop capability. What's to stop us from having the Control Link (hand) drag into any clip (or field), a MIDI cc, or parameter control? So that clips embody their own way of actuating some unique control. The answer is likely, something along weather developers "can", or dont wish to raise too many un associated variables into the mix. I certainly dont want to convolute ideas, but I do think the thought of easily dragging in from selected parameters, some controller, or parameter has a sweet workflow to it.

I could simply add it as a line item as:
•Control Link drag & drop to clips (or desired interior fields) for selection ease.

Thoughts....

 

[Vocalpoint]

With that, I'm curious about something that Studio One does very well in its superior drag & drop capability. What's to stop us from having the Control Link (hand) drag into any clip, a MIDI cc, or parameter control? So that clips embody their own way of actuating some unique control.

Can you describe what you see this doing? I am not getting a visual at all....

Not a Control Link specialist by any means but I thought this was hardware specific - not understanding how that would benefit me if I have a drum loop I have in Scene 1 Cell 4?

VP

 

[lokeyfly]

Instead of picking a particular CC, or parameter, in a field in the clip launcher, instead use the Control Link drag feature.

Just the way the Control Link operates now by simply clicking on virtually ANY control point (slider, switch, knob) from some synth, instrument, device, that the Control Link sees (hand immediately turns white). Then drag the hand to an already opened clip to a respective item such as [Send to MIDI CC], or [Recieve Conroller Device parameter] .

1. Open (right click) on desired clip
2. Select a parameter, such as resonance, on Dune 3, Osc 1, (synthesizer).
3. This auto activates the control link and is ready to be sent (dragged to any location)
4. Drag the Control Link hand to a respective field in the clip. This is no different then dragging the hand to an open edit window where the fields (or tabs) reside at the bottom. Only here, the hand is dragged into a field, simply to capture that control.

Let's say, your jamming along the way Mattias was, but now you want to add, or include resonance control and play that on-the-fly from your synth. The clip can accommodate this, as it has a direct line to CC or parameter changes (easily and way faster accomodated through the control link).

* setting up CC's looks to be a next feature in the clip launch campaign. Ideally, Control Link eliminates any cludgy assigning an instrument, its selected parameter, and such, into the frey. With Control Link, you select with the mouse pointer, drag, and off you go.
The newly added CC or parameter (pitch, volume, etc) is added to the recorded take. Not the event on which the clip originally came from.


● list updated.

 

[lokeyfly]

My question is a little more pointed. More like - what is the point of introducing a Clip Launcher at all if all it does is play loops

Because right now - this S1 implementation is just a slight nicer looking version of Sony Acid Pro (with playlists) if you really think about it.

VP

What I mean by "The question will be, how much Studio One holds to clip launch improvents, and still maintain its own lean identity. But there's a lot of room for growth going down this road."
Is exactly that. "Its own identity". We know there's much room for improvement. Currently, one can do quite a bit with the clip launch. Creating different parts played and recorded from different places along the arrangement timeline. Even recording on top of that as well! We also can likely take from Studio One's slightly unique clip design so far, that development hasn't followed the same path as other clip launchers. That's largely because its still pretty early on, but also that they just might follow their own design concepts. That leaves a lot of exciting and unique possibilities open.

 

[lokeyfly]

Something for the generative randomness of it all. Lokeyfly. food for thought.

Taches doing his thing, the 1st 10 minutes gives an alternative way of generating controlled randomness.

I will check that out, my friend. Before then.......
Controlled randomness is a seriously good thing! This is also a huge bonus with sequencers like Stepic. The ability to set a random layout, then trim ends, up/down, before, after, by percentage, etc.

Let's hope that if and when Studio One explore some of the points here, that they have the foresight to taylor random input. That is a very creative way to sit back, listen and hear what that random repeat, or real-time change will give.

 

[Vocalpoint]

We know there's much room for improvement.

The more I use this launcher (and given that a full year has gone by without so much as a mention) - I must admit - I am starting to wonder what the inclination was for this enhancement.

On one hand it seems like a logical step forward - like making S1 competitive on this front with the Ableton's and Bitwigs of the world. But on another hand it kinda felt like "OK fine - let's get this in there - but make it as bare bones and as pedestrian as possible. If it takes off - we will come back to it - if not - at least its functional for a single dimension"

The scary part (for me) is this year that has gone by. Considering this thing got zero love - it is hard to understand how/why anyone would even want to use it. I can find hundreds of Ableton and Bitmwig vids on their Launchers - but about a half dozen on S1's Launcher. And all of them doing exactly what we all do. Load a few clips, play a few scenes and get down tonight. Get down tonight.

If there is never going to be any forward motion - seems a tad ironic that they wasted time on this at all. Must admit - this is a first for Presonus - adding something with so much potential to the mix and then letting it become as interesting as watching paint dry.

Currently, one can do quite a bit with the clip launch. Creating different parts played and recorded from different places along the arrangement timeline.

For me - that is almost standard fare for all clip launchers and while it's nice to be able to do this - the cludgy methods of implementation are what is triggering me a bit. Like NOT having a Stop All command if I right click on a Scene Header - stuff like that.

In all previous versions of S1 - there are at least 3 ways to do everything - ranging from blatantly obvious to obscure. But a Stop All for these scenes and cells? Had to dig deep into the Macro framework to find such a thing - then when I did - had to assign it to a key command.

And then - in a quick session yesterday - sometimes this command works and sometimes it does not. Have never seen a key command misbehave like that - but I was pounding away on my keyboard - trying to get a selection of cells to stop/reset and it took at least 3 attempts to do so.

It is stuff like this that makes me crazy - here I am - in the moment, making stuff happen and then I have to surface, gulp air and struggle with a key command that has suddenly lost it's mind. And then while that is going on - I realize I just lost my vibe. Sigh.

VP

 

[lokeyfly]

@ Vocalpoint. Well, I get your concerns. No need to quote them. They're real and they're accurate. I also thought about some partial things only implemented. Still, what we have is an opportunity to make suggestions and reap the rewards of what transpires.
Let's keep the positive flag flying. With a few REAL improvements in the front end, we can still enjoy the many, many, benefits Studio One still has over the competition.

Heck, some of this good stuff could even find its way into Studio One's freakishly over simple arpegiator, and nuts and bolts Chorder. Random, and selectable control over randomization being just one of them!

Onward, and forward my friend. Keeping all noted points (by all) alive.

 

[Vocalpoint]

Still, what we have is an opportunity to make suggestions and reap the rewards of what transpires. Let's keep the positive flag flying.

Trying real hard to stay grounded my friend. Trust me.

But that incessant "tick tick tick" of the clock as the days turn into weeks turn into months is really not helping to conjure up a warm and fuzzy feeling.

Actions speak louder than - well you know the rest.....

VP

 

[lokeyfly]

... and it will require their action. Lukas' positive indicator is all we need to keep focused. We all appreciate your offerings so far. Excellent points at that!
I'll update the list again tonight. Just trying to write a damn song.

 

[sintil8]

I will check that out, my friend. Before then.......
Controlled randomness is a seriously good thing! This is also a huge bonus with sequencers like Stepic. The ability to set a random layout, then trim ends, up/down, before, after, by percentage, etc.

Let's hope that if and when Studio One explore some of the points here, that they have the foresight to taylor random input. That is a very creative way to sit back, listen and hear what that random repeat, or real-time change will give.

Hiya, have edited my post above as an aide-mémoire.

Regards

 

[lokeyfly]

Hiya, have edited my post above as an aide-mémoire.

Regards

Thanks sintil8. Yes, the video from Taches shows him playing with D, F, A, C using quarter notes, eighth, rests, and such. He started with a general theme around that chord, and eventually included random which made the progression more musical, or relatively predictable. One can decide to incorporate random, type, when, where, and amount of random level. A beautiful thing.

In the video, his progress was much in the way that Devicemeister's Stepic operates. Of course in a different manner as Stepic doesn't launch clips, but embodies selecting notes off of a scale, or pattern. One can select that at each pass, the note or in our case clip is ignored, skipped, jumped, randomized, and so on.

Later in the video, he touches on MIDI triggers here as well, which I've already included in the list. "Trigger notes, CC's send/recv". Taches triggers were based (optionally) on a "Block". In our case, that might be represented in the playlist. Where lists (or clips) can send or recieve CC, or selected notes to alter a Playlist. Yes, that's right, in real time!

So thanks for providing the video. If we're being honest, much of the music progress in that video could be done in a standard linear (timeline) fashion. Making even the visual representation of notes and scales far easier. However, we can also see where the clips even when non visual (or stacked), can take ones music to some pretty happy, or functionally unique places. So, I'd expect the next release of Studio One developers should go full throttle on adding a good many functions. Above and beyond our general list. This includes a global type of panel, as to not inundate the clips with drop downs. Clips should provide many choices but remain clean.

The ability to somehow make color or icons display function inside the clips skin would also be a great asset!

Yes, I saw at 4:08, 12:34 snd 13:22 the various choices within those panels.
TY.
We can keep the list as a general guide to stress the need that there's a good many functions that should still be included. For our purposes here, because we know how Studio One dances, we can add any preferred notables to our list that meet our needs, knowing the program as we do. to all.

Tomorrow, I'll finalize the list. We can give it a final critique. Whatever works. Cheers and thanks again.

 

[sintil8]

We can keep the list as a general guide to stress the need that there's a good many functions that should still be included. For our purposes here, because we know how Studio One dances, we can add any preferred notables to our list that meet our needs, knowing the program as we do. to all.

Tomorrow, I'll finalize the list. We can give it a final critique. Whatever works. Cheers and thanks again.

Great, it's all good,

I see your point about the how SO1 does things the SO1 way, and how additional software such as Stepic can bridge what might be described as gaps in SO1.

All folk can ask for is for user's request to be given reasonable consideration and acted upon, that is if dev can bring them into reality.

Cheers for posting the thread, best of regards.