EightySix — Roland JUNO-6 Clone (v1.1.3 UPDATE - Automation/Midi Learn/Distortion)

[Funkybot's Evil Twin]

The arpeggiator seems to add notes that aren't being played. To reproduce:

1. Load Eighty Six on a track (I'm using Reaper/Mac)
2. Load up a Keys style patch or make your own
3. Turn on the Arpeggiator
4. Set it to Up
5. Range = 1
6. Play an Am triad A-C-E

Expected results: it plays A-C-E in that order repeatedly, no extra notes, constrained to the original octave.

Actual results: it does it's own little thing, acting more like there's a sequence playing versus an Arpeggio.

Also, as a feature request: when Tempo Sync is enabled, there should be somewhere on the GUI where the current sync setting is visible (e.g. 1/4, 1/16, etc.)

[Morphoice]

The arpeggiator seems to add notes that aren't being played. To reproduce:

1. Load Eighty Six on a track (I'm using Reaper/Mac)
2. Load up a Keys style patch or make your own
3. Turn on the Arpeggiator
4. Set it to Up
5. Range = 1
6. Play an Am triad A-C-E

Expected results: it plays A-C-E in that order repeatedly, no extra notes, constrained to the original octave.

Actual results: it does it's own little thing, acting more like there's a sequence playing versus an Arpeggio.

Also, as a feature request: when Tempo Sync is enabled, there should be somewhere on the GUI where the current sync setting is visible (e.g. 1/4, 1/16, etc.)

that's probably because the preset you are using comes with a sequence preprogrammed in the arpeggiator. you can change them and make your own on the effects page. You can set velocity and pitch per step. If you want just the same note you hit on the keyboard played, then set all pitch values to zero

[El°HYM]

The Linux Beta asked for an Update to most recent version (I guess) and is now running in Demo mode. The Output cut off #bug was solved through updating; everything seems to be running just fine on Ubuntu 24.04/Studio now.

[bk]

Just downloaded again to try the new features. UI doesn't show the version number, but the Arp and Drive controls do nothing. I uninstalled the old version before installing this one. Perhaps the demo file hasn't been updated?

Yeah, I might have to take the blame on this one. When I went to un-install a second time, the version number was still 1.1.2.
I had multiple versions of this app on my desktop, and I may have clicked on the wrong one to install. It's all good now.

[Funkybot's Evil Twin]

that's probably because the preset you are using comes with a sequence preprogrammed in the arpeggiator. you can change them and make your own on the effects page. You can set velocity and pitch per step. If you want just the same note you hit on the keyboard played, then set all pitch values to zero

That's exactly what it was. I didn't realize there was a full-blown sequencer hiding on the FX page.

I was going to buy today, but the price keeps changing. Is that expected? I've seen different prices quoted a few times. $56, $39, and today $44.74. What's the price of this and why the variability?

A few small suggestions if I may:

1. Add a display for the Arpeggiator tempo somewhere, even if it's just the Rate label temporarily changing to show the time, like you do for the delay time when tempo sync'd.

2. Rename the "Effects" page, "FX/SEQ" to make clear that there's also a sequencer there

[JerGoertz]

Bug Report: I tried EightySix in Bitwig 5.something on Windows 11. When the plugin started up, I could play notes for 2-4 seconds before audio cut out and produced no sound. Whenever I changed the preset, the 2-4 seconds would "restart" and I could play for that duration before audio stopped again. Changing control values via the interface didn't restart the sound, only changing the preset. (I wonder if this has something to do with Bitwig's plugin sandboxing?) I'm happy to run some tests on my setup if you provide instructions.

Had the same Issue on Linux, rechecked Windows 10. Assuming you are also working @ 96 kHz, the solution is to use standard 44.1 or 48 kHz instead. The plugin (for now) doesnt seem to like any higher Sample Rate. Excellent synth btw. - gorgeous sounds and reverb!

I tried the most recent verison (1.1.4.0) and still saw the error @ 96 kHz, and didn't see the error at 44.1 kHz. So, the sample rate appears to be relevant for the problem to manifest.

Great-sounding synth, BTW!