3.2 speculations

[Vladislav_Gronk]

I know the collaboration feature was part of the original launch promises, but is there really a big market for that? I hope they focus on improving other things first and leave (imo) gimmicky features like that for the future.

[aMUSEd]

Midi grid and midi capture are the main things I'd like to see next

More filter modules in the grid are also needed

[SLiC]

I know the collaboration feature was part of the original launch promises, but is there really a big market for that? I hope they focus on improving other things first and leave (imo) gimmicky features like that for the future.

If it doesn't take any real development time (as apparently it is already built in) they may as well just get it out then all of the initial promises are fulfilled and we can move on to new 'big' things. Personally I am interest to see it, I have more than 1 computer in my studio, networking them and sharing processing/projects would be very useful if this is what it does (audio/midi pipeline like fxteleport). I think we will also get the midi/audio/comping type updates 'as well' as many of these are actually quite simple, Bitwig just likes to realy integrate the workflow so I am sure they will be 'special'

[antic604]

Bitwig just likes to realy integrate the workflow so I am sure they will be 'special'

Or awkward, like audio clips being a container and to stretch a sample or save it you need to go to the event in edit window... It's actually pretty surprising that 'reverse' function works as it does, because it could well just reverse evens themselves but keep their order in the clip unchanged

Does anyone know what's the benefit of using clip containers?? They can't even hold audio & MIDI events at once, which would make a great sense to use for bounce-in-place, where you could slip-edit the MIDI back in the view when you wanted to edit it and re-bounce again...

[SLiC]

'special' isn't necessarily good

[aMUSEd]

I know the collaboration feature was part of the original launch promises, but is there really a big market for that? I hope they focus on improving other things first and leave (imo) gimmicky features like that for the future.

If it doesn't take any real development time (as apparently it is already built in) they may as well just get it out then all of the initial promises are fulfilled and we can move on to new 'big' things. Personally I am interest to see it, I have more than 1 computer in my studio, networking them and sharing processing/projects would be very useful if this is what it does (audio/midi pipeline like fxteleport). I think we will also get the midi/audio/comping type updates 'as well' as many of these are actually quite simple, Bitwig just likes to realy integrate the workflow so I am sure they will be 'special'

I suspect in the current situation where people are social distancing the market for online collaboration tools will increase hugely. Bitwig would be smart to strike while the iron is hot.

[mrfrenkie]

Hope "online collaboration feature" will never implemented. There so many basic industry features that still not presented in Bitwig. Such as normalize audio, sample browser (without pages and correct sorting), midi workflow (stretching clips, non-destructive quantize, legato, chords or scales, drum mode etc), snapshots, cpu (ram) monitor, fixed audio engine (!), panel management, MSEG, external audio editor, takes system, video support, EQ, warp markers quantize, monitoring FX, plug-in window controls, fixed layered editor, gui improvements and some smart algorithms - audio to midi, transient detection, groove extracting, fully root note detection, some modern oscillators and filters (or analog), ARA integration, file metadata (such bpm, waveforms, root notes), project version management, services integration (soundcloud, splice?), convolution reverb, and more...

Even Grid devices not integrated in Bitwig more than regular plug-ins. And you can use any modular plugin instead with nothing to lose. There no benefits for native devices.

[SLiC]

Hope "online collaboration feature" will never implemented. There so many basic industry features that still not presented in Bitwig. Such as normalize audio, sample browser (without pages and correct sorting), midi workflow (stretching clips, non-destructive quantize, legato, chords or scales, drum mode etc), snapshots, cpu (ram) monitor, fixed audio engine (!), panel management, MSEG, external audio editor, takes system, video support, EQ, warp markers quantize, monitoring FX, plug-in window controls, fixed layered editor, gui improvements and some smart algorithms - audio to midi, transient detection, groove extracting, fully root note detection, some modern oscillators and filters (or analog), ARA integration, file metadata (such bpm, waveforms, root notes), project version management, services integration (soundcloud, splice?), convolution reverb, and more...

Even Grid devices not integrated in Bitwig more than regular plug-ins. And you can use any modular plugin instead with nothing to lose. There no benefits for native devices.

Many of those 'basic' industry features are not in DAWS that have been around for 20 years!

About half of those features I have no need for at all and think are an utter waste of time (splice integration!) or I already have them in Studio One, so I hope the developers don't waste a second implementing them, I want Bitwig to be different and specialised....

See, Dev's can't please everyone

Online collaboration feature is already integrated, it would be dumb not to put it out for the people that will find it useful.

[BufoBufo]

I'd be happy if they finally implemented proper VST multi-out routing into audio tracks, so one could properly *record* and monitor the discrete chains without the audio tracks' meters being dead

[antic604]

...

sample browser (without pages and correct sorting) - what's wrong with current browser?

