The Synthmaster 3 Thread

[neverbeeninariot]

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.

Quite so.

I did some limited testing here this morning, for what it's worth...

- PC: i7 4790 (stock) running Win10 (my primary DAW machine with years of accumulated sh*te installed)
- Interface: Scarlett 18i20 / ASIO
- DAWs: Bitwig 5, Cubase 11, Live 11, and Reaper 7 (all at the latest point release for those versions).
- Controllers: Korg padKontrol, Nektar LX, and Novation SL Mk II (all connected via USB)
- SM2 and SM3, both VST3 (I don't have the VST2 versions installed)

Assigning the modwheel to multiple random parameters on an init patch.

Cubase, Live and Reaper
Modwheel (cc1) works as expected.

Bitwig
Modwheel (cc1) is not recognised by either SM2 or SM3
If I insert the Bitwig MIDI Note FX as a modulater and map cc1 (default cc in the Note FX) to cc1 in SM2/SM3 then it works.

I tested a few other VST3 synths in Bitwig (Twin3, Phase Plant, Bazille, and Pigments), the modwheel (cc1) works for them all without requiring the MIDI Note FX.

So there is /something/ not right with SM's cc handling in Bitwig.

As for the crashing... I tried to crash SM2/3 by assigning the modwheel to multiple random parameters (just whatever fell under the mouse...), but it's solid in any (tested) DAW, for me.

When it crashes for you, does it take the DAW with it or is it just SM crashing?
If the DAW crashes, are there any Windows crash dumps that could be analysed to find out what is happening? Does your DAW generate logs that might provide useful info?

@kv331 - does SM generate logs? I searched but couldn't find any.

[kv331]

Bitwig
Modwheel (cc1) is not recognised by either SM2 or SM3

Just got an answer from Alexandre @ BitWig, apparently I wasn't supposed to mark MIDI CC parameters as "automateable", YAY This should fix the issue

[neverbeeninariot]

Bitwig
Modwheel (cc1) is not recognised by either SM2 or SM3

Just got an answer from Alexandre @ BitWig, apparently I wasn't supposed to mark MIDI CC parameters as "automateable", YAY This should fix the issue

Nice ! :~)

[DarkS474]

A Synthmaster 2 license now has been added to my account.
I guess all Synthmaster 3 customers missing the license are now receiving it.
Thank You for fixing the issue then.

[kv331]

A Synthmaster 2 license now has been added to my account.
I guess all Synthmaster 3 customers missing the license are now receiving it.
Thank You for fixing the issue then.

You are very welcome. I apologize for the confusion. We fixed the "request license key" page on our website and also the email license key dialog functionality. I also updated the SM3 web page and wrote clearly that SM3 includes a license for SM2.

[KTlin]

Bitwig
Modwheel (cc1) is not recognised by either SM2 or SM3

Just got an answer from Alexandre @ BitWig, apparently I wasn't supposed to mark MIDI CC parameters as "automateable", YAY This should fix the issue

Happy to hear that!

[hurricaneaudiolab]

Hey there - so if indeed the BUS section can't be globally locked, then I would like to suggest to address that in SM3. Or give us some way to completely disable all effects globally and permanently.

[teilo]

I also have zero issues using CC1 with the VST2 of SM2 and SM3 in Bitwig. That said, I always default to VST2, so didn't run into the VST3 issue (though I can confirm it). Glad you got to the bottom of it, Bulent. And also: you have the patience of a saint.

[Milkman]

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.

Quite so.

I did some limited testing here this morning, for what it's worth...

