James wrote: >Saved me so much pain in the butt when I did the >resolve thing, but I never re-locked the files. Is there an advantage to >that? I do change them on a fairly regular basis. I've found a number of >programming errors that were really annoying for a software package this >expensive. The big one is the key switching. On a very erratic basis I've >found the manual says the switch is at C0 and the program has the switch at >C-0. Little things like that I've had go in and correct. Sure, for what you describe above, they must be unlocked. However, I discovered a bug (known) which worried me and prompted me to post as below: Bug#1: Here's a nasty one: Select an EXS24 instrument (eg VI-14_sus_basic-EN.exs) Open the EXS24 Instrument Editor and modify a few settings. Close the window - you get an alert asking you if you want to save or not. DON'T save. Select another instrument, then go back to VI-14_sus_basic-EN.exs Open the Editor. Even though you chose NOT to save changes, the instrument will still be in the edited state in which you last left it. Not even closing the song helps - you have to quit Logic to reset the instrument. I don't know if the Project Manager is at fault, perhaps retaining settings in a buffer of some kind. This is a serious bug and completely inhibits a user when editing instruments. Bug#2: Warning: Re-lock your files I found that after some editing experiments (and choosing NOT to save any of my edits), some instrument files had new dates with the current time - in other words, Logic or the Project Manager had somehow decided to overwrite the .exs files. Until these bugs are fixed, I have locked all my instrument files again (thank you Golden Key!) until further notice. I don't feel like having to re-install from DVD every time I try out some experiments. I have forwarded these bugs to Emagic. Regards - Colin
Message
Re: [EXS] Major freezing using VSL. Help, anyone?
2003-06-14 by Colin Shapiro
Attachments
- No local attachments were found for this message.