After using this plugin for some time I need to ask some question about the way it works...The question is - does Dynamic DSP insert content of its internally configured DSP chain and lefts rest of chain intact or just... replaces whole chain with the one programmed inside Dynamic DSP?My normal DSP Chain looks like this:Dynamic DSPSkip SilenceDownmix multichannel to stereoPlayback Rate Shift - most of time just set to 100% (unaltered playback rate)Skip TrackDynamic DSP is used to occasionally change playback rate on selected tracks. I created additional DSP chains that are used for configuring Dynamic DSP plugin. In general they are copies of my normal regular DSP chain with removed Dynamic DSP and adjusted playback rate via Playback Rate Shift plugin. And I started thinking if this isn't source of my occasional problems with Skip Track component. Initially for some reason I thought that this is obvious that Dynamic DSP must fully replace original DSP chain - that's why all chains used by DDSP are nearly copies of my main chain. But now I wonder if don't cause that for some files (tagged to trigger DDSP) my DSP chain looks like this:Skip SilenceDownmix multichannel to stereoPlayback Rate Shift - set somewhere between 95 and 107%Skip TrackSkip SilenceDownmix multichannel to stereoPlayback Rate Shift (unaltered playback rate)Skip TrackAnd I don't care for double Playback Rate Shift occurrence but about Skip Silence and especially about Skip Track... Popatr - your answer, as the creator of this plugin will be much appreciated.
Main chain looks like this:Skip SilenceDownmix multichannel to stereoDynamicDSPSkip TrackDynamicDSP setup:chain named faster:playback Rate Shift: 107%chain named slower:playback rate shift: 97%
I've been using this plugin a lot, it's great for automatically setting different low-pass filters to chiptune songs.I'm basically necro-ing the thread but I'd like to be able to use values like "Less than" in the plugin, for example a chain that is triggered by any song with a Sample Rate Lower than 44100 Hz. I'm not sure if it's possible with the current version, is there any code to make this work?It would be really useful, because it's hard to edit custom DSP tag info in chiptune / non-standard files.
ps, in the past I have looked into why the component crashes when launched from view/dsp. I have been unable to figure it out.