Frodo wrote: I know this is not the way you'd like for it to work, but it seems that what you're asking DP to do is to change the tempo but to have the movie just playback without following the tempo changes designated by the tap entries. This is inherently a play of opposing functions.
EXACTLY!
And do you know what is even worse? That the ANSWER to all this is
ALMOST right there in the QT movie.
The little lock on top of the QT window... when
unengaged, the movie runs totally independently of DP... the problem is that this includes transport control. So when you stop the sequence, the movie keeps running.
I've made tests using it unlocked, but it quickly turns distracting and annoying. Every time you stop, you have to take your hands away from the keyboard, lock the button again, and the impossible: to press play in DP AND the QT movie at the
exact same time.
Obviously, one can't work like this, but the fact that there is a way to have the QT movie run independently from DP takes me ALMOST there, but not quite.
So the answer would be to have a similar option to let the movie run freely and independently, EXCEPT for transport control (play, stop, rewind, locate, etc).
Frodo wrote:... but even if you had two computers in sync, Tap Tempo would still render the same result: the rate of the movie's playback will change.
REALLY?!?!?!?!?!?!?!?!?!?!?!?!?!
How come?
I'm trying to wrap my Mexican brain around this....
Damn! System error. Kernel panic crash here....
I don't get it. If the computers are in sync via MTC (or LTC), why would one affect the other? Isn't the slave just synchronizing to the master every 24 (or whatever) MIDI clocks? And isn't the MIDI clock (or LTC) always running at the same rate no matter what?
So let me get this straight: Even if I managed to Sample Accurate Sync both computers to perfection, the slave computer would also slow down/speed up the other QT movie???
If so, then I'm glad you tell me about this BEFORE I go through the trouble of even trying to sync them! I was already checking out other options, even considering buying an extra MTP....
Please reconfirm this for me, Frodo. Did I get that right?
Frodo wrote:Maybe someone else has an easier approach, but at some point (and early in the process) the groundwork must be done for a workable tempo map before much else can be accomplished. I'm just not sure that Tap Tempo is the best tool in this particular case.
You may very well be right.
It's just that one of the many techniques I was taught at school to score a cue, and one that I
really liked, involved a simple stopwatch and paper. For rubato cues, they taught us to use the stop-watch and compose melodies/phrases, sort of "fitting them" into X amount of seconds (by singing them before even touching a keyboard). Those X amount of seconds would be a "control point" in the written score, or a non-critical hit, or something.
My best cues at College were written using this technique... and naturally, I now tried to apply that with the vastly superior possibilities DP gives us now. I just never thought this would be an issue with DP and the QT movie changing speeds with Tap Tempo!
Frodo wrote:I'll keep my eyes and ears on high alert for other possible solutions because I know the feeling of needing to work a certain way but not getting the results you need. It's quite a conundrum!
I'd really appreciate this, my friend!
It has never made sense to me why DP changes the QT movie speed rate. How is that useful? How can THAT be a feature? The first time I noticed this in DP I thought I was dreaming a bad dream!
So, if I understood correctly, even having 100 computers wouldn't fix this the way I thought at first (the playing rate of the QT movies).
Then it sounds like the problem is MY approach and not DP's... and it would look like I will have to settle for my usual workarounds to be able to keep working with my "workflow".
To tell you the truth, my best work around is not THAT bad after all. It involves a few extra steps, but our good friend B.G. gave me a VERY COOL tip to speed up my workaround.
Check it out:
http://www.motunation.com/forum/viewtop ... op#p301307" onclick="window.open(this.href);return false;
So basically, I record my taps in a regular MIDI track as a constant note. Then I fool DP into thinking that those notes are tempos I'd tap using Adjust Beats, and it automatically turns them into tempo data by creating a MIDI loop!
My only complaint is that I can only play the music material with one hand (one of them is stuck tapping the tempo).
I did try making a Console to convert CC64 into a MIDI note (so I could use the hands to play and the foot to tap), but no luck. It doesn't really work very good.
So it looks like I will either, have to convince MOTU to implement a thing similar to the QT lock (but better), or grow an extra arm in my body, or simply change my ways...
But thank you for your patience and good will, Frodo
I would've felt pretty dumb and stupid buying and extra MTP (or whatever) and sync both machines and be all excited only to find out the QT "problem" still persists. You just saved me not only money, but an embarrassment with myself! 