Factory Preset Bug (with fix)

[chysn]

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.

[electronicsupersonic]

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

[strytten]

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.