Is it possible to change the JVM used by beaTunes on OS X?
beaTunes on M1 is dead-slow running the JVM under Rosetta2. Is there a way to change the JVM used by beaTunes, so I can point it to an M1-native JVM?
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by hendrik on 19 Mar, 2021 06:09 PM
Hi Amos,
I wish it was that simple, but beaTunes depends on a set of native libraries that aren’t necessarily available yet for ARM.
So simply swapping out the JVM won’t do the job.
Sorry,
-hendrik
2 Posted by amos.elberg on 19 Mar, 2021 07:01 PM
Do you have an ETA? All of the dylibs I'm seeing under there look to come
from you guys. I'm not saying beaTunes is unusable on M1 at present, but
its definitely on the edge of unusable.
Support Staff 3 Posted by hendrik on 20 Mar, 2021 11:23 AM
Hey Amos,
yes, the used dylibs are indeed all ours. That said, it is impossible for a small indie shop to continuously provide free updates, because Apple decided it was good idea to change the eco-system. So M1 support will probably be part of a larger, paid upgrade called v6. And that is simply not done yet.
So, no, unfortunately, I don't have an ETA at this time. But if you recently bought a license, I'm absolutely willing to issue a refund.
If you are just trying out beaTunes for the first time, please consider that it's absolutely possible that M1 is not the problem, but that beaTunes should be configured differently.
I'd be very happy to help out here. If that's the case, please let me know how many tracks are in your collection, whether it's Music.app-based or folder-based, and what exactly seems to be extra slow.
Thank you,
-hendrik