The Synthmaster 3 Thread

[kv331]

Is there also a way to change that setting globally? I don't want to change each layer to MPE one by one.

And please also provide a way to change the pitch-bend range for all oscillators and layers at the same time. This is useful for MPE as well because the appropriate pitch bend range can change depending on the controller.

Those were in my mind as well. Changing Midi Input Channel / Pitch Bend Range for each layer is not user friendly. I will put global settings for those two.

[Held]

Those were in my mind as well. Changing Midi Input Channel / Pitch Bend Range for each layer is not user friendly. I will put global settings for those two.

That's great to hear. SM3 already sounds great and with all the usability improvements it hopefully will also be fun to use.

[ReverendLove]

Does your user name have any non-ascii characthers ? or is the program files located at a path that contains non-ascii characthers? (I am now testing the latter case)

Like ğüşiöç ?

EDIT: I tested with non-ascii path for SM3 data folder. No issues so far.

Phew, that was a spent day. I zried nearly everything.

At rhe end - knowing that SM3 gives me the license for SM2 too - I did an uninstall of SM2 & 3. Then I installed SM3 FIRST amd what a surprise: No error, no freeze no warning. It runs w/o catastrophic issues on Cubase 13 Pro. Now I did a setup of SM2.9.16. No issues at all.
Case closed!

With Love
Reverebd

[Milkman]

Im just trying to use CC1/modwheel in synthmaster 1 or 2. It doesnt work, and if you try to bind it (software claims it is already bound) again, synthmaster2 crashes. Its been this way years on cubase and bitwig.

You don't MIDI Learn the Mod Wheel or Pitch Wheel. They are updated already by the incoming MIDI data that the plugin receives.

The modwheel in SM2 and SM1 DOES NOT WORK using any controller or keyboard. I tried to bind it BECAUSE IT DOESNT WORK, so I tried to midi-learn the mod wheel in desperation. THIS CAUSES SM2 to CRASH, as I mentioned in the comments and threads I created about this here in early 2022. I asked "if I buy SM2 today and you release SM3 soon, will I get a discount?", and you replied that I would. Then I found the modwheel issue, and nobody ever explained it or helped me!

This has been going on SO long, and Ive asked about it SO many times, its hard for me to really understand. I will NOT buy SM3 or upgrades to "find out if it works" as dubious people have repeatedly suggested. Either prove to me this is fixed, or Ill skip it.

[Milkman]

Guys, what do you mean? The modwheel works just fine in SM3. I just tested it again in Bitwig just to be sure. You can assign it to any modulatable parameter in SM3.
Like this:


modwheel.jpg


And you can also MIDI-learn it. And it works as expected.

Can one single person confirm or deny if the modwheel works properly, and/or if it can be assigned in SM3?

Yes, it works properly.

The issue is about Sythmaster 1 and 2, which had this issue for many years without a fix. If it FINALLY works in SM3, this is still incredibly frustrating and strange that such an issue was abandoned for that many years, and this concerns me to do with any future issues.

[kv331]

Then I found the modwheel issue, and nobody ever explained it or helped me!

This has been going on SO long, and Ive asked about it SO many times, its hard for me to really understand. I will NOT buy SM3 or upgrades to "find out if it works" as dubious people have repeatedly suggested. Either prove to me this is fixed, or Ill skip it.

My answer from the previous page:

What is your DAW? Bitwig certainly has this issue. ModWheel works fine with other DAWS (VST2 AND VST3)

and just to make sure that it is NOT our issue, I debugged Bigwig Studio: Bitwig does NOT send MIDI CC messages to the VST3 plugin (I selected Generic MIDI Controller for my input). Other DAW do send because our plugins support IMidiMapping interface

[Milkman]

It works in the synth but neither Synthmaster 2 or 3 detect the mod wheel input from either my M-Audio Pro Mini or Arturia Minilab keyboards. The pitch bend wheel works on both.

This looks like a BitWig specific issue. ModWheel works fine with other DAWS (VST2 AND VST3)

and just to make sure that it is NOT our issue, I debugged Bigwig Studio: Bitwig does NOT send MIDI CC messages to the VST3 plugin (I selected Generic MIDI Controller for my input). Other DAW do send because our plugins support IMidiMapping interface

This is NOT a DAW specific issue, as I mentioned in my year ago post asking for help with it. I was using cubase 11, then 12, and it happens on any of my 6 controllers from any brand. It also happens in Live and Bitwig, I can confirm.

I am not convinced - I will wait for full SM3 release, I will wait for various user feedback. Something isnt right here.

Edit: just saw your last reply - I use multiple DAWs, many keyboards and controllers and this issue is consistent everywhere, including on a separate laptop/workstation. Windows10, focusrite 18i20, consistent behavior across 2 system rebuilds on this system.

Modwheel does NOT work unless you click the mouse and turn it onscreen.

[kv331]

Modwheel does NOT work unless you click the mouse and turn it onscreen.

To end the discussion:

1. I can not fix something I can not reproduce .
2. I can not fix something that is caused by the DAW (Bitwing not sending the synth MIDI CC messages) .

[kv331]

At rhe end - knowing that SM3 gives me the license for SM2 too - I did an uninstall of SM2 & 3. Then I installed SM3 FIRST amd what a surprise: No error, no freeze no warning. It runs w/o catastrophic issues on Cubase 13 Pro. Now I did a setup of SM2.9.16. No issues at all.

Closed for you but not for me

Did you delete documents/synthmaster2 folder before running SM3 again ? because normally SM3 searches for license key file under documents/synthmaster2 folder. I wonder if something went wrong with the SM2 license key file. I will test for that case now.

[audio/fault]

Really looking forward to SM3, but i have one small feature request:
an option to change the scrolling behaviour in the presets. i'm sure different users have different behaviours, but i'm used to scrolling down, when my fingers move down on the apple mouse. in SM2 it's the other way round and it's driving me nuts

[kv331]

in SM2 it's the other way round and it's driving me nuts

Does reversing the mouse wheel help with that ? (Under Settings/User Interface)

(If it doesn't help no worries, I will add a new setting for listbox scroll)

[ReverendLove]

Closed for you but not for me

Did you delete documents/synthmaster2 folder before running SM3 again ?

Yes, that is exactlx what I did. I deleted all visible traces of SM2 & 3 left by the uninstallers. For the license I only used the file delivered with SM3.

[DazzW]

OS is Microsoft Windows [Version 10.0.19045.3803] German language

Does your user name have any non-ascii characthers ? or is the program files located at a path that contains non-ascii characthers? (I am now testing the latter case)

Like ğüşiöç ?

EDIT: I tested with non-ascii path for SM3 data folder. No issues so far.

I've a standard Win 11 install (I believe it was the same when I had Win 10) and my username is basic non-accented English letters. I'm using Bitwig 5.1 which apparently has VST API Version 3.7.9.

[geiger167]

I'm just looking at the everything bundle on the site and noticed one and two have full NKS support, will synthmaster 3 also continue NKS support and what presets will it ship with (I wont be using 3 till it is out of Alpha so will be playing with 1 and 2 in the meantime)

[kv331]

Yes, we will introduce NKS for SM3 as well. Let's first finish the product