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

[N__K]

Regarding future support: as some others here, I too think that idea of .DAWproject resonates with REAPER ethos. Not sure which will happen first - official support by Cockos, or import/export scripts by scriptwriters in REAPERland.

Meanwhile in the land of FL Studio, there is a thread on Looptalk about this. At the time of writing this post, Image-Line staff have not yet commented. But even from FL Studio and its pattern-based paradigm, a lot of the project can be exported into a .DAWproject file. Also, since scripting features are being expanded in FL Studio, there is some possibility of utilizing .DAWproject format via that. Much depends on Image-Line's current business vision though.

Overall, this is a very welcome development in the DAW market.

[machinesworking]

If DAWproject becomes a normal format for interchange between DAWs it's a great thing. I for one do not only know people who use Live, or Reaper etc. and I personally love Digital Performer, which is super rare these days. If it become the standard I'll be happy.

Yes, there will be issues, but it's 100% worth looking into a standard, end to end audio files is an annoyingly dull way to collaborate.

[Scotty]

What this say to me is that Bitwig won’t get pushed into developing every feature that established linear DAWs do very well. They can continue to concentrate on the integrated modularity aspects of their platform and break new ground without the pressure of reinventing the wheel.

[spigmu]

... for those who regularly use two or more different DAWs. I don't know how many people do that really.

I do, and I know lots of people who don't settle for one DAW if it's not their favorite for any area. I'm mostly in Reaper, certainly tracking and mixing, but if there's midi tracking involved aside from the most basic I always use DP for midi tracking and editing. Try as I do to do it all in Reaper, as much of an inconvenience it is to use both, I always go back to using both. I'm not even a big fan of how Reaper handles grabbing and moving audio edits, but I dislike it in DP even more.

I would say it's a huge game changer for anyone who collaborates. I pass files around from collaborators who use DP, PT and Logic as their main DAW. No one is going to start using a new DAW just because a new collaborator only uses XYZ. We share stems duped from the same start time. Or time stamped, if that happens to work. Once you get a workflow groove either here or switching DAWs it's fine. BUT it eats up a lot of time doing the secretarial work making a new set of stems every time you do, just clicking around to do the exports and labeling.

I'm sure some of the more established DAWs won't see the upside to themselves for providing it, but if only half of the devs get on board any time soon it will be an extremely worthwhile development for a lot of end users.

[Atlatnesiti]

Well, I consistently use Cubase Pro, Logic, Live Suite and Reason and somehow can’t see any of these adopting this standard

[BONES]

This, and it's not just Studio One. Whenever I reinstall Windows, even on the same computer (which thankfully isn't something one has to do very frequently these days) I have to spend days trying to convince Studio One, Cubase and FL Studio to open old projects without complaining about missing samples and plugins.
Sometimes this even happens on projects that simply haven't been opened in a while, usually because some plugin was updated and the developer decided to randomly change the ID/name.

What makes it annoying in Studio One is that it doesn't give you the opportunity to find it yourself, like it does with missing samples, so it makes the project, or at least some of the tracks in it, unusable. In Orion, if it can't find a plugin it pops up a dialogue and lets you locate it yourself, before it loads the track, so those kinds of problems are easily dealt with. I wish Studio One would do the same, it would eliminate a lot of headaches. It's become such an annoyance for me that I've been seriously thinking about going back to Cubase but, if Cubase is no better, there'd be no point.

I couldn't care less, as I'm no Apple user. It's just that delusional talk which always bugs me again.

That's what gets to me, too. People think I hate Apple but Apple is just one of many greedy companies out there willing to take advantage of idiots. I hate Microsoft a lot more because they have actually f**ked me over several times. It's the way the Applyte apologists carry on that I really hate because it misleads others who don't know any better. It honestly has most of the hallmarks of a true cult.

So, two DAWs with small user bases team up to make their sessions compatible, commendable for sure but mostly useless

I don't think Studio One's user base can be described as "small". If it is, then Presonus must spend a disproportionately large amount of money on support/marketing because they do a lot more for their users than anyone else does. They seem to have three guys working full-time on videos and tutorials for users - Gregar, Craig and Joe. Bitwig also has a big user base for a product that hasn't been around for a long time. Even Studio One is a relative newcomer, yet has carved out a decent user base. I doubt Steinberg and Ableton will be as dismissive of this announcement as you.

If there is no general system which everyone uses, it's pretty useless. And, most DAW developers will also consider if they really want to implement something which would make people use competitive products instead, I guess.

That will depend on how much faith you have in your own product, won't it? If you believe you have a better offering, then you'll see this as a way to introduce S1 and Bitwig customers to your superior product.

^^^ They're almost complementary to each other; I don't know what the crying is about

My thoughts, exactly. Now if anyone wants to whinge about S1 not having a clip launcher, Presonus can invite their customers to use the exchange format to try out Bitwig. Similarly, if a Bitwig customer wants better mixing tools or whatever, Bitwig can point them to S1 via their exchange format. In the end, it leaves both dev teams to concentrate on the core strengths/differentiation of their products, instead of having to turn them into jacks-of-all-trades. It's a win for everyone.

