View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000900||OpenMPT||[All Projects] Feature Request||public||2016-12-11 16:38||2016-12-12 14:54|
|Product Version||OpenMPT 1.?? (long term goals)|
|Target Version||OpenMPT 1.?? (long term goals)||Fixed in Version|
|Summary||0000900: Plugin chains with mixer support|
As per my chat with Saga_Musix:
I'm using Xlutop Chainer because I miss certain functionality inside OpenMPT. There are a few reasons I haven't said goodbye to Chainer. It'd be awesome if these can be implemented in OpenMPT at some point.
What I'd love to see (its slightly different than how chainer does it by default, but I make changes to follow this workflow) is the following:
Have 16 channels, each listening to a different midi channel. (actually this is not even necessary if I can somehow send any instrument's midi data directly to such channel.)
Have an overview of what comes out at the very bottom of the channel to a volume switch with VU meter.
Have the ability to save the entire channel with plugins and their settings into a file, so I can reopen that channel in its entirely and it works out of the box. (I dedicate a channel for an instrument with its settings and EQ and so forth, so when I reuse an instrument, I only need little tweaking to make it work in my current song.
The ability to insert an output somewhere during the chain to redirect the sound to a different chain with a dry/wet slider allowing the sound to also continue in the same channel.
The ability to control the chain itself using midi macros, such as volume and dry/wet ratios of a redirect to channel block.
|Tags||No tags attached.|
|Has the bug occurred in previous versions?|
|Tested code revision (in case you know it)|
Oh i'm all for this! But I would have thought that would have been well under way if it was easy to implement...
The main reason I use Chainer is for side-chaining, esp. compression. So if somehow we can get this down without Chainer, AND if the interface were simple enough, I would jump right into it.
One of the other things I like with Chainer is that I can access all the presets from that window, but with MPT's plugin window not all the presets are evident. Usually this applies to VSTi's that have an internal list of presets or different banks. (I can check to see which ones I had problems with...)
A plugin either exposes its presets to the host or it doesn't. There's no way Chainer can show the presets but OpenMPT can't.
Or someone would have had to think about it before. I asked LPChip to submit his reasons for clinging to Chainer because people seem to use this crash-prone and old plugin but never tell us WHY.