CONCISE BITWIG FEATURE REQUEST

[Semipro]

1-Edit automation in tablet touch mode
2-Time signature change
3-Piano roll improvement: the pen tool should repeat the note when hold, not extend it. A step recording option would be nice, and the ability to stretch midi notes too.
4-Arpeggiator improvement: Load and play/transpose midi clips across the keyboard, hold/latch option
5-Trim/crop, normalize and warp inside sampler
6-Multi track spectrum analyzer inside eq 2.0
7-Add Audio track from pop up browser
8-Drawing LFO/Envelope tool mapable to anything on any track not only nested devices
9-Convert 3rd party presets to bitwig's format
10-Share user's presets

[mclstr]

I know this is old and out of date, but I am surprised nobody mentioned the limited midi implementation?

I can easily talk midi between Ardour, Qtractor, Renoise, ..., many (not VST) software synths but not so easy with BW.

BW needs jack midi bad!

Yes, I know that there are workarounds, but they are messy and unreliable.

[David Boura]

I bump my FR for Bitwig 1 here. This has been deleted in under 5 mins from the 1.3.16 RC1 thread...

Eq Spectrum... waiting for it since day 1;
An updated and complete manual;
Official updated tutorials (esp. Panel Mappings from A to Z);
Life on the youtube channel;
Hotkeys and midi mapping for absolutely everything:
- including track/device select, preset saving, browser window
- possibility to change default Bitwig ones without exception.
- a hotkey to add a device and another one for presets (not the same "b").
- not per project, but in the general settings, save/load.
Automation for everything (would solve the stop at ends of tracks i.e)
Global transpose indicator in the top bar;
Faster project (or engine?) loading, nowadays i have to wait 5 to 10 sec before Bitwig plays something;
Sometimes one of your vsts didn't load properly, or you uninstalled it, the entire channel doesn't play. You have to chase the culprish and for some projects, it takes time. Maybe something could be done on that topic? A warning list on loading?;
Offical support for Push;
Possibility to type in text in Browser window while CAPS is on (or de-activate it when it's opened, just an idea);
Ability to add text notes to a project;
More scripts for midi controllers, even an LPD8 is not recognized;
Back of the drummachine (or other multi-out channel) individual soloing behavior (now if you solo the snare, that's all you hear for the entire track, this is absolute nonsense);
Why when changing a device preset, it looses all the mapping for i.e the channel faders?;
Zoom in views, and scroll in devices with the mousewheel;
More macro knobs for devices (16?);
More Lfo mods in the LFO tool, it is a headache as it actually works in a Russian doll way. And possibility to record them into automations, and stop them from evolving when the track is stopped. We could bake the result of random lfo, so it always play the same.
We could create random patches/sounds, and save them as presets;
Proper stretching;
Improved visibility of played notes in the piano-roll;
Better visualisation of the velocity change on a note, when using Ctrl+shift+drag. For now we have to deselect to see the result;
We don't see the complete names of drums in the piano-roll;
More colors in the color picker;
Browser can't be moved even partially outside the screen;
The return of the back of my microphone under Wasapi mode, as it was in the past.
Undo/redo for Vsts.

And this:
Bug with tempo and pre-roll:
http://www.kvraudio.com/forum/viewtopic ... s#p6671119

Since the V2 announcement (fiasco), i add to the pile:
True and honest communication with us, that is also a form of respect.



As you won't answer and adress this (i know by experience), i definitively left the boat since i saw the two letters V, and 2.

[dom@bitwig]

I bump my FR for Bitwig 1 here. This has been deleted in under 5 mins from the 1.3.16 RC1 thread...

Correct, it does not belong there as i pointed out in the PM i sent you.

Cheers,
Dom

[David Boura]

I bump my FR for Bitwig 1 here. This has been deleted in under 5 mins from the 1.3.16 RC1 thread...

Correct, it does not belong there as i pointed out in the PM i sent you.

Cheers,
Dom

Mmm, no fix for full screen mode on Win 10 1607

This is the first comment for the 1.3.14 RC1, as an exemple.

Why didn't you delete it?

[David Boura]

Any word about my FR, like the simplest ones (color picker) instead of making an new modular system?
What about the tempo bug?

Are you kidding?

[dom@bitwig]

I bump my FR for Bitwig 1 here. This has been deleted in under 5 mins from the 1.3.16 RC1 thread...

Correct, it does not belong there as i pointed out in the PM i sent you.

Cheers,
Dom

Mmm, no fix for full screen mode on Win 10 1607

This is the first comment for the 1.3.14 RC1, as an exemple.

Why didn't you delete it?

Because it is not offtopic.
Re-posting a big feature wish list, however, is and we would like to keep the RC thread on topic.

Cheers,
Dom

[David Boura]

You are actually absolutely kidding me, publicly.

1 - Go clean up all the new releases threads from FR, complaints etc.
2 - Answer my FR and bugs

It's not a game, it's about keeping your customers, and de facto your job.

[dom@bitwig]

I'm not kidding you, far from my intention.
The forum is not the right place for feature requests and bug reports, as stated in the forum rules:
viewtopic.php?f=259&t=420129

Cheers,
Dom

[Coockie1176ln]

You are actually absolutely kidding me, publicly.

1 - Go clean up all the new releases threads from FR, complaints etc.
2 - Answer my FR and bugs

It's not a game, it's about keeping your customers, and de facto your job.

Dom is right it has been like this since forever feature request of rc threads. Just because you dislike the new pay plan you dont have to make everything an issue where there is non

[WXLF]

Eq Spectrum... waiting for it since day 1;
An updated and complete manual;
Official updated tutorials (esp. Panel Mappings from A to Z);
Life on the youtube channel;
Hotkeys and midi mapping for absolutely everything:
- including track/device select, preset saving, browser window
- possibility to change default Bitwig ones without exception.
- a hotkey to add a device and another one for presets (not the same "b").
- not per project, but in the general settings, save/load.
Automation for everything (would solve the stop at ends of tracks i.e)
Global transpose indicator in the top bar;
Faster project (or engine?) loading, nowadays i have to wait 5 to 10 sec before Bitwig plays something;
Sometimes one of your vsts didn't load properly, or you uninstalled it, the entire channel doesn't play. You have to chase the culprish and for some projects, it takes time. Maybe something could be done on that topic? A warning list on loading?;
Offical support for Push;
Possibility to type in text in Browser window while CAPS is on (or de-activate it when it's opened, just an idea);
Ability to add text notes to a project;
More scripts for midi controllers, even an LPD8 is not recognized;
Back of the drummachine (or other multi-out channel) individual soloing behavior (now if you solo the snare, that's all you hear for the entire track, this is absolute nonsense);
Why when changing a device preset, it looses all the mapping for i.e the channel faders?;
Zoom in views, and scroll in devices with the mousewheel;
More macro knobs for devices (16?);
More Lfo mods in the LFO tool, it is a headache as it actually works in a Russian doll way. And possibility to record them into automations, and stop them from evolving when the track is stopped. We could bake the result of random lfo, so it always play the same.
We could create random patches/sounds, and save them as presets;
Proper stretching;
Improved visibility of played notes in the piano-roll;
Better visualisation of the velocity change on a note, when using Ctrl+shift+drag. For now we have to deselect to see the result;
We don't see the complete names of drums in the piano-roll;
More colors in the color picker;
Browser can't be moved even partially outside the screen;
The return of the back of my microphone under Wasapi mode, as it was in the past.
Undo/redo for Vsts.

You can remove spectrum in EQ and better visibility for piano roll keys because those will be in 2.0 (and please don't say you expected them in 1.0, they never made that promise, that I know of)

Some would be nice improvements, but no offense, this huge list of feature requests kind of sounds like "tailor Bitwig specifically for me"

[David Boura]

Eq Spectrum... waiting for it since day 1;
An updated and complete manual;
Official updated tutorials (esp. Panel Mappings from A to Z);
Life on the youtube channel;
Hotkeys and midi mapping for absolutely everything:
- including track/device select, preset saving, browser window
- possibility to change default Bitwig ones without exception.
- a hotkey to add a device and another one for presets (not the same "b").
- not per project, but in the general settings, save/load.
Automation for everything (would solve the stop at ends of tracks i.e)
Global transpose indicator in the top bar;
Faster project (or engine?) loading, nowadays i have to wait 5 to 10 sec before Bitwig plays something;
Sometimes one of your vsts didn't load properly, or you uninstalled it, the entire channel doesn't play. You have to chase the culprish and for some projects, it takes time. Maybe something could be done on that topic? A warning list on loading?;
Offical support for Push;
Possibility to type in text in Browser window while CAPS is on (or de-activate it when it's opened, just an idea);
Ability to add text notes to a project;
More scripts for midi controllers, even an LPD8 is not recognized;
Back of the drummachine (or other multi-out channel) individual soloing behavior (now if you solo the snare, that's all you hear for the entire track, this is absolute nonsense);
Why when changing a device preset, it looses all the mapping for i.e the channel faders?;
Zoom in views, and scroll in devices with the mousewheel;
More macro knobs for devices (16?);
More Lfo mods in the LFO tool, it is a headache as it actually works in a Russian doll way. And possibility to record them into automations, and stop them from evolving when the track is stopped. We could bake the result of random lfo, so it always play the same.
We could create random patches/sounds, and save them as presets;
Proper stretching;
Improved visibility of played notes in the piano-roll;
Better visualisation of the velocity change on a note, when using Ctrl+shift+drag. For now we have to deselect to see the result;
We don't see the complete names of drums in the piano-roll;
More colors in the color picker;
Browser can't be moved even partially outside the screen;
The return of the back of my microphone under Wasapi mode, as it was in the past.
Undo/redo for Vsts.

You can remove spectrum in EQ and better visibility for piano roll keys because those will be in 2.0 (and please don't say you expected them in 1.0, they never made that promise, that I know of)

Some would be nice improvements, but no offense, this huge list of feature requests kind of sounds like "tailor Bitwig specifically for me"

This is my Bitwig 1 FR, it doesn't ask for other people FR.
Done before the V2 announcement, EQ piano roll included.

Let them answer us please, stop doing their job. We're not hotline workers, nor testers and bug chasers.

Someone is passing the day chasing unpleasant comments (for them) while he could just answer our questions.

[David Boura]

You are actually absolutely kidding me, publicly.

1 - Go clean up all the new releases threads from FR, complaints etc.
2 - Answer my FR and bugs

It's not a game, it's about keeping your customers, and de facto your job.

Dom is right it has been like this since forever feature request of rc threads. Just because you dislike the new pay plan you dont have to make everything an issue where there is non

No, all releases threads have their complaints etc. I just prove it with one example. Just go check.
Issue with plan? Go find one word from me talking about this.

Once again, i'm talking to Bitwig.

[David Boura]

You are actually absolutely kidding me, publicly.

1 - Go clean up all the new releases threads from FR, complaints etc.
2 - Answer my FR and bugs

It's not a game, it's about keeping your customers, and de facto your job.

Dom is right it has been like this since forever feature request of rc threads. Just because you dislike the new pay plan you dont have to make everything an issue where there is non

And my FR is from before the V2 annoucement, so you just said absolute BS.

[TasmanianAngel]

Here's hoping this already exists: CTRL+D duplicates notes in selected time range. How about a keyboard shortcut that duplicates selected notes but vertically, octave up or down?