Recently I wrote a Perl script to synchronize CUTS, CART, /var/snd, and
logs between two Rivendell systems. It wasn't written with remote voice
tracking in mind, but for two of my clients who have Rivendell systems at
transmitter sites that need to be synchronized with the systems at their
studios.
I can only synchronize in one direction, because when two copies of a
table have differences, there's no way for me to tell which is the more
recent. I have to assume that when there's a difference between a record
in a table at the studio and another such at the transmitter, the one at
the studio has been changed and the table at the transmitter needs to be
updated to reflect that. So, if someone makes a change at the transmitter
end, my script will immediately undo it.
In order to use my script to synchronize a remote system used for voice
tracking with another at the studio, it would be necessary to synchronize
in both directions, which could only be done if each record in a log were
time-stamped so the script could tell which direction to propagate changes
in a log.
Rob
On Sun, 2 Mar 2014, John Anderson wrote:
yea...if there is a way to export the voicetracks and logs, and then import
them as a group, the amount of time needed to transport/ftp/get the vt's
over to the main station becomes LESS important, although i would't even
attempt it, if i didn't have a few hours or so, although it and when it
becomes proven, it would be faster.
i don't know if producing an aux voice track log might work, and if that is
the case, could it be called from the mail log?.
I think whatever is done, if anything, if you really want to voice track in
the large market sense, you'll likely need a pretty good connection,
although i don't see why it won't work!
Course, not being a programmer, i don't know how this all goes together..
-----Original Message-----
From: rivendell-dev-boun...@lists.rivendellaudio.org
[mailto:rivendell-dev-boun...@lists.rivendellaudio.org] On Behalf Of Cowboy
Sent: Sunday, March 02, 2014 1:30 PM
To: rivendell-dev@lists.rivendellaudio.org
Subject: Re: [RDD] Voicetracking over a slow connection - what works best?
On Sunday 02 March 2014 12:52:13 pm John Anderson wrote:
Assuming that you did all of the voice tracks on a different Rivendell
machine in a different location, could you then make up some type of
transport package, that would send all of the voice tracks at one time,
the
as a final step, patch the updated log into the main log?
rsync -auOP --compress-level=9 user@source::/var/snd/PATTERN
user@dest://var/snd/
This is the way I'd consider first.
Of course, I'd run...
rsync -auOPnvh --compress-level=9 user@source::/var/snd/PATTERN
user@dest://var/snd/
first, to make sure it's going to do what I think it will.
--
Cowboy
http://cowboy.cwf1.com
The First Rule of Program Optimization:
Don't do it.
The Second Rule of Program Optimization (for experts only!):
Don't do it yet.
-- Michael Jackson
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
---
This email is free from viruses and malware because avast! Antivirus protection
is active.
http://www.avast.com
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
