muzdol
I said,
'but also no long face. things just happen, right?
just wondering why they suggest for joining their site with same email as cakewalk email.'

period.

BandLab purchased the Intellectual Property and certain assets from Cakewalk inc. part of that was the forum and user accounts.

So that our records and accounts can be maintained, BandLab wants to migrate all that information and keep it in one place, a new forum and account structure under the BandLab banner not Cakewalk inc.

So opening an account with BandLab (necessary for downloading the new Cakewalk by BandLab program) using the same email as you used for your Cakewalk account will allow the easiest migration of data at some point in the future. Easy really..

mudgel

muzdol
I said,
'but also no long face. things just happen, right?
just wondering why they suggest for joining their site with same email as cakewalk email.'

period.

BandLab purchased the Intellectual Property and certain assets from Cakewalk inc. part of that was the forum and user accounts.

So that our records and accounts can be maintained, BandLab wants to migrate all that information and keep it in one place, a new forum and account structure under the BandLab banner not Cakewalk inc.

So opening an account with BandLab (necessary for downloading the new Cakewalk by BandLab program) using the same email as you used for your Cakewalk account will allow the easiest migration of data at some point in the future. Easy really..

i think the question is, how is this useful for end users? it's obvious how it's useful for bandlab, but not end users, as anyone can now get the new app for free, not just previous sonar users, so why bother using the same email?

pwalpwal

mudgel

muzdol
I said,
'but also no long face. things just happen, right?
just wondering why they suggest for joining their site with same email as cakewalk email.'

period.

BandLab purchased the Intellectual Property and certain assets from Cakewalk inc. part of that was the forum and user accounts.

So that our records and accounts can be maintained, BandLab wants to migrate all that information and keep it in one place, a new forum and account structure under the BandLab banner not Cakewalk inc.

So opening an account with BandLab (necessary for downloading the new Cakewalk by BandLab program) using the same email as you used for your Cakewalk account will allow the easiest migration of data at some point in the future. Easy really..

i think the question is, how is this useful for end users? it's obvious how it's useful for bandlab, but not end users, as anyone can now get the new app for free, not just previous sonar users, so why bother using the same email?

Because it will probably be linked to your existing/old Cakewalk Account and, following on from that, all the extra plugins we have been fortunate enough to be given for free over the years. New users simply won't get this (without paying)
 
Without that - how would they (Bandlab) know?

Bristol_Jonesey

pwalpwal

mudgel

muzdol
I said,
'but also no long face. things just happen, right?
just wondering why they suggest for joining their site with same email as cakewalk email.'

period.

BandLab purchased the Intellectual Property and certain assets from Cakewalk inc. part of that was the forum and user accounts.

So that our records and accounts can be maintained, BandLab wants to migrate all that information and keep it in one place, a new forum and account structure under the BandLab banner not Cakewalk inc.

So opening an account with BandLab (necessary for downloading the new Cakewalk by BandLab program) using the same email as you used for your Cakewalk account will allow the easiest migration of data at some point in the future. Easy really..

i think the question is, how is this useful for end users? it's obvious how it's useful for bandlab, but not end users, as anyone can now get the new app for free, not just previous sonar users, so why bother using the same email?

Because it will probably be linked to your existing/old Cakewalk Account and, following on from that, all the extra plugins we have been fortunate enough to be given for free over the years. New users simply won't get this (without paying)
 
Without that - how would they (Bandlab) know?

don't you already have all the extra plugins?

pwalpwal

Bristol_Jonesey

pwalpwal

mudgel

muzdol
I said,
'but also no long face. things just happen, right?
just wondering why they suggest for joining their site with same email as cakewalk email.'

period.

BandLab purchased the Intellectual Property and certain assets from Cakewalk inc. part of that was the forum and user accounts.

So that our records and accounts can be maintained, BandLab wants to migrate all that information and keep it in one place, a new forum and account structure under the BandLab banner not Cakewalk inc.

So opening an account with BandLab (necessary for downloading the new Cakewalk by BandLab program) using the same email as you used for your Cakewalk account will allow the easiest migration of data at some point in the future. Easy really..

