Should Bitwig take Ableton 11 as an example?

[pdxindy]

for me I want more sequencing type modules in the grid (including a CV/GATE -> MIDI OUT for sequencing other plugins without an audio to midi hack) and comping as my main wishlist.

Maybe either some improvements to the arpeggiator or a straight up "sequencer" midi effect modelled on the RYK-M185 with ratcheting and stuff per step.

A few more filter models wouldn't hurt either (maybe alongside a more dirt focused analog emulation instrument that can be converted into a grid like polymer?)

What would you like to see as far as Arpeggiator improvements?

Here is one instance of Polysynth using 2 Arps and 2 held notes.

https://dandelionaudio.com/sound/Polys-Arp-4.mp3

[pdxindy]

It would be useful to have a sequencer device... in the meanwhile, just about anything can be done with the arp since every parameter can be modulated. Here is another example of a 4 bar pattern

https://dandelionaudio.com/sound/Polys-Arp-5.mp3

[lokanchung]

Yes, that's why 11 is such a big thing. I too am using Live now more than Bitwig, before 11 that was the opposite.

Oh, and I forgot the better multi-track MIDI editing, that's now better than Bitwigs solution.

I thought we were talking about whether Live's main concern is live performance or not.

Anyway, it's true Live 11 is good update. I might switch back to live if they keep pushing out updates like this. I just don't want to pay upgrade fee yet. When they finally improve UI performance and stability, most Live users will be happy and will never consider a switch.
Bitwig don't have much time.

[nsq]

Until such idiotic bugs are eliminated, Bitwig should take any DAW as an example.

[pdxindy]

Until such idiotic bugs are eliminated, Bitwig should take any DAW as an example.

hmmm... works as expected here

I'm on OSX and Bitwig 3.3.1 beta 1

[ReleaseCandidate]

Until such idiotic bugs are eliminated, Bitwig should take any DAW as an example.

hmmm... works as expected here

I'm on OSX and Bitwig 3.3.1 beta 1

Same error here with 3.3, 3.3.1 B1 and Windows. Has been like that before (3.2) too, I remember that copy and paste always felt weird, but couldn't really figure out why.

[carlca]

Until such idiotic bugs are eliminated, Bitwig should take any DAW as an example.

hmmm... works as expected here

I'm on OSX and Bitwig 3.3.1 beta 1

Same error here with 3.3, 3.3.1 B1 and Windows. Has been like that before (3.2) too, I remember that copy and paste always felt weird, but couldn't really figure out why.

Works as expected for me on macOS and BWS 3.3.1b1 as well. The only possible point of confusion I can see is that when you do the right click to paste, the clipboard buttons are at the bottom of the dialog.

Copy...

Screenshot 2020-12-12 at 15.33.52.png

Paste...

Screenshot 2020-12-12 at 15.34.18.png

Of course you can always use Cmd/Ctrl C and Cmd/Ctrl/V

[carlca]

Until such idiotic bugs are eliminated, Bitwig should take any DAW as an example.

Are you referring to the paste operation happening in the wrong place? I've just had a closer look at your video but I cannot replicate the problem. Have you informed Bitwig?

[ReleaseCandidate]

Until such idiotic bugs are eliminated, Bitwig should take any DAW as an example.

Are you referring to the paste operation happening in the wrong place? I've just had a closer look at your video but I cannot replicate the problem.

Bitwig always(?) aligns to the 'first' selected note (top if selecting from above, the bottom one when selecting from below), not taking the distance to the start of the selection.
Which, I guess, is no bug, but a very unlucky design decision.

bitwig_copy_notes.gif

[pdxindy]

Until such idiotic bugs are eliminated, Bitwig should take any DAW as an example.

Are you referring to the paste operation happening in the wrong place? I've just had a closer look at your video but I cannot replicate the problem.

Bitwig always(?) aligns to the 'first' selected note (top if selecting from above, the bottom one when selecting from below), not taking the distance to the next beat/bar/...
Which, I guess, is no bug, but a very unlucky design decision.
bitwig_copy_notes.gif

Not on OSX... from either top or bottom it aligns as expected

[pdxindy]

Another example using the Arp to make complex patterns. Basic Polysynth sound

https://dandelionaudio.com/sound/Polys-Arp-7.mp3

[nsq]

I used the right click just to show what I was doing. I think this bug was already in v1.0. Notes are sometimes pasted correctly and usually in a random position. I have no idea what it depends on. I reported it at least once, a long time ago.
Another long-standing serious bug was incorrect handling of raw audio clips when there are tempo changes in the song - they finally fixed it in v3.3.

Bitwig always(?) aligns to the 'first' selected note (top if selecting from above, the bottom one when selecting from below), not taking the distance to the start of the selection.
Which, I guess, is no bug, but a very unlucky design decision.
bitwig_copy_notes.gif

If this is a design decision, it's either very wrong, or I'm too stupid to use Bitwig because I didn't think of it. While I have no problems pasting notes in other programs.

[pdxindy]

It's a Windows only issue. OSX works as expected. So if it is a design decision, then OSX has the bug... so either way it is a bug and should be reported as such

[Vladislav_Gronk]

Yes, they should focus more on production related stuff instead of adding even more sound design bloat. There's a reason 97% of Bitwig's users never release anything substantial and only tinker around making obscure sounds.

[nsq]

It's a Windows only issue. OSX works as expected. So if it is a design decision, then OSX has the bug... so either way it is a bug and should be reported as such

It's also Linux issue - I just checked.