18 bit BPM12: there are always complications

Main INDEX

Monthly INDEX

NEXT
Make New Entry, Make Followup Entry

User name rsholmes

Log entry time 22:52:53 on September 08, 2009

Entry number 288689

This entry is a followup to: 288686

Followups:

288913 09/10/09 10:46 dalton Further monitor saturation complications

keyword=18 bit BPM12: there are always complications

One problem with this change is that the saturation levels for the different BPMs now are different, and the single saturation cut level we currently use is no longer appropriate. We could make tricky changes to pan to have it pull different cut levels out of the database for different BPMs. Or we could sleaze a hardwired exception for BPM12 in the code. "But that would be wrong." -- R. Nixon.

For now the saturation cut level has been set high, so it doesn't cut everything -- but we're left defenseless against saturation in the 16-bit BPMs until appropriate software changes are made.