Obviously, internal voicetracks are not a problem.
-----Original Message----- Are you guys missing that fact that most, if not all voice track systems have local matched libraries in multiple locations, and the only thing that is transferred is the actual voice track itself, with it's internal "enclosed data" to put it where and when it runs? So you are not actually working on the machine/station that you are doing VT's on. If you are making vt's for four or five other markets, they send you the log, the music and timings match, you bring up the log and do the vt's at your location, then the system transfers the finished VT's ONLY to the end station, but isn't sending the music, or attempting to operate the local machine. (99.5 percent of the time, it works, it is funny when a stations library isn't updated properly!) -----Original Message----- From: rivendell-dev-boun...@lists.rivendellaudio.org [mailto:rivendell-dev-boun...@lists.rivendellaudio.org] On Behalf Of Morten Krarup Nielsen Sent: Sunday, March 02, 2014 8:19 AM To: User discussion about the Rivendell Radio Automation System Subject: Re: [RDD] Voicetracking over a slow connection - what works best? I've tried option 1. There's a 20/20 fiber connection in both the studio and at my home. At best it works a little slow, but I can live with that. Some times the log gets corrupted though. We store our music in wav. It would work faster if you work with MP3. I thought about using Bittorrent Sync for /var/snd but haven't done any experimentation yet. 2014-02-28 16:17 GMT+01:00 Keith Thelen <kthe...@kanabec.net>: Hello all! I know there's no official remote voicetracking feature at this point. But from digging through past posts, I gather there's people out there who have managed to assemble something that accomplishes the same function, more or less. As I see it, there's at least two ways of doing this: 1) Provide the person who will be voicetracking with a computer running Rivendell, let them connect over a VPN, tweak things to obtain acceptable results. (There seems to be a few ways in which people have done this. local copy of the library, a patch that reduces log writes, etc. What are the best techniques here?) 2) Provide the person who will be voicetracking with a copy (printed, text, PDF, whatever) of the log in question, and receive a pile of individual voicetracks which must then be imported and placed. (This seems like an ugly solution, but on a technical level it's the simplest. Who, if anyone, is doing this? What tricks have you used to reduce the labor involved?) Any hints would be appreciated. don't want to reinvent the wheel if I can help it. --------------- Keith Thelen Kanabec Systems _______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev _____ <http://www.avast.com/> This email is free from viruses and malware because avast! Antivirus <http://www.avast.com/> protection is active. --- 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
