Package Details: jjazzlab-x-bin 3.2.1-1

Git Clone URL: https://aur.archlinux.org/jjazzlab-x-bin.git (read-only, click to copy)
Package Base: jjazzlab-x-bin
Description: A Midi-based framework dedicated to backing tracks generation
Upstream URL: https://www.jjazzlab.com/
Licenses: LGPL
Submitter: jypma
Maintainer: jypma
Last Packager: jypma
Votes: 3
Popularity: 0.024573
First Submitted: 2021-06-16 09:03 (UTC)
Last Updated: 2022-05-12 09:04 (UTC)

Dependencies (1)

Required by (0)

Sources (2)

Latest Comments

nyxkn commented on 2022-02-07 01:50 (UTC) (edited on 2022-02-07 01:53 (UTC) by nyxkn)

Tried your last update. The software runs fine, but by default it writes all of its config and cache data straight into your home folder. To work around this, one needs to pass the --userdir and --cachedir arguments to jjazzlab.

Together with the _JAVA_OPTIONS fix I mentioned before, my command to launch jjazzlab now looks like this:

_JAVA_OPTIONS=-Duser.home=$HOME/.local/share/jjazzlab \
    /usr/bin/jjazzlab \
    --userdir $HOME/.config/jjazzlab \
    --cachedir $HOME/.cache/jjazzlab

This prevents all possible home cluttering and perfectly fits the standard usage of .local/share, .config, and .cache folders. It looks like it's what the defaults should already be, but it seems like the software has some issues figuring out the correct paths on its own.

@jypma: userdir is also where the "lock" file gets created so this should solve at least one of your issues.

jypma commented on 2022-01-11 08:07 (UTC)

Thanks a lot for all of your input! I've incorporated the suggestions (using system JDK, and fixing the symlink) and bumped to the 3.0.2a version. However, a few issues are still left:

  • I'm still seeing the delays described in https://github.com/jjazzboss/JJazzLab-X/issues/245, which means I'm not currently a user of jjazzlab.
  • The startup (loading) screen doesn't have the right bitmap on it when running the packaged version, vs. running the extracted ZIP directly.
  • The program tries to create a file called "lock" in the current directory when launching. This prevents startup if launched from a non-writable directory.

nyxkn commented on 2022-01-10 14:40 (UTC) (edited on 2022-01-10 14:40 (UTC) by nyxkn)

By default jjazzlab creates a JJazzLab folder in your home.

If you dislike this as much as I do, you can work around this by setting a custom "user.home" property with the _JAVA_OPTIONS environment variable: _JAVA_OPTIONS=-Duser.home=/home/user/whatever/path

nyxkn commented on 2022-01-10 14:28 (UTC)

@jypma: Current version 3.0.2a starts just fine with uhoso's .conf fix!

nyxkn commented on 2022-01-10 14:26 (UTC) (edited on 2022-01-10 14:28 (UTC) by nyxkn)

Confirming uhoso's findings. Not sure if this is the correct approach but the linking issue can be solved by changing the ln command to this: ln -s /opt/jjazzlab-x/bin/jjazzlab ${pkgdir}/usr/bin/jjazzlab.

Also had to comment out jdkhome in the .conf file. Thanks for that suggestion!

uhoso commented on 2021-12-23 10:50 (UTC)

I installed it using trizen with the --movepkg option. The link createt by ln -s ${pkgdir}/opt/jjazzlab-x/bin/jjazzlab ${pkgdir}/usr/bin/jjazzlab pointed to the temporary folder created by trizen. I removed the link and created a new one pointing to /usr/bin/jjazzlab. I had also to comment the line jdkhome="jdk" in /opt/jjazzlab-x/etc/jjazzlab.conf by inserting "#" in front of it.

jypma commented on 2021-12-21 10:29 (UTC)

Version 3.0.1 doesn't start for me, probably related to https://github.com/jjazzboss/JJazzLab-X/issues/245. Does anyone else have more luck?