.dawproject

Official support for: bitwig.com
RELATED
PRODUCTS

Post

hmmm.. this looks interesting:
"Open exchange format for user data between Digital Audio Workstations (DAWs)"
https://github.com/bitwig/dawproject

Post

this is, very very interesting... tnx for heads-up

Post

That's an awesome initiative, although I'm not super thrilled about Claes dividing his attention between Bitwig and this... Obviously, it might help Bitwig in the long run (like Ableton & FL import already seems to), but it's hard to get excited about long-term stuff when so many low hanging fruit and QoL things are left on the table.

I remain cautiously enthusiastic ;) :D
Music tech enthusiast
DAW, VST & hardware hoarder
My "music": https://soundcloud.com/antic604

Post

gah. xml note data. reminds me of reverse-engineering GuitarPro files. coding/debugging tied notes, mixed with non-tied notes, across bar boundaries, with time sig changes, amongst reams of verbose XML, was character forming. makes MIDI look almost trivial. cemented my hatred of music notation.
.................................
"Hell is other People" J.P.Sartre
.................................

Post

antic604 wrote: Thu Jun 03, 2021 3:40 pm That's an awesome initiative, although I'm not super thrilled about Claes dividing his attention between Bitwig and this...
I'm not that interested in bitwig anymore, it's a very skillful and beautifully coded clumsy instrument to me not really a DAW (to develop projects in).
But a solid "Open exchange format for user data between Digital Audio Workstations (DAWs)" would mean everybody can come in with their compositions made in whatever tool with whatever VST and can be tinkered with at the roots, on proper studio machines; no need to work with/on those flawed bouncing attempts anymore.

Post

Neat!!! This is super nice, finally! Very nice move by the devs. I will report this to Renoise team. Might write a script or so.

Post

Hanz Meyzer wrote: Thu Jun 03, 2021 8:29 pm Neat!!! This is super nice, finally! Very nice move by the devs. I will report this to Renoise team. Might write a script or so.
That would be so cool, love renoise.

Obviously fantastic if .dawproject became a thing, getting support from just one other DAW might be enough to get the ball moving quickly. Love this forward-thinkingness from the team!

Post

Seems like a decent way to make it easier for people to switch DAWs.

Post

coroknight wrote: Thu Jun 03, 2021 10:03 pm Seems like a decent way to make it easier for people to switch DAWs.
Or move a project to another DAW for various reasons, and cross DAW collaborating.
I use other DAWs as well as Bitwig, and porting is always... fun.

Post

machinesworking wrote: Thu Jun 03, 2021 10:42 pm
coroknight wrote: Thu Jun 03, 2021 10:03 pm Seems like a decent way to make it easier for people to switch DAWs.
Or move a project to another DAW for various reasons, and cross DAW collaborating.
I use other DAWs as well as Bitwig, and porting is always... fun.
Yeah I can see multi-DAW use-cases. It's a lossy process though right? So probably of limited use for collab.

Post

machinesworking wrote: Thu Jun 03, 2021 10:42 pm
Or move a project to another DAW for various reasons, and cross DAW collaborating.
I use other DAWs as well as Bitwig, and porting is always... fun.
Or in my case, it is a bit of motivation to use Live 11 (which I own but don't have installed). If basic midi imports flawlessly by the time Bitwig 4 is released, I could use the Midi Step Record in Live (which I always liked) and it could be a reasonable workflow.

Post

pdxindy wrote: Thu Jun 03, 2021 10:51 pm
machinesworking wrote: Thu Jun 03, 2021 10:42 pm
Or move a project to another DAW for various reasons, and cross DAW collaborating.
I use other DAWs as well as Bitwig, and porting is always... fun.
Or in my case, it is a bit of motivation to use Live 11 (which I own but don't have installed). If basic midi imports flawlessly by the time Bitwig 4 is released, I could use the Midi Step Record in Live (which I always liked) and it could be a reasonable workflow.
That's yet another Reason Studios-like thing, who made a Reason Rack Plugin so that people would stop complaining about Reason DAW, moved elsewhere and the devs could abandon it with clear conscious - "see out usage data? no one uses Reason as a DAW anymore" :dog:

Next time you complain about something in Bitwig's piano roll, don't be surprised if they tell you to use FL or Live and import the clip.
Music tech enthusiast
DAW, VST & hardware hoarder
My "music": https://soundcloud.com/antic604

Post

antic604 wrote: Thu Jun 03, 2021 10:59 pmNext time you complain about something in Bitwig's piano roll, don't be surprised if they tell you to use FL or Live and import the clip.
I don't complain to the Devs...

Oh, and neither Live nor FL properly record MPE data!

Post

pdxindy wrote: Thu Jun 03, 2021 11:13 pm I don't complain to the Devs...
I do, there's no sense in complaining here to other users if you haven't sent in a feature request of bug report.

Post

This is pretty cool. Maybe this is the first step towards the collaboration features that were promised in Bitwig a while back. Perhaps the devs (rightly) think that it shouldn't be something that should just work in Bitwig.

Since it seems to be a non-binary format that could make it easier for collaboration and versioning tools to work with it. It doesn't seem like the goal is for it replace existing project files but to be a collaboration format for the most part.

I can also see it as Bitwig response to ALS quickly becoming the format for collaboration. Something open and DAW agnostic would probably be preferable imo. It would (should) help with hardware adoption as well.

Now the issue is adoption. Let's hope more DAWs take up the call to an open collaborative format.
Studio One // Bitwig // Logic Pro // Ableton // Reason // FLStudio // MPC // Force // Maschine

Post Reply

Return to “Bitwig”