Hey, everybody! I have a weird one here...I had started a project at 16 bit a long time ago on an old G3. Now that I have a G5 I like to work at 24 bit, so I started work on the project again.... converted the project and all the bites to 24 bit. I flew in some 24 bit drum tracks and everything seemed to line up fine. Now, after laying down a lot more tracks and replacing some of the originals I'm noticing that the "feel" is going down the tubes. I turned on the click and discovered that it is getting way off as the tune progresses. Starts off ok and then about a minute in...bye bye sync. And then it continues to stay out for the rest of the track, although not by THAT much. It kinda flirts around the beat and every once in a while the downbeat hits dead on and then drifts again. I've checked all the obvious stuff. I'm synced to the tempo slider. It's the same tempo as the original 16 bit file. HELP!
Has any one else had a similar problem? I'm trying to avoid manually setting the tempo via the conductor track, because I know I'm gonna end up re cutting a months worth of work....
Tempo/click out of Whack!
Moderator: James Steele
Forum rules
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
I'm actually having the same problem. My click is not even close to right!
I first thought this was due to Metric Halo ChannelStrip on my EzDrummer tracks, but after bouncing the the tracks and then using shift to compensate for the latency I thought was there (+/- 16ms) neither orig pos. or +/-16ms made any difference. Which is kinda wierd since the MIDI track is synced to the project BPM, so it should all be ok. but alas, noes :/
I first thought this was due to Metric Halo ChannelStrip on my EzDrummer tracks, but after bouncing the the tracks and then using shift to compensate for the latency I thought was there (+/- 16ms) neither orig pos. or +/-16ms made any difference. Which is kinda wierd since the MIDI track is synced to the project BPM, so it should all be ok. but alas, noes :/
Interesting...
I poked around the forum and found someone had a similar problem solved by going to Setup and making sure the Time Formats is set to measures, not real time. Maybe this would help you... Unfortunately for me no luck! I'm in the habit of "Saving As" while I work on a tune, so I have a version of my project from a week ago, AFTER I had converted the sample rate and the click is fine, sooo I must have hit some button or changed a parameter somewhere inadvertently that did it! Still looking....