I noticed aliasing too. At first I thought it was a particularly gritty patch but then it became evident this was undesirable artifacts. A recent review was less than complimentary but did say it sounded retro, but not in a 1980’s way! Shame. I have a particular affinity with the Juno and was hoping this would be good for me.
4 Likes
I noticed this problem too. Let’s say that the project is in full active evolution, with bugs solved and constant improvements. I don’t know wich is the version installed in Zynthian but the last version was released today! It would be nice to have periodic updates in Vangelis.
2 Likes
I built the new 2.3.1 version on my V5.1. Sadly, despite the reworking of VCF, it still sounds appalling when compared with similar TAL Uno presets… Nevertheless, it’s nice to see that the developers are addressing the feedback they’re getting!
2 Likes
Rebrand it as a Korg Poly 800 and call it done!
3 Likes
New version 2.4.2 (three new versions since yesterday) with several improvements. I tested the Windows version and i can confirm that aliasing is no longer a problem.
2.4.2 Wavetable DCO, UI improvements
- Replaced polyBLEP oscillators with bandlimited wavetable DCO, eliminates aliasing at all pitches
- Oscillator runs at base sample rate; VCF handles its own oversampling internally
- Remove output saturator for cleaner signal path (clip LED at ±1.0)
- Master volume: squared audio taper for better low-end control, CC7 mapped
- Double-click text editing on knobs (was sliders only)
- Spectrum analyzer: 4096-point FFT for better low-frequency resolution
- VCF frequency response scope: stop drawing line along bottom of display
4 Likes
Looking forward to this on the zynthian!
I am curious if there’s a way to get the oscilloscope visualisation working on Zynthian, on the main screen without using VNC.
Yay, just tested 2.4.2 on my Zynthian V5.1 and the improvement is obvious. I’m looking forward to try it on my old V2 and see whether some performance boost, albeit marginal, makes it viable for my use case.
1 Like
Hey everyone, this is Karl the developer of the KR-106, I appreciate all of your feedback. I just pushed a new oscillator model in v2.4.2 that uses bandlimited wavetables instead of the polyBLEP. Still working on calibrating my filter model. Is my arm64 build working now? I don’t have hardware to test it on.
12 Likes
Hi @kayrockscreenprintin! A very warm welcome and lots of thanks for such a wonderful contribution to the world. I just tested the ARM64 build on zynthian RPi5 and it works. I will test on RPi3 & 4 in case there are any oddities. I am so pleased to hear the aliasing issue is resolved. My heart sank when I heard it because this is the synth of my uni days and really want to play with it.
Here’s one way:
You can search on Zynscope in this forum to find more info on this PureData patch.
Thanks @tunagenes ,
It has been added to the default PureData presets since then, under the graphic bank. So no more manual preset upload is needed.
Tried it out on a V4 kit and halfway there with latest vangelis.
Learned about the gotcha of disabling VNC to get the scope on the Zynthian screen.
Double-checked the audio output, however I see no moving scope (also checked with VNC enabled and looking at the Engines VNC). Any advice on the audio routing?
Here’s the recording:
Hmmm, I don’t know what’s going on, seems like it should work in your video. I see a few possible avenues to look at:
The PureData patch, or the settings used for it, might have to be updated for Vangelis.
You could try a more ‘standard’ engine like ZynAddSubFX just to eliminate the new engine factor.
I wonder if @wyleu ever got the tutorial written or @ronsum has any ideas…
I also tried the Surge synth with same result.
1 Like
I tried it with KR-106 and it worked so I decided to remove all chains and capture a video. I added the chains, send KR-106 audio out to PD and it is no longer working. I’ll investigate further and let you know if I get it figured out.
Whilst you have the hood up, can you see whether there is an option to direct output to the main UI, e.g. adding DISPLAY=:0 to whatever launches the GEM window?
I added the chains and sent audio to zynscope and no responce. Next I turned on VNC to see what was going on with my PC. I looked at the pd patch and all looked normal as expected. I clicked on the GEM tab to see the GEM window and played random notes. Still no responce. So I clicked on the patchage tab and noticed no connections going to pd audio input, I manually connected the audio output of KR-106 to the pd audio input and played some notes. The zynscope GEM window now showed the wave. So I turned off VNC and clicked save. Soon I was greeted by the ERROR screen, so I rebooted. Now I see the GEM window on my zynthian screen and it is working. With this clue, perhaps @riban knows how to make a permanent fix.
1 Like
Thanks @ronsum - I’m wondering if you saw this and if it might even be related to the current issue we’re seeing.
I did, but I don’t think that is the issue because the GEM window is displayed on zynthian when vnc is disabled. I think the jack audio routing is the issue here, but that is just my best guess. Since I made the manual connection in patchage it seems to be working even after deleting all chains and starting over. It also has continued working after reboot.
Welcome to the zynthian forum! As you had realized, this community is highly pleased with the KR-106! Thanks a lot for bringing this nice plugin to the world! Both of you deserve the heaven! 
FYI, we have integrated the plugin and now it’s fully accessible from the Zynthian UI, including well grouped and sorted parameters, envelope and filter widgets, etc.
Also, i just updated the KR-106 packages and now the latest version is available for all zynthian users (vangelis & oram branches). Simply update and enjoy!
All the best!
5 Likes