Sorry to ask a stupid question, but has the global dry/wet control changed, either by accident or by automation?
DG
200,014 users have contributed to 43,190 threads and 259,035 posts.
In the past 24 hours, we have 2 new thread(s), 18 new post(s) and 96 new user(s).
Hmm ... hard to tell from the distance. Is the silent Icon placed outside the valid HotSpot area, maybe? (... but then it shouldn't play back anything at all.)
If the problem persists, please send the VI-Frame to our support - we will look into it.
Kind regards,
As a matter a fact it was a problem of latency. I chose a larger latency value and the instance with the problem began to work. Thank you very much for the help.
I studied the problem a bit more and I'll try to explain what happens. If in the VEP server the Vienna MIR latency is set to 0 it results in the following manner. Four of five instances are working and one plays back the dry signal. The problematic instance is always the one I have been feeding midi data last. For example if I have chosen the piano track and played some notes on my keyboard, the VEP instance containing the piano goes dry. If I then press play, all other four instances are working just fine. If I then play for example the trombone with my keyboard, the VEP containing the trombone goes dry and the one containing the piano starts to work again and so on. Does this make any sense.If you know the reason for this, that's good. If you don't I'm glad to offer any information you wish.
Sorry, I'm not very good in these kinds of things, but I'll try to give you all the information you want. My system is:
Mac pro with 2xQuad-Core Intel Xeon 2,8GHz 16Gb RAM
Os X 10.6.8
Logic pro 8 with VEP5 in server mode
Apogee Duet as audio hardware
What more would you like to know?