> I think this may be because wine uses a client/server model. There is
> the wine client which runs the actual applications, but they seem to
> share the core wineserver process which seems to be responsible for
> actually mixing and generating the sound output. Renicing the 'wine'
> (frontend) process give the 'wineserver' (backend) process more CPU time
> to actually get the sound out.
yes, this is an accurate description of the wineserver model.
to prove this point, could you try and renice wineserver to -10 (as root)
- does that fix the latency issues still?
(if this doesnt then it could be the foreground process starving yet
another process - we have to find out which one.)
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/