I've got bought and registered copies of Angelina (and the other Big Tick plugins, but it's Angelina that seems to have this problem).
I'd got a project open on my host (SONAR) with Angelina inserted, and had a rare crash. Re-opening SONAR and then the project caused Angelina to report that it was unregistered (bad in itself) and that I couldn't save in the unregistered version. I duly entered my registration code into Angelina, which re-registered it, and could save the project fine.
However...on re-opening the project, Angelina would unregister itself repeatedly. So I saved the fxp of the edited program, re-registered Angelina, and loaded the fxp. Angelina would unregister itself.
There was no seeming way to recover the state of Angelina from before the crash short of noting down the patch details manually and re-entering them (and re-creating an envelope in Angelina is not a quick job).
Loading a patch should not unregister the plug-in, and neither should an application crash. Fortunately, the Big Tick method of registration is pretty painless, but imagine if this had been a challenge/response type method...I'd be completely screwed.
When a host crashes...
-
- KVRian
- 694 posts since 6 Aug, 2002 from London, UK
-
- KVRAF
- 3002 posts since 24 Nov, 2003 from Heidelberg&Hamburg
Hi there,
this is an old problem, which I get too here. The only solution at the moment is this: I built - after registering the Angelina again - a preset (storing presets works only with the registered version
) a preset (a fxp file, that is) with exactly my registration info. That's not the best solution ever, but you don't need to search the info again or have it in your brain
like I tried. You just load the preset with your number and Angelina is registered.
I guess 'Tick will change this soon, as the wonderful Rhino2 doesn't suffer from this strange thing. But until that time do like that and at least it saves you one step.
Second thing I do is I render the angelina tracks after I'm happy with them.
Yes, it's annoying, but after I work with those steps I can go on with my music instead of going to search for computer-bugs. And mind, I know Mac- and Linux AND PC-users who work 40% of their time thought for making music on hunting strange bugs... For example in Vista before sp1 there was this strange bug that nearly ALL software, given to us by friendly developers like 'Tick with a lovely serial instead of challenge/response or even a syncrosoft-dingle-dumble, de-registered itself every new start... you had to switch off UAD in msconfig to get that bug away. And my challenge/response software (arrrgh) de-registered itself too every 3 days - because at that time I had in a very remote place internet just with "umts". This network configuration and Vista got the software to "think" it was not registered.... my, my....
And there was no way out until Microsoft found a bugfix (included in sp1 since quite some time now). So in comparison my Angelina-solution seems like not a big problem to me
.
cheers!
this is an old problem, which I get too here. The only solution at the moment is this: I built - after registering the Angelina again - a preset (storing presets works only with the registered version
I guess 'Tick will change this soon, as the wonderful Rhino2 doesn't suffer from this strange thing. But until that time do like that and at least it saves you one step.
Second thing I do is I render the angelina tracks after I'm happy with them.
Yes, it's annoying, but after I work with those steps I can go on with my music instead of going to search for computer-bugs. And mind, I know Mac- and Linux AND PC-users who work 40% of their time thought for making music on hunting strange bugs... For example in Vista before sp1 there was this strange bug that nearly ALL software, given to us by friendly developers like 'Tick with a lovely serial instead of challenge/response or even a syncrosoft-dingle-dumble, de-registered itself every new start... you had to switch off UAD in msconfig to get that bug away. And my challenge/response software (arrrgh) de-registered itself too every 3 days - because at that time I had in a very remote place internet just with "umts". This network configuration and Vista got the software to "think" it was not registered.... my, my....
And there was no way out until Microsoft found a bugfix (included in sp1 since quite some time now). So in comparison my Angelina-solution seems like not a big problem to me
cheers!
