Ohhh, I'm jealous...

In the 90's i was about to buy an LM-1 just because it was cheap (I was more in 909 techno sound at that time) and finally I spend the money in a Juno-106, I never regretted my decision as I enjoyed the Juno a lot, but now I will love to have a LinnDrum, an LM-1, a DMX or even a DrumTrack...

At the moment I'm using this one:

https://youtu.be/ukn-s_6WpoQ

Neat!

Programming a machine doesn't feel anything like actually playing drums to me. My rhythm thang doesn't work on push buttons I guess. :0)

Interestingly it appears there is also a User/Noise/VPM selector on drum-o-logue too. Hopefully they didn't fork the SDK feature set. Sort of worry about that with the 'platform type' code flags that we picked up last time. Hmm...

Customizable params is ready for testing with FM64 1.3-5.

Several other implications of the custom parameters variant that might not be clear and was not yet documented :
- Velocity is bound to Shape (Alt is of no use for not)
- Motion automation for params is not available on the XD (unlike AC with Shape/Alt!)
- LFO is bound to Amp (no feedback direct control)
- Since bipolar values are incorrectly initialized, '-100' value is not used
- All custom params are relative to the voice params
- All offset params are clipped so the altered value is within the original parameter range (except detune offset, which is not clipped!)
- All scale params applied just after offset and clip, but result is not clipped anymore, so the result could be out of bounds of the original synth (well, in most cases fixed-point clipping can be still limiting factor)
- KVS params sounds like value is inverted, this is because the actual velocity value applied to the overal level is negative (I wonder how KVS affect the actual synth)

Web page is altered too - highlighted params have a dropdown with all available internal parameter bindings.
As always, manifest format extension and header file with implementation are available at github.

I did a quick test of 1.3-5, it works very well, I will test it in full tomorrow.

I just noted something with Detune. Compared to previous version, I feel the high notes more detuned. I will check that properly tomorrow.

I didn't try all parameters as I did just one oscillator, but the ones I tried works as expected.

Velocity bounded to Shape is OK for me and I think is the better choice.

May be you could make Alt assignable and keep it unipolar by now, until you find a better solution. I mean just make it work from 0 to 100.

I can't say anything about it...

I always wanted to ask you (and forget to do it) what exactly LFO to Amp means... At the beginning I thought that LFO was routed to A Mod Sens to mimic the effect of the original LFO, but I tried several times and seems to affect all Modulators (not the Carriers?)...
To me the most natural behaviour will be that LFO affects Shape=Velocity...

OK, not a big problem...

I'm not sure what you mean. But at this point I want to ask if there is any parameters that is not reset with voice change.

OK

OK, KVS was not working right in last 2 versions, but I think is working right in this one (just checked a few voices). I didn't try the KVS custom parameters...

Web page is looking good!!!

Detune must be the same, just offset/scale precision was changed - 1% is exactly 1 cent now!

Custom params supports customizing Shape/Alt as well. So technically it should not be a problem to add the same params as unipolar +/- pair as Shape/Alt controls. I just need to consider the unified way of setting params.

LFO is applied to sample output
So just treat LFO like a tremolo.

KVS is key velocity sensitivity / touch sensitivity. It is not key-tracked, it is just s velocity scaler. But the way it is currently applied makes the referse effect

I had some time to play and test the new version and some of the new features.

This are the parameters I tested:

Detune is not working right.
The high notes aren't more detuned like I said before, but all the keyboard is more detuned.
I have to set Detune Scale to -99 to get the same detune that in previous version, so I think is a problem with the parameter. I didn't tested Detune Offset but Detune Scale works except for what I say before, may be is related to the value set at 0%.

Algorithm works right.

Rate Offset and Rate Scale work right (I have to decide wich one I like the most )

Level Offset and Level Scale seems to work right. It is kind of weird because affects all operators (carriers and modulators) at the same time.

KLS Offset is not working right. I think it have the same problem that Detune. KLS didn't work when is at 0% and I have to set it to positive values to get some KLS effect. Negative values have no effect.

KLS Scale is not working. It does nothing. Should be related to the KLS Offset problem.

KRS Scale works right. I didn't tested KRS Offset.

FB Scale and FB Offset are working right.

