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

[kv331]

hey Bulent is CPU bug that was introduced few updates ago has been fixed?

Hi there

I am currently comparing SM2 SM3 differences by loading the preset you mentioned:

Lead Another SuperSaw AZ

There is indeed a big difference in CPU usage. Fixed now.

EDIT: The root cause of the issue was in the release x64 build settings on Windows VST2 build. Optimizations were turned off for this build, since January 1. I turned them back on, the results are now similar:

sm2 sm3 compare.jpg

[kv331]

Hi guys,

Here's SynthMaster 3.2 Beta (v3.2.0). This update has 2 new important features:

1. We are supporting PlugInBoutique's "rent to own" system now.
2. You can now preview preset banks that you don't own, right within the preset browser.

preset preview last.jpg

There are also critical bug fixes:

1. SynthMaster 3 might crash when initializing a preset that had parameters midi learned previously
2. SynthMaster 3 crashes when more than 8 simultaneous regions play on a multisample
3. SynthMaster 3 doesn't recognize 'key' token in sfz files
4. SynthMaster 3 crashes when user selects a sample/multisample from the waveform browser window, and then double clicks on the osc waveform view
5. SynthMaster 3 skin fonts are not installed correctly on MacOS
6. SynthMaster 3 Windows VST2 build is not compiled with optimizations

This update is not officially released yet, so I am posting dropbox links:

Windows update: https://www.dropbox.com/scl/fi/2p117zap ... 3lk56&dl=0
MacOS update: https://www.dropbox.com/scl/fi/p0p5j95c ... ybp8f&dl=0

[audiojunkie]

Hi guys, we're trying to understand how important presets are in your music production workflow. Do you use them, or just design your own sounds? I am considering adding a "Preview" button to the preset browser tab, so that when you click on it, you would see the banks that you don't own and you can audition the presets in the bank(s) by moving the mouse over the Play icon next to the preset name. Do you think this would be a useful feature? Please comment, thanks!


bank preview.png


I am also reworking on the feature set for SynthMaster 3 Player, and hoping to add more editing features in it: The tab view is not available, so you can not add/remove modules, but the track view & mix view are still available, so that you can change the parameters in those parts.

Good presets are important to me, as long as I can favorite them and quickly and easily see my favorites.

[audiojunkie]

Good presets are important to me.
As I just bought the All pack the PREVIEW is not relevant to me. But I like the feature.

Tweaker here, too. I mostly work offline, so I would like to be left alone by shopping and convenience features.

Maybe the shopping features can be cleanly hidden away unless users want to browse them? I wouldn't want to see them every time I open the synth, but I would love to have the features in there for when I want to shop for presets.

[audiojunkie]

Hi guys, update on the "Expansion Preview" implementation: Added a new button next to Local & Online called Preview. When you click on it, SM3 displays the expansion banks that you don't have a license for. (If the audio previews are not installed, SM3 will ask at this point to download the missing ones, and will download once you confirm). Then, it displays the preset names and metadata for that bank. You can move the mouse over the play icon(s) for each preset, and you can listen to the audio preview. Mouse click doesn't work on the previews so there's no way to load them


preset preview 2.jpg


Does this sound good? I am also considering adding a Shop icon next to the bank name, so that if you liked the bank, you can click on the Shop icon and you are directed to our expansions page.

Oh! This is perfect!! Hidden away just enough, yet close by when needed! Well done!

[audiojunkie]

If the preview-and-buy isn't intrusive, I have nothing against it. But like others, overshoppifying can make a plugin feel annoying.
If it is implemented non-annoying and optional, I like the idea to preview presets I don't own in context.

No it's not intrusive. Unless you click on the "Preview" button, you don't see/audition the banks that you don't own:


preset preview 3.jpg


If you click on the play icon next to the bank name, you would be directed to our SoundCloud page for the expansion:


preset preview soundcloud.jpg


