Now this is a game changer - Bitwig, Presonus team up DAWProject

[Teksonik]

To me, this satisfies one of the only reasons to be excited about a new product… if it either makes you better or helps you work faster. This would help someone work faster *if* they switch hosts or collaborate.

Ok fair enough. I work alone but do use several different DAWs. Being able to load an entire project from one DAW to another might be useful here but only if it can load pretty much 1:1 which of course would not be possible if I use an instrument or FX that's locked to one DAW and not available in the other.

[vurt]

To me, this satisfies one of the only reasons to be excited about a new product… if it either makes you better or helps you work faster. This would help someone work faster *if* they switch hosts or collaborate.

Ok fair enough. I work alone but do use several different DAWs. Being able to load an entire project from one DAW to another might be useful here but only if it can load pretty much 1:1 which of course would not be possible if I use an instrument or FX that's locked to one DAW and not available in the other.

it does list basic stock fx processors as part of the project
but even if for example it can automatically work out "oh this is a bitwig only synth" then render that track to audio but keep vsts as plug in and midi?

early days, but good that at least someone is looking in to it.

like you i work alone (who'd want to work with me? ) but i have in the past done a few odd collabs, and it was just a case of adding to each others audio, no editing or anything, which this may have opened up even some basic options.

[xbitz]

I can see it only in the import list in the manual in S1

Importing Project Files from Other Applications
Studio One can open several other application project file types. These include PreSonus Capture™ Sessions (.capture), Daw Project (.dawproject), Steinberg Cubase Track Archives (.xml), Steinberg Sequel Projects (.steinberg-project), Kristal Audio Engine Projects (.kristal), and Open TL (.tl). To open any of these project file types in Studio One, navigate to File/Open, and select the desired file, or drag and drop the file onto Studio One itself.

back to Logic then

ps. hmm...

Képernyőfotó 2023-09-26 - 20.45.49.png

anyway I only have Prime

[xbitz]

^^^ ps2. hmm2

How can I use DAWproject?
DAWproject is currently (as of September 26, 2023) supported in Bitwig Studio 5.0.9 and Studio One 6.5, and later.
Export
Studio One: Go to the menu File > Convert To > DAWproject File…
Bitwig Studio: Go to the menu File > Export DAWproject…

Import
Go to menu File > Open, or just drag and drop a DAWproject file onto your DAW window.

Specifics to Bitwig Studio 5.0.9 and Studio One 6.5
Bitwig Studio imports Studio One Alias Clips as Clips
Studio One doesn’t read Bitwig Studio Clip Launcher data (Clips and Scenes)
Studio One AU plug-in data isn't read by Bitwig Studio
Bitwig Studio CLAP plug-in data isn't read by Studio One
Built-in generic devices: supported in Bitwig Studio 5.0.9, coming soon in Studio One 6.5
Studio One Video track currently isn't supported in Bitwig Studio

https://www.bitwig.com/support/technica ... t-faqs-62/

anyway it's missing from Prime mac 6.5

ps.3 new email new trial and yepp

Képernyőfotó 2023-09-26 - 21.54.14.png

[xbitz]

so... Bitwig doesn't recognize the plugin-related settings that has been exported by S1(Nexus), but at least Studio One is able to read back the file it(or BWS) exports flawlessly so far so good

Képernyőfotó 2023-09-26 - 22.33.21.png

PreSonus should consider exporting their own QC team first

[apoclypse]

Keep trying. Maybe you'll get it at some point.

Why should we keep guessing if you can't express yourself clearly and apparently don't care to be understood?

Cubase actually even has an API for their MIDI FX, but, it seems like it's very old, and hardly anyone ever made use of it (and it's also, obviously, limited to MIDI FX in Cubase): https://www.steinberg.net/de/developers/ (VST Module Architecture SDK)

You suggested another format. I don't need another format. That's the point. Either VST3 should support this, or Steinberg should develop an offspring which supports this, if they argue that VST is an audio plugin format, not a MIDI plugin format.

Is that so hard to understand?

You are literally asking for another format. VST3 is not going to support this, and then you go ahead and ask Steinberg to create another format to support this if VST3 doesn't. So it's hard to understand your aversion to "another format" when you are literally asking Steinberg to create another format. At least CLAP (so far) isn't beholden to the whims of Steinberg or Apple. Seems like exactly what you want.

[cptgone]

Ok fair enough. I work alone but do use several different DAWs. Being able to load an entire project from one DAW to another might be useful here but only if it can load pretty much 1:1 which of course would not be possible if I use an instrument or FX that's locked to one DAW and not available in the other.

If your DAW gets discontinued, this format would provide a convenient way to transfer all MIDI and audio to another DAW, even if it doesn't transfer every aspect of your projects 1:1, in the case of DAW specific plugins.

[apoclypse]

To me, this satisfies one of the only reasons to be excited about a new product… if it either makes you better or helps you work faster. This would help someone work faster *if* they switch hosts or collaborate.

Ok fair enough. I work alone but do use several different DAWs. Being able to load an entire project from one DAW to another might be useful here but only if it can load pretty much 1:1 which of course would not be possible if I use an instrument or FX that's locked to one DAW and not available in the other.

