A new Daisy daughter board would likely fix it.

Can you describe the failure? Echo Cinematic is normally 100% reliable so we'd be very keen to see whats wrong.

I haven't tested the Monumatic with the Erae controller but I have tested it with the Exquis

Hi Ned, Sorry for the delay on getting back sooner. Ive just returned back from summer vacation and I dont always check the forum when Im away other than to remove reported spam posts. I'm really sorry about the knob situation, you just need to separate the caps and turn them theres a "how to video" here https://youtu.be/u1n72gtb8u0?si=VEI6IQKxahwBXWYH

This was fixed in the first update which may not have shipped on earlier batches.

1 ppq or less.

V 0.1.0 should fix the gate sensitivity

Hi Chris, it sounds like the midi CC transmitted from the keyboard is messing with settings on the monumatic. You can disable midi CC on the Monumatic with CC 106 A value above 64 disables CC control. Factory reset to restore control.

This bug has been fixed in the new firmware 0.1.0. There was a case where a fully loaded chord memory of 8 notes could crash the unit when triggered if even more notes were also being played on top.

Yes. You can store a chord in each of the 8 chord memories. The active chord memory is overwritten by any chord detected at the midi input.

I sell many more Pianophonics in the US than Europe so the number of people having issues will be greater in the states, but 50/60hz aside we are ourselves looking for any clues as why the issue persists for some and not for others. My suspicion is on the SD cards corrupting the settings.dat file as it’s the only thing that’s changed between batches but because the issue isn’t repeatable it’s been really difficult for us to track it down. I take it from your post that you are using the latest firmware and still getting freezes, occasionally or all the time? Is it only when you load a sound in? Let me know, the feedback really helps to diagnose it.

Firstly thank you for sharing this information about your thorough testing routine. In each case I would recommend deleting the settings.dat file rather than carrying the same settings across different firmwares. From the results your seeing it looks like something else is at play so it’s good to rule out the settings.dat which if corrupted from an earlier session will mess with your results. The settings.dat is a binary file that cannot be edited but it is created fresh if one is not present on the card, so deleting it is a nice way of rebooting the whole session.

Regarding distortion, the newer 'smooth' factory library is distortion free. The issue arises from the wavetable 'sampled' sounds having low frequency artifacts embedded in them. Depending on the settings, particularly high Morph Speed and Overdrive, crackling can be heard as Pianophonic jumps between waveforms that contain differing DC offsets. I hope that helps.

Calibration can be done over midi CC, I'll update the manual if it isnt already in there.

Are there any CV connections to the module? This sounds like the knob recorder has bad data in the persistent memory (power off memory). Try resetting to factory default by holding down Tap button while powering up.

the error message is normal, the pianophonic ejects itself after a succesful firmware update.

Oh no. Not good. That needs to come back for a closer look. I really appreciate the trouble you've gone to to test this out with the video and everything, it really helps. There is only one thing you might want to try before returning it, since you have done such a thorough job of testing it so far - try deleting the Settings.dat file on the SD card, once this gets corrupted it can cause disk load problems. If that doesnt help then contact your dealer and we'll get you another one.

Not all SD cards are equal and it might be worth trying a larger and branded card just to rule it out. Whilst Pianophonic doesnt need the 32Gb storage space of a larger card we have found them to be faster and more reliable. One of the changes in 1.1.2 was made to make it less vulnerable to slower SD card performance, but like you have experienced it is difficult to replicate on demand as a bug. Never-the-less, any information you share with us from out in the field is helpful.

Hi There, Sorry to hear youre having issues with the SD card loading. It sounds like you've tried all the right things only the symptoms you describe don't match the behaviour we've seen with 1.12. Can you describe a specific situation that reproduces this bug, what midi controller, what SD card. Did you definitely drag the firmare file onto the Pianophonic drive to update it (flashing the bootloader is a different process). Hopefully we can get to the bottom of this and find a solution quickly.

I'm happy to repair it here in London if you can send it. We've not had this fault before but its probably a simple fix.