You are not logged in.
they both can run normally,and can start with "sudo /etc/rc.d/timidity start" or "sudo /etc/rc.d/fluidsynth start" without any problem.
but when i put it in the rc.conf and startup with system as daemon,they cannot work out.
timidity++ service start with busy stat then put out error msg:couldn't open output device.
fluidsynth just start ,without any error msg output,but after boot,to test with "aconnect -o", no vertual midi writable port setup.
any help will be great.
Offline
Just guessing, is timidity starting after alsa? I'm pretty sure alsa has to be running before timidity can connect. Try adding alsa then timitidity++ to rc.conf without @ flag to see if that's the problem.
Offline
thank you,but this wont work out.
error still exist.
Offline
I have the same problem also.
Offline