Why you left Bitwig?

[moss]

So, it becomes a hybrid track? Does the audio clip take precedence over the MIDI clip? And does it just hide it behind?

If so, then that works for me.

It becomes a hybrid track, but the midi clip is not auto-saved when you bounce in place.

If I want to keep a copy of the midi clip and I am in Arrange, I now drag the midi clip to the launcher on the same track which makes a copy, then bounce in place.

Boo!!! Deleting anything without express user permission is a big no-no. Even ProTools keeps everything. And I mean everything.

There is a misunderstanding here:
- The normal Bounce method creates a new track and bounces the selected clip on there.
- Then there is "Bounce in place" which replaces the MIDI clip with its audio version. This is handy if you e.g. have a MIDI drum groove with several copies and now want to create a break in the n-th clip. Simply bounce it in place and edit the audio, which can happen on the same track.

[syntonica]

There is a misunderstanding here:
- The normal Bounce method creates a new track and bounces the selected clip on there.
- Then there is "Bounce in place" which replaces the MIDI clip with its audio version. This is handy if you e.g. have a MIDI drum groove with several copies and now want to create a break in the n-th clip. Simply bounce it in place and edit the audio, which can happen on the same track.

I don't think you read my original post. Adding a new track = adding unnecessary clutter.

[middle_color]

Hopefully when MIDI comping gets added, Bitwig will simply send the MIDI clip to comp lane below and put audio on the top lane.

That's very smart idea and very bitwigish . I did not even dream about mixed audio/midi comping... until now

[M-Prod]

(every time I work in Ableton I'm disappointed how much I need to do with the mouse)

despite Push2?

I tried to really produce songs with push, and that only works kinda mouse free if you adapt (force) your workflow to push. I had a blast doing so, but (especially for anything past the sketch phase) it slows me down considerably and for even moderate projects it’s easy to get lost or you need a lot of pushes/turning knobs to find your way. It’s amazing what you can do with push, but there is so much you can’t that you always need to work with the mouse/screen/keyboard in tandem anyway. I’m sorry to say it’s collecting dust at the moment despite the fact there is also excellent integration for bitwig. I now use a midi fighter twister and this does all I need from a controller (and takes a lot less desk space).

[pdxindy]

There is a misunderstanding here:
- The normal Bounce method creates a new track and bounces the selected clip on there.
- Then there is "Bounce in place" which replaces the MIDI clip with its audio version. This is handy if you e.g. have a MIDI drum groove with several copies and now want to create a break in the n-th clip. Simply bounce it in place and edit the audio, which can happen on the same track.

I don't think you read my original post. Adding a new track = adding unnecessary clutter.

In Live, you need 2 tracks to have an arpeggiator driving a synth. In Logic, I cannot use 2 midi controllers at the same time on individual tracks. Every DAW has some issue or another.

In practice, it is no big deal. One works around those things and gets on with it. Bitwig's Bounce in Place is great to use. Would it be handy to have it auto-save a hidden midi clip? Sure, but it doesn't make that much difference in terms of workflow...

[pdxindy]

(every time I work in Ableton I'm disappointed how much I need to do with the mouse)

despite Push2?

I tried to really produce songs with push, and that only works kinda mouse free if you adapt (force) your workflow to push. I had a blast doing so, but (especially for anything past the sketch phase) it slows me down considerably and for even moderate projects it’s easy to get lost or you need a lot of pushes/turning knobs to find your way. It’s amazing what you can do with push, but there is so much you can’t that you always need to work with the mouse/screen/keyboard in tandem anyway. I’m sorry to say it’s collecting dust at the moment despite the fact there is also excellent integration for bitwig. I now use a midi fighter twister and this does all I need from a controller (and takes a lot less desk space).

Yeah, my Push started collecting dust before I switched from Live to Bitwig. Similar story...

[syntonica]

There is a misunderstanding here:
- The normal Bounce method creates a new track and bounces the selected clip on there.
- Then there is "Bounce in place" which replaces the MIDI clip with its audio version. This is handy if you e.g. have a MIDI drum groove with several copies and now want to create a break in the n-th clip. Simply bounce it in place and edit the audio, which can happen on the same track.

I don't think you read my original post. Adding a new track = adding unnecessary clutter.

In Live, you need 2 tracks to have an arpeggiator driving a synth. In Logic, I cannot use 2 midi controllers at the same time on individual tracks. Every DAW has some issue or another.

In practice, it is no big deal. One works around those things and gets on with it. Bitwig's Bounce in Place is great to use. Would it be handy to have it auto-save a hidden midi clip? Sure, but it doesn't make that much difference in terms of workflow...

There's something for me to hate about all DAWs. I'm just on a quest to find the least annoying DAW.

[pdxindy]

In Live, you need 2 tracks to have an arpeggiator driving a synth. In Logic, I cannot use 2 midi controllers at the same time on individual tracks. Every DAW has some issue or another.

In practice, it is no big deal. One works around those things and gets on with it. Bitwig's Bounce in Place is great to use. Would it be handy to have it auto-save a hidden midi clip? Sure, but it doesn't make that much difference in terms of workflow...

There's something for me to hate about all DAWs. I'm just on a quest to find the least annoying DAW.

Good luck...

[THE INTRANCER]

The glaring small aliased white fonts on the black pane backgrounds. ( even at standard 1080P ). Lack of functions relating to GUI colours. No thumbnail images. No scaling functions of GUI elements. No video support features.

[syntonica]

In Live, you need 2 tracks to have an arpeggiator driving a synth. In Logic, I cannot use 2 midi controllers at the same time on individual tracks. Every DAW has some issue or another.

In practice, it is no big deal. One works around those things and gets on with it. Bitwig's Bounce in Place is great to use. Would it be handy to have it auto-save a hidden midi clip? Sure, but it doesn't make that much difference in terms of workflow...

There's something for me to hate about all DAWs. I'm just on a quest to find the least annoying DAW.

Good luck...

Thanks! It's a long and arduous journey, but fret not! I packed some cheese sandwiches and a thermos.

[pdxindy]

There's something for me to hate about all DAWs. I'm just on a quest to find the least annoying DAW.

Good luck...

Thanks! It's a long and arduous journey, but fret not! I packed some cheese sandwiches and a thermos.

I settled on Bitwig and have Logic for doing some stuff that Bitwig doesn't. My needs are fairly modest and I am not on anyones schedule so production speed is not a concern for me. I'd be fine with Studio One or Live as well.

[antic604]

Hopefully when MIDI comping gets added, Bitwig will simply send the MIDI clip to comp lane below and put audio on the top lane.

That's very smart idea and very bitwigish . I did not even dream about mixed audio/midi comping... until now

Yeah, I like it too. I even asked devs few months ago about it, but they basically avoided an answer. I'm afraid this requires a concept of 'hybrid clips' which is not something they've anticipated from the start and is probably not easy to implement now? Same with alias/linked/ghost/shared clips feature, that many have been asking for.

Let's hope they'll figure it out, or come up with even better - more Bitwig(ish) - solution

[moss]

The glaring small aliased white fonts on the black pane backgrounds. ( even at standard 1080P ). Lack of functions relating to GUI colours. No thumbnail images. No scaling functions of GUI elements. No video support features.

Regarding scaling: you can scale the whole UI up to 200% either by right clicking on the title bar or in the settings (Settings -> User Interface -> Display Profile).

[gExpectations]

I guess they want to scale GUI elements individually.

[ferez21]

Does Bitwig not have comping for MIDI? Only audio?