I'm glad everybody is enjoying it
There is one tiny issue with it that I'm going to release a fix for soon. Sometimes the ducking distorts the sound slightly because the compressor part is responding too quickly. I have a fixed version already done, but I'm going to hold off a little longer to see if I can improve the ducking characteristics even further. I'm also sitting on improved versions of LMS Filter and LMS Comb, where LMS Filter sounds smoother when modulating cutoff, and LMS Comb is more stable in a few hosts that were exhibiting weird behaviour.
DoosC wrote:What is the next step ? What about a sidechain compressor like Steve Harris SC3 ? It is the only one I know and it is LADSPA so I guess there is room for a DSSI one.
It just so happens that I have one in the works
I'm working on a compressor right now called LMS Dynamics, when it is finished, I'm going to immediately fork it into LMS Sidechain, which will only require me to change about 10 lines of code. I was hoping to release them this weekend, but I'm not happy with the way it sounds, so I might hold off a little longer on it.
slowpick wrote:While trying to fix something else, I discovered that running this command as root:
service network restart
cures one of my systems, that previously refused to display any dssi GUIs.
It would load the instrument, without any interface. The command evidently
resets something in certain network defaults. Maybe this could be coded
into a future update of your library?
I'll include that in the LMS wiki when I finally get it up and going, but as far as I know, there's no good way to put that in the library. DSSI plugins are setup like this:
1. The plugin (.so shared library file)
2. The GUI (elf executable file, optional)
The 2 communicate to sync their knobs and sliders over OSC(the GUI updates the plugin, and host automation and MIDI CCs update the GUI). The plugin .so file is loaded by a host like Qtractor or jack-dssi-host, then the GUI executable is run by the DSSI host and told to make an OSC network connection to the plugin's address, so the underlying plugin itself has no idea the GUI is even being started until it's already running and has established a GUI connection.
The DSSI host's developer could code that into the host, however... Right now it seems most DSSI hosts just launch the GUI without even checking to see if it started.