The Synthmaster 3 Thread

[kv331]

Kv331 - Could you please add a parameter lock function? Or some way to disable effects or the arp globally.

Hi,

We already have "module lock/unlock" functionality

lock section.jpg

[Milkman]

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

Mod wheel and pitch wheel are controlled by the incoming MIDI messages (MIDI CC0 and MIDI Channel Pitch Bend messages), they are not automateable parameters. (I answered this question in our facebook users group last month as well, but I think you are not a member of that group). So, instead of automating those, you record MIDI CC in your DAW and send those messages to the plugin.

Bulent

Thanks for the reply.

I dont use facebook, so I wouldnt have seen that, no.
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.

If synthmaster3 has the same issue (cant use physical CC1 modwheel), I would be shocked. Are you saying you also cannot use a physical modwheel in SM3, and I will have to write CC1 messages manually into my DAW?

[kv331]

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.

[DazzW]

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.

Same here, the mod wheel hasn't worked in any of the Synthmaster versions for me in Bitwig either.

I'm loving v3 so far and looking forward to using the final version but a good modern dark skin will make or break it for me. A huge part of why I switched to Bitwig is that Ableton felt like creating in an Excel sheet so I hope Synthmaster 3 doesn't fall at this hurdle as visuals are a big part of the inspriation/creation vibe for a lot of people who'll use something that's visually pleasing over something that can do more but just looks functional.

[KTlin]

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.

[ericzang]

Does SM3 still have microtuning via scala? Is there any consideration about adding MTS-ESP capability? Thanks.

[ReverendLove]

The VST2 DLL prevents Cubase 13 from startimg and got blacklisted.
Further I got a messages with status information about my system the VST hosr (Cubase 13, Sound forge, Audacity, Elements, literally any). I also did not get the license dialogue. Using the VST3 all my hosts crash and Cubase 13 won't start the affected project again until I uninstall SM3.

[DazzW]

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.

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.

[kv331]

The VST2 DLL prevents Cubase 13 from startimg and got blacklisted.
Further I got a messages with status information about my system the VST hosr (Cubase 13, Sound forge, Audacity, Elements, literally any). I also did not get the license dialogue. Using the VST3 all my hosts crash and Cubase 13 won't start the affected project again until I uninstall SM3.

I tested VST2 / VST3 versions with Reaper (6) and Cubase (12). I got the license key dialog. No issues so far.

[kv331]

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

[ReverendLove]

The VST2 DLL prevents Cubase 13 from startimg and got blacklisted.
Further I got a messages with status information about my system the VST hosr (Cubase 13, Sound forge, Audacity, Elements, literally any). I also did not get the license dialogue. Using the VST3 all my hosts crash and Cubase 13 won't start the affected project again until I uninstall SM3.

I tested VST2 / VST3 versions with Reaper (6) and Cubase (12). I got the license key dialog. No issues so far.

Well, so we should find what are the differences between your and my system.
OS is Microsoft Windows [Version 10.0.19045.3803] German language

I don't assume that the hosts (ubase 13, Sound Forge, Audacity, Elements, mulab, Soectralayers 10, Wavelab Essential) are the problem as they all behave nearly the same.

I tried different things until mow: Dehault insrallation, dehault insrallation as Admin,
customized installation with paths outside the "Program Files" folder.

Even an installation of Windows in repair mode did not help.

[kv331]

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.

[kv331]

P.S. Loaded VST2, no MPE at all, unless I did not find the right spot to activate it...

Just fixed the MPE stuff. It now works in BOTH VST2 AND VST3

Also, you can change the MIDI Input Channel for each single layer, so that each can receive MIDI input from a different channel:

mpe.jpg

[KTlin]

Just fixed the MPE stuff. It now works in BOTH VST2 AND VST3
Also, you can change the MIDI Input Channel for each single layer, so that each can receive MIDI input from a different channel

Great!

[Held]

Also, you can change the MIDI Input Channel for each single layer, so that each can receive MIDI input from a different channel:

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.