v5 Browser regressions

[pdxindy]

It would be nice if in v5 they implemented an option to use the old browser as well, for example Settings -> User Interface -> Use old browser (Bitwig must be restarted)

There is no chance they are going to do that.

[BobDog]

I think I must be Mad as I think the new browser is great, a few tweaks is all it needs.

For me a major improvement!

[simmo75]

I much prefer the old browser too. Shame they changed it really. The thing that is most irritating is that you used to be able to open it and type, now you have to open it, click in the search and then type. It’s the little things…

[pdxindy]

I much prefer the old browser too. Shame they changed it really. The thing that is most irritating is that you used to be able to open it and type, now you have to open it, click in the search and then type. It’s the little things…

That is a bug... When I open the new browser, the search is always in focus and I just type.

[moxxi]

It would be nice if in v5 they implemented an option to use the old browser as well, for example Settings -> User Interface -> Use old browser (Bitwig must be restarted)

There is no chance they are going to do that.

Very likely, but it would be nice to have an option for the old browser as well. If it doesn't happen, it doesn't matter, I'll get used to the new one. I'm just saying that having that option would be desirable for some users.

[simmo75]

I much prefer the old browser too. Shame they changed it really. The thing that is most irritating is that you used to be able to open it and type, now you have to open it, click in the search and then type. It’s the little things…

That is a bug... When I open the new browser, the search is always in focus and I just type.

Not surprised, there’s been a few issues.
Erica Zen Delay plugin vst3 version seems to be screwed since v5

[nekavoq]

Very grateful that Beta 6 added the alphabetical sort, but man, after using it and genuinely trying to love it for the past few days, I'm constantly in a state of yearning for the older browser's UX. While I'm happy to hear that some of you are enjoying it, to me the new browser doesn't feel like moving forward, it feels like they outright changed lanes and slowed way down. I wouldn't say it's objectively bad, but I can say with certainly that it definitely loses the immediate efficacy of the old browser.

Here's to hoping Bitwig adds a separate UX option that more closer resembles the old browser in the future. Until then, and in a morbid sense I'm glad to know I'm not alone, it looks like those who preferred the old browser will simply have to carry on and deal with the UX downgrade, or make the difficult decision to stay on v4.

Personally, I'll probably still use Bitwig; but, and it genuinely pains me to type this out, I am genuinely starting to feel like the browser UX downgrade is bad enough for me to let go of global modulators and to restart and redo multiple projects I already am working on in v5 with v4.

I don't know man, I genuinely tried. Maybe if I had never used v4 I would've been fine with v5's browser; but it's very much because I am hyper aware of how good v4's browser was at getting a item I needed as quick as possible that v5's feels terrible in comparison. Like, mass produced sliced bread isn't bad, and if that was all you had, your life would be totally fine; but that changes when you were originally consistently fed some good ass fresh bakery bread, and then suddenly lose access to a bakery when you're supposedly moving house to somewhere "fancier", leaving only mass produced sliced bread; you won't die due to lack of bakery bread, but the constant reminder of having had something significantly better will haunt you for as long as you eat that mass produced bread.

Half-baked analogy I know, but the takeaway here is that I appreciate good ass bread as much as I appreciate good ass UX, and I'm honestly and wholeheartedly disappointed at the thought of losing it for no good discernible reason.

[iowastate89]

It would be nice if in v5 they implemented an option to use the old browser as well, for example Settings -> User Interface -> Use old browser (Bitwig must be restarted)

There is no chance they are going to do that.

Very likely, but it would be nice to have an option for the old browser as well. If it doesn't happen, it doesn't matter, I'll get used to the new one. I'm just saying that having that option would be desirable for some users.

I'm going to visit them at Superbooth and mention this in person

[pdxindy]

I much prefer the old browser too. Shame they changed it really. The thing that is most irritating is that you used to be able to open it and type, now you have to open it, click in the search and then type. It’s the little things…

That is a bug... When I open the new browser, the search is always in focus and I just type.

Not surprised, there’s been a few issues.
Erica Zen Delay plugin vst3 version seems to be screwed since v5

There are also still a few key commands that are supposed to work but don't.

These things are why there is a beta

[pdxindy]

It would be nice if in v5 they implemented an option to use the old browser as well, for example Settings -> User Interface -> Use old browser (Bitwig must be restarted)

There is no chance they are going to do that.

Very likely, but it would be nice to have an option for the old browser as well. If it doesn't happen, it doesn't matter, I'll get used to the new one. I'm just saying that having that option would be desirable for some users.

There's no way they are going to maintain two codebases. It will never happen.

Better to focus on how you might like to see the new browser improved. That there is a chance of. They have already responded to user requests in that regard.

[carlca]

Half-baked analogy I know,

I see what you did there

[carlca]

Not surprised, there’s been a few issues.
Erica Zen Delay plugin vst3 version seems to be screwed since v5

Interesting! I’m using beta 6 on macOS 13.3.1 Ventura and Erica Zen Delay VST3 works perfectly here. What OS are you using?

[simmo75]

Not surprised, there’s been a few issues.
Erica Zen Delay plugin vst3 version seems to be screwed since v5

Interesting! I’m using beta 6 on macOS 13.3.1 Ventura and Erica Zen Delay VST3 works perfectly here. What OS are you using?

Interesting indeed, beta 6 on Mac OS 13.3.1 Ventura… it is not working properly here.
When I reopen a project with zen delay in, it causes a huge cpu spike and zen delay no longer works

[pdxindy]

Not surprised, there’s been a few issues.
Erica Zen Delay plugin vst3 version seems to be screwed since v5

Interesting! I’m using beta 6 on macOS 13.3.1 Ventura and Erica Zen Delay VST3 works perfectly here. What OS are you using?

Interesting indeed, beta 6 on Mac OS 13.3.1 Ventura… it is not working properly here.
When I reopen a project with zen delay in, it causes a huge cpu spike and zen delay no longer works

Maybe you are both using different plugin sandboxing settings?

[carlca]

Interesting indeed, beta 6 on Mac OS 13.3.1 Ventura… it is not working properly here.
When I reopen a project with zen delay in, it causes a huge cpu spike and zen delay no longer works

Maybe you are both using different plugin sandboxing settings?

That might well be the problem…

SCR-20230504-ihcj.png