On Thu, 2013-05-30 at 14:29 +0100, Wayne Merricks wrote: > Getting stuff from point A - B isn't too bad but you need to deal with > file replication and MySQL replication separately.
File replication is done with rsync. in our case material that is provided as mp3 is distributed as mp3 and carted at each remote as well as on the master server > > File replication is quite trivial, the easiest thing I've found to > setup recently is Bit Torrent Sync which is like a private peer to > peer version of drop box. If you're only working with Linux AeroFS > might be better but I think its limited to 10 users on the free > version as it interacts with AeroFS servers in some way. rsync is hard to beat. > > MySQL is a bit trickier but you could set up a slave replicator on the > satellite sites for the CARTS and CUTS tables. Just be aware that > you'll inadvertently be overwriting play counters and the like with > whatever is on the master. we run the remote log here on a second playout slot on the master machine and that updates the play counters on the master, we also get the master to cat all material being sent to the remote so the CARTS and CUTS tables have correct durations. We have a group of 'local' carts for each remote. Some items get downloaded at both server and remote at the same time so mysql has correct durations for cart. remotes can caart and run stuff between mysql refreshes and this works for stuff that has short TTL like breaking news. > > Being a bit cleverer about it you could always make some sort of > script that only deals with new songs. So if you have a new songs > folder it looks up the cart and cut info for that cart number and then > performs an insert query on the slave machines. rsync all music 1am gets all new cuts loaded yesterday. Logs are run 10 days out so there is a 10 day lag before new music is played. If it's really critical to get new stuff in you just run the script and recreate the log. > > Only problem with that is potential cart number collisions if the > satellite sites are importing their own CARTS / CUTS. By allocating a set of News Weather Sport for each remote youre off the dodgems and on the merry go round. > > Expanding on that, what about using Bit Sync to get the files across. > Then have someone drop them into an import folder. You could then > script a lookup on the master server for all the marker info and > attach that to the new cart number you get from rdimport. I already > did something similar as a batch import from a Dalet system so it is > possible to do. hard to go past rsync -av -e 'ssh -p ???? -i /root/.ssh/id_dsa_alexi' --delete --bwlimit=500 --include="001???_*.wav" --include="00092?_*.wav" --include="007???_*.wav" --exclude="0?????_*.wav" x.x.x.x:/var/snd/ /var/snd run every hour uses port shifted ssh, logs in with no password alexi is remote host, limits bandwidth to keep server stable, 1000 carts are ads, 920 carts are news for this relay, 7000 are all 'local' items for this relay and exclude everything else on this hourly update, the "all" update runs at 1am. the script then pulls down a mysql dump of the carts and cuts to ~/dropbox #then we import the files into local server mysql -u root Rivendell </home/rd/dropbox/hourly.sql we have 2 independents running off the on server here, and the only problem was solved by choking the bandwith to each one. We schedule the connects so each has a window for download/update. Might be improved with a gigabit card in the server which is due for an upgrade after having been on for 5 years. the remote can run without updates for 7-10 days because logs are ready that far out. Of course the fine tuning that happens close to air time is lost, but the longest we have has broadband out was about a day, when there was a local service provider issue, and I was out of town. Murphy! regards Robert > > Regards, > > Wayne > > On 30/05/13 13:28, Alan Smith wrote: > > > Darn...Is there an easy way to get audio from point A to point B > > while maintaining to overlap/meta info? > > > > Go easy on me...I am a Windoze guy (hopefully soon to be > > Ex-Windoze). > > > > We are a group in Memphis with a lot of small market stations spread > > around the country. We would like to be able to do some production > > here and get it there if that is possible. I am still learning > > alot. I have the remote access down and all that, this I believe > > would be the icing on the cake. > > > > Thanks! > > > > -Alan > > > > On 5/30/2013 7:22 AM, Geoff Barkman wrote: > > > > > Hi alan > > > The seque and fade points are stored in the mysql database. Not > > > inside the audio file to the best of my knowledge. > > > Many thanks > > > Geoff > > > > > > sent by geoff on his android phone > > > > > > On May 30, 2013 10:19 PM, "Alan Smith" <[email protected]> > > > wrote: > > > If I export an audio file, then lets say email that file > > > to another person who uses Rivendell and they import it, > > > will the segue/fade points be maintained, or will they be > > > lost? > > > > > > While on the subject....what (if any) info will be lost > > > during an export process like that? Is all the > > > metadata/overlap info stored within the audio file itself, > > > or is is stored separately in the database? > > > > > > Thanks! > > > > > > -Alan > > > _______________________________________________ > > > 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 > > _______________________________________________ > 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
