Hell froze over! Steinberg Cubase14 supports Bitwig dawproject open format! First test!

[@mossgraber]

0:00 Refresher - What is dawprocject? 2:20 Which DAWs support dawproject and to what extend? 5:02 Test 1: Reaper pure audio project to Cubase 10:00 Test 2: Bitwig MIDI+Audio project to Cubase 13:35 Test 3: Cubase fully mixed project to Bitwig/Studio One

[@OdoSendaidokai]

Happy to see how companies start to understand, that people still are loyal but want to exchange data. Absolutely great move! 🌻

[@patrick5301]

NOT LIKE THIS

[@ataturu]

Crazy! Would have never expected this from Steinberg. Usually they just do marginal updates LOL Using cubase for mixes again does sound nice. Something to try out for sure!

[@agressteve5008]

Beste update der welt.. wirklich richtig krass was da abgeht bei steinberg.. werd direkt upgraden

[@theRumbleChannel]

Very nice! That's probaly also a good sign 4 future clap support. Let's hope they'll do some thorrower testing next time :).

[@mossgraber]

I remembered why I left Cubase after doing this... 😉

[@PriyanshuKumar-sp9gg]

Reaper does have a third party extension/script called playtime (paid) which adds clips support (idk to what extent) to it. Ig it will take work on reaper's API side for it to make use of the dawproject format to work.

[@mossgraber]

Yes, would love to retire my little workaround tool, if Reaper would support dawproject natively!

[@PriyanshuKumar-sp9gg]

Ah I forgot reaper doesn't even support it natively, and I was talking about third party extensions making use of the format 😅

[@pcfirebeats]

This is great news! If they support Linux and CLAP next it would be great.

[@pnutbuttajellee1394]

Thanks for trying! I ran into the same issue as you...audio and midi all out of sync in Cubase import from either a Bitwig or Reaper conversion. I can't imagine they leave it this broken for long because the formatting has been out long enough to get right. My first thought is maybe its a sample rate or time stretching issue/translation. All of the supporting DAWs all use elastique.

[@mossgraber]

It's easy to get it wrong since there can be several layers of wrapped clips with different stretch and timing settings in the dawproject format. But I am still surprised that it is not working straight away since the projects I tested are a pretty simple use-case.

[@247digital]

After testing, there is still a lot to be implemented for DAW project to work correctly. Would be good if when you export, you can render clips on exports, for plugins and instruments that don't exist in the target DAW

[@mossgraber]

Yes, that would be a great feature!

[@CirTap]

Danke für deinen Test. Ich klicker mich seit ein paar Tagen durch alle möglichen Versuche durch :-) Alle Tests die ich aber bisher gesehen hab waren sehr ernüchternd, auch die aus Bitwig heraus. Alles in allem ein guter erster Ansatz von den Hamburgern. Die Bitwig Leute haben da scheinbar ausgeholfen, Berlin ist ja nicht weit weg 🙂 Was mir fehlt ist etwas mehr als die vier Generic EQ, Compressor, Gate und Limiter. Damit kommt man in der Praxis nicht weit. Es gibt z.B. kein "Generic Reverb" oder "Generic Chorus" in dem Format. Die eingebauten Reverb, Echo, Delay, Flanger, Chorus etc. Effekte und Filter machen in *allen* DAWs praktisch das Gleiche, auch wenn sie am Ende unterschiedlich klingen mögen. Dann ist eben der Hall etwas flacher im Zielsystem und das Delay schwächelt etwas unter 50% Feedback... aber es wäre wenigstens was da. Als Cubase (Artist Version) Nutzer frag ich mich dann halt auch, was mir die ganzen tollen hoch gepriesenen FX Stock Plugins nutzen, wenn ich sie im Grund nie einsetzen darf, falls es dann um den Datenaustausch geht. Man muss quasi ausnahmslos mit Drittanbieter VST arbeiten. Ich wittere da eine Verschwörung der Plugin-Schmieden... 🙂 Da leg ich dann ungern hunderte von Euro für Cubase hin (hier wieder ein Hunni für das Upgrade von Cubase 13 auf 14 🤪), wenn ich praktisch keines der teuer bezahlten, internen Effekt- oder Filter-Plugins einsetzen kann. Für VST Instrumente seh ich das ja noch ein oder wenn ich unbedingt "Luxus EQ MK2" oder "Super Spacious Galaxy Reverb 3" und solche Scherze einsetzen will. Aber das sind ja angeblich abgedeckt. Es sollten wenigstens die Effektkanäle / Busse angelegt werden, damit man nicht alles akribisch nachbasteln muss. Und eine Logdatei mit den Infos was NICHT exakt exportiert werden konnte wäre sinnvoll, damit man eben nicht vergisst, dass auf Track 578 noch dieses kleine Echo und ein EQ auf den Glissando der Harfe drauf war... Wird man wohl auf "Version 2.0" des Formats warten müssen und in der Zwischenzeit viele, viele Github Issues aufmachen und das Interesse für "Generic Effect Plugin Support" bekunden 🙂

