patrickviens wroteImpact XT being DFD ( direct from disk) is ideal has also no wave file lenght limit, and it has all the sample playback/trigger options offered by a clip launcher (it offers multi out routing as well).

It can stretch files to match the tempo too.

Before buying Metric AB i have used it as a bank of reference tracks launcher and it was very good at that.

For me there is no point in building a daw around clip launching, especially when there is an accessory included that can do it.

aye thats what i;ve been doing with Impact..using it as a primitive clip launcher and to save random sounds to slip into tracks in presets. I like Impact. It's very useful for that and a big reason I;m sticking with Studio One

Vocalpoint wroteIf the forums did have that kind of clout - I would be very surprised.

VP

Ok I'll put it to the test.
We want a shrubbery.

Any day now...

Lokeyfly wroteMy hat is off to Presonus for not cluttering Studio One. I'm relatively convinced that will continue. But hey, I'm not here to bash the idea. Just simply support that yeah, it's not here, and that suits a whole lot of people just fine. Its not about hey if you dont need it, dont use it. Lean and elegant acounts for a lot! Especially in the arts. For those old schoolers who will know what I'm talking about. Most don't need a floor wax that's also a desert topping.

ummmmm ...what he said. In the words of Vinnie "thought is the enemy of flow". When inspiration strikes you shouldn't have to run to the manual. That's why, after three years, I abandoned Pro Tools.

frankzappa3 wrote

Lokeyfly wroteMy hat is off to Presonus for not cluttering Studio One. I'm relatively convinced that will continue. But hey, I'm not here to bash the idea. Just simply support that yeah, it's not here, and that suits a whole lot of people just fine. Its not about hey if you dont need it, dont use it. Lean and elegant acounts for a lot! Especially in the arts. For those old schoolers who will know what I'm talking about. Most don't need a floor wax that's also a desert topping.

ummmmm ...what he said. In the words of Vinnie "thought is the enemy of flow". When inspiration strikes you shouldn't have to run to the manual. That's why, after three years, I abandoned Pro Tools.

Vinnie Colaiuta is a fine example of master craftsmanship without interruption.

Again, the point of efficiency at the forefront, has to be made. Studio One as a DAW, does happen to carry that banner. On the creative front: Once you have to stop and think, you lose.
JCT

robertpaczkowski wroteA 3rd party VST solution: NI Maschine software (£59) - up to 128 scenes triggered by MIDI Notes, supports audio loops and MIDI patterns/

Rob

Any chance you could share how you use Maschine software as a clip launcher? I messed around yesterday for a bit but as usual - it felt like I was trying to use one daw inside of another which made for plenty of confusion and little accomplished.

Having a real hard time trying to understand how transport/measures/cursor positioning in Studio One correlates to the grid/session one sees inside the Maschine software.

Once that cursor is in motion in Studio One - I am completely lost in what I am looking at.

Any tips, tricks or vids would be most appreciated.

Cheers!

VP

Vocalpoint wrote
Rob (...) Any chance you could share how you use Maschine software as a clip launcher?

I use Studio One Sound Variations to switch Maschine Scenes (MIDI Channel One). I use channels 2-16 to play VST instruments (Maschine I/O settings: Input “Host”). When I drag audio loops - the instrument is set to “Sampler” by default – I change it to “Audio”. VST Instruments MIDI parts can be played and recorded as an Studio One events, then dragged to the browser as MIDI and moved to Maschine pattern later on.

Short demo here:

https://youtu.be/GPqS_3jD-yI

---

robertpaczkowski wrote I use Studio One Sound Variations to switch Maschine Scenes (MIDI Channel One). I use channels 2-16 to play VST instruments (Maschine I/O settings: Input “Host”). When I drag audio loops - the instrument is set to “Sampler” by default – I change it to “Audio”. VST Instruments MIDI parts can be played and recorded as an Studio One events, then dragged to the browser as MIDI and moved to Maschine pattern later on.

Wow. That is both awesome and deep at the same time.

I will need to study this clip (a lot) to understand exactly what is going on here - but it seems very slick to switch between the Maschine "scenes".

I am not familiar at all with Sound Variations - so that will be my first step. Then I am thinking super simple baby steps here getting Maschine going - if I am able to cobble together two scenes and switch between them - that would be a start I suppose.

Cheers

VP

