Notifications
Clear all
Topic starter
September 19, 2022 7:58 pm
Cubase 11 - Meldas MDrummer - and Unify.
If I put Unify on an instrument track within Cubase and put in MDrummer all on its own and set it playing a beat, after a random period - the Cubase volume for that track will jump to a random low value like -68dB or -80db or infinity. It's just MDrummer which has this problem all other instruments work wonderfully inside Unify.
If I stick MDrummer on a normal Cubase track not using Unify it works perfectly - the track volume stays where it's set. Stick MDrummer in Unify playing the same beat and the Cubase track volume randomly jumps low. Somehow MDrummer is causing Unify (or is doing it itself because its inside Unify) to reduce the track volume.
I could just use MDrummer on a normal Cubase track I suppose but I'm completely Unified now and use this wonderful thing extensively. It's late and maybe my brains too tired to spot something simple but this has got me right baffled.
EDIT: Just noticed on a brand new Unify track that adding an AUX effect lane made the Cubase track volume reduce to zero and adding and deleting AUX lanes messed about with the volume - doesn't seem repeatable and nothing concrete but this upsets my theory it was just MDrummer doing this.
This topic was modified 1 year ago by Voltaire
September 19, 2022 10:29 pm
Very interesting. This is most probably a bug in MDrummer. There is no defined mechanism whereby any plug-in can affect the host track volume, so if this is happening, it's because either MDrummer or Unify is misbehaving and writing outside of its designated memory bounds. Unless you can find a case where this happens with any plug-in other than MDrummer, I'm inclined to assume the bug is in MDrummer.
As to why MDrummer exhibits this bug inside Unify, but not directly in Cubase, it's probably because it loads at a different memory address in the two different situations.
If the bug is of the type I'm describing (known as a "bad or uninitialized pointer"), these are among the hardest kind to track down.
I suggest you contact Melda Productions, report what's happening, and point them to this forum post for details. I'll be happy to provide them with an NFR license for Unify so they can run this specific situation in a debugger, and hopefully track down the bug. (They can email me via UnifySupport@PlugInGuru.com, and specifically ask that it be forwarded to me.) If it turns out to be in Unify, they can let me know and provide me with an NFR for MDrummer so I can test in my debugger.
Topic starter
September 19, 2022 11:01 pm
Thanks for the explanation of what might be going on - but see my EDIT on the original post. It has happened on adding an AUX lane without MDrummer being used within Unify (it had UVI Workstation on an instrument lane).
As I said I just wish this was repeatable and I could be convinced it was a bug between Unify and Cubase and I could show you convincing evidence. I've happily been a Unify user for a long time and I don't think I've had this kind of problem until now. I'll play with this some more and will do some more thorough testing.
September 20, 2022 1:03 pm
Thank you for the update. It sounds like this is a Unify issue.
As I mentioned before, this kind of bug can be very difficult to track down, and as you suggest, repeatability is the key. If I can make this happen in my debug environment, I can find the bug and fix it.
Are you using Cubase on a Mac or PC? What are the exact version numbers of Cubase and Unify?
You said "adding an AUX effect lane made the Cubase track volume reduce to zero and adding and deleting AUX lanes messed about with the volume". Has this ever happened with NO third-party plug-ins loaded in Unify?
Topic starter
September 20, 2022 1:24 pm
Just to put this to bed.
Unplugging an aged Akai MPK25 seems to have fixed this. Seems this well used piece of kit may have been sending unwanted midi CC7 messages to Cubase. Shaking the desk with big kicks and wild leads may be wobbling the old pots and sending junk flying into the DAW. This bit of kit has been a bit hit and miss lately with the mod wheel not getting to 127, the pitch wheel has packed in and one or two of the control knobs sending bonkers bits of info. Message to myself - look for buggy hardware first then software.
Love it but time for a new one. Won't replace it with anything new fangled just a less well used one will do nicely.
Thanks again @getdunne. There's lots of devs who could learn a thing or two about customer support from you.
This post was modified 1 year ago by Voltaire
pluginguru and getdunne reacted
September 22, 2022 6:49 pm
good idea
September 23, 2022 5:09 pm
It's always a gremlin in a machine! This has happened more than once to people writing to us with problems like this... it actually happens to me often because the NI Keyboard controller I use has a stupid fader touch-bar right below the modulation/pitch bend wheels. It LOVES to jump to whatever value it is at when I use the wheels... grumble grumble grumble...
Life is Sound / Sound is Divine
www.pluginguru.com
September 24, 2022 9:14 pm
Sounds like you have one of the S-series MKII keyboards. That touch strip is so poorly placed. They clearly did no research into its placement and how easy it is to hit when using mod/pitch. Ridiculous.
I recommend turning off the touch strip. Load the Komplete Kontrol app, click the MIDI icon in the upper right, then click the touch strip tab. Set the option to off.
It's such a waste. I was looking forward to having a touch strip but its placement makes it 100% useless.
I actually really enjoy my S61 MKII and use it all the time. There is a lot of missing potential, but it does meet my needs for why I bought it.
Ableton Live 10, Omnisphere, Native Instruments (Pianos), Spire, Hammer + Waves, Heavyocity (Ascend and Mosaic Keys), Diva, SynthMaster, Alchemy 1.55, Addictive Keys, Unify
