Bitwig

dom@bitwig · Post by **dom@bitwig** » Fri Oct 17, 2014 3:46 pm

Yes, the audio receiver features a mix knob.
For routing multiple midi tracks into one, i would just use the new output routing in the mixer section instead of multiple note receivers.
And yes, you can modify the midi channel if you route the output of a midi track to another track's VST instrument.

spinlud · Post by **spinlud** » Fri Oct 17, 2014 4:14 pm

dom@bitwig wrote:
spinlud wrote:I don't remember if this was asked before..

when solo a track with a send amount to an effect track (a reverb for example)...you can ear also the audio signal of other tracks that are sending audio to the same effect track. Is this fixed in 1.1? It's super-ultra-mega annoying.-.
Positive, sir!
Already in 1.1beta 4, but there was a little bug that we just fixed in beta 5.

irtimid · Post by **irtimid** » Fri Oct 17, 2014 4:54 pm

shadiradio · Post by **shadiradio** » Fri Oct 17, 2014 9:28 pm

dom@bitwig wrote:For routing multiple midi tracks into one, i would just use the new output routing in the mixer section instead of multiple note receivers.

Oh that's fantastic! I didn't realize that was part of the new track routing options. Excellent!

I also heard from support that in 1.1 you can now map macro knobs and modulators to control buttons on/off states, not just numeric input fields. I wonder what other little nice things are in this update.

crazyfiltertweaker · Post by **crazyfiltertweaker** » Sat Oct 18, 2014 9:38 am

when can I update full without beta?

I really need all these new features for my actual projects especially the fixes which I think are as helpful as the other ones!

But please someone can answer: is a drag&drop importing&exporting of midi&audio with Browser and Bitwig now possible?
And can I rename containers now to see fast the function of a fx chain?

And using the multiband FX and fx chain causes a toooo huge latency with transient sounds, is this fixed?
And is the saving bug with UAD Plugins descripted often, also fixed?
And you can assign parameter ranges which dont exist(beyond this orange area), so is this also fixed?

Thanks for answers!

crazyfiltertweaker · Post by **crazyfiltertweaker** » Sat Oct 18, 2014 9:39 am

dom@bitwig wrote:For routing multiple midi tracks into one, i would just use the new output routing in the mixer section instead of multiple note receivers.

but you cannot use it for another destination so the note receivers let me SPLIT the MIDI for parallel routing.

throst · Post by **throst** » Sat Oct 18, 2014 11:04 am

+1 for renaming container headers

xbitz · Post by **xbitz** » Sat Oct 18, 2014 11:52 am

crazyfiltertweaker wrote:
dom@bitwig wrote:For routing multiple midi tracks into one, i would just use the new output routing in the mixer section instead of multiple note receivers.
but you cannot use it for another destination so the note receivers let me SPLIT the MIDI for parallel routing.

except if a track source (MIDI from) can be an other track (or a device in a track) as is in AL

midi_routing.png

crazyfiltertweaker · Post by **crazyfiltertweaker** » Sat Oct 18, 2014 12:13 pm

I dont understand....
this is ableton, not Bitwig.
But do you mean that now midi is not just from devices outside and also from other tracks like it is shown on the picture?

One more:
If you have an audio clip on a audio or midi track which I use as bus for other tracks, it would be nice if other tracks mix with the audio from the bus and that I dont hear just the bvus audio clip.

Dunder · Post by **Dunder** » Sat Oct 18, 2014 12:41 pm

xbitz wrote:
crazyfiltertweaker wrote:
dom@bitwig wrote:For routing multiple midi tracks into one, i would just use the new output routing in the mixer section instead of multiple note receivers.
but you cannot use it for another destination so the note receivers let me SPLIT the MIDI for parallel routing.
except if a track source (MIDI from) can be an other track (or a device in a track) as is in AL

midi_routing.png

I really hope that they DONT solve it in that crappy ableton way. Instead I hope they take the reaper route (he he), that as soon as you select a "midi to" destination, a new drop down box appears under your first. In this way you can send many tracks to many other tracks, instead of just being able to send one track to many or many tracks to one as you are in ableton.

Eta Carinae · Post by **Eta Carinae** » Sat Oct 18, 2014 1:08 pm

I'm sure that whatever Bitwig do, it'll be a fresh take on midi routing. From what I've seen so far, this is the way they like to do things.

If we have the option to route midi between tracks, and also have a plugin that can receive midi from any track, that's already streets ahead! You could be receiving midi from several other tracks in one track, which is pretty cool.

Although in reality I probably won't use it for anything as complicated as that. But it's nice to have the freedom and choice.

Dunder · Post by **Dunder** » Sat Oct 18, 2014 2:39 pm

Eta Carinae wrote:If we have the option to route midi between tracks, and also have a plugin that can receive midi from any track, that's already streets ahead! You could be receiving midi from several other tracks in one track, which is pretty cool.

Stop trying to to make 'Streets Ahead' happen

On a more serious note (he he), I think a midi receive plug-in is an awesome way to do it

Eta Carinae wrote: Although in reality I probably won't use it for anything as complicated as that. But it's nice to have the freedom and choice.

Sometime you will come up with that crazy idea that requires this, that is why having the option is important. Freedom of routing is very important in a DAW.

ObsoleteAcc99 · Post by **ObsoleteAcc99** » Sat Oct 18, 2014 9:13 pm

[DELETED]

carlosjcuevasm · Post by **carlosjcuevasm** » Sat Oct 18, 2014 10:59 pm

nvm. Mistake.

KTlin · Post by **KTlin** » Sun Oct 19, 2014 10:38 pm

I really hope that Halion will work in Bitwig 1.1

Bitwig

KVR Audio

Bitwig Studio 1.1 life