KVR Audio

jamcat · Post by **jamcat** » Tue May 31, 2022 3:57 pm

jbraner wrote: Tue May 31, 2022 11:55 am
jamcat wrote: Mon May 30, 2022 8:35 am Has anyone else confirmed this bug?
Hi jamcat,
I have to say that using the LH neck position keyswitches seems to be working here.
The only time the position changes is if a not is not actually in that position - so it goes one position down or up to accomodate - but then goes right back to the correct position.

I can happily play in 5th position or 7th position etc - and it stays right where it should be.

I'll dig in some more today - and see what I can come up with...

Thanks. Are you on v2.0.0 or 2.0.1?

jbraner · Post by **jbraner** » Tue May 31, 2022 3:59 pm

I'm on 2.0.1

jamcat · Post by **jamcat** » Wed Jun 01, 2022 2:59 am

EDIT: Problem solved. (some keyswitch defaults have changed in MODO BASS 2)

Tj Shredder · Post by **Tj Shredder** » Wed Jun 01, 2022 6:42 am

jamcat wrote: Wed Jun 01, 2022 2:59 am FORCE A STRING that is broken.

Oh, they model broken strings? How cool is that…!

jamcat · Post by **jamcat** » Wed Jun 01, 2022 6:46 am

EDIT: Problem solved. (some keyswitch defaults have changed in MODO BASS 2)

jbraner · Post by **jbraner** » Wed Jun 01, 2022 7:59 am

FORCE A STRING does not work.

Double check that. I thought these "Force string"s weren't working too - but you have to play notes that are possible on that string - otherwise it plays on a different string.

It's working here.

jamcat · Post by **jamcat** » Wed Jun 01, 2022 8:35 am

EDIT: Problem solved. (some keyswitch defaults have changed in MODO BASS 2)

jbraner · Post by **jbraner** » Wed Jun 01, 2022 8:42 am

The model I’ve been testing with is the 5-string Stingray set to 4 strings and drop tuning, with OPEN STRINGS set to ON. (I don’t think any of this should make a difference, but who knows.)

Well, it may very well have a difference.
Like maybe (for it to be broken) it depends if the model is a 4 string or 5 string - or something else...

I'll play some more later.

jbraner · Post by **jbraner** » Wed Jun 01, 2022 10:44 am

jamcat wrote: Wed Jun 01, 2022 8:35 am It’s definitely not working here.

Only notes below A1 and above A3 are out of range for the A-string.

Make sure you are testing the A-string keyswitch specifically, which is A-1 by default.

The model I’ve been testing with is the 5-string Stingray set to 4 strings and drop tuning, with OPEN STRINGS set to ON. (I don’t think any of this should make a difference, but who knows.)

I can verify that it's working OK here.
ver 2.01
I used a 5 string Sting Ray bass
"Force A" is on the default A-1
It plays on the A string from A1 up to F3

I have a animated gif file - but can't work out how to upload it.
But, trust me - it's working here...

jamcat · Post by **jamcat** » Wed Jun 01, 2022 9:48 pm

jbraner wrote: Wed Jun 01, 2022 10:44 am
jamcat wrote: Wed Jun 01, 2022 8:35 am It’s definitely not working here.

Only notes below A1 and above A3 are out of range for the A-string.

Make sure you are testing the A-string keyswitch specifically, which is A-1 by default.

The model I’ve been testing with is the 5-string Stingray set to 4 strings and drop tuning, with OPEN STRINGS set to ON. (I don’t think any of this should make a difference, but who knows.)
I can verify that it's working OK here.
ver 2.01
I used a 5 string Sting Ray bass
"Force A" is on the default A-1
It plays on the A string from A1 up to F3

I have a animated gif file - but can't work out how to upload it.
But, trust me - it's working here...

Hey, thanks for your time here!

I figured it out for real this time.

The problem I was having was IK changed some of the default keyswitches in MODO BASS 2 from what they were in MODO BASS 1.5, including the A-string (it was A0 in MODO BASS 1.5).

I was using a keyswitch map for MODO BASS 1.5, so it was sending FORCE A STRING to A0 instead of A-1.

