[POLL] What next?

Official support for: bitwig.com
Post Reply New Topic

What do you miss the most?

Advanced tools in the piano roll (scrub, velocity ramp, chop, strum, stretch, etc.)
189
22%
Musical scales highlighting (per clip configurable)
100
12%
Chord/harmony track
64
8%
ARA(2) integration
45
5%
Automation clips including automation generators and modifiers
72
8%
Linked/ghost/alias clips
52
6%
Track comping
78
9%
Access to the modular development tool
66
8%
Video track
40
5%
Groove quantize with custom templates
92
11%
Other? (describe)
50
6%
 
Total votes: 848

RELATED
PRODUCTS

Post

antic604 wrote: Mon Feb 19, 2018 7:41 am
Echoes in the Attic wrote:Actually one other thIng - I want to be able to use the surface pen and not have the multitouch stuff come up, which is impossible to use with pen. Ruins the whole experience.
That's on Windows, not Bitwig :(
Never noticed this reply before. But no it isn't on Windows, it's on Bitwig. Other programs use the pen just fine in Windows, like Maschine and Ableton. Pen usage is borked in Bitwig because of the multi-touch stuff. There is now a setting to ignore pen gestures, but unfortunately there is a lag between touching the screen and grabbing something, so it's almost impossible to grab an automation node or use the brackets to extend a note or anything that is click and drag because of this delay in response. Other programs like Maschine and Ableton don't have this problem with the pen input.

So that would be my biggest in the Other category, and just improve the touch stuff generally as well, there are still things you can't do.

Beside that my other wishes got filled, so it's mostly the above and global parameter snapshots (save and recall), like in Maschine. Would be perfect in Bitwig.

Post

groove templates 100000 days waiting for
device parameter snapshots per scene with snapshot track.
Last edited by flares on Tue Dec 03, 2019 2:07 pm, edited 1 time in total.

Post

Randall P. McMurphy wrote: Tue Jul 31, 2018 6:23 am
- groove templates

- crossfading loop on the sampler. *DONE :tu:

- support for microtuning, scala etc *DONE :tu:

- 'modulation receiver' that works the way the audio receiver does - as it stands the only way to move modulation outside individual tracks is by using MIDI or grouping all the instruments in one track *DONE (via Grid) :tu:

- ability to set default preset for modulation tools (unless I missed how to do this) - bit of a pain constantly having to change the waveform on the LFO or bring values to 0 etc

- ability to save groups of modulations that are already interdependent - again, bit of a pain to have to constantly drop an LFO, then route it to the sample & hold, then route that to one side of the mix, then an lfo to the other side - would be great to just drop a preset of modulations into a device *DONE (via Grid) :tu:

- legato glide option box for Hardware CV Instrument *DONE (via Grid) :tu:

- Accent Template, so that the user can specify which notes get an accent.
Could just be a grid block of one bar that you specify grid size 1/2, 1/4/, 1/16T as per regular note entry, and then enter steps. These steps are then accented according to the accent knob in the global section. Keep in the sidebar where the accent controls are now. For me as it stands the current sine wave isn't useful or precise.

- ability to assign as a shortcut or map to midi for "Device: Set Next / Previous Parameter Bank". Currently using Moßgraber Flexi script but this should be built into the program for all users.

- ability to assign as a shortcut or map to midi for "Record Quantization", I'm often moving between 'off' and '16ths' and this would speed things up, too many clicks right now.

- use shift to select multiple empty clip spaces in the launcher and then enter to make them all activate and start recording at once (a good technique I used in Ableton that I miss here). *DONE :tu:

- option to edit the tag list that is shown in the clip / device saving dialog to replace with your own tags. I never ever use 'acoustic' but always use 'superdope' etc.

- option to turn off “embed files not in project folder” as default option to save, maybe just remember last chosen behaviour, easy!

- clean up the way duplicate works with clips. If you don't move the start marker its all good, but if you move the start marker within a loop and then try to duplicate the loop weird things often happen (but this is more a bug then a feature request).
Slowly crossing my requests off the list!!! Thanks to the developers you are the best!!!

Post

Don't if its track comping? My wish would be free audio routing possibilities! Drag n drop an audio chain from a multi-out VST (Kontakt, Reaktor, Omnisphere, XO, etc) to maybe a group track! The 'Audio Reciver' solution is for me a workaround only.

Post

+1 for multi-out VSTis normal routing. Can't believe this is not yet possible...

Post

Multiple outs of course is possible. If you really want it on multiple tracks, place an audio receiver device on each track simply, and mute the original plugin track.

EDIT: I think you can place the multi-out / midi-multi-in generator onto a group and then add instrument tracks as children within the group. For multi midi input, then use the midi mapper to set the appropriate channel. Then you also can place an audio receiver, so you will have notes and audio per channel.

Then you can save the whole group track as a template.

Post

Already mentionned, but this is a workaround. The audio outputs, by evidence, should appear like new tracks in the mixer, instead of complicated routings/additionnal modules: workflow killer.

Post Reply

Return to “Bitwig”