One has to keep in mind that VST Live does not deactivate any plugin instance when Parts are changed, unless shared instruments are beeing used. For now, the workaround is to end and restart VST Live before loading another project, sorry for that. This will certainly be fixed with the next version. Plugins are not released in this case, so memory consumption accumulates. We did find a problem though, which occurs when you load a project while one was already activated. Memory consumption comes from the plugins in the Layers (Halion Sonic SE). There is nothing special with your project. I wonder whether this has something to do with VstViewer - how do I uninstall it? CPU still at 102%Ĭlosed VstLive and it thought I’d changed something, which I hadn’t, started the app again. Not always by the same amount but it is cumulative and not released. One thing I noticed this time is that the memory usage increases every time I select a song. Restarted VstLive and was able to get it running again but playback cursor still choppy. At this point could actually play songs again but still choppy. Right click on task bar and quit app from there finally got to a windowed display after cancelling the force quit. After playing a couple of seconds of each song now unable to access the window green button to bring it out of full screen. Restarted the MacBook and the project would load and was responsive but the display was choppy- the playback cursor was not smooth. Memory usage at about 1GB but the CPU was at 103% (not sure how that is possible). After closing VstLive and reopening it locked up. I rebuilt a project with 3 songs in and just the stems.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |