Thanx
ULLI...witch one?
-
Basic Pitch
- Posts: 627
- Joined: Fri Aug 15, 2003 4:00 pm
Well that depends on the sequencer you use, delay and buffer sizing. Setting may need to be changed when tracking vrs. mixing. For me personally when tracking I like to set as low a buffer as possible, but not so low the your system will explode and be brought to its knee's, so lets say a decent tracking buffer of 128, which should roughly equate to around 4ms of latency, then a mixing buffer of 512 which translates to around 6.x-7.x ms latency.
It really depends but those two settings are pretty general, of course there are many things that can change this, one being track size and audio count etc.
Changing these settings wont hurt a thing, you can always change it back, but I can say one thing for sure, if you have a half decent sized track count, I wouldnt bother with trying anything under 128 buffers, this will undoubtedly cripple your PC
YMMV..
It really depends but those two settings are pretty general, of course there are many things that can change this, one being track size and audio count etc.
Changing these settings wont hurt a thing, you can always change it back, but I can say one thing for sure, if you have a half decent sized track count, I wouldnt bother with trying anything under 128 buffers, this will undoubtedly cripple your PC
YMMV..
i don't also use any vst instrument. just reason and sonar and i'm ended up at 13ms. 7 or 10ms cause me nothing but crackles...can you tell me how do you do that 7ms!!!On 2003-09-07 21:02, alfonso wrote:
Hi, I don't use Vst instruments, so I don't need low latency, but if you use them, 7ms is decent enough...and not too demanding. If it's all tight with it you can try lower.
- Mr Arkadin
- Posts: 3283
- Joined: Thu May 24, 2001 4:00 pm
-
Shayne White
- Posts: 1454
- Joined: Tue Dec 11, 2001 4:00 pm
- Location: California
- Contact:
This is my performance report:
3ms (1.5ms in sequencer): high CPU utilization, prone to clicks and pops, poor reliability
4ms (2.9ms): slightly better reliability, but still high CPU utilization
7ms (5.8ms): still rock solid timing for soft synths, but much better CPU scores and reliability -- use this for tight performances
13ms (11.6ms): good general pupose setting -- 90% reliability (occasional click or pop when under heavy stress) and decent for performing
25ms (23.2ms): 100% reliability, no sound flaws whatsoever, excellent for mixing, but unacceptable for performing
I usually use 13ms unless I want solid timing when I'm performing, and then I switch to 7ms. Occasionally if I have a lot of Pulsar and DXi synths running at the same, I have to go up to 25ms. But I think 13ms is good for most stuff.
Shayne
3ms (1.5ms in sequencer): high CPU utilization, prone to clicks and pops, poor reliability
4ms (2.9ms): slightly better reliability, but still high CPU utilization
7ms (5.8ms): still rock solid timing for soft synths, but much better CPU scores and reliability -- use this for tight performances
13ms (11.6ms): good general pupose setting -- 90% reliability (occasional click or pop when under heavy stress) and decent for performing
25ms (23.2ms): 100% reliability, no sound flaws whatsoever, excellent for mixing, but unacceptable for performing
I usually use 13ms unless I want solid timing when I'm performing, and then I switch to 7ms. Occasionally if I have a lot of Pulsar and DXi synths running at the same, I have to go up to 25ms. But I think 13ms is good for most stuff.
Shayne
-
Shayne White
- Posts: 1454
- Joined: Tue Dec 11, 2001 4:00 pm
- Location: California
- Contact: