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

[TechHaus]

In the tune of a famous Bob Marley song "No Linux, No Buy"

Well, the Linux version just dropped — so by your own rule, "No Linux, No Buy" becomes "Got Linux, Must Buy." We'll be watching for that order.

No sound in REAPER, and the bottom preset window is almost getting cut off, but not quite. The light shows that it is receiving MIDI. Will keep testing new versions, and will probably fork over some cash for bringing it over to us Linux folk when it works!

Thanks.

[Mogular]

I can see MIDI learn on the effects. Any plans to do the same for the synth parameters?

Edit: a couple of switches seem to be midi learnable but none of the sliders

[Morphoice]

In the tune of a famous Bob Marley song "No Linux, No Buy"

Well, the Linux version just dropped — so by your own rule, "No Linux, No Buy" becomes "Got Linux, Must Buy." We'll be watching for that order.

No sound in REAPER, and the bottom preset window is almost getting cut off, but not quite. The light shows that it is receiving MIDI. Will keep testing new versions, and will probably fork over some cash for bringing it over to us Linux folk when it works!

Thanks.

I'm sorry it's not working properly for you. The honest situation is that I don't own a Linux machine, so I can't realistically test or support the plugin across all the different distros and DAW combinations out there — I'd just be shipping fixes blind.

For now I'll keep the Linux builds available for anyone who can get them running, but I'm not in a position to actively troubleshoot that environment. For context, Linux accounts for about 0.3% of downloads, so I have to be realistic about where my limited time goes — and right now that's the Mac and PC versions most people are on.

If a Linux user who knows the ecosystem ever wants to help track down what's going wrong, I'd genuinely welcome it. But I don't want to promise support I can't deliver. Appreciate you testing it and reporting back either way.

[Morphoice]

I can see MIDI learn on the effects. Any plans to do the same for the synth parameters?

Edit: a couple of switches seem to be midi learnable but none of the sliders

Currently the new sliders I made over the past week don't have that functionality, but it's planned to add it in the future.

[Mogular]

Great to know thanks

[Morphoice]

In the tune of a famous Bob Marley song "No Linux, No Buy"

Well, the Linux version just dropped — so by your own rule, "No Linux, No Buy" becomes "Got Linux, Must Buy." We'll be watching for that order.

No sound in REAPER, and the bottom preset window is almost getting cut off, but not quite. The light shows that it is receiving MIDI. Will keep testing new versions, and will probably fork over some cash for bringing it over to us Linux folk when it works!

Thanks.

I did some changes in the JUCE framework and recompiled if you want to redownload and test, it's a long shot but maybe it works

[audiojunkie]

In the tune of a famous Bob Marley song "No Linux, No Buy"

Well, the Linux version just dropped — so by your own rule, "No Linux, No Buy" becomes "Got Linux, Must Buy." We'll be watching for that order.

No sound in REAPER, and the bottom preset window is almost getting cut off, but not quite. The light shows that it is receiving MIDI. Will keep testing new versions, and will probably fork over some cash for bringing it over to us Linux folk when it works!

Thanks.

I'm sorry it's not working properly for you. The honest situation is that I don't own a Linux machine, so I can't realistically test or support the plugin across all the different distros and DAW combinations out there — I'd just be shipping fixes blind.

For now I'll keep the Linux builds available for anyone who can get them running, but I'm not in a position to actively troubleshoot that environment. For context, Linux accounts for about 0.3% of downloads, so I have to be realistic about where my limited time goes — and right now that's the Mac and PC versions most people are on.

If a Linux user who knows the ecosystem ever wants to help track down what's going wrong, I'd genuinely welcome it. But I don't want to promise support I can't deliver. Appreciate you testing it and reporting back either way.

@Morphoice: The solution is much more simple that it seems. Let me explain how "most" developers do it, and why. It will make much more sense. As you know, there are more than 600+ Linux distros out there. No one wants to support all of that (and no one really needs to). The most popular distro by far, is the Debian family of distros, which includes the Ubuntu family. For the most part, Linux is simply a kernel with various libraries of various differing versions, along with a repository of compiled applications and a package manager to mange those applications. This is a bit simplified, but at the core, that's what it basically is.

