i have rosegarden, and everything works fine, except that there is no sound when I try to play something back. i checked the configuration, and it says that MIDI works fine with the sequencer, but not audio. sound works for everything else on my computer. i have an integrated sound card.

any help is greatly appreciated.

if your soundcard can't do midi then i guess you have to use timidity or iiwusynth or some other midi soft synth

i can't give details because i don't have to do it but both can be started in such a way as to provide a open midi port that can then be written to by alsa / jack or whatever

might take a while to figure out

timidity -iA -B2,8 -Os &
will open a alsa midi (sequencer) server port and when you issue the command will tell you the port number

another example
iiwusynth -a alsa -m alsa_seq gm.sf2

this will open a midi port with the soundfonts in the file gm.sf2

but the thing is that im not trying to use midi. im just want to be able to compose music and play it back, and then when i try to play it back i dont hear anything.

i've never used rosegarden, but if it's one of those things where you compose the music using musical notation and then it plays it back then that's MIDI... maybe your program is trying to use your soundcard's game/MIDI port instead of the internal MIDI device... if that's the case then you'd just need to configure it to use your soundcard's midi device instead of an external one through the midi port... just my ...

I also have the same problem... after taking me several weeks to get Rosegarden to download to my computer "properly", I now have it running - but producing no sound...

Checked the "alsaconf" - it gives me the sequenced fanfare without a problem...

Had a helluva time getting JACK to run, tho' - but even that appears to be working...

Any thoughts, questions, or insights?

Maybe its a SuSE problem. I switched to FC4 recently, and I'll see if I can get it working there.

So, people with no sound, at risk of asking the too obvious, did you use a mixer and check every channel?
If you run aconnect or Jack, do you see your list of writable ports and readable ports? And are they connected?

(I had trouble getting any sound with Muse (in Suse), but it came right after some fiddling. Unfortunately I don't know what exactly fixed it.)
Also, Big C, in Suse if you run under KDE you might get some trouble from arts, so you could experiment while using a more slimline window manager.

Spindles,

Yes, I used the alsamixer to check the volume of the channels...

Checked JACK - it listed the ports, and the Rosegarden master out L & R were connected to the Audio...

I use KDE - any ideas on what would be a slimmer one (GNOME)???

If you figure out what you did - let me know...

I don't think my soundcard supports MIDI - do I need to use timidity or something like that? And if so, do you know how to set up JACK to get it working?

Any thoughts, insights or good jokes would be appreciated...

Hi Big C,

Here are some pretty random thoughts.
If none of this helps, I suggest you let us know more about your soundcard and drivers.

KDE and Gnome are the two window managers that are big, busy and hungry (also friendly, easy to use etc.). For making music you might want to try for a window manager that's less likely to cause interruptions. My suse 9.1 came with blackbox, openbox, IceWM and Window Maker included: I can choose them from a menu at the welcome screen.

You might need to make sure that when Jack starts it kills arts. (In my Suse Jack already did this by default: there is an option in Jack to run scripts at start, and one of them is "artsshell -q terminate".)
(arts is the KDE sound server.)

When you open the connections window in Jack, although you can see connections in the Audio tab, you need to click on the Midi tab to see whether there are any readable and writable ports there.

Another possible problem with Jack and Midi could be permissions: if you look around at midi, Muse and Jack related threads here you will notice the advice to run Jack as root. A quick way is, opening from the command line:
sudo qjackctl
sudo muse


_______
This is just a guess, but if you use an alsa driver you might need to tweak your .asoundrc file in your home directory.
Here is mine.

##This bit I already had-- it should mention your sound driver, mine being emu10k1:
pcm.emu10k1 {
type hw
card 0
}

ctl.emu10k1 {
type hw
card 0
}

##This bit I added some time between not having sound from Muse and having sound working properly:

pcm.jackplug {
type plug
slave { pcm "jack" }
}

pcm.jack {
type jack
playback_ports {
0 alsa_pcmlayback_1
1 alsa_pcmlayback_2
}
capture_ports {
0 alsa_pcm:capture_1
1 alsa_pcm:capture_2
}
}
____________________
I saw this (above) here on LQ in a thread where foo_bar_foo was helping somebody get their Jack and sound sorted out, so I thought it was worth adding.

The other thing I did was load soundfonts into my card (SB Audigy2).
(Because this doesn't happen automatically.)
Run:
/usr/bin/sfxload /usr/share/sounds/sf2/some_sound_font_file_.SF2

Best bet for a start is probably a sound font file that came with your soundcard's installation disk for windows.

In summary: those were the three main things I did in my system that got Midi working.
1. run Jack (and Muse) with sudo
2. put the jack stuff (above) in .asoundrc
3. load soundfonts

Anyway, I'm no expert. I totally relied on LQ to get these things working (in advance of properly understanding them!).
Good luck.

It's not trying to use some sort of MIDI map file, is it? If it is, chances are it won't work with your sound card as heir instrument definitions are probably different