Re: [RDD] Voicetracking over a slow connection - what works
On Tue, 2014-03-04 at 18:19 +, Jim Stewart wrote: > It would be nice to know how to “restore” the database via an > automatic script at the remote end (been using rdadmin manually). > Perhaps I can use a mysql restore command of some sort? I don’t know > mysql at all, have had issue with it, am afraid of it, and finally > consider it Rivendell’s worst attribute. this is a script I use to dump a file for each of my 'out stations' from the central server. it runs at :45 as a cron job The remotes are "Wireless" "Thames" and "Whangamata" Data for all services is kept in the central server. This is a belt and braces update. Seperately each remote service pulls down their weather and other local items as an mp3 file from the same server. The updates complete by :52 and locally stations pull down news and other items which they load from :55 to :59, updating their local version of mysql Some programmes are loaded in the central server for all stations and the audio gets networked as mp3 and loaded locally because updating wav files is a bit data intensive. All music updates are distributed at 1am which works because we typically add only a few tracks each week. this is the server script #! /bin/bash # get tables related to individual services and put them in dropbox mysql -u root Rivendell -e 'show tables like "%ireless%" ' -s --skip-column-names | xargs mysqldump Rivendell -u root >/home/rd/dropbox/wireless.sql mysql -u root Rivendell -e 'show tables like "%hangamata%" ' -s --skip-column-names | xargs mysqldump Rivendell -u root >/home/rd/dropbox/whangamata.sql mysql -u root Rivendell -e 'show tables like "%hames%" ' -s --skip-column-names | xargs mysqldump Rivendell -u root >/home/rd/dropbox/thames.sql #get tables all services need to update and put them in dropbox mysqldump -u root Rivendell --lock-tables=false AUDIO_PERMS CART CLOCK_PERMS CLOCKS CUTS EVENT_PERMS EVENTS GROUPS SCHED_CODES SERVICE_PERMS SERVICES LOGS>/home/rd/dropbox/hourly.sql exit 0 at the remote station we rsync the station.sql and hourly.sql into a local folder from the central server mysql -u root Rivendell /home/rd/dropbox/hourly.sql mysql -u root Rivendell /home/rd/dropbox/station.sql I could have made it smarter and tidier, but this transports the essential changes in small text files that move fast and are 100% accurate. mysql makes this kind of thing possible, and enables Rivendell to function as it does. Well worth making friends with! I got a mysql for dummies book and while I think I am just a novice I have learnt to do stuff with it. Very powerful tool. regards Robert Jeffares ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
[RDD] Voicetracking over a slow connection - what works
My dream setup would be to use Jack Audio's "Netjack" over the Internet using the new Opus Codec so to have very low latency pre and post cut audio transported near-real-time to the remote site during voice tracking, then a simple rsync script that moves the recorded audio back to the main Rivendell library. Anyone want to tackle this? The most I got working was the older "CELT" codec working with Jack audio over the Internet about a year ago, but it wasn't as reliable as I had hoped, but probably good enough for voice tracking. There might also be a problem (for us anyway) as it looks like Opus currently doesn't not support the 44.1kbs sample rate that we have all of our library and have our Jack Audio running at. But maybe this would be a simple patch to fix? I would hate to have to resample. As far as the database issues, I have had good success (despite warnings in the Rivendell documentation saying otherwise) using the RML command to snapshot the database at about 1:30am then rsyncing it off to the remote site so that it is somewhat current for the next morning's use. It would be nice to know how to "restore" the database via an automatic script at the remote end (been using rdadmin manually). Perhaps I can use a mysql restore command of some sort? I don't know mysql at all, have had issue with it, am afraid of it, and finally consider it Rivendell's worst attribute. ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Voicetracking over a slow connection - what works best?
As an aside, don't expect to turn on mysql replication and have applications magically start syncing between sites. I have yet to find an easy transparent mysql replication layer that you can plug underneath existing applications without things dying horribly. The only way I've managed to get something like this to work on in house applications is active/slave and then I had to rewrite all the database calls so that all the reads came from the local slave and the writes went to the master for the remote sites. You could in theory use MySQL clustering but my head exploded when I tried to implement that without code changes. Its much easier to designate one box as the "all writes happen here" and use the slaves as read slaves. Its also nice to turn on replication to have a slave for backups so you can do mysql dumps on large tables without impacting performance on the main host. Wayne Merricks The Voice Asia On 03/03/14 16:28, Fred Gleason wrote: On Mar 3, 2014, at 10:46 49, Cowboy wrote: If you were so inclined, you could check and compare the timestamps on the files in /var/lib/mysql/databasename/tablename.MYI between the two ( or three, or... ) machines and know which is the most recent No, No, NO - you do *not* want to do this! MySQL makes extensive use of internal file caching as a technique for boosting performance. The only time that the timestamps on the actual files can be taken as indicative of the true state of things is after doing a FLUSH TABLES WITH READ LOCK call (perhaps — InnoDB tables can get you in trouble here) or ideally if the mysqld(8) daemon is shut down. A setup where two MySQL instances update each other is known as ‘active-active replication’. It can be done, but it requires careful application design to ensure that updates to a particular table are wholly confined to one or the other of the instances (a technique known as ‘data sharding’). The consequence of violating this rule can be data collisions in things like column auto-increment values, which in turn will halt replication and require manual intervention to recover from the inconsistent state. Cheers! |-| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |-| | Like the ski resort of girls looking for husbands and husbands looking | | for girls, the situation is not as symmetrical as it might seem.| |-- Alan McKay| |-| ___ 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
Re: [RDD] Voicetracking over a slow connection - what works best?
On Mar 3, 2014, at 10:46 49, Cowboy wrote: > If you were so inclined, you could check and compare the timestamps > on the files in /var/lib/mysql/databasename/tablename.MYI between the > two ( or three, or... ) machines and know which is the most recent No, No, NO - you do *not* want to do this! MySQL makes extensive use of internal file caching as a technique for boosting performance. The only time that the timestamps on the actual files can be taken as indicative of the true state of things is after doing a FLUSH TABLES WITH READ LOCK call (perhaps — InnoDB tables can get you in trouble here) or ideally if the mysqld(8) daemon is shut down. A setup where two MySQL instances update each other is known as ‘active-active replication’. It can be done, but it requires careful application design to ensure that updates to a particular table are wholly confined to one or the other of the instances (a technique known as ‘data sharding’). The consequence of violating this rule can be data collisions in things like column auto-increment values, which in turn will halt replication and require manual intervention to recover from the inconsistent state. Cheers! |-| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |-| | Like the ski resort of girls looking for husbands and husbands looking | | for girls, the situation is not as symmetrical as it might seem.| |-- Alan McKay| |-| ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Voicetracking over a slow connection - what works best?
That, sir, would be absolutely awesome ! Le 03/03/2014 01:22, Fred Gleason a écrit : > Hi John: > > This is an area of active work here right now. Specifically, the goal is to > be able to write changes to a log in the form of a sequence of operations on > a known base state rather than rewriting the entire log. Sort of a > ‘diff/patch toolchain' for logs. This would get us a number of Good Things, > including Undo/Redo capability when editing logs and the ability to have > multiple users simultaneously working on the same log (including voice > tracking) without train wreck. > > Cheers! ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Voicetracking over a slow connection - what works best?
On Mon, 3 Mar 2014, Cowboy wrote: If you were so inclined, you could check and compare the timestamps on the files in /var/lib/mysql/databasename/tablename.MYI between the two ( or three, or... ) machines and know which is the most recent That would tell me which copy of the table has been most recently modified, but not necessarily which copy of a particular record is the most recent. Consider announcer A, inserting a voice-track at home, while B is making a last-minute addition to the Saturday log in the studio. If my script relies on the timestamp of Saturday_LOG, then either A's work or B's gets undone, depending on which of them finishes first and the timing of the cron job that runs the script. Rob ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Voicetracking over a slow connection - what works best?
On Monday 03 March 2014 06:43:08 am Rob Landry wrote: > 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. Actually. If you were so inclined, you could check and compare the timestamps on the files in /var/lib/mysql/databasename/tablename.MYI between the two ( or three, or... ) machines and know which is the most recent -- Cowboy http://cowboy.cwf1.com "Kirk to Enterprise -- beam down yeoman Rand and a six-pack." ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Voicetracking over a slow connection - what works best?
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
Re: [RDD] Voicetracking over a slow connection - what works best?
On Mar 2, 2014, at 12:52 13, John Anderson wrote: > Item #3 is the key to make the experience usuable. I looked at the network > traffic of the Voicetracker program when saving, inserting, and modifying a > track and there appears to be quite a bit sent. From looking at the code, > the entire log seems to be sent to MySQL each and every time there is a > slight change to the log. With a fully loaded log, this can take 30-60 > seconds of a reasonable link where there is network management in place. > These sorts of things are reasonable to expect in most radio envioronments. Hi John: This is an area of active work here right now. Specifically, the goal is to be able to write changes to a log in the form of a sequence of operations on a known base state rather than rewriting the entire log. Sort of a ‘diff/patch toolchain' for logs. This would get us a number of Good Things, including Undo/Redo capability when editing logs and the ability to have multiple users simultaneously working on the same log (including voice tracking) without train wreck. 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 Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Voicetracking over a slow connection - what works best?
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
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
Re: [RDD] Voicetracking over a slow connection - what works best?
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? Say, if you did a 2 hour show, you might send 12 or so voicetraacks, then one updated log to be imported?. If the transport package first put the track data in place, the log should find it with no problem. 3. Modification of source code for the Voicetracker to reduce MySQL traffic Item #3 is the key to make the experience usuable. I looked at the network traffic of the Voicetracker program when saving, inserting, and modifying a track and there appears to be quite a bit sent. From looking at the code, the entire log seems to be sent to MySQL each and every time there is a slight change to the log. With a fully loaded log, this can take 30-60 seconds of a reasonable link where there is network management in place. These sorts of things are reasonable to expect in most radio envioronments. There was a patch that was released to only transmit the log on modification, or on final save if the actual voicetrack was changed. I modifed several source files on 2.8.1 and was able to get this to work. It still is very chatty with MySQL, and has some times where there is a large delay in sending the full log. All said, this patch makes remote voicetracking possible versus unusable. The basis of the patch is here, it will need to be manually modified to work with newer versisons: https://www.mail-archive.com/rivendell-dev@lists.rivendellaudio.org/msg00421 ..html \ --- 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
Re: [RDD] Voicetracking over a slow connection - what works best?
Hello, I've been working with this too in trying to voicetrack remotely from a satellite office to a central office with some success. The issue we face is limited bandwidth over a VPN. Here is the approach I tested: 1. Sync files with a Cloud Service like SpiderOak This type of service ($10/month or so) allows for reasonable prices, backup, and easy distribution across multiple nodes on the WAN. Configure /var/snd on all machines to be "synced" and updated files appear on all nodes almost instantly. Compared to RSync, this service does a much better job managing the network traffic. Also - use MP2 as the back-end for files. 2. VPN for the MySQL database connection 3. Modification of source code for the Voicetracker to reduce MySQL traffic Item #3 is the key to make the experience usuable. I looked at the network traffic of the Voicetracker program when saving, inserting, and modifying a track and there appears to be quite a bit sent. From looking at the code, the entire log seems to be sent to MySQL each and every time there is a slight change to the log. With a fully loaded log, this can take 30-60 seconds of a reasonable link where there is network management in place. These sorts of things are reasonable to expect in most radio envioronments. There was a patch that was released to only transmit the log on modification, or on final save if the actual voicetrack was changed. I modifed several source files on 2.8.1 and was able to get this to work. It still is very chatty with MySQL, and has some times where there is a large delay in sending the full log. All said, this patch makes remote voicetracking possible versus unusable. The basis of the patch is here, it will need to be manually modified to work with newer versisons: https://www.mail-archive.com/rivendell-dev@lists.rivendellaudio.org/msg00421.html RDLogedit was designed for local network access, and thus we see this sort of behavior. Architecturally, it would great to modify RDLogedit to work over a WAN. This would require: 1. Migrating to the Web Services vs. MySQL for data 2. Modification of the Client and Server component to transmit only Deltas of the log 3. Implementation of some sort of locking mechanism for when the log is being edited Short of these modifications, the only thing I could think of was to use the patch suggested above. Maybe we could get this put into the general code base if it tests out alright? I'd be happy to share the modified files with the development team if they would like to consider putting it into the code base - please email me privately. Brian On Sunday, March 2, 2014 12:11 PM, Fernando Della Torre wrote: I Think rsync'ing your /var/snd to the local machine would help a lot. After recording you could rsync back only the voice files. Anyway accessing MySQL over a WAN link it's not the optimal. Regards. 2014-03-02 10:19 GMT-03:00 Morten Krarup Nielsen : 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 : > > >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
Re: [RDD] Voicetracking over a slow connection - what works best?
I would think that a better way might be to be able to set up different VT groups/numbers for remote VTs, on a station/host AND SHOW basis, then as long as the remote station has the same library (or at least the same music library) you should be able to do the vtracks and have them inserted into the log the station previously sent. Different group numbers hopefully will prevent duplications, if local vts were done after the log was sent, as the remote numbers could not be duplicated in the log by anyone else? -Original Message- From: rivendell-dev-boun...@lists.rivendellaudio.org [mailto:rivendell-dev-boun...@lists.rivendellaudio.org] On Behalf Of Fernando Della Torre Sent: Sunday, March 02, 2014 12:11 PM To: Morten Krarup Nielsen Cc: User discussion about the Rivendell Radio Automation System Subject: Re: [RDD] Voicetracking over a slow connection - what works best? I Think rsync'ing your /var/snd to the local machine would help a lot. After recording you could rsync back only the voice files. Anyway accessing MySQL over a WAN link it's not the optimal. Regards. Atenciosamente, Fernando Della Torre Tecnologia da Informação *: +55 16 98137-1240 *: +55 16 99137-2886 *: <mailto:f...@vdit.com.br> f...@vdit.com.br V.D.I.T. Soluções em Virtualização A utilização deste e-mail não implica em autorização ou outorga de poderes para seu usuário praticar qualquer ato em nome das empresas citadas, cuja representação considera-se válida se praticada exclusivamente por representante legal ou procurador devidamente constituído, na forma estabelecida em seu respectivo estatuto ou contrato social 2014-03-02 10:19 GMT-03:00 Morten Krarup Nielsen : 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 : 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 ___ 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
Re: [RDD] Voicetracking over a slow connection - what works best?
I Think rsync'ing your /var/snd to the local machine would help a lot. After recording you could rsync back only the voice files. Anyway accessing MySQL over a WAN link it's not the optimal. Regards. Atenciosamente, *Fernando Della Torre* Tecnologia da Informação (: +55 16 98137-1240 (: +55 16 99137-2886 *: *f...@vdit.com.br * V.D.I.T. Soluções em Virtualização A utilização deste e-mail não implica em autorização ou outorga de poderes para seu usuário praticar qualquer ato em nome das empresas citadas, cuja representação considera-se válida se praticada exclusivamente por representante legal ou procurador devidamente constituído, na forma estabelecida em seu respectivo estatuto ou contrato social 2014-03-02 10:19 GMT-03:00 Morten Krarup Nielsen : > 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 : > > 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 >> > > > ___ > 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
Re: [RDD] Voicetracking over a slow connection - what works best?
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 : 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
Re: [RDD] Voicetracking over a slow connection - what works best?
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 : 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 --- 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
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 : > 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 > ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Voicetracking over a slow connection - what works best?
Sorry if it may sound strange, but what if we could use a mix of VNC, jackd and CELT codec? Rivendell would be at the station, we could connect remotely using VNC and the sound could be sent/received to/from remote location using a local jackd, netjack and CELT codec. I have no idea of how would be the delay, but it may be worhy the try. Sorry if it seems stupid, it was just an idea. Regards Atenciosamente, *Fernando Della Torre* Tecnologia da Informação (: +55 16 98137-1240 (: +55 16 99137-2886 *: *f...@vdit.com.br * V.D.I.T. Soluções em Virtualização A utilização deste e-mail não implica em autorização ou outorga de poderes para seu usuário praticar qualquer ato em nome das empresas citadas, cuja representação considera-se válida se praticada exclusivamente por representante legal ou procurador devidamente constituído, na forma estabelecida em seu respectivo estatuto ou contrato social 2014-02-28 12:17 GMT-03:00 Keith Thelen : > 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 > ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
[RDD] Voicetracking over a slow connection - what works best?
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
