Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm a recent newbie to Slackware. I've also recently joined the choir at my church. Twenty years ago music was an avid hobby of mine, but alas, that was twenty years ago. I want to type my part into rosegarden for various songs we sing, and then have rosegarden play it back to me so that I can rehearse at home. I have typed in my part for one song so far, but there is no sound when I hit the 'play' button. I know I have general sound on this system, as I tested pianobar and mpg123 both before I began typing this message and they both output sound as expected. I am rather embarrassed as I do not know what information you would need to assist me with this particular problem. Some random informational bits that I think would help with this:
What also may be helpful is the version of rosegarden:
Code:
michael@caitlyn ~ $ rosegarden --version
Rosegarden version: 16.02 ("Querida")
Build key: 8b07014380
Built against Qt version: 4.8.7
Code:
michael@caitlyn ~ $ uname -a
Linux caitlyn 4.9.28 #2 SMP Mon May 15 21:56:14 CDT 2017 x86_64 Intel(R) Pentium(R) CPU G3250 @ 3.20GHz GenuineIntel GNU/Linux
And I built it with sbopkg if that matters. I had to install a bunch of other stuff that I don't really remember the names of. Thank you in advance to anyone who can help me to solve this issue.
I'm thinking that I need a MIDI sequencer. On my old distro I used timidity++ (which will not build at this moment.) Is there another way?
Last edited by maschelsea; 05-28-2017 at 05:04 PM.
One of the pieces of software that you'll need is JACK. My experience with JACK is that it immediately disables Pulseaudio, so when I'm finished my music session there is no audio for YouTube and system sounds. My way around that means renaming the .pulse folder to .pulse.old, logging out then logging back in.
For more advanced people who work with DAWs (digital audio workstations) everyday, JACK must be real easy to use, and quite sophisticated in operation. It provides a plug-board-like system to input one audio stream or many audio streams and connect it to a virtual output.
As I said in my video, you'll also need Timidity++, a MIDI server.
One of the pieces of software that you'll need is JACK. My experience with JACK is that it immediately disables Pulseaudio, so when I'm finished my music session there is no audio for YouTube and system sounds. My way around that means renaming the .pulse folder to .pulse.old, logging out then logging back in.
For more advanced people who work with DAWs (digital audio workstations) everyday, JACK must be real easy to use, and quite sophisticated in operation. It provides a plug-board-like system to input one audio stream or many audio streams and connect it to a virtual output.
As I said in my video, you'll also need Timidity++, a MIDI server.
OK. I got timidity++ to build. In your video, you used some kind of gui app to start jack-audio-connection-kit. I don't think I have that. This is what I have:
I have no idea what distro your using in the video, but I am running Slackware. I'm kinda new here, so I don't really know my way around yet. Please advise as to that jack-audio-connection-kit gui app.
Timidity++, but there's also fluidsynth (or qsynth the gui front end to fluidsynth). For midi stuff you need a midi provider like timidity++ OR fluidsynth.
Timidity++, but there's also fluidsynth (or qsynth the gui front end to fluidsynth). For midi stuff you need a midi provider like timidity++ OR fluidsynth.
I've got timidity working. I need the jack-audio-connection-kit to start jack, but I don't know how to get it.
NEW (jackdbus):
$ jack_control ds alsa
$ jack_control eps realtime false
$ jack_control dps device hw:1
$ jack_control dps rate 48000
$ jack_control dps nperiods 3
$ jack_control dps period 512
$ jack_control start
$ pulseaudio --kill
$ pulseaudio --start
(for a pulse over jack configuration, with autospawn=no)
$ qjackctl
(to make sure pulseaudio shows up, otherwise quirky jack_control stop and pulseaudio --kill things to get things moving as intended. Jackdbus will start pulseaudio automagically, but probably too early to bind properly)
Although you might want to use 44100 for midi stuff since a lot of samples are sampled at that rate (CD quality). Performance trick for midi and jackd. Although pulseaudio favors 48000 which is more common to video feeds.
The -n 3 -p 512 would be -n 2 -p 1024 if omitted aka defaults. I tend to have less crackling with -n 3. YMMV.
As far as timidity++, in the days of old I had to recompile alsa $(--with-sequencer=yes) to get that to work. Which wasn't a debian default long ago (pre-wheezy?). Otherwise some odd post boot steps to use snd-seq-oss for roughly the same functionality. Kernel config option $(CONFIG_SND_SEQUENCER=m) which is a distro default for me. Not quite what slackware does, but something to know / look for.
NEW (jackdbus):
$ jack_control ds alsa
$ jack_control eps realtime false
$ jack_control dps device hw:1
$ jack_control dps rate 48000
$ jack_control dps nperiods 3
$ jack_control dps period 512
$ jack_control start
$ pulseaudio --kill
$ pulseaudio --start
(for a pulse over jack configuration, with autospawn=no)
$ qjackctl
(to make sure pulseaudio shows up, otherwise quirky jack_control stop and pulseaudio --kill things to get things moving as intended. Jackdbus will start pulseaudio automagically, but probably too early to bind properly)
Although you might want to use 44100 for midi stuff since a lot of samples are sampled at that rate (CD quality). Performance trick for midi and jackd. Although pulseaudio favors 48000 which is more common to video feeds.
Lots of options, some harder to setup than others. And most probably NOT distro defaults.
I don't have jackdbus, but I DO have jackd:
Code:
root@caitlyn:~# jackd -r -d alsa -d hw:1 -r 48000 -n 3 -p 512
jackd 0.124.1
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 48000
creating alsa driver ... hw:1|hw:1|512|3|48000|0|0|nomon|swmeter|-|32bit
ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode
cannot load driver module alsa
root@caitlyn:~#
So which alsa module does it want? I can rebuild kernels. I just need to know which alsa I need to turn from 'y' to 'm'. The only one that's not already 'm' is the CONFIG_THINKPAD_ACPI_SUPPORT, and I don't think it's that one...
And then try without the -r, and omit the last parm(s) until it works. Just jackd without parms should work although the assumed defaults might not yield desired results. Especially since computers have multiple soundcards now. One on the motherboard, video card, webcam, and on and on. In general the one with index 0 is default until "customized" via pulseaudio or $HOME/.asoundrc or other methods.
root@caitlyn:~# jackd -d alsa -d hw:0 -r 48000 -n 3 -p 512
jackd 0.124.1
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 48000
creating alsa driver ... hw:0|hw:0|512|3|48000|0|0|nomon|swmeter|-|32bit
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /home/michael/.gvfs
Output information may be incomplete.
ATTENTION: The playback device "hw:0" is already in use. Please stop the application using it and run JACK again
cannot load driver module alsa
root@caitlyn:~#
As you can see, jackd won't start. Something is using hw:0. I tried to look at lsof, but couldn't make out what any of those numbers meant. Maybe tomorrow I can look up how to interpret the lsof output, but for tonight, I don't have the time or the concentration to manage it.
And then try without the -r, and omit the last parm(s) until it works. Just jackd without parms should work although the assumed defaults might not yield desired results. Especially since computers have multiple soundcards now. One on the motherboard, video card, webcam, and on and on. In general the one with index 0 is default until "customized" via pulseaudio or $HOME/.asoundrc or other methods.
Already in use is probably pulseaudio. Depending on your distro.
$ grep -i autospawn /etc/pulse/client.conf
If you change that to "autospawn = no", you can stop pulseaudio.
$ pulseaudio --kill
And with a pulse over jack setup you can restart it $(pulseaudio --start), after starting jackd. Without the autospawn=no, the init system will by default restart pulseaudio. Various other routes with snd-aloop plus other tricks.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.