Bug: TIME_SHIFT event.value Not Within Sequence Window

[vincentczhou]

This issue is mainly for bookkeeping purposes, and is still present as of commit af0bb08.

When using a v1 "ors" dataset, with certain beatmaps (e.g fieryrage - fieryrage accordion), TIME_SHIFT events can potentially be placed outside their respective sequence window timing range, which raises an error during the data loading/processing stage (ors_dataset.py, osu_parser.py).

The root cause of this has not been identified, but the issue is not present with the v2 "mmrs" dataset. It is recommended to use the more recent versions instead (mmrs_dataset.py, osu_parser.py)