Anyone experienced this problem??

[Wesma]

Hi! Recently I have been having a problem during tracking and I wanted to check with you guys if anyone have been through the same thing. Maybe someone could tell me what causes it..

So I'm right in the middle of tracking and suddenly the audio (everything that is monitored) "glitches" for a short moment. Like if you listend to a vinyl record and it speeds up for a moment. Tempo gets higher and so does the pitch of things. This get printed on the track being recorded.

What could be causing this strange problem? Is it a buffering issue? Interface problem?

I have a RME fireface 400. Running Cubase 5 on a PC with quad core, 4gb ram. Recording at 48kHz/24bit with buffersize set to 96.

Grateful for any help!

[oldeanalogueguy]

Originally Posted by Wesma

Hi! Recently I have been having a problem during tracking and I wanted to check with you guys if anyone have been through the same thing. Maybe someone could tell me what causes it..

So I'm right in the middle of tracking and suddenly the audio (everything that is monitored) "glitches" for a short moment. Like if you listend to a vinyl record and it speeds up for a moment. Tempo gets higher and so does the pitch of things. This get printed on the track being recorded.

What could be causing this strange problem? Is it a buffering issue? Interface problem?

I have a RME fireface 400. Running Cubase 5 on a PC with quad core, 4gb ram. Recording at 48kHz/24bit with buffersize set to 96.

Grateful for any help!

thta makes no sense

you can glitches pops and slow down
cuase the otehr pc software is interfering

have you tuned the pc for audio use
killed the antivirus
gotten off the internet
stopped all the useless autostart programs
killed auto indexing

[RightOnRome]

WOW WTF i cant say i have ever herd of such a thing ... is there any other programs running.. i have herd of sample rate problems between the platform and error sounds created by the box ..check pref. and try to disable .. shot in the dark

[drumdrum]

Sounds to me like you may have accidentally increased the tempo of the track at this section.

Are you 100% positive that the tempo automation track is flat? Pitch increase happens as things speed.
The did it with When Im 64 by the beatles to make paul mc cartney sound younger....though I'm guesting this isn't intentional

[Wesma]

It's certainly not intentional

The first time I experienced this was when I had moved my rig to a different location for recording. So I immediately thought there was something there causing it.. no idea what though - unsteady power from sockets . It happend several times there and never on the same part of the song. (so we can rule out any time automation setting error)

But then it happend again back at the studio when tracking drums.

I'm afraid it has to be some kind of hardware issue? Anyone's an elecrical engineer? I'm not so good at the technical stuff

Thanks

[Frankie Rich]

I've seen this occur once, with a Fireface 400 on a macbook pro running 10.6.3 or so, while recording in Ableton. Back then I worked as a audio support/tech guy at a Mac Creative Solution Expert store. A customer had the problem. If I recall correctly, it was a driver/clock problem, not hardware. I reinstalled all the driver software, repaired permissions etc. and the problem never reoccurred.

I'm not that good with PC's, but did you try reinstalling the drivers? If software doesn't fix it I would think it's a clock problem. Try syncing it to another clock (wordclock, ADAT, whatever) and see if the problem persists. Also check all sample rate settings in everything you have running at the time (cuebase, fireface mixer and control panel, itunes, whatever).

These things should get you closer to an answer. If not, contact RME support, they're usually nice.

Frank

[Wesma]

Originally Posted by Frankie Rich

I've seen this occur once, with a Fireface 400 on a macbook pro running 10.6.3 or so, while recording in Ableton. Back then I worked as a audio support/tech guy at a Mac Creative Solution Expert store. A customer had the problem. If I recall correctly, it was a driver/clock problem, not hardware. I reinstalled all the driver software, repaired permissions etc. and the problem never reoccurred.

I'm not that good with PC's, but did you try reinstalling the drivers? If software doesn't fix it I would think it's a clock problem. Try syncing it to another clock (wordclock, ADAT, whatever) and see if the problem persists. Also check all sample rate settings in everything you have running at the time (cuebase, fireface mixer and control panel, itunes, whatever).

These things should get you closer to an answer. If not, contact RME support, they're usually nice.

Frank

Ok thanks a lot! Have not done anything yet but I'll try and reinstall the drivers and see if it helps. Will look into clock and sample settings also. I'm not at my rig right now but will try it this weekend.

[Houston11]

Originally Posted by Wesma

I have a RME fireface 400. Running Cubase 5 on a PC with quad core, 4gb ram. Recording at 48kHz/24bit with buffersize set to 96.

It surely has nothing to do with your problem but:
Why do you use 48kHz as samplerate? And than you have to convert it to 44,1kHz?
What do you think is the benefit? 48kHz is used if you working for film.
If you want to use a higher samplerate, then use 88,2 kHz its far better to convert to 44,1 becuase it is exactly the half.

I just want to understand why people do this ... maybe iam wrong...

[Wesma]

Originally Posted by Houston11

It surely has nothing to do with your problem but:
Why do you use 48kHz as samplerate? And than you have to convert it to 44,1kHz?
What do you think is the benefit? 48kHz is used if you working for film.
If you want to use a higher samplerate, then use 88,2 kHz its far better to convert to 44,1 becuase it is exactly the half.

I just want to understand why people do this ... maybe iam wrong...

Hi! Actually I don't have a great reason for doing this. Just been trying it out. I used to record at 44,1 but I kept hearing from others to record at 48 to be on the safe side. I honestly don't think I could hear that big a difference. Have not been having any problem with downsampling either. Seems like, after searching the web, no one really have a great answer to what's "right" to do...

I don't blame you for question it though. I do it to Might go back to 44,1. It's simpler...

[unit13]

Sometimes my copy of Cubase 5 freezes but it doesn't affect the audio, just seems to stop for a second or so then everything starts moving again.

[oldeanalogueguy]

Originally Posted by Wesma

Hi! Actually I don't have a great reason for doing this. Just been trying it out. I used to record at 44,1 but I kept hearing from others to record at 48 to be on the safe side. I honestly don't think I could hear that big a difference. Have not been having any problem with downsampling either. Seems like, after searching the web, no one really have a great answer to what's "right" to do...

I don't blame you for question it though. I do it to Might go back to 44,1. It's simpler...

simpler and better
44.1 will be better than 48 downconverted to 44.1

use 88.2 , ,96 maybe , 192 or higher

[oldeanalogueguy]

Originally Posted by unit13

Sometimes my copy of Cubase 5 freezes but it doesn't affect the audio, just seems to stop for a second or so then everything starts moving again.

that sounds like windoze doing its thing

you need to tune a pc for audio use to stop those problems

[bogosort]

Originally Posted by Houston11

If you want to use a higher samplerate, then use 88,2 kHz its far better to convert to 44,1 becuase it is exactly the half.

Just to be clear, this is wrong. While there may or may not be benefit to using 88.2 kHz over 44.1, it has nothing to do with the math being "easier" to down-sample.