1. Option to have a default tool you can trust to be there
In every DAW except Bitwig, when you want to select several clips in the arranger, you can trust this to happen, independently from where you start drawing the selection box. In Bitwig, you must start the selection box from the upper half of a Track-lane – otherwise you’ll get the time-selection. There must be an option to disable this. And instead have a fixed default tool (like the pointer tool), while of course maintaining the ability to quickly change the tools via shortcuts (1-5). There must be the option to fully disable Bitwigs tool-switching behavior to “just” manual tool-switching via shortcuts.
This counts for all parts of the interface, including the note selections. It’s an insanely annoying and absolutely unnecessary workflow-killer, when the edges of selected notes are like a “mouse trap” for accidentally grabbing the time-selection instead of the note-length! The same counts for several other areas, like accidental time-selections of automation, when clicking just a few pixels distance away from the automationpoints. Please let us decide manually what we want to do in every Interface area which has at least two tool-options. The Alt-Modifier key is not the same as giving the option to have real manual tool-switching, as it forces the user to a completely redundant and unnecessary modifier step. Having to press Alt just to be safe from accidentally adjusting the time-selection of selected notes would be no convenient workflow.
Interface-Areas which only have one Option by default, can of course keep their automatic tool switching to their correct tool, like the Pencil for the Arranger-Loop-Bracket.
2. Undo/Redo and Cliprecording should work, while recording into the Arranger is active!
absolutely essential for live-performers who want to a) perform live via the Cliplauncher with the full undo-redo-workflow of Bitwig b) record their performance at the same time.
Undo/Redo also doesn’t work, when Midi Clip Overdub is active!
likewise essential: When recording into the arranger is active, and at the same time you record Audio or Midi into a Clip-Slot of the Launcher, the Audio or Midi-Notes are not “passed through” and not recorded into the Arranger. Only Midi-CC(Automation) is recorded into the Arranger, while Clip-Recording is active. Notes and Audio are ‘swallowed’ by the clip-recording. Notes and Audio should no longer be ‘swallowed’ by the clip-recordingand land in the Arranger-Recording, too.
Both undo/redo and passing through cliprecordings is working in Ableton by default!
3. Visibility of Gridlines, Clips, and Playback Bars
Option to increase/decrease visual strength of Gridlines, Clips, the Playback-barof the Arranger, and Playback-bars of Clips in the Launcher. Bitwig 5.1 Beta5 added a new gridline slider, but the 100% setting should go stronger than what has been possible before for 4th, 8th and 16th notes grid! -> Please add similar Sliders for transparency of Clips in the Arranger, Playbackbar of Arranger and Playbackbar of Clips!
Gradual Option to make Clips more transparent in the arranger, so you see the Gridlines through them.
The ArrangerPlayhead should stay visible, when Space or Shift+Space is used! It’s one of the fundamentals of any DAW and Editor, to see the exact current Playback AND Pause Position. The blue playback symbol in the top row is not enough, compared to a full line going over each Clip in the arranger. The disappearing Playhead should have an option to … NOT disappear at all.
The Arranger Playhead should be more clearly visible.The black thin line can quickly be overseen when being zoomed in vertically into dark colored Audio Clips in the Arranger. Especially when those Clips are heavily edited, the waveforms and black cutting-lines prevent the playhead from being clearly visible.
The Playheads in the Cliplauncher should be more clearly visible. The thin white lines can quickly be overseen for many color-combinations, when looked upon from further away, which is often the case for live-performances. Imho Clips in the Launcher should have an option to show Playbackprogress via ‘filling up with darker color’.
Option to show Loop Bracket Start and End as vertical Lines across the Arranger
4. Improve Automation-Lanes in Bitwig
Option to permanently turn off the muddy mouse-movement of automation-point dragging in ARRANGE view, especially when moving vertically. Removing this pudding-like mouse-deceleration and acceleration of vertical movement would be such a relief! The movement should be immediate instead. The red automation of the EDIT view is moving better – but still has a bit of this mouse-acceleration, which makes it less direct to control! [Bitwig seems to be working on this with v5.1b5]
Drastically improve automation-editing, by adding quick-editing tools (like creating of a 2-point segment with just one click/drag of a selected region in Ableton and Cubase).
Automation Editing Tools: Please add geometrical envelope drawing tools like in Cubase. Such tools (like a Line tool, Parable, Sinus, Square, etc) are much more powerful than just inserting static envelope shapes, especially because they can be adjusted in amplitude and frequency on the fly – AND applied to OTHER areas of the DAW, like creating a strumming on piano roll notes via the line tool within half a second! Adding such drawing tools would furthermore 100% fit into Bitwigs decision to go for a set of key-modifiers for tools (1-5), and there’s much room left for additional tools.
Option to quickly “bounce in place” modulator-based-automation into the automation lane, via the inspector or some other region of the interface, including a ‘preview’ picture, or better yet a live-preview line visible within the automation-lane.
Better Automation-Point-movement: Please add a preference-option or a modifier-key to the SHIFT+mousedrag movement of Automation-Points, so that there’s zero horizontal movement (axis lock). Right now, when using Shift+Mousedrag of Automation-Points vertically, it’s a wild ride!
Shortcut for “Show all Automation Lanes” in the Editor, so we can see ALL used Automation in the Editor. Seeing several Lanes of Automation in the Editor is very important for serious Midi Editing. Just think about Editing a Piano recording, for example: Seeing Sustain Pedal and Velocity at the same time is a MUST. For Synths, it’s many more parameters at once! 🙂
Seeing parameter values of automated VSTs and devices next to the Automation-Knob in the Tracklanes of the ARRANGE view, without being forced to hover over with the mouse above the Automation-Knob in order to see the value!
OPTION to make Automation points snap to other points so you can return the automation easily to its previous value.
Option to manually type in Automation-Point-Values with Alt+click, instead of a TRIPLE Click.
Option to have “Read” and “Write” for the Automation Lanes of each Track, like in Cubase and other DAWs.
Option to color Automationlanes based on Track color, which is an absolutely beautiful Feature in Cubase.
Option to set the automation fade time (currently 10ms, and unchangeable).
In Cubase and Ableton, when “snap to grid” and “adapt to zoom (=adaptive)” is activated, automationpoints only jump from gridline to gridline and can’t land in between. In Bitwig, points can land in between gridlines, despite “snap to grid” being active. I’m sure this can be seen as advantage, but i personally think it does result in a automationpoint movement which does not feel smooth at all. a) because it’s not the expected behavior, which would be only snapping to grid, and b) because the movement has sudden extreme accelerations. This sudden pull of the mouse doesn’t feel smooth at all, because it isn’t a jump from gridline to gridline, but often times from some random point in between gridlines to the next gridline. I’d be happy about an option for “exclusive snap to grid on/off”.
5. Looper/Loopstation Functionality for Bitwigs Cliplauncher
Bitwig has no audio overdub, and no Looper, and no possibility to automatically switch between Tracks to make quick Midi-Recordings with different Instruments. There is also no way to midi assign Bitwigs Post Recording Actions! These are huge problems for any live-looping-artist, which would ALL get solved AT ONCE, with the following suggestion.
Bitwig and its users would greatly profit from a Looper functionality, where you can make audio overdub (and midi-track-overdub) with a quick workflow, just like with a Loopstation. Ideally directly within the Cliplauncher. By letting the user switch and/or record automatically into the “next free scene slot”, accompanied by a smart settings-region mimicing loopstation functions. Click here to see this Feature Request on Bitwish, if you want to vote for it 🙂
This Feature request consists of three more “post recording actions” and their respective settings, to achieve proper Loopstation functionality:
“select next free slot” = Bitwigs Clip-Selection switches to the next free Slot of the same Track. You can record another take in the same track at a time of your choice without having to manually switch from clip to clip.
“select next free scene slot” = Bitwigs Clip-Selection switches to the next free Slot of the NEXT Track. you can record at a time of your choice in the next track of the same scene without having to switch manually. This is semi-automatic audio/midi overdub with a flexible recording start!
“record into next free scene slot” = you can immediately record into the next track without having to manually switch there and without having to press record. This is fully automatic audio/midi-overdub! Awesome!
To really be a proper Looper/Loopstation, Bitwig also needs more settings for the activation of those “post recording actions”. Aside from the already existing “post record delay”, there must be:
enable/disable post recording action = on/off for post recording action. Overrides all other options like “Post Record Delay” and “Loop Count”.
Enable/Disable Loop count before Post Recording Action (default value is x1 = one clip length) = If active, the Post Recording Action is triggered immediately when the current clip recording is ended by pressing the Record button. If the value is greater than 1, the clip is repeated a corresponding number of times, and then the Post Recording Action is triggered.
Enable/Disable first Clip sets Post Record Delay count = If enabled, the first clip recorded determines the clip length of all subsequent clips. Can only be enabled if Loop count is on and therefore Post Record Delay is off. As soon as the length of the first clip has been determined by ending the recording with the Record button, and Loop count has been processed (at x1 immediately, at x2 after repeating the clip once, etc.), Loop count is deactivated and Post Record Delay is activated with the bar length of the first clip.
Enable/Disable auto-adjust Clip-Length = Automatic shortening of the clip length, in case Record was not pressed in time, but a few milliseconds (up to one beat) after the desired bar length has elapsed. This subsequent automatic shortening by -1 bar (I’m assuming 1 bar Launch Quantization) would also work wonderfully together with “3. enable/disable first Clip sets Post Record Delay count”, since the bar count for Post Record Delay can also be changed while recording is running. Example of how Automatic loop length adjustment looks:
All mentioned settings/functions must be midi-assignable, to be quickly useable in a live-performance.
As first step towards these awesome Cliplauncher-Loopstation-Features, there could be an option to let switching Tracks mid recording of Clips in the Launcher not stop the recording process, but rather let the recording finish within the confines of the currently active launch quantization.
6. Improvement of Touchcontrol
Please fundamentally improve Touchcontrol: There are so many functions which are not available via touch, and which unnecessarily force us to go back to the mouse. The Bitwig way of touch control has its advantages in some specific areas, where the radial menu shines – but there must be a quickly accessible and assignable toggle button to deactivate it whenever needed, which in my case would be most of the time. We could then enjoy normal mouse left and right click via touch, and whenever needed, we could temporarily activate the radial menu, or the tools sitting at the numbers 1 to 5. Or even a new additional smart function, which, when activated lets us grab those tiny areas more easily, which are usually only grabbable when you hover over them with your mouse. By the way, such momentary or toggle buttons on a controller activate functions faster than having to press and hold and then choose something within the radial menu. With your left hand you decide what tool to choose, with your right hand you use it immediately at the same time. This would lead to the best touch experience in any DAW. Because it would finally combine the best of both worlds: every mouse function, every Bitwig tool, and the awesome Bitwig radial menu. Being able to customize the radial menus would also be great.
Here’s a list to show how impaired touch control is:
Right now, you are unable to make normal selections of many clips, notes, audio events etc. by drawing a diagonal line, like you’re used to since years of using a mouse or a tablet.
You can’t use the knife tool or any other tool which isn’t part of the radial menu. Sadly, pressing the numbers 1 to 5 to activate those tools doesn’t work in combination with touch.
You can’t use lots of other functions which are part of the right-mouse-click menu. Ironically that’s something you can reach in Ableton and even in Cubase by holding the touch for a second.
You can’t pin all shortcuts of the shortcut list in the preferences to the Bitwig-Toolbar.
You can’t grab automation points and drag them! You can’t. Of course you can draw automation in, just like in Ableton after activating the pen mode, but you can’t grab and drag any automation – which you can in Ableton, and even Cubase.
You also can’t use any functions which are usually accessible via mouse-hover-over, like grabbing fades, grabbing clip-gain, loop selection size (grabbing start and end, not drawing!), cue markers, etc. and many more.
Option to make doubleclick create notes in the piano roll based on grid-size, instead of Alt+Doubleclick.
Option to deactivate automatic tool-switching! No more accidental hitting of the time-range-handle over the note-edge-handle!
8. Better control over interface-sizes and panels:
Further reducing Track height while still showing midinotes and waveforms should be possible!
Further reducing Scene-Size (in the vertical scene Cliplauncher of ARRANGE view) should be possible! Increasing Scene-Size horizontally in MIX view should be possible. [Fixed in 5.1!]
Display/Interface-Scaling below 100% should be possible. Ableton allows for up to 50%.
Let users decide to show Arranger, Mixer Panel AND Device Panel at the same time. 4k Monitors could show everything with ease, and the constant panel-switching would stop forever. [This is of course a feature request for one big monitor.]
9. Please give users additional API functions
Clip playback progress, or the length of each clip, so the clip playback progress can be calculated. Would be awesome! Especially for a OSC Touch Interface
VU meter value in decibel,
VU peak hold level in decibel (!)
VU peak hold level reset function (!)
VU Meter for Muted Tracks! Right now, Muted Tracks on OSC interfaces show the ‘normal VU Meter’ while in Bitwig it is greyed out.
Grid-Settings! (Measure of beat time grid, beat grid subdivision, snap to grid, adaptive grid, snap to grid offset, snap to events) would be awesome to have, because those Settings could permanently be shown with their true on/off status in a OSC interface, improving Bitwigs experience alot, because even in Bitwig one doesn’t have an overview of all those toggles, without clicking around! Having those OSC Addresses would fundamentally improve the experience of controlling Bitwig!)
Browser-API-Access to “Play at original speed / stretch to project tempo” button
“Record Quantization”-settings should be available
Restore Automation Control needs to be accessible, so a OSC button will light up, when it’s lighting up in Bitwig.
No longer separate FX tracks and normal tracks into banks.
Option to increase bank-size of Track and Project Remotes
10. Browser Improvements, including “Save snapshot” “Save mapping” Features
Let users deactivate “live-preview” permanently!
Let users customize the Categories (including deleting existing categories)
Let users customize the Tags (including deleting existing tags)
Let users customize the names of Plugins
Let users create mini-preview-pictures of their Plugins (Optional “visual” Browser)
Fix the “Select All” Shortcut not really selecting all samples in huge Sample-Lists.
Saving snapshots of current macro-knob settings should be possible, also as Browser-Preset
Saving a device preset should also save the according midi mappings into the Browser-Preset!
11. Clicking anywhere in the Editor should switch playhead position to that spot.
Play from Cursor in the Editor (Detail View) should work by clicking anywhere in the Editor, and then Space, like in the Arranger. Also: The playback-position of Clips in the Cliplauncher can’t be adjusted! The blue-playback-symbol doesn’t even show up in Clips in the Cliplauncher! Please fix this 🙂
12. Clip-Playback-Progress showing in the Track in addition to within the Clip!
Incredibly important for big Livesets! Should exist as optional element to show/hide.
13. Option to make Shift+Mousewheel scroll the Arranger from left/right.
15+ Years of Muscle Memory from Adobe Premiere, Melodyne, Cubase, Ableton, Izotope RX, Audacity and many more Programs call for that option in Bitwig.
14. Add a “one button” Audio Quantization [Almost Fixed in 5.1!]
based on slicing on onsets.
Explanation: The Audio Quantization based on slicing on onsets currently needs many actions: rightclick on the audio, leftclick on slice in place (or shortcut), select “on onsets”, press “ok”, Ctrl+A to select all slices, then finally use Quantize. BUT, in order for certain legato-instruments to not sound all choppy, you then have to add fades, which is two more click+drag actions. In summary: At least 6 actions, sometimes even 8. There should be an option to automate this.
And there should be another option to just do audio-quantization based on warp-stretching, which truly only would need one button to do the job. [Fixed in 5.1!]
15. The “Activate/Deactivate” Button for Plugins should be Midi-Assignable!
The general shortcut for “activate/deactivate selected item/track” is not enough, as it is useless for quickly managing Latency and RAM usage of specific Plugins in a huge Liveset.
16. Show Peak hold levels in decibel in the normal mixer panel [Fixed in 5.1]
Overview of Peak hold levels should not just be in the Big Meters of the MIX View! The arranger needs to show peak hold levels in its mixer. [Fixed in 5.1!]
17. Fade Options for Audio-Playback and Recording – not just Audio-Edits!
Recording audio leads to obvious blips/glitches at the Beginning, when starting a clip-recording in the Launcher, while a sustained note is already coming in before the recording starts. (Wouldn’t be a problem if Clips already had a FADE button like in Ableton) Therefore, please a) Add “FADE” as default setting for Audioclips, exactly like in Ableton, to prevent audible Clicks at the beginning of Audioclips! b) Add Option to set the default fade length for recordings!
Please allow us to use the Ctrl+F Shortcut for Autofade on Clips (=Clip Containers) in the Launcher!
18. Retrospective Audio Recording
Together with optional intelligent quantization: Pulling the first recorded transient to fit perfectly on the “1”, for example. Would be insane for audio-live-recordings into the cliplauncher.
19. The Grid needs better Audio-Recording/Slicing abilities for live-performance
Audio Recording is currently limited to just a few seconds. Best thing would be to let users record into the Sampler.
20. Sampler-Upgrade: Slicing, Timestretching
Slice to Multisample should be usable in a live context, with easier slice-adjustion on the fly.
And option to slicing into an already existing Track, which then can have proper pre-made FX-setup for each slice.
Ideally with a visual synchronization of Arrangement-Timeline and Detail-panel.
22. Further improve transient/onset detection and warpstretching
Improve transient/onset detection to be on par with industry leading software.
Also add intelligent Pitch/Scale and BPM Detection for Samples (!), like in Traktor.
Improve warpstretching audio quality
23. Improve Bitwigs compatibility with Touch-Control Software
Using Touch-Control Software running on the same PC as Bitwig leads to Problems:
“select previous item” “insert from library” etc. all those actions must work via midi cc even when Bitwig is out of focus.
Assigning midi cc shortcuts should not require Bitwigs windows to be in focus, in order to receive the midi cc from the controller! Assigning Midi CC via touch controller running on the same PC is impossible right now.
25. Option to adjust Loop length with a shortcut for +/- 1 bar
without having to open the detail-view and having to select the loop length, but rather just by selecting the Clip in the Cliplauncher and pressing the shortcut.
26. Option to make Copy&paste and duplicate non-destructive
Right now, audio/midi clips which are in the way of pasted or duplicated Clips get destroyed/deleted forever. There should be the option to instead of destroying clips, they just get overlapped, while staying intact (like in Cubase)!
27. The stretch tool (Alt+Drag) should always work!
There should be a forth option in Bitwigs settings for “Default stretch mode” called “On using the stretch tool”. Otherwise, a essential function of Bitwig (Alt+Drag) is rendered completely useless for Short samples, which for 99% of all producers have Strechmode=RAW turned on. It’s a highly inconvenient workflow to being forced to manually activate a stretchmode, to be able to use Alt+Drag again for RAW samples.
28. Cue Markers get pushed into the wrong spot when changing Loopsize
When Loopsize is narrowed/lengthened again, the cue marker stays there and doesn’t follow!
29. Option to change the colorization of the VU Meters
Right now they show red where there’s still -10db headroom.
30. “Select Device” should be Midi-Assignable
And Bitwigs viewfocus should follow the selection.
31. Vertical zoom of Tracks needs a shortcut+mousewheel action
32. Mappings Panel needs a SCROLL BAR
33. “Plugins crashed” must show WHICH ones!
34. Add a glue tool for the Arranger, and for the Editor
It’s much better than just having to consolidate (which by the way does not work in detail/editor!), as you can quickly glue some ‘sliced on onsets’ audio snippets to form new, quickly draggable units.
This has a perfect synergy with a non-destructive clip-dragging in the arranger/editor, where overlapping events are possible, instead of deleting the overlapped event! In Cubase, you can drag midi clips on top of each other and quickly combine them via the gluetool.
35. Add Audio-to-Midi, equally good or even better than in Ableton
Not as a fiddly grid-device. But as a fully integrated and highly precise feature, which has a shortcut for ‘transform to drumkit’, ‘transform to melody’, ‘transform to chords’.
Ideally with an option to immediately import transformed midi chords into a CHORD Track
36. Add CPU Meters in Tracks
Perfect synergy with Bounce In Place, because users can quickly decide which Tracks to bounce first, when resources are short.
37. Add Clip-Playback-Progress bar filling each clip with color
as optional setting for improved visibility, especially important for Liveperformance!
As a first step: Add option for bigger/fatter Bar-lines to see Clip-Playback-Progress better.
Add Option to show Clips as Circles in the Launcher (like in Loopy pro or Logic) 🙂 🙂 🙂
38. Change the colors for the Buttons in the Crossfading Section.
It makes zero sense to color the “A” and “B” and “AB” Buttons all the same (orange). That’s a visual nightmare. At least two colors are necessary, as can be seen in Ableton.
39. Add an Action-Script for Bitwig, resembling ClyphX Pro
, where you can put action commands into dummy clips and Bitwig will act upon those, when launched. My favorite example of how powerful that can be (because it also shows how awesome a better slicing tool can be for Bitwig): ClyphX Pro Q&A with Stray: Slicing and Chopping
40. Improve the Midi Scripts: Add bi-directional generic script!
It’s just incredibly sad that there’s no natively working bi-directional midi-script. Explanation: Minute 29:42https://youtu.be/oLDshsHmLYo?si=0A-PDrLLCVSZKdhM&t=1781
41. Option to show “Edit in external Editor” in the Audio-Editor!
(Like in Ableton, but with option to use 2 or more Editor-Shortcuts.
42. ARA integration (Or a native pitch-editing better than melodyne, haha)
43. Renaming anything in the interface shouldn’t need an ENTER to confirm it!
44. Extend the Grid to be like Max 4 Live, but better
with stability as top priority. Full access to the API, so the users can create all the awesome tools which they are missing from Bitwig, even with their own GUIs.
45. Improve Midi Export and Import!
Exporting single Midi Clips should be possible.
Exporting Midi CC together with Midi should be possible.
Importing Midi should be possible without the nagging “Import Tempo & Time Signature” Dialogue Pop-Up! The Pop-Up must have a “remember selection” Setting and a permanent Setting in Bitwigs Preferences!
46. Zoom behavior in the Grid should match Zoom behavior in Arranger
(Mousewheel to zoom in/out, instead of going up/down.)
47. Chord Tracks, intelligent Scales function for the Piano Roll
A chord track like in Cubase, which a) serves as audio-to-midi transformation pool, extracting chords out of any given audio. b) serves as scale-guide for pitch-tuning of vocal audio tracks. [This requires pitch tuning abilities in Bitwig first]
48. Clips should not lose synchronization after resuming Playback
49. “Arm on Selection” should work, while recording into Arranger is active
Bitwigs Interface should stop lying to the user: When “Auto-Arm” is set to “on”, it should be on. Right now, as soon as recording into the arranger is active, “Auto-Arm” is set to “off” even though the interface shows “on”.
50. Fix the “Follow Playback” button
The Follow Playback button should be a real toggle on/off button instead of turning off automatically all the time.
51. Let us listen to Audio in real time
when doing certain edits, like dragging clips, stretching / moving audio, using the knife tool behind the playback position, etc, Bitwig will not play the Audio in its actual real time position
52. Loop-Bracket Improvements
Shortcut for “Select everything in the Loop-Bracket”!
Let us use the Cltr/Ctrl+Alt Shortcuts to set the start and end of Loops within the EDIT and DetailView, not just the Arranger!
When changing the size of Loops via grabbing the end and dragging it smaller via mouse-drag, the Loop-Size should not be restricted to 1 Beat, but go smaller than that!
53. Retrospective Midi-Recording
= Midi Capture, but with an optional smart function: Slicing to specific bar-length, adjustable in the preferences.
54. Midi Comping
Not so important for me personally, but i’d be happy for all the people who want it.
IF Bitwig ever implements Midi Comping, they should please please include an option to permanently and absolutely turn it off with a simple on/off switch in the preferences/toolbar, so that the arranger will never be cluttered with empty/half-empty takelanes. (Just a preemptive wish ;D )
Some people also want midi-step-recording.
55. Linked Clips/Alias Clips
56. Groove Pool
Groove extraction function
Save & Load Grooves
Apply Groove globally and individually onto Clips (strength slider for applying it in each Clip)
Grooves being more than just swing
57. Instrument Selector +
There should be a Instrument Selector+ which has a Featureset similar to PluginHoster Softwares like Komplete Kontrol, Gigperformer and Mainstage.
Option to turn on intelligent RAM management (changing instruments will then unload the last Instrument out of the RAM)
A new hover-Browser-popup-window, which lets users search in their custom made preset library, to insert favorite Instruments quickly, while liveperforming.
Full API access to this Browser, so users can access it via OSC adresses (results in full overview of the custom Instrument Browser on a Touch OSC Tablet, for example)
New Feature for the Browser: Saving Snapshots of Parameter Settings, and Saving Midi Mappings of Macro-Knobs. This way, loading Instruments in the new Selector+ will result in all custom assigned parameter mappings working out of the box via Midi Controller.
58. “Loop” Clip should be Assignable to a Shortcut!
Also: Add option to determine whether recordings in a track result in looped clips or oneshot clips!