We do the same thing with a VPN to access the server’s SQL.
We then run rsync from cron to send new voice tracks to the server and update
local /var/snd from the server.
It works ok.
Patrick
> On Mar 1, 2019, at 5:54 PM, Peter Claes wrote:
>
> Mark,
>
> I have the same question.
> We log
Fred:
Is there an approximate target date for the first release of 3.x ?
Rich
On 3/1/2019 09:53, Fred Gleason wrote:
On Fri, 2019-03-01 at 11:06 -0600, Alan Smith wrote:
On a more general note...is the 2.x branch going to be put to rest in
favor of the 3.x branch, or will they be developed
Mark,
I have the same question.
We log in over VPN. so we can access the database on server, works pretty
neat.
At the moment I am only syncing from server to client. (mounting
/var/snd.server, and copying that to /var/snd)
But for syncing client to server (certainly multiple clients) I am not
Greetings
While trying to compile 3.0 on Ubuntu 18.04-2
make stopped with this all recursive error
schemamap.cpp:105:13: warning: In the GNU C Library, "minor" is defined
by . For historical compatibility, it is
currently defined by as well, but we plan to
remove this soon. To use "minor",
I've been wondering how one might go about providing a remote staff member or
voice tracker with a full copy of a Rivendell system featuring all of the audio
and other data and then synchronizing their system with the system back at the
radio station? Is there a fairly easy way to do this? Is
Daniel,
On Fri, Mar 1, 2019 at 1:05 PM Daniel Kahn wrote:
> I am testing the Ubuntu Rivendell 3.0.0beta00. So far everything looks
> real nice. The problem I am having is that the Rivendell daemons are
> running as root. This is a problem if you want to use a jack server.
> Jack would have
I am testing the Ubuntu Rivendell 3.0.0beta00. So far everything looks
real nice. The problem I am having is that the Rivendell daemons are
running as root. This is a problem if you want to use a jack server.
Jack would have to run as root and then all other clients as well. This
is not
Too bad on no more updates to the 2.x branch. I was just starting to
feel comfortable :-)
But otherwise, AWESOME news! Thanks for all that you do!
-Alan
On 3/1/2019 11:53 AM, Fred Gleason wrote:
On Fri, 2019-03-01 at 11:06 -0600, Alan Smith wrote:
On a more general note...is the 2.x
On Fri, 2019-03-01 at 11:06 -0600, Alan Smith wrote:
> On a more general note...is the 2.x branch going to be put to rest in
> favor of the 3.x branch, or will they be developed in conjunction?
At this point, there are no further releases planned for the 2.x
branch, short of a major bug or
On Fri, 2019-03-01 at 11:06 -0600, Alan Smith wrote:
> Will we get this feature addition (ticking the appropriate box to
> suppress them) in the 2.x branch? Or is it in there and I missed it?
It will *not* be added to the v2.x branch.
Cheers!
Will we get this feature addition (ticking the appropriate box to
suppress them) in the 2.x branch? Or is it in there and I missed it?
Thanks!
On a more general note...is the 2.x branch going to be put to rest in
favor of the 3.x branch, or will they be developed in conjunction?
We are
11 matches
Mail list logo
