Hi there
EdGrip wrote: β03 Feb 2021
"190?" really made me lol
Its must be progression with logical step "200"... But its not interesting to use "200", we used "190" for some fun.
arnigretar wrote: β03 Feb 2021
Nice 4OP like the good old TX81Z, etc. Will try this
Yesterday we think about TX81Z waveforms. And may be add it soon.
Today no needs in new emulations of DX7. Nobody interesting just another in new one oldschool FM.
WTFM created to not emulate anything, but use power of the various possible waveforms.
Loque wrote: β03 Feb 2021
Featurewise it sounds interesting. Only loading of own wavetables or samples is missing.
Currently is hard for us to realise user custom WT samples loading to the FM Operators.
Device architecture not have sample using at all (no one-sample included), so no possibilities by engine to play WT samples or sample convetion into it.
450+ Wavetables - have a massive portion of waveforms.
Look from other side: 32 categories!!
Device include WTs from
16 hardware synths (and its only 7 categories of WT's) and
17 modular eurorack modules. Try RE and open hardware categories... its a really sweet collection of WT... into FM synth.
Back for seconds to DX7 (one Sine waveform at 12bit DAC outs), or TX81Z/DX7gn2 (8 waveforms)... and back up to the WTFM's 30.000 waveforms! We plan to add more
Our synth not about strong emulate of any real hardware, but we using their source waveforms for powerful results.
Oldschool FM... Time for modern FM with flexibility of the operators waveforms. Look at the Korg OpSix, its a real modern engine.. So WTFM includes some syhthesis modes:
1. Wavetable
2. FM synthesis
3. FM modulated by WT (FM WT MOD)
4. Ringmod
5. Filter FM
Device based on spectral analysis, and
not have any internal samples at all. WTFM not make at all any stress for the DSP.
antic604 wrote:
I'll wait for RS' reveal of Algoritm (or however it's spelled...) to decide.
Month of waiting for the new beatiful GUI and FM synth. I believe. Algorithm FM by RS must be interesting and we all can love it

PX7 - was been really outdated.
We start work under WTFM at July. And PX7 going out from the shop is a big news for us. And new device Algorithm release from RS break some our plans. But anyway, WTFM something other with flexibility of
FM and waveforms (not just for quantity, all wavetables - really useful). They not must be the same exclude FM category)))
WTFM not a waveform-limited few-Osc synthesizer with target to producing collection of patches.
Its a collection of waveforms for user experiments into FM. Main idea - user work with WT morphings and can produce much more from oscillators under FM engine.
How much FM synths can morphing waveforms? Modern Korg OpSix FM synth include waveworms "Width", and this is something near to WT morphings, but not at all. WTFM include realy deep WT morphings. This is a perfect side of modern FM.
antic604 wrote: β04 Feb 2021
do devs not have access to their devices in high-res mode when using the dev tools?
Im one of the devs who very long time ask for SDK - renderning pictures for shop, as ready device panels with all GUI elements. To have real device screen... But currently SDK render only background skin of the device, without any display elements (text values and some active graphic is not icluded).
Two ways solution to have finished shop pictures :
A. using printrsceens of real device in Reason (only current 754px width),
B. Use rendered background panel of device in sourced 4k. Plus add layers to it of some text with another fonts.. graphical elements layers.. and rescale it down to 1650px for the shop. Additional manual work that not present 1:1 to real Reason device screenshots but with better quality.
All files for REs build in 4K. (all RE in years waiting Hi-Res update, because all of them based on 4K graphic).
This is 1650px of the device,that been attached to product page soon as possible:
WTFM1650px.png
Open this image in new window for 1650px size.
Yes, devs need manual work to additionaly create finished product screens, SDK not render panels as finished.
But I beleive that sometime SDK must render shop screens, its logical. May be something change with anounced Hi-Res support.
antic604 wrote: β04 Feb 2021
that's my main issue with their devices - they're overcrowded & squeezed into GUIs that are 2x too small and usually very depressingly & drab looking
We build WTFM based on the GUI elements size of Subtractor and Maelstrom. All knobs as minimum - like in SubTractor. No real problem to use any knobs or faders. All elemnts is absoltely compared with other native and some 3rd part REs.
I understand what you try to say... Device not have enough free space on the panel.
Mainstream - to have Big-U panels with big elements. Compare something modern to Subtractor..
But years ago, PH SDK have rules: device must not using big panels and have oversized design from real hardware into the rack... time is go, and many RS devices - using big U-panel in height with big elements...
Anyway, we already change design solutions and our new FX (in work), have absoltely new design from all our products.
We are look what users say about this and from this point - start our design from this with new design priorities.
ps: We start to dicontinued our first old device. Know, some REs also need in redesign too.
Design is not the main part, but must be going on the modern level. Possibilities of FM - really more important.
Just opening project with 12 WTFMs on 4k...... Need to scroll....
If we open in double-sized panels this project, we need to scroll x2 4k displays..))))
For me - its a pain to select size between small compact GUI and big device into rack that really eat rack space. Need solution between this.
You do not have the required permissions to view the files attached to this post.