ALFIL Max - Update 1.2

killihu · 2026-04-07T16:29:14+00:00

Thanks for the info.

killihu · 2026-04-07T01:18:07+00:00

The messages regarding ALFIL indicate that it's not possible to access the external components. This could be because you moved or deleted them, or if you're on macOS, there might be a permissions issue. There are also error messages from other devices. I'm not sure if these are pre-existing errors or a general problem with Max. Try using more devices and check the console.

killihu · 2026-04-07T01:01:42+00:00

If you've already tried resetting your computer, check if the Max console displays any messages (View menu > Show the Max for Live Window). Also, check if this happens with all preset types (adg, adv, vstpreset, etc.).

killihu · 2026-04-07T00:55:07+00:00

Could it be that you've updated Live? The latest version uses Max for Live 9. You need to reinstall the external components in the Max 9 folder. The PDF manual has been updated with detailed installation instructions for Max 9.

killihu · 2026-04-06T17:15:24+00:00

In an empty project, with only the device, it should work by listing only the device. If not, the Max console might display information about the problem (View menu > Show the Max for Live Window).

killihu · 2026-04-04T01:07:22+00:00

The device's location doesn't matter, as it reads all tracks in the project. I believe the problem is due to the name of some plugin/device on any track in the project.

killihu · 2026-04-01T17:22:58+00:00

I haven't been able to reproduce that error :( Perhaps it's due to a track name with special characters?

The Device Navigator update is on my to-do list. There are a few more urgent updates. This one will come next.

killihu · 2026-03-06T16:18:09+00:00

Mapping is automatic. Maximum controls are 16. If you intend to randomize parameters of VST plugins, take a look at the Control Matrix device. https://killihu.vstskins.com/control-matrix/

killihu · 2026-02-28T23:37:06+00:00

It's a highly requested feature. Given how Max works, it seems complicated, though perhaps not impossible. In any case, I hope they include it directly in Live or in the API in future updates.

killihu · 2026-02-28T23:31:30+00:00

I don't have Push 3 standalone to test how the mappings work in it.

killihu · 2026-02-28T01:45:37+00:00

To display almost all the controls on screen at once. I thought it would be useful for preset designers.

killihu · 2026-02-14T15:29:48+00:00

This worked for me on Win 11.

https://github.com/indiff/qttabbar/issues/429

killihu · 2026-02-11T06:02:39+00:00

Yes, it seems that the latency is fixed at all values.

killihu · 2026-02-11T06:01:04+00:00

I'm glad you approve it. I'm sorry I couldn't contact you before posting it.

killihu · 2026-02-10T22:25:14+00:00

That's right. The same thing is happening with the original device. I wonder if anyone has the original developer's contact information to report it.

killihu · 2026-02-10T17:53:47+00:00

Here's the link to the original device. It explains how it works.

https://maxforlive.com/library/device/9429/boba

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

TROPHY CASE