I have been working in MSPro 8 for only a few days, and I was sent a "click track" from the composer creating music for my video. This track consists of a steady "click" type sequence for me to put timing down in my editor.
I have noticed that when I place cues exactly on the wave form peak of the click, then if I scroll the source window left a few screens, then right a few screens, that the cues have usually "drifted" a bit left and then right by a non-trivial amount. Of course, this happens wherever I place the cues...I only noticed it when I was placing (or rather, trying to place) cues on the exact peaks of the waveform.
This makes it very hard to set my cues at the exact part of the wave that I want.
I have noticed that using the "jump to next/prev cue" tends to always line up the cue exactly where I placed it. But scrolling causes the cue to shift.
I should further note that when I place cues in this "shifted" environment, when I use the "next/prev cue" button and come back to those cues, they are all shifted...and I have to move them again. This means that not only is the display goofed up, but the underlying code is placing the audio cue in a slightly different position than what it is showing me on the screen when it gets into this mode (and it almost always gets into this mode as soon as I scroll the source window at all).
A very frustrating problem for anyone trying to synch with audio. I hope ULead will look at this ASAP.
Peter S. Lee
Audio cues "drifting" in the source window in MSPr
I have just tested this out and have not been able to reproduce it, no matter how hard I try.
I'm wondering whether you are not trying to beat the system. The cue resolution is one frame or 1/25 (PAL) or 1/29.97 (NTSC) seconds. If you are trying to work to shorter times than this, then it is not possible. In practice, it does not matter, because the eye-to-ear perception never sees a synch issue of up to about 50 msec or, in most cases, only 100 msec starts to become noticeable.
I'm wondering whether you are not trying to beat the system. The cue resolution is one frame or 1/25 (PAL) or 1/29.97 (NTSC) seconds. If you are trying to work to shorter times than this, then it is not possible. In practice, it does not matter, because the eye-to-ear perception never sees a synch issue of up to about 50 msec or, in most cases, only 100 msec starts to become noticeable.
[b][i][color=red]Devil[/color][/i][/b]
[size=84]P4 Core 2 Duo 2.6 GHz/Elite NVidia NF650iSLIT-A/2 Gb dual channel FSB 1333 MHz/Gainward NVidia 7300/2 x 80 Gb, 1 x 300 Gb, 1 x 200 Gb/DVCAM DRV-1000P drive/ Pan NV-DX1&-DX100/MSP8/WS2/PI11/C3D etc.[/size]
[size=84]P4 Core 2 Duo 2.6 GHz/Elite NVidia NF650iSLIT-A/2 Gb dual channel FSB 1333 MHz/Gainward NVidia 7300/2 x 80 Gb, 1 x 300 Gb, 1 x 200 Gb/DVCAM DRV-1000P drive/ Pan NV-DX1&-DX100/MSP8/WS2/PI11/C3D etc.[/size]
-
PSLee
Thanks for looking into it...but perhaps my description was lacking.
This has nothing to do with the eye-to-ear perception. I am talking about the ques "drifting" visually over the waveform by a small (but non-trivial) amount. It is enough so that when I place cues at the start of each wave on the click track, when I return to the main timeline, I should see cues evenly spaced at the tempo of the soundtrack. This ends up being off a bit in both directions (you can see this visually) unless I use the technique/workaround that I indicated.
If you are interested, I can take some screen shots of how the cues drift without me having to touch them. I could also send you the click track if you wish (or have you download it from my web site) if you want to play with it.
I do not recall this happening in my older version of the program (I just upgraded from 6.5 to 8.0). I did not see any updates to install over 8.0 so I presume I am running the latest and greatest software (by the way, some nice enhancements since 6.5!).
I do not know the research, but what you say about the perception of people to detect the drift sounds reasonable to me. I should say, however, that I noticed the difference when I was working with a full audio track. However, I am a percussionist and am excessively focused on timing and rhythm. I am not saying I can hear differences in the time range you are indicating...I am suggesting that the synch may be off by more than that.
Again, while this does show up in the audio/video synch, the problem was readily apparent visually in both the wave form/source window and when I went back to the main timeline.
Thanks.
Peter S. Lee
This has nothing to do with the eye-to-ear perception. I am talking about the ques "drifting" visually over the waveform by a small (but non-trivial) amount. It is enough so that when I place cues at the start of each wave on the click track, when I return to the main timeline, I should see cues evenly spaced at the tempo of the soundtrack. This ends up being off a bit in both directions (you can see this visually) unless I use the technique/workaround that I indicated.
If you are interested, I can take some screen shots of how the cues drift without me having to touch them. I could also send you the click track if you wish (or have you download it from my web site) if you want to play with it.
I do not recall this happening in my older version of the program (I just upgraded from 6.5 to 8.0). I did not see any updates to install over 8.0 so I presume I am running the latest and greatest software (by the way, some nice enhancements since 6.5!).
I do not know the research, but what you say about the perception of people to detect the drift sounds reasonable to me. I should say, however, that I noticed the difference when I was working with a full audio track. However, I am a percussionist and am excessively focused on timing and rhythm. I am not saying I can hear differences in the time range you are indicating...I am suggesting that the synch may be off by more than that.
Again, while this does show up in the audio/video synch, the problem was readily apparent visually in both the wave form/source window and when I went back to the main timeline.
Thanks.
Peter S. Lee
I had a similar issue come up a few months back. It was suggested to me that instead of using .mp3 audio, I should be using .wav because the compression involved with an .mp3 is the cause of the problem. Not sure if that applies to you though. I still use .mp3 audio from time to time and have not had the sync issue/shifting anymore. Go figure. Good Luck!