i think the question is, how is this useful for end users? it's obvious how it's useful for bandlab, but not end users, as anyone can now get the new app for free, not just previous sonar users, so why bother using the same email?

Because it will probably be linked to your existing/old Cakewalk Account and, following on from that, all the extra plugins we have been fortunate enough to be given for free over the years. New users simply won't get this (without paying)
 
Without that - how would they (Bandlab) know?

don't you already have all the extra plugins?

Only by using the same logon & password as before

Bristol_Jonesey

pwalpwal

Bristol_Jonesey

pwalpwal

mudgel

muzdol
I said,
'but also no long face. things just happen, right?
just wondering why they suggest for joining their site with same email as cakewalk email.'

period.

BandLab purchased the Intellectual Property and certain assets from Cakewalk inc. part of that was the forum and user accounts.

So that our records and accounts can be maintained, BandLab wants to migrate all that information and keep it in one place, a new forum and account structure under the BandLab banner not Cakewalk inc.

So opening an account with BandLab (necessary for downloading the new Cakewalk by BandLab program) using the same email as you used for your Cakewalk account will allow the easiest migration of data at some point in the future. Easy really..

i think the question is, how is this useful for end users? it's obvious how it's useful for bandlab, but not end users, as anyone can now get the new app for free, not just previous sonar users, so why bother using the same email?

Because it will probably be linked to your existing/old Cakewalk Account and, following on from that, all the extra plugins we have been fortunate enough to be given for free over the years. New users simply won't get this (without paying)
 
Without that - how would they (Bandlab) know?

don't you already have all the extra plugins?

Only by using the same logon & password as before

but you already have them, from before bandlab (and i don't think the password has to be the same ) and bandlab simply doesn't include all the plugins you got before even if you do use the same email address - see the comparison google spreadsheet - all it does is allow bandlab to keep a clear data path of you as a user

pwalpwal

mudgel

muzdol
I said,
'but also no long face. things just happen, right?
just wondering why they suggest for joining their site with same email as cakewalk email.'

period.

BandLab purchased the Intellectual Property and certain assets from Cakewalk inc. part of that was the forum and user accounts.

So that our records and accounts can be maintained, BandLab wants to migrate all that information and keep it in one place, a new forum and account structure under the BandLab banner not Cakewalk inc.

So opening an account with BandLab (necessary for downloading the new Cakewalk by BandLab program) using the same email as you used for your Cakewalk account will allow the easiest migration of data at some point in the future. Easy really..

i think the question is, how is this useful for end users? it's obvious how it's useful for bandlab, but not end users, as anyone can now get the new app for free, not just previous sonar users, so why bother using the same email?

To use the same email for your BandLab account and your soon to evaporate Cakewalk inc account, is the most logical and efficient way of making a bridge for your Cakewalk inc licenses over to BandLab. It's a very gracious offer in my opinion ... they saying that they will respect and maintain your existing licenses with the now defunct Cakewalk inc company ... despite never having profited from the sale of these licenses. 

I think the point is that your licenses from any product you own from Cakewalk previously will still be available from BL. So you will be able to continue installing and running them. To do that, BL have to migrate your customer account from CW to BL and they need a consistent, unique identifier to match the CW and BL accounts. Email addresses are the ideal unique identifier. So if you have a BL account with the same email as your old CW account they can transfer your old products across to make them accessible to you in the future.

It does make sense if the old Cakewalk servers (and CCC) go offline at some point [which seems planned], and they are migrated to BandLab [which also seems planned]. There are things in our Cakewalk accounts that were never ported into the CCC [which supported the "new" SONAR], so without that migration (and email confirmation on our parts), I presume that the old Cakewalk accounts will vanish at some point as they exist today.
 
KORG just did this with their legacy collections, and it is pretty common.

pwalpwal,
 
In the event that the Cakewalk (company, not the software) CCC server is shutdown I want to know that BandLab has a record that I am licensed to use the Cakewalk company produced plugs that I assume BandLab also acquired as assets; such as LP-EQ, LP-MB, CA-2A, Dim Pro, Rapture Pro, Adaptive Limiter, Z3ta+ and Session Drummer 2/3. I have older projects that have these plugs in them and I would sure like a going forward plan to recover them if the CCC server goes down (and no auth file is provided).