cpu (ram) monitor - there's a CPU monitor, RAM isn't really a problem for 95% of cases

fixed audio engine (!) - what's wrong with it, specifically?

panel management - it's much more flexible than competition, don't know what's wrong with it?

external audio editor - read that slowly: EXTERNAL

EQ - there's three, each of which can be turned into left/right, mid/side and dynamic EQ

plug-in window controls - there is, just look it up in keyboard shortcuts

fixed layered editor - what's wrong with it? it's much better than MOST daws have

gui improvements - again, what specifically?

some modern oscillators and filters (or analog) - why? you said "there are no benefits to native devices" - make up your mind

project version management - it's called Ctrl+Shift+S and also Bitwig saves incrementally 10 last versions of the project in case you forget the above shortcut

Even Grid devices not integrated in Bitwig more than regular plug-ins. And you can use any modular plugin instead with nothing to lose - you gotta be kidding me, or you simply have not dove deep enough into Grid

There no benefits for native devices - stick to Reaper, then

[antic604]

I'd be happy if they finally implemented proper VST multi-out routing into audio tracks, so one could properly *record* and monitor the discrete chains without the audio tracks' meters being dead

What's wrong with using Audio Receivers?

[BufoBufo]

What's wrong with using Audio Receivers?

1) You can monitor but not record what the Audio Receiver receives
2) To record some specific chain of a multiout VST, you have to explicitly select that chain as the audio track's input. And even then when you arm that audio track, the meter remains dead although you hear (and can record) actual audio data received from the VST's chain. That's just stupid.

Please correct me if I'm missing something here as I'm aware you know quite a lot about Bitwig.

[antic604]

What's wrong with using Audio Receivers?

1) You can monitor but not record what the Audio Receiver receives
2) To record some specific chain of a multiout VST, you have to explicitly select that chain as the audio track's input. And even then when you arm that audio track, the meter remains dead although you hear (and can record) actual audio data received from the VST's chain. That's just stupid.

Please correct me if I'm missing something here as I'm aware you know quite a lot about Bitwig.

Well, I'm sure you're right if you say this is how it works - I never had the reason to use multi-out VSTs, but I'll defintiely check what's up in the evening and let you know. I'd expect in BOTH of those cases for Bitwig to work.

[antic604]

Please correct me if I'm missing something here as I'm aware you know quite a lot about Bitwig.

Ok, you're not wrong - both of them should work, but don't!
Please contact support@bitwig.com if you haven't alrady

However, I found a workaround that's usable: instead of Audio Track for each audio out insert a Instrument Track, on each put an Instrument Layer and within it stick an Audio Receiver pointing to relevant audio out from the multi-out VST. With this you can:
- monitor the audio
- record your live performance onto the VST track as MIDI clip
- when you want to convert to audio - select empty time on the audio tracks corresponding with the MIDI clip's length, right click on it and select Bounce In Place.

"Easy"

Zrzut ekranu (25).png

[Trancit]

sample browser (without pages and correct sorting) - what's wrong with current browser?

e.g. that you cannot use it as long as it is scanning... if you try to scroll down it always scrolls up automatically again... not a biggie but present and silly behaviour
Second... saved bwclips always are played back at 120bpm...no matter what their original bpm is... silly!!
Timestretch algo for tempo synced playback is the worst mankind ever heard... useless!!
No tempo synced playback without having the project running... silly!!

cpu (ram) monitor - there's a CPU monitor, RAM isn't really a problem for 95% of cases

On which planet do you live??? i.e. every single instance of Avenger takes more than a gig of RAM plus many others with similar poor resource sharing... not to speak about bigger sample libraries
a standard project with some VST´s and samples can easily cause a problem on a 32gig system not to speak for systems with less RAM

fixed audio engine (!) - what's wrong with it, specifically?

i.e. the silly attack spike by playing back a project with some muted tracks... often discussed here and present since a very long time...
Compared to Ableton`s engine Bitwig reaches perhaps 20% of stability...

external audio editor - read that slowly: EXTERNAL

Yes... and it would be extrem handy... to be able to open any sample/audio file in an external editor from within Bitwig and be able to overwrite the edited file that Bitwig uses the new file from that moment on... that´s an extrem handy feature and present in Ableton from ...dunno... day one???
Same goes about the ability to rename files within Bitwig´s browser... that I don´t end up with master bounce... master bounce 2...master bounce 3... master bounce 4... you get the idea...

EQ - there's three, each of which can be turned into left/right, mid/side and dynamic EQ

And not a single one offers a clean 24db LP... every EQ offers just an "analog" emulation...
Second... the volume scale by editing inside the display is the worst I´ve ever seen... every little movement changes the node volume by several db´s...

fixed layered editor - what's wrong with it? it's much better than MOST daws have

But auto zoom is often messed up...

...

Just a few examples...