Cubase LE. I have been recording on this computer in this project just fine, and then yesterday, whenever I would record something, it would play the clip slightly too soon. Notice I say too "soon" and not too "fast." It's the correct speed and if I nudge it forward a hair, it right in sync, but it's annoying as hell. I haven't been able to google anyone with this issue.
Topic Tags
Comments
Alright, but why is it doing this now when it wasn't before? I d
Alright, but why is it doing this now when it wasn't before? I don't know what has changed. I'm on a super fast computer (quad core) with good hard drives (SATA II). It seemingly randomly started doing it.
I took a look in the cubase manual and don't see any kind of latency compensation ability or record placement offset option. :(
Sorry it's taken me a little while to get back to this thread. I
Sorry it's taken me a little while to get back to this thread. It doesn't seem to be doing it on every track. I think it's just that one track, even though I have delay set up on multiple tracks. I turned the delay off and that didn't change anything. I found something really weird when I looked at the audio up close.
http://i37.tinypic.com/jj66u9.jpg
These audio tracks look like the audio isn't in sync, right? Well, it is. For some weird reason, it's playing what looks like the later audio in sync with the earlier audio. So I think when I record something, it puts it visually in line with where it should be, but because cubase is reading that track at a slightly different time, the track has to be bumped .030th of a second back to make it APPEAR out of sync while the audio is in sync.
My brain is melting.
hackenslash, there's no automation in the tempo track.
majormusic wrote: Check your latency settings, and then buffer s
majormusic wrote: Check your latency settings, and then buffer settings. And then make sure you have over a Pentium 4. If not, that's the reason too.
This has little or nothing to do with latency or bufferes. The jpg looks to be a snapshot of an older version of Cubase. Likely SE, SL, SX or an older version of LE. All of which can function perfectly well on a 1GHz or better machine. That means P3 or better. In fact I'm pretty sure you could run it on a 700MHz machine with enough RAM, provided you don't have any other programs on the machine.
Anyway. I know this is totally unrelated but you may want to check into it. Look in the steinberg folder under start menu/steinberg/cubase/ and look for a folder marked "ignore emulated midi ports". There is a file in that folder. Put that file in with the general population of other files. In other words take the file out of the folder and put it in that folders "mother" folder. If this is the problem, you will notice it even more with midi files. If it doesn't work, no harm done.
^^ It isn't that, I'm sure. Port emulation isn't connected with
^^ It isn't that, I'm sure. Port emulation isn't connected with audio in any way. Further, simply moving that file doesn't accomplish anything except making the emulated versions of MIDI ports visible within Cubase.
What specific version and revision of Cubase are you using? Have you activated 'musical mode' on any of the audio files? You can check that in the pool window.
Post a screenshot of your pool window.
The other thing it could be is that you have executed some range functions while one of the tracks was muted.
hackenslash wrote: ^^ It isn't that, I'm sure. Port emulation is
hackenslash wrote: ^^ It isn't that, I'm sure. Port emulation isn't connected with audio in any way. Further, simply moving that file doesn't accomplish anything except making the emulated versions of MIDI ports visible within Cubase.
Meh. It was a stab in the dark. It fixed a midi issue i had that was similar to this audio issue. I don't know why and I don't care. It worked for me.
Incidentally, I read back and apparently he's using Cubase LE. Probably pre Cubase 4.
Yes, I got the LE, but he doesn't say which specific revision. T
Yes, I got the LE, but he doesn't say which specific revision. There are quite a lot of differences in functionality between even the minor revisions.
Your issue was obviously the famous 'two clocks' problem, that had to do with drift between two clocking sources. It's fairly common, but only when using Cubase in conjunction with specific MIDI devices, such as the Midisport series of MIDI interfaces. The Windows MIDI ports would drift, hence the need for using emulated ports and the later addition of the 'use system timestamp' option.
Just in case you ever experience such issues again, of course.
hackenslash wrote: ^^ It isn't that, I'm sure. Port emulation is
hackenslash wrote: ^^ It isn't that, I'm sure. Port emulation isn't connected with audio in any way. Further, simply moving that file doesn't accomplish anything except making the emulated versions of MIDI ports visible within Cubase.
What specific version and revision of Cubase are you using? Have you activated 'musical mode' on any of the audio files? You can check that in the pool window.
Post a screenshot of your pool window.
The other thing it could be is that you have executed some range functions while one of the tracks was muted.
Musical mode? I can't even find that in the manual. I don't think that's something you can do in my version, unless it's general known by another name. Here's a cap of my pool. Below, are my specs.
http://i38.tinypic.com/2002tg1.jpg
Groff wrote: Looking just at the photo it's recording placement offset. According to your words seems it is not.It could be graphic card, ASIO driver or OS.
What is your audio card (AD/DA)?
What is your OS?Check the ASIO driver clock source in CB, it should be on - internal
Yeah, it's set to internal. I'll just give the whole shebang:
DFI Blood Iron mother board. Pentium Quad Core, 4 gigs of Corsair DDR2, XP Pro (32 bit), Presonus Firebox, Cubase LE version 1.0.7 Build 94. Yes, I know. I have one hell of a PC for a such a little sequencer. :)
I'll upgrade to C4 when I have some spare cash.
A few basic things: Disconnect/disable any other audio card/dev
A few basic things:
Disconnect/disable any other audio card/device (ie on board).
XP control panel/Sound & audio devices - select the FireBox (ASIO) as main device.
The FireBox ASIO driver should be also selected in CB.
Try to change audio priority settings in CB.
Have you installed SP2? Have you read about FW chipset/XP problems and compatibility?
I doubt this will fix your problem but it's good to know how to tune XP for audio:
http://www.musicxp.net/dnn/
hueseph wrote: [quote=majormusic]Check your latency settings, an
hueseph wrote: [quote=majormusic]Check your latency settings, and then buffer settings. And then make sure you have over a Pentium 4. If not, that's the reason too.This has little or nothing to do with latency or bufferes. The jpg looks to be a snapshot of an older version of Cubase. Likely SE, SL, SX or an older version of LE. All of which can function perfectly well on a 1GHz or better machine. That means P3 or better. In fact I'm pretty sure you could run it on a 700MHz machine with enough RAM, provided you don't have any other programs on the machine.
Yes it does dufus. I have Cubase. You don't know anything about music, so stop quoting me like you know things. You do not know anything.
[quote=majormusic]Yes it does dufus. I have Cubase. You don't kn
[quote=majormusic]
Yes it does dufus. I have Cubase. You don't know anything about music, so stop quoting me like you know things. You do not know anything.
Right. There's been a few people here who have uh "chased" you far more than I. For the most part I have given you the benefit of the doubt. If I touched a nerve it isn't because of anything wrong I've said.
Of course I know nothing about music. Maybe I should flip my mic downward and point it up 1" toward me? I should probably also ditch everything and buy a $99 preamp that sounds as good as a Neve. And there's that medium (1/2" ) diaphragm AT2020 that sounds awesome for it's price.
I sense an e-fight about to break out. Am I going to have to rem
I sense an e-fight about to break out. Am I going to have to remove all of the breakable items from the area? :wink:
Groff wrote: A few basic things:Disconnect/disable any other audio card/device (ie on board).
XP control panel/Sound & audio devices - select the FireBox (ASIO) as main device.
The FireBox ASIO driver should be also selected in CB.
Try to change audio priority settings in CB.
Have you installed SP2? Have you read about FW chipset/XP problems and compatibility?
I doubt this will fix your problem but it's good to know how to tune XP for audio:
http://www.musicxp.net/dnn/
:wink: :wink:
Alright, I've gone through all of that and checked everything. The only I'm unsure of is audio priority settings in CB. Is there something I might need to adjust in the device setup?
Thanks for all of the help, guys. If I don't get this figured out soon, maybe it will just fix it self when I make the jump to Cubase 4 in the next month or so.
Just to get it straight. Latency is the delay between the signal
Just to get it straight. Latency is the delay between the signal going in and the signal coming out. The OP was talking about his audio getting shifted AHEAD of what he recorded. Latency doesn't work backwards. In otherwords the saw can't anticipate what you are going to play and record it before you play it.
I could have pointed that out to begin with but I thought that would be mean.
Your screen shot: http://i37.tinypic.com/jj66u9.jpg There seem
Your screen shot: http://i37.tinypic.com/jj66u9.jpg
There seems to be confusion as to what the issue is.
If you bounce that down to a WAV file and zoom in on the same section in your image are the two tracks aligned?
1. If they align: then your problem is with a delay on the track probably caused by a VST plug in that is not compensating for some reason.
2. If they are not aligned: (the delay is being caused when you record to the track) It is possibly over compensation for recording latency, (as Hueseph mentioned, negative latency is impossible)
You could also test it by putting a snare sample on one track, and a kick on the other. Make sure they are time aligned visually and bounce it. Then check the bounced track (or listen) to see what occurs first. If they do come up different after bouncing, then try removing all your plug ins and bus sends from both tracks to see if that is causing the issue.
It's called latency delay compensation. In Cubase LE the option
It's called latency delay compensation. In Cubase LE the option to adjust for it is in the audio preferences... or was it Devices -> Device setup? ... or VST connections... Someone else will know. To measure it route one of the tracks you have recorded out your head phones and into a line in and record a 2nd track. Then zoom in and measure the delay.