[@mossgraber]

Having more generic plugins is a good idea. However, these are more tricky when you look at how many different sounding plugins of such effects exist. I also think that it is not necessary to bring over every detail of a project since the use-case is either that you want to mix it in a different DAW or maybe go the other direction an prepare something for a live show where you would bounce things anyway.

[@albertohernandezserradilla3348]

It looks like a sample rate issue Jürgen… Have you checked Cubase uses the same sample rate for the imported dawproject as it was configured in Bitwig & Reaper? Awesome video, thank you for your incredible software solutions, love them!!! 👏🏻🖤🔥🤘🏻💪🏻

[@mossgraber]

Good idea but that's not the problem (I tried it to be sure). It looks to me as if the audio event in a clip is stretched. MIDI clips are correct.

[@CirTap]

@@mossgraber might still be a sample rate issue. could be wrong property on a "per clip" basis within the DAWformat export. maybe the converter did wrong? also from what I've seen "audio stretch" settings are not properly interpreted by Cubase.

[@mossgraber]

@@CirTap Let's just hope they figure it out...

[@BeatsAndMeats]

If you can iron out all the kinks, this will be the greatest thing to happen to music producers in a LONG TIME! Luckily, I'm rarely using MIDI in my projects so maybe I'll have better luck!

[@mossgraber]

Audio seems to be buggy not MIDI.

[@PriyanshuKumar-sp9gg]

Also I haven't looked into the format, but am curious to know how it handles encoding of data for some feature that a daw is exclusively bringing, if it's extensible to encode the data for other daws which might implement the feature in future without major changes in the format. Something (I might be wrong) similar to Wayland protocols in Linux.

[@mossgraber]

The format is already pretty complete, besides native plugins of the DAW, which is something that cannot be fixed. E.g. as I mentioned in the video as well is that videos can already be stored even if Bitwig does not support it (yet?). And there is already room for a v2.

[@sadiporter2966]

annoying that clap support wasn't added.

[@TrishAngel3]

Does anyone use the Unison MIDI

[@jg_yro5845]

Any chance for a Push 3 script for Cubase?

[@mossgraber]

Not from my side.

[@rosshoyt2030]

The problem is theyre using Java for it 😂 but actually it is an exciting piece of software. Definitely still in alpha stage

[@mossgraber]

dawproject is just a simple XML structure. Can be coded in any language.

[@pnutbuttajellee1394]

I think you mean Cubase modulator scripting?

[@mossgraber]

@@pnutbuttajellee1394 I don't think so. dawproject comes with some Java-Code which allows you to load and store a dawproject file. Due to this one can come to the false conclusion that you need to use Java to support the format which is not the case. Similar code can be generated e.g. for C++ easily.

[@kypresso4328]

Its just a way for cubase to get people to stop using clap plugins.

[@cristianomello9424]

Your test seems not enough. Almost none fx plugins in channels or routings like sidechains, buses, fx chains, etc..

[@mossgraber]

Indded! But as buggy as it currently is it did not make any sense to test any further.

[@jabulanimahlangu6863]

no you do it wrong check your cubase project set up

[@mossgraber]

What exactly did I do wrong?

[@jabulanimahlangu6863]

@@mossgraber my apology if it sounded inappropriate, I was saying firstly check your Cubase project setup, it must match with the same project with other daws

[@mossgraber]

@@jabulanimahlangu6863 No, this should not be necessary since all information is contained in the dawproject file. Which settings do you mean sepcifically which might have the need to get adjusted?