6 Mar
2008
6 Mar
'08
4:28 p.m.
Rui Nuno Capela wrote:
On Thu, March 6, 2008 14:01, schoappied wrote:
Aha... whow whow... that such a thing can cost me so much time and
effort to solve.... pfieuw.... (that was really a waste of time...)
Thanks!
I use the default version in the Ubuntu repo.... I thought Ubuntu was
one of the most up to date distro...!?
Other related question...
I thought to be smart and use the soundfonts of finale 2007 with qsynth.
But will work, with the *.sf2 extension, but the ones with the *.sfx
extention doesn't work.... Is there a way to work with this kind of file
on linux??
Regards,
Dirk
Shelagh Manton wrote:
(snip)
As I said, only engine 1 is not working.... You
can see that in the
messages displayed by qsynth.
(snip)
13:38:55.455 Qsynth1: Creating audio driver
(jack)...
13:38:55.581 Qsynth1: Creating MIDI router (alsa_seq)...
13:38:55.582 Qsynth1: Creating MIDI driver (alsa_seq)...
*13:38:55.615 Qsynth1: Failed to create the MIDI driver (alsa_seq). No
MIDI input will be available.
JACK tmpdir identified as [/dev/shm]
ALSA lib seq.c:935:(snd_seq_open_noupdate) Unknown SEQ snd-seq
fluidsynth: error: Error opening ALSA sequencer*
while in your qsynth1 engine setup/midi, is there anything legible in the
midi device name box? even though its greyed out?
if it is, make it blank. aha
btw, which qsynth version is this? don't get me started :) i'll suggest
you upgrate to the current maintained level (0.3.2) as this has already
been cleaned out, probably ;)
byee