Modo Bass 2 Certain Strings Not Sounding (Broken!)

[fulvia]

Anyone else get this bug where a string totally stops sounding (as if it's a broken string!) https://youtu.be/w6aftkoPosw
It happens to me quite a lot. Not always the same string that fails.

I've got several support tickets on the go as one is for sticking notes also.

Just to confirm, this happens in Reaper, plus standalone, and even if you play the note/string with the mouse, it still does not sound which I guess excludes the midi in set up.

[BarryLegg1980]

You might have inadvertently toggled on a keyswitch or control change which mutes that particular string.

[BarryLegg1980]

Check you’ve got the right number of strings set (in the video you posted - the guy is using a 5 string bass but it’s somehow saying it’s a 4 string bass) and check that haven’t accidentally latched on something here that could be causing weird behaviour

[fulvia]

It never happened with Modo 1.
Could others possibly check that there should be no similar issues modifying models by changing number of strings?
Just can't see what's causing it.
One thing I noticed was that changing the age of the string corrected it, but it's not really a proper fix as the problem crops up regularly.

[BarryLegg1980]

I have all sorts of weird issue ps like this with 1. I couldn’t say if I have this exact one. But having ‘drop’ tuning on and 5 strings would confuse things. Most of the issues I had came from keyswitch / control change overlaps though.

Tbh it would make much, much more sense the user could just set the tuning of each string yourself rather than relying on this ‘drop’ option.

Things get extra confusing when you’ve set Cc /Ks notes in your piano roll and you’re looping back and forth over those notes and they don’t always toggle correctly….

[mod redacted - unnecessary]

[mfassi94]

Hi

I have same exact issue.
I reported it to IK team. No feedback since.
Some time ago I pinged them to see what's happening. They told me the issue is still under investigation.

[fulvia]

Hi

I have same exact issue.
I reported it to IK team. No feedback since.
Some time ago I pinged them to see what's happening. They told me the issue is still under investigation.

Ahh! Thank you! So glad it's not just me. When it happens, if you change the string age, does it get to work again?

I've been through all my control map settings and cannot pin down anything. Plus, there's nothing in there which mutes a particular string like someone mentioned, so cannot see how it is that.

[Cdbaksu84]

I'm having the same issue but with the E string. Pressing the ! panic button restores the sound, only to have it die out (with a small click) when I play the lower notes again.

Has there been any fix or any updates regarding this?

[_cherryblossom]

This is happening to me as well. I have a 5 string instrument, and when the bottom string (E) is played, all sound stops. Pressing panic sometimes restores sound, sometimes does not.

[_cherryblossom]

So I've found a possible workaround fix ... The issue seems to be triggered by the lowest string. So if I need 5 strings, I add a 6th string to the bass, then the problem happens every time the 6th string is triggered. So I add a keyswitch to force E string (5th) whenever the MODO Bass player would automatically choose the B string (6th). This seems like it should be a high priority fix since it leaves the whole workflow completely messed up.

[hcmarkus]

Ongoing issue here.

Best way to recover for me (running Digital Performer) is to Disable, then Re-Enable the VI.

Very annoying and only occurs with MODOBass 2. MB1 doesn't display this issue.

[Peter_IK]

If you feel you have uncovered a bug in the software, please report your issues to IK Support and they will be able to take it from there.