3.2 speculations

[bolba]

...

....

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

Just wanted to point out that mr. Frenkie is constant Bitwig alpha/beta tester and you can find a lot of his presets in base Bitwig package, including dozen of Grid presets.
He also is pretty much only one Bitwig's advocate in Russian community I know.

So while some of his points may require further explanation, he is certainly knows what he talks about.

[bolba]

Regarding Sample browser what really sucks is lack of desire from Bitwig's team to support search of Google Drive / Team Drive (and most likely other modern cloud services) folders. (already reported with negative answer)

But I just don't understand why 6 years since release of Bitwig 1.0 we still cannot scale midi, at least using Inspector :/

[aMUSEd]

Regarding the browsers I would love the 2 browsers to be integrated into one - it’s annoying that the pop up browser can’t be docked and the docked browser can’t hot swap patches.

[bronswerk]

Regarding the browsers I would love the 2 browsers to be integrated into one - it’s annoying that the pop up browser can’t be docked and the docked browser can’t hot swap patches.

+1

[antic604]

Just a few examples...

Ok, most of those are irrelevant for my workflow or I've not encountered such problems. Perhaps I'm not enough of a power user.

[antic604]

Just wanted to point out that mr. Frenkie is constant Bitwig alpha/beta tester and you can find a lot of his presets in base Bitwig package, including dozen of Grid presets.
He also is pretty much only one Bitwig's advocate in Russian community I know.

So while some of his points may require further explanation, he is certainly knows what he talks about.

Could be. I don't recall ever seeing his posts here. Still, I think Grid is one of the things making Bitwig stand out. If they were to make Cubase or Reaper out of it, why would I even use it?

[machinesworking]

I'm on board for external audio editor for sure. Mostly owning Metasynth it's been a fantastic way to add it in as a tool in Ableton by assigning it to open audio files in Live.

Comping and online collaboration are big on my list as well.

UX improvements whether bugs or oddities are the main one though, it's weird that keyboard shortcuts can be stymied by unnecessary selections.

[mtelesha]

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...

I bounce the audio and put it in a group with the MIDI clip. I wouldn't want it with both. I get the flexibility of having the audio or audio. If I want the sound to extend past scene the clip is in your only option is to make it a MIDI. If I want to keep my CPU usage down I use audio.

[mtelesha]

Chord Track
Implemented like Waveform 11 (MIDI focused but can do samples) and not Studio One (Sample focused).

Music is organized by chord progressions As a old head jazz player I live and die by cheat sheets and chord sheets. It has ALWAYS drove me nuts that I can't organize a song easily to the chord progression. I finally could with Waveform 9 and it has been great. I can then do simple MIDI generation and have a working song in minutes and not hours. I then can edit and change.

Clip Launcher
End of a clip being played X times it launches next scene. I once again an old head still treats Bitwig as a sideways tracker. I use it for live performance and I HATE that I have to press for every change. I should only have to press a button when I am wanting to repeat a chorus or verse.

MIDI Controlers
When my controller gets unplugged I have to restart Bitwig. I can't get Bitwig to ever recognize it a second time. I can't restart in console and have it work again. Really is bad in the middle of a set.

I also am a programmer and the API is great but still too much work.

[stamp]

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.

I agree.

[BufoBufo]

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.

Thanks for your thoughts, but recording MIDI and post-bouncing is no option for me.
I want to jam on the Digitakt and record its 8 audio channels into 8 audio tracks in Bitwig in realtime using Elektron's Overbridge VST (which is the only way to record the DT's 8 channels separately). That is basically possible in Bitwig, but only with "dead" meters as described earlier.

Anyway, I don't want to hijack the thread for this issue. Will message support instead

UPDATE
Here's what support replied:
"no, this is by design: internal routings like this are not being monitored in audio tracks, as the signal is exactly the same as the source track and can be observed there and technically can't clip anyway."

In other words, yeah, there's audio going into those 8 audio tracks and it can be recorded, but hey, keep the other 8 VSTs chains open to check actual levels. Great. After insisting that this is inconsistent and waste of space, they're now "happy to put it on the wish list for future consideration". Sounds promising. NOT.

[brunomolteni]

Clip Launcher
End of a clip being played X times it launches next scene. I once again an old head still treats Bitwig as a sideways tracker. I use it for live performance and I HATE that I have to press for every change. I should only have to press a button when I am wanting to repeat a chorus or verse.

You can actually do that on a clip level... I do it all the time... you gotta select a clip and edit the clip action... so you setup some clips for "after 8 bars play the next one" and you're done.

[mtelesha]

Clip Launcher
End of a clip being played X times it launches next scene. I once again an old head still treats Bitwig as a sideways tracker. I use it for live performance and I HATE that I have to press for every change. I should only have to press a button when I am wanting to repeat a chorus or verse.

You can actually do that on a clip level... I do it all the time... you gotta select a clip and edit the clip action... so you setup some clips for "after 8 bars play the next one" and you're done.

Yes but the other clips in the previous scene still play. I want the whole next scene to play at the same time. (Am I missing something? Is it possible to have it all programmed out at clip level and forget the scene button?)

[bronswerk]

You can also do this on Scene level afaik.

[antic604]

Yes but the other clips in the previous scene still play. I want the whole next scene to play at the same time. (Am I missing something? Is it possible to have it all programmed out at clip level and forget the scene button?)

You can "do" this on the scene level, BUT you need to have clips - even empty ones - in tracks where you have active clips in following scene that you what played. This is because in reality there's no such thing as 'next scene action' - what this does is setting the same parameters for all the clips in the scene. So for example:

Code: Select all

Scene   1 2 3
Track1  . . X
Track2  X X X

if Scene 2 above is playing and you've set it to "play next" after 4 bars, then after 4 bars only Track2 will play, because there was no clip in Scene 2 on Track1 and it can't play next if it wasn't playing at all in the first place. Therefore inserting an empty clip in Track1 is required.