Stringpark wrote:Hey there, I'm fixin' to ask a stupid question, I can just feel it, but here goes anyway. I am trying to set our drummer up with a BFD Eco rig for live use. Here is the setup: Laptop: 1.66GHz Core 2 Duo, 1GB RAM, 120GB 5400 RPM HD, WinXP Pro SP3 (probably not the best hardware, but the price was right). Audio Interface: Alesis IO|2 using the ASIO4All driver. Kit: Stock V-Session (TD-10).
So, I've tried to tune up XP as much as possible (though I haven't messed with the page file yet) and the performance monitor shows about 500MB or so of RAM in use with Eco running. I have the RAM buffer in Eco set to 32k since the HD is only 5400RPM. I do not have "Load on demand" selected. With all of above configuration, I am able to run my buffer size down to 192 samples @ 48kHz before audio problems set in. So, I think this works out to 4ms of audio latency on top of whatever midi delay there may be in the chain, which I have not yet investigated (I just simply connected the midi out of the TD-10 to the midi in of the IO|2). I don't guess 4ms is too bad, but since RAM is cheap, I was just wondering if adding RAM might enable me to reduce the buffer size any?
Stringpark wrote:...There is virtually no distinguishable difference in the timing of the Eco sounds vs the internal Roland sounds...
NicoD wrote:Modules also have latency so you still need to add the internal time from your TD10 to your midi and audio latency.
NicoD wrote:You can measure the latency from your module by plugging an Y-cable into the pad. One cable into the line-in (1st mono channel) audio interface, other cable into module. Record on the 2nd channel output from module. With an editor you can see the delay between the piezo signal and audio from module. Roland modules seem to have around 4 ms latency.
Users browsing this forum: No registered users and 1 guest