Each distro has its own philosophy on what is packaged and how it is released. Some distros use a rolling release, where the newest packages are released as soon as they are made available, like Arch Linux. Some are very, very conservative, and use a versioned release, and only release when there has been extensive testing of the software. Then they freeze the version and only do bug fixes or security patches to it until the next new version is ready, like Debian does.

The key point to all of it, is that most packages in Linux, regardless of the distro used, use almost the exact same libraries, even if the library versions differ. And since the libraries are designed to be backwards compatible, most distros using newer libraries can run software from distros using older libraries.

So, the key is to compile your software on a distro, such as Debian, and produce just two binaries: a .DEB package and a zipped archive of the binaries that were compiled on Debian. For the majority of the Linux users, the .DEB package will work great for the .Debian family of distros (including the Ubuntu family). This covers most of the Linux users. The other package, that contains the binaries, is for the remaining Linux distros. You simply put a readme file in the Zipped package that tells where the binaries need to be placed, and you are done. This covers all of Linux. To remain most compatible, you compile with the oldest still supported long term version of Debian. So, if the new released version of Debian is 13, you compile on Debian version 12. That should cover pretty much everyone.

On your regular computer, you use Virtualbox or KVM/QEMU to install Debian on to your regular computer. You compile your software on that. You don't need a separate computer to support Linux. The software is free, so there is no cost. Officially, you only support Debian, but it works for almost everyone. This is how most Linux developers do it.

I hope this helps you continue to persevere with Linux until you become more comfortable with it.

[D-Fusion]

The easiest is just to compile it and make a zip file and let us copy and paste the files to the vst or clap folder.

Then it can be used on any distro

[Morphoice]

In the tune of a famous Bob Marley song "No Linux, No Buy"

Well, the Linux version just dropped — so by your own rule, "No Linux, No Buy" becomes "Got Linux, Must Buy." We'll be watching for that order.

No sound in REAPER, and the bottom preset window is almost getting cut off, but not quite. The light shows that it is receiving MIDI. Will keep testing new versions, and will probably fork over some cash for bringing it over to us Linux folk when it works!

Thanks.

I'm sorry it's not working properly for you. The honest situation is that I don't own a Linux machine, so I can't realistically test or support the plugin across all the different distros and DAW combinations out there — I'd just be shipping fixes blind.

For now I'll keep the Linux builds available for anyone who can get them running, but I'm not in a position to actively troubleshoot that environment. For context, Linux accounts for about 0.3% of downloads, so I have to be realistic about where my limited time goes — and right now that's the Mac and PC versions most people are on.

If a Linux user who knows the ecosystem ever wants to help track down what's going wrong, I'd genuinely welcome it. But I don't want to promise support I can't deliver. Appreciate you testing it and reporting back either way.

@Morphoice: The solution is much more simple that it seems. Let me explain how "most" developers do it, and why. It will make much more sense. As you know, there are more than 600+ Linux distros out there. No one wants to support all of that (and no one really needs to). The most popular distro by far, is the Debian family of distros, which includes the Ubuntu family. For the most part, Linux is simply a kernel with various libraries of various differing versions, along with a repository of compiled applications and a package manager to mange those applications. This is a bit simplified, but at the core, that's what it basically is.

Each distro has its own philosophy on what is packaged and how it is released. Some distros use a rolling release, where the newest packages are released as soon as they are made available, like Arch Linux. Some are very, very conservative, and use a versioned release, and only release when there has been extensive testing of the software. Then they freeze the version and only do bug fixes or security patches to it until the next new version is ready, like Debian does.

The key point to all of it, is that most packages in Linux, regardless of the distro used, use almost the exact same libraries, even if the library versions differ. And since the libraries are designed to be backwards compatible, most distros using newer libraries can run software from distros using older libraries.

So, the key is to compile your software on a distro, such as Debian, and produce just two binaries: a .DEB package and a zipped archive of the binaries that were compiled on Debian. For the majority of the Linux users, the .DEB package will work great for the .Debian family of distros (including the Ubuntu family). This covers most of the Linux users. The other package, that contains the binaries, is for the remaining Linux distros. You simply put a readme file in the Zipped package that tells where the binaries need to be placed, and you are done. This covers all of Linux. To remain most compatible, you compile with the oldest still supported long term version of Debian. So, if the new released version of Debian is 13, you compile on Debian version 12. That should cover pretty much everyone.

