I am only one which prefer synths which show envelope times in real world time? not like 0-127 numbers what mean for example 0ms-10seconds or even poorer they dont show values at all. If you are developer and develop for mac this is very important way try sell stuff for me.

no, I completely agree with that.

i like to have a numerical reference, but i don' really need them to betrue pameter numbers.... all i would like to have is that there's no discret values in between the numbers of the readout. if the readout says 120, it should be 120... not 119,7 or 120,4... for real values, on env's they don' tell you shit, as you don' know the curves of the times, and the curves determine, how long you perxceive the time. f.e. a value of 2sec decay sounds way shorter if the curve is concaved, and way longer if convexed... so these realworld values don't tell you shit in many cases... to me the most important thing regarding the readouts is, that i know where i am, i don' care if the values are real or if they're abstract.... of course exeptions tighten the rule, i.e i prefer the cutoff to be adjustable un hz, while i don't care for the resonance to be displayed in db, as, especially with a selfoscillating filters, that valie can only be cvery rough and unpredictable....

but enough now, off to the beaach...

Lucky you, Will have to wait 11 month now to know again what a beach is

As for envelopes, real time is OK. And symbolic stepes are OK too. Real time gives you an idea of what the time will be, and can make it easier to adapt to new synths if they all use the same scale system. But symbolic values are almost as easy to work with for me, as I trust my ears first.