We have a problem with this opcode because ARIA and Cakewalk interpret the value differently.
Candiate solutions are as follows, with respective advantages and inconvenients.

1. Use Cakewalk range 0-360

• (+) it complies to the SFZ standard as established by RGC
• (+) it uses a consistent unit with the larger set of opcodes (eg. apan_phase)
• (-) few existing instruments have it

2. Use ARIA range 0-1

• (+) compatible to many existing instruments, which includes Garritan's
• (-) inconsistent with other opcodes like apan_phase which use degrees

3. Hybrid: use ARIA if value within ±1, otherwise Cakewalk

• (+) compatible with both, for most cases
• (-) doesn't work with some cases of modulations
  (eg. I want the phase CC to perform 2 wraps using ARIA semantics lfo_phase_onCC1=2.0)

4. Compatibility modes

• (+) user can manually select a compatibility mode, behavior will be applied accordingly
  this indication may also be provided as a hint_* opcode
• (+) there might be a possibility to auto-detect whether an input is compliant to ARIA or Cakewalk
• (-) detecting might not work all the time