Nope, just some simple old content farming. That can entail a wide variety of all the fertilizer you mentioned. I see no screenshot. Save the rest of it. In only a low number of posts, you were already on ignore list. Despite the nice features here, I can't put you on ignore twice.

For you to even type something when a simple screenshot of shell would take 10 seconds, it's pretty obvious how you should proceed.

When you make comments like this one, then to try to play the victim, trolling.

 

Last edited: Nov 4, 2025 at 9:05 PM

How can insulting your fellow craftsmen for their choice of tools make you a better craftsman, let alone human being. This is just plain pathology.

But for you curious fellow Linux enthusiasts, I uploaded these two snippets
https://limewire.com/d/7iCMi#ciqo7x5oO2

 

Last edited: Nov 4, 2025 at 10:05 PM

Let's get on to the gaslighting. This is the sort of thing that got you ignored in the first place, I'm sure.

Still no screenshot? When I see one, i will waste more of my time.

 

If you have any decency left you will apologise now, but if it's too much for your overinflated sense of grandeur, I'm looking forward to being ignored by you.

 

Yep. It is an Apple M1 with Linux Asahi on it. Well done!

 

I've just added a video of a rerun of a test that AS member Martel and I did around two years ago. We then compared max channel count on his Windows laptop vs my M1 iMac running MacOS.

We used Reaper as a DAW. Every channel had one instance each of ReaControlMIDI, ReaSynth, and ReaDelay, playing a 2-bar long 4-note chord. 44.1 kHz/24-bit, 1024 samples.

I managed to squeeze over 1100 channels before getting audible clicks. However, it was summer and I had no aircondition in a tiny room. Later in the winter I repeated the test in an unheated room and got 1475 channels on the same iMac.

Tonight I got 2835 channels using the same test project in Reaper, but this time on my M1 Pro MacBook Pro (8 performance cores) running Asahi Linux, in a moderately heated room.

https://limewire.com/d/7iCMi#ciqo7x5oO2

 

Last edited: Nov 4, 2025 at 11:27 PM

Thanks for the compliment!
I'm now getting it done on Linux but it's way less easy as I know it from windows, at least on Arch Linux.
Tried to install Bitwig over there, ended up unpacking the *.deb archive and moving the files manually
because Arch doesn't support debian packages. And for every step I had to run processes elevated
and type in my password (which I then removed through root access via the bootloader).

I might switch partly to linux as a 2nd OS but I keep beeing a windows user with a heavily modified
windows for getting rid of all that crap like automatic updates, bitlocker, online account enforcement,
TPM, AI, recall, copilot, defender, etc.

 

Only took 24 hours to come up with a workaround for a simple screenshot that would have date, and other embedded ways of showing it was actually what it is purported to be? What a surprise, still no screenshot. And only at the cost of exposing why the new user account.
And running a plugin collection that looks like it is from the Salvation Army.

Regular Mac VST3 and AU plugins cannot be loaded or bridged under Linux on M1 or Modern Apple Silicon processors. There is no macOS to Linux equivalent bridge because of Apple’s licensing and closed frameworks. Now you are going to use a Apple Silicon Mac to Run Linux, to then run a regular Windows bridge like Yabridge to run Windows plugins on a Mac. That sounds efficient.

Regular Mac VST3 and AU plugins cannot be loaded or bridged under Linux on M1. Keep that part in mind. Now emulation of Windows ARM plugins? Nice stacking of abstraction layers.

So if you are using your DAW as a tape recorder, then have over 200 channels of audio sounds impressive to idk who. Probably someone who doesn't know MacOS, but realizes they now make very fast processors for reasonable prices. That's why you are stuck running freeware software that even the PC Linux users won't even bother with inside a DAW other than Protools, Logic, Cubase. But you can always flip back to that "unimpressive" MacOS and use some real effects and synth plugins when you need to.

This makes lots of sense.

 

Last edited: Nov 5, 2025 at 12:24 AM

24 hours?
No screenshot?
New user account?

Are you drunk or simply losing it?

Look, your entire crusade is based on no direct experience with music production on Asahi Linux whatsoever, so the whole time you have been talking out of your rear end, but what you are saying now is downright pathetic.

You have made a fool of yourself and whatever you write from now on, no matter what topic, will have to be taken with a huge pinch of salt, because you don't seem to be able to control your output at all when there's something or someone you find annoying for whatever reason.

 

Last edited: Nov 5, 2025 at 12:39 AM

I migrated to Linux like 5 months ago and felt compelled to create an account to reply to this lol.

My experience so far has been great, but it's very closely related to who I am as a person (and how I see music making).

First off: migrating to Linux made me rethink how I approach music making and creativity in general. It made me more minimalistic with my plugin count, while also giving me a huge incentive for using DAW stock devices to their full extent (in my case, I use Renoise and Bitwig).

