Bitwig 4.3 is out - Space & Tone (RELEASED)

[billcarroll]

I noticed several seconds freezes on OSX, when I browsed for impulse file in convolution.

Was this browsing Bitwig impulse files, or impulse files from another source?

[dupont]

I noticed several seconds freezes on OSX, when I browsed for impulse file in convolution.

Was this browsing Bitwig impulse files, or impulse files from another source?

Bitwig impulse files.

[SmajjL]

Yeah it is beta and hopefully that means they are in commit-mode to get flatty to worky and we are suppose to WhINE if we see issues.
Release Candidate's mount tip was new for me, did not know one could do that, but still hope the devs make it stupid simple or, an official manual how-to we are supposed to do it.
I did manage to lower the Pipewire buffer and BAM! all MIDI was gone as in, RIP, had to go Pulseaudio and back, and all was good again.

[lunardigs]

The pipewire implementation is just pure fantastic, major improvement here.

But: Anyone know a workaround for wine-bridged plugins (wine + linvst)? I would assume (hope!) this is solved before it's out of beta, as this is a major showstopper. Should I mount all locations of the wine installation plus the linvst installation?

Yup I love it already. I don't have to start and shutdown Jack anymore.

I don't think wine + linvst is possible unless it's built into the Bitwig flatpak.
I really hope they keep releasing .deb files!

[ReleaseCandidate]

But: Anyone know a workaround for wine-bridged plugins (wine + linvst)? I would assume (hope!) this is solved before it's out of beta, as this is a major showstopper. Should I mount all locations of the wine installation plus the linvst installation?

Yes, you have to bind-mount everything you need from the 'outside world' in the Flatpack (or Snap).
The main idea of Flatpack (-style) containers is that they run in an isolated sandbox that contains everything needed by the program and not allow access to the 'real' linux filesystem. So the solution would be to include Wine in the Bitwig Flatpack.

[SmajjL]

Yes, you have to bind-mount everything you need from the 'outside world' in the Flatpack (or Snap).
The main idea of Flatpack (-style) containers is that they run in an isolated sandbox that contains everything needed by the program and not allow access to the 'real' linux filesystem. So the solution would be to include Wine in the Bitwig Flatpack.

And add Yabridge/Linvst also?
It reads to me on your text that ReleaseCandidate can make Native Instrument stuff work Right Now, is that correct reading?
Also, I have not known for so long that if .wine name links in Yabridge have spaces to your stuff, you are supposed to yabridgectl add "blabla blabla/bla/bla bla/coffee/gevalia/"
Then Yabridgectl will not give you loveletters about errors.
Minor simple stuff like that can waste peoples time

[ReleaseCandidate]

Yes, you have to bind-mount everything you need from the 'outside world' in the Flatpack (or Snap).
The main idea of Flatpack (-style) containers is that they run in an isolated sandbox that contains everything needed by the program and not allow access to the 'real' linux filesystem. So the solution would be to include Wine in the Bitwig Flatpack.

And add Yabridge/Linvst also?
It reads to me on your text that ReleaseCandidate can make Native Instrument stuff work Right Now, is that correct reading?
Also, I have not known for so long that if .wine name links in Yabridge have spaces to your stuff, you are supposed to yabridgectrl add "blabla blabla/bla/bla bla/coffee/gevalia/"

