Your TOP 5 feature requests for Bitwig
- KVRAF
- 4805 posts since 21 Jan, 2008 from oO
there is bounce in place and regular bounce pre/post fader or custom version. What do you mean?isosis wrote:bounce track
JamWide - a cross-platform Ninjam client for DAWs
- KVRist
- 195 posts since 14 Dec, 2013
1. Polysynth redesign or Polysynth2 which includes:
- more punchy adsr envelopes (current ones sounds terrible)
- more emphasis on "EG" (filter envelope) control knob. I know I can target cutoff with "feg" modulator for more emphasis but this is bad soultion for many reasons.
- getting rid of wierd punchiness on unisono sounds ( when playing supersaw you can clearly hear "ompf" sound on the start of every note even if "R"(retriger) button is off )
- sine/triangle waves
2. Being able to control certain parameter in all layers at once inside the instrument/fx layer devices - like controlling cutoff in multiple polysynths at once ( assigning everything to macro controls is NOT an ergonomic solution ).
3. Soft Clipper Device
< no more requests >
- more punchy adsr envelopes (current ones sounds terrible)
- more emphasis on "EG" (filter envelope) control knob. I know I can target cutoff with "feg" modulator for more emphasis but this is bad soultion for many reasons.
- getting rid of wierd punchiness on unisono sounds ( when playing supersaw you can clearly hear "ompf" sound on the start of every note even if "R"(retriger) button is off )
- sine/triangle waves
2. Being able to control certain parameter in all layers at once inside the instrument/fx layer devices - like controlling cutoff in multiple polysynths at once ( assigning everything to macro controls is NOT an ergonomic solution ).
3. Soft Clipper Device
< no more requests >
-
- KVRist
- 250 posts since 16 Jul, 2014
In order of importance..
1. Better arrangement tools. Arrangement sections and scratch pad like in Studio One. At the moment a simple copy and paste can completely destroy your arrangement and cue points. For me this is where the workflow in Bitwig becomes a drag.
2. Midi control track. A new track type specifically for sending Midi control notes to plugins. So that you can easily see in the arranger what note is being sent, name the notes etc. Need this for plugins like Glitch2 that are controlled via midi notes.
3. File versioning in Dashboard. Group all the different versions of the same project together in the Dashboard.
4. Better clip organisation. Currently saving a clip puts them all in to one big folder. I have to manually create a folder structure in Windows for it work correctly. Im not using clips as much as I should/want because of this.
5. Better metering. Its still not great in V2.
A couple of others, not so important but still...
6. WASAPI Exclusive to work.
7. Make it possible to roll back a version upgrade.
1. Better arrangement tools. Arrangement sections and scratch pad like in Studio One. At the moment a simple copy and paste can completely destroy your arrangement and cue points. For me this is where the workflow in Bitwig becomes a drag.
2. Midi control track. A new track type specifically for sending Midi control notes to plugins. So that you can easily see in the arranger what note is being sent, name the notes etc. Need this for plugins like Glitch2 that are controlled via midi notes.
3. File versioning in Dashboard. Group all the different versions of the same project together in the Dashboard.
4. Better clip organisation. Currently saving a clip puts them all in to one big folder. I have to manually create a folder structure in Windows for it work correctly. Im not using clips as much as I should/want because of this.
5. Better metering. Its still not great in V2.
A couple of others, not so important but still...
6. WASAPI Exclusive to work.
7. Make it possible to roll back a version upgrade.
http://Freshby6.com
Bitwig since 1.0
Bitwig since 1.0
-
beliefsystemrecords beliefsystemrecords https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=325410
- KVRist
- 31 posts since 26 Mar, 2014
i only have 1
NEGATIVE TRACK DELAY
thx
NEGATIVE TRACK DELAY
thx
- KVRAF
- 26963 posts since 3 Feb, 2005 from in the wilds
Seems like more trouble than help. For example, every time you want to move a midi clip, you would also have to go to the control track and move those control notes instead of having the control notes be part of the clip when moving, duplicating, deleting.craigtumps wrote:
2. Midi control track. A new track type specifically for sending Midi control notes to plugins. So that you can easily see in the arranger what note is being sent, name the notes etc. Need this for plugins like Glitch2 that are controlled via midi notes.
- KVRist
- 183 posts since 13 Jan, 2015 from SLC, UT
1. Save New Version (just appends a number on the end of current working file)
2. Automatic enabling and disabling of previewing notes in piano roll (disables preview when track is playing). Or at least a key that I can use to toggle it on and off.
3. Chords in piano roll.
4. Better ability to route midi. So I can have 16 midi channels in from the same device and send them to individual tracks.
5. More color options instead of the current small group of 16.
6. I may be missing how to do this but I would really like to be able to copy and past knob values.
7. I may be missing this as well, but a way to detach and expand the analysis displays.
Not all huge things, but these are minor things that annoy me.
2. Automatic enabling and disabling of previewing notes in piano roll (disables preview when track is playing). Or at least a key that I can use to toggle it on and off.
3. Chords in piano roll.
4. Better ability to route midi. So I can have 16 midi channels in from the same device and send them to individual tracks.
5. More color options instead of the current small group of 16.
6. I may be missing how to do this but I would really like to be able to copy and past knob values.
7. I may be missing this as well, but a way to detach and expand the analysis displays.
Not all huge things, but these are minor things that annoy me.
-
- Banned
- 7 posts since 24 Sep, 2016
i just need stretched session tracks*...... (less larger)
(for example if ur screen show more traxx than this laptop HD....)
(*columns, clips, squares....)
**like scalable or dividable (vert+HOR)
(for example if ur screen show more traxx than this laptop HD....)
(*columns, clips, squares....)
**like scalable or dividable (vert+HOR)
-
- KVRist
- 250 posts since 16 Jul, 2014
Im a bit confused, I cant put midi control notes in with the clip as it will play sound right? Or is there way to have control notes combined with a clip that wont be sent to the synth?pdxindy wrote:Seems like more trouble than help. For example, every time you want to move a midi clip, you would also have to go to the control track and move those control notes instead of having the control notes be part of the clip when moving, duplicating, deleting.craigtumps wrote:
2. Midi control track. A new track type specifically for sending Midi control notes to plugins. So that you can easily see in the arranger what note is being sent, name the notes etc. Need this for plugins like Glitch2 that are controlled via midi notes.
http://Freshby6.com
Bitwig since 1.0
Bitwig since 1.0
- KVRAF
- 26963 posts since 3 Feb, 2005 from in the wilds
Can be done... how depends on the situation... I've only done that with synths that have some articulations and in that case, the notes do not play. If you have an FX plugin after a synth, then you would need to use note filter and/or note receiver to not send the notes to the synth.craigtumps wrote:Im a bit confused, I cant put midi control notes in with the clip as it will play sound right? Or is there way to have control notes combined with a clip that wont be sent to the synth?pdxindy wrote:Seems like more trouble than help. For example, every time you want to move a midi clip, you would also have to go to the control track and move those control notes instead of having the control notes be part of the clip when moving, duplicating, deleting.craigtumps wrote:
2. Midi control track. A new track type specifically for sending Midi control notes to plugins. So that you can easily see in the arranger what note is being sent, name the notes etc. Need this for plugins like Glitch2 that are controlled via midi notes.
-
- KVRist
- 261 posts since 19 Jan, 2008 from Poland
Basic things:
1) groove extract
2) saving channels as default
1) groove extract
2) saving channels as default
-
- KVRist
- 250 posts since 16 Jul, 2014
Yes so that's how I have been doing it but it gets a bit painful and confusing after a while. I create a track and send the notes to the receiver. But on the arranger I have no overview of whats going on. Its just dots in arranger track. What I do is name the clips so at least I have something to tell me whats going on. But especially when copy and pasting sections of the arrangement it gets messed up quickly, so this is kinda related to my first requested feature.pdxindy wrote:craigtumps wrote:pdxindy wrote:craigtumps wrote:
If you have an FX plugin after a synth, then you would need to use note filter and/or note receiver to not send the notes to the synth.
Another FX plugin I use that's controlled by midi notes is Looperator. You can do a lot with it but it starts to get complicated. I could get more out of these plugins if I had a better and quicker overview of what instructions Bitwig is sending to them.
To me its a whole new track type. Because its not audio or instrument notes. I dont need to see a mini display of the pattern on the arranger because there is no pattern! Maybe if the midi control notes could be edited directly on this control track in the arranger view. Right now I have to open the piano roll and move the piano notes around to change the instructions its sending. I just want to tell Looperator to play pattern 3 instead of 2 but I need to do that through the piano roll..
http://Freshby6.com
Bitwig since 1.0
Bitwig since 1.0
- KVRAF
- 26963 posts since 3 Feb, 2005 from in the wilds
Well, it is instrument notes... they are just midi notes, not a different kind of data. It's really kind of a hack by the VST developer... anywaycraigtumps wrote:
Yes so that's how I have been doing it but it gets a bit painful and confusing after a while. I create a track and send the notes to the receiver. But on the arranger I have no overview of whats going on. Its just dots in arranger track. What I do is name the clips so at least I have something to tell me whats going on. But especially when copy and pasting sections of the arrangement it gets messed up quickly, so this is kinda related to my first requested feature.
Another FX plugin I use that's controlled by midi notes is Looperator. You can do a lot with it but it starts to get complicated. I could get more out of these plugins if I had a better and quicker overview of what instructions Bitwig is sending to them.
To me its a whole new track type. Because its not audio or instrument notes. I dont need to see a mini display of the pattern on the arranger because there is no pattern! Maybe if the midi control notes could be edited directly on this control track in the arranger view. Right now I have to open the piano roll and move the piano notes around to change the instructions its sending. I just want to tell Looperator to play pattern 3 instead of 2 but I need to do that through the piano roll..
How would your new track type would be any different than what we already have? Each instance of Looperator (or other such plugin) would need a separate track, just like now.
If you do not want to have to open the piano roll, just make 1 note per clip. So if you have 4 patterns (pattern 1, pattern 2, pattern 3 and pattern 4) make 4 short clips each with 1 note named for the pattern. Then move, duplicate, etc. the clips on the arrange track how you want them to trigger patterns. Perhaps I am misunderstanding, but doesn't that already do what you are asking for?
-
- KVRist
- 250 posts since 16 Jul, 2014
pdxindy wrote: Well, it is instrument notes... they are just midi notes, not a different kind of data. It's really kind of a hack by the VST developer... anyway
How would your new track type would be any different than what we already have? Each instance of Looperator (or other such plugin) would need a separate track, just like now.
If you do not want to have to open the piano roll, just make 1 note per clip. So if you have 4 patterns (pattern 1, pattern 2, pattern 3 and pattern 4) make 4 short clips each with 1 note named for the pattern. Then move, duplicate, etc. the clips on the arrange track how you want them to trigger patterns. Perhaps I am misunderstanding, but doesn't that already do what you are asking for?
So you are right with that process, that's exactly how I do it currently. Also you are right its a hack by the developers. But there are many plugins that use this method of control so that's why I request its done better so its not such a hack. This track type could also help with sending midi trigger notes to external hardware too, triggering patterns etc..
This new track type could look like a one line step sequencer on the actual arranger view. I made this really bad mock up with a screen shot of NI Battery.

This way I could click on the steps and change the control directly on the arranger. It could open up as a drop down. No need for copy and pasting pre-made clips, no need for a piano roll or note receiver.
You could preset the midi control notes in the track device and most importantly name them. Currently all you see in the piano roll is the note e.g. C-2 that I have to mentally tie up to the plugin every time I open the piano roll. I notice Drum Machine is able to rename the notes but I cant see a way to do it myself, even that would help a lot..
I have multiple plugins controlled this way and it becomes a drag quickly. It hit me that this shouldn't be an instrument lane at all.
Last edited by craigtumps on Wed May 24, 2017 8:41 pm, edited 1 time in total.
http://Freshby6.com
Bitwig since 1.0
Bitwig since 1.0
-
- KVRer
- 3 posts since 21 May, 2017
1) ability to set mix faders by typing in a value, for when you need to hit 0 or suchlike
2) a virtual dip around 0 so I could get a fader to 0 rather than nowhere between -0.67 and 0.34
2) a virtual dip around 0 so I could get a fader to 0 rather than nowhere between -0.67 and 0.34
