Thanks Jim.
First a correction of one of my points above. VideoClock does indeed adjust both the video and audio components of a movie, in order to play video smoothly. The video clock is adjusted to match the frame rate of the display, and the audio is then adjusted to match the video output. There is a VideoClock Wiki article that is worth reading over a few times, particularly the
Target Ratio including PAL Speeddown section.
It confirms what I thought. If done correctly, the Pitch is
adjusted down when PAL content that was originally shot at 23.97 fps and is recorded on disc or media at 25 fps, in order to correct the Pitch. So if you play back that 25 fps media at 24 (23.97) fps, then the Pitch needs to be
adjusted up to correct it back to the original sound. So I guess the title of the thread is a little confusing.
I think the issue is that VideoClock adjusts Tempo, not Rate.
I was having trouble differentiating between the definitions of Tempo (synonyms: cadence, speed, rhythm, beat, time, pulse; measure, metre) and Rate, with respect to Pitch (synonyms: tone, timbre, sound, key, tonality, modulation, frequency), until I looked at the "Tempo & Pitch" settings in the DSP Studio, which simply defines a Rate change as a combination of a Tempo and Pitch change, "like speeding up or slowing down a record". I was overthinking it.
Actually I was thinking maybe you could create a Convolution filter to change the Pitch for these videos, but then when I looked at the "Tempo & Pitch" controls in the DSP Studio, I see what you want is already there! Then it would be easy to create a Zone for when you want to adjust the Pitch, and a ZoneSwitch rule to switch to it.
Unfortunately the DSP Studio Pitch adjustment doesn't work when VideoClock is turned on. Maybe it could work with VideoClock switched on, but that would require a change by JRiver. A Convolution filter may suffer the same effect, with VideoClock undoing what the filter did.
Anyway, back to the start point I guess.
PS: I did play with the Pitch with VideoClock turned off, and a 4% adjustment was very minor. Perhaps noticeable with high resolution audio, but with the sample video I was using, not really noticeable at all.