Kudos and thanks for implementing the KR-106 in both Oram and Vangelis versions, as some of us are held up moving, either by the test nature, or by real obstacles, such as having machines that need the Akai APC25 ctrl driver to run.
1 Like
I made a PR for the akai apc key25 drivers, I think our beloved devs haven’t had the time yet to review this (many many changes were needed)
3 Likes
Thank you, that’s good to hear. Let me know if you’d like me to try it before it becomes part of Vangelis.
I don’t see an update (Oram stable 2601.1)
Oram staging.
Thanks @ronsum, with this workaround I can get it to work. I also got the ERROR screen.
I learned about the find <path> -mmin -60command to look at files changed in the last hour.
Unfortunately this didn’t help me to locate where the workaround was saved. The preset file itself remains unmodified.
You are definitely welcome to. It’d be good to obtain feedback from actual users!
The PR is here.
Hi Niels!
I’ve closed the PR. Please, read the comments on it and send 2 separated PRs. One with the driver upgrade and another one with the fixes to the core API.
Regards,
Hi @jofemodo,
As stated in the PR, I can try and remove the changes to core files that I felt were needed for functionality that used to exist to still exist.
If I feel I the driver cannot do without some changes to core, what is the best way to discuss them?
Let’s discuss the changes in the github PR. But first, send a new PR with the minimum changes to upgrade the driver to vangelis. And send a separated PR with your fixes or proposed changes to the API.
The more atomic the changes, the more easy to test and manage.
Thanks!
Thanks, working on it.
Just wanted to say that i love the analog vibe the KR-106 can give. I’m experimenting with several instances of the plugin in tracks and the results are great to my ears.
I swear i was about to ask for synched ARP and LFO but you preceded me with the last 2.4.4 version 
2 Likes
Awesome! Someone asked about that last week and I just implemented it. Do you think I have a good range of sync options or should there be more like dotted quarter notes?
3 Likes
It was me 
4 Likes
More is better, of course expecially dotted notes. It would be nice to have also some different arp mode like As played, Random and maybe Repeated up & down and down & up.
On the Zynthian side, it would be great to have the options parameters in the interface. Now they’re only available in webconf in VNC-Engines. One more thing… i noticed that the arpeggiator is not synched to BPM 
1 Like
Oh yes!!! the new filter (and perhaps other changes) made absolute wonders with this nice plugin. Its eons better sounding now 
Its a very nice plugin with a great UI on top.
2 Likes
I have KR-106 working on my Oram staging, I can even build the updated source, but for some reason the custom dsp.ttl is not showing the synth parameters in the chain, just the presets. I already tried to delete the patchlevel.txt file and run all available update recipes, but didn’t fix it. Is there something I should attempt before doing a new SD image? Thanks a lot
If you manually installed then it is possible there are 2 instances and zynthian’s LV2 plugin host (jalv) will chose one which might not be the one that we support though the standard update. Do you remember the commands you may have run when you built it, particularly where you might have copied the lv2 files to?
1 Like
I used the recipe script on zynthian-sys (btw, i fixed it and submitted PR), so all should be in the correct folders. But I will investigate that possibility, thank you.
I really want to understand this, it may be handy in the future to tweak other plugin parameters ttl. It’s the kind of contribution I can embrace.
I don’t exactly understand what you mean by this. Typically with every update zynthian copies custom ttls from zynthian-data/lv2-custom to the respective location.
It might be possible that with ne newer updates parameter symbols changed? That way the custom ttl would need to be adapted.
1 Like