[proaudio] trouble emerging museseq

[ Thread Index | Date Index | More lists.tuxfamily.org/proaudio Archives ]


I have had two problems while emerging museseq.  And then I couldn't get midi 
in or out working.

Firstly, I got an error about VST:

>>> Emerging (1 of 1) media-sound/museseq-0.8.1a to /
>>> checking ebuild checksums ;-)
>>> checking auxfile checksums ;-)
>>> checking miscfile checksums ;-)
>>> checking muse-0.8.1a.tar.gz ;-)
>>> Unpacking source...
>>> Unpacking muse-0.8.1a.tar.gz to /var/tmp/portage/museseq-0.8.1a/work
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/museseq-0.8.1a/work/muse-0.8.1 ...
 * vst useflag is disabled due segfault

In other words VST support is broken.

Secondly, the compile failed because /usr/lib/libladcca was missing. This was 
easily worked around by temporarily emerging ladcca. The problem is that 
ladcca blocks lash in portage, and it wants to use the same ip port as lash. 
Therefore when museseq is emerge USE=lash, it should definitely not depend on 
ladcca.

And then the trouble connecting midi:

I was able to write directly on the piano roll and play what I had written 
using one of the internal synths, but I was completely unable to get muse 
either to receive midi from my music keyboard or to route it to soft synths.

When I chose any existing port on the qjackctl midi connection map as the 
destination no midi data would be passed on, but the 
qjackctl "connect", "disconnect" and/or "disconnect all" buttons would start 
flashing on and off very rapidly.

I've tried installing museseq-cvs instead, but that doesn't compile either.

Robert
-- 
Robert Persson

Conspiracy Bears:
Once upon a time there were lots of conspiracy bears...




Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/