But not because the plugins don't work (I'd say 95% plugins I tried to bridge worked flawlessly, some DRM caveats). Instead, because there's a substantial loss of performance for several plugins, and specially in VST3. When I migrated I was very persistent on making Windows stuff work, and even managed to make most of the plugins work fine. Now I'm like: "if it's not Linux native I'm not bothering, unless it's something REALLY missable.". I've been dropping non-Linux native plugins like crazy. Stuff I thought I needed but never really did, and was only getting on the way of my creative process. I don't need 20 different compressors, 20 EQs, 20 reverbs, etc. I need a couple good ones of each. If you have this mentality, it helps.

So here's tip number #1: Use a DAW that has good native devices. Bitwig is perfect for Linux for this reason. I barely need any 3rd party plugins with the amount of power it has to offer.

Tip #2: If you really need to use Windows plugins (with Carla or Yabridge), stick to VST2. The performance gain is HUGE in comparison to VST3, an the UI problems are way less frequent. Ask a LLM why if you're curious, I won't bore you with the details.

Tip #3: Create separate Wine prefixes for different plugin brands - this ensures samey plugins use the same dependencies and prevents you from breaking the prefix while trying to fix a certain brand that need specific packages (such as the DXVK, which btw crashes VST3 UIs lot on my AMD GPU). You can easily do this by opening the terminal and doing this:

WINEPREFIX=<path> wineboot

Then, when installing the plugins, do

WINEPREFIX=<path-to-prefix-you-just-made> wine "Installer Name (Please Stop Putting Spaces On Installer Names, Guys).exe"

By the way, Tip #4: Use winetricks to install and manage packages for your Wine prefixes. Most plugins will work fine on a clean Wine-staging 9.21 prefix, but others will need specific stuff. The following packages are notable for fixing problems when a clean prefix doesn't work out for your desired plugin: corefonts, vcrun2022, vcrun6sp6 (some installers will give you a MFC140.dll error without this package), dgiplus, and dxvk (only as a last resort when I have the "black GUI" bug - which is fairly common on VST3s). For example, if you have the MFC140.dll error when installing plugins from a certain group:

WINEPREFIX=<path-to-prefix-you-just-made> winetricks corefonts vcrun6sp6 vcrun2022

Now just add the plugin DLL path to yabridge using the yabridgectl command (check the github for instructions) or drag and drop the DLLs to Carla Rack plugin. Ez.

People will say "Linux is a nightmare!! !1 !"

But, honestly?

Skill issue, laziness or lack of time.

If you want to get rid of your shitty OS, it will take an effort.

In fact, OS companies are profitable because people are too lazy to do their homework (or maybe they just don't have time for it, which is understandable) and want to live in a comfortable position in which the companies just handle them what they want in terms of software, customization, etc. Personally, that's lame - specially in the times we're living, where companies own more and more of our time and personal affairs. But to each, his own.

Peace out and hope this was helpful.

PS: The whole reason why I started typing this was to recommend ZL Equalizer as a full on alternative to FabFilter Pro-Q, but totally forgot while yapping.

Go check it. Has linear phase mode, different processing modes, etc. Worth checking.

 

You’ve been using Linux for five months, you say? Who says Linux is so difficult? Look at you, you seem to have figured it out just fine....

Getting rid of your terrible OS is as simple as grabbing a flash drive. Download a distro ISO to create a live-Linux pendrive. Use Rufus, Balena Etcher, Ventoy, or any USB tool you like. You could even dust off the good old UNetbootin, though that’s been around so long before your epiphany those five months ago, it's nearly obsoleted. Once at a shell, fire up a partition tool like GParted, GNOME Disks, or libparted, wipe any partitions, rebuild the table, and format the disk however you want. Install the bootloader your distro recommends—Grub is standard—and drop the installer onto the brand-new partition. Done in an hour or less. Debian-style upgrades? apt-get update && apt-get dist-upgrade—and you’ll still have months left to ponder how “masterful” you are. Be happy you don’t even know what LiLo is, because that part of Slackware really did suck.

But now for the truly laughable puffery from MacOS guy, more specifically:

Why would anyone in 2025 install Linux on the slowest, oldest Apple Silicon MacBook—maybe even a MacBook Air—just to run REAPER and open-source plugins, when people on the newest, fastest M4 Max Apple Studio Macs are complaining that anything under Rosetta is unbearably slow? On that Air, you’re running non-native ARM64 builds that are often slower and less efficient than Intel plugins inside Rosetta2. You’ve also tossed all the AU plugins baked into macOS, which are deeply optimized, low-latency, and studio-proven. That’s a massive downgrade in performance and workflow.

And the payoff? Essentially nothing. Almost no professional-grade plugins exist as native ARM64 for Linux or Windows, so there’s no practical gain. Track count benchmarks on non-ARM64 laptops are purely academic, artificially generated numbers that rarely reflect a real project. Nobody in a real studio cares how many tracks a laptop can purport to show, and those numbers are seldom verified objectively. In the end, this is Running Linux to Say You’re Running Linux 101: slower plugins, fewer options, zero real-world benefit, and yet somehow the bragging rights you are trying to cling to. That dual boot is still dual boot for a reason. And still no....well you get the idea.

 

"Mummy, mummy, those boys over there play with their ugly toys and I tell them that my toys are so much better and they still play with their stupid ugly toys and I tell them they are stupid and they still play with them boohoo mummy nobody loves me!"