Forums > MaxMSP

Reading .fxp file in vst~ does not close the file handle

June 8, 2012 | 8:31 pm

I am working on a vst host for live use (on Windows 7). I use a single NI Kontakt instance in a vst~ object. I noticed that when I read a fxp file (which represents a "song") with the "read" message the file stays locked and I can not overwrite it with the "writepgm" message (e.g. when I made changes to the Kontakt Multi).
Inspecting Max (latest Max 6 release) with SysInternals Process Explorer I noticed that when I load some fxp files (onme after another) that all of them have open file handles. Is this a bug or is there a workaround?

September 21, 2012 | 12:24 am

I too am having a problem with this. Any fxp loaded into vst will remain open, even after another fxp is loaded in its place. Any loaded fxps will remain "open" until Max is shut down. This makes it impossible to overwrite existing presets. Anyone figured out a solution to this?

September 21, 2012 | 1:15 am

Appears resolved in latest 6.0.7 release. Yay!

Viewing 3 posts - 1 through 3 (of 3 total)

Forums > MaxMSP