So now more people have Cubase at their disposal and can use it free and make eventually money and buy it, solo or can be shared with 3 friend, which is funny price in that context.Īll is marketing, in this moment good for us, but now we have more possibilities to move one from Studio One to Cubase, because most of nowdays Studio One users were Cubase users, but there was not cracked stable Cubase for 12yrs. Remember AVICII Studio Session and Sylenth1 cracked by Team AiR or IDONTKNOWHO, and can not remember who was using cracked FLStudio in the Studio Session, maybe was Martin Garrix I don't remember.īut that was quite a good marketing for both companies, because everyone wanted FLStudio or Sylenth1 to make a new summer hit! Yes, I believe that Steinberg have done this on purpose, but they will not change or implement a lot protection in the future, business wise, it is a smart move, because they were already 99% cracked form Team VR, and now they will reach more users using cracked software, which will then eventually end up buying it. Well it is similar protection, if not easier, because what Activation Manager does, it stores physical licenses file in the Activation Manager folder, so once you bypass that check, all apps are cracked, but. Protection is quite easy if the cracking team is experienced, otherwise no.īecause it uses external Authorization Manager, like FXpansion have.īut FXpansion is buggy even for legit users, so Team R2R gave up on them and there is a lot of products to cover, so they could not to manage to keygen everything with bad Auth system. It still amazes me, how they were able to release a cubase 12 pro, so so quickly!Īs far as i know. Question: if your new copy protection/ license management/ etc are flawless, and can't be cracked (like the dongle elicenser), why waiting 1 year for the offline registration.Īnd BTW, are the V.R, and the more recent team RET releases working 100% fine ? too fast.Īlso, if I remember well, steinberg said they would only offer offline activation at the end of the year. There are at least 100 top devs, at steinberg, who had to direct or indirectly work on the new copy protection.Īgain, I find these cubase cracks too easy. which methods they use to crack all kinds of shit. They also know how V.R and other teams do work. If they weren't 100% sure, they would have gone like 'ok, guys, we're not 100% sure our copy protection is perfect, so, we will first release a small product, like padshop or retrologue, with the new copy protection, that way, we will limit our losses, if some hackers manage to crack it" They would never release cubase 12 without a dongle, with the new copy protection and licensing system, without asking top hackers, or even top devs, to try to hack their app. They would NEVER release an app such as cubase pro 12, if they weren't 100% sure the new copy protection would resist at least 2 or 3 years. Steinberg must have started working on the new licensing system for at least 4 or 5 years. I don't believe one single second that a sylenth3 copy protection is more robust than. and now, we have cubase pro 12, that gets cracked in '5 minutes'. and many other, serial number or C/R based, that still haven't been cracked, since many many years. and they left some demo/trial code, that will revert all cubase pro 12 to demo/other, 2 or 3 weeks from now, thus forcing EVERYBODY to download the new cubase version, with the full copy protection enabled, this time around.īecause I'm finding these cracks TOO easy. Now, Knowing how absolutely paranoid Steinberg are, regarding the copy protection of their products,Ĭould it be that they released this v12, with some copy protection features disabled on purpose.so they (steinberg) could analyze and see what the audio scene would do.which parts of the protection would be attacked, etc. Do you remember a few years ago, when UHe had released a new Diva version, and he had 'FORGOTTEN' to remove some demo code, from the main retail binary(or something like that), and ALL Diva users had to download the new, proper update, as the 1.2.0.0 (can't remember) would no longer work after x days.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |