PlanetZ forums - scopeusers.com

I´m working with my pulsar2 and Cubase SX 3, and I´m getting lots of latency this time. The computer is well set-up. I did it many times already, so I don´t think I got anything wrong. I also have a working creamware plataform in my home, and it works fine for me here. But in the studio, I´m getting this latency in the ASIO audio playback, and I can´t be sure where it comes from.

I´ve set up the computer really well, no internet, disabled all services I don´t use (I´m really used to do it), and all windows frills. So, The cubase runs fine and even in the lowest possible latencies I can playback more than a hundred channels with good amount of reberbs and comps. The problem is that in the VST device window it shows the 4ms, or 7ms I´m used to, depending of my settings on the Scope program. BUT, still, I hear LOTS of latency, more like 200 or 300 ms... when I try to monitor throught Cubase.

Does anyone experienced this problem already?

It would be great for me if I can monitor direct from cubase in realtime, just like I do at home... I can´t understand why it´s not working at my setup the studio.

by the way, we are using XP pro, intel D865 PERL motherboard, 1g ram, fast hard drives and processor, so...

<font size=-1>[ This Message was edited by: rafafredd on 2006-04-07 19:18 ]</font>

<font size=-1>[ This Message was edited by: rafafredd on 2006-04-07 19:19 ]</font>

<font size=-1>[ This Message was edited by: rafafredd on 2006-04-07 19:20 ]</font>

can it be that you are using some other plugins at your studio than in your home? I mean, plugin delay compensation might confuse things (just a guess).

Most probably your "midi device" is set to "multimedia" instead to SCOPE. This is a common configuration issue when somebody starts with Pulsar. Check this out, it is very important.

This is what I mean:

http://www.planetz.com/forums/viewtopic ... &forum=3&4

Thanks for all the roplies!

I don´t really get anything like "asio driver not found"... Like I said in the first post, it all works almost perfectly. The audio playback works nice, with no latency. It´s only when I try to monitor the signal going throught Cubase, in real-time, that I get all this "ghost" latency. I mean ghost, because it sayd "7ms" or "4ms" in the Device multitrack asio panel, at Cubase, but still I get a "ghost" latency of aprox 200ms, and I can´t say where it comes from...

can it be that you are using some other plugins at your studio than in your home? I mean, plugin delay compensation might confuse things (just a guess).

What do you meas by delay compensation. I´m using other plugins in the studio. Not the same ones I use at home, but how can I verify if the problems lies in there?

maybe I should just try to unistall all plugins and see how it goes???

...

Don't uninstall them, just remove them from the tracks when you do the latency test. Obviously , any loaded plugin will affect latency.

monitor the cwa mixer. monitor cubase on the cwa mixer. don't monitor through cubase and this won't be an issue.

are you SURE that you are using the asioscope driver and not the asiomultimedia driver?

monitor the cwa mixer. monitor cubase on the cwa mixer. don't monitor through cubase and this won't be an issue.

Yes, that´s how I´m working. Only it makes working much more time dispending, believe me. And it´s not an ideal stup-up for tracking, definetly...

As I said, I´ve used Creamware at home for many years, and I´m sure everything is done right, I´m suery using ASIO SCOPE driver. No way to get it wrong.

Anyway, thanks for all the replies. I´ll keep searching for my problem. I´ll probably try unistalling all plugins, and if it doesn´t solve the problem, formating the HARD DRIVE again, and maybe try an English version of Win XP should do it. Only I take two days, to format it, install win, configure all the windows frills, installing all audio programs and plugins, etc... It sucks.

yyou dont need to uninstall i think, just see if the issue is the same with a simple audiofile in cubase. does the same latency appear then? do not apply any effects etc.

Have you done the asio simulation are the buffers the right size,so they can sync properly, and yes it might be windows seeing as the asio drivers sync to the wave driver.

<font size=-1>[ This Message was edited by: H-Rave on 2006-04-15 03:12 ]</font>

On 2006-04-10 19:08, rafafredd wrote:

monitor the cwa mixer. monitor cubase on the cwa mixer. don't monitor through cubase and this won't be an issue.

Yes, that´s how I´m working. Only it makes working much more time dispending, believe me. And it´s not an ideal stup-up for tracking, definetly...

i disagree. it's the easiest, best way to track and the most likley way to avoid latency. it is the way real hardware would work, hence it's the most logical. it also offers the most flexibility. you just need to stop fighting it and get used to it. or not...

<font size=-1>[ This Message was edited by: garyb on 2006-04-15 10:35 ]</font>

The issue have been solved somehow???

The problem is... I don´t know what I did, because I set this problem aside and I was messing with other configurations and now the problem is gone.

mmm... I´ll try to find out what it was that I did.

But thanks for all the help.

<font size=-1>[ This Message was edited by: rafafredd on 2006-04-23 19:53 ]</font>

I concur, I was having this "ghost" issue while monitoring the cubase signal sent to the cwa hardware while in Cubase. All I did was disable the monitoring when record enabling a track and monitored through cwa. Problem solved. You can still use the mute buttons and what not in cubase if you dont' want to hear a particular track so I'm happy. This has been one huge mind F*** in learning the software and hardware though. But I emphasize on LEARNING because it hasn't been a waste of time. Now if only I could get SFP plugins to work for post signal processing I'd be a happy camper. I don't understand how to get that one to work yet for myself.

<font size=-1>[ This Message was edited by: JoshT on 2006-05-02 19:30 ]</font>

simple.
on mixdown(last step), make the asio source module big enough to transfer your tracks individually. sum in the cwa mixer.