Your TOP 5 feature requests for Bitwig

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

Post

My Top Feature is Browser Midi Playback Preview with activated Synth, like in Studio One :tu:

Post

SLiC wrote: I would probably keep using S1 for the melodyne intigration, but I think BWS could (and should) integrate ARA quite easily.

Although S1 has lots of other benefits and features, it would probably only take both of above for me to seriously consider using BWS as my main DAW.
Yes to ARA. For me it is an almost essential feature.
So now I am primarily looking at the following DAW's:
Studio One.
Sonar
Samplitude
Waveform
Mixcraft

Number two on my list for BWS is that it has a Modular environment such as
Multi-instruments or Patcher.

Editable Midi Event list.

Scrub

Point and play as in Cubase. Point to any location on a waveform and hear it even if it is muted.

Post

larsomat wrote:In that order

1.) ableton-style grain delay effect (most wanted!!!!)
2.) Midi recall for bounced regions
3.) Easy track freeze
4.) Easy to see indicator when one/some of your sandboxed plugins crashed (I often don't see it in large projects)
5.) AU support, so I can use my sinevibes plug-ins (one can dream...)

regarding 3., I've already developed a good bounce/deactivate workflow in Bitwig, but sometimes I just want to preserve some CPU quickly and a "simple" freeze button would be quite helpful for that.
4.) has been solved in Bitwig2.

1 done. 4 to go. :clap:

Post

I can't believe it doesn't have rex support. Does 2.0 have this?

Post

Is there any real advantage with a Rex file when Bitwig can slice at transients and loop/timestreach a standard wave file?
X32 and 24C mixers, S88MK3, Live + PUSH 3, Osmose, RedShift 6, Pro3, S4, Tempera, Syntakt, Digitone, OP1-F, OPXY, TR-1000, Eurorack, TD27 Drums, Guitars, Basses, Amps and of course lots of pedals!

Post

Hmm no,. not really i guess. Put onsets on the places you want, and slice to DMaschine.
But i can imagine that a lot of people got a pile of them on their HD.

Post

AU and NKS support.

Post

I don't want to do that, I want to be able to use the rex files I have :shrug:

And they are significantly better than trying to time stretch yourself ;)

The workaround is using them in "arsenal" but it's a PITA to load them.

Again, considering rx2 is a standard, I cannot believe they are not available (especially considering that it's so loop oriented)

Post

Hello, im new here i grow up with fruity loops1-4, reason 1-4 than ten years cubase i missed pojekt autosave and perhaps chronologigal nummeric for projekts workstate. At secound i missed syses and global sysex and since many years nrprn controllers in all daws thats a problem.At third the metronome volume cant be saved global.If i make a new song and have forgotten control metronom volume my dynaudio blow me away from chair with85-105 db.

Timo from hessen de

Post

At this point I really just care about them sorting out the midi issues. Tracks need to be able to receive all midi channels and filter them, and record the midi channel that any given note was recorded with. Especially needed for MPE. Don't halfway implement things!

After that it would be cool to see some nice granular and timestretch options in sampler. After loop fades of course. Let's bring sampler into the 90's before the 2000's. But at least I can avoid using sampler. I can't avoid using midi.

Post

As someone who never switched for these reasons, yes they matter. :x

1. ReWire- full implementation, i.e. Bitwig remains a VST host as a slave.

2. SysEx - Why cripple your software the same way Live did? Why?

3. Get the basics of your touch screen support working on OSX.- I have a Slate Raven here, and even with the extra support of their V-Control and UPDD implementation, Bitwig works worse in touch screen mode, even though you can choose that as an option in OSX! Slate figured it out....

4. Get the network collaboration implementation up. - This would probably get me to switch without the others, if I could convince my vocalist to switch..

5. Implement ways to switch between instruments live like Mainstage does- and beat Ableton in the live performance market! I was thinking about how Maschine and Live both offer a lot, but they demand you work in certain ways. Live demands you 'perform' more like a DJ than a keyboard/MIDI controller player.

They did all these things and I doubt I would be the only person who was a constant salesperson hype team for them.

Post

I would love to have tempo/clock change per track or clip. absolute and divisions.

Post

Echoes in the Attic wrote:At this point I really just care about them sorting out the midi issues. Tracks need to be able to receive all midi channels and filter them, and record the midi channel that any given note was recorded with. Especially needed for MPE. Don't halfway implement things!
+1

yes, please... make Bitwig able to record all midi data!! It seems kinda bizarre to me that in 2017 we have to ask for the ability to record, playback and export midi data exactly as it is played.

Post

[quote="Echoes in the Attic"]At this point I really just care about them sorting out the midi issues. Tracks need to be able to receive all midi channels and filter them, and record the midi channel that any given note was recorded with. Especially needed for MPE. Don't halfway implement things!
[/quote]

I have to agree with this, straighten out the basics first.

1) Fix the MIDI implementation.
2) Make the UI respond to changes in the editors instantaneously like other modern DAWs. Currently you have to release the mouse button every time before any change takes effect. This really slows down the workflow. Ugh.

Post

Oh ya and finish touch screen mode. Why make a mode where you can't draw or edit automation?

Post Reply

Return to “Bitwig”