Factory Preset Bug (with fix)

chysn

  • *****
  • 1812
Re: Factory Preset Bug (with fix)
« Reply #20 on: January 19, 2024, 12:12:37 PM »
I was just curious if that possible data condition might not be handled through it.

Any editor that supports Q Comp would read the value as 2, with it being impossible to distinguish between an intentional 2 and an unintentional 2.

Q Comp is weird. Every other P-5 parameter has a numeric range starting at 0 and incrementing by 1. So you'd expect the Q Comp to have a range of 0-7. But no, it uses the high four bits, so 0x00, 0x10, 0x20, 0x30, 0x40, etc. It's an odd duck.
Prophet 5 Rev 4 #2711

MPC One+ ∙ MuseScore 4

www.wav2pro3.comwww.soundcloud.com/beige-mazewww.github.com/chysnwww.beigemaze.com

he/him/his

Re: Factory Preset Bug (with fix)
« Reply #21 on: January 19, 2024, 12:31:54 PM »
I was just curious if that possible data condition might not be handled through it.

Any editor that supports Q Comp would read the value as 2, with it being impossible to distinguish between an intentional 2 and an unintentional 2.

Q Comp is weird. Every other P-5 parameter has a numeric range starting at 0 and incrementing by 1. So you'd expect the Q Comp to have a range of 0-7. But no, it uses the high four bits, so 0x00, 0x10, 0x20, 0x30, 0x40, etc. It's an odd duck.

Appreciate the further explanation, I haven't looked into any dump to sort out the specifics :)

Re: Factory Preset Bug (with fix)
« Reply #22 on: February 21, 2024, 08:53:18 AM »
I was on the Sound! tower website a few days ago and noticed an update for the Prophet 5/10. I havenít had a chance to check whether the update reflects all of new features that were added to the Prophet in recent firmware updates.
Prophet 10 Rev4, OB-X8, Moog One, Rhodes Mk8, Osmose, OB-6 desktop, Trigon 6 Desktop, Kawai VPC-1, Steinway D