Skip to content

Latest commit

 

History

History
44 lines (26 loc) · 1.45 KB

troubleshooting.md

File metadata and controls

44 lines (26 loc) · 1.45 KB
Raw
Clatter

Troubleshooting Clatter

The document is a non-exhaustive list of common problems in Clatter and how to fix them.

Sounds are too "plinky"

This is a general problem with Clatter that we intend to correct by recording larger objects. In the meantime, you can adjust the size bucket values and fake masses of objects. You can also try increasing the resonance of the non-moving object.

Non-rigid impact materials don't sound as good

Synthesis of non-rigid materials is in our development plans, and will be supported in a future update to Clatter.

There are extra impact sounds

Usually, this is because roll sounds are being interpreted as impacts. Try setting roll_substitute in the Clatter constructor to "scrape" or "none".

You could also try increasing min_time_between_impacts in the Clatter constructor, or any of the other parameters that directly affect impacts.

There are missing impact sounds

Try adjusting any of these constructor parameters:

  • area_new_collision
  • scrape_angle
  • impact_area_ratio
  • roll_angular_speed
  • min_time_between_impacts
  • roll_substitute

Scrape sounds are too loud

You can fix this in several ways:

  • Choose a different scrape material.
  • Set scrape_amp in the Clatter constructor to a lower value.
  • Set scrape_speed in the Clatter constructor to a lower value.

Next: How to Contribute to Clatter

Return to the README