16 Jul
2009
16 Jul
'09
9:11 p.m.
All this will hopefully change in future and was
discussed in some
length on the LAD list some time ago. Until that changes I personally
recommend to compile jack without dbus unless you want to use laditools.
I use Gentoo pro audio overlay, I have found if using FFADO i seem to need to
have the dbus USE flag turned on.
Also, I'm new to the whole live ebuilds
thing. I see that the
overlay offers Ardour, Jack, and many other things in the form of
direct CVS snapshots. It seems that these are prefered, however, it
looks like they often require unmasked versions of dependency
programs. Should I be afraid of that? For example, the live ebuild
for Ardour seems to be trying to pull in a version of aubio that is
masked for amd64, though I didn't see a bug in the bug database
explaining why. Should I simply unmask any package that is demanded
of a program in the overlay on the basis that overlay programs are
basically bleeding edge anyway?
I can't help you with that specifically since I never used gentoo but
as a general guideline: stay away from it if you don't know what you're
doing. A CVS (or any version control system for that matter) checkout
might be totally broken and there's no guarantee that it will even
compile.
17 Jul
17 Jul
4:41 p.m.
New subject: Jack, Ardour, and the Gentoo Pro-Audio Overlay
I've been settling into my own Gentoo system, and so far haven't had any
trouble with unmasked pro-audio packages (for numbered versions anyway)
interfering with anything else in portage. It seems to me that pro-audio is
not very well maintained. I've had to hack several ebuilds to get them to
work, but for the ones that do, likely any masks are just because no one has
tested the ebuild, or because it is live. But more people care about jack
and Ardour so you're likely to find more support on those. Anyway, I would
say don't be afraid of the masked packages. Sometimes the live ebuilds will
work, sometimes not, you may have to fix things yourself and submit bugs
upstream. Though so far my practice has been to build stable versions, then
rebuild with cvs versions as I want. Bad idea to use live ebuilds if you
want something working right away, but if you really want that latest
feature or bug fix, just try it.
I generally haven't built any dbus support, and I'm not sure how jack itself
uses dbus. Not sure about "classic" either, but for those undocumented
flags, I find the best thing to do is just open the ebuild and see what
options those flags are passing to configure (which you should be able to
figure out without any knowledge of how ebuilds work) and then see what
those do.
On Thu, Jul 16, 2009 at 7:11 PM, sonofzev(a)iinet.net.au <
sonofzev(a)iinet.net.au> wrote:
Live ebuilds are always masked for this very reason. However you may find
that
some things are worth unmasking. (I have found that for my hardware I need
to use
the live ebuild for FFADO and Jack to get the best results..
You won't find reported bugs on Gentoo for live ebuilds as they aren't
really
supported but the bug you find may be worth checking for and reporting
upstream
(if you intend to help the particular project)... BTW Ardour 2.x live
ebuild is
relatively stable but not 3.x....
I highly recommend you join the pro-audio overlay mailing list for specific
discussion around this overlay... (We won't bite :)
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
All this will hopefully change in future and was
discussed in some
length on the LAD list some time ago. Until that changes I personally
recommend to compile jack without dbus unless you want to use laditools.
I use Gentoo pro audio overlay, I have found if using FFADO i seem to need
to
have the dbus USE flag turned on.
Also, I'm new to the whole live ebuilds
thing. I see that the
overlay offers Ardour, Jack, and many other things in the form of
direct CVS snapshots. It seems that these are prefered, however, it
looks like they often require unmasked versions of dependency
programs. Should I be afraid of that? For example, the live ebuild
for Ardour seems to be trying to pull in a version of aubio that is
masked for amd64, though I didn't see a bug in the bug database
explaining why. Should I simply unmask any package that is demanded
of a program in the overlay on the basis that overlay programs are
basically bleeding edge anyway?
I can't help you with that specifically since I never used gentoo but
as a general guideline: stay away from it if you don't know what you're
doing. A CVS (or any version control system for that matter) checkout
might be totally broken and there's no guarantee that it will even
compile.
5:01 p.m.
New subject: Jack, Ardour, and the Gentoo Pro-Audio Overlay
On Fri, 17 Jul 2009, Tim Jones wrote:
I've been settling into my own Gentoo system, and
so far haven't had
any trouble with unmasked pro-audio packages (for numbered versions
anyway) interfering with anything else in portage. It seems to me that
pro-audio is not very well maintained. I've had to hack several
ebuilds to get them to work, but for the ones that do, likely any
masks are just because no one has tested the ebuild, or because it is
live.
Since the time I wrote earlier, I've had significant progress getting
things installed, mostly from avoiding the live CVS versions of
everything, and settling for Jack 0.116.2, which is still 0.116 or newer
as cautioned on the Ardour site. (I compiled with no DBus or firewire
support, since I don't use Ffado or FreeBob.) Everything now seems to
coexist well with my other apps and system libraries. I've got Ardour
2.7.1.
My next challenge is to pick a version of rt-sources and get that
configured and setup. I usually prefer to setup a kernel with modules
that my current system has or is likely to ever have, and put the ones
that are needed to boot into the kernel statically, so I'm going to see
if I can do without an initrd. That certainly out to be possible
though. I just don't like having ninety drivers I don't use autoloaded
by 'discover' during the bootup...it's annoying.
I wonder if it's better to go with the unmasked rt-sources-2.6.16-r29
(which I see has a very high patchlevel number, so apparently a lot of
time is going into it), or the newest rt-sources-2.6.29.2-r11, which is
more current, but masked. I asked this recently on the Pro-Audio
overlay list, so I'll see what they say there.
But more people care about jack and Ardour so
you're likely to find
more support on those. Anyway, I would say don't be afraid of the
masked packages.
Yeah, I've seen so many packages in Pro-Audio that needed unmasking to
install that I've just started treating that as par for the course in
the overlay. I'm still sticking with stable packages for my base system
though.
I generally haven't built any dbus support, and
I'm not sure how jack
itself uses dbus. Not sure about "classic" either, but for those
undocumented flags, I find the best thing to do is just open the
ebuild and see what options those flags are passing to configure
(which you should be able to figure out without any knowledge of how
ebuilds work) and then see what those do.
I did finally find a websvn interface to the changelogs on the overlay
site that described that: It's for if you'd like to compile both Dbus
*and* non-Dbus Jack -- you can enable "dbus" and "classic" together.
I've just gone with 0.116.2 and no Dbus, and that seems to coexist with
everything else nicely.
--
+ Brent A. Busby + "We've all heard that a million monkeys
+ UNIX Systems Admin + banging on a million typewriters will
+ University of Chicago + eventually reproduce the entire works of
+ Physical Sciences Div. + Shakespeare. Now, thanks to the Internet,
+ James Franck Institute + we know this is not true." -Robert Wilensky
8:44 p.m.
New subject: Jack, Ardour, and the Gentoo Pro-Audio Overlay
maybe you're already doing this, but thought its worth mentioning.
if you unmask packages, make sure you set ACCEPT_KEYWORDS="~x<arch>" in
/etc/portage/package.keywords
setting that line in make.conf can be disastrous, as in its easier to
reinstall everything. and yes, that sucks as well. I've done it :(
pretty much everything in pro-audio overlay is masked. i believe they have a
mailing list as well.
On Fri, Jul 17, 2009 at 12:01 PM, Brent Busby <brent(a)keycorner.org> wrote:
On Fri, 17 Jul 2009, Tim Jones wrote:
I've been settling into my own Gentoo system,
and so far haven't had
any trouble with unmasked pro-audio packages (for numbered versions
anyway) interfering with anything else in portage. It seems to me that
pro-audio is not very well maintained. I've had to hack several
ebuilds to get them to work, but for the ones that do, likely any
masks are just because no one has tested the ebuild, or because it is
live.
Since the time I wrote earlier, I've had significant progress getting
things installed, mostly from avoiding the live CVS versions of
everything, and settling for Jack 0.116.2, which is still 0.116 or newer
as cautioned on the Ardour site. (I compiled with no DBus or firewire
support, since I don't use Ffado or FreeBob.) Everything now seems to
coexist well with my other apps and system libraries. I've got Ardour
2.7.1.
My next challenge is to pick a version of rt-sources and get that
configured and setup. I usually prefer to setup a kernel with modules
that my current system has or is likely to ever have, and put the ones
that are needed to boot into the kernel statically, so I'm going to see
if I can do without an initrd. That certainly out to be possible
though. I just don't like having ninety drivers I don't use autoloaded
by 'discover' during the bootup...it's annoying.
I wonder if it's better to go with the unmasked rt-sources-2.6.16-r29
(which I see has a very high patchlevel number, so apparently a lot of
time is going into it), or the newest rt-sources-2.6.29.2-r11, which is
more current, but masked. I asked this recently on the Pro-Audio
overlay list, so I'll see what they say there.
But more people care about jack and Ardour so
you're likely to find
more support on those. Anyway, I would say don't be afraid of the
masked packages.
Yeah, I've seen so many packages in Pro-Audio that needed unmasking to
install that I've just started treating that as par for the course in
the overlay. I'm still sticking with stable packages for my base system
though.
I generally haven't built any dbus support,
and I'm not sure how jack
itself uses dbus. Not sure about "classic" either, but for those
undocumented flags, I find the best thing to do is just open the
ebuild and see what options those flags are passing to configure
(which you should be able to figure out without any knowledge of how
ebuilds work) and then see what those do.
I did finally find a websvn interface to the changelogs on the overlay
site that described that: It's for if you'd like to compile both Dbus
*and* non-Dbus Jack -- you can enable "dbus" and "classic" together.
I've just gone with 0.116.2 and no Dbus, and that seems to coexist with
everything else nicely.
--
+ Brent A. Busby + "We've all heard that a million monkeys
+ UNIX Systems Admin + banging on a million typewriters will
+ University of Chicago + eventually reproduce the entire works of
+ Physical Sciences Div. + Shakespeare. Now, thanks to the Internet,
+ James Franck Institute + we know this is not true." -Robert Wilensky
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
11:34 p.m.
New subject: Jack, Ardour, and the Gentoo Pro-Audio Overlay
On Fri, 17 Jul 2009, munkeyfreenix batcat wrote:
maybe you're already doing this, but thought its
worth mentioning.
if you unmask packages, make sure you set ACCEPT_KEYWORDS="~x<arch>" in
/etc/portage/package.keywords
setting that line in make.conf can be disastrous, as in its easier to
reinstall everything. and yes, that sucks as well. I've done it :(
Thanks! I have been doing that though... Like I said, aside from the
Pro-Audio Overlay, I'm going with stable packages for everything in the
whole distro...(except for the HP print manager HPLIP, which only works
with my printer in a masked version...which works perfectly!).
I suppose there are people who run ~arch for everything...probably
developers though.
pretty much everything in pro-audio overlay is masked.
i believe they
have a mailing list as well.
Yeah, I'm on it now. It seems to only get one message every few days.
--
+ Brent A. Busby + "We've all heard that a million monkeys
+ UNIX Systems Admin + banging on a million typewriters will
+ University of Chicago + eventually reproduce the entire works of
+ Physical Sciences Div. + Shakespeare. Now, thanks to the Internet,
+ James Franck Institute + we know this is not true." -Robert Wilensky
18 Jul
18 Jul
6:52 a.m.
New subject: Jack, Ardour, and the Gentoo Pro-Audio Overlay
On Fri, 17 Jul 2009 14:01:31 -0500 (CDT)
Brent Busby <brent(a)keycorner.org> wrote:
On Fri, 17 Jul 2009, Tim Jones wrote:
You can, but it's not a very good idea, read up on it in: [LAD]
jackd/jackdbus : D-Bus or not D-Bus...
I've been settling into my own Gentoo system,
and so far haven't
had any trouble with unmasked pro-audio packages (for numbered
versions anyway) interfering with anything else in portage. It
seems to me that pro-audio is not very well maintained. I've had to
hack several ebuilds to get them to work, but for the ones that do,
likely any masks are just because no one has tested the ebuild, or
because it is live.
Since the time I wrote earlier, I've had significant progress getting
things installed, mostly from avoiding the live CVS versions of
everything, and settling for Jack 0.116.2, which is still 0.116 or
newer as cautioned on the Ardour site. (I compiled with no DBus or
firewire support, since I don't use Ffado or FreeBob.) Everything
now seems to coexist well with my other apps and system libraries.
I've got Ardour 2.7.1.
My next challenge is to pick a version of rt-sources and get that
configured and setup. I usually prefer to setup a kernel with
modules that my current system has or is likely to ever have, and put
the ones that are needed to boot into the kernel statically, so I'm
going to see if I can do without an initrd. That certainly out to be
possible though. I just don't like having ninety drivers I don't use
autoloaded by 'discover' during the bootup...it's annoying.
I wonder if it's better to go with the unmasked rt-sources-2.6.16-r29
(which I see has a very high patchlevel number, so apparently a lot
of time is going into it), or the newest rt-sources-2.6.29.2-r11,
which is more current, but masked. I asked this recently on the
Pro-Audio overlay list, so I'll see what they say there.
But more people care about jack and Ardour so
you're likely to find
more support on those. Anyway, I would say don't be afraid of the
masked packages.
Yeah, I've seen so many packages in Pro-Audio that needed unmasking
to install that I've just started treating that as par for the course
in the overlay. I'm still sticking with stable packages for my base
system though.
I generally haven't built any dbus support,
and I'm not sure how
jack itself uses dbus. Not sure about "classic" either, but for
those undocumented flags, I find the best thing to do is just open
the ebuild and see what options those flags are passing to
configure (which you should be able to figure out without any
knowledge of how ebuilds work) and then see what those do.
I did finally find a websvn interface to the changelogs on the
overlay site that described that: It's for if you'd like to compile
both Dbus *and* non-Dbus Jack -- you can enable "dbus" and "classic"
together. I've just gone with 0.116.2 and no Dbus, and that seems to
coexist with everything else nicely.
5417
days inactive
5419
days old
linux-audio-user@lists.linuxaudio.org
5 comments
5 participants
participants (5)
-
Brent Busby -
hollunder＠gmx.at -
munkeyfreenix batcat -
sonofzev＠iinet.net.au -
Tim Jones