Things you would love to see happening in Bitwig

[kdgh]

Same idea as the WTF thread, but a little more positive.
What are the things that surprised you and would like to see more developed?

To me it's :

#1

A little project sample library like Renoise. I really like the browsing system how it works right now, but sometimes i just add a lot of samples in my little library as "i gonna use that later" without dragging them into the project immidiatly. In this way i already searched my sounds i want to work with, without looking for them over again in my complete samples-folder.

#2

Tell me if i'm wrong, but I would like to see a curve (from point to point) posibility in the sample-editting.

#3

Possibility when you switch project tabs, it also switches the activity of the project. This could be a preferences settings right?

Show what you think is quite done greatly, but could use that extra little feature!

[HamHat]

Multi outs, x64 support, 3rd party sidechaining, Audio Units, VST3, no PDC issues as promised, A customizable meta data folder (like studio one), and mono tracks. Everything else was pretty awesome! But still not enough to pull the trigger

[drhawk]

x64 support, what exactly do you mean?

I'm looking for:
PDC fixes
multi channel support (midi/audio)
group channels
dB values in text on the small volume peak displays in channel strips
Project + channel name on each VST window title bar
space bar starting playback when VST is focused
per channel ms delay
per channel midi transpose

[ThomasHelzle]

Same idea as the WTF thread, but a little more positive.
What are the things that surprised you and would like to see more developed?

To me it's :

#1

A little project sample library like Renoise. I really like the browsing system how it works right now, but sometimes i just add a lot of samples in my little library as "i gonna use that later" without dragging them into the project immidiatly. In this way i already searched my sounds i want to work with, without looking for them over again in my complete samples-folder.

#2

Tell me if i'm wrong, but I would like to see a curve (from point to point) posibility in the sample-editting.

#3

Possibility when you switch project tabs, it also switches the activity of the project. This could be a preferences settings right?

Show what you think is quite done greatly, but could use that extra little feature!

As for 1: I personally started to load a second project and place my selected samples/midi clips/sound devices in there, already laid out in some order on the tracks.
Then later on, I can drag and drop from one project to another - not only clips, but full tracks, devices, VSTs, whatever...

Not sure if I understand what you mean with number 2 - but automation can be curved? Press the ALT key and drag the inbetween-line up or down.
Or create a new point between two existing ones and ALT drag to create an S-shape.

I agree with number 3 as a possible preference, but most of the time I actually prefer to have it the way it is.

Cheers,

Tom

[Gnuus]

Would love to see polyphonic aftertouch!

[Gnuus]

....and support for the AxiomPro Hypercontrol!

[kdgh]

Same idea as the WTF thread, but a little more positive.
What are the things that surprised you and would like to see more developed?

To me it's :

#1

A little project sample library like Renoise. I really like the browsing system how it works right now, but sometimes i just add a lot of samples in my little library as "i gonna use that later" without dragging them into the project immidiatly. In this way i already searched my sounds i want to work with, without looking for them over again in my complete samples-folder.

#2

Tell me if i'm wrong, but I would like to see a curve (from point to point) posibility in the sample-editting.

#3

Possibility when you switch project tabs, it also switches the activity of the project. This could be a preferences settings right?

Show what you think is quite done greatly, but could use that extra little feature!

As for 1: I personally started to load a second project and place my selected samples/midi clips/sound devices in there, already laid out in some order on the tracks.
Then later on, I can drag and drop from one project to another - not only clips, but full tracks, devices, VSTs, whatever...

Not sure if I understand what you mean with number 2 - but automation can be curved? Press the ALT key and drag the inbetween-line up or down.
Or create a new point between two existing ones and ALT drag to create an S-shape.

I agree with number 3 as a possible preference, but most of the time I actually prefer to have it the way it is.

Cheers,

Tom

Ah thanks Tom!

Couldn't find #2, but now i do .

#4 for me would be sizable channels. It seems you can't minimize or maximize them. I don't really have a big screen, so it would be pleasant to have the possibility to change size.

[muelb]

1. VST Multi Outs
2. File Templates
3. Track Templates
4. Track Versions
5. Automatic and enditable clip fade in and fade out

[KGZM]

#1. Full JACK support(including both MIDI and JACK transport) and the ability to open audio and midi ports on Bitwig and bypass port discovery.

#2. Crossfading between clips and easy fade in/out envelopes.

#3 External sync.

That's really it. Everything else can go hang.


(For those that don't know JACK transport lets you unify the transport of every client connected to JACK so moving the transport in one moves it in all. Beyond audio programs you can use it to edit audio against video and animations and vice versa .. or do them simultaneously.)

[EvilDragon]

Pretty much what others are saying:

* multi-out VST
* templates for everything
* proper crossfades
* editable key commands and mouse modifiers
* option to run plugins natively instead of using IPC for lower CPU usage
* poly aftertouch definitely
* more flexible track height resizing (not having just two sizes, and this should be adjustable per-track, not global for all tracks)
* lower price

[ThomasHelzle]

There is a kind of track template, but it's a bit hidden:
If you drag a clip to the browser, it not only saves the clip, but all the devices and settings in the track too! It's saved to the clip tab in the browser automatically.
If you drag it back into an existing track, only the clip will be loaded.
But if you drag it to the empty space, a new track with all the devices is created.
Does that help a bit?

The Poly-Aftertouch situation is a bit complex at the moment.
I created a controller script for my AKAI MPD18 that supports Poly-AT:
http://www.kvraudio.com/forum/viewtopic ... 9&t=406759
In the script, the PA is translated into Bitwig Timbre and works with the internal Devices. The scripting changes needed are very simple.
In an ideal world, this would be re-translated to PA on the fly so all VSTs that support PA already (u-he, Alchemy etc.) would be able to use it.
This is not the case yet, but I hope we can convince them to implement that.
Even better would be an additional track in the event-editor for PA.

Otherwise I think most suggestions here are spot on, many I made myself in the beta phase.

Cheers,

Tom

[SWallace]

Support for Multi Out instruments is #1 by far. Omnisphere, Stylus RMX, and Kontakt are used everyday. Not having Multi Out supports kills the workflow and cpu related to these instruments.

[Cyrex]

First of all, I had a blast playing with Bitwig for the first time yesterday evening. Congratulations to the devs for bringing such an inspiring DAW to the crowds. And this is only version 1.0.. the future looks bright

As for the wish list, I am mainly concerned with features for a HW oriented workflow:

I would love to see proper (real-time) bouncing of HW device inputs.
This implies also proper recording of effect tails of bounced clips. I imagine this can be done best with an input level monitor that keeps recording until the input source sound level remains below a predefined threshold for a few seconds.

Note that both SW and HW synths/effects that are bounced would benefit from the preservation of tails.

Once you have clips with tails you require two further things for an optimal workflow:

- clip launcher looping should not cut playback of tail when the clip is looped
- arrangement tracks should allow overlap of tail from previous clip with next clip. (not a crossfade, but a constant mix of the two clips, both at 100% gain).

I would be thrilled if this were to be implemented.

Cheers,

Erik

[ZenPunkHippy]

I would love to see proper (real-time) bouncing of HW device inputs.
This implies also proper recording of effect tails of bounced clips. I imagine this can be done best with an input level monitor that keeps recording until the input source sound level remains below a predefined threshold for a few seconds.

I use a hybrid setup too, so this is important to me and raised during beta testing.

They are aware of the problem. General improvements to the export dialog (which is currently a bit basic) will happen in the future (no idea when, but it seemed pretty important to them).

Peace,
Andy.

[mobthrow]

Seriously... no fade in/out tool for audio?