DP 7.22 Kontakt 4.1 volume control problem

[aztic]

Hi,

I am new to DP but has been reading this forum for awhile. I am using 7.22 with Kontakt 4.1 and recently encountered a rather weird situation.

On some of my projects, I could not control the volume of Kontakt without leaving the VI window open. That says, when I close the VI window, and try to move the volume slider in mixer window, there is a short clip sound and a short stop of the VI playing, and then the volume remains the same. Also when I close a opened Kontakt window, the clip sound and the short stop happens. However, if I leave the Kontakt window open, everything resumes normal.

I have tried to isolate the possible causes of the problem by:
1. Creating a new project: things will get back to normal, but at one point, this situation comes up.
2. Deleting the original Kontakt and creating a new one: Does not work.
3.Change my audio driver (from Apogee Duet to System audio): does not work.

I searched the forum but did not find previous posts regarding to similar situation. Has this happened to anyone here? Is there something I can try to further identify the cause of the problem?

Thank you!
aztic

[James Steele]

I suspect what is going on here is that Kontakt is responding sluggishly to MIDI volume, as many VIs do, because when its window is closed it goes from real-time mode to pre-rendering mode. To alleviate this, put the Kontakt instance in real-time by clicking the little menu widget in the upper right of the DP VI window and select "Run in realtime."

[aztic]

Hi, Mr. Steele,

Thank you for your fast reply, and, it IS the cause of the problem!!
I have searched for solutions for 2 days but could not find any answer.
Although I did see your response to other people's posts about this VI problem, I did not realize it is related.

Thank you, Thank you!
aztic

[James Steele]

Not a problem. It's always nice when we get the right answer. One of the reasons I got it is that you gave a good explanation and the fact that you mentioned that it went away when the GUI window was open was the clue that gave it away. You see, when the GUI window is open on a VI, DP automatically takes the VI out of pre-render mode and into real-time mode. The reason for this is obvious: DP assumes that if you've opened a VI, it is likely your intention to make real-time parameter adjustments, hence it MUST be real time.

One other thing to look out for too. If your VI is NOT in realtime mode, you will lose audible mode in the MIDI graphic editor window. Clicking a note will not sound the note on the VI. The workaround is to temporarily record enable the MIDI track which will then take the VI out of pre-render mode. When you've done your edits, turn off rec-enable and the VI will return to pre-render mode.

BTW, once you feel you've made all the volume adjustments you expect to make, you can turn off realtime mode to save some of the CPU hit if you no longer need the responsiveness.

[aztic]

Thank you for all the information. Actually it answers some questions that come up to my mind after I know the cause. Now I have a better understanding about what is going on!

Thank you so much!! I mean, I saw a lot of posts in other forums talking about that MOTUNATION has some of the most friendly and patient people that they have ever seen. This is my first post on the forum and I do appreciate being treated so nicely as a new comer.

aztic

[Timeline]

I suspect what is going on here is that Kontakt is responding sluggishly to MIDI volume, as many VIs do, because when its window is closed it goes from real-time mode to pre-rendering mode. To alleviate this, put the Kontakt instance in real-time by clicking the little menu widget in the upper right of the DP VI window and select "Run in realtime."

This is another good one for a prefs addition surely!