Hi Preston, The fluidsynth command line options in the script have -is. i says no-shell, s says run as a server. Then the terminal session started automatically at boot starts it up. It seems to work reliably enough for me, although there is a delay (5 sec? in the script that I might lengthen as the large soundfont file that I am using seems to take a bit more digestion.
There is probably a smart way to query status from fluidsynth (are you ready yet?) but I don’t know it. Peter > On 31 Oct 2017, at 11:24 am, H P Ladds <householdwo...@gmail.com> wrote: > > Hi Peter, > > Man! I had a miserable experience getting fluidsynth to run at boot. I tried > everything: editing the rc.local,.bashrc, init.d,even tried my hand at the > new system. > > Somewhere I stumbled upon the "-- no-shell" and the "-- service" options and > one of these (I don't know which just yet) did the trick for me. > > Thanks again for the script. Does it run successfully at boot time? I don't > understand how it does this? > > Cheers, > Preston > > > > On Thu, Oct 26, 2017 at 1:18 AM, Peter Hanlon <hanlo...@bigpond.net.au > <mailto:hanlo...@bigpond.net.au>> wrote: > Hi Preston, > > What I actually have is an organ with a Teensy 3.2 running Arduino code > reading the keystrokes and producing a MIDI stream to a USB port. This USB > then connects into the RPi where fluidsynth processes the MIDI into an audio > output. So logically I imagine Piano Booster also produces MIDI which you > want to run into fluidsynth in a similar way. You would probably run the > amidi -i and amidi -o commands as detailed by Ted, and change the script to > get the right port name for the PB output stream. > > Peter > >> On 26 Oct 2017, at 1:15 pm, H P Ladds <householdwo...@gmail.com >> <mailto:householdwo...@gmail.com>> wrote: >> >> Hi Peter, >> Thanks so much for the script. Good to know that you got it to work. One >> line in the script had me wondering. >> "echo Arduino input port: $myownport" Did this script also work on the RPi? >> My next step is to optimize the "machine" to the task of making sound. Ted >> Felix MIDI should be some help. >> Cheers, >> Preston >> >> On Tue, Oct 24, 2017 at 10:31 PM, Peter Hanlon <hanlo...@bigpond.net.au >> <mailto:hanlo...@bigpond.net.au>> wrote: >> I don’t claim to be an expert, but amended a script to my requirements. >> >> I finished with a script called ‘fluid’ which I installed in /usr/local/bin. >> >> I also established a user called synth in the ‘audio’ group, to help with >> latency, and added a couple of lines to the end of /home/pi/.profile, >> consisting of first line 'sudo su synth’, and second line ‘fluid start’. >> >> Google Ted Felix MIDI for better info. >> >> In my case, I also needed to hold off on supplying MIDI until fluid synth >> was ready for it. You could probably extend the script to start the other >> application. >> >> Peter >> >> >> >> > On 25 Oct 2017, at 11:24 am, H P Ladds <householdwo...@gmail.com >> > <mailto:householdwo...@gmail.com>> wrote: >> > >> > Anyone tried or had success starting Fluidsynth at boot on a Rasp Pi? >> > >> > I'm trying to create a RPi machine dedicated to playing Piano Booster (an >> > application that teaches piano playing.) Piano Booster depends upon a >> > running instance of Fluidsynth. >> > >> > Cheers, >> > Preston >> > _______________________________________________ >> > fluid-dev mailing list >> > fluid-dev@nongnu.org <mailto:fluid-dev@nongnu.org> >> > https://lists.nongnu.org/mailman/listinfo/fluid-dev >> > <https://lists.nongnu.org/mailman/listinfo/fluid-dev> >> >> >> _______________________________________________ >> fluid-dev mailing list >> fluid-dev@nongnu.org <mailto:fluid-dev@nongnu.org> >> https://lists.nongnu.org/mailman/listinfo/fluid-dev >> <https://lists.nongnu.org/mailman/listinfo/fluid-dev> >> >> >> _______________________________________________ >> fluid-dev mailing list >> fluid-dev@nongnu.org <mailto:fluid-dev@nongnu.org> >> https://lists.nongnu.org/mailman/listinfo/fluid-dev >> <https://lists.nongnu.org/mailman/listinfo/fluid-dev> > > > _______________________________________________ > fluid-dev mailing list > fluid-dev@nongnu.org <mailto:fluid-dev@nongnu.org> > https://lists.nongnu.org/mailman/listinfo/fluid-dev > <https://lists.nongnu.org/mailman/listinfo/fluid-dev> > > > _______________________________________________ > fluid-dev mailing list > fluid-dev@nongnu.org > https://lists.nongnu.org/mailman/listinfo/fluid-dev
_______________________________________________ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev
