On 1/20/21 7:43 AM, Bengt Gördén wrote:
On 2021-01-20 00:40, Doug McGarrett wrote:
doug@linux1:~> fluidsynth -j
My thought was that if the "ps" command was positive (found jack daemon, not just ps it self) you could just as well test fluidsynth with jack backend and auto connect with it through the switch -j.
Like so:
fluidsynth -a jack -j /usr/share/sounds/sf2/FluidR3_GM.sf2 ~/Downloads/fur-elise-guitar-duo.mid
fluidsynth have several audio backends.
$ fluidsynth -a help -a options (audio driver): 'alsa','file','jack','oss','pulseaudio','sdl2'
Only alsa, jack, pulseaudio and sdl2 is applicable here. But try them out to see if you get any sound. But only use -j for jack audio backend.
I think I'm missing something very basic or fundamental. There are just too many problems.
My son says I should try Windows,
I take it that you're just not used to doing audio in linux as a musician. System sounds, youtube and playing a mp3 or wav file etc. is not a problem. The desktop environment takes care of that. MIDI and audio (recording, playing, mixing) as a musician is a totally different ballgame. It's never been easy. Not even on windows. There are hoops of problem there to, even on mac. But it's a bit easier to begin with. The problems on windows and mac comes as you go along. Both windows and mac are superior in amount of software and quite often in how advanced some of them are. Especially the plugins.
Is there a package somewhere that installs EVERYTHING? Including libs and repos?
Unfortunately not. But my first suggestion should have worked unless there are problems with your installation. My suggestion used qsynth/fluidsynth with pulseaudio. The second suggestion with command line version should have been even simpler solution for the system. No jack, no gui nothing that gives problems like yours. So my guess is that something isn't right with you're opensuse tumbleweed installation. At least I can't spot it from your information.
But to try to dig some more.
Do this so we can see what's been installed.
zypper se -x jack fluidsynth libfluidsynth1 libfluidsynth2 alsa-plugins-jack pulseaudio-module-jack qsynth qjackctl Cadence libSDL2-2_0-0 libSDL2-2_0-0-32bit fluid-soundfont-gm alsa-utils libasound2
doug@linux1:~> zypper se -x jack fluidsynth libfluidsynth1 libfluidsynth2 alsa-plugins-jack pulseaudio-module-jack qsynth qjackctl Cadence libSDL2-2_0-0 libSDL2-2_0-0-32bit fluid-soundfont-gm alsa-utils libasound2 Repository 'openSUSE:Tumbleweed' is out-of-date. You can run 'zypper refresh' as root to update it. Repository 'home:hawkeye116477:waterfox:build-depends' is out-of-date. You can run 'zypper refresh' as root to update it. Repository 'openSUSE:Factory' is out-of-date. You can run 'zypper refresh' as root to update it. Repository 'openSUSE-Tumbleweed-Non-Oss' is out-of-date. You can run 'zypper refresh' as root to update it. Repository 'openSUSE-Tumbleweed-Oss' is out-of-date. You can run 'zypper refresh' as root to update it. Loading repository data... Retrieving repository 'home:hawkeye116477:waterfox:build-depends' data... Retrieving repository 'home:hawkeye116477:waterfox:build-depends' metadata ...........................[error] Repository 'home:hawkeye116477:waterfox:build-depends' is invalid. [https-download.opensuse.org-658aa113|https://download.opensuse.org/repositories/home:/hawkeye116477:/waterfox:/bu...] Valid metadata not found at specified URL History: - [https-download.opensuse.org-658aa113|https://download.opensuse.org/repositories/home:/hawkeye116477:/waterfox:/bu...] Repository type can't be determined. Please check if the URIs defined for this repository are pointing to a valid repository. Problem loading data from 'home:hawkeye116477:waterfox:build-depends' Resolvables from 'home:hawkeye116477:waterfox:build-depends' not loaded because of error. Reading installed packages... S | Name | Summary | Type ---+------------------------+----------------------------------------------------------+-------- | Cadence | A JACK Audio Toolbox | package | alsa-plugins-jack | JACK I/O Plug-In for ALSA Library | package i+ | alsa-utils | Advanced Linux Sound Architecture Utilities | package i+ | fluid-soundfont-gm | Fluid (R3) General MIDI SoundFont (GM) | package i+ | fluidsynth | A Real-Time Software Synthesizer That Uses Soundfont(tm) | package i | jack | Jack-Audio Connection Kit | package i+ | libSDL2-2_0-0 | Simple DirectMedia Layer Library | package i+ | libSDL2-2_0-0-32bit | Simple DirectMedia Layer Library | package i+ | libasound2 | Advanced Linux Sound Architecture Library | package i+ | libfluidsynth2 | Library for Fluidsynth | package | pulseaudio-module-jack | JACK support for the PulseAudio sound server | package i+ | qjackctl | Graphical User Interface to Control JACK Servers | package i | qsynth | Graphical User Interface for fluidsynth | package doug@linux1:~>
Also. If you could run alsa-info.sh in a terminal (as a normal user. not root). At the end of the test you'll be asked if you want to upload the info to alsa-project.org, do that. When you quit the script you'll get a link at the top. Copy the link and paste it here.
doug@linux1:~> alsa-info.sh
Absolute path to 'alsa-info.sh' is '/usr/sbin/alsa-info.sh', so running it may require superuser privileges (eg. root). So I did run as super-user. Got "Information collected" (heading) "Your ALSA information is in /tmp/also-info.txt.L2Jf07UVMb" That is an extremely long report--many pages of text. I made one so that you can see how it looks. /tmp/also0info.txt.L2Jf07UVMb Firefox can't find this file.
Unfortanitley it's a little bit old so it doesn't say if you have jack2 installed or running. I've made a pull request on github for that today. To check if jack2 is running just issue command: pgrep jackdbus. If you get a PID you've got it running, if not, it's not running. The same can be accomplished with "ps waux | egrep jackdbus". Different answers: doug@linux1:~> pgrep jackdbus doug@linux1:~>
then doug@linux1:~> ps waux | egrep jackdbus doug 2211 0.0 0.0 6188 692 pts/2 S+ 16:57 0:00 grep -E --color=auto jackdbus doug@linux1:~> where "jackdbus" is printed white on red background
There is also pa-info which does quite a lot of checking but you need to upload that to paste.opensuse.org or another service.
To run pa-info and upload to susepaste with expiration of one week do this as normal user.
pa-info | TITLE="My audio settings (pa-info)" NICK=`whoami` susepaste -e "10080"
doug@linux1:~> pa-info | TITLE="My audio settings (pa-info)" NICK=`whoami` susepaste -e "10080" lsof: WARNING: can't stat() tracefs file system /sys/kernel/debug/tracing Output information may be incomplete. which: no alsa-info.sh in (/home/doug/bin:/usr/local/bin:/usr/bin:/bin) which: no alsa-info in (/home/doug/bin:/usr/local/bin:/usr/bin:/bin) Pasted as: https://susepaste.org/20861544 https://paste.opensuse.org/20861544 Link is also in your clipboard. doug@linux1:~> And that's one test that's often asked for when talking to people at linuxaudio.org maillinglists:
cd /tmp && wget http://community.ardour.org/files/adevices.sh && bash ./adevices.sh | TITLE="My audio settings (adevices.sh)" NICK=`whoami` susepaste -e "10080"
doug@linux1:~> cd /tmp && wget http://community.ardour.org/files/adevices.sh && bash ./adevices.sh | TITLE="My audio settings (adevices.sh)" --2021-01-20 17:12:08-- http://community.ardour.org/files/adevices.sh Resolving community.ardour.org (community.ardour.org)... 54.235.123.47 Connecting to community.ardour.org (community.ardour.org)|54.235.123.47|:80... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://community.ardour.org/files/adevices.sh [following] --2021-01-20 17:12:09-- https://community.ardour.org/files/adevices.sh Connecting to community.ardour.org (community.ardour.org)|54.235.123.47|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 2249 (2.2K) [application/octet-stream] Saving to: ‘adevices.sh’ adevices.sh 100%[========================================>] 2.20K --.-KB/s in 0s 2021-01-20 17:12:09 (234 MB/s) - ‘adevices.sh’ saved [2249/2249] doug@linux1:/tmp> Here's the whole works. I hope it means something to you! Thanx for your patience and help! --doug