Clicktrack runs to fast!

[Allard123]

Hi!

Ive been using this fine program for quite some time but after the last update my clicktrack runs about 15 clicks to fast which is making recording impossible for me since i get tracks delivered recorded on a click but without the click sound which i put under it again and record my drums over it.

I never had any problems with this. I took an older clicktrack that was on time and in a new track i tried to create a new one of the same bpm but everytime i try it its about 15 clicks faster.

Any ideas?

[steve]

Windows or Linux?
http://audacityteam.org/forum/viewtopic.php?f=12&t=5499

[Gale Andrews]

Since the last update of what? Audacity, your operating system or your sound device? Are you perhaps recording from one sound device and playing back with another? This could give desyncing due to different clock speeds, aside from the consideration that one might need driver updates or be faulty.
If you respond please do so to the forum for the operating system you are actually on.

Gale

[Allard123]

I am very sorry for putting it in the windows forum aswell.

I am running Ubuntu 8.04. Ive been using audacity for quite some time without internet connection and at some point i had internet and updated my operating system. After that i noticed there were new features in audacity, the clicktrack program which allows me to choose midi notes n stuff and i saw a pluck feature.

Afterwards i wanted to continue on one of the programs but the click i had was without the peak note so it was just a 1/1 click so i wanted to make a new one and there i noticed that the click wqas running way faster but i did type the exact speed.

I tried making new projects and i compared it with my metronome and the audacity click is running 15.5 clicks to fast. I searched alot on the internet but i cant find anything concerning this problem.

reinstall maybe?

Thanks alot guys!

[Allard123]

by the way,

gale, im not recording anything. im just working on a project.

thx!

[Gale Andrews]

So

* the click track generates correctly according to looking at the timeline (both overall length and number/position of clicks) but then appears to play fast?
* and playing back other audio in Audacity plays at the correct speed (if it's a three minute song it actually lasts three minutes?


Gale

[Allard123]

Thx alot for the effort man.

Yeah its like you said. Everything plays normal in audacity with the correct speed and length.

So at the moment when i start a click of 185 it gives me a 200 click. its as easy and annoying as that.

At the moment i have to work on songs that are recorded at 180(guit only). So i import the wav file into audacity and checked with a metronome the speed and that was 180. Then i open the clicktrack plugin and i enter 180 and the correct measure length and then it gives me a click of 195... and at lower speeds its the same. I type 100 and it gives me 115...but the click isnt prefectly 15 to fast else i could work with it. its like 15.something.

Thx again gale!

[steve]

If you generate a click track,
starting at time=0
120 bpm
4 beats per bar
60 measures
offset = 0.0

If you check it against the time line, or the times in the selection toolbar, how long is the track?
It should be 1 sample short of 2 minutes 0.000 seconds.

[Gale Andrews]

It still "sounds" to me that what we are talking about is a Nyquist (the type of plug-in it is) length generation problem. If you try Steve's experiment using the parameters he gave, the track will be shorter than 2 minutes, I think?

If it's what I think it is, the crux of the problem is in the Audacity implementation of Nyquist and until it's rewritten the problem will continue to come and go intermittently. I've seen it do exactly that on Windows - change to a different version of Audacity and back again, and the problem may go away in the first version, even if the second had the same problem.

Three suggestions:

1) try Audacity Beta 1.3 - all Linux distributions should have a packaged 1.3 version of some sort.
2) Work out the percentage by which the length of the click track Steve's parameters produce is short of the 2 minutes it should be. Example: if it's 100 seconds long, that's 20/120 = 16.6667% short. Select all the click track, do Effect > Change speed and enter 16.6667 > OK. Now the BPM should be what you asked for.
3) Record a click track of the required BPM. Does not need to be long, you can extend the length with Effect > repeat. Record an online metronome from the web if you need to:
http://www.metronomeonline.com/

Note this isn't what you "seem" to be saying, which appears to be a fixed rather than proportional miscalculation. I've never seen a Nyquist generation error like that, however see if the above helps and let us know.


Gale