O.K... new glitches to deal with... :p

  • Thread starter Thread starter WATYF
  • Start date Start date
WATYF

WATYF

...happier than you.
Alright.. so after having a horrible time with the initial set-up of n-Track... I have finally found a configuration that works relatively stable. I discovered that certain variables (like which 24 bit setting I used) were causing stability problems.

So now that I can record without incessant crashes, I need to take care of one of the other problems I'm having...

I can't hear the metronome. This is what happens. I have to change the Windows settings so that all sound is played through the Delta 44. That way, when my generic midi plays the metronome, I can hear the sound through my headphones (which are plugged in to the Delta 44) So I hit record and the metronome starts, and I record a take.. and then I go back to do a second track and hit record, and there's no metronome.. I can hear the first track I previously recorded, but not the metronome. As soon as the first track finishes playing, then I can hear the metronome again, (which makes it worthless, because I don't need it when the song is over,.. I need it during the song) :p

So what's the deal...? It's as if the wavs and the metronome can't share the same "space" and that it's either one or the other... so how do I get around this? Any ideas?

WATYF
 
The metronome sucks. How's that for an answer :) haha

Slackmaster 2000
 
Yeah, I usually just make a scratch drum track with Fruity Loops and import it into n-Track, so I don't have to deal with the metro-gnome
 
Great... :p Oh well... I'll just run a metronome through my mixer... thanks for the help.

WATYF
 
Try this.....record the metronome as a wav BEFORE you lay down any other parts, then you can forget about the midi side of things while recording your audio parts. An added bonus of doing this is that you can easily line up parts by zooming in. You've then got a dependable, rock solid click track as a wav. When you come to mixdown just delete or mute the click track. Don't know why Slacky says the 'nome sucks.......I never had any probs with it. Good luck!
 
The metronome doesn't suck, it's just not that useful :)

Anyhow, the reason it doesn't work after you've recorded a track is that it can't possibly work that way. If you record a track using the metronome, and then start recording another track from a DIFFERENT offset, then the metronome will not be on time with the first track...because it simply starts clicking whenever you hit record/play...it's not embedded in the track. (Actually, I think the metronome should technically continue work...why it doesn't I don't know. Sometimes it takes a couple seconds for the metronome to start for me.)

Adding a "click track", as mentioned above, is a much better idea. A click track will always be on time, because it is the time...it's an actual track. Recording the metronome is a pretty cool idea. You can also create a click track in fruity loops or other drum type application.

Slackmaster 2000
 
Slack,
What if you always start recording at 0? Would the metronome work properly then? I guess I can try it tonight. I'm finally getting around to using a click track, and I figured the built-in metronome would be easiest.
Thanks!

If you record a track using the metronome, and then start recording another track from a DIFFERENT offset, then the metronome will not be on time with the first track...because it simply starts clicking whenever you hit record/play..
 
A click track is 100 times easier man, trust me here. But yeah, I suppose if you always started at 0, the metronome might be on time, but it really depends on what clock is driving the metronome. My guess is it's the system clock and a bunch of flavio code, which means that it may not match up with your soundcard's clock....but it might be close enough.

Starting at 0 all the time would be annoying. Do you have fruity loops or anything? It takes about a minute to generate a click track and export it.

Slackmaster 2000
 
Back
Top