SynthMaster 3 Official Thread: SynthMaster 3/Player v3.4.9 Rev 17271 update

[kv331]

Argh, thanks Bulent, sorry for wasting your time! I've been through this before I think.

No worries. As I wrote before, the end goal is to be able to connect anything to anything

I think I can add Mono2Stereo, Stereo2Mono modules which would let us connect oscillators to oscillators.

[audiojunkie]

Argh, thanks Bulent, sorry for wasting your time! I've been through this before I think.

No worries. As I wrote before, the end goal is to be able to connect anything to anything

I think I can add Mono2Stereo, Stereo2Mono modules which would let us connect oscillators to oscillators.

Anything to anything is such a powerful concept! Synthmaster 3 is essentially a 16 layer modular synth! So cool!

[swilow11]

Decided to give SM3 another go. Basically the first instance I opened and tried to resize by dragging out a corner simply extended sort of blank underlay while the synth stayed the same. Than Bitwig crashed (hung audio). Maybe I am just being naive but this is easily the buggiest synth I've ever used. Even just rescanning my plugin folder causes Bitwig to get stuck on SM3. It is an amazingly powerful synth and basically usable but no other synth I have is as problematic. Still hoping for a fully stable release but it's been months since release so I'm not holding my breath.

[digitalboytn]

No worries. As I wrote before, the end goal is to be able to connect anything to anything

That's great news...

So can you please make the info pane at the centre/top wider please ?

SM2 was the perfect size, but ATM in SM3, a lot of the info is cut off because the pane is too small...

There's plenty of room up there to make it wider and those HUGE arrows could be shrunk.

That way,we could connect our eyes to the patch information that was written in SM1 & SM2

And that's the goal here...

Thanks for that....it is appreciated

[kv331]

Decided to give SM3 another go. Basically the first instance I opened and tried to resize by dragging out a corner simply extended sort of blank underlay while the synth stayed the same. Than Bitwig crashed (hung audio). Maybe I am just being naive but this is easily the buggiest synth I've ever used. Even just rescanning my plugin folder causes Bitwig to get stuck on SM3. It is an amazingly powerful synth and basically usable but no other synth I have is as problematic. Still hoping for a fully stable release but it's been months since release so I'm not holding my breath.

I tested with Bigwig on both Windows and MacOS, BUT I CAN NOT REPRODUCE THIS SCENARIO.. I resize the UI, and even played a midi track to make it a scenario with multiple threads running, but no luck. It works as expected.

As the developer, I need an reproduceable scenario to be able to fix user issues.

I see that you are constantly making negative comments for my product, -which I believe is unfair-, could I at least ask for the log files so that I try to understand what is wrong with your configuration ?

The logs are located at:

Win: c:/users/public/public documents/synthmaster3/logs
Mac: /users/shared/synthmaster3/logs

You can email me at: bulentbiyikoglu AT kv331audio DOT com

[Examigan]

Decided to give SM3 another go. Basically the first instance I opened and tried to resize by dragging out a corner simply extended sort of blank underlay while the synth stayed the same. Than Bitwig crashed (hung audio). Maybe I am just being naive but this is easily the buggiest synth I've ever used. Even just rescanning my plugin folder causes Bitwig to get stuck on SM3. It is an amazingly powerful synth and basically usable but no other synth I have is as problematic. Still hoping for a fully stable release but it's been months since release so I'm not holding my breath.

I tested with Bigwig on both Windows and MacOS, BUT I CAN NOT REPRODUCE THIS SCENARIO.. I resize the UI, and even played a midi track to make it a scenario with multiple threads running, but no luck. It works as expected.

As the developer, I need an reproduceable scenario to be able to fix user issues.

I see that you are constantly making negative comments for my product, -which I believe is unfair-, could I at least ask for the log files so that I try to understand what is wrong with your configuration ?

The logs are located at:

Win: c:/users/public/public documents/synthmaster3/logs
Mac: /users/shared/synthmaster3/logs

You can email me at: bulentbiyikoglu AT kv331audio DOT com

The log files I sent to Bulent helped fix an issue I was having, so I recommend it as well.

[VELLTONE MUSIC]

Everything is working fine,just can't find any skin change option ...

Did you watch our "What's New in SynthMaster 3.3" video?


Change Skin.jpg

