Remember this... the victor CHOPS at 120Hz on its output (which is dang slow, hence the angry buzzing all first robots seem to make).
The victor can only take input at a rate of about 100Hz (98Hz if your cautious). I wrote myself a two channel pwm driver using CCP's to make a high update rate traction motor servo for our robot and found that there was a control output delay of just microseconds from control input to output when you use an output hardwired in the processor and use an oscilloscope triggering on the control input and measureing the shift on the output by having channel 2 on your scope hooked on to M+.
Mechanics do add some latency, but the thing you really have to watch is that most people are running their pwm's on the default ifi 26.2ms basis, not on a timebase of your own.
My suggestion is just to set up a freerun timer, use eccp1 as a timebase, then eccp2 and eccp3 as duty cycle triggers (set them in hardware to initialize pin high then clear + interrupt on compare match). not only do you get a nice high update rate, but you get 16x the resolution on your motor drives. VERY nice for pid's, made a world of difference with the resolution and the update rate increase.
any ?'s just hit me up. I can dig up my research notes on the victor period times n such if anybody wants it, i'll scan the pages in and hopefully somebody reads bad handwriting....
-q