Thanks.
I do not use any VST3 at all. VST2 is ok for me.
I see what is meant with sandboxing. It has a rather bad reputation for consuming resources. I don't think that the Bitwig guys could optimize it by a great lot. Although in this case it has nothing to do with MD's behaviour eg. it wouldn't prevent - and it does not - MIDI notes from reaching the plugin.
A bit in a similar way in this case, every Windows plugin is a distinct isolated process since each one requires a Linux counterpart to bridge between Windows and Linux. For instance MMultiAnalyzer cannot see other running instances. That's OK, I can live without this feature.
Again, this windows/linux bridge does not prevent anything from happening in the case of MDrummer. MDrummer does not communicate with other processes running in parallel.
I run other Windows plugins that acts as sequencers, taking MIDI notes in, played or recorded in clips. Sugar Bytes products like Obscurium and Consequence. Sonic Charge Windows drum machine Microtonic takes MIDI notes as commands for muting notes for instance and start/stop. The processes runing in such a way are isolated from each other since the bridge, linVST, does not provide communications. However they are not isolated from the system. For instance I can press copy on the Patternarium web page and press paste in Microtonic to bring the pattern here and it works.
I'm certainly looking forward to see this resolved. MDrummer is such an exceptional drum machine with incredible sounds, and more sounds are coming. It would be a pity that Bitwig is not supported.
Cheers.
[SOLVED] MDrummer and Bitwig : MIDI commands broken ?
-
- KVRAF
- Topic Starter
- 3729 posts since 3 Nov, 2015
-
- KVRAF
- Topic Starter
- 3729 posts since 3 Nov, 2015
Regarding regular Melda plugins and MIDI, it works the usual way in Bitwig as with any audio plugin that accepts MIDI commands such as MFM2, Glitch2, Waverazor, etc... : the plugin is put on a group track whose input is set to 'All Ins' (meaning all MIDI in) and then the audio to process is put on an audio track and that track is put inside the group.
I can set for instance a knob on a MIDI keyboard to control the smoothness of MAutopanMB processing an audio drum loop.
I already tried this approach with MDrummer: does not work.
I can set for instance a knob on a MIDI keyboard to control the smoothness of MAutopanMB processing an audio drum loop.
I already tried this approach with MDrummer: does not work.
-
Chandlerhimself Chandlerhimself https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=318799
- KVRAF
- 1823 posts since 19 Dec, 2013 from Japan
Are you looping the same midi note over and over? If so that is probably the problem. MD needs to know what to play before the bar starts. Sometimes even if the midi note is snapped to the beginning of the bar it isn’t sent to MD on time. When this happens MD will wait for the next bar to start playing. If you’re looping the same note I imagine MD is getting the command too late and everytime it gets ready to play the midi is telling it to stop and wait.
Take the midi note out of the loop and see if it works. If the first bar doesn’t play, move the note a bit before the bar line. MD loops by itself and IMO doesn’t need to be looped. When I’ve looped section in Reaper it sometimes takes a bar for things to sync up correctly.
Take the midi note out of the loop and see if it works. If the first bar doesn’t play, move the note a bit before the bar line. MD loops by itself and IMO doesn’t need to be looped. When I’ve looped section in Reaper it sometimes takes a bar for things to sync up correctly.
My Youtube page https://www.youtube.com/user/GuitarChandler
-
- KVRAF
- Topic Starter
- 3729 posts since 3 Nov, 2015
Yes, it is a clip looping, as shown at the very beginning of this thread. Four notes, from C-1 to C2.
Out of the loop I have a better test: the same test that works with Harrison Mixbus32C DAW on the same computer:
Connect a MIDI keyboard, play one single C-1. MDrummer starts playing (provided there's a kit and beat loaded)
Not in Bitwig.
In Bitwig MDrummer will say welcome to the MIDI notes when in Drum Pad mode. When in Drum Pad mode MDrummer will welcome to all MIDI notes and will play a drum sound if the note corresponds to a drum instrument.
Switch to normal command mode and even though the notes are banging on MDrummer's door, MDrummer will refuse to let them in, will not act upon them. In Bitwig.
It's like as if MDrummer throws itself into some kind of special mode not seen in any other plugin, some corner case state that's somehow (hopefully) very much needed for its operation but sets it apart from most, if not all other plugin devices found on the market and that was not included in Bitwig's software plans. Why does it need that ? Have no idea.
For comparison, the Microtonic drum machine (Windows VST) will accept MIDI note commands to start playing patterns, mute channels and play instruments (all at the same time) without having to resort to a special mode of operation as such (from my notes) :
(Axiom 25 octave 0) : Mute drum channels, keys C to G.
(Axiom 25 octave 1) : Start playing specific pattern C to G = 1
to 8. C2 = stop C2 twice = stop immediately
(Axiom 25 octave -1) : Play instrument, C to G= 1 to 8
Why can't it be a simple operation ? Receive a MIDI note like all other MIDI notes in Drum Pad mode and start playing a pattern upon reception. Why get into a state where the practical net result in Bitwig is no longer responding on incoming MIDI notes ?
I feel that both Vojtech and Bitwig will hold their stance. They both have other things to do and from their perspective they have sales, and so it works.
That leaves me for the time being with a wonderful drum machine that cannot be used creatively to compose pieces.
And with a mystery... what is exactly this everything seems to work fine in Bitwig that Vojtech wrote earlier in this thread ?
Out of the loop I have a better test: the same test that works with Harrison Mixbus32C DAW on the same computer:
Connect a MIDI keyboard, play one single C-1. MDrummer starts playing (provided there's a kit and beat loaded)
Not in Bitwig.
In Bitwig MDrummer will say welcome to the MIDI notes when in Drum Pad mode. When in Drum Pad mode MDrummer will welcome to all MIDI notes and will play a drum sound if the note corresponds to a drum instrument.
Switch to normal command mode and even though the notes are banging on MDrummer's door, MDrummer will refuse to let them in, will not act upon them. In Bitwig.
It's like as if MDrummer throws itself into some kind of special mode not seen in any other plugin, some corner case state that's somehow (hopefully) very much needed for its operation but sets it apart from most, if not all other plugin devices found on the market and that was not included in Bitwig's software plans. Why does it need that ? Have no idea.
For comparison, the Microtonic drum machine (Windows VST) will accept MIDI note commands to start playing patterns, mute channels and play instruments (all at the same time) without having to resort to a special mode of operation as such (from my notes) :
(Axiom 25 octave 0) : Mute drum channels, keys C to G.
(Axiom 25 octave 1) : Start playing specific pattern C to G = 1
to 8. C2 = stop C2 twice = stop immediately
(Axiom 25 octave -1) : Play instrument, C to G= 1 to 8
Why can't it be a simple operation ? Receive a MIDI note like all other MIDI notes in Drum Pad mode and start playing a pattern upon reception. Why get into a state where the practical net result in Bitwig is no longer responding on incoming MIDI notes ?
I feel that both Vojtech and Bitwig will hold their stance. They both have other things to do and from their perspective they have sales, and so it works.
That leaves me for the time being with a wonderful drum machine that cannot be used creatively to compose pieces.
And with a mystery... what is exactly this everything seems to work fine in Bitwig that Vojtech wrote earlier in this thread ?
-
- KVRist
- 106 posts since 13 May, 2018
user: melda plugin is not working in host X but all other plugins with same features working fine - must be a melda problem.
melda: plugin does not work in host X but in all other hosts - must be a host problem.
Lots of topics in here end like that. Unfortunately it's a dead end on both sides. The good thing with your problem is that you can prove the plugin receives MIDI events fine but does not respond to it. So it is more likely a plugins problem and not the hosts fault.
melda: plugin does not work in host X but in all other hosts - must be a host problem.
Lots of topics in here end like that. Unfortunately it's a dead end on both sides. The good thing with your problem is that you can prove the plugin receives MIDI events fine but does not respond to it. So it is more likely a plugins problem and not the hosts fault.
-
- KVRAF
- Topic Starter
- 3729 posts since 3 Nov, 2015
Yes and no. I can see both sides. And both sides are making money and have other things to do.
It should be stated up front on Melda's product page that MDrummer does not work with Bitwig.
I am still hoping for a resolution ... from somewhere.
Or maybe the mystery will have some light shed upon ?
Cheers.
It should be stated up front on Melda's product page that MDrummer does not work with Bitwig.
I am still hoping for a resolution ... from somewhere.
Or maybe the mystery will have some light shed upon ?
Cheers.
-
Chandlerhimself Chandlerhimself https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=318799
- KVRAF
- 1823 posts since 19 Dec, 2013 from Japan
Why are you looping the notes? I’m guessing that is the problem. Of course it could be something else, but there is really no reason to loop midi commands. Have you tried just using 1 midi command without looping and seeing if that works? If that doesn’t work then there is a communication problem between bitwig and MD, but if it does work then like I said above it’s probably just a problem with looping and midi command timing.mevla wrote:Yes, it is a clip looping, as shown at the very beginning of this thread. Four notes, from C-1 to C2.
Out of the loop I have a better test: the same test that works with Harrison Mixbus32C DAW on the same computer:
Connect a MIDI keyboard, play one single C-1. MDrummer starts playing (provided there's a kit and beat loaded)
Not in Bitwig.
In Bitwig MDrummer will say welcome to the MIDI notes when in Drum Pad mode. When in Drum Pad mode MDrummer will welcome to all MIDI notes and will play a drum sound if the note corresponds to a drum instrument.
Switch to normal command mode and even though the notes are banging on MDrummer's door, MDrummer will refuse to let them in, will not act upon them. In Bitwig.
My Youtube page https://www.youtube.com/user/GuitarChandler
-
- KVRian
- 975 posts since 10 Jan, 2007 from London
This could well be a problem with some kind of the Bitwig/MD relationship...but I've re-read everything you've said re MIDI channels and I still have a lingering doubt that your MIDI commands are actually set to channel 1. Can you start again with a fresh MIDI clip, forget your keyboard for now (indeed, turn off record arming), just enter some commands with mouse...and somehow make sure they are channel one. I guess by default they would be, but is there a way in Bitwig to check that; note properties or something?
I was about to say try it without looping but see Chandlerhimself (yes, the man in person) just suggested that....looping the clip works here in Reaper but who knows, might be a problem with Bitwig/MD.
I was about to say try it without looping but see Chandlerhimself (yes, the man in person) just suggested that....looping the clip works here in Reaper but who knows, might be a problem with Bitwig/MD.
-
- KVRAF
- Topic Starter
- 3729 posts since 3 Nov, 2015
That's precisely what I described and what you quoted. Connect a MIDI keyboard press one, only one C-1 note. That's it. Ain't a loop. Unless you press again and again. Damn, it doesn't work, and continue hitting the same noteChandlerhimself wrote: Why are you looping the notes? I’m guessing that is the problem. Of course it could be something else, but there is really no reason to loop midi commands. Have you tried just using 1 midi command without looping and seeing if that works? If that doesn’t work then there is a communication problem between bitwig and MD, but if it does work then like I said above it’s probably just a problem with looping and midi command timing.
I have described that this works in Harrison Mixbus32C and not in Bitwig.
-
- KVRAF
- Topic Starter
- 3729 posts since 3 Nov, 2015
By now I have tried just about everything. I've put the C-1 note on the second bar to be certain it does not clip right at the start (can happen sometimes). I sent a single MIDI note. I tried in Mixbus32C that I use for mixing/mastering: it works. But not in Bitwig.
Sandboxing is disabled. I used two Bitwig filter devices to specify MIDI channel 1 right before MD. All details in previous replies in this thread.
As I've said, late last week was my 362nd improv/jam/piece in 2.5 years, "Escape of the Hopping Rhinos" in the signature below. All made in Bitwig. That's about a creation per 2 days for the last 2.5 years. Some going up to 35 tracks in Bitwig and close to 50 tracks at mixdown in Mixbus32C. All have synths of various types. So I'm not exactly new in the field. And my work so far is in software development, embedded style.
Still, the mystery remains with what Vojtech wrote earlier in this thread that everything seems to work fine in Bitwig. I would like to know exactly what's this everything is and how it is precisely achieved. MDrummer certainly stands out of the rest of plugins regarding its behaviour, at least at a certain level enough to scratch Bitwig software development, so it might be just a tiny option, a little something in MDrummer that makes all the difference. Something that only someone who knows the product very well can immediately know. Maybe, hopefully.
Cheers.
Sandboxing is disabled. I used two Bitwig filter devices to specify MIDI channel 1 right before MD. All details in previous replies in this thread.
As I've said, late last week was my 362nd improv/jam/piece in 2.5 years, "Escape of the Hopping Rhinos" in the signature below. All made in Bitwig. That's about a creation per 2 days for the last 2.5 years. Some going up to 35 tracks in Bitwig and close to 50 tracks at mixdown in Mixbus32C. All have synths of various types. So I'm not exactly new in the field. And my work so far is in software development, embedded style.
Still, the mystery remains with what Vojtech wrote earlier in this thread that everything seems to work fine in Bitwig. I would like to know exactly what's this everything is and how it is precisely achieved. MDrummer certainly stands out of the rest of plugins regarding its behaviour, at least at a certain level enough to scratch Bitwig software development, so it might be just a tiny option, a little something in MDrummer that makes all the difference. Something that only someone who knows the product very well can immediately know. Maybe, hopefully.
Cheers.
-
- KVRAF
- 10376 posts since 2 Sep, 2003 from Surrey, UK
Can you send a problem Bitwig project to Vojtech so he can have a look?
https://www.meldaproduction.com/about/contact
https://www.meldaproduction.com/about/contact
-
- KVRAF
- Topic Starter
- 3729 posts since 3 Nov, 2015
Done. Thanks.DarkStar wrote:Can you send a problem Bitwig project to Vojtech so he can have a look?
-
- KVRAF
- Topic Starter
- 3729 posts since 3 Nov, 2015
Update. There a very good email exchange with Vojtech. I will also see with Bitwig.
Cheers.
Cheers.
-
- KVRAF
- Topic Starter
- 3729 posts since 3 Nov, 2015
Vojtech has found out after debugging work from a Bitwig session I sent him, that Bitwig is sending the improper channel number. Bitwig sends the channel number + 1. This means that Rhythm Channel 1 in MDrummer will not be activated. It also means that Rhythm Channel 2 will be activated by, for instance, a C-1 MIDI note in a clip.
So this is great. Thanks a lot to Vojtech ! It becomes possible to use MDrummer with channel MIDI 2, and perhaps with other channels upwards as I learn more about MDrummer, although a single channel is all right.
Time to watch the videos made by Chandler and open the user guide !
Cheers.
So this is great. Thanks a lot to Vojtech ! It becomes possible to use MDrummer with channel MIDI 2, and perhaps with other channels upwards as I learn more about MDrummer, although a single channel is all right.
Time to watch the videos made by Chandler and open the user guide !
Cheers.