On Tue, 28 May 2019, Seth Kenlon wrote:
Interesting. I haven't had to stop Pulse for my music work in
years
(but admittedly haven't worked on Fedora in a while, opting for the
stability of Slackware and RHEL; maybe this apparent regression
confirms my bias). Any way, glad you got it working!
Technically, it seems that you "suspend" it and never really kill the
process.
If you look at the init.d-like script on Ted's MIDI Linux guide, the
following line suspends pulseaudio.
pasuspender -- jackd -d alsa --device hw:0 --rate 44100 --period 128
&>/tmp/jackd.out &
If you do something like pgrep -a pulse you'll see that there is a PID for
a pulseaudio process.
Once you're finished with MIDI, you should stop fluidsynth and jackd; note
the line that reads:
killall fluidsynth
killall jackd
echo Audio servers stopped.
Once that's done, then pulseaudio governs, and you can go back to using
vlc, mplayer, watch youtube, etc.
fyi,
M
> On Tue, May 28, 2019 at 5:18 AM Max Pyziur <pyz(a)brama.com> wrote:
>>
>> On Sat, 25 May 2019, Seth Kenlon wrote:
>>
>>> For a MIDI file to produce sound out of Rosegarden (and probably most
>>> DAWs) you do have to assign the MIDI file an instrument.
>>>
>>> If the MIDI file is composed for General MIDI, you have to assign
>>> General MIDI to the track containing the MIDI file you are trying to
>>> play. I haven't used Timidity++ directly in a long while, but if I
>>> remember correctly, General MIDI is the default for it (although you
>>> can swap out instrument sets in timidiity.cfg). So in other words,
>>> while it *is* the default behaviour of Timidity to use General MIDI
>>> mappings in order to produce sound from a MIDI file, that is *not* the
>>> default for Rosegarden (et. al) because a DAW sort of expects you to
>>> assign your own instruments.
>>>
>>> If you are assigning an instrument (in Track Parameters) to the track
>>> in Rosegarden, then I'd look at your sound output settings. I imagine
>>> Rosegarden is sending sound output to something other than the
>>> speakers or headphones you expect to hear output from. The way I check
>>> for that is from the outside in: check all my physical cable
>>> connections, then my sound settings in pavuctl (Sound Settings in
>>> Gnome), then check JACK sound mappings, and then finally check
>>> Rosegarden sound mapping.
>>
>> Thank you for this.
>>
>> I now can plug in a USB MIDI hardward controller (Akai LPK25) and open
>> Rosengarden, and get sound output. I also can load a MIDI file (found on
>> some MIDI archive) into Rosengarden, and it plays.
>>
>> Not all Fedora-installed MIDI-related is functioning for me.
>>
>> But combined that's a start and gets me to the next set of obstacles.
>>
>> The critical set of instructions and web source that got me through this
>> is
>> Ted's Linux MIDI Guide
>>
http://tedfelix.com/linux/linux-midi.html
>>
>> There's some explanation; critically Pulseaudio impedes MIDI functionality
>> and needs to be shutdown at the user level. The webpage provides a bash
>> init.d-style StartStopStatus script. It needs a bit of modification for
>> things such as the location the recommended soundfont.
>>
>> The webpage also provides examples of commands to use for diagnostic
>> purposes.
>>
>> fyi,
>>
>> MP
>>
>>> On Sat, May 25, 2019 at 9:43 AM Samuel Sieb <samuel(a)sieb.net> wrote:
>>>>
>>>> On 5/24/19 6:32 AM, Max Pyziur wrote:
>>>>> I then began working through your Rosengarden item. I connected my
USB
>>>>> MIDI controller ((Akai LPK25).
>>>>>
>>>>> Started jackd, then qjacktl, and then Rosengarden.
>>>>>
>>>>> I loaded a MIDI file, pushed "play," and I get no sound.
That's where I
>>>>> get stuck.
>>>>>
>>>>> As I mentioned, I can work w MuseScore, Transcribe!, Audacity, strip
>>>>> audio from videos using ffmpeg, etc.
>>>>>
>>>>> So, it seems that there are some services that need to be
>>>>> enabled/started or disabled/stopped to move further here.
>>>>
>>>> Try installing qsynth (gui for fluidsynth). Connect it to the midi
port.
>>>>
>>>> I helped my son setup rosegarden to play around with some composing, so
>>>> I know it works.
>>>> _______________________________________________
>>>> users mailing list -- users(a)lists.fedoraproject.org
>>>> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>>>> Fedora Code of Conduct:
https://getfedora.org/code-of-conduct.html
>>>> List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
>>>> List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>>> _______________________________________________
>>> users mailing list -- users(a)lists.fedoraproject.org
>>> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>>> Fedora Code of Conduct:
https://getfedora.org/code-of-conduct.html
>>> List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
>>> List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>>>
>> _______________________________________________
>> users mailing list -- users(a)lists.fedoraproject.org
>> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>> Fedora Code of Conduct:
https://getfedora.org/code-of-conduct.html
>> List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://getfedora.org/code-of-conduct.html
> List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>