#How to maximize eastwest quantum leap free
Just can't afford to dump all of those libraries on a 1TB SSD just yet, but I wouldn't think that's the issue, especially since I freeze a track once it's recorded to free up resources for streaming samples when recording/editing new parts.Item: 152988365176 Nouveau EastWest East West Quantum Leap SD2 Stormdrum 2 Sample Library. When I do a complete orchestral arrangement, that'll be the true test!) By the way, I have a SSD system drive and my EWQL libraries are all streaming from a separate 10,000RPM internal drive. (I'm only using 4 tracks right now, one for each of the main string groups. I bumped it up to 1500 milliseconds, recorded some additional MIDI, then froze/unfroze everything a couple times and thus far no dropouts, but given the seemingly random nature of the dropouts when rendering, I'm not 100% confident it won't happen again, but at least in this small test everything is working. I checked my MIDI preferences and "Prepare using" is already set to 1000 milliseconds. Regular playback seems to work just fine, but freezing the track doesn't. And it isn't a specific place/instrument each time (as if I'd done something goofy with the MIDI information while recording or editing). Unfortunately, when freezing the tracks, I'm still getting dropouts in the rendered file. Well, the good news is that with the newest Everett update, I haven't been able to replicate the issue of having to reload the instrument in order to force a refresh, so I'm able to go back and forth between several tracks, and whichever one is highlighted, it plays back the appropriate Hollywood Strings instrument. Anyway, in the off chance there are other EWQL Hollywood users out there running into similar issues, I'd appreciate some feedback! Thanks.
One last note: I don't run into any dropouts/hiccups when I play the stuff in the standalone PLAY, only within Sonar. I do have my interface buffer set to 64 samples when tracking (I record most performances in real time, so latency is an issue if I increase the buffer setting), and I know that can contribute to some dropouts, but I don't think it explains why I'd have to reload the instrument in PLAY to force it to refresh.
#How to maximize eastwest quantum leap Pc
CPU/RAM performance meter doesn't take much of a hit when I'm playing the samples, so I don't think it's my PC setup (i7 2600K, 16GB RAM). I'm running Sonar on a solid state drive, and my sample library is on a separate 10,000RPM drive. This will occasionally happen with the Hollywood Brass library, but the main culprit is Hollywood Strings.
So I end up unfreezing the track, soloing it, playing it for several bars, then freezing it again, and eventually I'll get the complete performance bounced, but it can take a LONG time with all that back and forth. I understand how a live playback could result in some dropouts, but the main purpose of freezing a track is to free up resources so you DON'T get dropouts, etc. When I freeze the track, quite often the resulting audio has dropouts as well. It's gotten to the point where once I've done this several times and finally have a performance I want, I'll freeze the track and cross my fingers that I don't have to go back and do meticulous MIDI editing since Sonar/PLAY keeps dropping out. Then when I go back to that previous track, there's no sound and I have to go back into PLAY, force it to reload the instrument, then it plays back fine. I'll load an instrument into PLAY, lay down a track, and move on. Most samples/articulations work great, but there are a handful of string patches (usually on the bow change articulations or true legato articulations) that cause dropouts during playback. Anyone here use EastWest Quantum Leap sample libraries, specifically Hollywood Strings? I've run into a handful of issues and I'm not sure if it's the PLAY software, something happening in Sonar, or a strange byproduct of my hardware.
0 kommentar(er)
