![]() ![]() The song in question uses 9 instances, along with a bunch of other VSTs. Also I tend to use just one patch/channel per Omnisphere instance. According to the Sonar resources thing I'm using 57% of my system memory. But, what is it exactly that's going on here? Is it a resources issue? I would have thought freezing the track in the original project would be good enough for resource related issues. We've got a serviceable, although annoying workaround. BUT then I froze the track in the new project and copied the frozen audio over, and that works great. ![]() I froze the track in the original project and it freezes with the crackling. And comparing the two is night and day, it's totally clean in the new project, then I jump over and its crackly (even when soloed) in the other project. Now it did seem to save the higher preload memory size as a default in omnisphere, so we're working with that and a brand new sonar project. SO, I went to the other suggestion of creating a new project and copying that single midi track over to it with a new instance of Omnisphere using the same patch. But on the next song I tried, it didn't seem to be making a difference. the crackle is much more apparent out there than on my monitors/headphones. Funny thing is on one song it seemed to be working (I'll know better once I go play it in my car. I found the setting to slide up the preload memory size. In that scenario, there is little benefit to multiple instances beyond separate freezing. However, the CPU benefit of multiple instances depends on whether or not the patches actually play concurrently. Because I typically use Omnisphere for color and accents rather than main instruments, I'll often have many patches in a single multi that aren't all playing at the same time. Consult your host's documentation to make sure that it has support for multi-core/multi-processor systems. So the most efficient use on a multicore machine is to use a couple of instances multitimbrally - if assigning all Parts to a single instance is using up all the resources of a single core. ![]() The resource handling is done by the host, so in this case it's useful to open more than one instance of Omnisphere. However, if a multi-core system is used, it can be beneficial to open multiple instances of Omnisphere to distribute the processor load between the cores. This is the best way to utilize the available CPU power for Omnisphere. Here's what Spectrasonics has to say: On single and dual-core systems, it's best to load multiple Parts (on different MIDI channels) within a single instance of Omnisphere, before opening any additional instances of the instrument. Separate instances will also allow you to freeze instruments individually. Could there be an option to play with in my Audio / Driver settings? I mean my songs have been getting bigger than they ever were in the past, but I'm pretty sure I'm good as far as RAM and my Processor is concerned for projects of the size I'm working with.Ĭan anyone think of anything that could be causing this or any way to fix it? These songs are in the mixing down phase, so I'm fine with freezing the tracks, but even then the crackling seems to freeze along with them. I'm pretty sure it's not an issue of resources. The crackling noises happen in the same spots every time I play the song.Īlso, I've found that panning that particular track with an effected Omnisphere patch in it to the left or right makes the problem much worse. It's only when a full song of multiple tracks is going does the issue start to happen. BUT, if I play that patch by itself, it sounds fine. Basically some of the patches are hot/crackling/staticky. I'm having an issue with Omnisphere that I never used to have. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |