Re: WinXP - Win 8 --- something I need to know ?!?
Posted: Mon Oct 21, 2013 11:18 am
You know, I really hope we can get this fixed because its essential in vst production. Take my example, I use the save/load for registering and keeping a plugin unlocked (once successful registration, write file so that it can be loaded every time and unlock the plugin). However this is turning to quite the hunt! Ill explain. . .
So as I said, once you register the vst writes a "unlock" file to Appdata/Roaming. Now when you load the vst, it checks if file is there, if so, unlock. Simple. . . hah, well I have found out that the vst writes the file no problem, but when it comes to loading it up. . . nope! (huh? I thought we had a folder access problem?) This doesnt make sense!
Maybe we are the only ones who need something like this to work on many different machines. Maybe not, but either way its gotta get right.
My whole issue is why do we need to find another way of writing/loading files when they work perfect on certain machines? This leads me to believe that its NOT our code, or the way we have done things but rather something that lies with the multitude of different systems and setups.
Hmmm... its hard to test too because while you have tested on 5-6 machines and all OK, you will get some coming back saying its not working. And on top of that one user will report it ONLY works in Live and another saying it doesnt work at all in Live. . . there is no resolve from this.
More and more I am thinking it is down to individual user systems but there still lies the problem!
Im off to try some Marshalling and see if that helps. . . .
So as I said, once you register the vst writes a "unlock" file to Appdata/Roaming. Now when you load the vst, it checks if file is there, if so, unlock. Simple. . . hah, well I have found out that the vst writes the file no problem, but when it comes to loading it up. . . nope! (huh? I thought we had a folder access problem?) This doesnt make sense!
Maybe we are the only ones who need something like this to work on many different machines. Maybe not, but either way its gotta get right.
My whole issue is why do we need to find another way of writing/loading files when they work perfect on certain machines? This leads me to believe that its NOT our code, or the way we have done things but rather something that lies with the multitude of different systems and setups.
Hmmm... its hard to test too because while you have tested on 5-6 machines and all OK, you will get some coming back saying its not working. And on top of that one user will report it ONLY works in Live and another saying it doesnt work at all in Live. . . there is no resolve from this.
More and more I am thinking it is down to individual user systems but there still lies the problem!
Im off to try some Marshalling and see if that helps. . . .