Not yet,will watch it now.
Hope just some changes i am not aware,don't want to reinstall everything.
Don't have such menu,just green skin.
Grey/Black/White is dope as color combination.
Cheers

[kv331]

Don't have such menu,just green skin.

Screenshot 2025-05-25 at 18.28.55.png

[Charlie Firpo]

Hello Bulent! I got a crash in Renoise/Win10 doing this:
1) Init patch
2) Add Step Lfo
3) Set nr of steps to 3
4) Open the step lfo's own edit window
5) Select edit mode: steps
6) Left click on the first step = Crasch

[Examigan]

Hello Bulent! I got a crash in Renoise/Win10 doing this:
1) Init patch
2) Add Step Lfo
3) Set nr of steps to 3
4) Open the step lfo's own edit window
5) Select edit mode: steps
6) Left click on the first step = Crasch

That worked ok for me with the latest version of SM3 - no crash. I checked VST2 and VST3 versions.
Using Cakewalk and Win10 here.

[Charlie Firpo]

Hello Bulent! I got a crash in Renoise/Win10 doing this:
1) Init patch
2) Add Step Lfo
3) Set nr of steps to 3
4) Open the step lfo's own edit window
5) Select edit mode: steps
6) Left click on the first step = Crasch

That worked ok for me with the latest version of SM3 - no crash. I checked VST2 and VST3 versions.
Using Cakewalk and Win10 here.

Yeah, i've done it a couple of times now and it's not 100% reproducible everytime. If it doesn't crash i may have to clear the instrument and load a fresh instance in Renoise and do the steps above again.

However i noticed one thing: I can see when it's going to crash looking at the mouse pointer graphics. When selecting "edit mode" the cursor graphic changes to one arrow pointing left and right. If the cursor graphic dont change back to the usual windows "point upwards" cursor when i move it to the steps window, it's going to crash when using leftclick.

[kv331]

Yeah, i've done it a couple of times now and it's not 100% reproducible everytime. If it doesn't crash i may have to clear the instrument and load a fresh instance in Renoise and do the steps above again.

Hi Charlie

I was able to reproduce the issue after turning on "Address Sanitizer" in Xcode (My development tool on MacOS). Looks like the issue was happening as Loop Start > Number Of Steps. So I changed the code so that Loop Start is always smaller or equal to Number Of Steps.

I will release an update shortly.

Thanks for the bug report!

Cheers

[kv331]

Here's an unofficial release for v3.3.2 on dropbox. The installers are not signed/notarized yet:

Mac: https://www.dropbox.com/scl/fi/sf0q96e8 ... wuk9i&dl=0

Win: https://www.dropbox.com/scl/fi/9qixklnf ... dogmc&dl=0

Changelog:

1. FIX: Skins are not up to date on MacOS setups
2. FIX: SynthMaster 3 might crash when loading a SM2 preset with custom wavetable
3. FIX: Floating windows are clipped on Windows
4. FIX: Windows Standalone doesn't resize plugin window correctly when the current skin changes
5. FIX: SynthMaster 3 crashes when a modulator is connected to another one with self feedback
6. FIX: SynthMaster 3 might crash when Step LFO Loop Start value is greater than Number Of Steps

[Examigan]

Yeah, i've done it a couple of times now and it's not 100% reproducible everytime. If it doesn't crash i may have to clear the instrument and load a fresh instance in Renoise and do the steps above again.

Hi Charlie

I was able to reproduce the issue after turning on "Address Sanitizer" in Xcode (My development tool on MacOS). Looks like the issue was happening as Loop Start > Number Of Steps. So I changed the code so that Loop Start is always smaller or equal to Number Of Steps.

I will release an update shortly.

Thanks for the bug report!

Cheers

That works for the Windows version also?

[kv331]

Yeah, i've done it a couple of times now and it's not 100% reproducible everytime. If it doesn't crash i may have to clear the instrument and load a fresh instance in Renoise and do the steps above again.

Hi Charlie

I was able to reproduce the issue after turning on "Address Sanitizer" in Xcode (My development tool on MacOS). Looks like the issue was happening as Loop Start > Number Of Steps. So I changed the code so that Loop Start is always smaller or equal to Number Of Steps.

I will release an update shortly.

Thanks for the bug report!

Cheers

That works for the Windows version also?

Yep