As an extension of this idea any additional effects should default to the
parent effect as their initial source, but it would also be kind of cool if
we could route around a previous effect for a quad+ input effect so we
could use a previous source as an alternate input. So for example in the
case of something like Span one could compare the unaltered input spectrum
to the altered output of the previous effects spectrum. Likewise each
previous effect should be an additional optional input source for any child
input. This would give the equivalent of a node based effect chain while
keeping things organized in a stack format... Yes, it would mean the choice
list could grow rather large, but the potential would be cool. :)
On Mon, Feb 17, 2014 at 12:17 PM, Bill Y. <b...@anzovin.com> wrote:
> What I was thinking was a multi-select box that could exist above or below
> the controls button for an effect. Here is are some ascii examples of how
> the pull down list might function.
>
> x = selected
> o = unselected
>
> ---Example 1 (instrument or FX-Mixer with a single source feed) -------
>
> [ x source 1 Left > effect input 1 ] (default)
> [ o source 1 Left > effect input 2 ]
> [ o source 1 Left > effect input 3 ]
> [ o source 1 Left > effect input 4 ]
> [ o source 1 Right > effect input 1 ]
> [ x source 1 Right > effect input 2 ] (default)
> [ o source 1 Right > effect input 3 ]
> [ x source 1 Right > effect input 4 ] (a 2nd assignment)
>
> ---Example 2 (FX-Mixer channel 2 source feeds)
> ------------------------------
>
> [ o source 1 Left > effect input 1 ] (default)
> [ o source 1 Left > effect input 2 ]
> [ o source 1 Left > effect input 3 ]
> [ x source 1 Left > effect input 4 ]
> [ o source 1 Right > effect input 1 ]
> [ o source 1 Right > effect input 2 ] (default)
> [ x source 1 Right > effect input 3 ]
> [ o source 1 Right > effect input 4 ]
> [ x source 2 Left > effect input 1 ] (default for 2 inputs)
> [ o source 2 Left > effect input 2 ]
> [ o source 2 Left > effect input 3 ] (default for 4 inputs)
> [ o source 2 Left > effect input 4 ]
> [ o source 2 Right > effect input 1 ]
> [ x source 2 Right > effect input 2 ] (default for 2 inputs)
> [ o source 2 Right > effect input 3 ]
> [ o source 2 Right > effect input 4 ] (default for 4 inputs)
>
>
> On Mon, Feb 17, 2014 at 11:09 AM, Bill Y. <b...@anzovin.com> wrote:
>
>> Would it be possible to add a pulldown input list for effects that was
>> dynamically based off feeds coming into the effect, and available inputs
>> for the effect? That way on instruments you would have a single feed, but
>> could direct it to multiple inputs of the effect, and on the FX mixer it
>> would show the multiple track feeds which could be directed to the various
>> effect inputs. This would open up multi track VST's like Span which can do
>> spectrum comparisons of two stereo pairs.
>>
>>
>> On Mon, Feb 17, 2014 at 9:26 AM, Vesa <dii....@nbl.fi> wrote:
>>
>>> On 02/17/2014 04:19 PM, Johannes Lorenz wrote:
>>> >> I guess my question now is , Where is the LADSPA vocoder plugin? I
>>> can't
>>> >> find it in the plugin list, but I see its library in the plugins
>>> directory.
>>> > It does not work. Reason: The ports are labeled incorrect (must start
>>> with
>>> > "In" or "Out"). However, even if you re-label them correctly, the
>>> effect is
>>> > not supported, because it has 2 stereo inputs.
>>>
>>> It does work. Someone made a tweak for it for LMMS, changing its output
>>> to stereo, so that it has two in - two out.
>>>
>>> It shows up in the list as "LADSPA Effect: Vocoder for LMMS", but I'm
>>> not sure if it was included before or after the RC.
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Android apps run on BlackBerry 10
>>> Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
>>> Now with support for Jelly Bean, Bluetooth, Mapview and more.
>>> Get your Android app in front of a whole new audience. Start now.
>>>
>>> http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> LMMS-devel mailing list
>>> LMMS-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/lmms-devel
>>>
>>>
>>
>
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
LMMS-devel mailing list
LMMS-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmms-devel
