Public + Forkable - if you publish a revision and make it forkable - you're someone who embraces the world of open source and want to inspire others, or to see what people can create with your music.People can listen, like, comment, add to Collections (our version of Playlists), share, embed but they can't access the multi-track files or anything more. Public - if you publish a revision, but do not make it forkable - it's equivalent to uploading to a gallery or any audio-hosting site.If you have Collaborators, or are in a Band, then they can see private revisions. If you don't collaborate with anyone, it's just you. Private - the track is not visible by anybody, except those who have access to the project.There are three different states of revisions in BandLab that are your choice: Projects/Songs are made up of different revisions - e.g you don't 'publish' a project, you publish a revision/mix from a Project. We're putting together some better tutorials as BandLab has a lot of hidden complexity but let me address a couple of things here - there are some core misunderstandings.ġ) We already have embed - it's via the 'Share' button on a post - it's only available for published posts right now, as it would not make sense to embed private revisions that no-one else can access! 2) Projects that are on the 'interweb' - more on collaboration in the next post, but it's important to understand how projects work on BandLab.

Using ux2 with cakewalk by bandlab