FFT is slow compared to older release about beads

[cacheflowe]

Now that I've looked at the list of jars in the latest build, it seems like there are a couple that are doubled up (jlayer & tritonous-share). This reminds me that my Processing IDE freezes when downloading the Beads library via the library manager, which is an entirely different problem and might warrant its own Issue. I generally grab the latest libraries via the Processing IDE and bring them into my Eclipse setup. So these doubled-up jars are being downloaded from the Processing IDE (I just wiped it and started fresh to confirm). Hope this is helpful!

[orsjb]

Thanks for the heads up on this Justin. I had an intern working on this and hadn’t noticed this issue, something in the build process gone wrong no doubt. I can’t guarantee when we’ll get to this next as there’s limited resources. Please advise if you can specify a workaround for other people.

…

On 30 Dec 2020, at 4:15 am, Justin Gitlin ***@***.***> wrote: Now that I've looked at the list of jars in the latest build, it seems like there are a couple that are doubled up (jlayer & tritonous-share). This reminds me that my Processing IDE freezes when downloading the Beads library via the library manager, which is an entirely different problem and might warrant its own Issue. I generally grab the latest libraries via the Processing IDE and bring them into my Eclipse setup. So these doubled-up jars are being downloaded from the Processing IDE (I just wiped it and started fresh to confirm). Hope this is helpful! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#28 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAGYIT3LQQV7JGO2HCASRDSXIFCXANCNFSM4VNNCEBQ>.

[cacheflowe]

I don't have a workaround for any of this - apologies. I reverted to the older version, as FFT is one of my primary uses, and the refresh rate is super important to me. I'll let you know if I can help figure anything out!

[cacheflowe]

I upgraded my tools to Processing 4 and OpenJDK 11, and this is no longer an issue 🎉 Seems like this could've been a Java 8 issue.