Bitwig 6

[tumface]

@tumface @pdxindy thanks so much. For the velocity issue, yes it was in drum mode. Where should I be reading to keep informed about things like the bugs Bitwig have accepted?

Unfortunately, they don't share such things publicly. Every user must report every single bug they find from scratch using Bitwig's beta email address, because Bitwig doesn't share a list and so there's no way to know if they've already received the bug, or if they've received it but think it's not a priority because only a single user reported it.

This creates a lot of wasted work for their users, and especially must create a ridiculous amount of manual work for their support team, but oh well

I've submitted about 15 bugs or misbehaviors so far, with videos for how to reproduce them in each one.

[pdxindy]

@tumface @pdxindy thanks so much. For the velocity issue, yes it was in drum mode. Where should I be reading to keep informed about things like the bugs Bitwig have accepted?

The Bitwig Discord is active and lots of user interaction for tracking bugs.

[tumface]

The Bitwig Discord is active and lots of user interaction for tracking bugs.

Heh. I joined and checked, and they have *none* of the bugs (actual bugs, not gripes) I've reported in their tracker thing.

[pdxindy]

The Bitwig Discord is active and lots of user interaction for tracking bugs.

Heh. I joined and checked, and they have *none* of the bugs (actual bugs, not gripes) I've reported in their tracker thing.

Well... get posting over there!!

[tumface]

Well... get posting over there!!

From a game theory perspective, it's better if I don't, so that other people are more likely to also report the bug, instead of being complacent.

[tumface]

Now that alias clips exist, couldn't they get rid of resize-based clip looping? I mean, the user interaction could be kept the same, but instead of looping the single clip and struggling to visualise loop boundaries, they could just draw new alias clips instead.

The Recurrence feature (aka nth, modulo) relies on looping.

BitwigStudioApp_kJnuq09YaR.png

[Dionysos]

I'd argue that playing the same alias clip in a row should work exactly the same way as a looped clip and if that's not the case, it could be considered a bug.

