|
Post by toodamnhip on Oct 10, 2016 19:52:28 GMT -8
Sometimes there is a non optimum working relationship between Raven and DP that a user “knows is not right”, but doesn’t know how to explain it?
Well, for awhile now, I have seen what I finally realized might be some sort of “data overload”, when using touch mode in DP.
First off all, touch mode for long periods of time, like 1 min or what have you, can at time FIGHT between the interface and DP>, with the fader trying to jump or moving a small amount. This may be occurring less when actually writing data, as opposed to holding a fader with prior automation to a new position while in touch mode.
But where thing get weirder is when Raven completely goes out of communication with a channel necessitating a re start of the main computer to get things to work again. I am starting to see that using touch mode, holding a fader in place for a minute or so, while NOT writing, can result in the fader losing all communication. Either permanently necessitating a re start, or momentarily. It would be nice if engineers could make a really packed DP session , with audio, tons of mix plug ins, and slaving lots of VOs in VE Pro, and watching what happens under the hood when holding down a faders in touch mode.
|
|
|
Post by jameyz on Oct 11, 2016 6:34:16 GMT -8
Sometimes there is a non optimum working relationship between Raven and DP that a user “knows is not right”, but doesn’t know how to explain it? Well, for awhile now, I have seen what I finally realized might be some sort of “data overload”, when using touch mode in DP. First off all, touch mode for long periods of time, like 1 min or what have you, can at time FIGHT between the interface and DP>, with the fader trying to jump or moving a small amount. This may be occurring less when actually writing data, as opposed to holding a fader with prior automation to a new position while in touch mode. But where thing get weirder is when Raven completely goes out of communication with a channel necessitating a re start of the main computer to get things to work again. I am starting to see that using touch mode, holding a fader in place for a minute or so, while NOT writing, can result in the fader losing all communication. Either permanently necessitating a re start, or momentarily. It would be nice if engineers could make a really packed DP session , with audio, tons of mix plug ins, and slaving lots of VOs in VE Pro, and watching what happens under the hood when holding down a faders in touch mode. Are you on the Latest Raven version 3.2??? I just tried this on a huge session and everything felt and looked right.. Can you shoot a little iPhone video or something?? Are you using any other controllers that could be interfering, Like Komplete Kontrol or something else with HUI? V-control must first be opened and connected to the DAW for Raven to work correctly. Here is how to reset the V-control prefs. Maybe deleting the prefs will help..
|
|