Page 1 of 1
Direct Monitoring has huge latency. (Cubase)
Posted: Wed Dec 27, 2006 4:57 pm
by balaftuna
Hello.
Problem is that when I record with "Direct Monitoring" I get a very big latency (it doesn't sound direct at all).
I had this with Cubase SX3. when installing Cubase 4, I thought it was fine, but now it's bad again. (small chance that it was never OK, but I doubt it).
The only way I can record now is by NOT using direct monitoring, and use very low latency instead, but this is obviously a problem with big projects cause the CPU usage is maxed.
Not sure if this is related, but 2 more strange things are happening:
1)The default selected latency in Scope's control panel is 6ms, though cubase shows it as 22, and when re-selecting 6, cubase shows it as 4. Basically whenever I start cubase ( and it's been like that in previous versions too) I have to open the Creamware control panel and re-select 6.
2)Problem with MIDI sync. When recording MIDI and Audio, you actually see in the sequencer the MIDI notes BEFORE the audio.
I am a bit lost here, and these problems are quite big, so any help would be appreciated
Thanking you
Shay
Posted: Wed Dec 27, 2006 4:58 pm
by balaftuna
P.S.
Pulsar II
A16
Cubse 4.01 (though problems occured with previous versions)
Windows XP Pro
P4, 2.8Mhz.
Posted: Wed Dec 27, 2006 8:35 pm
by at0m
Do not use Direct Monitoring. Use a DSP mixer to monitor to analog out in Scope, that's what us pulsarians call direct monitoring

Posted: Thu Dec 28, 2006 1:00 am
by katano
which asio modules do you use for routing to cubase? i still work with asio monitoring, with asio2-24bit modules, i did never recognice any considerable latency in my work though most say this kind of monitoring is crap.
with asio 1 you'll definitively have more latency, as "zero" latency is introduced with asio2...
cheerz
roman
Posted: Thu Dec 28, 2006 7:46 am
by balaftuna
at0m & katano, thank you for your replies.
at0m, the monitoring method you suggested means no XTC mode, right ?
katano, .. forgive the ignorance, but how do I know which ASIO i use? I'm using cubase4, which was just released recently, so doesn't it mean it's the latest ASIO version?
cheers.
Shay
Posted: Thu Dec 28, 2006 7:55 am
by katano
Shay, it depends on the used software i/o modules in the scope routing window. you can choose asio, asio2 (in some variants), wave dest/source etc. btw wave dest will be the one with the biggest latency and is definitively not recommend for realtime recording.
in cubase you have to set the multitracker settings (i think it's called that way) to ASIO SCOPE.
As said before, ASIO2-24bit works best for me...
Good luck!
Roman
Posted: Thu Dec 28, 2006 8:06 am
by katano
ah, forgot to say that if you use some effects with lookahead in your recording path, turn this function of (or set to zero), else it will give you latency for shure...
btw. looooove ireland
cheerz
Roman
Posted: Sat Dec 30, 2006 5:15 pm
by Kymeia
at0m wrote:Do not use Direct Monitoring. Use a DSP mixer to monitor to analog out in Scope, that's what us pulsarians call direct monitoring

How do you set up the routing for this? Any screenshots would be helpful - thanks:)
I'd like to be able to record Scope fx when I insert them in my ASIO host but they don't seem to record and I end up having to use VDAT.
Posted: Sat Jan 20, 2007 2:29 pm
by balaftuna
katano wrote:
As said before, ASIO2-24bit works best for me...
Good luck!
Roman
I use ASIO2-24 bit too. 48KHz, but still have latency. The only way for me not to have latency is to change it in the control panel, but with big projects, it's a problem.
I also have a serious MIDI sync problem. The recorded midi is always BEFORE the audio. The audio is recorded in the right place, but i always have to move the MIDI tracks to the right for them to be in the right place. maybe the problems are related, and maybe not..
Any ideas?
Thank you.
Shay
Posted: Sat Jan 20, 2007 2:32 pm
by garyb
you will always have at least 3ms latency, it depends on the ulli setting.
as to the midi timing thing, do a search. usually the problem is a setting in the device setup in cubase. check "use system timestamp".
Posted: Sat Jan 20, 2007 2:39 pm
by balaftuna
garyb wrote:you will always have at least 3ms latency, it depends on the ulli setting.
as to the midi timing thing, do a search. usually the problem is a setting in the device setup in cubase. check "use system timestamp".
3ms is not a problem. 4 is fine too.
maybe i am missing something, or do not understand fully the 'direct monitoring' concept. suppose the latency in the asio control panel is set to 22, will the direct monitoring give me 3 ms or 22 ms latency?
Many thanks.
Shay
Posted: Sat Jan 20, 2007 7:28 pm
by garyb
the asio control panel is useless..or are you in xtc mode?
Posted: Sun Jan 21, 2007 8:01 am
by balaftuna
i am in xtc mode.
never used it in any other mode.. isn't this the easiest way of using it with cubase..?
Posted: Sun Jan 21, 2007 10:46 pm
by garyb
no.
scope mode looks difficult at first, but it works like the real world works and offers more possibilities.