djsoft said:
nelson c said:
Today a power cut made disaster in the RadioBOSS configuration.
The disc has disabled the option "Cache to increase speed", to avoid this problem, and yet this didn't work.
Can you improve this?. I have attached the profile files and error reports
The correct way to solve this problem is to eliminate power outages in the first place. Use UPS, it will keep the computer up for 20-30 minutes and correctly shut it down in case there's still no power (you'll need UPS which connects to PC via USB). UPS is a must have for any PC, especially ones which used for broadcasting.
RadioBOSS already creates one backup copy of each settings file. In your case it seems both copies were damaged... It's nothing more RB can do apart from making backup copies, and it already does so.
Also, from bug reports I see that you're using the previous version (5.2.0.10) - I'd suggest you to install the latest one (5.2.3) as it contains lots of various fixes and improvements.
I am aware that the ultimate solution is a UPS, but at this time it is not possible for the economic factor.
At this time we have on the one hand the studios of radio station, RadioBOSS is where used for the emission to air, which it is important to be able to save the settings. and in transmitting plant there is another PC with RB that only receives streaming.(which virtually never anything is changed, even the position of the window is what you want to freeze.) Screenshot attached.
At the moment we're saving to install other two FM transmitting stations in different cities in the which initially there will not be a person intended to control all the time that everything is working well.
We have the need to install everything as soon as possible, so at first nor will there be UPS.
These PC configuration, will be the same as we have in the transmitting plant of the unique frequency that we have in the air at the moment.
So if this problem happened here, also it could be repeated in any of the other transmitting plants installed, and we want to minimize the likelihood of these problems.
djsoft said:
nelson c said:
Also would be good thing to "Freeze the configuration of RadioBOSS" or set the profile as "Read-only" so that these things do not happen.
This instance that failed only is used to play streaming, but it has a lot of settings that are never modified (or rarely).
So have frozen profile would be very stable.
This can be frustrating, with frozen settings you'll be unable to change anything, even some minor setting (e.g. window position and size, etc).
What you offer is fighting with symptoms, but fighting a cause (power outages) is way more effective and reliable.
You can "freeze" settings like this: set everything up as needed and create a backup copy. Then, if something goes wrong, you can simply restore from that backup.
You can also try "freezing" if you play with settings folder access rights (you can make it effectively read-only for RB). I'm not sure, however, how RB will behave under those circumstances, probably you'll see lots of "unable to write to..." error messages.
You're right about this.
On the backing of the profile, is really a feature very useful.
The problem is that if a profile is damaged, RadioBOSS does not load the profile from the backup automatically, this was what caused the cut from 4 pm. (I was advised by a listener that the radio was the silence)
Perhaps with the feature "When unable to load profile, restore the BackUp configuration..." would be good.
Anyway you have reason above that the problem itself is not caused by RadioBOSS.
If we can make work RadioBOSS with a read-only profile, this would be the ultimate solution to the problem, already profile not to break ever.
I'll try then as RadioBOSS behaves with a read-only profile. I'm going to disable logs (that do not use for anything), and the "CurrentSong.txt" file will be moved to my documents.
Not opened any problem to RadioBOSS alert that there are problems of writing (except that this generates a high CPU usage).
I'll know if it works then.
