Bitwig Studio 4 announced (+beta available)!

[Trancit]

I think this is the first time I've seen "Producer" editing in the piano roll portrayed as superior to being able to play an instrument. In DP forums I see a lot of the opposite, so it's interesting to see that's all.

I thought it´s time to bring that into the game

[Benutzername]

I really like what I see in the announcements and I'll definitely check it out before my subscriptions runs out in a few weeks.

Too bad that I've paid for a full year and hardly got anything in return this time. Bitwig should have split the different features into smaller versions and distributed them evenly across the year as promised ("machine gun updates"). Doing it the old school way by delivering everything in one large and feature packed version every 18 months and almost nothing in between is a huge slap in the face of everybody who was dumb enough to buy an update plan between the releases.

[Benutzername]

double post

[SLiC]

I really like what I see in the announcements and I'll definitely check it out before my subscriptions runs out in a few weeks.

Too bad that I've paid for a full year and hardly got anything in return this time. Bitwig should have split the different features into smaller versions and distributed them evenly across the year as promised ("machine gun updates"). Doing it the old school way by delivering everything in one large and feature packed version every 18 months and almost nothing in between is a huge slap in the face of everybody who was dumb enough to buy an update plan between the releases.

I agree with you about little and often, although I suspect moist people (myself included) just consider we are buying 'an upgrade' like any other DAW when there is something we need/want and then take the free year as a bonus. That said, I don't think I lasted more than 6 months without an active plan, they always put something out I want! This has been by far the longest run without anything new....but I paid for V3.3 to get Polymer etc back in November 2020 and will get V4 free in 2021....cant complain!

[PieBerger]

I suspect moist people

As should we all

[pdxindy]

Doing it the old school way by delivering everything in one large and feature packed version every 18 months and almost nothing in between is a huge slap in the face of everybody who was dumb enough to buy an update plan between the releases.

That is quite an exaggeration... if V4 is released at the end of June, it will have been 7 months since 3.3 which will have been the longest period between updates since they adopted the current pricing method.

[apoclypse]

There is a difference between clutter and organised chaos.

Tell me there's any information at all to glean from that Reaktor thumbnail? I'm flatly not going to believe you if you say it's worth the .. clutter!

As a former hardcore Logic user and custom icon fan, I immediately realized the mistake of full screenshot thumbnails, and again, it's weird that Prosonus did not. They had Logic around to learn from and flatly learned nothing.

I think you are conflating two different things. Logic's custom icons are only for track headers. Studio One doesn't even have custom icons for track headers, the conversation is about the plugin browser.

Ofcourse for track headers icons are going to be simpler because it doesn't make sense to have a plugin screenshot there. For a plugin browser having an accurate representation of what the plugins are can be helpful, especially if you don't always recall what the name of the plugins are. Sure an icon of the plugin would work way better than just a screenshot for sure, but that's not something Logic "figured out". You have to literally go find/download the icons and add them into Logic and Logic doesn't automatically assign these track header icons depending on what plugin you have loaded you have to do that manually. As far as I can tell that's not what's being asked for here.

That being said I don't agree that Bitwig needs it due to how powerful the search and categorization features are.

[antic604]

Ofcourse for track headers icons are going to be simpler because it doesn't make sense to have a plugin screenshot there.

Why not?! This is actually one of things that's great about Reason's sequencer! I can quickly see where my bass is, where my pads are and where my acid lines are. With a generic "synth" icon I wouldn't be able to tell as easily.

[jonljacobi]

Images work great in small sets. I use color coding so I don't need them. There are a whole lot of things I'd like to see fixed in Bitwig before they start in with the images.

[antic604]

Images work great in small sets. I use color coding so I don't need them. There are a whole lot of things I'd like to see fixed in Bitwig before they start in with the images.

Definitely. I'm against track icons & browser thumbnails (maybe in Bitwig v10 when we have everything else already ).

Just saying that if they're there, they can be helpful.

[machinesworking]

There is a difference between clutter and organised chaos.

Tell me there's any information at all to glean from that Reaktor thumbnail? I'm flatly not going to believe you if you say it's worth the .. clutter!

As a former hardcore Logic user and custom icon fan, I immediately realized the mistake of full screenshot thumbnails, and again, it's weird that Prosonus did not. They had Logic around to learn from and flatly learned nothing.

