typical AI mambo jambo which we deserve

 

The VU900 plug-in won't load and isn't showing up in Logic's Plugin Manager.
I've codesigned it and restarted the DAW as per the developer's instructions but... nothing.
If I try to load it with BC Patchwork it tells me that VU900 isn't compatible with 64-bit.

Is it just me or is anyone else having the same problem with this plug-in?

 

Last edited: Dec 20, 2025 at 2:06 PM

VU900 - BETA-20251220T142913Z-3-001

Spoiler: The enclosed installation instructions:

The enclosed installation instructions:

Installer will install VU900.vst into Program Files/Common Files/VST3

If You want to install it in different place, download VU900.vst3
(Google drive will pack You this into zip) unzip it and then copy VU900.vst3.

Installer is not certificated so antivirus software can do some trouble.
But don’t worry. There is no bitcoin miner in there.

The plugin works in: Windows 11 / VST3 / PreSonus - Studio One
I was able to import a wav sample and the main control is working!

 

adjust the folder location and run this command to see if it has a matching binary slice to your cpu architecture:
file /path/to/VU900.component/Contents/MacOS/VU900

The error is typically from a cpu architecture mismatch with the plugin.

 

/path/to/VU900.component/Contents/MacOS/VU900: cannot open `/path/to/VU900.component/Contents/MacOS/VU900' (No such file or directory)

 

You need to replace the /path/to/ with the actual path where the file resides, best done with dragging the file to terminal window after the "file" command. Should look something like this:
file /Library/Audio/Plug-Ins/Components/Aalto.component/Contents/MacOS/Aalto

(I made this with different plug-in because I don't have the VU900). You need to "show package contents" on the VU900 component and navigate to the proper file and drag it.

 

file /Library/Audio/Plug-Ins/Components/VU900.component/Contents/MacOS/VU900
/Library/Audio/Plug-Ins/Components/VU900.component/Contents/MacOS/VU900: Mach-O 64-bit bundle arm64

It seems it's 64-bit... Then I wonder why Logic/Monterey doesn't see it? Good question...

 

It seems it's only for ARM (m1 etc) Macs. Do you have older Intel Mac? Is there another download with Intel version maybe?

 

Yes, I think it's only for Arm. I didn't see a file for Intel this morning but... now Discord won't let me log in anymore.

 

VU900 - BETA-20251220T142913Z-3-001 - NFO from 19.12.2025

Download the ZIP file

Unzip

VU900.component goes to Library/Audio/Plug-Ins/Components

VU900.vst3 goes to Library/Audio/Plug-Ins/VST3 (if the folder doesn't exist, create it)

Try to test if it works for you. If your DAW shows that VST/AU is corrupted, then:

COMMAND+SPACE

Enter terminal

In the terminal, enter the command depending on whether it's VST3 or AU.


VST3:

sudo xattr -dr com.apple.quarantine /Library/Audio/Plug-Ins/VST3/VU900.vst3


AU:

sudo xattr -dr com.apple.quarantine /Library/Audio/Plug-Ins/Components/VU900.component


After entering the command, you'll be prompted to enter your password—this is the password you use to log in to your MacBook (the terminal doesn't show you're entering a password).



It's worth restarting your DAW and scanning your plugins again.

If you had to take these additional steps, let me know. If not, let me know as well. In theory, this should work without a problem.

 

Usually different versions should in the same package anyway. Maybe Intel version will come later since this thing is only in beta, but maybe there won't be intel version at all. Maybe the Discord channel will have more info about this.

 

I believe the problem is due to the fact that the plug-in is only for Arm (I'm on Intel).

 

@aymat Don't get mad at me but may I please have a copy of

 

The file command will show this: Mach-O 64-bit bundle x86_64 if there is an intel slice. This plugin shows ARM only in your result. I put the placeholder "vu900" path/to location as the "file" command doesn't really look like one without an example path.

 

Last edited: Dec 20, 2025 at 8:55 PM

I assume that you just pasted that info from elswhere. And that info is bulshit. (So take no offence.)

11.75 second DOES NOT PRESERVE the S900 workflow. Because that sampling time was available when using the 40 kHz sampling rate in the Akai (and 40 kHz is not available in the plugin!). But in the original sampler you could have much more sampling time when you lowered the sample rate. At 7.5 kHz we could have as much as 63 seconds on the Akai.
So it looks that this plugin is not an S900 emulation at all. It it just very loosely inpired.

 

Last edited: Dec 20, 2025 at 8:32 PM

Sorry for the incorrect statement. This source should be true: Source: www.muzines.co.uk/articles/akai-s900-sampler/1931

Akai S900 MIDI Digital Sampler

Maximum sample rate
40kHz = 16kHz audio bandwidth, 11.878 secs max

Minimum sample rate
7.5kHz = 3kHz audio bandwidth, 63.351 secs max

The fact of the matter, though, is that you're unlikely to need the lowest bandwidth available, as the S900 has enough memory to cover the multi-sampling of most instruments quite comfortably at much higher quality.

It's also possible to adjust the audio fidelity very precisely, so you can use the exact bandwidth necessary to capture any sound and not be forced to use lower or higher fidelity simply because your machine can only manage one or two sampling rates. By offering a continuously variable sampling rate, the S900 makes the most economical use of the generous memory available, so you get the best of both worlds.

In fact, I soon discovered that 13-14kHz bandwidth was more than enough for most sounds, though there will always be more 'difficult' instruments (cymbals, high piano notes and the like) which need all the headroom they can get. My only grumble in this department is that there's no way the more experienced sampler (the user, not the instrument) can get an exact measurement of the sampling rate being used. If there was, you could match the sample frequency to a multiple of the pitch of a musical note for optimum fidelity.

 

Where 11.75 seconds comes from:

A modern plugin usually flips the logic from what the programmer is trying to emulate.

Instead of: Heres is the RAM, choose a sample rate
It does: Here’s a fixed maximum sample count, everything else adapts

For example, a developer might decide max_samples = 524,288. That number isn’t musical — it’s 2¹⁹, a power of two.
Programmers love these because: memory alignment is easy, DSP code is simpler, No dynamic allocation edge cases.

Convert that to time. At 44.1 kHz: 524,288 ÷ 44,100 ≈ 11.88 second

All of these complaint comments look like some Google research to me anyway. Just something to bitch about. It's not going to parachute onto anyones hard disk without buying it.

 

That’s exactly the same phrase ChatGPT repeats when I catch him on lying or what is being politically correct called hallucinations

Pulse arent you tired of this buffoonery trying speaking on themes you don't understand?