MIDI problem--no sound
(TW) Have a musical keyboard, "Studio 61" by Fatar, which I know works-- I saw it demoed when I bought it--but I have yet to make a sound with it. When I research midi, I get recommends for several different midi apps, all of which seem to assume you have your keyboard working. What must I do to get the instrument to produce musical notes in my speakers? Some futzing around shows the unit plugged into a usb port on the computer called (by lshw) usb3 Audio device E-MU XMidi1X1Tab physical id: 5 bus info: usb@1:5 serial: E-MU-E6-3F0E-07D90A1E-1014A-TAB capabilities: usb-1.10 audio control configuration: driver=snd-usb-audio maxpower=100mA speed=12Mbit/s (Unit is self powered by wall-wart and should not need power from the computer.) (and by lsusb) Bus 001 Device 007 Creative Technology Ltd Xmidi 1x1 Tab --doug
On 1/14/21 1:45 AM, Doug McGarrett wrote:
(TW) Have a musical keyboard, "Studio 61" by Fatar, which I know works-- I saw it demoed when I bought it--but I have yet to make a sound with it. When I research midi, I get recommends for several different midi apps, all of which seem to assume you have your keyboard working. What must I do to get the instrument to produce musical notes in my speakers?
Some futzing around shows the unit plugged into a usb port on the computer called (by lshw)
usb3 Audio device E-MU XMidi1X1Tab physical id: 5 bus info: usb@1:5 serial: E-MU-E6-3F0E-07D90A1E-1014A-TAB capabilities: usb-1.10 audio control configuration: driver=snd-usb-audio maxpower=100mA speed=12Mbit/s
(Unit is self powered by wall-wart and should not need power from the computer.)
(and by lsusb)
Bus 001 Device 007 Creative Technology Ltd Xmidi 1x1 Tab
--doug Addition: I have installed Rosegarden and QSynth, but still no sound. I have to stop at this point, but will be back tomorrow. Thanx for any helpful words! --doug
On 2021-01-14 08:39, Doug McGarrett wrote:
Addition: I have installed Rosegarden and QSynth, but still no sound. I have to stop at this point, but will be back tomorrow. Thanx for any helpful words! --doug
Hi Doug, There can be a lot of weird problems with linux audio but you probably haven't connected your midi keyboard with Qsynth (actually fluidsynth) through alsaseq. And I take it you use pulseaudio and not jackd, right? It might also be that you haven't installed any soundfonts but lets start with the connections. Start Qsynth and have your keyboard connected and then check with aconnect and paste the response here: aconnect -l -- /bengan
On 1/14/21 3:11 PM, Bengt Gördén wrote:
On 2021-01-14 08:39, Doug McGarrett wrote:
Addition: I have installed Rosegarden and QSynth, but still no sound. I have to stop at this point, but will be back tomorrow. Thanx for any helpful words! --doug
Hi Doug,
There can be a lot of weird problems with linux audio but you probably haven't connected your midi keyboard with Qsynth (actually fluidsynth) through alsaseq. And I take it you use pulseaudio and not jackd, right? It might also be that you haven't installed any soundfonts but lets start with the connections.
Start Qsynth and have your keyboard connected and then check with aconnect and paste the response here:
aconnect -l
doug@linux1:~/Downloads> aconnect -l client 0: 'System' [type=kernel] 0 'Timer ' Connecting To: 128:0 1 'Announce ' Connecting To: 128:0 client 14: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 20: 'E-MU XMidi1X1 Tab' [type=kernel,card=1] 0 'E-MU XMidi1X1 Tab MIDI 1' client 128: 'PipeWire-System' [type=user,pid=1442] 0 'input ' Connected From: 0:1, 0:0 client 129: 'PipeWire-RT-Event' [type=user,pid=1442] 0 'input ' client 130: 'FLUID Synth (7435)' [type=user,pid=7435] 0 'Synth input port (7435:0) There is no sound from keyboard keys. I suspect that I need a "sound font" but I'm having trouble getting one installed. Thanx for responding. This is tricky! --doug
On 2021-01-15 00:44, Doug McGarrett wrote:
doug@linux1:~/Downloads> aconnect -l client 0: 'System' [type=kernel] 0 'Timer ' Connecting To: 128:0 1 'Announce ' Connecting To: 128:0 client 14: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 20: 'E-MU XMidi1X1 Tab' [type=kernel,card=1] 0 'E-MU XMidi1X1 Tab MIDI 1' client 128: 'PipeWire-System' [type=user,pid=1442] 0 'input ' Connected From: 0:1, 0:0 client 129: 'PipeWire-RT-Event' [type=user,pid=1442] 0 'input ' client 130: 'FLUID Synth (7435)' [type=user,pid=7435] 0 'Synth input port (7435:0) There is no sound from keyboard keys. I suspect that I need a "sound font" but I'm having trouble getting one installed. Thanx for responding. This is tricky!
Don't use qjackctl/jack to begin with. It'll get you mostly sorrows if you just want to play your keyboard. I've been doing oss/alsa/jack/pulseaudio in that order since late 90th and to understand linux audio/midi I recommend you to start with pure alsa-midi and not jack-midi. As can be seen from your aconnect -l you seem to have a USB connected MIDI thingy (client 20). I take it that your keyboard is connected via that USB-MIDI thingy. That needs to be connected with fluidsynth (qsynth). You can do that with a GUI like qjackctl but as I said it will probably get you into the realm of jack. Wait with that until you get some sound out of qsynth/fluidsynth. If you have qjackctl running, quit it and see to it that jackd or jackdbus isn't running. ps waux | egrep jack if you have, kill it. Have qsynth started and run aconnect like this (with respect to the above output). If you have disconnected and reconnected a few times the clients tend to get new client numbers, use the new one if that's the case. aconnect 20:0 130:0 If you don't hear any sound check to see if you have a soundfont installed and if not the easiest in opensuse is to install fluid-soundfont-gm. zypper in fluid-soundfont-gm You will then get /usr/share/sounds/sf2/FluidR3_GM.sf2. Point qsynth to that in by going to Setup->Soundfont->Open in qsynth. -- /bengan
On 1/15/21 6:55 PM, Bengt Gördén wrote:
On 2021-01-15 00:44, Doug McGarrett wrote:
doug@linux1:~/Downloads> aconnect -l client 0: 'System' [type=kernel] 0 'Timer ' Connecting To: 128:0 1 'Announce ' Connecting To: 128:0 client 14: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 20: 'E-MU XMidi1X1 Tab' [type=kernel,card=1] 0 'E-MU XMidi1X1 Tab MIDI 1' client 128: 'PipeWire-System' [type=user,pid=1442] 0 'input ' Connected From: 0:1, 0:0 client 129: 'PipeWire-RT-Event' [type=user,pid=1442] 0 'input ' client 130: 'FLUID Synth (7435)' [type=user,pid=7435] 0 'Synth input port (7435:0) There is no sound from keyboard keys. I suspect that I need a "sound font" but I'm having trouble getting one installed. Thanx for responding. This is tricky!
Don't use qjackctl/jack to begin with. It'll get you mostly sorrows if you just want to play your keyboard. I've been doing oss/alsa/jack/pulseaudio in that order since late 90th and to understand linux audio/midi I recommend you to start with pure alsa-midi and not jack-midi.
If you are on tumbleweed you can now use Cadence / Jack over qjackctl / Jack. This will lead to a much better user experience. As a disclaimer I haven't used it with midi yet and I generally use it with a audio interface as a sound card. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On 1/17/21 8:44 PM, Simon Lees wrote:
On 1/15/21 6:55 PM, Bengt Gördén wrote:
doug@linux1:~/Downloads> aconnect -l client 0: 'System' [type=kernel] 0 'Timer ' Connecting To: 128:0 1 'Announce ' Connecting To: 128:0 client 14: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 20: 'E-MU XMidi1X1 Tab' [type=kernel,card=1] 0 'E-MU XMidi1X1 Tab MIDI 1' client 128: 'PipeWire-System' [type=user,pid=1442] 0 'input ' Connected From: 0:1, 0:0 client 129: 'PipeWire-RT-Event' [type=user,pid=1442] 0 'input ' client 130: 'FLUID Synth (7435)' [type=user,pid=7435] 0 'Synth input port (7435:0) There is no sound from keyboard keys. I suspect that I need a "sound font" but I'm having trouble getting one installed. Thanx for responding. This is tricky! Don't use qjackctl/jack to begin with. It'll get you mostly sorrows if you just want to play your keyboard. I've been since late 90th and to understand
On 2021-01-15 00:44, Doug McGarrett wrote: linux audio/midi I recommend you to start with pure alsa-midi and not jack-midi.
If you are on tumbleweed you can now use Cadence / Jack over qjackctl / Jack. This will lead to a much better user experience. As a disclaimer I haven't used it with midi yet and I generally use it with a audio interface as a sound card.
I have been off the (musical) keyboard for a couple of days, but I am still interested in getting this working. Meanwhile, how do I select alsa-midi rather than jack-midi? AFIK, sound on this computer is using pulse audio, not alsa.(Yes, I know that PA uses alsa somehow. I would not like to destroy the ability to play "normal" computer sound, like that from YouTube. Now specifically, "doing oss/alsa/jack/pulseaudio in that order" means what? What, for instance, is oss? I have been keeping copies of all the responses, and I have to try and synchronize them somehow till they make sense to me. Thank you all for your interest! --doug
Hi Doug, As for the jack. I do not want to be a party pooper. My take on jack is that there are many degrees of freedom in Linux audio stack(s) and it can be very difficult to find problems by adding even more degrees. I use jack daily in my studio so I think it is good and very nice. But in the end, it's up to you to choose. But lets just check if your fluidsynth (the software synth used in Qsynth) is up to par with your current setup (pulseaudio) As I said. First install a soundfont. Ex. zypper in fluid-soundfont-gm Grab a midi-file that you have or download some. Ex. wget https://www.mutopiaproject.org/ftp/BeethovenLv/WoO59/fur-elise-guitar-duo/fu... -O ~/Downloads/fur-elise-guitar-duo.mid then run fluidsynth from the command line to see if you got any sound: fluidsynth -a pulseaudio /usr/share/sounds/sf2/FluidR3_GM.sf2 ~/Downloads/fur-elise-guitar-duo.mid stop it on the fluidsynth cli by issue command quit -- /bengan
Hi Doug,
As for the jack. I do not want to be a party pooper. My take on jack is that there are many degrees of freedom in Linux audio stack(s) and it can be very difficult to find problems by adding even more degrees. I use jack daily in my studio so I think it is good and very nice. But in the end, it's up to you to choose.
But lets just check if your fluidsynth (the software synth used in Qsynth) is up to par with your current setup (pulseaudio)
As I said. First install a soundfont. Ex.
zypper in fluid-soundfont-gm
Grab a midi-file that you have or download some. Ex.
wget https://www.mutopiaproject.org/ftp/BeethovenLv/WoO59/fur-elise-guitar-duo/fu... -O ~/Downloads/fur-elise-guitar-duo.mid
then run fluidsynth from the command line to see if you got any sound:
fluidsynth -a pulseaudio /usr/share/sounds/sf2/FluidR3_GM.sf2 ~/Downloads/fur-elise-guitar-duo.mid
stop it on the fluidsynth cli by issue command quit
Thank you for your input. It has problems on my system:
On 1/19/21 7:21 AM, Bengt Gördén wrote: linux1:~ # zypper in fluid-soundfont-gm long paragraph of complaints, ending in "nothing to do" linux1:~ # wget https://www.mutopiaproject.org/ftp/BeethovenLv/WoO59/fur-elise-guitar-duo/fu... -O ~/Downloads/fur-elise-guitar-duo.mid --2021-01-19 14:27:04-- https://www.mutopiaproject.org/ftp/BeethovenLv/WoO59/fur-elise-guitar-duo/fu... apparently worked--no complaint linux1:~ # fluidsynth Warning: Unable to initialize SDL2 Audio: Could not setup connection to PulseAudiofluidsynth: warning: SDL2 not initialized, SDL2 audio driver won't be usable FluidSynth runtime version 2.1.5 Copyright (C) 2000-2020 Peter Hanappe and others. and lots more--no sound at the end of it fluidsynth: Jack sample rate mismatch, adjusting. (synth.sample-rate=44100, jackd=48000) Finally: fluidsynth: Jack sample rate mismatch, adjusting. (synth.sample-rate=44100, jackd=48000) Type 'help' for help topics. linux1:~ # fluidsynth -a pulseaudio /usr/share/sounds/sf2/FluidR3_GM.sf2 ~/Downloads/fur-elise-guitar-duo.mid Warning: Unable to initialize SDL2 Audio: Could not setup connection to PulseAudiofluidsynth: warning: SDL2 not initialized, SDL2 audio driver won't be usable then fluidsynth: error: Failed to create PulseAudio connection Failed to create the audio driver I didn't print this stuff out, but it looks like about three standard pages of output, none of it good! For some reason, I can't copy the rest of the output. My son says I should try Windows, but I'll put the keyboard away before I get into that! --doug
On 2021-01-19 20:53, Doug McGarrett wrote:
fluidsynth: Jack sample rate mismatch, adjusting. (synth.sample-rate=44100, jackd=48000) Finally: fluidsynth: Jack sample rate mismatch, adjusting. (synth.sample-rate=44100, jackd=48000)
Check if you have jack running: ps waux | egrep jack If it's there and working you can try to use it in same manner as pulseaudio with fluidsynth. Just add -j so that the ports will connect in jack. fluidsynth -a jack -j /usr/share/sounds/sf2/FluidR3_GM.sf2 ~/Downloads/fur-elise-guitar-duo.mid -- /bengan
On 1/19/21 4:34 PM, Bengt Gördén wrote:
On 2021-01-19 20:53, Doug McGarrett wrote:
fluidsynth: Jack sample rate mismatch, adjusting. (synth.sample-rate=44100, jackd=48000) Finally: fluidsynth: Jack sample rate mismatch, adjusting. (synth.sample-rate=44100, jackd=48000)
Check if you have jack running:
ps waux | egrep jack
If it's there and working you can try to use it in same manner as pulseaudio with fluidsynth. Just add -j so that the ports will connect in jack.
fluidsynth -a jack -j /usr/share/sounds/sf2/FluidR3_GM.sf2 ~/Downloads/fur-elise-guitar-duo.mid doug@linux1:~> ps waux | egrep jack doug 24390 0.0 0.0 6188 748 pts/1 S+ 18:34 0:00 grep -E --color=auto jack doug@linux1:~> fluidsynth -j FluidSynth runtime version 2.1.5 Copyright (C) 2000-2020 Peter Hanappe and others. Distributed under the LGPL license. SoundFont(R) is a registered trademark of E-mu Systems, Inc.
fluidsynth: Connection of Midi Through Port-0 succeeded fluidsynth: Connection of E-MU XMidi1X1 Tab MIDI 1 succeeded fluidsynth: warning: Failed to set thread to high priority Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jackdmp 1.9.14 And another 30 or 40 lines of complaints! I think I'm missing something very basic or fundamental. There are just too many problems. Is there a package somewhere that installs EVERYTHING? Including libs and repos? --doug
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
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
On 1/20/21 5:13 PM, Doug McGarrett wrote:
On 1/20/21 7:43 AM, Bengt Gördén wrote:
On 2021-01-20 00:40, Doug McGarrett wrote:
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. It looks like that problem does not affect my music problem, except
/snip/ possibly the last line about "some repositories." /snip/ linux1:~ # zypper refresh Repository 'SoftMaker Office Repository' is up to date. Repository 'Packman Repository' is up to date. Repository 'libdvdcss repository' is up to date. Repository 'openSUSE:Tumbleweed' is up to date. 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. Skipping repository 'home:hawkeye116477:waterfox:build-depends' because of the above error. Repository 'openSUSE:Factory' is up to date. Repository 'home:Ledest:bashisms' is up to date. Repository 'home:hawkeye116477:waterfox' is up to date. Repository 'openSUSE-Tumbleweed-Non-Oss' is up to date. Repository 'openSUSE-Tumbleweed-Oss' is up to date. Repository 'openSUSE-Tumbleweed-Update' is up to date. Repository 'skype (stable)' is up to date. Some of the repositories have not been refreshed because of an error. linux1:~ #
On 2021-01-21 01:22, Doug McGarrett wrote:
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. Skipping repository 'home:hawkeye116477:waterfox:build-depends' because of the above error.
Just a small recommendation about repos. You shouldn't have repos like that. It can mess things up. Delete it and re-add if you use it. Check if you have anything installed from it. If not just delete it. It's probably easier for you through the Yast gui. According to your output your waterfox repo has the name/alias home:hawkeye116477:waterfox:build-depends For command line version check whats installed from the repo like this: zypper se -i -r 'home:hawkeye116477:waterfox:build-depends' If you re-add it, it should have this URI: https://download.opensuse.org/repositories/home:/hawkeye116477:/waterfox/ope...
It looks like that problem does not affect my music problem
PS. I'll try to get back on the audio stuff later today or tomorrow. DS. -- /bengan
On 1/21/21 6:03 AM, Bengt Gördén wrote:
On 2021-01-21 01:22, Doug McGarrett wrote:
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. Skipping repository 'home:hawkeye116477:waterfox:build-depends' because of the above error.
Just a small recommendation about repos. You shouldn't have repos like that. It can mess things up. Delete it and re-add if you use it.
Check if you have anything installed from it. If not just delete it. It's probably easier for you through the Yast gui.
According to your output your waterfox repo has the name/alias home:hawkeye116477:waterfox:build-depends
For command line version check whats installed from the repo like this: zypper se -i -r 'home:hawkeye116477:waterfox:build-depends'
If you re-add it, it should have this URI: https://download.opensuse.org/repositories/home:/hawkeye116477:/waterfox/ope...
Ran zypper refresh. Among other lines, got this: 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. How do I delete this? --doug
It looks like that problem does not affect my music problem
PS. I'll try to get back on the audio stuff later today or tomorrow. DS.
On 2021-01-21 20:20, Doug McGarrett wrote:
How do I delete this?
From command line: zypper rr home:hawkeye116477:waterfox:build-depends Or from Yast. You should have it in your start menu. You can start yast and go to repos directly from command line like this: xdg-su -c "/sbin/yast2 repositories" -- /bengan
participants (3)
-
Bengt Gördén -
Doug McGarrett -
Simon Lees