[Rosegarden-user] Please help: no sound 11.11.42-51.17 & earlier [suse 12.x & kDE]
Hello, I'm new to rosegarden (11.11.42-51.17) & cannot for the life of me get any sound out of it! Have tried earlier rosegarden versions too. Fluyidsynth & qsynth are installed, soundfonts too. Jack/qjackctl are installed (sofar not used) I load a midi file into rosegarden just to test sound and try to play it, it plays but no sound. Looking for a real good step by step tutorial not about composing music but about settin it up so that it can be heard. Thanks -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
Re: [Rosegarden-user] Please help: no sound 11.11.42-51.17 & earlier [suse 12.x & kDE]
On Sat, 25 Aug 2012 13:17:19 -0700 (PDT) "Gary G." wrote: > Here's a quick youtube tutorial on how to set things up. > > http://www.youtube.com/watch?v=tNdXdWoHU0w > > Reply to the list if this doesn't help Thanks but even that one is way ahead of my game. For one thing I don't have a real syth, I just want to compose some music and hear the notes while doing it or hear the whol etune when done. Or, I may want to import a midi file and hear that. I tried to follow the video but none of my rosegarden behaved the way it's shown there. My problem is getting rosegarden to make any sound at all under any circumstance. OpenSuse-12.1 or 12.2 KDE4 Some soundfonts & fluidsynth are installed This works, I can hear the midi: fluidsynth -a alsa -l /0/sa14/comp/build-common/music/sf2-filez/Unison.sf2 /0/sa14/guitar/midi/mmp.mid Qsynth is installed Jack is installed Qjackctl is installed if I try to start it I get 21:26:58.690 Patchbay deactivated. 21:26:58.692 Statistics reset. 21:26:58.693 ALSA connection change. 21:26:58.696 JACK is starting... 21:26:58.697 /usr/bin/jackd -v -dalsa -dhw:0 -r48000 -p1024 -n2 -H 21:26:58.700 ALSA connection graph change. 21:26:58.700 JACK was started with PID=4977. 21:27:05.903 Could not connect to JACK server as client. - Overall operation failed. - Server communication error. Please check the messages window for more info. 21:27:05.972 JACK was stopped successfully. 21:27:05.973 JACK has crashed. but when Rosegarden starts, it starts JACK OK 21:28:15.941 Patchbay deactivated. 21:28:15.943 Statistics reset. 21:28:15.944 ALSA connection change. 21:28:15.983 JACK connection change. 21:28:16.000 Client activated. PluseAudio is so hard wired into KDE that I cannot uninstall it While trying to find my way in the ncurses also mixer sliders I lost all sound and had to recover the entire partition from a backup. If I try Qjackctl with server path: pasuspender --jackd on launch it gives 21:53:56.441 Patchbay deactivated. 21:53:56.443 Statistics reset. 21:53:56.444 ALSA connection change. 21:53:56.448 ALSA connection graph change. when I click Start it continues with 21:56:02.022 JACK is starting... 21:56:02.022 /usr/bin/pasuspender --jackd -v -dalsa -dhw:0 -r48000 -p1024 -n2 -H 21:56:02.025 JACK was started with PID=5731. 21:56:02.027 JACK was stopped with exit status=1. 21:56:04.065 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info. Here's a few pokes pactl list sources short 0 alsa_output.pci-_05_00.1.hdmi-stereo.monitor module-alsa-card.c s16le 2ch 44100Hz SUSPENDED 1 alsa_output.pci-_00_14.2.analog-stereo.monitor m odule-alsa-card.c s16le 2ch 44100Hz IDLE 2 alsa_input.pci-_00_14.2.analog-stereo module-alsa-card.c s16le 2ch 44100Hz SUSPENDED 4 alsa_input.usb-FMIC_Mustang_Amplifier_AF98FF303235423 157216139-02-Amplifier.analog-stereo module-alsa-card.c s16le 2ch 44100Hz SUSP 0 alsa_output.pci-_05_00.1.hdmi-stereo module-alsa-card.c s16le 2ch 44100Hz SUSPENDED 1 alsa_output.pci-_00_14.2.analog-stereo module-alsa-card.c s16le 2ch 44100Hz RUNNING All of the above is chinese to me but I can follow step by step guides. I've never seen a more uncooperative application :-) -- > > All The World's A Stage > > http://soundcloud.com/happyrat1 > > > > > --- On Sun, 8/26/12, k...@trixtar.org wrote: > > > From: k...@trixtar.org > > Subject: [Rosegarden-user] Please help: no sound 11.11.42-51.17 & earlier > > [suse 12.x & kDE] > > To: rosegarden-user@lists.sourceforge.net > > Date: Sunday, August 26, 2012, 11:57 AM > > > > Hello, > > > > I'm new to rosegarden (11.11.42-51.17) & cannot for > > the life of me get any sound out of it! Have tried > > earlier rosegarden versions too. > > > > Fluyidsynth & qsynth are installed, soundfonts too. > > > > Jack/qjackctl are installed (sofar not used) > > > > I load a midi file into rosegarden just to test sound > > and try to play it, it plays but no sound. Looking for > > a real good step by step tutorial not about composing > > music but about settin it up so that it can be heard. > > > > Thanks -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint securi
Re: [Rosegarden-user] Please help: no sound 11.11.42-51.17 & earlier [suse 12.x & kDE]
Assuming you are running JACK, in Suse, the connections from the your software synth to ALSA through JACK are not made automatically. Using qjackctl, you will want to make sure there is a connection from whatever soft synth you are using to ALSA (may be labeled system but it is the same thing). Dave On 8/26/12 11:57 AM, k...@trixtar.org wrote: > Hello, > > I'm new to rosegarden (11.11.42-51.17) & cannot for > the life of me get any sound out of it! Have tried > earlier rosegarden versions too. > > Fluyidsynth & qsynth are installed, soundfonts too. > > Jack/qjackctl are installed (sofar not used) > > I load a midi file into rosegarden just to test sound > and try to play it, it plays but no sound. Looking for > a real good step by step tutorial not about composing > music but about settin it up so that it can be heard. > > Thanks > > > -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > ___ > Rosegarden-user mailing list > Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe > https://lists.sourceforge.net/lists/listinfo/rosegarden-user > -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
Re: [Rosegarden-user] Please help: no sound 11.11.42-51.17 & earlier [suse 12.x & kDE]
On Sun, 26 Aug 2012, k...@trixtar.org wrote:
> All of the above is chinese to me but I can follow step by
> step guides. I've never seen a more uncooperative
> application :-)
Perhaps the problems aren't "uncooperative application" but because of
"uncooperative distribution", or
"uncooperative setup/configuration", or
"uncooperative user" :-)
Most common Linux distros are not MIDI friendly. Getting Linux MIDI setup
involves many configuration steps, orders of apps to start, as well as "audio
connections", and "midi connections" properly in connected.
I don't use SUSE, nor KDE, nor GNOME for that mater. Different Linux distros
do things differently, so I can't tell you step-by-step how to do things under
SUSE, let alone some particular version of SUSE. Even with Debian, I use
Debian Unstable/Sid, which is a lot different than Debian Testing, or Debian
Stable.
I also read just enough to stay away as far as I can from PulseAudio.
especially with low-latency usage of MIDI. You can try to configure
"PulseAudio" daemon to not automatically start, as well as configure KDE to use
"Alsa" for audio. That's right, if the distribution won't uninstall it. just
tell it not to run PulseAudio. Although, you may have to reconfigure many apps
to use Jack, or Alsa, or default audio output.
Fastest way to see it all working on your particular computer is to download a
liveCD of one of these distro: Musix, Studio64, Dynebolic, "Ubuntu Studio" (not
"Ubuntu", or "Kubuntu"). Boot up with one of those liveCD to try it out, if
you like it, install it in a separate disk partition to have it run faster.
Once you see it running, you can inspect the configurations and settings to see
how they all fit together. The order of things I would look at are:
Get rid of PulseAudio (just my preference to use ALSA).
Get jackd/qjackctl running with low-latency configuration.
Get fluidsynth to start using "jack" audio output ("-a jack"), not Alsa
audio output ("-a alsa"). Make sure to connect fluidsynth audio output to jack
audio "system" input port. Or, use the "-j" option of fluidsynth to do this
automatically.
Optionally use "Alsa Midi through", by loading "snd_seq_midi" kernel module,
connect Alsa Midi output port "14:Midi through" to Alsa Midi input port of
"FLUID synth"
Use "aplaymidi -p 14 /path/to/some/midi-song.mid" to play via the "14:Midi
through".
Start Rosegarden, and connect rosegarden "Alsa midi" output port to
fluidsynth "Alsa midi" input port.
I know each of those step require quite a few things in place. Those thing may
change slightly from version to version of the kernel, and of each application.
So, most instructions out there are almost always outdated. But if you learn
and understand how they fit together, you can get it done in any Linux
distribution, given that you have the the proper kernel, as well as time to do
the full configuration.
Yes, you can install all of those liveCD's on the same hard drive, each in its
own separate logical disk partition, along with whatever else you are using
currently. That's the beauty of Linux, if you have the diskspace and know
enough not to mess up and wipe out your hard drive in the process.
If you are not comfortable and don't know yet what you are doing, I suggest you
use a spare computer, and a spare hard drive to learn, meanwhile unplug the
current hard drive from that computer so you don't accidentally wipe out your
data.
Personally, I recommend Musix liveCD because it use Debian, I learned much from
Musix LiveCD a full decade ago. Yes, I spent months and months trying to get
Linux MIDI to work until I tried Musix liveCD. Yes, after trying Musix liveCD,
it took me weeks, and months to fully understand how all the apps fit together
with jackd binding things together.
Don't try to use MIDI apps without jack in Linux, some of those older apps may
work directly with Alsa. But in the long run, you will more likely need
jackd/qjackctl.
Precompiled low-latency enabled kernel for Debian, with fairly up-to-date
kernel version is available in Debian-based distros like aptosid, sidux,
siduction.
Yeah, I know much of what are wrote are all "geek" for the Linux MIDI newbies.
But if you really want to get Linux MIDI to run, you have to learn it. I
already tell you where to start, hint: Musix liveCD. I'm not related, or
involved with the Musix liveCD folks, just learned alot, and much appreciated
their work in the early days. Good luck,
Jimmy
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Re: [Rosegarden-user] Please help: no sound > 11.11.42-51.17 & earlier [suse 12.x & kDE]
On Sun, 26 Aug 2012, k...@trixtar.org wrote: > > OpenSuse-12.1 or 12.2 > KDE4 > > Some soundfonts & fluidsynth are installed > This works, I can hear the midi: > fluidsynth -a alsa -l > /0/sa14/comp/build-common/music/sf2-filez/Unison.sf2 > /0/sa14/guitar/midi/mmp.mid At least you have some MIDI sound. The problem is that command tells Fluidsynth to use "Alsa audio", which locks "Alsa audio" in exclusive mode, and Jackd (Qjackctl) can't access the "Alsa audio" for audio output. Here's my Fluidsynth command: fluidsynth -a jack -j -r 44100 -g 0.40 -o synth.midi-bank-select=xg /full-path-to/soundfonts/Unison.sf2 you can skip the "-o synth.midi-bank-select=xg", if you don't care about Yamaha XG midi stuff. Note the "-a jack" tells Fluidsynth to use "Jackd audio" output instead of "Alsa audio". So you need to have jackd already running, or if you use Qjackctl you need to have jackd started within Qjackctl. After I have qjackctl started jackd, I can get the full command by looking at the output of: ps -ef | grep jackd | grep -v grep and that command starts from the /usr/bin/jackd, until the end of that output text line. Once you get all the parameters selected as you want in qjackctl, the command to start jackd may be helpful if you want to use the commandline instead of qjackctl. Anyway, once you have both qjackctl and fluidsynth started, click on "Connect" button of qjackctl. Within the qjackctl connection window, The "Audio" tab is the "jackd audio" (not "Alsa audio") connections. The "MIDI" tab is for "jack MIDI" connections. The "ALSA" tab is for "Alsa MIDI" connections. Select "Audio" tab, make sure fluidsynth is connected to "system". Select "ALSA" tab, select "14:Midi through" on the left list (output ports), select "Fluid synth" on the right list (input ports), click on "Connect" button within that qjackctl connection window. This is the If you don't see "14:Midi through", you may need to load some kernel modules into memory with the modprobe command. Here are my midi kernal modules loaded: lsmod | grep -i midi snd_seq_midi3592 0 snd_rawmidi12701 1 snd_seq_midi snd_seq_midi_event 3620 2 snd_seq_oss,snd_seq_midi snd_seq35462 11 snd_seq_midi_event,snd_seq_oss,snd_seq_dummy,snd_seq_midi snd_seq_device 3969 5 snd_seq,snd_rawmidi,snd_seq_oss,snd_seq_dummy,snd_seq_midi I don't remember which one is the one that shows up as "14:Midi through", I believe it is snd_seq_midi, but I could be wrong. The "Audio" tab selection above is automatically connected by the "-j" option of the fluidsynth command. If you use fluidsynth without the "-j" option, you will need to manually connect it to the "jack audio" output to hear any sound using jackd. The "ALSA" tab selection above is connect the virtual midi-through port to the fluidsynth "Alsa MIDI" input port. Now you can test play a midi file with: aplaymidi -p 14 /full-path-to/some-midifile.mid the "-p 14" option of aplaymidi tells it to send "Alsa MIDI" output to port 14, which is the same as the "virtual midi-through port" shown in qjackctl connection window under "ALSA tab". Again, the order of apps that need to get started are: jackd (manually, or via qjackctl) fluidsynth using "jack audio" output, not "Alsa audio" output (manually, or via qsynth), make sure to specify a GM soundfont file within fluidsynt, or qsynth. connect both "jack audio", and "alsa MIDI" connections. play a sample midi file with aplaymidi. Once you get all tha working, you should have at least a vague idea of the difference between "jack audio" vs "Alsa audio", as well as some idea about "Alsa MIDI" connection. Now you can try to start Rosegarden, then try to connect the first rosegarden "Alsa MIDI" output port to "FLUID synth" directly, or connect rosegarfen "Alsa MIDI" output port to "14:Midi through", and "14:Midi through" to "FLUID synth". > PluseAudio is so hard wired into KDE that I cannot uninstall > it > While trying to find my way in the ncurses also mixer > sliders I lost > all sound and had to recover the entire partition from a > backup. I don't use PulseAudio at all, so I don't know for sure if it can cause problem, but I have heard plenty, so I stay away from it. > > If I try Qjackctl with server path: pasuspender --jackd > > on launch it gives > 21:53:56.441 Patchbay deactivated. > 21:53:56.443 Statistics reset. > 21:53:56.444 ALSA connection change. > 21:53:56.448 ALSA connection graph > change. > > when I click Start it continues with > 21:56:02.022 JACK is starting... > 21:56:02.022 /usr/bin/pasuspender --jackd > -v -dalsa -dhw:0 -r48000 -p1024 -n2 -H > 21:56:02.025 JACK was started with > PID=5731. > 21:56:02.027 JACK was stopped with exit > status=1. > 21:56:04.065 Could not connect to JACK > server as client. - > Overall operation failed. - Unable to > connect to
Re: [Rosegarden-user] Please help: no sound > 11.11.42-51.17 & earlier [suse 12.x & kDE]
On Sun, 26 Aug 2012 08:41:53 -0700 (PDT) jimmy <> wrote: Thank you VERY MUCH for the time you took in two replies! I got some good work done as a result, also booted Musix-2.0-Live for an initial looksee. First I killed pulse (possible via Yast the Suse system manager) which I guess means that the entire system uses just alsa --- Next I tried my only old-reliable fluidsynth -a alsa -l /0/sa14/comp/build-common/music/sf2-filez/Unison.sf2 /0/sa14/guitar/midi/mmp.mid FluidSynth version 1.1.4 Copyright (C) 2000-2011 Peter Hanappe and others. Distributed under the LGPL license. SoundFont(R) is a registered trademark of E-mu Systems, Inc. fluidsynth: warning: Failed to pin the sample data to RAM; swapping is possible. fluidsynth: warning: Ignoring sample *KPianoB5: can't use ROM samples fluidsynth: warning: Requested a period size of 64, got 940 instead Type 'help' for help topics. > fluidsynth: warning: Failed to set thread to high priority fluidsynth: warning: /home/abuild/rpmbuild/BUILD/fluidsynth-1.1.4/ src/midi/fluid_midi.c: 1468: Loading midifile /0/sa14/guitar/midi/mmp.mid It still plays though weakly Tried to start jackd via qjackctl it crashed Launched Rosegarden which launched jackd & then I spied ps -ef | grep jackd | grep -v grep u3 2765 1 0 19:31 ? 00:00:00 /usr/bin/jackd -T -ndefault -v -m -ddummy -r48000 -p1024 which I suppose is how Rosegarden got it going so I tried that from CLI and also input it into qjackctl as 'ServerPath' /usr/bin/jackd -T -ndefault -v -m -ddummy -r48000 -p1024 Now I can start jack from command or with qjackctl --- So, with jack already RUNNING fluidsynth -a jack -j -r 44100 -g 0.40 -o synth.midi-bank-select=xg /0/sa14/comp/build-common/music/sf2-filez/Unison.sf2 All qjackctl connections as per yours verified OK: AUDIO tab: fluidsynth L/R connected to Sys. Plauyback 1/2 MIDI tab: 0:Midi through Port-0 connected to 0:synth input port (3922:0) aplaymidi -p 14 /0/sa14/guitar/midi/mmp.mid It plays because there are no errors and it stops after a while, BUT no sound! --- Start Rosegarden Load above midi file Segment Params: Label: Acoustic Grand Piano (unchanged) Playback params: Device: Synth plugin Inst: #1 (FluidSynth DSSI) Instrument Params: Synth plugin #1 Fluidsynth-DSSI Out: Master VOL knob=100, slider=100 Segment 1 Synth plugin #1 fluidsynth-dss Kmix is set to card: HDA ATI SB channell: Master Playing midi, no sound Notes in rosegarden editor, no sound --- > > > > OpenSuse-12.1 or 12.2 > > KDE4 > > > > Some soundfonts & fluidsynth are installed > > This works, I can hear the midi: > > fluidsynth -a alsa -l > > /0/sa14/comp/build-common/music/sf2-filez/Unison.sf2 > > /0/sa14/guitar/midi/mmp.mid > > > At least you have some MIDI sound. The problem is that command tells > Fluidsynth to use "Alsa audio", which locks "Alsa audio" in exclusive mode, > and Jackd (Qjackctl) can't access the "Alsa audio" for audio output. > > Here's my Fluidsynth command: > >fluidsynth -a jack -j -r 44100 -g 0.40 -o synth.midi-bank-select=xg > /full-path-to/soundfonts/Unison.sf2 > > you can skip the "-o synth.midi-bank-select=xg", if you don't care about > Yamaha XG midi stuff. > > Note the "-a jack" tells Fluidsynth to use "Jackd audio" output instead of > "Alsa audio". So you need to have jackd already running, or if you use > Qjackctl you need to have jackd started within Qjackctl. > > After I have qjackctl started jackd, I can get the full command by looking at > the output of: > >ps -ef | grep jackd | grep -v grep > > and that command starts from the /usr/bin/jackd, until the end of that output > text line. Once you get all the parameters selected as you want in qjackctl, > the command to start jackd may be helpful if you want to use the commandline > instead of qjackctl. > > Anyway, once you have both qjackctl and fluidsynth started, click on > "Connect" button of qjackctl. Within the qjackctl connection window, The > "Audio" tab is the "jackd audio" (not "Alsa audio") connections. The "MIDI" > tab is for "jack MIDI" connections. The "ALSA" tab is for "Alsa MIDI" > connections. > >Select "Audio" tab, make sure fluidsynth is connected to "system". > >Select "ALSA" tab, select "14:Midi through" on the left list (output > ports), select "Fluid synth" on the right list (input ports), click on > "Connect" button within that qjackctl connection window. This is the > > If you don't see "14:Midi through", you may need to load some kernel modules > into memory with the modprobe command. Here are my midi kernal modules > loaded: > >lsmod
Re: [Rosegarden-user] Please help: no sound > 11.11.42-51.17 & earlier [suse 12.x & kDE]
My Personal favorite synth is zynaddsubfx. Check it out and see how it works in suse 12.1. Don't forget to make sure it is connected to the system in jack On 8/27/12 8:57 PM, k...@trixtar.org wrote: > On Sun, 26 Aug 2012 08:41:53 -0700 (PDT) > jimmy <> wrote: > > Thank you VERY MUCH for the time you took in two replies! > > I got some good work done as a result, also booted Musix-2.0-Live for an > initial looksee. > > First I killed pulse (possible via Yast the Suse system manager) which I > guess means that the entire system uses just alsa > > > --- > > Next I tried my only old-reliable > > fluidsynth -a alsa -l /0/sa14/comp/build-common/music/sf2-filez/Unison.sf2 > /0/sa14/guitar/midi/mmp.mid > >FluidSynth version 1.1.4 >Copyright (C) 2000-2011 Peter Hanappe and others. >Distributed under the LGPL license. >SoundFont(R) is a registered trademark of E-mu Systems, Inc. >fluidsynth: warning: Failed to pin the sample data to RAM; swapping is > possible. >fluidsynth: warning: Ignoring sample *KPianoB5: can't use ROM samples >fluidsynth: warning: Requested a period size of 64, got 940 instead >Type 'help' for help topics. >> fluidsynth: warning: Failed to set thread to high priority >fluidsynth: warning: /home/abuild/rpmbuild/BUILD/fluidsynth-1.1.4/ >src/midi/fluid_midi.c: 1468: Loading midifile > /0/sa14/guitar/midi/mmp.mid > > It still plays though weakly > > > > Tried to start jackd via qjackctl it crashed > > Launched Rosegarden which launched jackd & then I spied > >ps -ef | grep jackd | grep -v grep > >u3 2765 1 0 19:31 ? 00:00:00 /usr/bin/jackd -T -ndefault -v -m -ddummy > -r48000 -p1024 > > which I suppose is how Rosegarden got it going > > so I tried that from CLI and also input it into qjackctl as 'ServerPath' > >/usr/bin/jackd -T -ndefault -v -m -ddummy -r48000 -p1024 > > Now I can start jack from command or with qjackctl > --- > > > > So, with jack already RUNNING > > fluidsynth -a jack -j -r 44100 -g 0.40 -o synth.midi-bank-select=xg > /0/sa14/comp/build-common/music/sf2-filez/Unison.sf2 > > All qjackctl connections as per yours verified OK: > >AUDIO tab: fluidsynth L/R connected to Sys. Plauyback 1/2 >MIDI tab: 0:Midi through Port-0 connected to 0:synth input port (3922:0) > >aplaymidi -p 14 /0/sa14/guitar/midi/mmp.mid > > It plays because there are no errors and it stops after a while, BUT no sound! > --- > > > > > Start Rosegarden > Load above midi file > > Segment Params: Label: Acoustic Grand Piano (unchanged) > Playback params: >Device: Synth plugin >Inst: #1 (FluidSynth DSSI) > Instrument Params: >Synth plugin #1 >Fluidsynth-DSSI >Out: Master >VOL knob=100, slider=100 > Segment 1 Synth plugin #1 fluidsynth-dss > > Kmix is set to >card: HDA ATI SB >channell: Master > > Playing midi, no sound > Notes in rosegarden editor, no sound > --- > > > > > > > > >>> OpenSuse-12.1 or 12.2 >>> KDE4 >>> >>> Some soundfonts & fluidsynth are installed >>> This works, I can hear the midi: >>>fluidsynth -a alsa -l >>> /0/sa14/comp/build-common/music/sf2-filez/Unison.sf2 >>> /0/sa14/guitar/midi/mmp.mid >> >> At least you have some MIDI sound. The problem is that command tells >> Fluidsynth to use "Alsa audio", which locks "Alsa audio" in exclusive mode, >> and Jackd (Qjackctl) can't access the "Alsa audio" for audio output. >> >> Here's my Fluidsynth command: >> >> fluidsynth -a jack -j -r 44100 -g 0.40 -o synth.midi-bank-select=xg >> /full-path-to/soundfonts/Unison.sf2 >> >> you can skip the "-o synth.midi-bank-select=xg", if you don't care about >> Yamaha XG midi stuff. >> >> Note the "-a jack" tells Fluidsynth to use "Jackd audio" output instead of >> "Alsa audio". So you need to have jackd already running, or if you use >> Qjackctl you need to have jackd started within Qjackctl. >> >> After I have qjackctl started jackd, I can get the full command by looking >> at the output of: >> >> ps -ef | grep jackd | grep -v grep >> >> and that command starts from the /usr/bin/jackd, until the end of that >> output text line. Once you get all the parameters selected as you want in >> qjackctl, the command to start jackd may be helpful if you want to use the >> commandline instead of qjackctl. >> >> Anyway, once you have both qjackctl and fluidsynth started, click on >> "Connect" button of qjackctl. Within the qjackctl connection window, The >> "Audio" tab is the "jackd audio" (not "Alsa audio") connections. The "MIDI" >> tab is for "jack MIDI" connections. The "ALSA" tab is for "Alsa MIDI" >> connections. >> >> Select "Audio" tab, make sure fluidsynth is connected to "s
Re: [Rosegarden-user] Please help: no sound 11.11.42-51.17 & earlier [suse 12.x & kDE]
On Mon, 27 Aug 2012, k...@trixtar.org wrote > I got some good work done as a result, also booted Musix-2.0-Live for an > initial looksee. Did you get any midi sound to play with it? If there's any problem, it would more likely be the jackd, and related connections to get MIDI sounds. I sugest trying the following while you run the Musix liveCD. It is a Debian-based distro, last I checked, and has low-latency kernel as well as related low-latency, realtime priority configuration done in that environment. > First I killed pulse (possible via Yast the Suse system > manager) which I guess means that the entire system uses > just alsa With many Linux distros, there is a soft-link in /etc/rc5.d/ , or /etc/rc3.d/ pointing to the daemon script in /etc/init.d/ Rename the PulseAudio link in /etc/rc5.d/ that has the "S" as the starting character to start with "K" as the starting character. It will prevent that script from starting the daemon at startup. > > > Next I tried my only old-reliable > > fluidsynth -a alsa -l > /0/sa14/comp/build-common/music/sf2-filez/Unison.sf2 > /0/sa14/guitar/midi/mmp.mid > > FluidSynth version 1.1.4 > Copyright (C) 2000-2011 Peter Hanappe > and others. > Distributed under the LGPL license. > SoundFont(R) is a registered trademark > of E-mu Systems, Inc. > fluidsynth: warning: Failed to pin the > sample data to RAM; swapping is possible. > fluidsynth: warning: Ignoring sample > *KPianoB5: can't use ROM samples > fluidsynth: warning: Requested a period > size of 64, got 940 instead > Type 'help' for help topics. > > fluidsynth: warning: Failed to set > thread to high priority > fluidsynth: warning: > /home/abuild/rpmbuild/BUILD/fluidsynth-1.1.4/ > src/midi/fluid_midi.c: 1468: Loading > midifile /0/sa14/guitar/midi/mmp.mid > > It still plays though weakly Play with the fluidsynth "-g 0.40" or something between 0.0-5.0 to see if you can get a louder sound. The period size, and thread priority is probably relating to "low-latency" kernel. With low-latency kernel, the output of: zcat /proc/config.gz | grep -i config_hz should show at least: CONFIG_HZ_1000=y CONFIG_HZ=1000 If you dont have these configs lines, you will want to hunt down a "low-latency" kernel for your distro. Once you have a low-latency kernel, check related configuration in: /etc/security.d/limits.conf , or /etc/security/limits.d/audio.conf which might be configurable by the package manager when installing jack2 package. You use SUSE, I don't know if it can be done there. With Debian, it can be done with: dpkg-reconfigure jackd2 > > > > Tried to start jackd via qjackctl it crashed > > Launched Rosegarden which launched jackd & then I spied > > ps -ef | grep jackd | grep -v grep > > u3 2765 1 0 19:31 ? 00:00:00 > /usr/bin/jackd -T -ndefault -v -m -ddummy -r48000 -p1024 > > which I suppose is how Rosegarden got it going Rosegarden default may get jackd going, but may not be a reasonably good value for your audio card. What you may want to do is play around with qjackctl instead. My Qjackctl only have 2 things selection: No memory lock Soft mode Frames per period: 256 Frames rate: 44100 Frames/Buffer: 2 (frames per buffer) Timeout (msec): 2000 (2 seconds) Driver: alsa MIDI driver: none (you can also try "seq") everything else is not selected, or using default value. The "latency" value shownw at the bottom right corner of the qjackctl setup window is "11.6 msec", which is tolerable for playing midi keyboard alongside some audio, or midi music. Smaller latency value is more "responsive", larger latency means pressing a keyboard key down and you won't hear that note for a while, that's not good for MIDI live performance. > > so I tried that from CLI and also input it into qjackctl as > 'ServerPath' > > /usr/bin/jackd -T -ndefault -v -m -ddummy -r48000 > -p1024 > > Now I can start jack from command or with qjackctl > --- > > > > So, with jack already RUNNING > >fluidsynth -a jack -j -r 44100 -g 0.40 -o > synth.midi-bank-select=xg > /0/sa14/comp/build-common/music/sf2-filez/Unison.sf2 > Note the jackd option "-r48000" and fluidsynth "-r 44100" are mismatched rates. You should specify the same rate for both as either 48000, or 44100. Although, it is not a problem, these 2 apps will adjust and/or resample dynamically, but not an optimal situation. > All qjackctl connections as per yours verified OK: > > AUDIO tab: fluidsynth L/R connected to Sys. > Plauyback 1/2 > MIDI tab: 0:Midi through > Port-0 connected to 0:synth input port (3922:0) > > aplaymidi -p 14 /0/sa14/guitar/midi/mmp.mid > > It pl
Re: [Rosegarden-user] Please help: no sound > 11.11.42-51.17 & earlier [suse 12.x & kDE]
On 08/27/2012 02:57 PM, k...@trixtar.org wrote: > On Sun, 26 Aug 2012 08:41:53 -0700 (PDT) > jimmy<> wrote: > > I got some good work done as a result, also booted Musix-2.0-Live for an > initial looksee. Please note that there is a Musix 3.0 beta or two available. I have it running on my effects box laptop and it seems to work quite well. -- David gn...@hawaii.rr.com authenticity, honesty, community http://clanjones.org/david/ http://dancing-treefrog.deviantart.com/ -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
Re: [Rosegarden-user] Please help: no sound 11.11.42-51.17 & earlier [suse 12.x & kDE]
> Once you have a low-latency kernel, check related > configuration in: > > /etc/security.d/limits.conf , or > > /etc/security/limits.d/audio.conf > Oops, I meant: /etc/security/limits.conf , or /etc/security/limits.d/audio.conf Mine had at least: @audio - rtprio 70 @audio - memlockunlimited @audio - nice -10 it means your userid, which start jackd, needs to belong to the groupid called "audio". I think in Debian, the "/etc/security/limits.d/audio.conf" portion is done by the package manager when jackd2 is configured to use realtime priority. But you need to check the userid that starts up jackd belongs to the audio group. The command "groups" should list all the groupid's that the current user belongs to. This is the "low-latency" configuration portion of a pre-compiled low-latency kernel. You can check to see similar configuration done within the Musix liveCD environment. Again, once you understand all the numerous steps and things which need to be in placed, you can configure any Linux distro to do similar thing, but each distro may have done things slightly different. If any of those are out of placed, you may not get Linux MIDI to work, or may have numerous problems like no sound, latency (out of sync, long delayed note) issues, skipped notes... Jimmy -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
Re: [Rosegarden-user] Please help: no sound 11.11.42-51.17 & earlier [suse 12.x & kDE]
On Mon, 27 Aug 2012 03:53:09 -0700 (PDT) jimmy <> wrote: > > Once you have a low-latency kernel, check related > > configuration in: >/etc/security/limits.conf , or all commented out >/etc/security/limits.d/audio.conf don't have that one > Mine had at least: > > @audio - rtprio 70 > @audio - memlockunlimited > @audio - nice -10 > > > it means your userid, which start jackd, needs to belong to the groupid > called "audio". > > I think in Debian, the "/etc/security/limits.d/audio.conf" portion is done by > the package manager when jackd2 is configured to use realtime priority. But > you need to check the userid that starts up jackd belongs to the audio group. > The command "groups" should list all the groupid's that the current user > belongs to. > > This is the "low-latency" configuration portion of a pre-compiled low-latency > kernel. > > You can check to see similar configuration done within the Musix liveCD > environment. > > Again, once you understand all the numerous steps and things which need to be > in placed, you can configure any Linux distro to do similar thing, but each > distro may have done things slightly different. If any of those are out of > placed, you may not get Linux MIDI to work, or may have numerous problems > like no sound, latency (out of sync, long delayed note) issues, skipped > notes... > > Jimmy I tried Musix-2.0 live and installed it when rosegarden just plain worked out of the box, also installed Ubuntu-Studio but haven't tested it yet, seems promising. 64studio bombed on reboot twice so something in that one is broke, anyway with the other two I should be OK. So thanks for you help one more time. I'll probably back later with small stuff because unless I move to Debian full time I will still want to set up Suse like a studio. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
