| Re: [proaudio] trouble emerging museseq |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/proaudio Archives
]
On Wed, 17 May 2006 01:37:42 -0700
Robert Persson <ireneshusband@xxxxxxxxxxx> wrote:
> 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.
Yes. That's also mentioned in the 00-OVERLAY-INFO file ;)
That's due to MusE not beeing compatible with fst-1.7 - it compiles,
but segfaults then, common error.
> 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.
It doesn't, i know this bug form the main portage version, please use
museseq-0.8.1a from the overlay, or museseq-0.8.1-r1 from main portage
(which is also 0.8.1a).
you can verify which version you are using with
$ equery which museseq
(equery is part of gentoolkit)
If it's the version from main portage /usr/portage/media-sound, the
file a bugreport on bugs.gentoo.org, although the latest version thre
should be OK.
> 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.
please try to make the midi connections inside MusE
Settings --> Midi Ports/Soft Synths
that works here without any problem.
> I've tried installing museseq-cvs instead, but that doesn't compile
> either.
Yes. See the "problems with museseq-cvs" thread on the mailinglist for
details why it doesn't work ;)
> Robert
> --
> Robert Persson
>
> Conspiracy Bears:
> Once upon a time there were lots of conspiracy bears...
>
>
Regards,
Tom