Updated to v1.2: Integrate — Subtractive Synthesizer [CLAP, FL Studio]

[audiojunkie]

Here on Arch Linux / REAPER, UI mouse interaction is extremely laggy, it takes like 10 secs to see the effect of a click. Thus pretty much unusable. UI rendering seems fine though, e.g. oscilloscope animation is looking smooth.

That's really weird and doesn't sound the least bit usual. Is this only when using Integrate, or when you are using Reaper altogether? If it's not just with Integrate, then I recommend joining the Reaper Linux forum to get some help on your issue.

[nakst]

Sorry, I got sidetracked.

It occurs in both Integrate and Integrate FX
It occurs when a project is playing or not.
The Arp does also run twice as fast.
It sounds exactly twice as fast to me but I haven't tried to scientifically measure it.
I'm testing at 44.1K and 512 samples (12ms) latency, Focusrite ASIO drivers. Same settings when testing the CLAP version in Bitwig.

Thanks for this, I'll continue looking into the problem. Unfortunately I'm not able to reproduce it, so I may need to send you a PM later with a special diagnostics build so I can get better insight into how the DAWs are reporting the tempo/timing information to the plugin.

[nakst]

Here on Arch Linux / REAPER, UI mouse interaction is extremely laggy, it takes like 10 secs to see the effect of a click. Thus pretty much unusable. UI rendering seems fine though, e.g. oscilloscope animation is looking smooth.

Hi, thanks for the report. Nice to see a fellow Arch Linux user! I have just uploaded a new version v1.1.4 that should fix the issue with Integrate. IntegrateFX still has some minor lag, but it is significantly more usable than it was previously. I'll continue to look into how input handling is managed on the Linux build. Hope this helps

[Teksonik]

Sorry, I got sidetracked.

It occurs in both Integrate and Integrate FX
It occurs when a project is playing or not.
The Arp does also run twice as fast.
It sounds exactly twice as fast to me but I haven't tried to scientifically measure it.
I'm testing at 44.1K and 512 samples (12ms) latency, Focusrite ASIO drivers. Same settings when testing the CLAP version in Bitwig.

Thanks for this, I'll continue looking into the problem. Unfortunately I'm not able to reproduce it, so I may need to send you a PM later with a special diagnostics build so I can get better insight into how the DAWs are reporting the tempo/timing information to the plugin.

I forgot to reiterate that the issue does not occur on this system, only on my studio system.

FL Studio versions are the same on both and both are running the same build of Windows 10 21H2. Both run the same sample rate and latency.

The only difference is the studio runs a Focusrite 6i6 with FR ASIO and this system runs FL Studio ASIO with an onboard sound card.

At this point it looks like a system specific issue but I don't know where to place the blame. I use Arp/Seqs/Trancegates in every plugin I own that has them and have not encountered this issue before so it wouldn't appear to be the Focusrite drivers at fault.

But all those plugins are VST 2 or 3. Integrate being FL native and CLAP so the speed difference is a mystery at this point.

Here's a .wav file rendered from FL on my studio system. It's the init patch which defaults at 1/32 with the trancegate turned on. Host BPM is 130.

[karrikuh]

Hi, thanks for the report. Nice to see a fellow Arch Linux user! I have just uploaded a new version v1.1.4 that should fix the issue with Integrate. IntegrateFX still has some minor lag, but it is significantly more usable than it was previously. I'll continue to look into how input handling is managed on the Linux build. Hope this helps

Thanks a lot for the fast response, can confirm that UI working fine now with v1.1.4

[nakst]

I forgot to reiterate that the issue does not occur on this system, only on my studio system.

FL Studio versions are the same on both and both are running the same build of Windows 10 21H2. Both run the same sample rate and latency.

The only difference is the studio runs a Focusrite 6i6 with FR ASIO and this system runs FL Studio ASIO with an onboard sound card.

At this point it looks like a system specific issue but I don't know where to place the blame. I use Arp/Seqs/Trancegates in every plugin I own that has them and have not encountered this issue before so it wouldn't appear to be the Focusrite drivers at fault.

But all those plugins are VST 2 or 3. Integrate being FL native and CLAP so the speed difference is a mystery at this point.

Here's a .wav file rendered from FL on my studio system. It's the init patch which defaults at 1/32 with the trancegate turned on. Host BPM is 130.

I believe I have fixed the issue in the latest version, v1.1.6. Let me know if this problem still occurs.

If you have an existing instance of Integrate in a project, it will start in "compatibility mode" and retain the old timing behaviour. To switch to the corrected behaviour, from the Settings menu select the Exit compatibility mode option. (New instances of the plugin will not be in compatibility mode.)

I'll be rolling out fixes to my other plugins in the coming days since they also have the same bug. But I want to be careful to ensure that compatibility with existing projects is kept, so it might take a little time.

Thank you for your help in diagnosing the problem

[Teksonik]

I'm happy to report that version 1.1.6 has solved the speed issue in FL Studio here. Thank you for the fix.

[nakst]

One week left on the Halloween sale, 30% off: https://itch.io/s/78374/halloween-sale

[nakst]

Black Friday sale: 25% off until next Monday
https://itch.io/s/82150/black-friday-sale

[robindrieghe]

interesting, apricot is fun...

[Sawtooth Fairy]

Um, am I missing something or does that synth not have an ADSR filter envelope? Would be an odd decision given how complete the synth is.

[nakst]

Um, am I missing something or does that synth not have an ADSR filter envelope? Would be an odd decision given how complete the synth is.

You are correct. You have to assign one of the AD mod envelopes to the filter cutoff.

If I knew how controversial this design decision would be, I would have done it differently! I wanted to make a quirky classic VA-style synth, and this is what happened.

In all seriousness though, all my synths going forward will almost certainly have proper ADSR envelopes.

[Sawtooth Fairy]

Um, am I missing something or does that synth not have an ADSR filter envelope? Would be an odd decision given how complete the synth is.

You are correct. You have to assign one of the AD mod envelopes to the filter cutoff.

If I knew how controversial this design decision would be, I would have done it differently! I wanted to make a quirky classic VA-style synth, and this is what happened.

In all seriousness though, all my synths going forward will almost certainly have proper ADSR envelopes.

Oh, has anyone else commented on that? I did not read the entire thread
Ironically, your more basic Apricot synth has complete envelopes.

[robindrieghe]

is there anything planned for this update wise or are you working on other synths?
want to do some spending to support you but not planning to buy 10 more software synths

[nakst]

is there anything planned for this update wise or are you working on other synths?
want to do some spending to support you but not planning to buy 10 more software synths :)

Currently, I'm focusing my development efforts on making a new synthesizer. I can't say much yet, but I'm pretty excited about it :)

As for Integrate, there may be updates in the future, but I can't promise when that could be, or what the updates could contain.