Mike,
Several of the Jack2 packages are compiled with dbus enabled. This
shouldn't be a problem, but on some systems dbus doesn't get started
unless you are running X. I've run into this on Ubuntu/Debian systems
quite a bit. Jack doesn't actually need X to run, it is possible to
compile it without dbus.
Sometimes work around this and run jackd2 by doing a dbus-launch to get
the dbus daemon started. An alternate is to try Jack1 as you've
indicated.
Admittedly for a few reasons I often prefer Jack2, but for what you're
doing it really doesn't matter which you use.
Lorne Tyndale
>
> G'day along,
>
> I have installed jackd, but I am getting...
>
> root@tantive:~# jackd -d alsa -d hw:0
> jackdmp 1.9.11
> Copyright 2001-2005 Paul Davis and others.
> Copyright 2004-2014 Grame.
> jackdmp comes with ABSOLUTELY NO WARRANTY
> This is free software, and you are welcome to redistribute it
> under certain conditions; see the file COPYING for details
> no message buffer overruns
> no message buffer overruns
> no message buffer overruns
> JACK server starting in realtime mode with priority 10
> self-connect-mode is "Don't restrict self connect requests"
> Failed to connect to session bus for device reservation Unable to
> autolaunch a dbus-daemon without a $DISPLAY for X11
>
> Audio device hw:0 cannot be acquired...
> Cannot initialize driver
> JackServer::Open failed with -1
> Failed to open server
>
> THere is no X on this box and very little running, I can;t see what or
> why it can't get hw:0.
>
> Any pointers?
>
> --
> Mike Phillips
> Coast FM.
> _______________________________________________
> openob-users mailing list -- openob-users(a)lists.talkunafraid.co.uk
> To unsubscribe send an email to openob-users-leave(a)lists.talkunafraid.co.uk
G'day all,
Is case you have not heard there is a virus thing going around :-)
We are home basing all our radio presenters where possible.
We have been using openob for obs for some time but only one at a time.
We are now in the situation of having multiple openob trx's at the same
time (only because they are not switched off) and this, I believe, is
causing issues.
questions:
1. I presume multiple tx's to 1 rx does not work.
2. I should be able to to run multiple openobs on different ports using
jack and it will merge everything together? Hopefully.
So so long as only one rx is sending audio we will only hear one feed.
Ideally I would use an audio switch to switch between the various feeds
but we have no real way of setting this up now.
We do have this but only one OB input currently. :-(
--
Mike Phillips
Coast FM.
G'day along,
I have installed jackd, but I am getting...
root@tantive:~# jackd -d alsa -d hw:0
jackdmp 1.9.11
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2014 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
no message buffer overruns
no message buffer overruns
no message buffer overruns
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
Failed to connect to session bus for device reservation Unable to
autolaunch a dbus-daemon without a $DISPLAY for X11
Audio device hw:0 cannot be acquired...
Cannot initialize driver
JackServer::Open failed with -1
Failed to open server
THere is no X on this box and very little running, I can;t see what or
why it can't get hw:0.
Any pointers?
--
Mike Phillips
Coast FM.
Mike,
You can run multiple ob connections on different ports, I've done this
before. I'd have to double check my notes, but years ago I had a
machine at a station which had a multiple in-out sound card (with 8 in's
and 8 out's an M-Audio Delta 1010lt) and I'd set it up to be able to -
from one computer at the station - have 4 different stereo incoming /
outgoing connections at the same time, each one with different audio.
OpenOB was on the back end making it all work.
Essentially I ran several different instances of OpenOB at the studio
each on different ports. I'd establish both send/receive channels
(again on different ports) to each location. On the Studio end I'd
routed it all through Jack. Of course this means with some jack
disconnect/connect commands it is easy to change where audio goes. The
studio end all ran on a single computer, just with multiple instances of
OpenOB.
The biggest trick to keeping it all working was to be very specific
about documenting it all. Without solid documentation it would become
easy to incorrectly route audio to the wrong location.
So as an example:
Remote location 1 talks to Studio computer - OpenOB 1, on a particular
set of ports
Remote location 2 talks to Studio computer - OpenOB 2, on a particular
set of ports
Remote location 3 talks to Studio computer - OpenOB 3, on a particular
set of ports
etc
Studio OpenOB 1, 2, and 3 all ran on the same computer, just as
different processes and using different Jack connections.
Route it all in Jack at the studio. If you want location 1, 2, and 3
all going to the same audio output at the studio then Jack can do that
for you - just route the audio from all 3 OpenOB's to the same audio
card output.
For extra security you might want to consider having the remote
computers establish a VPN connection into your studio. OpenOB by itself
is not secure, I would not recommend using it on the public internet
without some added security layer.
Hope this helps.
>
>
> G'day all,
>
> Is case you have not heard there is a virus thing going around :-)
>
> We are home basing all our radio presenters where possible.
> We have been using openob for obs for some time but only one at a time.
>
> We are now in the situation of having multiple openob trx's at the same
> time (only because they are not switched off) and this, I believe, is
> causing issues.
>
> questions:
> 1. I presume multiple tx's to 1 rx does not work.
>
> 2. I should be able to to run multiple openobs on different ports using
> jack and it will merge everything together? Hopefully.
>
> So so long as only one rx is sending audio we will only hear one feed.
>
> Ideally I would use an audio switch to switch between the various feeds
> but we have no real way of setting this up now.
> We do have this but only one OB input currently. :-(
>
> --
> Mike Phillips
> Coast FM.
> _______________________________________________
> openob-users mailing list -- openob-users(a)lists.talkunafraid.co.uk
> To unsubscribe send an email to openob-users-leave(a)lists.talkunafraid.co.uk
