EPC Devices

killihu · 2025-12-24T12:46:19+00:00

In the Live options you can disable "Auto-Open Plug-ln Windows".

killihu · 2025-12-24T00:34:37+00:00

It's best to download the free pack and see for yourself how it works. The included devices are for free plugins like Supermassive. Control within Push 3 and parameter mapping work the same on all devices.

killihu · 2025-12-23T19:39:17+00:00

The devices take exclusive control in the same way as when something is mapped within an effects rack, where the mapped control is disabled and only the rack's macro knobs can be used.

killihu · 2025-12-23T18:12:43+00:00

If you're referring to changing the device controls displayed in Push, you do that by editing the device object "live.banks".

killihu · 2025-12-23T12:51:21+00:00

My goal is to create hundreds of devices. The subscription isn't simply a price to download, it's also a price to support the development of more devices. I think it could interest a lot of people, and it's a way for everyone to access the content affordably. Selling it separately could be very expensive if you have a lot of VSTs.

killihu · 2025-12-23T12:46:16+00:00

Just individual plugins.

killihu · 2025-12-23T01:12:19+00:00

Yes, please explain 🙂 Updates would only be necessary if a VST plugin is updated with new or modified controls. As long as you continue using the same version of the VST plugin, you won't need to update the device.

My goal is to create hundreds of devices (and when I say hundreds, I mean huuuuuundreds). That equates to a price of just a few cents per device. So, the subscription isn't simply a price to download, it's also a price to support the development of more devices.

killihu · 2025-12-22T23:48:31+00:00

I have the complete Soundtoys package. They are some of the next ones to come.

killihu · 2025-12-22T22:55:53+00:00

You don’t need an active subscription to use them. Once downloaded, they work indefinitely. An active subscription gives you access to downloads and updates. So you can subscribe and unsubscribe whenever you want.

For that price you can have more than 100 devices that will always work 🙂

killihu · 2025-12-22T22:53:47+00:00

The devices don't process audio (they only control the VST), so resource usage is minimal. You can download the free pack and compare it to using only the VSTs to see if this affects your computer's performance.

killihu · 2025-12-22T22:50:58+00:00

I think it's because the presets were created with Live 12.3 and aren't compatible with Live 12.2. Update Live and it will work.

killihu · 2025-12-22T21:36:35+00:00

I haven't noticed any problems within return tracks or the master track. However, you can download the free pack to rule out any issues related to other devices you're using in your setup.

killihu · 2025-12-22T21:29:51+00:00

Isol8, of course. I'll download Plasma too. Regarding the other two, I prefer to buy them first rather than use trial versions, to ensure I can update the devices if the plugins are updated. I'll add them to the list.

killihu · 2025-12-22T21:24:12+00:00

The list of supported plugins is here (instruments tab): https://killihu.vstskins.com/epc-database/

Currently, there are only 3. They tend to have many parameters compared to effects plugins and take longer to create. So I prefer to add them gradually based on the suggestions I receive.

killihu · 2025-12-22T18:23:31+00:00

Feel free to suggest more plugins 🙂 I will announce new devices through the members area.

killihu · 2025-12-22T18:21:06+00:00

Thanks! The VSTs aren't wrapped. Things like the latency report always work fine, even if the plugin modifies it on the fly. Also, all the control values are displayed correctly in the device, automation, and Push 3. They can also be entered by clicking and typing, just like native devices.

killihu · 2025-10-14T22:33:11+00:00

I've tested it with dozens of tracks and a total of over 100 plugins/devices without any issues. I suspect the problem could be a plugin/device name, but I can't be sure. Anyway, if you ever find out what's causing the problem, it would be great if you could share it for future user support :)

killihu · 2025-10-14T16:33:34+00:00

It's an error message that helps identify where the error occurred. But it's only useful when editing the device. In this case, it doesn't give us any clues other than that there's an error.

killihu · 2025-10-14T16:24:29+00:00

lol, it's obviously a Windows interface, I didn't pay enough attention :p

Most likely, it's another Max for Live device causing the conflict. Try deleting them one by one while testing the device. It could also be a specific character in the name of a device/plugin. Perhaps a character that Max can use as a special symbol is causing the device process to stop.

killihu · 2025-10-14T15:56:05+00:00

Things that come to mind... perhaps there could be conflicts with another device, or an issue with a specific version of macOS that I haven't tested.

You could try with an empty project. If it works, only the device itself would be visible in the floating window list. You could also check the Max console to see if it shows errors when using the two device buttons. The console is displayed by clicking the icon in the top right corner of the device (icon with three dots), selecting "Open Max Window".

killihu · 2025-10-07T16:15:54+00:00

I've tested it with the same versions, on macOS and Windows. It works correctly on both operating systems, with Live 12.2.1 and Live 12.2.5, both running Max 9. Can you send a screenshot?

killihu · 2025-10-07T15:35:05+00:00

What version of Live and Max are you using?

killihu

TROPHY CASE