That is what I tested until now. I will check the rest later.

Some strange thing I found is that some patches with sustain at 99 sounds with sustain at 0. It happened with some of the banks I made for testing in the past, but I didn't found the some problem in other patches. Those patches worked right before... I will investigate some more...

OK, I think I confused it with the FB modulation mode. It is clear now.

I confused KVS with KRS, sorry
I didn't try KVS yet....

I can't see what could be wrong with detune now:

I'm comparing to ver 1.3-0 now, but I'm pretty sure that until ver 1.3-4 detune was working right... I will double check with ver 1.3-4 to be sure.

I tried ver 1.3-4 and indeed Detune was working right, just like in ver 1.3-0

Try with both scale & offset. It might be oddset paraminitialization issue, so start from setting both to zero

I tried with Detune Offset and Detune Scale, both set to 0 and behaves the same, it is very detuned.

I found that Detune Offset acts like an overall oscillator fine tune, I mean it changes the tuning of all operators at the same time but keep the relationship between them... so I can't think of a use for it unless you want to detune FM64 respect the analogue VCOs.

Also tried to set KLS Offset and KLS Scale to 0 and also behaves like before...

Sounds strange - I checked detune, and it was close to the previous version. Well, one of the debug bulds has scaled up detune resolution 256 times - THAT was a big detune

I did a quick recording to show the difference:

https://drive.google.com/file/d/1A9l...ew?usp=sharing

1 - ver 1.3-5 - E PIANO 1 - single note
2 - ver 1.3-4 - E PIANO 1 - single note
3 - ver 1.3-5 - E PIANO 1 - chord
4 - ver 1.3-4 - E PIANO 1 - chord
5 - ver 1.3-5 - VIBE - two notes (octaves)
6 - ver 1.3-4 - VIBE - two notes (octaves)

Also noted that the envelopes in 1.3-5 are shorter... strange...

EDIT: May be there is a problem with Rate Offset or Rate Scaling initial value...

1.3-4 has a bug with AC 4&5 zero initialization, needs to be set to 50% before testing. That should fix the envelopes difference IMO.

Yes, it is that. Setting AC 4 and 5 to 50% give me the same envelope time that 1.3-5

AC rates is already fixed in sources, but I did not publish compiled 6/67/68 versions yet.
Checked sources - Looks like I screwed up with fine detune control. Since 1.2-19 detune is 4 times less than intended to be.

So try to compare the latest version with the Detune Scale set to 25% - it should be just in par with previous. I wonder now with what version I compared PLG-DX

By 25% do you mean -50% or you actually mean +25%?
Because +25% will more detuned...
When I compared with previous version I had to set Detune Scale to aprox. -99%, but I'm going to try -50%...

In versions 1.3-0 and 1.3-4 detune is very close to Dexed and Arturia.

Duke, does this thing support params? https://nts-web.oscarrc.me/

Just -75% display

NTS-1 just do not have MIDI control for params :(

Does the XD?

Yes, both XD and prologue have NRPNs for this

Thanks. I was under the impression that it didn't respond to them.

Well, I didn't try it too

Nor me I read that and gave up. I have a controller that can send either MSB or LSB for NRPNs - but not both in one message, i.e. not 16 bit values other than by using two separate knobs, one per byte. I'll experiment with that.

I see there's no Alt Assign, for FM-64 1.3-5. Is that just to try out new parameters or have you decided not to let other parameters be changed, any more? That seemed to be the only way of doing it, other then editing the sysex - e.g. to try the different waveforms in FM66-68.

Alt not assigned since any direct control will alter selected voice and shape knob does not have bipolar tomake it work like an offset. I'll add waveform selecton as custom params later

OK, I will try that.

Shape and Shift Shape (Alt) can be controlled by normal CC (54 for Shape and 104 for Shift Shape) on the Prologue.

But none of the user parameters can be controlled by CC, NRPN or sysex. The only way to change them via MIDI is sending the whole sysex patch.

Yep, prologue does not have midi control over user params too - only XD :(

-75% works good.
I didn't measured the beating but by ear is very close, may be if I set to -70% I feel it closer but theres is not much difference.

Just added a various waveform selection custom params with the FM66 1.3-5