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 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. I made one so that you can see how it looks. http://alsa-project.org/db/?f=ca205085b0aa34e10ff956372d8cf288ef4958b1 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". 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" And 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" -- /bengan