Synth1: Bug Reports/Feature Suggestions

[3ee]

I told him about this thread, but If daichi can't read English it might have pointless.

We can use this... http://www.kanjidic.com/
But we got to keep the text very simple or it's easy for the program to mistranslate because japanese grammar is different I guess. So a good idea would be to write in english, translate into japanese and then take the translation and translate back in english again to check if it's cool.. you will notice that some sentences would become really altered... so we got to compose more "cave-manish" sentences to get it good in japanese... the simpler the better.

[3ee]

I think orbik's unison voice bug has been sorted in the latest release - can anyone confirm this...

Just took the test suggested by Orbik with the new vers. (1.12) and every 4th note bla bla...so, it didn't get fixed.

[hakey]

I think orbik's unison voice bug has been sorted in the latest release - can anyone confirm this...

Just took the test suggested by Orbik with the new vers. (1.12) and every 4th note bla bla...so, it didn't get fixed.

Yes, you're right. I thought I'd set the test up correctly - obviously not.

[surfingo]

I would like a Morph function NL style
a step sequencer arpeggiator
the XY pad similiar to "oatmeal" modulation
ok!

[SciFiArtMan]

With the introduction of v1.12, I like to see the Patch Selector grid contain a smaller and narrower typeface (like 10pt or 12pt Arial Narrow or Helvetica Narrow) and be floating within the grid boxes so the bottom parts of the letters could be seen. (very good organ = verv aood oraan)

I have 1000s of original patches, but have trouble seeing the final version numbers of the patches due to the (relatively) oversized typeface used in the Patch Selector grid. (Crunchy Guitar - New Song 5 = Crunchy Guitar - New So)



Also still hoping to see Delay and Attack settings on the LFOs.

Love to see Positive AND NEGATIVE Filter Track control settings. (working on an organ patch last night that sure could benefit from having the lower notes be filter rich and the higher notes be more subdued and mellow).

Finally, maybe 14 or 16 colors for patch IDs, instead of 7.



I'm loving the many changes you are adding to this great softsynth, Daichi!!! Thank you so much!!!


v1.12の導入により、私はパッチ選択グリッドを表示するようにして）と10ポイントまたは12ポイントMS Pゴシック絞込みやHelvetica絞込みのように小さく、狭い書体を（を含むグリッドボックス内の文字の下の部分ように浮かんで見ることができる。 （非常に良い臓器= vervのaoodのoraan）

私は、元のパッチの1000を持って問題を（比較的）大型書体は、パッチ選択のグリッドで使用されるため、パッチの最終的なバージョン番号を見ている。 （パリパリギター - ニューソング5 =パリパリギター - ニューヨークだから）

また、まだつのLFOの遅延や攻撃の設定を参照してくださいことを望んで。

愛正と負のフィルタトラックコントロールの設定を確認します。下のノートには、フィルタと高音が豊かなより落ち着いたとまろやかされることから（オルガンパッチに取り組んで最後の夜は、必ず利益を得られる）。

最後に、多分14またはパッチIDの16色ではなく、7。

しかし、一般的に愛情のある多くの変更は、この偉大なソフトシンセを追加して、大地！どうもありがとう！


SciFiArtMan

[brok landers]

could someone maybe translate the collected bugreports (on page 1, 2nd post) into japanese, please? there's a fair chance that ichiro doesn't understand them otherwise. At least this would make his life easier, i suppose ...

[orbik]

A couple of feature requests:

1. More filter options:


2. Increase parameter resolution from 7 to 32 bits:

Now most vst-automatable parameters only take integer values in the range 0-127, which makes sense for direct midi control but not in the vst world. I'd suggest using 32-bit values internally (0-4294967295) and representing them either as percentages or rescaled to 0-127.99 (divided by 2^25) for preserving familiarity.

Editing the values with the mouse could be modified with:
Shift = 8x precision
Ctrl + Shift = 64x precision

The .sy1 files include version info, so backwards compatibility wouldn't be compromised either.

[EvilDragon]

Hm, 36 and 48 dB/oct filters would be overkill, IMHO. I'd rather have a selection like this:

TYPE:
LP
HP
BP
BR

dB/oct:
6
12
18
24

[orbik]

Hm, 36 and 48 dB/oct filters would be overkill...

Pff, 48 is plenty useful especially for clear, smooth lead-type sounds. Why would you rather not have the option? The 6 dB/oct (1st order iir) might be underkill though.

[hakey]

Why would you rather not have the option?

"Economy of form", or something like that? A good part of Synth1's charm is it's relative simplicity; if every conceivable feature were added that simplicity would necessarily be compromised. I can think of a very long list of additions for which the argument "why would you rather not have that?" would equally apply, but if every one of them was implemented Synth1 would become a dog's dinner.

FWIW, I'd actually prefer to see a second filter added with the ability to run them both parallel or in series - which would allow 48db cut off, plus formant filter type effects. But then that would require another env, and signal routing and mod controls that would take up a whole load more screenspace - and it would incrementally move Synth1 along the path of increasing complexity.

(I'd much rather see an improved/expanded mod matrix first )

[orbik]

"Economy of form" ... simplicity ... screenspace ...

I take it that by simplicity you mean ease of use, particularly for new users, and not simplicity of function per se. I don't think adding filter types makes it any harder to grasp, and hardly requires more screen space; e.g.:

[EvilDragon]

Now that's better.

Just ad 6 and 18 db/pole filters and that's it

[brok landers]

"Economy of form" ... simplicity ... screenspace ...

I take it that by simplicity you mean ease of use, particularly for new users, and not simplicity of function per se. I don't think adding filter types makes it any harder to grasp, and hardly requires more screen space; e.g.:

ditto.

[brok landers]

>snip< Just ad 6 and 18 db/pole filters and that's it

ditto.

[hakey]

I don't think adding filter types makes it any harder to grasp, and hardly requires more screen space; e.g.:

Yep, implemented like that it's fine - and an improvement over the original illustration you gave, which was a little bit cluttered and didn't really make the most efficient use of screen space - kind of what I was getting at re. 'economy of form'.