The Synthmaster 3 Thread

[dionenoid]

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.

Modwheel works fine here with SM2. Has always worked fine in every version of Cubase that i used it with (now in C13), plus with any synth and/or controller that i used over the years.

You don't have to midi learn anything. Just assign anything in SM2 to the modwheel and it'll work.

[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.

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.

So I did another test (in Bitwig 5, Windows 10), but this time I tested both the VST2 and the VST3 version (the other day when I replied here I've tested just the VST2 plugin), and I also tested the SynthMaster2 (both VST versions), and here are the results: modwheel works perfectly in both SM3 and SM2 BUT ONLY in the VST2 version of the plugins! In the VST3 it doesn't work at all, neither in SM3 nor in SM2!

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

Bulent, there is nothing wrong with Bitwig. There is something wrong with the VST3 version of both SM3 and SM2. I also tested other VST3 plugins: Kontakt, Vital, Arturia Augmented Woodwinds, NI Battery, Ample Sound Guitars and the modwheel works just fine in all of them! The SM3 and SM2 are the only VST3 plugins in which the modwheel doesn't work at all. So, again, there's nothing wrong with Bitwig.

[kv331]

Bulent, there is nothing wrong with Bitwig. There is something wrong with the VST3 version of both SM3 and SM2. I also tested other VST3 plugins: Kontakt, Vital, Arturia Augmented Woodwinds, NI Battery, Ample Sound Guitars and the modwheel works just fine in all of them! The SM3 and SM2 are the only VST3 plugins in which the modwheel doesn't work at all. So, again, there's nothing wrong with Bitwig.

That is really odd. I did implement the vst3 component according to Steinberg's guidelines

[audio/fault]

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)

do you mean in the mac os settings (can't find this in SM2)? yep that helps, but unfortunately everything else is wrong then
so a new setting would be great, thanks!
though I found out, it's not only the preset-list but also for knobs, but i don't control them with scrolling the mouse... it's also like that in sm one. in diva (for example) it's different and correct for me.

[kv331]

do you mean in the mac os settings (can't find this in SM2)?

Here it is for SM3:

settings 1.jpg

settings 2.jpg

[Milkman]

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) .

To end this discussion, indeed.

MANY people have complained about this modwheel issue over numerous years, Ive already described how it happens on ANY DAW, on ANY controller, on ANY machine, and yet you reply as if this isnt the case or that I've said something else.

I am a 30+ year net/sysadmin, I have 1000s+ of other plugins that have zero trouble with modwheel/CC1, and for you to "close" the discussion by denying all of this... lmao! Ok then. Good luck selling your software. I think I understand this just fine.

[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.

Modwheel works fine here with SM2. Has always worked fine in every version of Cubase that i used it with (now in C13), plus with any synth and/or controller that i used over the years.

You don't have to midi learn anything. Just assign anything in SM2 to the modwheel and it'll work.

Oh, really. This is becoming ridiculous.

lol Ive tested this on cubase 10.5, 11, 12, 12.0.80. It is EXACTLY the same on all versions, and if you try to assign modwheel to anything, SM2 crashes. I reported this to the dev 18+ months ago and they ignored it, then denied it.

Win10. Freshly built machines including desktop, laptop, older desktop. Focusrite 18i20 interface. Any controller or keyboard I use - all 6 of mine from novation, korg, arturia, akai do not work, but you are saying it does work. In cubase. Trying to bind the modwheel to anything inside SM2 results in a program crash. In Live. In Cubase. In Bitwig (4 and now 5), but no -- it didnt happen to you?

Something is very strange here.

[DarkS474]

Why did you change the selling policy for Synthmaster 3 ? It was clearly stated that Synthmaster 2 license was included but it's not being added to customers accounts.
I received an email a few days ago from your servers in which it was clearly written that Synthmaster 2 license was included with a purchase of Synthmaster 3.
I got the Synthmaster 3 upgrade from Synthmaster 2 Player but the Synthmaster 2 license was not added to my account at all.

This is what you wrote in the e-mails you sent to your customers:

synth3-email0.PNG

A friend of mine purchased Synthmaster 3 directly and the Synthmaster 2 license is not included either.
And on your website too you removed the "Synthmaster 2 license is included" text that was there when I purchased my upgrade like it was on the email I received.
This really is a very bad marketing move.
It was a good thing to give Synthmaster 2 to Synthmaster 3 Alpha/Beta early-adoption customers obviously. Even because Synthmaster 3 Alpha and Beta don't have any presets and you will add them in the following weeks.
As it was a wise decision to give a Synthmaster 2 license included with Synthmaster 3 to let customers use your current stable product it then became a really unwise and bad decision to change that all of a sudden and not giving the Sythmaster 2 license anymore.
What are you trying to achieve doing that I really don't get it... you are just alienating your new customers this way.
My friend is really disappointed, way more than me.
Even with the discount new customers this way are paying an higher price anyway for a still unstable unfinished product without receiving the current usable product. Do you think that this way people would just pay for a Synthmaster 2 license ?
You are thinking wrong.
When Synthmaster 3 is complete there is no need to use Synthmaster 2 clearly. And Synthmaster 2 expansions can be purchased and used with Synthmaster 3 anyway.. so what are you so concerned about by not giving with Synthmaster 3 a license for Synthmaster 2 as you previously stated on your emails to customers like me and as it was clearly written on your website ?
The only thing Synthmaster 3 customers would be missing then would be the included presets in Synthmaster 2 this way. But why ? Why is it like that at all ? You can still sell them all the Synthmaster 2 Expansions.
When any business writes something to its customers and then changes things and doesn't give what it promised to be included in the purchases it surely is the worst advertising possible indeed.
You surely should re-think your strategy about this and give a Synthmaster 2 license to all your Synthmaster 3 customers as you previously stated instead of removing the text on your website and thinking that customers like me wouldn't notice what you wrote on the emails you sent back then and so it wouldn't matter.
Leaving Synthmaster 3 customers to just wait until the end of March for the final release of the product without giving a Synthmaster 2 license anymore as you previously promised is the worst way to collect money for the development of any product. You previously stated that a Synthmaster 2 license was included with any purchase of Synthmaster 3 and that is what you should have done and what you still should do.

[kv331]

Why did you change the selling policy for Synthmaster 3 ? It was clearly stated that Synthmaster 2 license was included but it's not being added to customers accounts.

We did not change anything. What are you talking about

Please remove your post because that IS false information.

Here's the automated email we send to new SynthMaster 3 users:

Mon, Jan 1, 10:26 AM (5 days ago)

Dear xxx yyy,

Thank you for purchasing SynthMaster 2 and SynthMaster 3. The serial number for your copy of SynthMaster 3 is

zzz

By using this serial number along with your registered e-mail address, you can log on to your account to download the latest versions of SynthMaster 2 and SynthMaster 3 at:

https://www.synthmaster.com/userarea.as ... Number=zzz

After downloading the setup files, please run them. The setup will install all the necessary files to run SynthMaster 2/ 3 as a VST/AU/AAX plugin inside your DAW.

When you run SynthMaster 2 or SynthMaster 3 for the first time, License Key File Request Dialog will show up. You will have to enter your email address and serial number to download your license key file. If your computer is offline, you can request your license key file at: https://www.synthmaster.com/requestlicensefile.aspx from an online computer.

[DarkS474]

I didn't say anything false.
You should fix users accounts missing the license files for Synthmaster 2 then if you didn't change anything. And your support team should reply accordingly instead of telling that Synthmaster 2 is not included.
I replied to you by PM.

[mpaech]

Zitat: "Fri Jan 05, 2024 7:32 am
ReverendLove wrote: ↑Thu Jan 04, 2024 11:04 pm
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."

Habe auch das Problem, das auf einem PC SM3 sowohl als VST2 wie auch VST3 von Cubase als 32-bit Programm erkannt und daher nicht geladen wird. Könnte es sein, das die komplette Deinstallation von SM2 mit anschließender Installation von SM3 und anschließend SM2.9.16 mir auch helfen könnte? Steinberg hat zwar ein Ticket zum Thema eröffnet, aber nach 6 Tagen immer noch keine Anwort geschrieben.

I also have the problem that on a PC SM3 is recognized as both VST2 and VST3 by Cubase as a 32-bit program and is therefore not loaded. Could it be that completely uninstalling SM2 followed by installing SM3 and then SM2.9.16 could also help me? Steinberg opened a ticket on the topic, but after 6 days he still hasn't responded.

Die oben beschriebene Vorgehensweise hat bei mir leider nicht funktioniert, da SM3 die Registrierungsdatei von SM2 benötigt. Habe SM2 erneut installiert, danach SM3. Leider stürzt Cubase Artist 11 beim Laden von SM3 ab, ab nur auf einem meiner beiden Musik-PC. Heißt also warten, bis Steinberg das Ticket bearbeitet hat.

Unfortunately, the procedure described above did not work for me because SM3 requires the registration file from SM2. I installed SM2 again, then SM3. Unfortunately, Cubase Artist 11 crashes when loading SM3, only on one of my two music PCs. So that means waiting until Steinberg has processed the ticket.

[hurricaneaudiolab]

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

Forgive me, but I don't understand how to disable the effects globally so that as I switch from preset to preset, every preset would be dry. I want to disable the effects completely across every patch. I tried the layer lock, but when I switch presets it gets reset. For example, in DIVA, you turn off the effects and can lock them so they stay turned off permanently.

EDIT: I mean on the BUS 1 BUS 2 sections. Those keep unlocking on me as I switch through presets.

[Hanz Meyzer]

Guys, can you please calm down a bit and discuss in a friendly manner?

@kv331 Tried modwheel now on my macos 12 system and VST3:
- Works fine in Renoise and Live, both SM2/SM3 VST2 and VST3
- Does not work in Bitwig, neither SM2 VST3, nor SM3 VST3
- Does work in Bitwig with any other VST3 synth

So I would suggest that you could contact Bitwig support (support at bitwig), so you seem to have implemented something differently here. Obviously the problem seems to be in the code of SM2 and SM3 though. Or maybe the other devs know about some specific workaround needed in Bitwig... Might be a good question at dev forum here? Could this be MPE related somehow, so SM receives modwheel on the wrong channel?

There also is a midi monitor controller script (MOSS), which displays the received midi messages in the extensions console (set a shortcut) that Bitwig receives: I just looked at it and clearly it receives modwheel CC#01 data.

[VELLTONE MUSIC]

Start to understand why developers are so hostile sometimes - with so many complains and requests man need to have nerves of steel,not to react and to answer with similar tone hahaha
If you have account already,log in,buy the sm3 upgrade and immediately it will be available for download.
Anayway leave the man to work on sm3 development,i've never had any issue with the account and the downloads,despite i had some constructive critisism on fx and some functions as designer,but all constant complains are not helpful to development of sm3.
Don't want sm3 development to be abandoned,cause the developer is so mad to all critics he prefer to leave the business,instead of listening all over and over again,like some already did.
If i have to express my personal feelings to Bulent and kv331 attitude to my work, will be 24/7 negativism,but their synths are really dope,can't find serious replacement, so i stopped taking it personally and sm3 seems to be even better synth,so give the man time to make all the stuff right,no need of rush and nerves,we are all just human beings,not machines.
Cheers

[eagle007]

Modwheel is working and has been working fine for me in Studio One on MacOS, with versions 2.7 up to 2.98. With 4 different controllers. Arturia, M-Audio, Novation and Roland.

The only issue I have in version 2, which is really annoying and I do not seem to be able to fix is that all my presets pop up twice. Each and every one is listed on 2 rows and if I click the 2nd one it jumps to the 1st. The 1st one I can click to load.