|
|
Post by Jerome on Dec 7, 2023 21:48:52 GMT 1
For testing by Linux users, please provide feedback in this thread ! DEB package: jjazzlab_4.0-1_amd64.deb (Debian-based distros: Ubuntu etc) Download then run " sudo apt install ./jjazzlab_4.0-1_amd64.deb" RPM package: jjazzlab-4.0-0.x86_64.rpm (Red Hat based distros: Fedora etc) Download then run " yum --nogpgcheck localinstall ./jjazzlab-4.0-0.x86_64.rpm" I quickly tested the DEB package on Ubuntu 22, it worked OK. I could not test the RPM package, so feedback is very welcome.
Note: both packages depends on the libfluisynth3 package (version >= 2.1.0). If you don't already have it on your system, using the installation instruction above should install it together with JJazzLab 4. In case of problem, you can also install it manually, eg "sudo apt install libfluisynth3". If ever your system can't have a recent version of libfluidsynth3, JJazzLab4 will work, but the internal synth jjSynth will be disabled, so you will be back with the Midi mess of JJazzLab 3...
It is strongly recommended to tune Linux for audio, by applying the 3 easy steps here: jackaudio.org/faq/linux_rt_config.html This will avoid audio delays/cracks when using jjSynth/FluidSynth. |
|
|
|
Post by Jerome on Dec 7, 2023 22:50:39 GMT 1
Question for you Linux guys.
With JJazzLab 4 I tried to make rpm/deb packages but, with so many Linux distros out there with different package managers, I wonder if it would be more simple to come back to the standalone zip package, like for JJazzLab 3, which is supposed to work on any distro.
To fully benefit from JJazzLab 4, one will have to manually install libfluidsynth3 (eg "sudo apt install libfluidsynth3"), but I guess it's acceptable. The downside of using zip is that I think JJazzLab can not be made visible in the distro "store", so it's less "accessible" to new users...
So what do you think ? Do you prefer packages or is the .zip good enough ? any advice by people with software distribution experience on linux is welcome.
|
|
|
|
Post by bengan on Dec 8, 2023 0:00:36 GMT 1
Hi,
Many thanks for the beta.
I tried the rpm package on OpenSUSE Tumbleweed. Couldn't get jjSynth to work. And when I opened the options dialog and tried to change to VirMIDI, jjazzlab froze. I had to kill the application from the cli. I tried a few times but it didn't work. Then when I copied my 3.2.1 midi.properties to 4.0 it worked. But if you fiddle with the jjSynth option, jjazzlab hangs.
My old midi.properties
MidiEditorPath=/usr/bin/qtractor
MidiInProp=VirMIDI [hw:0,0,0]
MidiOutProp=VirMIDI [default]
SplitNote=60
Otherwise it looks fine as far as I can see tonight. It's getting late so I'll get back to the other question (zip/rpm/deb) tomorrow.
Cheers and good night.
PS. I've got libfluisynth3 installed.
# zypper if libfluidsynth3 | grep Version
Version : 2.3.4-1.1
|
|
|
|
Post by Jerome on Dec 8, 2023 9:29:42 GMT 1
Thanks bengan. Please post the log file. I would also need the list of the installed files from the libfluidsynth3 package (eg on Debian you get this with "dpkg -L libfluidsynth3")
|
|
|
|
Post by Jerome on Dec 8, 2023 16:49:55 GMT 1
@@test je viens de créer une discussion pour les retours en français, je déplace ton post là-bas
|
|
|
|
Post by Jerome on Dec 8, 2023 21:00:57 GMT 1
@ bengan I tried JJazzLab using OpenSUSE Leap (via VirtualBox on my Windows PC). It worked but the audio of the FluidSynth lib (jjSynth) was really not good (cracks, delays), and export to audio did not work. I noticed some warning "fluidsynth: warning: Failed to set thread to high priority", which explains the cracks. I did the changes described in the link below, then it was much better, and export to audio worked. jackaudio.org/faq/linux_rt_config.html |
|
|
|
Post by hajdam on Dec 12, 2023 21:14:56 GMT 1
Hi, tried BETA on Fedora 38. I ignored dependencies as on this version there are packages under name fluidsynth and fluidsynth-libs (2.3.4-1) already present. JJazzLab was installed in applications menu under Others and without icon, but seems to be working ok. Well, it's hard to make general installers for Linux, there are also options to make packages like flatpak, snap, AppImage... I think it would still be great / safer to also provide zip file, which could be used as fallback or on more exotic configurations... Best regards
|
|
|
|
Post by Jerome on Dec 12, 2023 22:14:32 GMT 1
Thanks hajdam. Been a long time, I hope you're well. I agree with you, now that I start to understand the complexity of packaging for Linux distros, I should always keep the .zip file, which is also easier to build for me.
I was thinking that by using Linux packages JJazzLab could be more visible/accessible to more linux users. Though I guess it means I need to put the packages on some public repositories, but I have not started investigating this.
Regarding Snap or Flatpak, I had a quick look but my understanding was that I would need to embed libfluidsynth (the only direct dependency) in the snap, but how can I do this since libfluidsynth (and libfluidsynth dependencies) seems to vary for each distro... I'm really a newbie for that matter, any advice is appreciated.
|
|
|
|
Post by donnek on Dec 15, 2023 21:33:50 GMT 1
I'm trying to install the deb on AVLinux (which is MXLinux under the hood).
I'm getting the following error:
dpkg-deb: error: archive '/home/kevin/data/downloads/backing/jjazzlab_4.0-1_amd64.deb' uses unknown
compression for member 'control.tar.zst', giving up
I've installed zstd, but that doesn't help.
Is this some other compression format?
Thanks.
UPDATE: Solved
It turns out that this is because Debian versions of dpkg older than 1.21.18 do not support zstd compression (Ubuntu versions got the support much earlier). The version in AVL-MX is 1.20.13.
So the deb needs to be unpacked and repacked using xz as the compression instead of zstd. In the dir where the deb has been saved, run:
ar x jjazzlab_4.0-1_amd64.deb # Unpack the deb. zstd -d < control.tar.zst | xz > control.tar.xz # Decompress the zst file and recompress it using xz.
zstd -d < data.tar.zst | xz > data.tar.xz # Decompress the zst file and recompress it using xz. this is 300Mb, so it will take a while to recompress. ar -m -c -a sdsd jjazzlab_4.0-1.deb debian-binary control.tar.xz data.tar.xz # Repack a new deb using the xz compressed files. rm debian-binary control.tar.xz data.tar.xz control.tar.zst data.tar.zst # Tidy up. sudo apt install ./jjazzlab_4.0-1.deb # Install the new deb.
Thanks to:
JJazzLab then opens and run fine, so far as I can see. The embedded synth makes setup much easier than the last time I experimented with it, so that's very welcome. Now to figure out how to use the software properly!
jérôme: Would it maybe be worth repacking the deb at source, so that this issue doesn't arise for installations that use the older Debian dpkg? The size goes down by about 30Mb too.
|
|
|
|
Post by bengan on Dec 16, 2023 10:22:03 GMT 1
@ bengan I tried JJazzLab using OpenSUSE Leap (via VirtualBox on my Windows PC). It worked but the audio of the FluidSynth lib (jjSynth) was really not good (cracks, delays), and export to audio did not work. I noticed some warning "fluidsynth: warning: Failed to set thread to high priority", which explains the cracks. I did the changes described in the link below, then it was much better, and export to audio worked. jackaudio.org/faq/linux_rt_config.htmlI'm really sorry for being absent. I got covid the night after I posted my message. Not the best of diseases. On the road to recovery now. I'll get back to you in a few days when I feel better. |
|
