Synthmaster One?

[sircuit]

Still no <prev next> browser for wavetables and proper marking of the loaded wavetable (Category/Subcat/Wavetable) with a ">" or "*"

And... when adjusting the curves in ADSR with the mouse:
- to adjust the A curve up, I have to drag the mouse upwards
- to adjust the D curve down, I have to drag the mouse still upwards
- why these curves don't go both ways (convex/concave) baffles me

I am so more and more dissapointed by one very good synth totally neglected in GUI area (SM) and a new synth lacking minor but very annoying things

[kv331]

Still no <prev next> browser for wavetables and proper marking of the loaded wavetable (Category/Subcat/Wavetable) with a ">" or "*"

And... when adjusting the curves in ADSR with the mouse:
- to adjust the A curve up, I have to drag the mouse upwards
- to adjust the D curve down, I have to drag the mouse still upwards
- why these curves don't go both ways (convex/concave) baffles me

I am so more and more dissapointed by one very good synth totally neglected in GUI area (SM) and a new synth lacking minor but very annoying things

You can use mouse wheel to scroll through waveforms/wavetables.

My work on SM1 is about to end with AAX support this week, after that I'll be back on planned updates for SynthMaster 2.8 and new work on SynthMaster 3

Also, please do not forget that I provided "free" updates since 2007, and 2.8 was our last free update.

[gjvti]

... and while we are on key tracking - how about key tracking modulation curves? I mean key tracking can be used as modulation source, but it would be nice if this key tracking curve could be edited... like this _/‾ or this ‾\_ for example

We do not support custome keytracking curves in SM1 (yet). But we have 2 separate keytracking mod sources: unipolar keytrack and bipolar keytrack.

yes, I know custom keytracking curves are not there, but with clever usage they are very, very useful I think, so in my opinion worth to consider at some point

[kv331]

yes, I know custom keytracking curves are not there, but with clever usage they are very, very useful I think, so in my opinion worth to consider at some point

+1

[zvenx]

Just installed v1.0.4 and when I change the skin to 120% the output meters start acting weird. When I switch back to 100% they behave normal.

I am seeing this as well, but no crashes with DP9.13

Same here in Cubase 9 on Sierra.
rsp

[kv331]

Same here in Cubase 9 on Sierra.

rsp

It's an image scaling error. Will fix in the next update.

[zvenx]

Same here in Cubase 9 on Sierra.

rsp

It's an image scaling error. Will fix in the next update.

Thanks Bulent.
rsp

[sircuit]

Also, please do not forget that I provided "free" updates since 2007, and 2.8 was our last free update.

Totally objective talking, this does not apply to me in any way, being a client only from last year, I hoped I'll see some improvements in the ergonomics/GUI department.

I am client only since Satya's synthmaster skin was released - so 2.7 or 2.8? - (the paid version of the skin, not the bundled one), until then I couldn't get my eyes to support the black GUI on retina.

However, I'm aware one can't satisfy everyone

[kv331]

However, I'm aware one can't satisfy everyone

That's right, however as I wrote above, I'm about to go back to 100% SynthMaster development, and I already talked to Satya about developing new skins with 200% scaled images for SynthMaster.

Before diving into SynthMaster 3 development I will release a couple of updates which will bring Retina support, new skins and also new factory presets.

[Amram]

Also, please do not forget that I provided "free" updates since 2007, and 2.8 was our last free update.

Much appreciate

[Captain]

Another GUI scaling related bug (apart from the output meters): when I set the size to anything >100% and open the plugin for the first time, the GUI is scaled, but the window is not, causing part of the GUI to cut off (see attached screenshot). Closing & opening the window once fixes the problem for that instance, but it's there again if I add another instance on another channel. Not a biggie, but slightly irritating.

Mac Pro, OS X 10.12.4, Logic 10.3.1. I have a three monitor setup, and my main monitor (where Logic always opens the SM window) has the resolution 2560x1440.

[Rogue Trooper]

Is there any chance we could have a change in the metering code? It's very disconcerting that the meter is red on SM1, but at -6dB in Reaper(0dB Pan law). It would be nice if anything over -6dB was yellow. Anything over 0dB is red. The meter isn't very helpful as it is for setting volume levels.

[fluffy_little_something]

Just out of curiosity, has SM One taken away sales from the "bigger" SM?

[kv331]

Just out of curiosity, has SM One taken away sales from the "bigger" SM?

Right now our biggest seller is SM 1+2 Bundle

[kv331]

Another GUI scaling related bug (apart from the output meters): when I set the size to anything >100% and open the plugin for the first time, the GUI is scaled, but the window is not, causing part of the GUI to cut off (see attached screenshot). Closing & opening the window once fixes the problem for that instance, but it's there again if I add another instance on another channel. Not a biggie, but slightly irritating.

Mac Pro, OS X 10.12.4, Logic 10.3.1. I have a three monitor setup, and my main monitor (where Logic always opens the SM window) has the resolution 2560x1440.

I will look into this. I guess it should be possible to report back to the plugin host about the size change