When you rip a file with an object which uses a pattern fill, the pattern position may shift. The ripped result looks different than the original PDF file.
There is no solution in Odystar to rip the file with the pattern without shifting.
This is because a pattern cell has certain width and height. When outputting to a certain resolution, by default the sizes (and positions) are slightly changed to fit the exact number of output pixels.
If you don't do this, and create for e.g. a line pattern which is 1.3 pixels black followed by 1.3 pixels white, you will have some 1-pixel lines and some 2-pixel lines with guaranteed moiré as a consequence. Due to the stretching (called "output grid snapping"), the pattern in the output file looks shifted compared to the input file.
There is no option in the Odystar rip to prevent the output grid snapping.
In FlexRip, the default behavior also performs the output grid snapping. You can change this by adding an environment variable in the FlexRipConfigurator: "PATTERNGRIDSNAP=0". This will prevent the output grid snapping and will keep the pattern position in its original location. But it can show moiré as a consequence.
When using Odystar rip, the only workaround is to modify the original file by replacing the pattern fill with another fill type and then process the modified file through the Odystar workflow.
Another possibility is to change the pattern cell size to fit the output resolution. For instance, if you want to output at 2540 ppi (= 100 pixels per mm), the size needs to be a multiple of 0.01 mm.
Odystar users who encounter this problem frequently should consider moving to Automation Engine with FlexRip workflow.