sysrqer wrote: ↑Thu Jun 04, 2020 1:44 pm
Just gave the synth a try in Reaper. It seems strange to me that I can hear a saw(?) with all three oscillators at zero.
The envelopes don't act as I would expect. With the default settings the release for amp env appears to do nothing yet has some kind of relationship with the filter env (env release only has an effect if filter env release is up). Of course there are no rules but for a basic synth I would expect those two envs to be independent or at least for the filter env to be activated/deactivated, at the moment if you have the filter env all the way down (off I would expect) then you get no sound.
Edit: just realised that you have to turn the filter off for the amp env to work correctly so I suppose what I wrote above is kind of irrelevant.
If oscs are turned all the way up then there is just a sine?
BW seems to be the wrong way around, to the left is high res and to the right is little res.
Width I think goes too far, all the way to the left or right makes no sound at all. I know this might be useful if you want triggers but according to reaper's meters nothing at all is output.
Edit 2: * parameters (ranges, etc) not properly scaled/calibrated - missed that bit, makes more sense about directions of sliders and ranges now.
Other than that it's a good start, the filters sound nice. I was getting weird bursts of noise or something but they seemed almost random.
thanks for testing..
yeah, the parameters and stuff are weird..
i will change all that when things are becoming a bit more stable.. and use more traditional ranges, milliseconds and decibels, etc.. at the moment, i'm more concerned about the 'innards', the low level code, plugin format specific things, binary compability, etc, than the sound generation and/or user experience things..
but it's nice to hear what people think about it all, and i will of course take all that into consideration..
the osc parameters:
with all sliders at zero, it starts out as a saw.. with the 'squ' slider you morph between saw and square/pulse (and the 'width' slider affects the pulse width).. the 'tri' slider then morph between the square/pulse and triangle (or parabola if 'squ' is zero).. finally 'sin' morphs the result towards a pure sin.. it's not ideal, just something i put together quickly to test the oscillator/waveform generation stuff.. i'm not sure if i will keep the current scheme at all, or have a 'regular' mix of different waveforms, or something else..
you can put an oscilloscope plugin or something after it, to see how it changes when you tweak the sliders..
the filter envelope controls the filter frequency, and is always applied, there's no modulation amount.. so, with a short release, the sound is quickly filtered away, and not audible, even with a long volume envelope release..
i will add a modulation matrix of some sort soon, and with that there will be a lot more flexibility.. modulation amounts, scaling, etc..
the filter is using bandwidth (bw), not resonance.. maybe i should just invert it, and call it resonance.. or use another filter.. we'll see..
pulse width at 0% or 100% produces no sound, i know.. but i don't want to restrict anything yet.. will look at those kind of things a little later..
[edit]
the squ/tri slider could perhaps be changed to a x/y control..
something like..
Code: Select all
SAW _________ SQU
| | |
| | |
|----x----|
| | |
|____|____|
PAR TRI
where 'squ' is horizontal and 'tri' is vertical
plus two sliders:
* smooth (previously 'sin')
* width (pulse width)
- tor-helge
but i'm concerned about the 'weird bursts of noise'.. i'm right in the middle of adapting everything to mpe, so there might be some issues related to voice allocation and similar.. if i turn on 'mpe compatible' in bitwig, it crashes quite quickly, which might indicate that there's something fishy with midi channels.. i'll investigate..