Reseating. This is when you remove the Daisy pcb and put it back again. It can damage the device if you are not careful. Alternatively just press the the board to make sure it is firmly sandwiched together.

Sorry to hear about your issue. Later firmware doesn’t blink on reset. Besides this won’t fix the problem of a noisy channel. I have not come across this problem before with Poly Cinematic, It is almost definitely hardware related. The easiest fix is to swap the Daisy board but since the problem is only on one channel this might be a fried op amp on the main pcb - more expensive fix. Try reseating the Daisy board but if the problem persists or gets worse it will need to be returned.

You are doing all the right things to test the module and I’m sorry you are still having issues. I’ve unwrapped a recent module from the same batch as yours to try to replicate issues but have yet to reproduce any consistent fault. Nevertheless I will endeavour to get to the bottom of this until we see 100% reliability. If there’s anything you find that can consistently reproduce any issue then let me know and I’ll pass it on to the developer.

Hi there, I’ve not come across a poly c that self triggers chords like you’ve described. At 10 months old your best bet is to return it for a warranty repair. I suspect it will just need a new Daisy board. Let me know how you get on.

I really appreciate your patience on this. I’d like to take a look at the module, can you let me know which dealer you bought it from.

I’ve DM the address

Yes that looks like there is an issue with the filter switch connection. It will need to be repaired.

If there is no connection from the filter switch to the pcb you will only get notch. Does high pass work?

I’ve just uploaded 3.7.3 which should fix this.

The bend range can be changed in PC with midi cc channel 22. I’m guessing this needs to be set to one semitone for Linn, which is not the default value.

No MPE support for Poly Cinematic at the moment.

Although Poly Cinematic isn’t MPE compatible it should still work with Linnstrument or Exquis in midi keyboard mode. I have an Exquis on order so I will be able to test with that soon. Currently I’m not sure why you are getting the behaviour you describe but hopefully we can fix it in a future firmware release.

Get in touch at info@knobula.com

The firmware update procedure is quite different on Pianophonic compared to Poly Cinematic. Check that you have done this correctly as you may have just installed a new boatloader and not completed the second stage where you boot up Pianophonic as a usb drive. The v/oct issue is a limitation of Pianophonic itself where it can only transpose one octave up and one octave down, this includes the Pitch control so you may hit the limit early. The trick is to pick a root note over midi that is in the centre frequency of your tune, so a base line should start with a bass note. Finally, we have new firmware coming out later this week that resolves the SD card issue, so worth waiting for that if you can.

Yes we found the cause of this issue on Friday and I will be publishing a release later this week as soon as we’ve checked it. It should solve a number of sd card related problems as well as some ui improvements.

I will try to replicate this issue today. It’s good that you’ve found something repeatable. We are currently looking at this loading issue so I will pass this onto to our developer

Version 3.7 uploaded now. It should fix the issue but I don’t have a hermod here so let me know.

I’ll get onto a fix in the next couple of days.

Does this only happen when hermod and poly cinematic are booted together? This is an older bug that may have returned in the latest build.

Released today