I'm new to Usine(couple of weeks now). Great program. Really enjoying it. After 5 years in SM, it's a nice change.
Got a nasty problem though. All the VST Plug in tests I've made so far fail my timing tests in host(FL Studio).
SO before I start uploading my "clocks" for you to look at, I decided to try some stock usine modules.
I started with the "Bassliner" module. I did nothing to it. Cut a vst plug in(with usine and Easine) and I get the same
results. Timing is way off, and it's drifting.
Is there a module in Usine that offers 100% accurate timing?(or a example somewhere)
Does Usine have any known timing issues?
Does usine have any known issues with FL Studio?
Note: all my clocks miss the first note in host-still working on that.........
Note: using latest versions of Usine and Easine.
VST Timing problems
Never test Vst made with Easine in FL studio,cause i don't have this host, have you test in other host too..?
have you test different values for your soundcard latency..?
Maybe some FL Studio users can help you here
have you test different values for your soundcard latency..?
Maybe some FL Studio users can help you here
yes, in Abelton Live as well.
Soundcard latency-I'm looking into that area now.
But my main question has not been answered.
Can Usine plug ins achieve 100% accurate timing in a host?
Soundcard latency-I'm looking into that area now.
But my main question has not been answered.
Can Usine plug ins achieve 100% accurate timing in a host?
hello Billv,
The timing clock in VST's is done by the host, not by Usine.
After few more tests I confirm that the accuracy of the clock is good according the clock given by the host.
For the test I've just exported as a Vst the metronome patch.
It means that your pb comes probably from elsewhere?
To answer to your second question, all the timers in Usine are accurate!
Moreover, the more you reduce the best bloc size (see setup) the more they are accurate.
So for example if your sound card delivers a bloc size of 2153 samples you'll have a very bad overall clock. And in this case Asio4all can produce miracles...
senso+++
The timing clock in VST's is done by the host, not by Usine.
After few more tests I confirm that the accuracy of the clock is good according the clock given by the host.
For the test I've just exported as a Vst the metronome patch.
It means that your pb comes probably from elsewhere?
To answer to your second question, all the timers in Usine are accurate!
Moreover, the more you reduce the best bloc size (see setup) the more they are accurate.
So for example if your sound card delivers a bloc size of 2153 samples you'll have a very bad overall clock. And in this case Asio4all can produce miracles...
senso+++
Olivier Sens
www.brainmodular.com
www.brainmodular.com
Great news. Thanks Oliver. Will try the metronome ASAP, and the "bloc size" options. Cheers.
Done lots of tests.
Here is the metronome. At 128 bloc size setting it's no good, but I brought it all the way down to the fastest setting
and it came up pretty close. There's not much drift in it either. Seems solid. Still have to build a big synth/seq and test
under a full load yet, but it looks promising. Doing lots of other tests with Master and Local sync, and other modules-will
take me awhile to understand the logic of how the modules are communicating-interesting program. Thanks Oliver.
Here is the metronome. At 128 bloc size setting it's no good, but I brought it all the way down to the fastest setting
and it came up pretty close. There's not much drift in it either. Seems solid. Still have to build a big synth/seq and test
under a full load yet, but it looks promising. Doing lots of other tests with Master and Local sync, and other modules-will
take me awhile to understand the logic of how the modules are communicating-interesting program. Thanks Oliver.
Who is online
Users browsing this forum: No registered users and 23 guests