BandLab Interchange file (BLX)

[Larry Blumer, Jr.]

Hey gang,

 

Longtime CW / Sonar user here who is getting back into the fold!

 

I'm using the full Cakewalk version in a hybrid mode with BandLab.  I (Member A) am able to export my CWP project audio tracks to BandLab.  I'm trying to work out a process to allow a BandLab bandmate (Member B) to collaborate.  Member B is able to download the stems (BLX file) which becomes another CWP project.  The issue is that Member B's CWP project is not linked to Member A's  BandLab project.  If Member B exports it, it will simply create a new project with the same name.

 

This differs in behavior from when Member A exports a second or third time.  This creates revisions in the project like a code repository.

 

So how can Members A and B have CWP projects which are linked to the same Bandlab project?  I'm not expecting to work at the same time, really just looking to trade off back and forth using an improvised exclusive check-out process (we are both software engineers as well).

[Larry Blumer, Jr.]

I guess this is a bust because even if it were possible, there's no way to do a "pull/import" request to update the CWP easily.

 

What's interesting is that the revision history includes a graph and seems to support branching, so there is some degree of sophistication to it.  However the integration with CbB is entirely unsophisticated.  Will this improve?

 

This would really benefit my project as the band is geographically scattered.  Two of us can handle CbB, but it would be great if the third member could do tracking using BandLab.

[scook]

Probably the best way to handle the BandLab user is upload a mix of the project and download the new track(s) they create, integrating them into the CbB project, just like one could handle any other DAW.

 

[jackson white]

Something like GitHub for CxB? 

Sounds like a major development effort, but a nice thought.