I’d forget about the built in send and return structure and kind of build your own with busses and literal outputs on your interface.
You can then build whatever kind of chain you want.
Sorry if that’s not super helpful. I don’t fully understand what you’re trying to do.
You have some external effects that you want to integrate in a flexible enough way so that you could route several tracks through a few, then route all of those through another.
I think you can do all of this with groups and audio tracks without using the sends.
Additionally, I think you can make an effect rack full of “external hw effect” devices and still maintain the flexibility you want. With this approach, you could save that device stack for future use.
I use a patchbay normally with a hardware chain and I would like to set up a chain that involves hardware and software. I thought that Send / Returns would do this but it doesn’t as I end up with Dry / Wet but I only want wet.
Busses might be useful for software and then into hardware but it isn’t quite as flexible as I would like
Yes, I also don’t understand what “main plus” represents.
If you want sub-busses, set them up!
Sends are going to be at 100% of whatever the results are, if you’re using external audio loop, you’d be able to set wet/dry mix. I usually use 100% there anyway.
My apologies if this has been discussed before but a search didn’t yield any answers.
Something I’ve noticed since the release of Live 12 is that many times my m4l devices will appear repeatedly (2-4+ copies of the same m4l plugin listed) in user-created tagged plugin “folders” or “collections”. I’m unsure of the proper terminology now. The problem being that it’s creating clutter and I’m concerned it will ultimately lead to missing resources if I suss out how to clean this up someday and then things stop working properly.
I’ll attach some screenshots to illustrate the problem. m4l plugs that get used very, very regularly are the ones that seem to be most likely to be repeated. (Stepic, Deviate, Opal, etc…).
Note: this doesn’t happen with any other plugin format, only m4l. In the Device folder where the actual resource files live, there is only a single copy, so the tags are what are appearing to be duplicated, I think.
Does anyone know how to stop this from happening or, perhaps, just why it’s happening? Am I making some sort of workflow mistake?
I have this issue, but I think I know what it is in my setup (this may be different for you). If you have any packs for Live that are 3rd party, and the browser has found devices in them, it will show them in this list. For example, if Live finds any imported devices in packs where the creator has done Collect All & Save, the list will show the same device multiple times. I’m not sure if there is a workaround though…
PS: Enjoying your extensive use of saved searches!
Yep this is what I do. I have a bunch of 3rd party packs and they all come with the devices added in. But as someone who tries to be organised, this was a bit annoying. There’s also the worry that you’ll potentially make a project that’s linked to a device outside the core install of Ableton.
As a result, I once attempted to simplify it by having only one reference point for each device, but honestly it ended up being more hassle because you have to then sort through each pack. In the end it was just easier to let the long list grow. I essentially now ignore the big list and only really look at use the new saved Library tabs, or add to a Collection, and just leave that list to do its own thing.
Simpler and the upcoming Drum Sampler just got a pretty sweet workflow upgrade in the latest 12.1 beta:
Drum Sampler, Simpler and Drum Racks now feature a new entry in their context menus. The entry allows to replace Simpler with Drum Sampler, Drum Sampler with Simpler, or all instances of one of the sampling Devices with the corresponding counterpart in a Drum Rack.
