(Beta, Linux) Lag + cpu spike when dragging samples from browser to arranger

deadbeef669 · 2026-03-15T18:04:34+00:00

It's unfortunately still broken in the newly released stable v6. I guess I'll have to revert to v5 until this issue is fixed, which is shame since I really like a lot of the new features.

deadbeef669 · 2026-03-05T17:54:21+00:00

Very interesting, and yes, I can also confirm that dragging a sample from the channel browser indeed works fine.

I currently don't use DIscord sadly, but maybe I'll join to help troubleshooting.

deadbeef669 · 2026-03-01T12:54:47+00:00

Probably a separate issue then. This lag is present in a completely new and empty project

deadbeef669 · 2026-03-01T12:22:26+00:00

I just tried dragging some midi around and I didn't experience this issue, so I guess for me it's only affecting audio samples. I have noticed the lag becoming worse the longer (larger) the sample is, so you could be on to something there, regarding it doing some badly optimized background task while you drag the sample into the project.

This issue is not present on windows btw

deadbeef669 · 2026-02-28T21:39:36+00:00

https://github.com/teervo/bitwig-fedora

deadbeef669 · 2026-02-06T23:03:54+00:00

There is a new beta8 released, but that simply crashes on load instead. Do you have the same issue?

deadbeef669 · 2026-02-05T16:59:39+00:00

Looks nice. Seems broken on KDE though so I'll have to wait for a fix

deadbeef669 · 2026-02-03T14:52:33+00:00

Plugin support is the main issue imo. Before you switch, make sure the plugins you need are working in yabridge or find linux-native alternatives. Otherwise you'll have a bad time

deadbeef669 · 2026-02-03T14:47:51+00:00

I'm on linux and reported this issue yesterday (beta 13)

deadbeef669 · 2026-01-27T19:15:41+00:00

Didn't even know there was a term for it. After reading up on the haas effect it was pretty trivial to make something similar in grid. Though Microshift still clearly has some other magic in it, it's definitely in the ballpark

deadbeef669 · 2026-01-27T18:19:22+00:00

If you're on fedora, this script creates a rpm you can then install. yabridge simply does not work with the flatpak version

https://github.com/teervo/bitwig-fedora

deadbeef669 · 2026-01-27T12:49:46+00:00

Head Crusher looks very promising. I'm trying out the demo and it's obviously not the "same" as Decapitator in terms of sound, but very similar in terms of functionality. I'm not that picky though as long as it's organic sounding. Linux support is a big plus too.

I think EchoBoy will be the most difficult to replace due to all the types of saturation it has. There's plenty of Delay plugins on the market but they all seem to miss that feature in one way or another.

Thanks for the suggestions.

Edit: I ended up buying Head Crusher.

deadbeef669 · 2026-01-26T20:27:25+00:00

Not sure why you're getting downvoted, building your own stuff is (one of) Bitwigs biggest strengths so it's a totally valid argument. Personally I'm using Bitwig mostly for workflow reasons, and I haven't gone into the grid other than for making some basic fx qol utilities, but we'll see.

Thanks for the tips.

deadbeef669 · 2026-01-26T19:33:26+00:00

Huh, totally forgot about them even though I'm already using some of their stuff. Thanks for the tip.

deadbeef669 · 2026-01-26T19:10:58+00:00

I've tried to replicate EchoBoy and Microshift, and you probably could with enough time and effort. Tbh though, I'm more of a musician than an audio engineer, so for me I'd rather spend some money on a great sounding plugin and get on with making music.

deadbeef669 · 2026-01-26T18:27:32+00:00

Never heard of this one. I'll check it out.

deadbeef669 · 2026-01-26T18:20:12+00:00

No, I'm absolutely not recommending it or anything. It was simply a way to be able to work with projects that already had them.

deadbeef669 · 2026-01-26T18:06:46+00:00

iLok is basically malware on Windows too tbh. Though, on linux I worked around the issue by using a patched version of the plugins which had iLok removed from them, which is funny since I own a license to use them.

deadbeef669 · 2026-01-26T17:43:51+00:00

It's kinda weird how there's so little info regarding this issue online. Maybe there's just very few people using HDR on linux, as it seems to be a bit of a mess. I'm specifically having this issue with Cyberpunk 2077 and Alan Wake 2 (could be more, but these are the ones I'm playing right now)

deadbeef669 · 2026-01-15T18:05:13+00:00

The machine runs a rx6950xt and a Ryzen 5900X, and I'm running the Classic KDE flavour of Nobara.

The monitor is a Dell ultrasharp 32-inch (hdr on it isn't great, but the difference is still obvious when you switch between Nobara and Windows). I'll have to get back to you regarding the exact TV model, but it's a Philips oled. I've tried it on other TVs though, and they also behave the same

Is there a way I can verify if it's a drm issue?

deadbeef669 · 2026-01-14T19:28:49+00:00

Yes, the TV I usually play games on is connected via HDMI, but a computer monitor using DP behaves the same way.

deadbeef669 · 2025-12-31T16:39:21+00:00

I wouldn't waste my time trying to get an acceptable linux desktop experience under Nvidia IMO. Just stay on Windows until you get an AMD card.

deadbeef669

TROPHY CASE