I am trying to use the new .dawproject file format in Cubase 14 by exporting a project from Bitwig Studio or Studio One and importing it in to Cubase 14 Pro.

The Project only has 8 tracks all VST instruments but when imported in to Cubase 14 the project doesn't load any of the VSTs used from the original bitwig or studio one projects, next to each track it says "No VST Loaded", it has the midi data just not the VST's used on the tracks no matter what DAW combination I use.

Exported from Bitwig Studio and imported in to Cubase 14
Exported from Studio One and imported in to Cubase 14

Am I miss-understanding what this file format is supposed to be or any limitations of it or does Cubase 14 not import the actual VSTs used?

Export from Studio One in to Bitwig, imports everything

Many thanks

 

Just gave it a shot (exported from Bitwig) and instrument is loaded here...

Crazy shot, any chance you are using VST2's?

Played with it more, strange stuff, when I open same project in Bitwig again (originally I just tested it with single track/instance), add second track, export/overwrite the dawproject file, then open it again in Cubase, it doesn't load the first instance of instrument, but the second, so I keep doing that and it doesn't open first two, just third and so on....

Tried more with one of my full projects, definitely when you re-save dawproject file in Bitwig it goes south in Cubase, instruments aren't loading anymore, but loads them on first try...

Dunno, I use mainly VST2's (backwards compatibility/old projects from Windows) and found a project with bunch of Nexus instances, they load fine, other VST3's too, but for example Bitwig's Tool device isn't translated to Cubase (I do my volume automation with it).

I'm really not a Cubase user, downloaded trial to help you troubleshoot this, but as someone who is using almost exclusively VST2's, it's a task to test anything meaningful on my system, but what I tested briefly confirms some strange stuff happening.

Hope you will get to the bottom of this brother.

 

Last edited: Nov 11, 2024 at 2:24 AM

I would also recommend naming the MIDI files according to synth and preset, so that once they're in Cubase, you can easily reassign the proper synth to them. If you have FX on that track, either put that FX/preset name in the MIDI file name or make text notes about it, because once Studio One is gone, you won’t be able to hear the files as you have been used to in Studio One.

If you render them to audio, you'll know what they are supposed to sound like, and I would also name those to match the MIDI file names.

That's what DAW Project is for, although it will likely be years before Steinberg adopts it.
https://support.presonus.com/hc/en-us/articles/19743606863629-Introducing-DAW-Project

 

What do you mean?

 

Last edited: Nov 11, 2024 at 3:34 AM

Thank you so much for giving this a try, I am so glad that’s it’s not just me.

I tried various other test projects and there were a couple that did include the tracks VST but it was only a track here and there like one track out of 6 or 8 and any tracks that had inserts effects on them none of the insert effects came through on the import.

I was using only VST3 at the time of posting but have since tried VST2 but it made no difference.

Basically what I am trying to do it is import some project with my saved custom Bitwig VST Presets on them so I can use the presets in Cubase 14 without having to recreate them all from scratch.

 

Last edited: Nov 11, 2024 at 7:45 AM

Ahhh thank you for this video, so the DAWproject is currently broken in Cubase 14, looks like Steinberg has a bit more work to do on this.

So glad the video was showing exactly what I am experiencing.

certainly looks like this hasn’t been tested thoroughly by them at all.

Hopefully steinberg will addresss this in the next update.

 

thanks Radio

when I moved from Studio One to Bitwig Studio importing the DAWproject from Studio One in to Bitwig worked really well, it wasn’t 100% but was certainly enough for what I needed.

 

My suggestion is that if you have a project, you should save the presets you use for each track in the VST effects as e.g. FXP. (Choose a meaningful name). I would also take a screenshot of each project. In his case, the VSTs are not included and he could still continue to edit his project and reload the VST effects and then simply load his saved presets.

 

Brother I quoted and even made bold the part I was asking you about, again

Don't understand the part about years that will take Steinberg to adopt it, adopt it properly or what?

 

How long did the developers of Bitwig and Studio One work on this initiative? Steinberg have to play catch-up with something they maybe did not even really want to do. Expecting them to be Johnny on the spot about it, might be disappointing.

 

Sorry @Melodic Reality, I don't know how that sentence got there. Just forget it.

 

Yeah, I was surprised to see that feature in C14, guess it's a good way to cater to people jumping DAW's, similar to what Bitwig did with whole ALS and FLP integration before DAWproject. They will get it right for sure, it's not like Bitwig's initial attempt of importing Live/FL's projects was flawless, I remember having some issues with it too and don't use it that often, but there's a chance it's still not perfect yet.

Sure brother, have a great one.