April 10Apr 10 Sorry to be insistent on the topic, I just want to help people that use windows machines.
April 10Apr 10 Author The fade instrument itself appears to compile correctly. The important part of the log is that clm_cross_fade.dll is created successfully. The real failure happens afterwards, when LispWorks tries to rename:E:\Opusmodus\clm\bin\t_fade.64ofasltoE:\Opusmodus\clm\bin\fade.64ofaslWindows reports that the file is being used by another process (error 32).Please try this:Close Opusmodus completely.Check Task Manager and make sure no other Opusmodus process is still running.Delete these files if they exist:E:\Opusmodus\clm\bin\fade.64ofaslE:\Opusmodus\clm\bin\t_fade.64ofaslAlso delete:E:\Opusmodus\clm\libclm\clm_cross_fade.*E:\Opusmodus\clm\libclm\clm_dissolve_fade.*Start Opusmodus again and load Load CLM Instruments.lisp once more.If it still fails, the most likely cause is that antivirus or another background process is locking the .64ofasl file in the bin folder.
April 10Apr 10 Author or simply add a comment (;) to the particular instrument in the "CLM Startup Instruments.lisp" file:; "fade"
Create an account or sign in to comment