3.2 (Beta 1) is OUT!!!

[sagetone]

I am missing something on the Drum Machine returns. How is it used, and how is it different than the DM FX bin?

If it works like I expect it to (unfortunately I can't try it, plan expired) you can run multiple effects in parallel right from Drum Machine and save them with the Drum Machine as a preset. I make these really specific drum kits so it's really useful to have this set up where I can easily move the Drum Machine around with it's built in parallel effects to any project.

Edit: What I can’t tell from the picture antic posted is if there’s a send amount for each pad/sound and a way to rout what gets sent where or if it’s only a return for the whole Drum Machine only which would be meh, kinda disappointing and limited. Could someone check and confirm?

@JHernandez, I just checked and I can't find a "send" for the individual pads. That's why I don't understand this new feature, and why it's any different than the FX bin.

[pdxindy]

I am missing something on the Drum Machine returns. How is it used, and how is it different than the DM FX bin?

If it works like I expect it to (unfortunately I can't try it, plan expired) you can run multiple effects in parallel right from Drum Machine and save them with the Drum Machine as a preset. I make these really specific drum kits so it's really useful to have this set up where I can easily move the Drum Machine around with it's built in parallel effects to any project.

Edit: What I can’t tell from the picture antic posted is if there’s a send amount for each pad/sound and a way to rout what gets sent where or if it’s only a return for the whole Drum Machine only which would be meh, kinda disappointing and limited. Could someone check and confirm?

@JHernandez, I just checked and I can't find a "send" for the individual pads. That's why I don't understand this new feature, and why it's any different than the FX bin.

Add a return to the Drum Machine, then you will see the new send show up

[sagetone]

I am missing something on the Drum Machine returns. How is it used, and how is it different than the DM FX bin?

If it works like I expect it to (unfortunately I can't try it, plan expired) you can run multiple effects in parallel right from Drum Machine and save them with the Drum Machine as a preset. I make these really specific drum kits so it's really useful to have this set up where I can easily move the Drum Machine around with it's built in parallel effects to any project.

Edit: What I can’t tell from the picture antic posted is if there’s a send amount for each pad/sound and a way to rout what gets sent where or if it’s only a return for the whole Drum Machine only which would be meh, kinda disappointing and limited. Could someone check and confirm?

@JHernandez, I just checked and I can't find a "send" for the individual pads. That's why I don't understand this new feature, and why it's any different than the FX bin.

Add a return to the Drum Machine, then you will see the new send show up

Thanks @pdxindy! Duh, I knew it had to be easy. Finally looked for the send over in the inspector. Voila!

[pdxindy]

[JHernandez]

I am missing something on the Drum Machine returns. How is it used, and how is it different than the DM FX bin?

If it works like I expect it to (unfortunately I can't try it, plan expired) you can run multiple effects in parallel right from Drum Machine and save them with the Drum Machine as a preset. I make these really specific drum kits so it's really useful to have this set up where I can easily move the Drum Machine around with it's built in parallel effects to any project.

Edit: What I can’t tell from the picture antic posted is if there’s a send amount for each pad/sound and a way to rout what gets sent where or if it’s only a return for the whole Drum Machine only which would be meh, kinda disappointing and limited. Could someone check and confirm?

@JHernandez, I just checked and I can't find a "send" for the individual pads. That's why I don't understand this new feature, and why it's any different than the FX bin.

Add a return to the Drum Machine, then you will see the new send show up

Thanks @pdxindy! Duh, I knew it had to be easy. Finally looked for the send over in the inspector. Voila!

Nice! I hope it’s as flexible as I imagine. Thanks.

[Randall P. McMurphy]

Downloaded it. So far so good with the Saturator. But in my opinion it should end the same way as the Amp device, with a wet fx box, output gain, and mix control.

Even with the normalize function I find I still need to adjust output gain sometimes, and I'd rather have it implemented in the device as opposed to always grouping the Saturator in with a Tool.

Nice GUI on that one though! Would love to see Ladder get a facelift / rework. . .

[Randall P. McMurphy]

As for the colour coding - I'm mostly ambivalent, its not something I really see myself using. I will say that I think a bit more attention should be paid to contrast / brightness as well as colour itself. Its really disorienting when you sweep a filter knob and it goes from dark red to bright yellow at 260hz but then hits another dark at 5.4 hz then absolute lightest at 19.9. I think the colour contrast should be more of a direct transition from dark to light.

[antic604]

Maybe 3.3 will be for you!

Seeing how things have been for the last couple of versions I really doubt it. They've lost it.

[antic604]

And to think I've upgrade plans paid up to end of 2021 AND I've just sold Live 10 Suite...

Are you kidding?

No. But I already found another copy of Suite and lost ~5EUR on the whole back & forth deal.

[antic604]

I hate the rainbow-y colours everywhere -

I love it personally, UVI does a similar thing for some of their plugins. Makes it look magical

Well, they make me puke...

[antic604]

doom and gloom



And to think I've upgrade plans paid up to end of 2021 AND I've just sold Live 10 Suite...

Brah, it's a beta. Chillax.

I know. Bugs are expected. But I'm starting to hate where they're going (3rd EQ, instead of adding those things to perfectly capable EQ-5?! We have now FOUR EQs. That's gotta be a record). Instead of fixing existing issues - often simple things - they're adding more clutter...

[Randall P. McMurphy]

But I'm starting to hate where they're going (3rd EQ, instead of adding those things to perfectly capable EQ-5?! We have now FOUR EQs. That's gotta be a record).

To a certain extent I agree with this. It would be more efficient if the EQ-5 device would just completely lose bands in the GUI when you deactivate them (and the GUI shrinks accordingly). So EQ-2 is no longer needed, if you want that functionality just activate only two bands.

The new EQ is a different beast because of oversampling & adaptive-q. Although I suppose you could just have an 'off setting' for oversampling and have it perform the same as the EQ-5?

Finally the DJ eq is absolutely distinct and serves its own purpose with its own GUI, I wouldn't want to incorporate that one into another.

I was always a bit confused why they left FM-4 in the program after introducing Phase 4. It seems you can do everything in Phase 4 and FM-4 is just totally redundant (and a difficult to use GUI because of the way assigning modulation amounts works, way too much dragging). Correct me if I'm wrong here.

[bronswerk]

Maybe it's just too dangerous to rework an excisting device extensively because of backward compability?

[antic604]

I was always a bit confused why they left FM-4 in the program after introducing Phase 4. It seems you can do everything in Phase 4 and FM-4 is just totally redundant (and a difficult to use GUI because of the way assigning modulation amounts works, way too much dragging). Correct me if I'm wrong here.

I'm completely opposite. Phase-4 is confusing, with all those options on top of every oscillator where instead of drop-down menus you cycle blindly through shapes, etc. And it's very CPU heavy, without sounding better than FM-4 to my ears. I agree the mod matrix in FM-4 isn't the greatest, but I like how they changed the colors - was it around 2.5? - to make operators stand out both in the GUI and in the detached window. I wonder why Polysynth didn't get that treatment...

FM-4 is actually my favourite instrument in Bitwig

[antic604]

Maybe it's just too dangerous to rework an excisting device extensively because of backward compability?

They can have legacy devices "hidden" from the Browser but available to use for older projects, with an "update" button if someone wants to switch to new one, at the risk of it sounding different. They already have this mechanism for modulators (I noticed this in 3.1, where I could "update" some modulators in my old products with new versions incl. extended sync options).