Cheers to all... Some time ago, there were a few folks who shared a directory on their web server to update voice node ID's as a way to exchange between us, for those that recorded a voice id for there node identifier. ( i.e. "the w a n hub" for node 2135 or "U K HUB" for 27066 ) Some of you know exactly what I'm speaking to while others will be completely lost, I understand. But while I was reviewing my scripts in doing a weekly update of new nodes from the server I had, I found what I was using no longer existed and probably has not for some time. I find them attractive if they are done right. Keeping the time to announce shorter while giving more precise info about node location/band. ... So my question is, is anyone doing such a think now, and if so, who/where/details. And if there is more than one, perhaps updating that share between them weekly would be in order to propagate changes so that we are not all relying on just one in the event something happens. I have security issues from time to time as I'm sure others do, so 3 of them make sense to me. I have a interest in keeping this going so if they are all gone, I'm willing to open a directory on one of my VPS servers for that, and/or exchange with others so it is well stored and propagated. All in all, we probably should issue a standard script for those that want to do such a thing (willing to share my sample). But for now, let's see where we are on this. Perhaps I'm just out of date with changes that have been going on. Any info ? I'm sure it would enlighten the group as well as myself. Thanks, ...mike/kb8jnm
On 5/12/18 12:55 PM, Mike wrote:
So my question is, is anyone doing such a think now, and if so, who/where/details.
And if there is more than one, perhaps updating that share between them weekly would be in order to propagate changes so that we are not all relying on just one in the event something happens. I have security issues from time to time as I'm sure others do, so 3 of them make sense to me.
I have a interest in keeping this going so if they are all gone, I'm willing to open a directory on one of my VPS servers for that, and/or exchange with others so it is well stored and propagated.
No need, the system will rsync node announcements about once per day from the main reg server. The main issue with this was finding someone willing to review the files and confirm they work. I've done this for people when asked, but I'm not going to edit or convert files. I can't tell you the number of times I've been sent a 30 second wav file and people expected it to work. I'd love an automated process, but there's not really a good way to do it. Check out node 40821 announcement for a good example (tooting my own horn), but it should be short (7-10s), have the node number and be normalized with clear audio. I know mine took some time in audacity to get just right. Would you be willing to help out with being the reviewer of these? -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net
Very good. Well, I'm still using ACID on 2 servers so, I wasn't aware. But does not help me at this point unless you might just state the server location of the files, I can write my own scripts for retrieving them. Just gotta know where they are. Yes, I fully understand about validity, and the time it al takes away from us for it. A long time ago, a few of us had a directory of known good files, and that directory was read only and one other directory for write/uploads so not to corrupt the good files until reviewed. thanks for the info Bryan, ...mike/kb8jnm On 5/12/2018 1:07 PM, Bryan Fields wrote:
On 5/12/18 12:55 PM, Mike wrote:
So my question is, is anyone doing such a think now, and if so, who/where/details.
And if there is more than one, perhaps updating that share between them weekly would be in order to propagate changes so that we are not all relying on just one in the event something happens. I have security issues from time to time as I'm sure others do, so 3 of them make sense to me.
I have a interest in keeping this going so if they are all gone, I'm willing to open a directory on one of my VPS servers for that, and/or exchange with others so it is well stored and propagated. No need, the system will rsync node announcements about once per day from the main reg server.
The main issue with this was finding someone willing to review the files and confirm they work. I've done this for people when asked, but I'm not going to edit or convert files. I can't tell you the number of times I've been sent a 30 second wav file and people expected it to work. I'd love an automated process, but there's not really a good way to do it.
Check out node 40821 announcement for a good example (tooting my own horn), but it should be short (7-10s), have the node number and be normalized with clear audio. I know mine took some time in audacity to get just right.
Would you be willing to help out with being the reviewer of these?
participants (2)
-
Bryan Fields -
Mike