Bitwig 6

[ere2learn]

Gettting clips starting on 1.2 for some reason in beta 2, can't reproduce confidently, anyone else come across it?

[pdxindy]

Gettting clips starting on 1.2 for some reason in beta 2, can't reproduce confidently, anyone else come across it?

Had the same... not sure the cause.

[bboxdw]

The latest Bitwig update is amazing. Wow!

Alongside sending them praises, I also sent the below future feature request inspired by some of the new updates. Sharing here in case anyone else is thinking along same lines and wants to request it as well. As I recently mentioned in the groove pool discussion thread, the alternative in the last paragraph (ability to mathematically manipulate one curve or automation segment with another) could also be used to apply a "groove curve" to existing automation clips and curves. These updates really lay the foundation for a lot of possibilities!


In a future update, I'd also love to see a "tilt" style automation editing feature in the time selection tool, similar to what Cubase has in its range selection tool. "Tilt" allows moving/scaling automation segments by dragging a corner of the selection up or down. This proportionally moves automation at one end of the segment more than the other end, bending the segment toward it. This is helpful for shaping dynamics, energy shifts, and fades quickly.

This feature could also be useful in the curves/segments editor.

Another way this could be implemented, with even more flexibility, is to have a function where an automation segment or curve can be mathematically transformed by an existing curve in the curve library. (In this case, the user would select "multiply" and choose an existing ramp-shaped curve.)

[slackhead]

In a future update, I'd also love to see a "tilt" style automation editing feature in the time selection tool, similar to what Cubase has in its range selection tool. "Tilt" allows moving/scaling automation segments by dragging a corner of the selection up or down. This proportionally moves automation at one end of the segment more than the other end, bending the segment toward it. This is helpful for shaping dynamics, energy shifts, and fades quickly.

If I am following you right, this has already been implemented.

Watch from 14:00

[stamp]

The latest Bitwig update is amazing. Wow!

Alongside sending them praises, I also sent the below future feature request inspired by some of the new updates. Sharing here in case anyone else is thinking along same lines and wants to request it as well. As I recently mentioned in the groove pool discussion thread, the alternative in the last paragraph (ability to mathematically manipulate one curve or automation segment with another) could also be used to apply a "groove curve" to existing automation clips and curves. These updates really lay the foundation for a lot of possibilities!


In a future update, I'd also love to see a "tilt" style automation editing feature in the time selection tool, similar to what Cubase has in its range selection tool. "Tilt" allows moving/scaling automation segments by dragging a corner of the selection up or down. This proportionally moves automation at one end of the segment more than the other end, bending the segment toward it. This is helpful for shaping dynamics, energy shifts, and fades quickly.

This feature could also be useful in the curves/segments editor.

Another way this could be implemented, with even more flexibility, is to have a function where an automation segment or curve can be mathematically transformed by an existing curve in the curve library. (In this case, the user would select "multiply" and choose an existing ramp-shaped curve.)

You can allready tilt a time selected section of automation. It's part of 6.

The trasformation of autoamtion you are talking about can allready be done vai modulators and macros.

[kultschar]

Not sure if this is a bug on Version 6 Beta 2 or me (reported anyhow). If I record a MIDI clip with Post Record Action as "play it automatically" it Loops continuously automatically after recording. However with an Audio Clip it only loops once and stops

[bboxdw]

If I am following you right, this has already been implemented.

You can allready tilt a time selected section of automation. It's part of 6.

Interesting. Thanks for this info. Such a long and impressive list of updates, I may have missed this. Looks like I need to take a closer look this evening!

[slackhead]

Interesting. Thanks for this info. Such a long and impressive list of updates, I may have missed this. Looks like I need to take a closer look this evening!

I added a link to my previous reply to the Polarity video that demonstrates this (if rather briefly).

[bboxdw]

I added a link to my previous reply to the Polarity video that demonstrates this (if rather briefly).

Very helpful. Thanks! The closest thing I could find in the release notes was "shear start/end of time range," but Polarity's video shows exactly the type of tilt behavior that I was thinking of.

[chaocrator]

i love new scale feature — but the selection of available scales is not great for now.
in particular, both of my favorite scales are not available. (luckily, there is a workaround since these two are modes of harmonic minor.)
hope they'll expand the list (it's now 23 vs for instance 35 in Ableton)

[dhemery]

in particular, both of my favorite scales are not available. (luckily, there is a workaround since these two are modes of harmonic minor.)

If you're correcting foreign notes via a device or an editor action, the correction corrects a bit differently for each mode of a scale, even though the notes are the same. This may or may not matter for your specific uses.

[DazzW]

Am I missing something or is there no way to map "stop all clips" to the keyboard or a controller in Bitwig 6?

[chaocrator]

If you're correcting foreign notes via a device or an editor action, the correction corrects a bit differently for each mode of a scale, even though the notes are the same. This may or may not matter for your specific uses.

yeah, i already noticed that, that's why i would love a proper implementation for Phrygian Dominant and Dorian #4 a.k.a. Ukrainian Dorian a.k.a. Romanian Minor.

[_leras]

If you're correcting foreign notes via a device or an editor action, the correction corrects a bit differently for each mode of a scale, even though the notes are the same. This may or may not matter for your specific uses.

yeah, i already noticed that, that's why i would love a proper implementation for Phrygian Dominant and Dorian #4 a.k.a. Ukrainian Dorian a.k.a. Romanian Minor.

Pls send Bitwig an email about this. They should be able to add more scales.

And how are they going to do melodic minor?

[dhemery]

And how are they going to do melodic minor?

I guess they'll leave it up to you to switch between ascending and descending as needed.