- PC: i7 4790 (stock) running Win10 (my primary DAW machine with years of accumulated sh*te installed)
- Interface: Scarlett 18i20 / ASIO
- DAWs: Bitwig 5, Cubase 11, Live 11, and Reaper 7 (all at the latest point release for those versions).
- Controllers: Korg padKontrol, Nektar LX, and Novation SL Mk II (all connected via USB)
- SM2 and SM3, both VST3 (I don't have the VST2 versions installed)

Assigning the modwheel to multiple random parameters on an init patch.

Cubase, Live and Reaper
Modwheel (cc1) works as expected.

Bitwig
Modwheel (cc1) is not recognised by either SM2 or SM3
If I insert the Bitwig MIDI Note FX as a modulater and map cc1 (default cc in the Note FX) to cc1 in SM2/SM3 then it works.

I tested a few other VST3 synths in Bitwig (Twin3, Phase Plant, Bazille, and Pigments), the modwheel (cc1) works for them all without requiring the MIDI Note FX.

So there is /something/ not right with SM's cc handling in Bitwig.

As for the crashing... I tried to crash SM2/3 by assigning the modwheel to multiple random parameters (just whatever fell under the mouse...), but it's solid in any (tested) DAW, for me.

When it crashes for you, does it take the DAW with it or is it just SM crashing?
If the DAW crashes, are there any Windows crash dumps that could be analysed to find out what is happening? Does your DAW generate logs that might provide useful info?

@kv331 - does SM generate logs? I searched but couldn't find any.

As I told the dev over 18 months ago, the first time I worked on troubleshooting this, this was CUBASE 10.5, then 11, then 12. SM2 crashed within cubase.

Then, years later, I bought a Bitwig license and the same issue exists there. This was CUBASE, first, then Bitwig much later. I see the dev moving toward blaming Bitwig for this issue and Im not here for it. I also see the dev now offering an "oopsie" about coding something wrong "for bitwig"? lol this is only about Bitwig (for me) in the last few months.

1000s of other FX, instruments work perfectly in this environment, including cubase. Blaming the environment, rather than addressing the narrow issue within this software, isnt a good look.

[Milkman]

I also have zero issues using CC1 with the VST2 of SM2 and SM3 in Bitwig. That said, I always default to VST2, so didn't run into the VST3 issue (though I can confirm it). Glad you got to the bottom of it, Bulent. And also: you have the patience of a saint.

Perhaps the dev should notate that VST3 is not supported by SM? I try to use VST3 whenever possible, and would not know if the VST3 implementation of SM1, 2, or 3... is broken unless the dev explained this to me many months ago. So the VST3 implementation is broken, or "its bitwig's fault"? Hard to really understand.

[teilo]

1000s of other FX, instruments work perfectly in this environment, including cubase. Blaming the environment, rather than addressing the narrow issue within this software, isnt a good look.

When you are a plugin developer, with years of experience under your belt navigating the mine field of idiosyncratic plugin implementations across multiple DAWs and OS platforms, and thus can speak from experience, we will take your outrage more seriously.

Bulent acknowledged the issue was with SM, and is fixing it. You got what you want.

[kv331]

I also see the dev now offering an "oopsie" about coding something wrong "for bitwig"? lol this is only about Bitwig (for me) in the last few months.

1000s of other FX, instruments work perfectly in this environment, including cubase. Blaming the environment, rather than addressing the narrow issue within this software, isnt a good look.

Don't try to teach me my job VST3 is a standard created by Steinberg. and as a developer I follow their guidelines. Just today, I learned that, to be compatible with Bitwig, I need to set MIDI CC parameters as "not automateable". Other hosts do not require that.

[Milkman]

1000s of other FX, instruments work perfectly in this environment, including cubase. Blaming the environment, rather than addressing the narrow issue within this software, isnt a good look.

When you are a plugin developer, with years of experience under your belt navigating the mine field of idiosyncratic plugin implementations across multiple DAWs and OS platforms, and thus can speak from experience, we will take your outrage more seriously.

Bulent acknowledged the issue was with SM, and is fixing it. You got what you want.

My outrage? This isnt really a hill you want to die on, but ok. Dont try to miscategorize my frustration as "outrage" -- this is about respectful customer service and honesty, and I dont need your thoughts on my client/vendor situation. If you cant help with the situation, dont bother me.

[Milkman]

I also see the dev now offering an "oopsie" about coding something wrong "for bitwig"? lol this is only about Bitwig (for me) in the last few months.

1000s of other FX, instruments work perfectly in this environment, including cubase. Blaming the environment, rather than addressing the narrow issue within this software, isnt a good look.

Don't try to teach me my job VST3 is a standard created by Steinberg. and as a developer I follow their guidelines. Just today, I learned that, to be compatible with Bitwig, I need to set MIDI CC parameters as "not automateable". Other hosts do not require that.

I reached out to your company for help for close to TWO YEARS and got none, and you can find many of my comments and posts asking for help about this. FOR SM2 modwheel issue in CUBASE. Then you claim "its bitwig", close to 2 years after this.

If you cant understand my frustration at this, perhaps you shouldnt be a developer.

[teilo]

1000s of other FX, instruments work perfectly in this environment, including cubase. Blaming the environment, rather than addressing the narrow issue within this software, isnt a good look.

When you are a plugin developer, with years of experience under your belt navigating the mine field of idiosyncratic plugin implementations across multiple DAWs and OS platforms, and thus can speak from experience, we will take your outrage more seriously.

Bulent acknowledged the issue was with SM, and is fixing it. You got what you want.

My outrage? This isnt really a hill you want to die on, but ok. Dont try to miscategorize my frustration as "outrage" -- this is about respectful customer service and honesty, and I dont need your thoughts on my client/vendor situation. If you cant help with the situation, dont bother me.

The only help you need is holding your tongue. You got what you wanted. Problem solved. Happy now? Or will you insist on dragging this out further for some personal reason I'd rather not speculate about?