ardura / actuate Goto Github PK

1. Load sample and make sounds
2. Save your project in your DAW and close the DAW
3. Reopen DAW and open project
4. try to play your sound again (nothing loads)

I'm thinking this either needs to store the sample in the nih param struct or call that regenerate samples function on reload/detection of nothing in the memory + Sampler/Granulizer Audio Module in use

When a long note is held and the filter cutoff is moved there is no change until you let go of the cutoff knob(s)

This should change to be real time rather than on release like the detune knobs on audio modules

It's an open-source plugin manager called StudioRack:
https://github.com/studiorack

The aim of the project is to provide a free open-source way to manage plugin dependencies and their versions. It would involve the following steps:

Publish a Github release containing the plugin source along with metadata plugins.json
Tag your Github repository with studiorack-plugin so it can be discovered
Wait for the studiorack-registry to index your plugin (every 24 hours)
Check the registry feed for your plugin to appear

Upon loading both the VST 3 and CLAP flavor, I get this error message:
Entry Point Not Found - The procedure entry point SetProcessDpiAwarenessContext could not be located in the dynamic link library USER32.dll.
I assume it's worth mentioning that I'm still using good old Windows 7...

I'd very much appreciate it, if Actuate could be made to run on this OS, but if the effort is too much, I understand that this will not happen. In this case please mention somewhere (e.g. on KVR Actuate page or at least in some README coming with the download) what is the minimum supported OS (maybe not only for Windows but also the other supported OSes.

You can't hear it but once you hit moog/tb/other SVF resonance algorithms linked to LFO modulations it never goes away even with no sound output. I'm not really sure how to fix that yet.

Recording to demonstrate below.

The filter envelope sustain stage is always below the set cutoff (max sustain = set cutoff), which causes the filter to open during the release stage.
Because the envelope attack stage ends at (set cutoff + env mod), this also creates the issue that the sustain point (max = cutoff) will always be lower than cutoff + env and at max sustain the filter will still close during the decay stage.

One other thing here is that the filter and filter envelope seem to be monophonic regardless of max voices. Not Necessarily a bug but it would be beneficial to have polyphonic filter. The issue that this causes is that when releasing a note while another note is held, the release stage takes priority, which causes the filter on the note still being held to be sustained at the set cutoff point (which is above the set sustain point as detailed above).

also wanted to say it's possible I missed some mode switch and am incorrect.

Issue demo:
https://soundcloud.com/ovrmnd/actuate-envelope-cutoff-end/s-0ghFtfXUQW0?si=c14ab2ed972f49b99a25a8647638fa08&utm_source=clipboard&utm_medium=text&utm_campaign=social_sharing

Clicking next or previous preset goes 0, 2, 4, 6 but in FL Studio it goes 0,1,2,3,4

I was testing Actuate on different hosts and I noticed that Actuate behave inconsistently on MIDI note input:

Bespoke Synth

• Actuate responds to midi notes from MIDI external devices/ports.
• Actuate doesn't respond when MIDI is generated/played inside Bespoke Synth itself.

Ardour

• Actuate doesn't respond to midi notes from MIDI external devices/ports.
• Actuate responds to MIDI when playing MIDI clips but:

1. Only a long sustained (stuck?) note is played
2. Only the first note of the MIDI clip is played, the other notes of the MIDI clip are ignored.

Carla

• Actuate doesn't respond to midi notes regardless of their origin (external devices/ports, other plugins, etc.)

Somehow DC Offset is created when there are 3 pulse wave Osc and the routing is changed on the middle one with the filter 1 being VCF and filter routing = parallel

I'm not sure what is causing this but it seems like an unstable filter either the VCF losing that full on/off signal or the SVF gaining a full signal immediately is likely causing this.

Bitwig shows a message that processing has stopped when it opens.

I haven't tested with Bitwig but in windows this process did throw exceptions that windows/FL allowed so it could be something like moving it to a background thread to fix this?

Actuate advertises these CLAP plugin features:

