PiBox » VideoFE

This is because of improper casting of static values in comparisons and variables in equations to unsigned long long. Currently those values are int's, and not even unsigned int's, which are far too small considering the status reports and computations need to be in microseconds.

This bug was uncovered during the first Drive-In Movie night where the feature, Vacation, stopped about 1/2 to 1/3 of the way through. Also, the improper computations cause omxplayer to exit which is why we get the "HDMI" notice from the projector each time the next video starts. If omxplayer doesn't actually exit, but rather starts the next video, then that won't happen.