A patcher (like the one in FL Studio) would be useful. It can make it a lot easier to see what plugins are being used and how they are affecting the sound. The patcher should include a dashboard for automation controls to allow for easy access to a variety of settings on the plugins. The implementation of an X/Y pad would be very much appreciated (as both a plugin and a controller on the patcher dashboard) because it can help to visualize what is being automated.
I too think that this should be implemented and is really a very useful feature.
One of you @sksar @BiRD4 need to explain the actual feature, in a concise and detailed way.
'patcher' means nothing to most, and insight in FLs latests ed. is not common.
@musikBear said it all, please explain the feature, or this will be closed.
A patcher is a window that can show instrument/effect chains. An important feature of a patcher is that patcher presets can be saved, similarly to .xpf files. This way, instrument/effect chains can be transferred between project files much more easily. The patcher can also act as an automation control panel, so that the controls for instruments or effects can be accessed easily.
Here's a picture showing a patcher with three tabs and two separate chains:
https://cloud.githubusercontent.com/assets/20910668/21571708/cd41513a-ce9f-11e6-9f08-9762a45162d4.png
Tabs 2 and 3 each have one controller linked to Monstro.
Without color:
https://cloud.githubusercontent.com/assets/20910668/21571536/5db84a7c-ce9e-11e6-8bb6-6bce52895185.png
Here's a page with a picture of FL Studio's patcher (which is much better looking than my drawing):
https://www.image-line.com/support/FLHelp/html/plugins/Patcher.htm
The red lines represent connections between controllers and plugins.
To summarize, a patcher is a window that contains a graphical representation of instrument/effect chains and automation controls and can save presets for later use.
Hopefully, this has illustrated what a patcher is and why it is useful.
@sksar - if you would like to add or correct anything, I would appreciate that very much.
@BiRD4 github allows pasting images directly into the bug reports. Please use that technique to protect against link rot.
@tresf I am a relatively new user, so I don't think I understand how to paste an image properly. Opening the image in paint, copying it, and pasting it in the box gives me a link. How do I do this correctly?
Just click on a picture in a folder on your computer and drag it over the comment entry window (Where I'm typing this) and drop it there.
Like this:
https://help.github.com/articles/file-attachments-on-issues-and-pull-requests/
[...] pasting it in the box gives me a link. How do I do this correctly?
That's exactly it. Click "Preview" tab and then switch back to "Write" and move it around as needed. 馃憤
Edit: The FX Preset request lives here, may be a dupe https://github.com/LMMS/lmms/issues/1680
Also, I think that the reason that the pictures were not showing up in the window was that I didn't go to the preview tab first. Thanks for the help!
A patcher?
@BiRD4, like Carla? http://kxstudio.linuxaudio.org/Applications:Carla
@SirBothersome The patchbay is the main idea I'm going for. The only thing Carla seems to be missing is an automation tab, but of course that isn't so important unless it's being used in a DAW, like what I'm suggesting. Carla is something pretty good to model a patcher after. Just get rid of all the unneeded parts and add an automation tab for use in LMMS's automation tracks.
In general, though, I think that if you want something to look at for reference, FL Studio's patcher is the best option. (Of course, I know that FL Studio's source code isn't available, but I still prefer using its patcher as a reference over Carla)
Most helpful comment
One of you @sksar @BiRD4 need to explain the actual feature, in a concise and detailed way.
'patcher' means nothing to most, and insight in FLs latests ed. is not common.