Feature sugestion: Cliplauncher launchmode "End of Clip" (Like Logic ProX)
-
- KVRist
- 108 posts since 1 May, 2005
Am i the only One using Logic Pro besides Bitwig and missing one of Logic Pro Cliplauncher Modes when working in BWS..."End of Clip"?
I´m into Dark Ambient and similar Stuff musicwise and this Launchermode comes in verry handy for all Things Ambient in my oppinion.
The Launchmode in Logic Pro does what the Name Says: Plays the next Clip when the running clip reached its End. No Matter if the Clip has 1 Bar, 5 Bars or 17 Bars or whatever length, it waits for the Clip to reach its end until it starts the next selected clip (or stops the Clip whn you trigger an empty Cell). Both in Global and Per Clip Modes.
Handy feature or to "Special".... what du you think??
I´m into Dark Ambient and similar Stuff musicwise and this Launchermode comes in verry handy for all Things Ambient in my oppinion.
The Launchmode in Logic Pro does what the Name Says: Plays the next Clip when the running clip reached its End. No Matter if the Clip has 1 Bar, 5 Bars or 17 Bars or whatever length, it waits for the Clip to reach its end until it starts the next selected clip (or stops the Clip whn you trigger an empty Cell). Both in Global and Per Clip Modes.
Handy feature or to "Special".... what du you think??
-
- KVRist
- Topic Starter
- 108 posts since 1 May, 2005
As far as i can see the Launchquantisation in BWS goes from Off (Clip starts emidiatly) to 8 Bars Maximum, same as in Ableton......?
Or is there Something i haven´t found until now?
- KVRAF
- 26967 posts since 3 Feb, 2005 from in the wilds
Select a launcher clip and in the Inspector, turn on Next Action. By default, it plays 1 clip length and then you select what happens next.
-
- KVRist
- Topic Starter
- 108 posts since 1 May, 2005
I know about the Followactions. What i´m talking about is the Launchquantisation. There Logic Pro has one Option more than Ableton and Bitwig: End of clippdxindy wrote: Sun Oct 29, 2023 4:35 pmSelect a launcher clip and in the Inspector, turn on Next Action. By default, it plays 1 clip length and then you select what happens next.
- KVRAF
- 26967 posts since 3 Feb, 2005 from in the wilds
How is it different? From your description, it sounds the sameastartes wrote: Sun Oct 29, 2023 6:50 pm
I know about the Followactions. What i´m talking about is the Launchquantisation. There Logic Pro has one Option more than Ableton and Bitwig: End of clip
-
- KVRist
- Topic Starter
- 108 posts since 1 May, 2005
Not really: If you set the Follow actions (no matter what follow action) to one duration and trigger another Clip by hand on the same Track the newly triggered Clip uses the Launchquantisation for it´s start and ignored the Follow Action on the running Clip (at least in Bitwig 5.1,Beta 2). If you can set the Launchquantisation to the Clips end (i almost always use that globlaly in Logic Pro) then any newly triggered Clip starts when the playing Clip on that Track reached its End.
-
- KVRian
- 765 posts since 26 Sep, 2007
Sounds like very useful functionality, make sure to send it to support@bitwig.com
- KVRAF
- 26967 posts since 3 Feb, 2005 from in the wilds
Select all the clips and change them at once.astartes wrote: Mon Oct 30, 2023 6:57 am Not really: If you set the Follow actions (no matter what follow action) to one duration and trigger another Clip by hand on the same Track the newly triggered Clip uses the Launchquantisation for it´s start and ignored the Follow Action on the running Clip (at least in Bitwig 5.1,Beta 2).
But yes, a default Next Action option would save that step.
-
- KVRian
- 765 posts since 26 Sep, 2007
I don't think what astartes is asking about can be achieved with Next actions. Next actions are for programming what happens when a playing clip finishes playing.pdxindy wrote: Mon Oct 30, 2023 3:46 pm Select all the clips and change them at once.
But yes, a default Next Action option would save that step.
What's being asked about here is a way to decide, on the fly, which clip to play after the current clip on the same track has finished playing. It affects when the triggered clip gets played, that's why it sort of belongs in the launch quantisation section. It's sort of a "queue up clip" function, where you can trigger a clip quite a bit ahead of when you want it to play.
- KVRAF
- 26967 posts since 3 Feb, 2005 from in the wilds
Oh, now I understand. Yeah, that's not possible in Bitwig.Dionysos wrote: Mon Oct 30, 2023 5:57 pmI don't think what astartes is asking about can be achieved with Next actions. Next actions are for programming what happens when a playing clip finishes playing.pdxindy wrote: Mon Oct 30, 2023 3:46 pm Select all the clips and change them at once.
But yes, a default Next Action option would save that step.
What's being asked about here is a way to decide, on the fly, which clip to play after the current clip on the same track has finished playing. It affects when the triggered clip gets played, that's why it sort of belongs in the launch quantisation section. It's sort of a "queue up clip" function, where you can trigger a clip quite a bit ahead of when you want it to play.
And yeah, send in a feature request for it!
-
- KVRian
- 1404 posts since 17 Oct, 2018
There are two other cool things Logic's clip launcher does that I would like to see in Bitwig.
- Playback speed. You can play the clip back at different speeds without have to edit or change the clip length etc
- Reverse playback
- Playback speed. You can play the clip back at different speeds without have to edit or change the clip length etc
- Reverse playback
Studio One // Bitwig // Logic Pro // Ableton // Reason // FLStudio // MPC // Force // Maschine
-
- KVRian
- 653 posts since 30 Oct, 2022
It's very fascinating to see that Logic has seemingly more options / a good option in the Cliplauncher which Ableton and Bitwig don't. First time i hear about Launchmode End of Clip.
Something i personally miss the most for Bitwigs Clips: Automatic "Fade" for Cliprecordings.
When you sing a note "aaaa" and while singing, start recording in a clipslot, Bitwigs Clip will playback a clearly audible "Click"noise at the start of the clip, due to the audiosignal being cut in the middle via recording. Doesnt happen in Ableton, due to automatically activated "Fade"!
The "Fade" value in Bitwigs preferences only affects Audio Editing, like Slicing, not recordings.
Already reported this to Bitwig btw.
Another thing which i think would be great to have: a shortcut for deactivating "Looping", to put Clips into Oneshot Mode without the need to click in the inspector!
Something i personally miss the most for Bitwigs Clips: Automatic "Fade" for Cliprecordings.
When you sing a note "aaaa" and while singing, start recording in a clipslot, Bitwigs Clip will playback a clearly audible "Click"noise at the start of the clip, due to the audiosignal being cut in the middle via recording. Doesnt happen in Ableton, due to automatically activated "Fade"!
The "Fade" value in Bitwigs preferences only affects Audio Editing, like Slicing, not recordings.
Already reported this to Bitwig btw.
Another thing which i think would be great to have: a shortcut for deactivating "Looping", to put Clips into Oneshot Mode without the need to click in the inspector!
I built a Looper for Bitwig!
https://www.youtube.com/watch?v=-z5ywDo2bU0
