![]() ![]() All he does is describe the technical stuff, which tells us end users ABSOLUTELY NOTHING. Yes (and thanks) but it is NOT an explanation. I found schwa's explanation (which I posted above), here: Why would you want to run EACH plug-in in a dedicated process? Since each plug-in will run in its own process, it won't take others down with it if it crashes, for example.Īs far as I know "Buggy compatibility mode" used to be a global option and now it's only available per instance via the FX Browser. Why would you want to run several plug-ins in the same process? Well, one process use less CPU than several processes running separately. Here you can see I'm running 2 plug-ins in "dedicated processes": EACH plug-in runs in a dedicated process: Now, let's select these two plug-ins, right-click on them and run them in "dedicated processes". Since this is just ONE bag, all plug-ins set to run in a "separate process" will share RAM and CPU. It's a like putting all plug-ins set to "separate process" in ONE bag. ![]() This is a common process where all plug-ins set to "separate process" run in. Here you can see I'm running two plug-ins in a "separate process": In the FX Browser, if we select both, right-click on them and choose "Run in separate process" they'll both run in the same process: A and B running in the same process: I will also ignore "buggy plugin compatibility mode" doesn't exist, since the manual doesn't even talk about it. Temporarily, I will assume that the "separate" selection within the FX window is meaningless, and will only use "dedicated" for my questionable plugins. It's amazing to me that the manual doesn't have a clear chapter explaining every aspect of this crucial topic. It also doesn't tell me if going back to prefs and selecting "only in native" overrides the FX window settings. It also doesn't explain what "Buggy mode" is, and I can't find the answer either in the manual or in the forums. If this were true, there would be NO REASON to have a "separate process" option in the FX browser, since this would not be possible on a per-plugin basis.Īdditionally, I can say 100% that running just 5 plugins under "separate process" FROM THE FX window took a LOT more cpu power than setting ALL the plugins to one separate process, from the Prefs window. Running plugins in a dedicated process will run each plugin in it’s own process, each with it’s own RAM allowance." The RAM will be shared by all the bridged plugins. "Running plugins in a separate process will put all the specified processes in ONE other process, like one other program. I read it, but that explanation MAKES NO SENSE. I just posted a blog about this yesterday ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |