Hi Robin,

Using the multitrack session is, of course, a great way to experiment and learn 
some techniques. It's also a bit of jumping in at the deep end, especially if 
you're thinking of trying to map the song in terms of bars and beats. Let me 
say that this is something that even I wouldn't undertake. Why? Well, because 
it's essentially unnecessary for the editing and mixing process. As you can 
imagine, roy Thomas Baker didn't have Pro Tools when he mixed this song. It was 
recorded on tape. To me, the idea of editing stuff without regard for bars and 
beats in this case is more important in and of itself. You'll need to get used 
to navigating with Tab and Option-Tab, Control-semicolon and Control-p, etc. 
Learn how Shuffle and Spot modes work differently. P.S. You'll definitely want 
to work in Slip mode in this case so your tracks won't shift around unless 
you'd like for everything to shift over to the beginning of the timeline. Also, 
you might want to create a duplicated playlist for all of the tracks before 
editing so that you can have a clean copy of the unedited tracks.

I spent the better part of a year learning Pro Tools by reading the Reference 
manual several times. I knew I needed to know it especially well because it's 
my spear. I'm not sure what your ultimate goal is and how well you really want 
to learn Pro tools but, if you're thinking of using it for serious work, I'd 
say you'll need to read the manual in addition to your experimentation. You'll 
be able to learn piece by piece by just asking on the list and sometimes you'll 
get good answers and sometimes not so good but, even when you do get good 
answers, it'll be primarily a solution to one issue and you'll be OK until the 
next issue creeps up and, guaranteed, it'll creep up again soon. So, by all 
means, post specific questions to the list but I'd really encourage you to read 
through at least the chapters on editing if you're trying to learn how to edit 
and then through the chapters on mixing if you're attempting to mix. 
Incidentally, as you can imagine, just the concept of mixing alone is big 
enough and now you're trying to undertake it on a new dAW with a different way 
of working, different plug-ins, different routing, etc. It's truly a gigantic 
undertaking so be patient. I hope it's worth the effort for you. I certainly 
think it is.

best,

Slau

On Aug 31, 2015, at 5:35 PM, Robin Kipp <[email protected]> wrote:

> Hello all!
> Well, yesterday I caught up with the list and also came across the discussion 
> of the ‚Bohemian Rhapsody‘ multi tracks! I definitely got quite excited when 
> I read that the tracks can be found online, and sure enough I was able to 
> successfully locate them after some Googling around… Now, I think that since 
> I’m quite new to PT and mixing in general, mixing those tracks probably would 
> be a good exercise. In addition, from listening to the tracks I found that 
> they appear to be unedited, so I’ll definitely get into editing those as well 
> before I do any sort of mixing… Now, when I dragged all those files into a 
> new PT session, I also added a click track. Of course, this gave me a default 
> track tempo of 120 BPM, so that the clicks are naturally way too fast. Also, 
> since there’s some noise on most tracks before the actual song begins, I 
> think that the grid that PT has created is probably not accurate as well… So, 
> what would be the best way for me to address this issue? Sure, I could 
> probably try to guess the BPM and experiment with entering it manually, but 
> I’ve noticed that PT also has an ‚identify beat‘ function. So, I already 
> tried soloing up one of the kick drum tracks, then selecting 4 bars and 
> afterwards pressing CMD + I to bring up the ‚Identify beat‘ window. Now that 
> window already had the start and end of my selection properly defined and so 
> the only obvious thing to do here was simply to hit the ‚OK‘ button. 
> Afterwards, however, that window simply disappeared, without giving me any 
> sort of result. I made sure to check the tempo in the Edit window, but this 
> was also still set to a way too fast value of 120BPM! So… Am I 
> misunderstanding something here, or am I just not using that ‚Identify beat‘ 
> functionality in the way that it’s meant to be used?
> Thanks a lot for any advice and clarification!
> Robin
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to