Hi.
I’ve started testing the latest beta version of MG3 with SuperCollider and I noticed that I am getting a stream of midi pitchbend events at zero, despite having the pitchbend turned off. I’m on a Macbook air M1. MG3 as a standalone application routed to SuperColliders midi in.
So how are you connecting? Are you using SuperCollider also as standalone and connecting via a MIDI OUTPUT module (MIDI Machine) on some of the chains? Are you using the NO BENDS option in MIDI OUTPUT? I tried this and got nothing on PB.
Hi.
Both applications are as standalone. I’m connecting via a MIDI output module on a chain with no bends selected. The module is in standard MIDI mode, not MPE. Channel pressure is also off.
So do you have any other controllers connected as well? If you want to try a great free MULTI controller MIDI Monitor I can recommend Gert Bevins ShowMIDI app. With that I can easily identify what sources are sending what information. GitHub - gbevin/ShowMIDI: Multi-platform GUI application to effortlessly visualize MIDI activity
in MG2 pitchbend=0 is send continously, as soon as pitchbend > 0 has been sent before. This is most likely part of the auto pitchbend mechanism, that switches between bends when 1 note sounds and non-bend when polyphonic.
Yes, of course. Like @Paul points out here, you will have something (a fixed value) for pitch bend. But you won’t have any change to that value. It is the 0 (64 or 8192) value. It looks like this in Ableton:
I have other controllers, like breath controllers etc, but I always keep my setup limited to what I’m actually using at the time. Thanks for the free app recommendation.
Ok, thanks. It just seems a bit unnecessary to fill up midi buffers with information that’s not needed. I can understand a zero message after bends are turned off, but don’t understand the constant stream after that single event. It doesn’t really matter though, Cubase couldn’t care less and SuperCollider will only respond to whatever I code it to do. I was just surprised to see the pitchbend information there, I just happened to be printing out received events in SuperCollider whilst debugging code.
But thanks, at least it’s not a bug. 
1 Like
I’m seeing the same issue: lots of pitchbend = 0 on the no pitchbend preset. This is a problem for me as I use a foot pedal for pitchbend in my set up. Every time MG3 Hex sends a pitchbend = 0 it overrides the output of the pedal creating an ugly warble.
I’ve written a script in MainStage which filters pitchbend on channels 2-7 (for pitchbend events coming from MG3 Hex) and set my pedal to send pitchbend on channel 1. So it’s solved for me but it would be good to have no pitchbend in the stream to start with.
Please help us understand.
How do you set up to acess MIDI channel 1 for foot pedal control over Pitch bends while still having separate per-note pitch bends on MIDI channels 2-7?
Are you introducing the pedal MIDI outside of MG3, so that the override is between the pedal and the MG3 PW (pitch bend) =0 messages in (say) MainStage? Or can you get this warble also with a setup completely done in MG3 alone?
I use MG3 Hex standalone to send MIDI to MainStage. MG3 Hex is configured with MIDI 1.0 Multi-channel, No Pressure, and No Bends. I also use an Audiofront MIDI Expression device (with expression pedal attached) to send pitchbend (only down) to MainStage. I’ve attached screenshots of MG3 and MainStage’s MIDI event log.
I have a pretty stable gigging rig in MainStage so haven’t explored MG3 Hex for hosting VSTs so can’t say if the warble would be eliminated in that use case. Anyway I’ve solved the issue with a script in MainStage.
Wish me luck as I have my first gig with MG3 Hex tomorrow. (I just picked up MG3 and Hex last week.)
Yeah, there is nothing unexpected there. MIDI guitar 3 is sending pitch bend = 0 for each string also on the MIDI 1.0 Multichannel output. But with “No Bends”, probably also a pitch bend = 0 for the pitch bend on Ch 1 (for the Pitch Wheel). I guess this could be what clashes with the expression pedal pitch bend you are sending on Ch. 1 directly in MainStage.
It is not an issue with MG3 itself really, even if it might be a problem with this setup. Your filter solves this, and I wish you the best of luck with you upcomong gig. 
may you rock on with your bad self. good luck tomorrow!