#Ravenscroft 275 by vi labs cracked drivers#
But it might not be as bad using just the one mic I downloaded the ASIO4ALL drivers and Cantabile Lite 64-bit, both of which I am not familiar with at all.
The problem does still hang around when using just one mic position though. I'll try to respond as best I Yes I was using two mic perspectives close and room. Having said this, running the piano in a host, and not in UVI, seems to be the best option (for me and many others here) Also, other softwares running at the same time could have an impact on the CPU performance. UVI has seen a few revisions since then so it's possible that it now runs properly under its own steam.not too sure about that though.Īgree with the suggestions, however, the CPU is just decent, not very powerful, so it might be best to check the polyphony, and the number of options activated, in addition to the number of mic positions.
#Ravenscroft 275 by vi labs cracked driver#
Go to control panels/windows mobility centre and make sure the drop-down menu for 'battery status' is set to 'high performance'.Īnother test would be to abandon the audio interface and try the system using only the asio4all driver with the computers own motherboard soundchip.Įdit: yes, as voxpops has noted, running UVI inside a host improved matters when we first got hold of the Ravenscroft. That could possibly arise from your power settings.
If it does then that might point to the cpu underperforming. How many of the 4 mic position samples have you loaded up? If more than one mic position, try it with one position only to see if that improves matters. It's not too bad a cpu so perhaps it's surprising you're getting problems with such a large buffer - there's certainly no point in increasing the buffer size since latency must already be noticeable or close to it.
0 kommentar(er)
