kkiiwwii wrote:I thought I had finally come to the end of my Breeze/Reaper problems, but a relatively small iritant remains. Everytime I start the combined programme, the starting GUI of Breeze comes up and I have to reinsert the authorisation key all over again, and then reselect my chosen factory reverb algorithm. This is just time consuming, especially as each block has to be inserted separately.
I'm guessing it may be a Reaper problem and I tried to get an answer from their forum, but cannot get in to it. There are over 20 options (yes) on right clicking the fz window and several choices in the VST information area. I'm a bit apprehensive of going back to my previous problem of not being able to input this code at all- I,m not too sure what I really did to fix that one.
Has Bill or any other Reaper user got any suggestions please
Charles
Charles
On both of my PC's and my IMac I am not seeing the symptoms you are.
On the Options | Preferences | General Tab check to see if you have yours set like mine:
http://cid-4cea0fc232061b19.office.live.com/self.aspx/VST%20and%20Hauptwerk/Startup%20Options.jpg
What this does is load the last used project where you have already entered the Authorization Key. On my computers Breeze also remembers the last used Factory Reverb setting.
Another thought comes to mind. If you are running a Window 7 or Vista system, you may be getting bit by UAC (User Account Control) found in the Control Panel. If it is set too high you are unable to save info into System type directories. For a test, go into Control Panel, find the UAC and move the slider to the lowest level of security (you may have to reboot to get it to take). Next, go back into Reaper and set it up. Exit Reaper and reenter Reaper to see if your settings have been saved.
If that is the case, you can then reset your UAC back and Reaper should continue to work normally.
Quoted from Wikipedia "User Account Control (UAC) is a technology and security infrastructure introduced with Microsoft's Windows Vista and Windows Server 2008 operating systems, with a more relaxed[1] version also present in Windows 7 and Windows Server 2008 R2 . It aims to improve the security of Microsoft Windows by limiting application software to standard user privileges until an administrator authorizes an increase or elevation. In this way, only applications trusted by the user may receive administrative privileges, and malware should be kept from compromising the operating system. In other words, a user account may have administrator privileges assigned to it, but applications that the user runs do not inherit those privileges unless they are approved beforehand or the user explicitly authorizes it."
Bill