My previous post I have an Edit with an example using exactly that.goatgirl wrote:Thankfully, I have not used Live much so I don't know how it does things. Which probably makes it easier for me to learn Bitwig, as I'm not carrying over any expectations or baggage. I just learn how Bitwig works and use it as intended.
To get back to some of the originals questions.
If you want to use a controller to mute a midi signal you can use the note filter device and set the velocity range from 0 to 0. This has the effect of stopping all MIDI messages. Then hook up the controller to the device on/off. When the device is on, the MIDI is muted. When it is off the MIDI will pass through.Ch00rD wrote:Thanks for your suggestion, but that method suffers from a similar drawback as muting clips or notes: there is no way to bind this to a controller, as far as I can see. (I would be glad to be proven wrong, of course!)ronnyrydgren wrote:Just alt+a and disable the channel insteed.
Muting a track does not mute its MIDI output
-
- KVRist
- 227 posts since 29 Sep, 2011
Amateurs worry about equipment, professionals worry about money, masters worry about fidelity. I just make music.
- KVRian
- 580 posts since 3 Jun, 2009
I've just hit upon this issue myself, having just bought Bitwig a little over a week ago.
I spent about two hours thinking I was doing something silly or had missed something obvious. Was going to report this as a bug (which I think I still will do) but thought i'd search here first and found this thread.
I am completely and utterly bamboozled and flabbergasted that track mutes DONT stop MIDI. What!!!!!!
I've been using MIDI sequencers since Pro24 on the Atari twenty five years ago (yes I am that old). In that time I've extensively used Cubase, Logic, Reaper and Samplitude as my main DAWs. All of these have track mutes that stop MIDI.
When using external and VST multitimbral instruments with limited outputs you absolutely need to do this - and I mean absolutely. The work flow gets so badly disrupted when you can't it just makes the whole show unworkable.
If I had spotted this while using the trial and realised the philsophy behind the design choice and that it may never get fixed, I would not have bought Bitwig. No way.
But now that I have all I can do is plead that the developers realise why a lot of us need this - and fix it - quickly! Please.
I spent about two hours thinking I was doing something silly or had missed something obvious. Was going to report this as a bug (which I think I still will do) but thought i'd search here first and found this thread.
I am completely and utterly bamboozled and flabbergasted that track mutes DONT stop MIDI. What!!!!!!
I've been using MIDI sequencers since Pro24 on the Atari twenty five years ago (yes I am that old). In that time I've extensively used Cubase, Logic, Reaper and Samplitude as my main DAWs. All of these have track mutes that stop MIDI.
When using external and VST multitimbral instruments with limited outputs you absolutely need to do this - and I mean absolutely. The work flow gets so badly disrupted when you can't it just makes the whole show unworkable.
If I had spotted this while using the trial and realised the philsophy behind the design choice and that it may never get fixed, I would not have bought Bitwig. No way.
But now that I have all I can do is plead that the developers realise why a lot of us need this - and fix it - quickly! Please.
-
- Banned
- 1601 posts since 29 Sep, 2014 from Halmstad, Sweden
Armageddon... whent he world has ended hehe.slackhead wrote:I've just hit upon this issue myself, having just bought Bitwig a little over a week ago.
I spent about two hours thinking I was doing something silly or had missed something obvious. Was going to report this as a bug (which I think I still will do) but thought i'd search here first and found this thread.
I am completely and utterly bamboozled and flabbergasted that track mutes DONT stop MIDI. What!!!!!!
I've been using MIDI sequencers since Pro24 on the Atari twenty five years ago (yes I am that old). In that time I've extensively used Cubase, Logic, Reaper and Samplitude as my main DAWs. All of these have track mutes that stop MIDI.
When using external and VST multitimbral instruments with limited outputs you absolutely need to do this - and I mean absolutely. The work flow gets so badly disrupted when you can't it just makes the whole show unworkable.
If I had spotted this while using the trial and realised the philsophy behind the design choice and that it may never get fixed, I would not have bought Bitwig. No way.
But now that I have all I can do is plead that the developers realise why a lot of us need this - and fix it - quickly! Please.
Sry but you make this such a big deal... Actually like this is the worst thing ever and you can not live with yourself anymore am i right? Well its sure is not a fun experience when a daw dont turn out like those you are used to. But then again its a diffrent daw. The workflow of bitwig is amazing btw. One small thing like this, when you get the advantage of the rest of things bitwig offers i think its a deal...
desktop: windows 10 x64, i5 4690k, 32gb ram 1600mhz, 2x ssd 128 gb +2x3 tb, asus gtx 970, asus proz gamer motherboard, no external audiocard
laptop: windows 10 x64, i7 mq4700, 12gb ram 1600mhz, 1 tb, asus gt 750
laptop: windows 10 x64, i7 mq4700, 12gb ram 1600mhz, 1 tb, asus gt 750
-
- Banned
- 1601 posts since 29 Sep, 2014 from Halmstad, Sweden
Nah thanks i have my license but thanks anyway:)slackhead wrote:"If bitwig dont suit you just sell your license "
OK - you buying????
desktop: windows 10 x64, i5 4690k, 32gb ram 1600mhz, 2x ssd 128 gb +2x3 tb, asus gtx 970, asus proz gamer motherboard, no external audiocard
laptop: windows 10 x64, i7 mq4700, 12gb ram 1600mhz, 1 tb, asus gt 750
laptop: windows 10 x64, i7 mq4700, 12gb ram 1600mhz, 1 tb, asus gt 750
-
- Banned
- 1601 posts since 29 Sep, 2014 from Halmstad, Sweden
but i found one area that muting tracks dont mute midi can be aweful. Is when you have multiout drums. Then you use 5 midi to send each to the channel you created inside the device. one kick, one snare, one tomb etc. You want to mute the snares. Then its not possible and i can see this as annoying like hell. Because you cant open up the outputs and mute them in the arranger only in mixer. i totally get the annoying thing with this now XD Its just that i dont have multi out, but thought of thinking of one area i could totally be annoyed with it
desktop: windows 10 x64, i5 4690k, 32gb ram 1600mhz, 2x ssd 128 gb +2x3 tb, asus gtx 970, asus proz gamer motherboard, no external audiocard
laptop: windows 10 x64, i7 mq4700, 12gb ram 1600mhz, 1 tb, asus gt 750
laptop: windows 10 x64, i7 mq4700, 12gb ram 1600mhz, 1 tb, asus gt 750
- KVRian
- 580 posts since 3 Jun, 2009
Exactly - you're beginning to get the idea!ronnyrydgren wrote:but i found one area that muting tracks dont mute midi can be aweful. Is when you have multiout drums. Then you use 5 midi to send each to the channel you created inside the device. one kick, one snare, one tomb etc. You want to mute the snares. Then its not possible and i can see this as annoying like hell. Because you cant open up the outputs and mute them in the arranger only in mixer. i totally get the annoying thing with this now XD Its just that i dont have multi out, but thought of thinking of one area i could totally be annoyed with it
-
- Banned
- 1601 posts since 29 Sep, 2014 from Halmstad, Sweden
everybody who thinks this is annoying send a mail here http://www.bitwig.com/en/support/tech-support.html
Write how this disrupt your flow and why its important for you to have it and how you have used it before. One example is the thing i described as multiout and having several miditrack for each drum. But its better to write to tech support. This is only forum and no place to say how bad things are bla bla. send a mail and the more that sends maybe you can make them understand the real problem for you guys. Seems alot complaining about this and i start to get the idea. bitwig is wonderful, would be to bad that this would make you get off bitwig
Write how this disrupt your flow and why its important for you to have it and how you have used it before. One example is the thing i described as multiout and having several miditrack for each drum. But its better to write to tech support. This is only forum and no place to say how bad things are bla bla. send a mail and the more that sends maybe you can make them understand the real problem for you guys. Seems alot complaining about this and i start to get the idea. bitwig is wonderful, would be to bad that this would make you get off bitwig
desktop: windows 10 x64, i5 4690k, 32gb ram 1600mhz, 2x ssd 128 gb +2x3 tb, asus gtx 970, asus proz gamer motherboard, no external audiocard
laptop: windows 10 x64, i7 mq4700, 12gb ram 1600mhz, 1 tb, asus gt 750
laptop: windows 10 x64, i7 mq4700, 12gb ram 1600mhz, 1 tb, asus gt 750
- KVRian
- 580 posts since 3 Jun, 2009
Already did that. Fingers crossed.ronnyrydgren wrote:everybody who thinks this is annoying send a mail here http://www.bitwig.com/en/support/tech-support.html
-
- KVRAF
- 5144 posts since 3 Oct, 2013
"You want to mute the snares. Then its not possible and i can see this as annoying like hell."
don't get it, why don't u simply solo the affected audio out subtrack/layer of the multiout VSTi ?
don't get it, why don't u simply solo the affected audio out subtrack/layer of the multiout VSTi ?
"Where we're workarounding, we don't NEED features." - powermat
-
- Banned
- 1601 posts since 29 Sep, 2014 from Halmstad, Sweden
that would mean you would have to open up the mixer. Its disrupts the work flow get it i get it:) would be easier just to mute the track if you want to mute.. but alt+a on the clip works also but still people will be annoyedxbitz wrote:"You want to mute the snares. Then its not possible and i can see this as annoying like hell."
don't get it, why don't u simply solo the affected audio out of the multiout VSTi ?
desktop: windows 10 x64, i5 4690k, 32gb ram 1600mhz, 2x ssd 128 gb +2x3 tb, asus gtx 970, asus proz gamer motherboard, no external audiocard
laptop: windows 10 x64, i7 mq4700, 12gb ram 1600mhz, 1 tb, asus gt 750
laptop: windows 10 x64, i7 mq4700, 12gb ram 1600mhz, 1 tb, asus gt 750
- KVRian
- 580 posts since 3 Jun, 2009
I agree. Bitwig has some great ideas and a very approachable interface, but little things like this (which in my mind are very fundamental and basic) can really let it down. It's as if the devs have their idea of how a DAW should work (which is fair enough) and have not considered how lots of others might want to use it.ronnyrydgren wrote:bitwig is wonderful, would be to bad that this would make you get off bitwig
The whole "if you don't like the ride get off the bus" approach can only lead one way and that is down a very steep hill!
- KVRian
- 580 posts since 3 Jun, 2009
Also, the output could well being used for other sounds. This is particularly the case with hardware instruments. I often run 8 or 10 sounds from a module that only has two stereo outs.ronnyrydgren wrote:that would mean you would have to open up the mixer. Its disrupts the work flow get it i get it:) would be easier just to mute the track if you want to mute.. but alt+a on the clip works also but still people will be annoyedxbitz wrote:"You want to mute the snares. Then its not possible and i can see this as annoying like hell."
don't get it, why don't u simply solo the affected audio out of the multiout VSTi ?
And in a live situation muting the audio cuts of any tails that might be playing. Not acceptable.
