First off, I was thrilled that Bandlab had purchased Cakewalk properties and was going to move forward with Cakewalk and Sonar. The FREE Sonar sounded really great! 
 
At the same time, I am a SONAR LICENSED OWNER. 
 
So I created a Bandlab account. No problem there, I checked everything on the settings. I thought I had it all set right. 
I simply shared a song of mine and someone following me had made a really ADULT "SAME CHORDS AND BEAT" street version of my song that I never give anyone permission to do so. I blocked that person, contacted BANDLAB, I thought that was the end of it. 
 
But even after contacting BandLab MULTIPLE TIMES and this person is on BLOCK, when I log in "This PERSON'S POST ALONG WITH THE MUSIC I MENTION IS STILL THERE RIGHT IN FRONT OF ME!". Yeah it says "BLOCKED, But It damn sure is not being blocked! So I guess popularity or monetary value ways better than newbies who post their music where the rules go. 
 
I really wanted to like BandLab. But considering the circumstances, I will no longer be using it. BandLab considers EVERYTHING YOU POST OR RECORD AS PUBLIC DOMAIN in my opinion. The issue is : "I recorded NOTHING I SHARED AND CLICKED THE DO NOT SHARE CHECKS & BOXES WITH ANY OF : THEIR SOFTWARE". I recorded it with my OWNED SONAR SOFTWARE. 
 
Either way, I prefer CAKEWALK SONAR and will not be using BANDLAB "Analytical USE AND SELL" software. 
 
That may not be the case, but it is the impression that I am getting now. 
I had a problem with Bandlab's site to begin with and it was a REAL quick response when they purchased Cakewalks entities, Now it's like not anybody on there cares at all with my issue. 
 
Either way, I bet this gets deleted or LEFT AND BLOCKED from others seeing. But it is my experience THUS FAR with dealing with the SITE BANDLAB and like I said, the music I posted on their site was recorded using my LICENSED SONAR PLATINUM. So I will continue using that. 
 
I Bet there will be a bunch of smart asses replying to this, but I suspect they are IN HOUSE SPEAKERS. 
 
Those are my thoughts, and that was MY EXPERIENCE SO FAR dealing with BandLab. 
 
It's NOT GOOD. And that is the end experience that I wish to convey WITH MY OPINION. 
 
Have a Wonderful day everyone!
 
Bobby
 
 
edit: OP advised me in a PM the issues have been solved by BandLab - scook

Serious_Noize!
I simply shared a song of mine and someone following me had made a really ADULT "SAME CHORDS AND BEAT" street version of my song

Once you share it, it's out there in the ether.

There's a reason some artists refuse to share stems.

Yikes, Serious Noize . . . I really hope what you're alluding to here is not the case !
Personally, I haven't shared anything on Bandlab yet, and probably won't.
I can't help thinking that your example is the worst case scenario, but it really makes me wonder about Bandlab sharing. I think if you share, you leave your music open to collaboration, that's what it's about, and now I'm not sure there's any proper controls in place to avoid it.
 

I shared a song on there and it wasn't long before a guy put "weed smoking Rap lyrics" to it! I had to laugh!!
 
I never thought this would happen. But once it did I keep my stuff private now.

I've got no interest at all in the collaboration platform, myself. But there's nothing forcing anyone using the DAW to also use the BandLab collaboration site.

Think of it like giving paper to children. You never know what they're going to draw with it.
That's what happens if you share your music. Expect people to set it on fire, get mud on it, etc.
Only share what you're prepared to be used and abused.
Anything really personal and precious to you, I'd NEVER share publicly. At least not the stems.

If you don't check the option to allow "forking" when you upload the song, they can't take it and change it. I also make sure anything I post is copyrighted.

With the internet, anything posted anywhere can be digitally nabbed and unless it gains attention you will probably never know it (and jurisdiction can hinder copyright anyway). About the only protection is don't post at all (sorta destroys the point of sharing music) or don't post stems (as mentioned above). I haven't even looked at Bandlab yet, but the idea of anyone in the world accessing stems is scary.

I had seen the "forking" mentioned before, but not sure how clear that is on their site. The OP is concerning, since it is not clear if a blocked user can still access you, but that is moot with a free system since they could just create another account anyway.

I don't plan on posting anything there. I write classical music. I doubt that anyone on the "classical" part of their forum actually knows what classical music is. I've seen covers of "Smoke Gets In Your Eyes" there, and most of the stuff is heavy on drum kits - fine if you're writing pop or rap, but not classical.
 
We need to keep in mind that this is a different culture, one with perhaps rather fluid views of intellectual property rights. Perhaps we can help them change that, but I wouldn't bet on it. In the meantime, it's good to bring this stuff to their attention. If they don't hear about it, there's no reason for them to change.

I'm sorry for the frustration. You seem to have found an issue with the BandLab blocking feature and we're looking into it now. Once you block a user their content should be removed from your feed immediately. Something isn't working and we'll dig in and figure out what happened and fix it ASAP. 
 
Regarding your song being used by someone else, that should only be possible via BandLab if you allow forks when you save and publish your song, if you save a song to a band, or if you invite a collaborator to your song. Allowing forks is like opening your song up to creative commons so anyone can use it as inspiration and do whatever they see fit with it. You can posts songs without allowing collaboration, or even just keep songs private. Or as mentioned earlier in this thread, you don't have to use BandLab at all. You can just use your BandLab account to access BandLa Assistant to get your Cakewalk by BandLab updates. 
 
I'll reply to your support ticket now.