@ robertpaczkowski,
Rob, when you noted from my earlier question that you can allocate various start points (sections) by switching to song/linear mode., was your video showing the linear mode? It appeared to be, based on the blue sections (scene's I suspect) at bottom. So while your example didn't display coming in at different selected bars (understably as that wasnt the intent here), is that where such markers could alter that? Then markers or MIDI keys would drive the relocation of the playhead? Remember, in middle bar positions, not the start of scenes.
TY.

Lokeyfly wrote@ robertpaczkowski,
Rob, when you noted from my earlier question that you can allocate various start points (sections) by switching to song/linear mode., was your video showing the linear mode? It appeared to be, based on the blue sections (scene's I suspect) at bottom. So while your example didn't display coming in at different selected bars (understably as that wasnt the intent here), is that where such markers could alter that? Then markers or MIDI keys would drive the relocation of the playhead? Remember, in middle bar positions, not the start of scenes.
TY.

I don't use song/linear mode functionality - I use MIDI notes to switch Maschine scenes (my "Sound Variation" settings are: notes 1-128 and this corresponds to scenes 1-128). Placing the notes on piano roll would do the same but I prefer sound variations (blue bars at the bottom). The Maschine sync settings on my video is "Retrigger - off" and "Sync - off". It switches the scene immediately when the "Sound Variation" changes but Maschine playhead stays in sync with Studio One song position.

P.S. Another method of allocating various start points would be duplicating pattern and changing the start position by dragging left/right loop markers

Thanks robertpaczkowski. I appreciate the clarity and description. The syncing of both sequencer's is and has been available in Studio One with Rewire, though S1v6 no longer adopts Rewire but still has the syncing and slave capability. Sync being understood.

Yeah, the loop marker is neither here nor there, unless multiple loop markers were available (independantly). Perhaps they are with Maschine, I dont know. Personally, I'd prefer using Studio One's track Inpector with the track selected as the arranger track. You simply select various splices of the arrangement and based on the snap resolution, the playhead follows the next available moment to follow. This is currently the case. The caveat, or missing ingredient with Studio One for now is, there is no way to alter selections in Studio One via MIDI selection or positional trigger keys. At least as far as I know.

So my wish with a silver lining would be to have both the Arrangement Track to incorporate such MIDI or key input triggering (it would be easy based on right clicking and addressing those event properties). The 2nd wish would be to have multiple loops that reside in a slightly expanded (same) place along the timeline. Multiple loops also addreassable within the track arrangement partitions/events. Want a global view? Well, that's both available by the loop bars already laid out, but could also be shown in the track Inspector in linear real time fashion.

Where's a dev when you need one?

Anyway, it looks by your example as a viable approach at least currently for those who'd want it. I think many might also see it as a DAW within a DAW, but hey, a clip launcher is effectively and rather affordably available so great job pointing that out.

I agree with you that it would be better to have a native, more advanced and user friendly solution (Maschine can be really confusing and can take some time to get use to).

robertpaczkowski wroteI agree with you that it would be better to have a native, more advanced and user friendly solution (Maschine can be really confusing and can take some time to get use to).

Keep up the good work. There's no substitute for 90% perspiration.

Lokeyfly wroteI certainly wouldn't use clip launch. Pro Tools doesn't need it.

Speaking of the devil... Pro Tools Sketch:

https://www.production-expert.com/produ ... -pro-tools

robertpaczkowski wrote

Lokeyfly wroteI certainly wouldn't use clip launch. Pro Tools doesn't need it.

Speaking of the devil... Pro Tools Sketch:

https://www.production-expert.com/produ ... -pro-tools

Well, I (or will be) stand corrected. Only look at that non sensible example video from Pro Tools Expert. I see no such sense in that process. It puts me in a state of contusion, I mean, confusion. 🤪
But hey, go for it! I've already got mine. I know I won't be shelling out $150+ for S1v7 if that's going to be their big curtain draw. It would only prove again that too many missing essentials will likely be ignored and that's just been business as usual.
Thanks for pointing it out for those who will want it.

I notice that Bitwig and Presonus have jointly developed their DAWproject project transfer format. This allows transfer between their DAWs of, among many other things, clip launcher clips and scenes (according to Bitwigs website.)

Could this be a clue that Studio One will also support clip launching in the near future?

https://www.bitwig.com/stories/bitwig-a ... grams-271/

callumhenderson wroteI notice that Bitwig and Presonus have jointly developed their DAWproject project transfer format. This allows transfer between their DAWs of, among many other things, clip launcher clips and scenes (according to Bitwigs website.)

Could this be a clue that Studio One will also support clip launching in the near future?

https://www.bitwig.com/stories/bitwig-a ... grams-271/

It’s never wrong to keep dreaming. For me Live‘s clip launcher is the only useful feature of Ableton Live. For me it’s incredibly useful to play around with ideas at the speed at which they pop up in my head. But that’s about it. So I wouldn’t buy Live just for that (again). It’s the other way around for S1. I love everything about it but hate that there is no clip launcher. I often switch to my MPC to get started but for me at least this workflow mix is not seamless enough to progress at the speed I want to. So I’d really like to have a clip launch feature. It could even work with the 4x4 grid of the ATOM and wouldn’t create the need for a new controller.

For the feature vote being so low: I think that people wanting a clip launcher above all else use Ableton Live for the most part and don’t even look at S1 after they’ve found out there is none. So why should they vote for clip launching in a different app that they don’t even know? The other thing is that until yesterday I didn’t even know that there’s a feature request page lol. Maybe there’s more people who don’t know about it? But maybe this is just me.

stefan.wendler wrote For the feature vote being so low: I think that people wanting a clip launcher above all else use Ableton Live for the most part and don’t even look at S1 after they’ve found out there is none.

My take on the feature vote being low - how about not a lot of S1 users want (or care) about a clip launcher?

That seems a bit more realistic and logical to me - more so that any specific connection or use of Ableton on the side.

VP

Vocalpoint wrote

stefan.wendler wrote For the feature vote being so low: I think that people wanting a clip launcher above all else use Ableton Live for the most part and don’t even look at S1 after they’ve found out there is none.

My take on the feature vote being low - how about not a lot of S1 users want (or care) about a clip launcher?

That seems a bit more realistic and logical to me - more so that any specific connection or use of Ableton on the side.

VP

You’re right might even be that people use S1 specifically because there’s no clip launcher.

The second part of my comment was meant more as in: if S1 would have a clip launcher, then I guess a lot of folks would switch over because S1 excels in every other aspect and this would grow the popularity further.