olzzon
10-05-2006, 02:52 AM
Just discovered something that might explain why some have trouble with low latency.
Not curing everything, but some machines.
If i turn on midi and midiclock out to a Generic USB-midi interface with windows drivers.
Itīs impossible to run lower than 128.
If i however turns off, midi clock to all dev or switch off the USB midi, i can run at 64 with no problems when doing my other tweaks. (RT perf)
The device i discovered this with was my BFC2000, with just standard drivers. Iīm not using it. And if i was i wouldnīt use it as a midi device, but as a control device, so itīs no issue for me. But just a place to look if low latency is needed.
There are no problems when i send midi clock out to my RME midi ports on the digiface.
So anyone having problems with clicks, try to disable your midi in prefīs just to see if this is causing any problems for you.
Maybe itīs only the BFC2000 that does this, and maybe itīs the windows generic midi driver.
Not curing everything, but some machines.
If i turn on midi and midiclock out to a Generic USB-midi interface with windows drivers.
Itīs impossible to run lower than 128.
If i however turns off, midi clock to all dev or switch off the USB midi, i can run at 64 with no problems when doing my other tweaks. (RT perf)
The device i discovered this with was my BFC2000, with just standard drivers. Iīm not using it. And if i was i wouldnīt use it as a midi device, but as a control device, so itīs no issue for me. But just a place to look if low latency is needed.
There are no problems when i send midi clock out to my RME midi ports on the digiface.
So anyone having problems with clicks, try to disable your midi in prefīs just to see if this is causing any problems for you.
Maybe itīs only the BFC2000 that does this, and maybe itīs the windows generic midi driver.