I don't have Bitwig, I have studio one pro v4, would this encourage me to update to 6.5.. probably.. but not this alone.

But what about those people who keep asking for Studio One to get a clip launcher? I can see those kinds of users being very excited about this. Better still, for people like me who don't want S1 to become a bloated mess that tries to keep everyone happy it's a win, too, because the dev team can concentrate on improving what S1 already does best, rather than waste dev resources on stuff I have no interest in.

If anything, they sell you an additional feature here, as usual.

If that's true, they are doing a shit job of it. It doesn't even rate a mention in their mail-out for v6.5.

[EnGee]

What makes it annoying in Studio One is that it doesn't give you the opportunity to find it yourself, like it does with missing samples, so it makes the project, or at least some of the tracks in it, unusable. In Orion, if it can't find a plugin it pops up a dialogue and lets you locate it yourself, before it loads the track, so those kinds of problems are easily dealt with. I wish Studio One would do the same, it would eliminate a lot of headaches. It's become such an annoyance for me that I've been seriously thinking about going back to Cubase but, if Cubase is no better, there'd be no point.

Cubase does prompts you for missing files with a dialog to locate them yourself.

I had several crashes in S1 that made me feels right about selling the Pro edition. I just can't depend on it for starting projects! Maybe for mixing later. So, it mainly now Bitwig and Cubase (in Windows) and Logic/Bitwig in Mac.

Regrading DAWProject, I think it would be a great way to make 2nd backups and to transfer the "basic" of one's project to another DAW (in any case, for oneself or collaborating with others).

I can't test it because I don't have the S1 Pro, but seeing the video posted, I noticed that only the arrangements gets opened. It is logical because S1 doesn't have clip launcher.

I hope other DAWs will do it because as I understood it is not that complex and it is using a standard XML tags that even us can read. I think Reaper would be next and I hope either Cubase or/and Logic would do that. It is useful IMO.

[BONES]

Good to know, thanks.

[pdxindy]

(Also, I don't see why you call it a marketing gimmick, it would be very low on the wish list of any person entering the DAW market, and can by definition not be claimed as unique selling proposition by any single DAW. I see it as the opposite: an open standard that, if implemented well by several DAWs, will benefit many consumers)

One of the Bitwig developers is the original creator of Surge synth. When he realized he no longer had time for it, he made it open source and now it's a flourishing project. Sometimes people do things cause they thinks it's useful and not for some marketing angle.

Bitwig's development of DAW Project has been public for a while and anyone could have been following it on GitHub.

The only news now is that Presonus is supporting it. Maybe someone thinks the Presonus announcement is a marketing gimmick? okay, well, whatever. But the project itself? It's free and open source.

[BONES]

Is it open source? Pity, it's now just a matter of time until someone comes along and ruins it or it ends up abandonware.

What this say to me is that Bitwig won’t get pushed into developing every feature that established linear DAWs do very well. They can continue to concentrate on the integrated modularity aspects of their platform and break new ground without the pressure of reinventing the wheel.

Of course, the same goes for Studio One - they can concentrate on what they do well and not have to add features that are well covered by other hosts. i.e. They can make a better Studio One, instead of wasting resources creating a lame Live/Bitwig experience.

[? ? ?]

You know what would be a game changer? An A.I. DAW that can mimic any feature of any DAW.

[chk071]

Right, because Apple have such a long history of supporting standards. You know, like USB Type C for charging phones.

They support plenty of standards.

Thanks for the laugh.

Apple have their own interfaces and file formats for literally everything, so that you're not compatible with Windows or Linux.

The latest iPhone has USB-C. After nearly a decade of not accepting to have it on their phones. And, they only really implemented it because they had to, not because they wanted to.

Anyway, if it was for me, they could have gone on like that forever, and build their island system. I couldn't care less, as I'm no Apple user. It's just that delusional talk which always bugs me again. No, Apple don't support plenty of standards. Apple is the prototype of the "You buy everything from us!" corporation, which locks out everyone else.

Well it was one of the first DAWS to support MIDI 2 and MPE for example, well before Studio One

Those are device standards for studio equipment, and not some interchangeable formats to work with other OS's or other DAWs. Logic still has its own plugin format. Which, of course, nobody else uses.

[Ploki]

oh my god, i'd kill for this for between logic/cubase/protools.

[Atlatnesiti]

This looks to me like another CLAP flop in the making
Steinberg, Ableton, Reasonstudios, Avid and Apple Logic will not participate of course.
Looks to me like desperate measures to boost their poor sales

[eerie_audio]

This seems like a reason not to include a clip launcher in Studio One version 7.

I really don't see the need for people to use two DAWs in the first place, unless you do a lot of work on other people's material or you collaborate a lot, which is a very low percentage to begin with.

Most DAWs are capable of doing everything you need already, updates are just sprinkles and glitter.