If the libraries on the local and the Flatpack system are compatible (I don't know what libraries Wine links against), then this should work, yes. But may be that almost the whole system has to be linked into the flatpack for that to work.

[SmajjL]

Yes, you have to bind-mount everything you need from the 'outside world' in the Flatpack (or Snap).
The main idea of Flatpack (-style) containers is that they run in an isolated sandbox that contains everything needed by the program and not allow access to the 'real' linux filesystem. So the solution would be to include Wine in the Bitwig Flatpack.

And add Yabridge/Linvst also?
It reads to me on your text that ReleaseCandidate can make Native Instrument stuff work Right Now, is that correct reading?
Also, I have not known for so long that if .wine name links in Yabridge have spaces to your stuff, you are supposed to yabridgectrl add "blabla blabla/bla/bla bla/coffee/gevalia/"

If the libraries on the local and the Flatpack system are compatible (I don't know what libraries Wine links against), then this should work, yes. But may be that almost the whole system has to be linked into the flatpack for that to work.

For a short while i did flip out abit and gave the Whole Planet permissions just to see if i could get it to work, but i don't think we are suppose to do that so i did some meditating and come back to my sences
I think Bitwig will try to make this moron-proof i hope before they go out of beta

[Beamboom]

I don't think wine + linvst is possible unless it's built into the Bitwig flatpak.
I really hope they keep releasing .deb files!

I just received a message from Bitwig support that indeed DEB files will be back again with the next release! So it seems they've discovered that sandboxing the DAW wasn't such a great idea for many of their users.

Phew - that was good, because I saw myself having to extract the app from each flatpak and manually install it from here on out. That'd be a drag, to put it mildly.

[SmajjL]

I know Fedora scripts can convert, I know Arch/Debtap can convert, I know Debian based won't complain and, the flathub version can stick around? all back to normal? What are we suppose to be complaining about now? *;)
Thankz you gang and, Bitwig-people

[kurt008]

I know Fedora scripts can convert, I know Arch/Debtap can convert, I know Debian based won't complain and, the flathub version can stick around? all back to normal? What are we suppose to be complaining about now? *;)

If you know how - nice for you. But I'm pretty sure I'm not the only one who doesn't know!.

BTW... Even though music producing is a hobby of me (still ... yet), I know for sure, that no real full time producer is willing to spend time for such a fumbling inside an operating system only for reasons based on convenience. There are already not little producers who avoid Bitwig Studio for reasons of distraction (well... that is an individual point of view, of course...), but ... system works only to make a DAW running with all hard- and software, which - before such an infantile change - worked seamlessly, is simply a very bad joke and everything worth than a 400€-license!
Of course "Never change a running system" leads to living corpses, to software-zombies over time, but changing software without a reasonable testing is simply a big mess, a lot of users frustration and hardly is worth much money!

And we even don't know by now, if all the hardware (and of course the software necessary to run them together with the system) was really fully compatible with that so-called "solution".

To say it in clear words: A solution is worth to be called a solution, if it helps the majority of users. And that's definitely not the case concerning flatpak.

[kurt008]

I don't think wine + linvst is possible unless it's built into the Bitwig flatpak.
I really hope they keep releasing .deb files!

I just received a message from Bitwig support that indeed DEB files will be back again with the next release! So it seems they've discovered that sandboxing the DAW wasn't such a great idea for many of their users.

Phew - that was good, because I saw myself having to extract the app from each flatpak and manually install it from here on out. That'd be a drag, to put it mildly.

That's good. I found out soon, that Bitwig Studio was unable to "see" folders in my directory, that me as user was able to open as usual, but belong to root. So all my plugins installed under /usr/lib were gone (VST-i-2 and VST-i-3)... and as a non-Linux-professional I had no idea in the beginning where to search for the real source of this problem...
And to be honest: I'm slightly angry, that - instead of trying something new out and keeping the old system alive - they simply changed it without any announcement or even own experiments (which would have shown them these problems without a doubt very quickly).
First they even had changed the 4.2.4 Pre-Release to flatpak (as far as I have recognized), but that was changed back to .deb meanwhile.

I'm not happy about such "surprising solutions", because they cost lots of unnecessary time which I urgently need elsewhere. Hopefully they learn from this miss.

[Tj Shredder]

I'm not happy about such "surprising solutions", because they cost lots of unnecessary time which I urgently need elsewhere. Hopefully they learn from this miss.

Hey its a beta, you should expect exactly that. If you don‘t want to waist time on this kind of issues, simply stick with stable releases…
I hope you learn from this miss and read the warnings which come with betas…

[kurt008]

I'm not happy about such "surprising solutions", because they cost lots of unnecessary time which I urgently need elsewhere. Hopefully they learn from this miss.

Hey its a beta, you should expect exactly that. If you don‘t want to waist time on this kind of issues, simply stick with stable releases…
I hope you learn from this miss and read the warnings which come with betas…

This change did not only concern the Beta!

There are conventions concerning the usual location of VST(i)(3)'s in a usual Linux system (at least for Debian-based machines. A software made for this type of Linux-system, which doesn't care about such existing default paths is at best Alpha in my eyes, instead of Beta. And - as already stated - this concerned at beginning the 4.2.4 Pre-Release as well.

[Tj Shredder]

I'm not happy about such "surprising solutions", because they cost lots of unnecessary time which I urgently need elsewhere. Hopefully they learn from this miss.

Hey its a beta, you should expect exactly that. If you don‘t want to waist time on this kind of issues, simply stick with stable releases…
I hope you learn from this miss and read the warnings which come with betas…

This change did not only concern the Beta!

Ok, I didn‘t know, I follow Linux issues only occasionally out of curiosity…