The click level can be changed slightly in the current configuration in a couple of ways. 1. As you turn the Click knob the sound changes but so does the volume, each zone of each click sound has a range of levels if you listen carefully. 2. The Attack control reduces the click level significantly. If it doesnt then you might be using older firmware. The attack doesnt fade in the sound like on a synth but it emphasises the body of the sound and reduces the transient at the start. I hope that helps.

If there is a DC or sub octave component in the source sound this can create artefacts in the resulting wavetable. Or if the pitch has not been correctly estimated, which can often be the case on lower frequency sounds. If you havent already, you could try explicity typing the note values into the source file name and changing the pitch detection method to "From Filename". Also you could try setting the Preset template to "Synth" in Step 2. Let me know how you get on.

The settings file on the card might have become corrupted which would have been fixed on the new sd card. The settings.dat file can be deleted and a fresh one will be created by Pianophonic if it can't find one. The settings contains saved information like midi channel and user presets.

If you can predictably recreate the crash we can issue a bug report and get it fixed in the next update. Or are you saying it happens randomly even when sound s aren't being loaded?

Check that the Part Select Switch is set to All. Other settings such as Sides and Hammer will show the same flashing led but changes in sound may not necessarily be audible.

Hi Gary, if the red light is on at the back, but the blue light isnt on at the front then you just need to replace the Daisy and flash it with the latest firmware. Daisys can be ordered here https://foundsound.com.au/products/15956?_pos=1&_psq=daisy&_ss=e&_v=1.0

We're about to release an update for CP including a hybrid Midi thru mode and midi CC control of all the parameters, so let us know how you get on.

Thanks for asking about using Poly Cinematic for alternative firmware development. We consciously made the Poly Cinematic as a unique product and didn't want to tread on the toes of other manufacturers whose products were more open ended such as Versio, Patch and Patch_SM which are really well supported for that purpose. So in answer to your question , I'm afraid we can't support your request, but that doesn't mean you shouldn't give it a try!

The pitch from poly cinematic is dependent on the chord memory. So to get a C3 out you’d need to play a C in via midi and store that ( shift and Trigger) The C you played in midi can be played via CV of 0volts. You can Also use the pitch knob to offset the pitch, since poly cinematic doesn’t accept negative CV you must pitch down an octave with the knob and then 1volt becomes your C.

I've attached a new firmware version I'm working on, give it a go and let me know if the problem persists. I'm interested to know how it gets along with Digitakt and the RK-08.Thanks

If the red light at the back is on but the front led is off then it sounds like a dead chip on the Daisy mcu board. it’s easy to replace but you’ll need to contact your dealer.

There shouldn't be any issues with Octatrack any more but I've attached the 2.1.0 firmware in case you want to see if that solves it. Let me know how you get on.

The 8 chords are selectable over a 0-5v range so you will need to send a wide range of voltages to access all 8 chords. Also it is not advisable to change chord at the same time as sending a gate since the intended voltage will be sampled whilst it is still changing although poly cinematic does a pretty good job to mitigate this. Currently there is no way to clear to chord bank.

Schneidersladen and Midi Amsterdam both stock our products. Poly Cinematic was influenced by the simplicity of my Roland sh101 and the sound of my JP8000. Always a fan of Detroit techno but spent most of the 90’s involved in the London House music and break beat scene. Your English is perfect , much better than my French!

in the uk we buy them from Thonk. https://www.thonk.co.uk/shop/tall-trimmer-toppers/

Hi Steve, sorry I wasn’t suggesting you unpatched every time, but just temporarily to help find the source of the problem, then we can try and fix it in a future firmware release. Factory reset is a last resort.

Its sounds like the unit is receiving some sort of unrecognised midi message at startup and that could be crashing the midi buffer. Alternatively there could be a spike at one of the CV/gates that is sending it an unusually high signal, the Chord Select input can be quite sensitive to this. Are there any inputs patched in at power up when this happens?

Updated manual uploaded today. all shift functions now included.

Max you're right, the manual needs to be updated. I'll get that done this week.. In the meantime check out the changelog in the firmware download.

Yes this is implemented. The September batch of kickain has it, otherwise there is the firmware update on our website.