• audio-effect
• stereo
• mono
• utility

I've never used this plugin before so I don't know which features would accurately describe it, but it appears to be a synthesizer plugin which takes midi input and produces audio output. In that case, it should provide the "instrument" feature otherwise DAWs may not categorize (or even load) the CLAP plugin correctly. I'm also not sure if "audio-effect" and "utility" are accurate, though you'd know best here.

In the branch of LMMS with work-in-progress CLAP support, LMMS categorizes Actuate as an audio effect and (falsely) assumes it to have an audio input because the plugin advertises itself as an "audio-effect". This prevents Actuate.clap from working in LMMS.

Here's the relevant part of the CLAP API if you'd like to review it:
https://github.com/free-audio/clap/blob/main/include/clap/plugin-features.h

After latest update I have the following errors when building on Linux, Debian sid, cargo 1.77.0-nightly (add15366e 2024-01-02) with cargo xtask bundle Actuate:

...
Compiling Actuate v1.1.0 (/home/user/opt/audioplugins/Actuate)
error[E0583]: file not found for module `FX`
  --> src/lib.rs:87:1
   |
87 | mod FX;
   | ^^^^^^^
   |
   = help: to create the module `FX`, create file "src/FX.rs" or "src/F
X/mod.rs"

error[E0432]: unresolved imports `FX::StateVariableFilter`, `FX::compressor`, `FX::delay`, `FX::reverb`, `FX::biquad_filters`, `FX::biquad_filters`, `FX::saturation`, `FX::phaser`, `FX::buffermodulator`, `FX::flanger`, `FX::limiter`
  --> src/lib.rs:72:5
   |
72 |     StateVariableFilter::{ResonanceType, StateVariableFilter},
   |     ^^^^^^^^^^^^^^^^^^^ could not find `StateVariableFilter` in `FX`
73 |     compressor::Compressor,
   |     ^^^^^^^^^^ could not find `compressor` in `FX`
74 |     delay::{Delay, DelayType, DelaySnapValues},
   |     ^^^^^ could not find `delay` in `FX`
75 |     reverb::StereoReverb,
   |     ^^^^^^ could not find `reverb` in `FX`
76 |     biquad_filters::{FilterType, self},
   |     ^^^^^^^^^^^^^^               ^^^^ no `biquad_filters` in `FX`
   |     |
   |     could not find `biquad_filters` in `FX`
77 |     saturation::{Saturation, SaturationType},
   |     ^^^^^^^^^^ could not find `saturation` in `FX`
78 |     phaser::StereoPhaser,
   |     ^^^^^^ could not find `phaser` in `FX`
79 |     buffermodulator::BufferModulator,
   |     ^^^^^^^^^^^^^^^ could not find `buffermodulator` in `FX`
80 |     flanger::StereoFlanger,
   |     ^^^^^^^ could not find `flanger` in `FX`
81 |     limiter::StereoLimiter,
   |     ^^^^^^^

Some errors have detailed explanations: E0432, E0583.
For more information about an error, try `rustc --explain E0432`.
error: could not compile `Actuate` (lib) due to 2 previous errors
Error: Could not build Actuate

Compiling suggestions:

1. Change generator type and routing knobs to dropdown menus
2. Generator type should contain all OSC types
3. Make FX Scrollbar stay visible
4. Rename Cancel to Close in preset browser
5. Align the Generator panes with the right side too
6. Flip the Attack curve button graphic
7. Use the horizontal curve buttons instead of the larger ones to save space

See if using the state is better than doing the setter for params and reloading things manually they way it is done currently. This would still need to work with the way samples are stored in presets.

In the future Actuate should "install" preset packs to a shared directory and then reference them there without needing to load preset packs again. Then the preset browser changes to:
Pack>Preset rather than just Preset. Something like Image-Line's stock plugins:

Found your synth, looks nice!

I was just gonna ask you to kindly list somewhere what kind of plugins it implements.
Unless I'm blind and it's already there...