Although I am not the one doing the logs, I highly doubt the one editing
the logs is doing anything wrong.
I set up all the clocks, and the only timed event is the legal ID every
hour at 59:50.
Yesterday, during his most recent LogEdit, it wiped out half the day,
and said the log would end at 1:30pm (it was around 12). He called me,
I remoted in, and looked at the log, sure enough, there was only an hour
and a half left on the log. Everything past 1:30 was just not there in
RDAirplay.
I unloaded the log, then reloaded the log, and it all came back,
including his edits.
I know I am new, and still have much to learn, but looks like this is a
confirmed bug by at least 2 other users.
Note: RDLogEdit (both on the machine and via win32 setups installed on
local Windows machines) has worked flawlessly. It only seems to be an
issue editing a "Live" log.
-Alan
On 5/28/2014 5:49 AM, Rob Landry wrote:
My gut feeling is that Rivendell is probably doing exactly what you
are telling it to do.
The key to this sort of problem is to assume that the apparently
random behjavior is not in fact random but deliberate. What is making
rdairplay jump to that particular point in the log and not some other?
Are there any times events in your logs?
Rob
On Tue, 27 May 2014, Alan Smith wrote:
Thanks Hoggins! At least I know I am not alone.
I too am using "auto refresh".
Would it help to turn off auto refresh and force them to manually
refresh the log, or does it still happen manually as well?
I would almost rather not go the manual route. I don't know for
certain, but I have a feeling if left up to the staff to manually
refresh, they would forget and log changes would not be aired.
On searching the issue, I found this-not quite my issue, but wonder
if its related?:
http://comments.gmane.org/gmane.comp.radio.rivendell.user/7256
-Alan
On 5/27/2014 5:17 PM, Hoggins! wrote:
Hello Alan,
Happens to me quite often, and I've never been able to understand what
is the common cause. Sometimes it behaves well.
My logs all have "auto refresh on", and the symptoms are *exactly* the
same as described here : either only one part of the log is showing, or
the refreshed log starts at a completely random place.
Hoggins!
Le 27/05/2014 21:03, Alan Smith a écrit :
A couple of times I have had the system that I recently set up get
"confused" in RDAirplay on the log. In some cases it seems to have
jumped out of place, or most recently, it just "forgot" half the day.
I have not witnessed this behavior directly [system is in another
state], but I don't think the person operating it could be doing
anything to cause this issue.
HOWEVER, all that said....what he is doing is using either RDLogEdit
on the machine itself OR the win32 build of RDLogEdit to edit the
CURRENTLY RUNNING LOG.
So is this a bug, OR is it NOT recommended to edit a currently running
log that way [and use RDAirplay itself]?
The issue I *THINK* stems from it "refreshing" the log at the same
instant that it is transitioning from one event to the next in
RDAirplay.
This is all based on the old V2 appliance (RD 2.5.5, CentOS 6.4).
Other than that which has only happened a couple times, things are
working GREAT!!!
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.3469 / Virus Database: 3722/7571 - Release Date:
05/27/14
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.3469 / Virus Database: 3722/7573 - Release Date: 05/27/14
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
