I was so sure I was doing something wrong in the workflow, too. I'll be purging the samples in Kontakt and only keeping the ones I need loaded. It was loading all the samples of the instrument to memory, and I had multiple instances of Kontakt running. As soon as I loaded it, the memory usage started shooting up. Thank you! I found the culprit this way! I was so sure that the plugin I was trying to edit (EWQL Play or ProVerb) was causing the crashes, but it wasn't. But, are you able to create a New Mix in the mixer window? If so, and if it does not crash, maybe try adding a plugin one at a time, test it out, and see if a particular plugin is implicated in the crash.Īs an example, I recently had crashes caused by a wayward Lexicon plugin, but I'm on a Mac so YMMV. Processor: Intel Core i5 2500k Quad core 3.3Ghzĭrives: Crucial M4 256GB SSD, Crucial M4 128GB SSDĮDIT: I did submit a Techlink with MOTU as well.īillf wrote:I'm not a Windows user, so it could be specific to your platform. Interface: Scarlett 2i2 (with passive DI box in front) I performed all updates to DP and my plugins in use.Īm I doing something wrong to have all this RAM in use? It doesn't seem like 2 Sequences, a v-rack, and a Song should be killing everything like this.Ĭontrollers: M-Audio Oxygen61 and Oxygen25 I guess I could start the project over from scratch, but I'm worried this will just repeat itself. It still uses a ton of RAM and crashes when I try to mess with plugins like ProVerb or East/West plugins. I've tried starting a new project and loaded each chunk in, starting with just the v-rack. No matter what I do, I can't seem to find a workaround to save my project. I have 16GB of RAM, and ~45% is being used when I have this project open, which is a lot of usage and probably the cause of the crashes. DP crashes when I try to either add ProVerb to a track or when I try moving/deleting the EWQL Play insert plug-in. I don't have that many tracks and plug-ins yet since I just started the movie. I have a project with a standard definition movie loaded (hour and a half, ~260MB), 2 Sequences, 1 v-rack, and 1 Song comprised of the 2 sequences. Second, I'd kill to have an old guru to shadow every day as I learn this stuff. In these situations, if you encounter audio glitches related to streaming, the first step is to thin the samples.First of all, I had the harebrained idea to learn DP by using it for a new job. This is most likely to happen when multiple large sample-based Patches have been loaded into multiple Parts, or when using patches originating from the Keyscape instrument. When Omnisphere is loaded with a large number of samples, CPU overload or streaming issues may arise. Sample Thinning is an important concept in Omnisphere, and allows Soundsources, Patches, and Multis to load with fewer samples, using less system memory and CPU. In some situations, you may need to perform several of these actions to remedy CPU overload issues. The actions are listed in roughly the order you should consider them-starting with the easiest and highest payoff actions. You should consider all the actions listed, but note that some actions may not be appropriate for your circumstances. This section describes actions you can take to minimize audio glitches and CPU overload. For this reason, we have included a number of memory management features that you can enable in Omnisphere to help manage your computer’s resources. Additionally, some Patches use CPU-intensive FX units which might result in CPU overload, which can cause audio glitches. If your system is not configured properly, streaming some Patches may not be fast enough and may produce audio glitches. However some Patches employ sophisticated effects or large numbers of streamed samples, and those may require special attention. The vast majority of Omnisphere Patches will play comfortably within your host, without over-stressing the computer’s CPU or memory.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |