If anybody tried it? I face couple problems: 1) linn slides doesnt work 2) pressing notes brings huge volume difference alomost distortion. How to fix?
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.
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.
i figured out that polycinematic opens filter when i push my finger up and down playin note on linn. it is quite sensitive thats why it is so loud (open filter). Is this possible to make it less sensitive?
is this still possible to use pitch bend (left-right slide)? this case i will fullfill my joy and actually needs to use this pair.
i had quite same trouble with other mono synths and i remember it was something deals with bend notes...
After digging in i recognized that knobula has +/- 4 semitones pitch bend range.
Setting 4 semitones in Linn it works.
Would be perfect if i could use all length of Linn (24 semitones) to slide left and right with no limits.
is this possible to do in future? or may be i can increase it now?
this is taken from Linn manual and i know how to do that:
To increase the range/distance of pitch slides, set the Bend Range in both LinnStrument and your synthesizer to a higher value.
But how can i do this in PC (taken from PC manual):
Adjusts the amount that the pitch changes up or down when using a pitch
bend controller.
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.
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.