[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

kpv wrote: Sat Feb 02, 2019 3:24 pm Midi step input

Midi chasing in clip luncher/arrangement when recording

being able to duplicate content of clips by pressing their region like Ableton

In other words, "finish" the clip luncher. The first two are essential from those who are used to working mainly in the clip luncher in Ableton. :pray:

Yes! Duplicate content is missed sorely. Also legato mode.

Post

^^^ unassigned shortkey : double content ?
"Where we're workarounding, we don't NEED features." - powermat

Post

xbitz wrote: Sat Feb 02, 2019 3:56 pm ^^^ unassigned shortkey : double content ?
Nice!!

Post

Double content doesn't work, bitwig 5 beta 4

Post

1. Track "Auto-monitor" is always on when creating a new track.
Needs a global switch to always off when creating a new track.

2. When opening a part first time for editing "Audition Notes" always on.
Needs also a global switch to always off.

Post

Remember that Bitwig devs don’t see feature requests or bugs mentioned here. Send beta-related feedback to beta@bitwig .com and send more general feedback to support@bitwig.com

Post

n0j0e wrote: Mon Feb 04, 2019 11:37 am When opening a part first time for editing "Audition Notes" always on.
Needs also a global switch to always off.
This! Should be global and not per track like it's now. Or at least an option to have it off as default.

Post

When I audition a MIDI file, I want to be able to select which track it is auditioned on. Currently all auditioned midi goes to a simple internal synth. This is bad enough when you want to hear how your melodic tracks will sound, but useless when you are trying to audition a MIDI drum loop.

To me this is astoundingly basic functionality for a pattern based DAW and I don't understand why it seems like I am the only one bothered by such a glaring flaw.
Even if the piano player can't play, keep the party going.
http://www.soundclick.com/mumpcake
https://mumpfucious.wordpress.com/

Post

I have never auditioned a midi file!
X32 Desk, i9 PC, S88MK3, S1, BWS, Live + PUSH 3, Osmose, RedShift 6 Pro3, Tempera, Syntakt, Digitone II, OP1-F, OPXY, Eurorack, TD27 Drums, Guitars, Basses, Amps and of course lots of pedals!

Post

I know they don't want to, but... Rewire please

Post

If you need it desperately, get the Energy-xt rewire vst...

Post

More flavors. I’m thinking pistachio and chocolate chip.

Post

-JH

Post

1)Multi Break Point Envelope/LFO

2)Save and load automation curves (same format as MBP Envelopes and LFOs)

3)Batch Processing/saving/exporting/

4)Normalize

5)Freeze Track (like Ableton, bounce until silent to effeciently capture reverb tails and delays)

6)Different Multi monitor formats. I'd like to see only devices and Waveform/midi on one monitor

Post

- Transient/onset editing in Bitwig is really awful. It's tedious and really backwards compared to everything else out there. You can't even set a threshold to set onsets.

- Dragging and dropping audio event from the arrange view to the drummachine shouldn't require a destructive bounce just to get one slice of the events to drag over. If I slice an even in the arrange view and just want that sliced audio to drag and drop into the drum machine, Bitwig is too dumb to know that I don't want to slice the audio, or I don't want the rest of the slices to be transferred over to the drum machine as well. It's a really wonky workflow and I have no idea who thought it was a good idea. It takes 3 or 4 steps to do something that Studio One, Logic, Ableton do in one.

- Resizable meters/faders please.

- The piano roll has been mentioned quote a bit in this thread.

- Better/easier distinction between clips and events. Look I get that events and clips are different but when you are editing things this workflow is clunky. They really need to re-think how this works and/or make it something users explicitly do. For example in S1, they have a similar concept to Events, you basically just group the clips but you can still dive into the clips within the group. Things like Reverse etc work as you'd expect instead of whatever Bitwig is doing (If I have say a kick sliced out in the arrange view then reverse that it will literally reverse the whole audio clip). Otherwise I kind of don't see the point of events. Especially for audio.

I don't care about fancy synth features. I need the meat and potatoes here. Fancy synth features are nice when the basics are there too.
Studio One // Bitwig // Logic Pro // Ableton // Reason // FLStudio // MPC // Force // Maschine

Post Reply

Return to “Bitwig”