On your regular computer, you use Virtualbox or KVM/QEMU to install Debian on to your regular computer. You compile your software on that. You don't need a separate computer to support Linux. The software is free, so there is no cost. Officially, you only support Debian, but it works for almost everyone. This is how most Linux developers do it.

I hope this helps you continue to persevere with Linux until you become more comfortable with it.

The Linux version should now be working. Both ARM64 and AMD64. On Debian 13 it ran fine in Reaper.

[GaryG]

Can confirm it's working on Linux Mint (debian/ubuntu based).

Only issue I found is that the Hold and Arp on/off buttons don't seem to do anything unless I'm doing something wrong..?

Regardless, sounds really nice, thanks.

[audiojunkie]

In the tune of a famous Bob Marley song "No Linux, No Buy"

Well, the Linux version just dropped — so by your own rule, "No Linux, No Buy" becomes "Got Linux, Must Buy." We'll be watching for that order.

No sound in REAPER, and the bottom preset window is almost getting cut off, but not quite. The light shows that it is receiving MIDI. Will keep testing new versions, and will probably fork over some cash for bringing it over to us Linux folk when it works!

Thanks.

I'm sorry it's not working properly for you. The honest situation is that I don't own a Linux machine, so I can't realistically test or support the plugin across all the different distros and DAW combinations out there — I'd just be shipping fixes blind.

For now I'll keep the Linux builds available for anyone who can get them running, but I'm not in a position to actively troubleshoot that environment. For context, Linux accounts for about 0.3% of downloads, so I have to be realistic about where my limited time goes — and right now that's the Mac and PC versions most people are on.

If a Linux user who knows the ecosystem ever wants to help track down what's going wrong, I'd genuinely welcome it. But I don't want to promise support I can't deliver. Appreciate you testing it and reporting back either way.

@Morphoice: The solution is much more simple that it seems. Let me explain how "most" developers do it, and why. It will make much more sense. As you know, there are more than 600+ Linux distros out there. No one wants to support all of that (and no one really needs to). The most popular distro by far, is the Debian family of distros, which includes the Ubuntu family. For the most part, Linux is simply a kernel with various libraries of various differing versions, along with a repository of compiled applications and a package manager to mange those applications. This is a bit simplified, but at the core, that's what it basically is.

Each distro has its own philosophy on what is packaged and how it is released. Some distros use a rolling release, where the newest packages are released as soon as they are made available, like Arch Linux. Some are very, very conservative, and use a versioned release, and only release when there has been extensive testing of the software. Then they freeze the version and only do bug fixes or security patches to it until the next new version is ready, like Debian does.

The key point to all of it, is that most packages in Linux, regardless of the distro used, use almost the exact same libraries, even if the library versions differ. And since the libraries are designed to be backwards compatible, most distros using newer libraries can run software from distros using older libraries.

So, the key is to compile your software on a distro, such as Debian, and produce just two binaries: a .DEB package and a zipped archive of the binaries that were compiled on Debian. For the majority of the Linux users, the .DEB package will work great for the .Debian family of distros (including the Ubuntu family). This covers most of the Linux users. The other package, that contains the binaries, is for the remaining Linux distros. You simply put a readme file in the Zipped package that tells where the binaries need to be placed, and you are done. This covers all of Linux. To remain most compatible, you compile with the oldest still supported long term version of Debian. So, if the new released version of Debian is 13, you compile on Debian version 12. That should cover pretty much everyone.

On your regular computer, you use Virtualbox or KVM/QEMU to install Debian on to your regular computer. You compile your software on that. You don't need a separate computer to support Linux. The software is free, so there is no cost. Officially, you only support Debian, but it works for almost everyone. This is how most Linux developers do it.

I hope this helps you continue to persevere with Linux until you become more comfortable with it.

The Linux version should now be working. Both ARM64 and AMD64. On Debian 13 it ran fine in Reaper.

Nice! I’ll check it out! Thank you!