There isn’t any way to disable velocity unfortunately.

Hi Richard, Thanks for getting in touch about your Pianophonic. There is a new firmware version available shortly that should improve reliability on loading. The distortion issue is more nuanced since the wavetables can be heavily processed by the unit, some controls particularly the Compress control will reveal artefacts in the wavetables that were resynthesised from acoustic instruments. The felt piano, on account of its soft tone, is the most difficult to conceal these artifacts. One other control that may help with output distortion is Shift Compress which controls the output level of the unit, reducing this may help. Let me know how you get on Kind regards Jason

To assign back to default press the Voice mode button instead of wiggling a knob. I’ll add it to the manual.

It’s a known bug we’ve fixed in the latest release. You’ll need to do a firmware update.

Poly Cinematic is always tuned to the last note you played/saved via midi. The v/oct input simply offsets from that note. So to guarantee a C3 with 0 volts you need to play a C3 into the midi in and Save settings (Shift and Trigger) Incidentally poly cinematic v/oct is unipolar so you can’t tune negatively but you can tune down an octave and tune upwards from there.

First try deleting the Settings.dat file on the SD card, you may need an SD card reader or adapter to do this. If the problem persists or it comes back then replace the SD card and download our pianophonic library from the website.

Yes this is a known issue and will be fixed in the next release

Boot and reset need to be pressed simultaneously. Some PCs are really flakey when it comes to usb and Daisy, but the Zadig fix should work. Alternatively if you know a Mac or Linux user it’s more straightforward. You will need to see the DFU is FS mode menu item for it to work.

The latest Kickain firmware is much more trigger sensitive. I think it’s around 5ms/3v.

I’ve added this in with cc only. It will be in the next release.

Hi Seb, I can confirm that none of the filters have been changed between firmwares but will try to explain what your friend might be experiencing: Filter cutoff knob range was extended to allow lower frequency cutoff , this might explain why it may not be audible at 12 o’clock since the cutoff also depends on the depth setting and more significantly the key follow switch. The BP is in fact a Notch filter and will be less audible when the Resonance is set. Not a firmware change. The HP hasn’t changed. Other than that there’s not much I can offer to help I’m afraid.

Fixed. Version 3.5 is now available in the download section of our website

Just checking here and can confirm it’s a bug. I will release a fix at the end of the day

We don’t normally make legacy firmware editions available as there should be no difference other than added features or better reliability. It’s very good of you to offer support for your friend and I’m sorry he’s not happy with your efforts. If you can find out more about what he’s missing over the earlier firmware we could look into this for you.

This issue has now been addressed and is available to download in the latest firmware release.

It probably needs a new Daisy board. This can be done under warranty.

Although 3ms sounds plausible, this is certainly something we will take a look at and improve on with the next release.

In 3.4 we reduced the minimum release time to near zero which naturally introduces a click at the minimum setting. For now the issue can be avoided by adding a very small amount of release. Let me know if this fixes it for you.

There is a plan to release more sounds. Waveslicer is available as online software that allows users (and us) to create new samples and wavetables. We thought we’d wait and see how the ecosystem develops around enthusiasts and try to enable that to grow. The second point about having drums is entirely doable right now however, with our wysiwyg design ethos, we won’t be adding multi timbral functionality, that is something we respectfully leave to Oxi Coral and screen based devices.

The pfon format is managed as a series of python scripts based around the librosa library. If you are interested in taking a closer look we can see if we can grant you access via GitHub.