I think this is more about collaboration than anything else. The same issue could happen even if you have two people using the same DAW. I collaborate with a friend, we both use Logic. I own far more plugins than he does so I have to do some work to make my projects work for him. He primarily just uses Logic so it's far easier for me to get his files. Having an intermediary format would make it so the I can collaborate with someone using another DAW, even if it means a little work (having to freeze or bounce down some tracks), but hopefully still get stuff like audio layers (for takes), automation data, etc.

Bitwig is actually pretty okay at opening Ableton and FLStudio projects so I can see the appeal here.

[jamcat]

Unfortunately, I think Logic and Pro Tools are both less inclined to get on board.

Pro Tools because they invested a lot in OMF, which is pretty useless. Its uselessness is to Avid's advantage because it keeps people locked into Pro Tools as the "industry strandard" since no one can manage to escape once they're sucked in. That has always been their business model.

Logic for much of the same reason. It's in Apple's interest to keep people locked into Mac OS. Apple will say your collaborators just need to buy Macs and use Logic. Problem solved.

[elxsound]

Unfortunately, I think Logic and Pro Tools are both less inclined to get on board.

Pro Tools because they invested a lot in OMF, which is pretty useless. Its uselessness is to Avid's advantage because it keeps people locked into Pro Tools as the "industry strandard" since no one can manage to escape once they're sucked in. That has always been their business model.

Logic for much of the same reason. It's in Apple's interest to keep people locked into Mac OS. Apple will say your collaborators just need to buy Macs and use Logic. Problem solved.

I hope you're wrong, but I think you're right. With Bitwig and Studio One... It's to their advantage to make this a feature.

The only thing that could convince the other companies to adopt it, would be if they lost customers because they don't provide this feature. How likely is that a possibility?

"Industry Strandard" Love it.

[machinesworking]

It's not just about collaboration. Personally I've always used a DAW like DP or Logic as well as the new school Live and Bitwig way of doing things. Not because I love it that way, but because dinosaur DAWs always get every new feature, but clip launching and super easy time stretching isn't their main thing, neither is fast global assignments of most used parameters of your plugins, great control surface support etc. etc.

The "new" crowd misses basic features, there is no count in, in either Live or Bitwig without recording, because apparently wanting to start on the first beat of the first measure isn't important to most users I guess? Yes over the years there are countless converts to Live and Bitwig who stop using Cubase, Logic, DP etc. but there are countless amounts of folks like me who never gave up DP etc. because Articulation maps, event lists, count in, metronome choices, automation types, advanced quantize, hundreds of possible keyboard shortcuts and full blown linear arranging features are still important.

The sad part about it to me is because Bitwig are a main contributor and don't support SysEx, it also doesn't support SysEx, which is a travesty considering the modern list of poly hardware synths that can do SysEx dumps to permanently ensure that your patch will be available in your projects a decade later etc.

[pdxindy]

Moss made a quick video looking at DAW Project and bringing a project from Bitwig to Studio One.

[apoclypse]

Unfortunately, I think Logic and Pro Tools are both less inclined to get on board.

Pro Tools because they invested a lot in OMF, which is pretty useless. Its uselessness is to Avid's advantage because it keeps people locked into Pro Tools as the "industry strandard" since no one can manage to escape once they're sucked in. That has always been their business model.

Logic for much of the same reason. It's in Apple's interest to keep people locked into Mac OS. Apple will say your collaborators just need to buy Macs and use Logic. Problem solved.

I hope you're wrong, but I think you're right. With Bitwig and Studio One... It's to their advantage to make this a feature.

The only thing that could convince the other companies to adopt it, would be if they lost customers because they don't provide this feature. How likely is that a possibility?

"Industry Strandard" Love it.

At this point Apple makes more money selling apple watch bands than they do on Logic. Logic is used strategically by apple not necessarily to make money. So they have no incentive to do what others do if it doesn't strategically meet their needs. That being said I do think Apple would support this at some point.

ProTools is also a possibility. Now that they've been sold they may be looking to get new paying customers (they've added clip launching which his weird to say the least). I'd expect them to keep adding more user friendly modern features to entice users back to their platform. So I think they may do it as well. The ones I don't see doing it is Ableton and Steinberg.

[pdxindy]

The ones I don't see doing it is Ableton and Steinberg.

I could see Ableton supporting it.

I only see Steinberg dying alone on a hill.

[apoclypse]

I just tried it out and there are some issues with export or import. I have fairly simple Bitwig project with a few audio files, one of the tracks never made it through to Studio One. Not really sure why. The project structure mostly made it through except for that one track.

I do like that the exported file is pretty much self contained, no folders etc to deal with. You can also easily open it by just changing the file extension on Mac. I do see the audio files for the missing track.

Edit: Yeah it's cool, but there seem to be too many issues right now. Especially on the Bitwig side. I just got an error "Exporting {0} error" exporting a fairly basic track. They need to a bit more work.

Just tested exporting a very basic project from S1 to Bitwig. Bitwig throws an error. It seems to me like Bitwig needed more time to work out the kinks. S1 seems to be doing just fine exporting and importing for the most part.