MOTUnation.com

Thanks brother.
In the meantime I think hosting the kontakt instance, housing the loop and instruments that are having pops/glitches, within DP is going to be my temporary fix. It seems to be working. "Seems".

Kevin

and i said I appreciate the suggestion.
in the middle of a feature and I am going to trouble shoot by creating a VEPro instance for each separate instrument in my template. I'm sorry you took offense to me not wanting to try out the suggestion.

best,
Kevin

thanks, but there is no way that's happening over here =) it's kind ofan absurd thing to do when my MIDI templates are huge containing upwards of 300 MIDI tracks. (mind you all 300 MIDI tracks are not all being used simultaneously) I appreciate the suggestion, but I highly doubt that CPU is the issu...

I am not quite sure I understand your suggestion. Here is how mine is set up. for example: VEPRo server running with about 8 instances minimum in it. Each instance has about the max of 16 different instruments. Each of those instances are routed to a VI instance in DP. Are you suggesting I have an V...

Here is the issue, if any one has ANY insight into a fix, or what's going wrong....i am all ears. scenario: say bars 1 thru 10 are at 80bpm. On bar 11 the tempo changes to 120bpm. Any samples triggered on bar 11 hiccup, pop, or click. If I have a loop start exactly on bar 11 the loop hiccups and it ...

Just chiming in here. video play back IS terrible and stuttery and choppy. Very sad that they tinkered with something that didn't need to be upgraded or messed with. DP3-7 was flawless and playback. Now it's terrible. Almost to the point where scoring to picture is irritating. tempted to boot back u...

are you guys using quite a few chunks in your sequence? and is omnisphere/trilian in each chunk, or as a V-rack. Don't forget that each VI in each chunk whether the chunk is active or not) still gets loaded into DP. As these 2 guys are memory hogs, that might be it? Just a thought :roll: this is my...

aramis, i am having the same issue but with Omnisphere alone.
no matter what i set the memory settings at, i still get errors.

I've heard it has something to do with Omnisphere not releasing the memory after loading different sounds, and or moving from chunk to chunk.

The strange thing is that it isn't consistent from one VI to another, or even one sample-based library to another. Sometimes it just seems to reload top-level info without reloading actual samples. It does the same thing after BTD is finished. In cases where the entire sample set is reloaded or unl...

thanks Itemma74, i appreciate the linkage. well to be specifc...my latest question is why does having 3 or 4 instances of any instrument (mainly KONTAKT x3) in v-rack hog up way more CPU(like 80% more) than if loading each instrument into the sequence. This of course is a hassle as when i now change...

nice, honestly dude. I was just asking if anyone knew anything. seriously...just take it easy. you do have valid points. but man. wow. can i just ask with out stirring up the pot? a simple i don't know would suffice...or maybe or yes or now. I don't have the time to sit here and list ALL the trouble...

well its not a matter of whether it works on my system or not...I was basically asking if anyone knew about a rebuild that's all. Maybe i should have just asked that instead of saying 'unstable framework' or that its running fine...(with many inefficient work-arounds that is) that's all...just askin...

When is motu going to rebuild DP from the ground up, instead of just adding and modifying what exists on this unstable framework!?? Not a disgruntled user at all...DP runs fine on my system. But isn't it due time for it to be completely redesigned (underneath the hood). If something was announced al...

Anyone alse having the issue of Copying existing Tracks to a New Sequence and then it hangs (Not Responding)....needing a 'force quit'

No idea what could be causing this. Though it might be the Track Folders I set up, but tried with out them and still hangs.

Anyone????