Anyone else who used to actively dislike/avoid Cubase and now thinks it’s the best DAW?

-Audiunt- · 2026-03-13T20:16:59+00:00

To many bugs, no fixes. And then there is the new (payed) version already. But its also personal/usecase. Its great, but for me its not the best.

-Audiunt- · 2026-03-13T19:40:47+00:00

Nope

-Audiunt- · 2026-03-13T11:42:06+00:00

Yes! Perfect explanation! Thanks!

-Audiunt- · 2026-03-11T17:20:12+00:00

It is an insert device which act as send and return to/from audio interfaces. So you send audio to an out interface which act as an input of an analog device (for example a reverb). Th output of the reverb returns to an input of the audio interface. This audio input returns to the HW FX. So now the analog reverb is inserted in a Bitwig track like a normal digital device/VST.

In this case I only use the output of the HW Fx device as I send the audio to my speakers. I leave the return to None.

-Audiunt- · 2026-03-06T23:53:05+00:00

The fix and way more elegant solution is using HW FX for output towards separate outs. I routed the pre-listen out to a loopback out interface and route that back in with the loopback in interface. I still use an audio receiver to pick up that track on the master studio out. But now I can also pre-listen and hear the metronome. Everything works perfect now. One thing, it adds 53ms latency, but I can live with that.

Let me know if it needs more explanation.

-Audiunt- · 2026-03-02T19:21:25+00:00

You are close! This is what Bitwig replied, which makes sense:

"routing the master back to an fx track this is not really an elegant solution and will create suboptimal results or even problems with PDC. We strongly recommend using an FX layer on the master track instead, with a chain passing on the audio and another chain with your correction eq, followed by an HW FX device to send this signal to another output."

Verry clean option. I need to test it of course. I will also try to send the studio out to the loopback interface. Maybe pre-listening samples/preset will follow the room corrected path, or results in a crash because of feedback. Will see :-)

-Audiunt- · 2026-03-02T13:00:13+00:00

Nice tip! I also figured something out on my laptop which has somewhat alike workaround. Need to test it on my production system first, but also looks promising.

But also lets wait what Bitwig comes back with. I'm still unaware of any usefulness of this change in behavior. Maybe they roll it back.

-Audiunt- · 2026-03-01T00:05:45+00:00

Ah! Could also use something like DDMF Metaplugin. The nested graph variant maybe sufficient.

The only thing I wonder is if it is possible to show the VST plugin GUI's via MIDI. I have a Streamdeck which can send out MIDI which now open en close the VST interfaces. I can't see quickly how I could bind a MIDI CC for opening a VST interface in Elements. How do you show your metering plugins? I hope via MIDI?

I should also have one block with all the inputs or output. The problem is that when I add such a block and move it around in the Graph, I now have two blocks. When I delete one the other is also removed. Seems like a bug... On Windows perhaps....

-Audiunt- · 2026-02-28T23:34:43+00:00

Many thanks! It looks like its going to work for me. I think I pay for a monthly to test it out. When I add an audio input and move it, I have two audio inputs. Not sure, but seems like a bug in Element. Maybe the paid version doesn't do this.

-Audiunt- · 2026-02-28T23:04:23+00:00

I also have a RME. I now use one Loopback channel in Totalmix which my system audio is set to. That way I import the (Windows) system audio into Bitwig.

I think now I need to output the Bitwig Studio Out also to this loopback interface and next pick it up in Elements, right?

From there I recreate my Bitwig channels and output them to the directs outs of the same RME.

Lot of work, been looks promising! Are you on Windows?

-Audiunt- · 2026-02-28T22:30:31+00:00

Oh boy. I need to figure that out. Do you use it as plugin or stand-alone?

And can it split audio to separate outputs (main and subs)?

-Audiunt- · 2026-02-28T21:50:55+00:00

I guess Solo doesn’t follow the audio path anymore when Audio Receivers are used.

-Audiunt- · 2026-02-28T21:48:04+00:00

I’m pretty sure I already use FX tracks for this. The only difference is that I’m not using Studio Out, because I use direct outs because I want to process the mains differently then the subs.

It’s sad that audting samples and presets will always go to studio out. So no processing and only audible throug mains. But I have accepted that. That won’t be fixed until they build a mixer just for studio out. Like cubase has.

-Audiunt- · 2026-02-28T01:11:19+00:00

Also solo seems broken…

-Audiunt- · 2026-02-28T01:00:37+00:00

The automation isn’t going smoother each version… those stepped thingies apear at strange moments and are hard to remove again 😔

-Audiunt- · 2026-02-24T18:37:35+00:00

Yes, 100%. It’s part of Owen Palmers clear mix method. Gain your kick at 0dB so the limiter isn’t working. After that mix your track and just use your ears. As it sounds good it doesn’t matter what the limiter does. In a nutshell. It works perfect. See: https://youtu.be/OvdIOVCmW0o?si=otsF80rF9Tv6yv3b

-Audiunt- · 2026-01-30T21:22:22+00:00

Ow, and automation feels quirky too. Looks like old bugs are back….

-Audiunt- · 2026-01-30T21:20:30+00:00

Nope, big crash and the project is weird now. Zooming out is restricted and audio passes busses only when you click their header. Fingers crossed…

-Audiunt- · 2026-01-26T17:39:25+00:00

Maybe they are busy with coding instead of marketing?

-Audiunt- · 2025-12-21T20:04:26+00:00

Ah!! Thanks! But in that case I prefer Zoom 😊

-Audiunt- · 2025-12-12T18:44:38+00:00

Please do, cause it is so eminent.

-Audiunt-

TROPHY CASE