DP 4.6 bugs worse in 4.61

[vaultcomplex]

The "incorrect pitch in Graphic Editor entry" bug is now MUCH worse in 4.61. While MOTU added a sort of "snap to pitch" feature while entering notes visually, the corresponding pitch you hear is almost always incorrect. One time as I was entering an E, I was hearing an Eb, and when I went to move it a 1/2 step up to F, the pitch jumped up a whole minor 3rd up to F#!!

Also, the lag in audio in quicktime movies still exists. It seems to me that perhaps MOTU should not focus on adding such features as "more files in the Recent Files" menu and instead concentrate on fixing work prohibiting bugs.

[sdfalk]

There's no lag at all regarding audio in a quicktime movie I'm working
with.
I've also had no problems with pitch correction (like your describing)
At least not yet.

[westla]

Just finished muisc for a trailer and I had no lag with the Quicktime movie.

[vaultcomplex]

Just finished muisc for a trailer and I had no lag with the Quicktime movie.

The lag is subtle, but annoying when you're trying to write around dialog.

I know three other people who have 4.61 and have these same exact issues. We all have different setups, so I know this is not problem with just my system.

Several people have posted on this forum about the MIDI entry problem.

Also, I posted about the movie audio lag issue a while back and several people responded claiming they had the same issue. So clearly it's something that exists and needs to be fixed (and should have been with 4.61).

[chrispick]

The lag is subtle, but annoying when you're trying to write around dialog.

Weird. I've never experienced this "lag" either. Granted, most of my work is for short-form broadcast video (e.g., promos, commercials, etc.), but I've never run across this problem.

I always import the QT's audio into a track, turn down the audio playing from the QT, then compose/sound design away. It always renders my stuff frame-on. I set up markers, lay in hit points, etc. All seems cool.

Now, I don't doubt the veracity of your claim. Just seems odd to me. I wonder what's up?

[vaultcomplex]

The lag is subtle, but annoying when you're trying to write around dialog.

Weird. I've never experienced this "lag" either. Granted, most of my work is for short-form broadcast video (e.g., promos, commercials, etc.), but I've never run across this problem.

I always import the QT's audio into a track, turn down the audio playing from the QT, then compose/sound design away. It always renders my stuff frame-on. I set up markers, lay in hit points, etc. All seems cool.

Now, I don't doubt the veracity of your claim. Just seems odd to me. I wonder what's up?

Importing the audio fixes the problem (the lag happens only when you play the audio on the movie itself). I'd have no problem doing that for something short, but I do multiple chunks (one for each cue) on a 45 min show each week, which means I'd have to reimport the 45 min of audio for each cue. Then of course there is the issue that whenever I try importing the audio on any chunk that does not start at 0:00:00:00, it NEVER lines it up. It just picks a random spot in the middle of the show to put at bar 1, instead of what's actually there.

[chrispick]

Importing the audio fixes the problem (the lag happens only when you play the audio on the movie itself). I'd have no problem doing that for something short, but I do multiple chunks (one for each cue) on a 45 min show each week, which means I'd have to reimport the 45 min of audio for each cue. Then of course there is the issue that whenever I try importing the audio on any chunk that does not start at 0:00:00:00, it NEVER lines it up. It just picks a random spot in the middle of the show to put at bar 1, instead of what's actually there.

I see. Interesting.

I suppose you've considered editing down your 45 min show into a QT for each cue using something like Final Cut? Then using that editorial-app-of-choice to piece your master stems (stereo or surround) back together, matching to timecode?

I'm just trying to throw out a workaround. It seems like some sort of modular approach might work, even it is kind of cumbersome.

An alternative would be to supply your editor with cue stems, labeled with timecode in-point. Let him or her lay them in.

I don't know. I'm riffing here.

[vaultcomplex]

I see. Interesting.

I suppose you've considered editing down your 45 min show into a QT for each cue using something like Final Cut? Then using that editorial-app-of-choice to piece your master stems (stereo or surround) back together, matching to timecode?

I'm just trying to throw out a workaround. It seems like some sort of modular approach might work, even it is kind of cumbersome.

An alternative would be to supply your editor with cue stems, labeled with timecode in-point. Let him or her lay them in.

I don't know. I'm riffing here.

Editing down the quicktime is not an option. It would take too much time away from writing, especially since it's sometimes 30 min of music that needs to be completed in two days. Plus, at the recording session, I'd have to load up a new quicktime every time we changed cues and set the "start time" for the movie each time. The point is, what I want to do should simply work, and MOTU should fix it. Also, the MIDI editing bug is a bigger problem than the audio lag.

[Tritonemusic]

..

[chrispick]

Editing down the quicktime is not an option. It would take too much time away from writing, especially since it's sometimes 30 min of music that needs to be completed in two days. Plus, at the recording session, I'd have to load up a new quicktime every time we changed cues and set the "start time" for the movie each time. The point is, what I want to do should simply work, and MOTU should fix it. Also, the MIDI editing bug is a bigger problem than the audio lag.

I hear you.

FWIW: Editing the QT would only take a few minutes tops. And loading QTs during recording should be pretty quick too.

I guess I always prep my QTs anyway to make them CPU efficient (e.g., resize, recompress, etc.), so it's no skin of my teeth to chop a clip up when I need to.

Not trying to talk you into anything. Just offering a "You gotta play the hand you're dealt" kind of option.

[westla]

I've never run into the QT lag problem. I've just done one project in 4.61, but in 4.6 I did three films (I think it was three) all where heavy dramas where they was a ton a dialogue to score around, and I didn't have any lag, weird.

As for the other problem, I don't use pitch correction.

[vaultcomplex]

As for the other problem, I don't use pitch correction.

It's not pitch correction I am referring to. It's editing the MIDI notes in the graphic editor (piano roll).

[westla]

Well that's really strange then, cause I didn't hire a bass player and played the part myself. So I did a lot of MIDI editing in the graphic editor, and didn't run into that problem. Very strange.

[vaultcomplex]

Well that's really strange then, cause I didn't hire a bass player and played the part myself. So I did a lot of MIDI editing in the graphic editor, and didn't run into that problem. Very strange.

I really don't know what causes it. The problem was also in 4.6 and my friends had the problem worse than I did. In fact I didn't have the problem at all at first and it slowly got worse and worse. If you like you can try some simple tests. Try putting a note on E and then try moving it to F and see if it gives you the correct pitch.

[westla]

Like I said I used that feature a bunch in the film I just finished and had no trouble.

So per your request, I just did a test of a new project I created and an older project, and moved MIDI notes around an all my sounds sources, no problems at all, behaves like it always did.

Called a few composers friends of mine who are DP uses, and the three of them haven't had any problems. And between the 4 of us we have three different Mac's, three us use use MOTU hardware, andn one used Pro Tools.


I wonder what's causing this for you?