Things you would love to see happening in Bitwig

Official support for: bitwig.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Ogopogo wrote:Bitwig should remember if you are using fold in the piano roll for each track. I don't want to switch back and forth when I go back and forth between drums and melodic stuff.
Yup +1, I'm constantly having to keep 'folding' my drum track

Post

The thin scrollbar below the device box could be thicker!
:hug:

Post

If you change the color of an effect track, i think the send knob should reflect this color! :)
:hug:

Post

# hope i don't lose meta tag when i change or upgrade computer or reinstall bitwig.
#kontakt 4 like meta tag database browser with add/rename tag.
#batch tag for samples/presets/vsts/whatever.

Post

Crackbaby wrote:The thin scrollbar below the device box could be thicker!
+1 i'd like to see that too

Post

Crackbaby wrote:If you change the color of an effect track, i think the send knob should reflect this color! :)
WOW! didnt think about that one but +1
:tu:

Post

1) Full undo history (in file with project as Reaper)
2) Undo for VST plug-ins!
3) VST plugins panel with basic functions: track/plugin name, bypass, preset selector.
4) Delay compensation for container devices: FX Layer, FX Chain (try dry/wet with iZotope for example)...
5) Switching on/off devices via macros.
6) Modulate LFO frequency via keytracking in Polysynth.
7) Mapping LFO frequency via macro when LFO synced.
8) Restart phase every OSC in Polysynth.
9) Input/Output in inspector when multiple tracks selected.
10) Something like marque tool or selecting other mouse tools with modificators.
11) Drag'n'Drop tracks of project in browser, like Ableton. Now this rudimentary.
12) time line!
13) Change pitch for RAW audio.

PS: Saving my audio clips, drum machines with content (samples). As container or just folder. Optional.

Sorry my english.)

Post

automation line LEVEL preview, when you click on it (like in FL)

I painted a green line here:
Image

In FL that looks like:
Image
Last edited by _TLG_ on Sun Apr 27, 2014 11:50 am, edited 1 time in total.

Post

mrfrenkie wrote: 4) Delay compensation for container devices: FX Layer, FX Chain (try dry/wet with iZotope for example)...
So containers don't have PDC? Wow, that sucks. I wonder what else doesn't have PDC, it seems that more and more things are cropping up.

Post

Letting the arpeggiator pass through/use events/expressions that it doesn't generate itself, such as pan, pitch and timbre.

E.g. if a clip's notes have 100% pan, the output of the arpeggiator should also have 100% pan.

Post

a good vocoder device like in live

Post

kling1 wrote:a good vocoder device like in live

Post

Besides all the other feature requests...

I would love to see the ability for various devices to be per voice (polyphonic, not just monophonic)

So for example, one could nest the resonator in the polysynth fx slot and have it be polyphonic... or nest the ladder filter in FM4 (which has no filter) and have it be polyphonic (optional)

Post

pdxindy wrote:Besides all the other feature requests...

I would love to see the ability for various devices to be per voice (polyphonic, not just monophonic)

So for example, one could nest the resonator in the polysynth fx slot and have it be polyphonic... or nest the ladder filter in FM4 (which has no filter) and have it be polyphonic (optional)
+1

Also, again, make the mod matrix modulatable/automatable in FM4. All FM VSTs allow this but not the ultra simple built-in one? Come on.

Post

Simulant wrote:
mrfrenkie wrote: 4) Delay compensation for container devices: FX Layer, FX Chain (try dry/wet with iZotope for example)...
So containers don't have PDC? Wow, that sucks. I wonder what else doesn't have PDC, it seems that more and more things are cropping up.
External instrument needs delay compensation, meaning the current imementation of pdc is insufficient for using external hardware.

Post Reply

Return to “Bitwig”