Description of problem: Current version of Rosegarden installed To get MIDI sounds TiMidity++ and dependencies installed Starting TiMidity in ALSA server mode using timidity -iA command Result is : Opening sequencer port : 128:0 128:1 128:2 128:3 Opening Rosegarden and connecting to one of the created ports gives : /dev/dsp : Device or resource busy Couldn't open dsp device (`d') And ther's no sound when starting to play a file Version-Release number of selected component (if applicable): How reproducible:every time Steps to Reproduce: 1. 2. 3.
Assignee: bugsquad => shikamaruSource RPM: Rosegarden => rosegarden
You should get sound using "timidity -iA -Os" command if you don't have jack installed. If jack is installed, Rosegarden starts it automatically (by default) and you have to follow that steps to get sound: -1) Start Rosegarden, but don't load any file (Rosegarden doesn't see any midi port as Timidity is not running still) -2) Start timidity with: "timidity -iA -Oj" (as Jack is now started, Timidity can connect to it) -3) Load a file to play in Rosegarden (which now sees the midi ports from Timidity) then play it.
CC: (none) => yc.guillemot
(In reply to comment #1) > You should get sound using "timidity -iA -Os" command if you don't have jack > installed. > > If jack is installed, Rosegarden starts it automatically (by default) and you > have to follow that steps to get sound: > -1) Start Rosegarden, but don't load any file (Rosegarden doesn't see any midi > port as Timidity is not running still) > -2) Start timidity with: "timidity -iA -Oj" (as Jack is now started, Timidity > can connect to it) > -3) Load a file to play in Rosegarden (which now sees the midi ports from > Timidity) then play it. Is this bug still valid or can it be closed? Regards, -- Shlomi Fish
CC: (none) => shlomif
You can close this bug. I din't trie the first solution, but the second, using Jack works. I tried it several times, in different ways, starting, stopping the computer or Jack. Every time I've got midi sounds. It's good to me. Thank you Jean-Louis Bourgeois
Resolving this bug.
Status: NEW => RESOLVEDResolution: (none) => INVALID