All my windows vst work great and with pretty much no configuration with yabridge. I think some heavy drm’ed vsts are a bit more problematic but most (all in my case) work.
You need to run sudo apt update before trying to install things. Notice that you’ll need to do this every time unless you installed Kali with some permanent storage. Which is why it’s usually a better idea to just use your day-to-day Linux box for stuff, Kali is for when you want to not leave traces and not allow any backtrack to get to your actual system, for most non red team related stuff you don’t need Kali.
It’s good to know amp sims and VSTs on Linux have come far! The drums still aren’t where I’d like them to be to switch and I’ve tried several times to get Steven Slate Drums and Superior Drummer working with a VST bridge in Ubuntu Studio, with no luck. Still sticking with Apple for now, but at least I finally have Windows out of my house.
And it’s thanks to the work of those people that it has finally made it upstream, specially Fedora’s Martin Stránský (who has been doing tons of work on Firefox, including making Fedora the first distro to ship Firefox with VA-API enabled by default).
Silly question but does that include Fedora spins like the KDE spin? I think the last time I checked Firefox it still said it was running through XWayland (although that was a while ago)
Honestly, I haven’t explored Vulkan yet. I initially chose GLES 2.0 as the primary renderer to ensure compatibility with a wide range of hardware. Introducing Vulkan myself would be a time-consuming task unless I receive assistance.
Regarding XWayland, Louvre doesn’t currently support it, so it’s naturally excluded. Well, it technically can run in rootful mode, but that is somewhat pointless. To enable independent window management, I believe I would need to create a mini X server, a task I haven’t tackled as of now.
Probably all of them have better Vulkan than opengl drivers (due to drivers being simpler). David Arlie rather quickly implemented first Vulkan driver for AMD once Vulkan was first released. Just in case you need incentive.
I was thinking of starting something similar as a learning exercise, but I’m really limited in time and not skilled as much in c++, so it would probably lead nowhere. Now I can just build on top - if I get any time for this, will come probably with questions.
Anyway, this idea was to make something modern. Without the legacy crap. Actual goals were:
Vulkan only (move gfx API Info the future)
no x/xwayland (most of the apps in newer toolkits already support Wayland, the others I’d rather avoid)
Interesting, I don’t recall where I read about Vulkan support still being experimental in many Mesa drivers; it might have been an outdated post. I’ll look into it, and perhaps I’ll decide to dive into learning Vulkan. Additionally, there are buffer-sharing mechanisms that already work smoothly with GLES, so I need to explore if the situation is similar for Vulkan. Thanks for your response, and if you have the time and inclination to help include it, feel free to do so! 😄
Fucking any of them. Seriously. It doesn't really matter. Eventually you'll come to the realization that until you're talking about oddball shit designed for one douchebag's personal proclivities it's all the same shit under the hood. They just have fourteen incompatible package managers because, again, douchebag personal proclivities.
Our school systems are admined by teachers with only half a clue of what they are doing with only a few hours per week as a budget. This isn’t meant as an offense, math teachers that like to fiddle with computers in their free time are just not qualified to run the infrastructure for schools
The idea of single, double, and triple buffering revolves around how many framebuffers we use for display rendering. Typically, we go with double buffering, displaying one framebuffer while rendering happens on the other. Swap them, and the cycle continues. The goal is to prevent screen tearing and glitches from popping up on the screen.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.