An issue has been reported with patches sounding different starting with version 1.3.4 which was released a couple weeks ago. The bug stems from changes that were made to parameter numbering, which in turn threw off the Motion Sequence Target – essentially the Motion sequence is modifying the wrong parameter from what it was originally set to. The changes have been undone in the next update, so newer patches made in 1.3.3 should go back to sounding how they did before once 1.3.6 is released. Patches made in 1.3.4 and 1.3.5 may need to be fixed, if they used Motion sequences. The fix is detailed here. We will post when 1.3.6 is live in the app store – for now, hold tight. Our sincere apologies go to anyone affected by the bug.
1.3.6 will also feature a couple other bug fixes (sound coming thru the headset, and one other motion bug) and one new feature, which is the + / – buttons on the Motion page: