I see this occasionally with CHOP data coming from external devices or other processes that may be outputting data a little faster than touch is running (aka default of 60fps). I think what’s happening is that multiple “packets” of data are arriving during a single frame of “TouchDesigner time” from said device and TD just joins them all together and presents them as one frame of multisample CHOP data that the CHOPto TOP tries to make into multiple pixels (hence the warning saying there are 7 “scanlines” - such old school terminology…) while python is probably just grabbing the first (aka
 ) sample of data to show.
The thing is, despite bringing in multiple samples of data, TouchDesigner is still showing it as a single sample CHOP, but if you middle click on the CHOP I bet it says it’s actually 7 samples (7i) instead of just one. I don’t know why TD does this, and I’ve always wondered if the “Maximum Time Slice Size” preference in the CHOP section had anything to do with this (it doesn’t as far as I can tell)
I was kinda able to reproduce this with two TD processes running at different speeds with DMX Out and In CHOPs since DMX is what I use regularly and where I’ve seen it before:
As to why your Oculus is outputting multiple samples with such different data, I can not say, but the trick I’ve found to solve this with other external hardware is to put a Trim CHOP and a Shift CHOP in as the first two CHOPs right after the hardware input CHOP, setting the Trim CHOP to absolute 0 samples and the Shift CHOP to shift to the first frame so that single sample stops moving along the CHOP timeline along with the project timeline (which I still don’t understand)
Even better, while messing with this, I noticed they added a “Shift Start to 0” parameter to the Trim CHOP, so that gets rid of one more operator, and it seems to fix my simulated version of your problem:
Try that with your Oculus (all I have are Vives) and let us know what happens.