Bitwig Studio 1.1 life

[toby]

Can somebody confirm if dragging samples from the browser to 3rd party samplers works in 1.1?

[thetechnobear]

- No, but you can route a track directly to a VST and select a Midi Channel for it, so you can have 16 Tracks all routed to one instance of for instance Kontakt or Bazille on different Channels.
Not very elegant yet, I know, but it's a first step.

Pretty similar to Ableton then.

You would still need to use the script to create your 16 inputs.

Ouch, I thought that would have been high up on the devs list.

- No luck with poly pressure. I seem to be the only one thinking it's important...

Doh… perhaps when the Linnstrument starts shipping, the devs will start to understand that a single channel midi keyboard is not the only controller out there

any changes on the controller api front that might help?
e.g. can I send multi channel midi directly to a VST
(I'm thinking along the lines of a special controller script, say receiving via osc, then using "you can route a track directly to a VST and select a Midi Channel for it")

oh well, the wait continues….

[TristanMendoza]

Damn thanks for that picture with all the new stuff! Even more excited now

[crazyfiltertweaker]

-is it possible to record midi from a midi track to another midi track for recording midi effects?
-can I route audio into a an instrument as example to use a vocoder?

[ISP]

I don't like the icons in routing section, its overloaded for the eyes imho. It was much better and easy for the eyes with just a text.

IMO they are actually needed to make clear what the routings mean. There are so many options now that I personally am thankful for the icons, even when I know what you mean.

Cheers,

Tom

Yes i agree and one thing i've noticed that icons makes less room for text, maybe it would be better to widen channels a bit then?

[ThomasHelzle]

oh well, the wait continues….

Yeah, you know I'm with you on that
It's just not such a widespread usecase yet, so it has to take the second seat for now - it's not ignorance.
1.1 is massive as it is, there will always be something missing, and it will hurt the more the closer it is to your own heart and work

Sending Midi directly to VSTs from the SDK doesn't sound too practical?
You wouldn't be able to record it in that case?

Cheers,

Tom

[Ogopogo]

I don't like the icons in routing section, its overloaded for the eyes imho. It was much better and easy for the eyes with just a text.

IMO they are actually needed to make clear what the routings mean. There are so many options now that I personally am thankful for the icons, even when I know what you mean.

Cheers,

Tom

I agree it does look pretty busy though, so maybe if the icons were a bit smaller or simpler they'd fit in with the text better. They seem out of alignment as it is, but maybe that's stuff they were planning on getting to anyway.

[ThomasHelzle]

-is it possible to record midi from a midi track to another midi track for recording midi effects?
-can I route audio into a an instrument as example to use a vocoder?

Yes to both.

Cheers,

Tom

[Cyoon]

Audio recording latency compensation is in the options menu.

So there won`t be a per track "Track Delay" available?

[thetechnobear]

oh well, the wait continues….

Yeah, you know I'm with you on that
It's just not such a widespread usecase yet, so it has to take the second seat for now - it's not ignorance.
1.1 is massive as it is, there will always be something missing, and it will hurt the more the closer it is to your own heart and work

Sending Midi directly to VSTs from the SDK doesn't sound too practical?
You wouldn't be able to record it in that case?

Yeah, I know...
as you know I view it as an opportunity... because the likes of LPX and Live also don't support it, bitwig could get in there with leader advantage, really have something others cannot do yet. (ok, cubase can, but its a linear daw) - also whilst the poly pressure isn't there, its has got a nice model to have per key expression, something others lack... so bitwig is 'closer'.

midi -> vst, no its not ideal, as you could not record midi, but you could record the audio output.
(i do this alot, due to the lack of per key expression and also when working with OSC based instruments, so daw is acting as a host)

[ThomasHelzle]

Yeah, I know...
as you know I view it as an opportunity... because the likes of LPX and Live also don't support it, bitwig could get in there with leader advantage, really have something others cannot do yet. (ok, cubase can, but its a linear daw) - also whilst the poly pressure isn't there, its has got a nice model to have per key expression, something others lack... so bitwig is 'closer'.

midi -> vst, no its not ideal, as you could not record midi, but you could record the audio output.
(i do this alot, due to the lack of per key expression and also when working with OSC based instruments, so daw is acting as a host)

Again, I agree. I personally would jump on that opportunity right away.
But then you would have to not-implement something else...
Not my decision to make anyway.

I'll keep my ear on the floor on this, but I don't want to create false hope for a quick solution...

Cheers,

Tom

[Redukt]

Will the effect tracks in 1.1 have the possibilty to send to another effect track like in Ableton? Like sending a delay track to a reverb one?

[ISP]

Guys! This is the place for "Deactivate" button - the Bitwig way! It can be anywhere but it should be separated from Name and Color section. Please listen, don't clutter the layout of the inspector. Bitwig Studio UI is one of the best, please keep it organized

[throst]

like this one

[u-u-u]

Will the effect tracks in 1.1 have the possibilty to send to another effect track like in Ableton? Like sending a delay track to a reverb one?

And into itself for some feedback?!