|
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#1
|
|||
|
|||
Beat Dectective -> tempo map trouble!
H'lo all,
I'm having a helluva time trying to get Beat Dectective (BD) to do what seems like what ought to be the simplest of jobs, but no joy. It feels like I'm missing something really simple here, so please weigh in if you have an idea where I'm screwing up. A client has sent me 2 files in a PT session; a 2 mix and a mono audio click track that the rhythm was cut to. It's about a 6 min. tune. The click rambles between aobut 125bpm and 130 bpm, with an occasional accel. up to about 155 for afew bars, then a ritard back to about 125. The click is in 4/4, all quarters. The click track is clean and I'm trying to get BD to anaylize it and create a tempo map for the session that I can quantize my midi parts to. I've trimmed the click track to it's first click, positioned it on Bar 1 Beat 1, selected the entire click track and opened BD. I've selected "Bar/Beat Marker Generation", "Start Bar/Beat 1/1, Time Sig. 4/4, Contains 1/4 notes", Analysis:High Emph., Then I hit "Analyze". I wind up with Beat markers (Triggers) on *most* of the clix - at least for the first 3-4 minutes of the track- but not all of them. I mess with the Sensitivity and (sometimes) get a few more of the clix to show Beat Markers, but never all of them. So, when I hit 'Generate', I get a tempo map that's valid for the first 80 bars or so, but then drifts significantly from the audio clix and is usless for the remainder of the tune. So that's where I am...can't get started on this project without an accurate tempo map and can't figure out what I'm missing in BD to get it to create one. Any/all help *HUGELY* appreciated! thanks, bill myers
__________________
PTools 10.3.5, DigitalPerf 8.04, Sibelius 6.2, Mac OS 10.8.4 MacPro 3,1 8core 2.8Ghz, 16 Gig RAM, 4 x 120Gig hds, multiple LCDs Presonus FireStudio Project, MTP AV |
#2
|
|||
|
|||
Re: Beat Dectective -> tempo map trouble!
the accellerandos and ritardos may be messing up the tempo map. It may help to map the click track in sections. if you have an approximate tempo to start with and it's reasonably stable for let's say 16 bars before the 1st accel, seperate a region after the 16 bars and BD on the first 16. seperate and select a region for the accel and BD it noting the start bar and length in the BD window. "Use selection" works well for reasonably stable tempos but for rubato performances, you have to split it up. lather, rinse, repeat. It's a little more work but you should be able to obtain very good results this way.
just another helpful hint. use tab to transient on the click track to place the selector when you make your region definitions. hope this helps.
__________________
G5 1.8X2/3gigRAM/Mbox/7.4 (retired) MBP C2D 2.4/4GigRAM/Mbox/8.0.1 iMac i7 3.4/16GigRAM/10.0.1 |
#3
|
|||
|
|||
Re: Beat Dectective -> tempo map trouble!
man, thanks for that idea, I'll try this afternoon!
thanks again, bill
__________________
PTools 10.3.5, DigitalPerf 8.04, Sibelius 6.2, Mac OS 10.8.4 MacPro 3,1 8core 2.8Ghz, 16 Gig RAM, 4 x 120Gig hds, multiple LCDs Presonus FireStudio Project, MTP AV |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Tempo mapping Beat Detective or identify beat? | grateful | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 1 | 08-14-2012 09:13 PM |
Beat Detective, Beat markers to Tempo Ruler?!? | phobia | Tips & Tricks | 3 | 01-01-2007 01:31 PM |
Is there some documentation for my Beat Dectective | skyking | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) | 3 | 08-19-2005 11:35 AM |
Beat Dectective Le | edytnbch | Tips & Tricks | 2 | 11-22-2004 05:21 PM |
Beat Detective/Tempo Changes | jeff...ya know...jeff | Tips & Tricks | 3 | 01-22-2003 06:31 PM |