This is that "can of worms that eventually leads to trouble and confusion down the line" I was talking about when you change keyswitch defaults!

jbraner · Post by **jbraner** » Thu Jun 02, 2022 8:18 am

Yay! I'm glad you worked it out.
It's good for someone to come back and say "it's working here" - so you know it's not the actual plugin that's broken.

This is that "can of worms that eventually leads to trouble and confusion down the line" I was talking about when you change keyswitch defaults!

Oh - I get that. Reaper doesn't have anything as sophisticated as a keyswitch map - so I just refer to a piece of paper with the settings on it.
If I change from the defaults - I just change the paper!

So, now we can get on with playing with all the fretless options - and I really like the Marcus Miller bass.
One weird thing is the E5 mapping to (non DB) slap noise. That's not listed anywhere, but a lot of the "patterns" use it.

jamcat · Post by **jamcat** » Thu Jun 02, 2022 7:31 pm

Well, I hate to be a bother, but I have come across 2 other issues...

1) MODO BASS occasionally ignores the FORCE STRING keyswitch.

This problem sounds a lot like the problem I was having before, and in fact, it was one of the symptoms I was experiencing. But as it turns out, even with the keyswitch map updated for MODO BASS 2, I am still getting occasional notes played on the wrong string with FORCE STRING applied correctly. It happens only occasionally, and seemingly randomly. I can duplicate a part 10 times, and it might switch to the wrong string once during playback. Play it again, and it might happen again in a different spot, or not at all. So as it turns out, the previous problem I encountered is not completely resolved after all.

2) RIGHT HAND POSITION isn't retained separately for FINGER, PICK, SLAP.

In MODO BASS 1.5, it would remember that your FINGER position is 3.20 and your pick position is 1.90. Switch between FINGER and PICK, and the RIGHT HAND POSITION changes to the correct position. But in MODO BASS 2, the position stays where it is.

jbraner · Post by **jbraner** » Thu Jun 02, 2022 8:21 pm

1) MODO BASS occasionally ignores the FORCE STRING keyswitch.

Are you sure it's not a problem with the keymap? (translating keystrokes?)
I'm not sure what the keymap is doing - but can you just use a "normal" keyboard - without any mapping? Does that help?

I'm not using MODO Bass "in anger" yet (ie working on an actual song) so I can't guarantee that it doesn't have "hiccups"

2) RIGHT HAND POSITION isn't retained separately for FINGER, PICK, SLAP.

huh - I didn't even know it could do different positions for finger/slap (I never use pick).
I'll need to play with that...

vurt · Post by **vurt** » Thu Jun 02, 2022 8:23 pm

Tj Shredder wrote: Wed Jun 01, 2022 6:42 am
jamcat wrote: Wed Jun 01, 2022 2:59 am FORCE A STRING that is broken.
Oh, they model broken strings? How cool is that…!

jamcat · Post by **jamcat** » Thu Jun 02, 2022 9:34 pm

jbraner wrote: Thu Jun 02, 2022 8:21 pm
1) MODO BASS occasionally ignores the FORCE STRING keyswitch.
Are you sure it's not a problem with the keymap? (translating keystrokes?)
I'm not sure what the keymap is doing - but can you just use a "normal" keyboard - without any mapping? Does that help?

I'm not using MODO Bass "in anger" yet (ie working on an actual song) so I can't guarantee that it doesn't have "hiccups"

The keymap I created doesn't transform the note (though it can). All it is doing is telling Studio One that A-1 is "A String" and E-1 is "E String." Those keys are highlighted in the piano roll and rolling over them says what they do. You can also "convert Keyswitches to Sound Variations" which removes the keyswitch notes from the piano roll and places them in a special Sound Variations lane. If you update the trigger note in the keyswitch map, it automatically changes all of those Sound Variation keyswitches to the new note.

It's pretty cool, and it hides a lot of the ugliness of keyswitches, and makes updating keyswitches very easy. It also means you can transpose your notes without affecting the keyswitches, since they're removed from normal MIDI notes.

MODO Bass 2 has arrived