If you click on the shop icon next to the bank name, you would be directed to our purchase page (it's work in progress, should be live tomorrow)


preset preview shop.jpg

Will the presets that a person owns be able to be downloaded and archieved along with the installer and the serial number?

[kv331]

Will the presets that a person owns be able to be downloaded and archieved along with the installer and the serial number?

Expansions are downloaded through the plugin. They are saved under:

Win: c:\users\public\public documents\synthmaster3\presets
Mac: /users/shared/synthmaster3/presets

You can backup this folder yourself, along with

my documents/synthmaster3 (this is where user data + license key file resides)

[KTlin]

There is a very nasty bug in the Slice mode of SM3: the sound gets extremely loud and distorted when using the Slice mode. Fortunately the limiter was enabled otherwise it could have damaged my speakers. And there are other issues with the Slice mode, not just this one. I've just recorded a video demonstrating all those problems and I'll send it to you by email.

[kv331]

There is a very nasty bug in the Slice mode of SM3: the sound gets extremely loud and distorted when using the Slice mode. Fortunately the limiter was enabled otherwise it could have damaged my speakers. And there are other issues with the Slice mode, not just this one. I've just recorded a video demonstrating all those problems and I'll send it to you by email.

I will look into the loud burst. But other than that, Slice mode is used to slice & play loops. In your video, you used a single note decaying guitar sample. That's not what slice mode is for

[Hanz Meyzer]

Is that idea to put multiple OSCs next to each other in the GUI still a topic? Can't find the original post anymore, but I really like the idea!

[kv331]

Is that idea to put multiple OSCs next to each other in the GUI still a topic? Can't find the original post anymore, but I really like the idea!

The idea is to have multiple interface sizes for each module, such as: Minimized, Normal, Maximized. This way, we can fit multiple modules on the screen.

[KTlin]

There is a very nasty bug in the Slice mode of SM3: the sound gets extremely loud and distorted when using the Slice mode. Fortunately the limiter was enabled otherwise it could have damaged my speakers. And there are other issues with the Slice mode, not just this one. I've just recorded a video demonstrating all those problems and I'll send it to you by email.

I will look into the loud burst. But other than that, Slice mode is used to slice & play loops. In your video, you used a single note decaying guitar sample. That's not what slice mode is for

You're focusing on the wrong thing mate (and it sounds a little bit like blame shifting to be honest). The type of sound I used for demonstrating that bug is not the problem in this case, it's completely irrelevant. The problem is the very nasty bug that produce an extremely loud burst that could potentially cause damage to the user's speakers and being such a serious issue with real world consequences it should have been fixed a long time ago, in the beta stage, not almost one year after the official release. And by the way, Serum 2 was released 3 weeks ago and after playing with it for a couple of days I encountered ZERO bugs or issues while SM3 which was released almost one year ago! still has bugs, issues and half-baked features (as demonstrated by this 100 pages-long thread full of bug reports) which makes us, the users/customers, some sort of perpetual beta testers. And that's not ok!

Also, it's not up to the software developer to tell the user what kind of sample he/she should use or should not use with the Slice mode. "Slice mode is used to slice & play loops" . Really? What if I want to slice and play anything other than "loops"? What if I want to slice and play a field recording, or a voice recording, or a long and fluctuating drone sound, or maybe a monkey's fart if I'm feeling adventurous? Should I be able to experiment with anything other than "loops" in the slice mode? Yes! Should your synth be capable of slicing anything other than "loops"? Yes! Should it produce extremely loud bursts? No! Should it produce clicks at the beginning of every slice as I demonstrated in that video? No! Should it produce gaps in the playback when playing the slices one after the other as I demonstrated in that video? No! So, in conclusion, the problem was not my use of a "single note decaying guitar sample", the problem is the buggy implementation of the slice mode in your software.

[Examigan]

There is a very nasty bug in the Slice mode of SM3: the sound gets extremely loud and distorted when using the Slice mode. Fortunately the limiter was enabled otherwise it could have damaged my speakers. And there are other issues with the Slice mode, not just this one. I've just recorded a video demonstrating all those problems and I'll send it to you by email.

I will look into the loud burst. But other than that, Slice mode is used to slice & play loops. In your video, you used a single note decaying guitar sample. That's not what slice mode is for

I hate to admit it, but I haven't even used Slice mode yet. I can try to duplicate the steps and see what happens on my system, but I wasn't sure how to set it up.

Is that in one of the help files in a module somewhere?

[KTlin]

Is that in one of the help files in a module somewhere?

Nope, there's no help file for the Slice mode (or for the entire Sample Editor for that matter) as there's still no user manual for the SM3 almost one year since the official release.

[kv331]

The problem is the very nasty bug that produce an extremely loud burst that could potentially cause damage to the user's speakers and being such a serious issue with real world consequences it should have been fixed a long time ago, in the beta stage, not almost one year after the official release.

After watching your video, I tried to reproduce the issue, but still can't. I tested with User mode, grid mode, added/removed slices but no way. The sample played fine.

EDIT: After changing the engine quality to a value higher than Draft, I can reproduce the issue. FIXED the issue. Will be released tonight