Re: [Denemo-devel] More timidity diagnostics

[Richard Shann]

On Thu, 2008-11-06 at 18:49 +0100, Nils Gey wrote:
> Don't use timidity.
ok. I got qsynth and a .sf2 soundfont and Qsynth said I needed the jack
daemon running so I tried:

$ jackstart --realtime --driver=alsa

and (in another window) launched QSynth which said that there could be
"tuning problems" and then, as with timidity, I go no output.

The window where I launched jack was as follows:

$ jackstart --realtime --driver=alsa
jackstart: cannot get realtime capabilities, current capabilities are:
           =ep cap_setpcap-ep
    probably running under a kernel with capabilities disabled,
    a suitable kernel would have printed something like "=eip"

back from read, ret = 1 errno == Success
jackstart: could not give capabilities: Operation not permitted
jackd 0.101.1
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details

JACK compiled with System V SHM support.
loading driver ..
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|
32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
Note: audio device hw:0 doesn't support a 32bit sample format so JACK
will try a  24bit format instead
Note: audio device hw:0 doesn't support a 24bit sample format so JACK
will try a  16bit format instead
nperiods = 2 for capture
Note: audio device hw:0 doesn't support a 32bit sample format so JACK
will try a  24bit format instead
Note: audio device hw:0 doesn't support a 24bit sample format so JACK
will try a  16bit format instead
nperiods = 2 for playback
cannot use real-time scheduling (FIFO at priority 20) [for thread
-1228375120, f rom thread -1228375120] (1: Operation not permitted)
cannot use real-time scheduling (FIFO at priority 10) [for thread
-1236767824, f rom thread -1236767824] (1: Operation not permitted)
subgraph starting at qsynth timed out (subgraph_wait_fd=7, status = 0,
state = Triggered)


And then further messages from time to time
like this:

**** alsa_pcm: xrun of at least 8.126 msecs

Does this make any sense to you?
Do I need to launch jackd as root?
Thanks for your help
Richard


>  I ever get problems with it and when it runs I get latency problems, even on 
> my ~3ms latency system.
> I would suggest you use Fluidsynth instead or better to speak of QSynth which 
> is a GUI for fluidsynth. You can load any .sf2 soundfont file with it, freely 
> avaible in the internet. I have the .sf2 file here which sounds like the 
> standard MS-Windows soundfont. This is not good in realistic-sounding quality 
> but I find it handy to have the "Windows-Midi" sound by hand if I work in 
> midi-enviroments with musicians who have windows. So if I send playbacks to 
> them I know what to expect.
> 
> Anyway... you have more feedback and controlls with QSynth. I suggest to use 
> the JACK-GUI Qjackctl with it. Not for JACK but for alsa midi. just don't 
> start the jack server, the alsa-midi ports will show up in the alsa-tab. You 
> can connect them how you like and connect to Denemo to QSynth/Fluidsynth or 
> even with Timidity if it shows up.
> 
> Nils
> 
> On Thu, 06 Nov 2008 16:41:32 +0000
> Richard Shann <address@hidden> wrote:
> 
> > I have tracked down some diagnostics:
> > After running 
> > timidity -iAD
> > to start the timidity daemon I get
> > 
> > $ aconnect -o
> > client 14: 'Midi Through' [type=kernel]
> >     0 'Midi Through Port-0'
> > client 20: 'USB Keystation 49e' [type=kernel]
> >     0 'USB Keystation 49e MIDI 1'
> > client 128: 'aseqdump' [type=user]
> >     0 'aseqdump        '
> > address@hidden:~$ aconnect -o
> > client 14: 'Midi Through' [type=kernel]
> >     0 'Midi Through Port-0'
> > client 20: 'USB Keystation 49e' [type=kernel]
> >     0 'USB Keystation 49e MIDI 1'
> > client 128: 'aseqdump' [type=user]
> >     0 'aseqdump        '
> > client 129: 'TiMidity' [type=user]
> >     0 'TiMidity port 0 '
> >     1 'TiMidity port 1 '
> >     2 'TiMidity port 2 '
> >     3 'TiMidity port 3 '
> > 
> > But when I try:
> > 
> > $ aconnect 129 20
> > Connection failed (Operation not permitted)
> > 
> > It does not complain if I connect the other way round, but it does not
> > give output to the speakers either. (I have installed soundfonts for
> > timidity).
> > Richard
> > 
> > 
> > 
> > 
> > 
> > _______________________________________________
> > Denemo-devel mailing list
> > address@hidden
> > http://lists.gnu.org/mailman/listinfo/denemo-devel
> 
>