noynekker Posted December 17, 2020 Posted December 17, 2020 I had a Cakewalk project idea on the go, which eventually turned into a good idea . . . so, I renamed it and moved it to a folder in Cakewalk Projects directory . . . then opened the project and saved it using a per project Cakewalk folder. Basic stuff ? Now, when I open the next day and try try to save it I get this "Sharing Violation" message, like it's in use somewhere else in Windows ? . . . the only way to keep my new changes is to do a "Save As" So, now I have 7 project versions, because of this. It's like The Edge of Tomorrow movie . . . every day this error repeats itself. Once I do a "Save As" I can properly save all my edits . . . until tomorrow, when I get the "Sharing Violation" message again . . . have to do "Save As" to a new version. Anyone experienced this ? . . . and know a way out of this perpetual time loop I'm trapped in ? 1
scook Posted December 17, 2020 Posted December 17, 2020 Using anything than needs an elicense? If so, this was the problem reported in this thread around on page 2
noynekker Posted December 17, 2020 Author Posted December 17, 2020 Scook, nothing in my Cakewalk world should need an eLicense . . . but I do have HaLion Sonic by Steinberg loaded as VST in this project which runs on the eLicense . . . you think that's the issue ? . . . I haven't seen this in the many other Cakewalk projects where I use HaLion Sonic.
mkerl Posted December 17, 2020 Posted December 17, 2020 Same Issue here for several weeks now. Still hoping for an update of the elicenser-app from Steinberg . . . it's annoying
noynekker Posted December 19, 2020 Author Posted December 19, 2020 I read the thread scook was referring to . . . seems there is no fix for this yet, all the software developers have to figure this out, so the rest of us just have to use the workaround "Save As"
Jimbo 88 Posted January 28, 2021 Posted January 28, 2021 (edited) Hey, I have this problem now too. I have a workaround. Freeze HaLion before save. Then when you re-open unfreeze. Edited January 28, 2021 by Jimbo 88 grammer
Noel Borthwick Posted January 29, 2021 Posted January 29, 2021 Steinberg has fixed this but have not released the patch to elicenser. They sent me a patch over a month ago. If you need it PM me and I can forward the link. 2 2
Byron Dickens Posted January 29, 2021 Posted January 29, 2021 I'm getting the same thing too. The workaround I found has been to alternately "save as" 2 different versions of the title such as [Title] and [Title1]
JoeGBradford Posted February 10, 2021 Posted February 10, 2021 Ah just got this too with a project with Halion Sonic in it! I remembered there being an issue and search came up with this thread. Does anyone know if they have issued a fix yet?
mkerl Posted February 10, 2021 Posted February 10, 2021 9 minutes ago, JoeGBradford said: Ah just got this too with a project with Halion Sonic in it! I remembered there being an issue and search came up with this thread. Does anyone know if they have issued a fix yet? PM Noel Borthwick, He's got a link to a patched elicenser. That one works. 2
pravind prasad Posted February 15, 2021 Posted February 15, 2021 can bandlab fix up this issue asap please
pravind prasad Posted February 15, 2021 Posted February 15, 2021 On 1/29/2021 at 2:08 PM, Noel Borthwick said: Steinberg has fixed this but have not released the patch to elicenser. They sent me a patch over a month ago. If you need it PM me and I can forward the link. send me a link on my email pls,,, pravo-1969@hotmail.com thanks
Simeon Amburgey Posted February 19, 2021 Posted February 19, 2021 * Update * I just heard that Steinberg has officially released the eLicensor update that fixes this issue. You can download it here: https://www.steinberg.net/en/company/technologies/elicenser.html 1
Noel Borthwick Posted February 19, 2021 Posted February 19, 2021 25 minutes ago, Simeon Amburgey said: * Update * I just heard that Steinberg has officially released the eLicensor update that fixes this issue. You can download it here: https://www.steinberg.net/en/company/technologies/elicenser.html @Simeon Amburgey Thanks can you confirm that their official update fixes the issue?
JoeGBradford Posted February 19, 2021 Posted February 19, 2021 Ah I am hoping that this is the one (saves me troubling Noel for the one he has)
Simeon Amburgey Posted February 19, 2021 Posted February 19, 2021 38 minutes ago, Noel Borthwick said: @Simeon Amburgey Thanks can you confirm that their official update fixes the issue? It appears to be fixed! Here are two scenarios I have tried. Open Previous Project and Save without doing a SAVE AS - FIXED Started an Empty Project, Loaded VSL Synchron Pianos and HALionSonic - Save - FIXED I also was able to save some previous broken projects with their pre-release version. It also appears the version number was bumped up a little more as well. I would say go get it. 2 1
mkerl Posted February 19, 2021 Posted February 19, 2021 Same here. Works fine. Saving, closing the project, reopen and changing some Instruments in Halion Sonic se, saving, no more problems Here is the release Notes: https://download.steinberg.net/downloads/Release_Notes.pdf?_ga=2.170654117.40775370.1613700749-1685742117.1599244740 1 1
JoeGBradford Posted February 19, 2021 Posted February 19, 2021 Yes just tried here too - just opened a project with Halion Sonic SE and saved it without any problems ? 1
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now