The Synthmaster 3 Thread

[kv331]

Does the Everything Bundle include all the future Synthmaster 3 expansions?

Yes. (Our policy is adjust the price of Everything Bundle from time to time after we add new expansions)

[aMUSEd]

Before I update can I check if the NKS have been updated to work with Synthmaster 3 or should I wait? Also if it can load Synthmaster One patches does that mean I no longer need One?

[eagle007]

$54 ? How? There is a $49 coupon in my account. But if I try to add that to the upgrade price it switches to the full price before adding the coupon, ending up at $90

You probably tried to purchase an upgrade product. As we state in the email we sent out for the credit coupon:

Just so you know, this coupon can only be used towards purchasing the full product, it doesn't apply to upgrades/crossgrades from other products

Yes, I did notice that. But without the coupon it is $109, so not anywhere near $54 either.

[teilo]

In the current list of preset templates, DX7 algorithms 3-9 are missing. #5 is especially important since it is the most used algorithm in classic patches.

[kv331]

In the current list of preset templates, DX7 algorithms 3-9 are missing. #5 is especially important since it is the most used algorithm in classic patches.

Actually all of the algorithms are in there. The problem is those presets you mentioned were not tagged with "Template" tag. Fixed it now.

[Lbdunequest]

Ill be very bold now...the idea behind the synth is great but not having a pretty looking GUI at first makes me loose the interest in even trying the alpha version. I think in the market of today GUI which is a huge part of workflow and usability which is probably 70% of the synth.

And id think its better to focus on that aspect now and do the ugly looking plugin testing inside the company.

[KTlin]

Ill be very bold now...the idea behind the synth is great but not having a pretty looking GUI at first makes me loose the interest in even trying the alpha version. I think in the market of today GUI which is a huge part of workflow and usability which is probably 70% of the synth.
And id think its better to focus on that aspect now and do the ugly looking plugin testing inside the company.

The current GUI is indeed ugly and uninspiring but it was already mentioned here a number of times that this is just a prototype GUI. So it shouldn't stop you from trying/testing all the features.

[medienhexer]

You can‘t win with the average consumer as a developer. If you include users in alpha version testing, they will complain that it‘s not feature complete. Yes, that is what alpha versions are.

If you only let them look at beta versions, they will flood you with new feature requests and changes to the workflow. Well, too late for that, we‘re only trying to fix bugs at this point. The features are done. Most changes now will break things and/or cost a lot of time and money for GUI designers. It‘s definitely too late to change anything fundamental.

And if you only show the finished product, people will go back to the absolute start of development. Why do you have all those features nobody needs but none of the features I WANT? I don‘t like the sound. I have enough synths which do the same. You didn‘t invent a completely new form of synthesis. You didn‘t revolutionize the field of workflow.

Don‘t get me wrong, the UI and aspects like signal flow, grouping of elements, contrast, sharpness, size, readability have been weak spots in the past. And will hopefully be solved.

But if you are uncomfortable with an unfinished product, don‘t try an alpha version. You will be disappointed. Things require your imagination sometimes, because they are not done. Things will not work correctly at times. You may not be able to open your projects with the final release version. Things may sound differently. You may not be able to open presets you create.

[teilo]

In the current list of preset templates, DX7 algorithms 3-9 are missing. #5 is especially important since it is the most used algorithm in classic patches.

Actually all of the algorithms are in there. The problem is those presets you mentioned were not tagged with "Template" tag. Fixed it now.

Excellent. Thanks!

By the way, the work you are doing here is amazing. I realize the UI is not final, but already it's one of the more straightforward UIs for modular patch design that I've seen. Your recent video covering the changes was extremely helpful. You are pushing into Falcon / Halion territory here, but with a much more intuitive UI.

[DazzW]

I've bought everything separately so I wouldn't get anything new by purchasing the everything bundle. Is there any way of you confirming this and registering me as an "everything" user so I can get the demo and upgrade?

Can you please PM me your registered email address? We recently sent out Everything Bundle upgrade coupons to our users. Have you received it ?

I sent you a PM last week but it doesn't look like you've seen it yet. I got the coupon for the Everything Bundle upgrade but I've already bought everything separately so my question is does this qualify me for the v3 upgrade?

[Milkman]

I keep asking if the MIDI-learn issue seen in the older versions, which is still present in the latest synthmaster2, has been resolved, but I still havent heard back.

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

[simmo75]

I keep asking if the MIDI-learn issue seen in the older versions, which is still present in the latest synthmaster2, has been resolved, but I still havent heard back.

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

Why don’t you demo it yourself?
Or email the developer?

[Milkman]

I keep asking if the MIDI-learn issue seen in the older versions, which is still present in the latest synthmaster2, has been resolved, but I still havent heard back.

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

Why don’t you demo it yourself?
Or email the developer?

What is even funnier about all of this is that Ive asked this same question 5x, and at least 3x someone (someone not with kv331) has replied with the exact same comment. "Why not try it???" lmao

Ive asked the dev enough times in enough threads, and if the dev cant give a simple reply about such a major issue - a major issue that MANY people already emailed the dev about over 2 years - then the dev doesnt deserve my time. Hope this helps. In fact, its insane how many chances the dev has had to reply about this issue but has totally ignored it every time. I wont bother asking again: I assume the MIDI-learn issue still exists, and the dev isnt planning on a fix.

[hurricaneaudiolab]

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

[kv331]

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