[overlay] Pro audio production applications, Part 2

[xaviermiller]

I use the "normal" versions with DBUS. I needed to explicitly set /usr/bin/jackdbus to get it running
_________________
Kind regards,
Xavier Miller

[hunky]

I used this command to get it running:
qdbus org.jackaudio.service /org/jackaudio/Controller StartServer
and it would run - I could start ardour and whatnot, but I couldn't get it to connect with alsa with the "normal" versions.

I tried to stop jackdbus various ways:
qdbus org.jackaudio.service /org/jackaudio/Controller StopServer
for instance which seemed to work but in ps aux it would show jackdbus still running. I tried killall and kill pid but those wouldn't either.

Not sure I needed to kill it but it seemed like other programs like amarok wouldn't work - but thinking back maybe I still had pulseaudio installed and it was conflicting with jackdbus.. it all gets pretty muddled when you don't really know what you are doing.

/jd

[audiodef]

I would really like to see a good explanation of what jackdbus is all about! Who put dbus together with JACK? Why? What are all the relevant commands? And so on.
_________________
Gentoo Studio: A Gentoo-based, professional digital audio workstation OS.

[xaviermiller]

The idea is that anybody can start jack and communicate with the jack instance through DBus.
So, you can start jack as a service (running as a service user), and connect your applications to that instance.
_________________
Kind regards,
Xavier Miller

[audiodef]

But I still don't understand why dbus is involved at all. What does using dbus with JACK do that using dbus without JACK can't do?
_________________
Gentoo Studio: A Gentoo-based, professional digital audio workstation OS.

[keenblade]

[audiodef]

I'm-a check it out! Sounds like what The Doctor ordered, and delivered with a free Tardis.

EDIT: Nice! I really like laditray and the way the config options are arranged.

I haven't run my usual Rosegarden/Ardour setup yet, but I got a couple of xruns and jack quit (using firewire driver - and it has to be this one due to my equipment). I'll post back about what happens when I actually work in my usual session setup. But I really like this and the ideas behind it, having read and now seen it in action.

This will force me to use Patchage rather than the connections dialog provided by qjackctl. I always thought Patchage was cooler, and now I have no excuse to be lazy about it.

EDIT++:

I left my usual setup running for a few hours using LADI/jackdbus instead of Qjackctl/jackd. Usually, by now, jackd would have quit, been killed, or told one or both programs they were no longer welcome, and I'd have to force quit Ardour, quit everything else, and start it all up again.

It's still running!
_________________
Gentoo Studio: A Gentoo-based, professional digital audio workstation OS.

[hunky]

Two problems I hope are easy for you:

1. How to get back to defaults in ladiconf?:
I've given ladi-tools a try and have a problem. I fired it up pretty much stock and it seemed to start jack no problem through ladi-tray. But trying to fire up a session in Ardour I am getting an error about the session was sampled with 48,000 and it is trying to use 16,000 instead. I had this problem with Qjackctl recently and tweaked something and got past that issue. So I started tweaking things in ladiconf and now have mucked up something so it won't start jack at all now - I get an error. (not at desk to post that error). I tried removing the ~/.config/jack/conf.xml file and restarting ladi-tray, but it still picks up my edits from somewhere else. I think my 16,000 problem could be that it is trying to grab my built in sound card or something. Which leads to question2.

2. Preferred method for ordering the naming of sound cards through reboots? I've found this: http://www.gentoo.org/doc/en/udev-guide.xml and one or two other sites but they come with caveats and some are a bit over my head. I can follow the given link there - I can figure that out and give it a try. Basically I have 4 sound cards (sound stuff is just a hobby and don't have a dedicated machine for it): webcam with mike, built in sound shows up with two - one analog and one digital (hdmi?), and then my Delta 66. Just curious if the link is what I should use.

many thanks, JD

[McGruff]

I've got a new home-brewed ebuild for Ardour OSC control with a TV remote: "media-sound/ardour-controllers". This can maybe evolve to encompass other remote controls with eg use flags for lirc, wii and bluetooth.

A remote can be handy if you're set up for a take in front of a mic, some distance away from the computer. Or just to sit back in an armchair and take in the mix.

Any advice/testers appreciated. I haven't done any ebuilding before. Should I try to get this into standard portage or the pro-audio overlay?

You can find all the files here if you want to try it out. This is a tarball of my private "underlay" overlay containing ebuilds for media-sound/ardour-controllers as well as some new perl module ebuilds (see dev-perl/ ) which you'll need to fill dependencies. Set the "underlay" dir as a local overlay, or add all the stuff inside to an existing one.

All the ebuilds keyworded ~x86 which I think might mean that they can't install on 64bit..? I'm new to this ebuild stuff but I want to make this work so just let me know any problems.

You'll probably need this lot in /etc/portage/package.keywords:

media-sound/ardour-controllers ~x86
dev-perl/Audio-Ardour-Control ~x86
dev-perl/Net-LibLO ~x86
dev-perl/Exporter ~x86
virtual/perl-File-Path ~x86
perl-core/File-Path ~x86

[mmxgn]

Hello,

I can't seem to be able to build media-sound/yoshimi-0.058.1 from the pro-audio overlay.
Something seems to go wrong at the linking stage.


output of $ emerge --info =media-sound/yoshimi-0.058.1

[keenblade]

[McGruff]

Won't build for me either but I get:

[keenblade]

mcgruff, is your gentoo or cmake is outdated a bit? Here yoshimi-0.058.1 emerges fine with:
cmake-2.8.3-r1
fltk-1.1.10-r1
portage-2.2.0_alpha15
_________________
Anyway it's all the same at the end...
Need help to get it working: "x-fi surround 5.1"

[McGruff]

Cmake - same: cmake-2.8.1-r2.

Portage is slightly older: portage-2.1.9.25

Maybe it's fltk:

[I--] [ ] x11-libs/fltk-1.1.9-r1 (1.1)
[I--] [ ] x11-libs/fltk-2.0_pre6970 (2)

Not sure why I've got fltk-2.0:

# equery depends fltk
[ Searching for packages depending on fltk... ]
media-sound/alsa-tools-1.0.23 (fltk? =x11-libs/fltk-1.1*)
media-sound/zynaddsubfx-2.2.1-r4 (>=x11-libs/fltk-1.1.2:1.1)

I'll do a --depclean (which should get rid of fltk-2.0), get 1.1.10-r1, and then try again.

[keenblade]

[mmxgn]

[McGruff]

[mmxgn]

[McGruff]

By default all off and I left it at that:

-debug -doc -examples -games -opengl -threads -xft -xinerama

[keenblade]

[McGruff]

That did it - thanks keenblade

[keenblade]

[darkbasic]

Uhm... I tried jackdbus and ladi overlay lots of months ago and I had tons of problems.
Are they production ready now?
_________________
Computers are like air conditioners:
they stop working properly when you open Windows...

Coltiva Linux, Windows si pianta da solo.

http://www.linuxsystems.it/

[audiodef]

I've updated my site design, because of which the Pro-Audio For Gentoo Workstations how-to has a new url: http://audiodef.com/projects.php?project_id=1.

Or go to http://www.audiodef.com and click on "Projects" to find it.

Pro-audio ebuild and source fixes I've made continue to be hosted in the same place, so pro-audio ebuilds Keenblade updated with my fixes should continue to work.
_________________
Gentoo Studio: A Gentoo-based, professional digital audio workstation OS.

[papapenguin]

I'm getting an error in jack audio connection kit...