(But tbh I don't feel strongly about this at all. I bet there are people who love resize-based clip looping, and it'd be a bit silly to remove the feature just because there's a different way to do the same thing.)

[tumface]

I'd argue that playing the same alias clip in a row should work exactly the same way as a looped clip and if that's not the case, it could be considered a bug.

Then there's no way to gaplessly reset the recurrence counter without creating a redundant non-aliased copy of the clip.

Also means your arrangement could sound different if you moved two sections to be adjacent to each other, only from having aliased clips starting to touch.

[stamp]

Now that alias clips exist, couldn't they get rid of resize-based clip looping? I mean, the user interaction could be kept the same, but instead of looping the single clip and struggling to visualise loop boundaries, they could just draw new alias clips instead.

Personally I see hardly any benefit for alias clips in my workflow. I mean if I want a 1 bar clip to extend for 8 bars extending it the ''old'' way is just faster. Do you really prefer having to duplicate it 7 times or doubling content 3 times? It could be useful if you want to copy a variation to another spot in your track knowing that you would change it the future. And if later I want to make it unique I have to unalias it. I mean if I want the same clip in another spot I just copy paste.
Another negative imo is that you have to keep track of what is aliased and if you mess up you will have a clip somewhere that is changing without you even knowing and maybe the old version of that clip was just better in that context.
I don't know. It's just one more opportunity for your brain to switch in a more technical and less creative state and we all know how hard sometimes it is to get in that creative state and how easy it is to get lost in technicalities.
I'm still happy for people who wanted this feature. The more happy people the merrier.

[gulugulufish]

@tumface @pdxindy thanks so much. For the velocity issue, yes it was in drum mode. Where should I be reading to keep informed about things like the bugs Bitwig have accepted?

Unfortunately, they don't share such things publicly. Every user must report every single bug they find from scratch using Bitwig's beta email address, because Bitwig doesn't share a list and so there's no way to know if they've already received the bug, or if they've received it but think it's not a priority because only a single user reported it.

This creates a lot of wasted work for their users, and especially must create a ridiculous amount of manual work for their support team, but oh well

I've submitted about 15 bugs or misbehaviors so far, with videos for how to reproduce them in each one.

My strategy is to wait until beta 2 and see if they've noticed/fixed the things i care about. If not then I'll send more in. So far I've only just sent in crash reports as those seem like they should be prioritized. I assume they have, 1000 or more requests from people and I don't wanna overwhelm. The community is super nitpicky.

[gulugulufish]

a
Personally I see hardly any benefit for alias clips in my workflow. I mean if I want a 1 bar clip to extend for 8 bars extending it the ''old'' way is just faster. Do you really prefer having to duplicate it 7 times or doubling content 3 times? It could be useful if you want to copy a variation to another spot in your track knowing that you would change it the future. And if later I want to make it unique I have to unalias it. I mean if I want the same clip in another spot I just copy paste.
Another negative imo is that you have to keep track of what is aliased and if you mess up you will have a clip somewhere that is changing without you even knowing and maybe the old version of that clip was just better in that context.
I don't know. It's just one more opportunity for your brain to switch in a more technical and less creative state and we all know how hard sometimes it is to get in that creative state and how easy it is to get lost in technicalities.
I'm still happy for people who wanted this feature. The more happy people the merrier.

I get it, I didn't think I would want to use them either, but I've discovered it's super handy for refactoring projects without having to go back and copy things. Namely because it can automatically detect duplicates and turn them into aliases which means I can use the feature only when I need to do a mass update of something I've decided to change.

[stamp]

I get it, I didn't think I would want to use them either, but I've discovered it's super handy for refactoring projects without having to go back and copy things. Namely because it can automatically detect duplicates and turn them into aliases which means I can use the feature only when I need to do a mass update of something I've decided to change.

Mmmh.. that's a good use for alias clips. Thanks for showing me another perspective.

[pdxindy]

I get it, I didn't think I would want to use them either, but I've discovered it's super handy for refactoring projects without having to go back and copy things. Namely because it can automatically detect duplicates and turn them into aliases which means I can use the feature only when I need to do a mass update of something I've decided to change.

Mmmh.. that's a good use for alias clips. Thanks for showing me another perspective.

Another use someone else mentioned, is when they have a bunch of copies of the same audio clip in Arrange, they can use the Merge Duplicates command which turns all copies of that clip into aliases, then the can replace the audio event and all the clips update. A fast way to replace a bunch of iterations of the same sample.

[pdxindy]

Personally I see hardly any benefit for alias clips in my workflow. I mean if I want a 1 bar clip to extend for 8 bars extending it the ''old'' way is just faster. Do you really prefer having to duplicate it 7 times or doubling content 3 times?

Couple nice things I found when using Alias clips for this is that each alias can be trimmed independently. So I can make 8 aliases of a 1 bar clip and I can, for example, trim off the last 2 notes of the 2nd and 6th clip to add some variation, a bit of space.

Also, each alias can have its own loop boundaries. So of those 8 clip aliases, I could have clips 1 and 4 loop at the first 2 measures, repeating the first half of the clip.

And at any time I can still edit the underlying clip and they all update.

None of those variations are possible just dragging loops of a 1 bar clip out to 8 bars.

[Echoes in the Attic]

I'm really glad to see that Bitwig turned it's attention to midi editing and core daw features, as opposed to a bunch of new devices again. Unfortunately it's not quite enough to pull me back from Ableton Live yet (though I still have a Bitwig 5 license). I used to prefer Abletons clip envelopes but now I get the feeling I might like Bitwigs clip automation more. however the thing that still keep me with Abelton is the performance pack and the ability to set and recall global parameter snapshots. It's just too handy of a feature for live playing, can't really do without it now. Similar feature would fit Bitwig really well, really hope that do something like that.