I think you are conflating two different things. Logic's custom icons are only for track headers. Studio One doesn't even have custom icons for track headers, the conversation is about the plugin browser.

Ofcourse for track headers icons are going to be simpler because it doesn't make sense to have a plugin screenshot there. For a plugin browser having an accurate representation of what the plugins are can be helpful, especially if you don't always recall what the name of the plugins are. Sure an icon of the plugin would work way better than just a screenshot for sure, but that's not something Logic "figured out". You have to literally go find/download the icons and add them into Logic and Logic doesn't automatically assign these track header icons depending on what plugin you have loaded you have to do that manually. As far as I can tell that's not what's being asked for here.

That being said I don't agree that Bitwig needs it due to how powerful the search and categorization features are.

I get that it's tracks VS browser, wasn't confused by that. We, the end users figured out that custom icons work better than screenshots of the entire plug in, that's what I was getting at, that they had Logics track icons as an example of how to implement this. So yeah, not the Logic teams examples, but all the user created examples.

Anyway it's getting frankly annoying how much this thread has become about a single feature request. Seems like every announcement of an upgrade gets bogged down with this on every forum everywhere.

[pdxindy]

Anyway it's getting frankly annoying how much this thread has become about a single feature request. Seems like every announcement of an upgrade gets bogged down with this on every forum everywhere.

Yeah... any attempt to talk about the actual update is swamped by feature requests for stuff that isn't there.

I am listening to a very simple patch as I type. 1 very short midi clip (16th note long) with 1 note. Using the new pitch spread function, the midi note pitch is randomized across 2 octaves. That is going to a Grid patch with a pitch quantizer set to a scale. The velocity is also randomized and a bit of chance on whether the note is triggered.

[machinesworking]

I am listening to a very simple patch as I type. 1 very short midi clip (16th note long) with 1 note. Using the new pitch spread function, the midi note pitch is randomized across 2 octaves. That is going to a Grid patch with a pitch quantizer set to a scale. The velocity is also randomized and a bit of chance on whether the note is triggered.

So you're getting randomly generated in key note runs out of it, nice!
Why does it feel like they just barely couldn't add MIDI to the Grid? At least that's what I hope.

[pdxindy]

I am listening to a very simple patch as I type. 1 very short midi clip (16th note long) with 1 note. Using the new pitch spread function, the midi note pitch is randomized across 2 octaves. That is going to a Grid patch with a pitch quantizer set to a scale. The velocity is also randomized and a bit of chance on whether the note is triggered.

So you're getting randomly generated in key note runs out of it, nice!
Why does it feel like they just barely couldn't add MIDI to the Grid? At least that's what I hope.

https://dandelionaudio.com/sound/only-one-note.mp3

Here's the example with a simple quick sound... 1 midi note, no arpeggiator/sequencer

Needs the Diatonic Transposer to also work as a quantizer, which it currently doesn't (could be a bug?). I sent in a request. Right now it has to go into the Grid to use the pitch quantizer.

I so want Midi Out on the Grid... and well implemented!

[apoclypse]

Ofcourse for track headers icons are going to be simpler because it doesn't make sense to have a plugin screenshot there.

Why not?! This is actually one of things that's great about Reason's sequencer! I can quickly see where my bass is, where my pads are and where my acid lines are. With a generic "synth" icon I wouldn't be able to tell as easily.

You could just name the track properly. I organize my tracks by color. All bass is red, all my vocals are yellow, fx are purple, synths are green. I know exactly where everything is based on that.

I also think it's depends on what the developers think is important. Reason value Skeuomorphism quite a bit, it's that concept taken to the ultimate level. The way Reason works you can't just click on a track on open the plugin window. You have to open the rack view. That's why the actual track name is tiny in comparison. Having some kind of representation of what's happening is necessary in Reason. Not so much in Logic, Bitwig, S1, Ableton. VST follows track selection or inspectors make it super easy and fast to open a plugin in another DAW. I find that to be more difficult or not as fluid in Reason.

Even so when you drag in a VST instrument you don't get a screenshot of it in the track header. You only get that with RE, and built in devices. The only thing you see in the track header is the plugin container.