This is where I ran into a problem. I did EXACTLY as you suggested
below. But Jack does not start and the carts didn't have any effect on
the connections. The command line I entered
inRDAdmin->ManageHosts->JackSettings is identical to what I use in my
script.
Any additional suggestions or sample data?
On 6/19/2014 4:23 PM, Fred Gleason wrote:
On 6/19/14, 16:07 39, Dave B wrote:
At first I didn't realize I could set up non-Rivendell Jack connections
in rd.conf. So, as long as Jack is started first and RDAirplay (or other
RD module) is started second...the connections will be made per the
[Jack Session] section of rd.conf.
You can, but it's deprecated in current Rivendell versions. The
better way is to create a macro cart that sets up the routing you want
(using the 'Connect Jack Port' ['JC'] and 'Disconnect Jack Port'
['JD'] RMLs), then set that as your 'Startup Cart' in
RDadmin->ManageHosts. This has the significant advantage that the
routing rules will now live within your RD database (and hence be
backed up up automatically as part of the regular backup regime).
Likewise starting jackd(1). Look in
RDAdmin->ManageHosts->JackSettings to configure it to start
automatically when the Rivendell service starts. Be sure to specify a
valid JACK command line. You can also specify other clients you want
started there.
Cheers!
|----------------------------------------------------------------------|
| Frederick F. Gleason, Jr. | Chief Developer |
| | Paravel Systems |
|----------------------------------------------------------------------|
| A room without books is like a body without a soul. |
| -- Cicero |
|----------------------------------------------------------------------|
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
