EightySix — Roland JUNO-6 Clone (v1.1 UPDATE - Velocity Response, Poly Aftertouch)

[phreaque]

Great! I've added that to https://virtualsynthesizers.com/synthes ... nd-juno-6/. Good job!

Your website still missing Kepler (A Juno-6 / 106 emulation synth in FL Studio).

[suseka2003]

Talking about Synths, found a new hardware in youtube video.


29 USD, made to order

[Funkybot's Evil Twin]

What does circuit modelled mean anyway? Modelling every resistor / capacitor?

Circuit modeling at that level exists, but it's wildly CPU expensive. Look at The Scream from Cytomic, SITRAL by Korneff, or the Relab 176 for some recent examples. They sound absolutely great, but eat CPU like nobody's business.

I don't think anyone's doing a complete circuit modeled synth. But they may be doing circuit modeled filters and/or VCA's, then using other approaches in places where circuit modeling is less important.

[Examigan]

Talking about Synths, found a new hardware in youtube video.


29 USD, made to order

That looks/sounds interesting!

[pixelizer]

Great! I've added that to https://virtualsynthesizers.com/synthes ... nd-juno-6/. Good job!

Your website still missing Kepler (A Juno-6 / 106 emulation synth in FL Studio).

You're right, I haven't uploaded the FL versions to the website yet. It really is essential. I'll get round to it soon. Thanks for the link.

[ampetrosillo]

What does circuit modelled mean anyway? Modelling every resistor / capacitor?

Circuit modeling at that level exists, but it's wildly CPU expensive. Look at The Scream from Cytomic, SITRAL by Korneff, or the Relab 176 for some recent examples. They sound absolutely great, but eat CPU like nobody's business.

I don't think anyone's doing a complete circuit modeled synth. But they may be doing circuit modeled filters and/or VCA's, then using other approaches in places where circuit modeling is less important.

You can get somewhere in the middle, with lookup tables and sufficiently cheap interpolation.

[Funkybot's Evil Twin]

What does circuit modelled mean anyway? Modelling every resistor / capacitor?

Circuit modeling at that level exists, but it's wildly CPU expensive. Look at The Scream from Cytomic, SITRAL by Korneff, or the Relab 176 for some recent examples. They sound absolutely great, but eat CPU like nobody's business.

I don't think anyone's doing a complete circuit modeled synth. But they may be doing circuit modeled filters and/or VCA's, then using other approaches in places where circuit modeling is less important.

You can get somewhere in the middle, with lookup tables and sufficiently cheap interpolation.

Yep, but that's where the questions of the definition come into play. How close is close enough?

And Cytomic and Kobeff's Sitral use lookup tables in spots from what I understand, but still eat quite a bit of CPU.

[Morphoice]

Thanks for the continued testing, this is genuinely useful.

CPU / sound cutting off: I could reproduce the CPU piling up with each note which should already be fixed in the current version 1.0.2. So this was indeed a bug, not just "circuit modeling is heavy." Looks like voices weren't being freed properly Thanks Danilo, Vortifex and Tj Shredder for pinning it down clearly.

I will have a look at the Chorus during the next revision later today.

On the "circuit modeled" / Faust question: yes, the DSP is written in Faust. Faust is just the language — the modeling is in the math, not the toolchain. We derive transfer functions from the actual circuit sections where it matters, and use lookup tables / optimizations where component-level accuracy isn't audible.

And thanks pixelizer for adding it to the list — much appreciated.

[Morphoice]

I tracked down the chorus mono-cancellation. The stereoWidth control was a M/S enhancement that peaked exactly at the default (0.5), which combined with the 180° L/R lfo offset to anti-phase the wet signal in mono summation. New default is direct L/R routing — the same topology as the original hardware, width now mapped properly and mono playback preservs the chorus instead of cancelling it. It will be rolled out with versoin 1.0.3 later today. Thanks again for the report.

[Uncle E]

You might want to look at how Universal Audio implemented the chorus in their Brigade plugin. In addition to the classic mode, they added a dual mode that modulates both side, providing a similar sound with superior mono compatibility.

[Uncle E]

Tried it just now. It sounds very good. I don't know if this soft sound is accurate but it's what I personally look for in a Juno.

[bk]

Sounds pretty good, here.
Noticed that if you select a patch in the browser, the patch changes, but the name at the bottom of the gui does not.

[Uncle E]

1.0.4 is available for download on Gumroad. Definitely funny things going on with the envelope that I didn't notice yesterday. Decays and Releases aren't consistent, and the sound cuts off every time the bars loop.

[Morphoice]

1.0.4 is available for download on Gumroad. Definitely funny things going on with the envelope that I didn't notice yesterday. Decays and Releases aren't consistent, and the sound cuts off every time the bars loop.

Thanks for the report — would you mind giving me a bit more to work with so I can actually track down the issue? "Funny things going on" is hard to chase without specifics.

The only thing that has been added since 1.0.3 was LFO and Envelope routing to the PWM. The envelope itself never changed.

A few things would really help:

Which DAW (and version) are you running it in?
VCA settings when you hear the issue — actual slider positions for Attack / Decay / Sustain / Release, plus envelope polarity, and whether VCF Env is engaged.
The pattern — how many simultaneous notes (chords or melodic?), and how long is the loop region (1 bar? 4 bars? 8?). A short MIDI export or even a screenshot of the piano-roll would be ideal.
The cutoff symptom — does the sound cut at the exact loop boundary, or a few ms before/after? Is the release tail killed instantly, or fading out faster than the Release knob suggests? And does it happen on every loop or only when the loop is shorter than your release time?
"Decays and Releases aren't consistent" — could you describe what "inconsistent" looks like? Different notes in the same pattern releasing for different lengths? The same key sounding different on second press? Or the Release knob value not matching what you hear?
Comparing against 1.0.3: did the same pattern work as expected in 1.0.3?
The cutoff at loop boundaries is most likely the polyphony cap (1.0.4 enforces 8 voices to match the real Juno-6 plus two "for good measure ", so release tails may simply get stolen when a new bar starts). If that's the cause, I can make it user configurable — but I want to confirm this is an actual bug before changing anything.

Thanks for taking the time to report it.

[Uncle E]

Thanks for the report — would you mind giving me a bit more to work with so I can actually track down the issue? "Funny things going on" is hard to chase without specifics.

Audio file and screenshot attached. You can hear how the sound cuts out much too quickly for those decay and release settings. Also, you'll hear in the middle how one note's attack is much longer than the rest. The attack time was set the same throughout, I didn't change or automate it.

The only thing that has been added since 1.0.3 was LFO and Envelope routing to the PWM. The envelope itself never changed.

Thank you. That explains why it doesn't sound the same to me today as it did yesterday. When I set the PWM modulation control to the middle, it sounds more like what I heard yesterday.

Which DAW (and version) are you running it in?

Gridshift

The pattern — how many simultaneous notes (chords or melodic?), and how long is the loop region (1 bar? 4 bars? 8?).

4 note chords, 8 bars.

A short MIDI export or even a screenshot of the piano-roll would be ideal.

Attached

The cutoff symptom — does the sound cut at the exact loop boundary, or a few ms before/after? Is the release tail killed instantly, or fading out faster than the Release knob suggests? And does it happen on every loop or only when the loop is shorter than your release time?

Cuts at exactly the loop boundary. Release tail is killed instantly. Happens every loop. I have the same part running next to it with AudioThing July and it doesn't cut off.

"Decays and Releases aren't consistent" — could you describe what "inconsistent" looks like? Different notes in the same pattern releasing for different lengths? The same key sounding different on second press? Or the Release knob value not matching what you hear?

In addition to what you hear in the audio example, I may have been getting confused by the voice stealing. I didn't realize there's a 6-voice limitation.

Comparing against 1.0.3: did the same pattern work as expected in 1.0.3?

Sorry, I didn't compare it. I was only playing it live yesterday.

The cutoff at loop boundaries is most likely the polyphony cap (1.0.4 enforces 8 voices to match the real Juno-6 plus two "for good measure ", so release tails may simply get stolen when a new bar starts). If that's the cause, I can make it user configurable — but I want to confirm this is an actual bug before changing anything.

It's cutting out at 6 voices for me. Even if it's not a bug, user configurable would be nice. Most of the criticism Softube gets for their Juno is the voice limitation.