On a fine day, 01-05-2003, Colin Shapiro wrote: >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. Something like this has been around for a long time. In LA5.5 (and probably prior to that): Open EXS editor, edit an instrument, close editor without saving, even remove EXS from the insert slot. Now quit Logic, and it'll ask you if you want to save the instrument. What the f*? I guess this is the exact same problem. >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. Whether this is a bug or not depends. The 1st time you load an instrument, the EXS goes looking for the samples, and when found, writes the complete filepath into the instrument file -- thus indeed changing them (but for the better). Of course the next time you load the same instrument, the file should remain untouched. -- Hendrik Jan Veenstra <h@...> Omega Art: http://www.omega-art.com/
Message
Re: [EXS] EXS24 notes and problems (partly-VSL related)
2003-05-02 by Hendrik Jan Veenstra
Attachments
- No local attachments were found for this message.