Runaways are rare these days but seem to be relate, for me, to scheduling a recording RS whilst a recording is in progressDoes not have foxlink installed but has had a runaway recording.
Does not have foxlink installed but has had a runaway recording.
There were quite a lot of runaways reported when RTS was first introduced but the most common cause was fixed a year ago since which there have been very few runaways reported, some but not all, appear to be related in some way to the use of Foxlink.I had a runaway recording when RTS was being introduced. RTS was enabled at the time the runaway happened.
I seem to recall reports of occasional runaways being linked to RTS. After my runaway I disabled RTS and haven't had a recurrence, although of course that proves nothing.
The experience of finding 35hr / 80Gb recording was fairly alarming so I haven't been tempted to use RTS since, which is a pity.
It is is probably worth giving RTS another try - most users seem to have few problems.
Thanks for the tip. I'll give it another try!
I use Arbookmarks to get to the beginning of my padded recordings. I do find that the beginning mark is accurate but the end mark is often in a random position (eg, a third of the way through, five minutes past the end of the recording or no end mark at all).Do we have any tools that will analyse a recording and report where the AR points actually are?
Is that the right way round as the previous poster is describing a problem with padding?Under the covers arbookmarks is stripts -X but it wont work on a recording made using AR instead of padding,
Strangely I also had a run on recording last night, the BBC News at 10 ran until until I shut down the box with remote control a bit after midnight.
I had that on a runaway AR recording last night .In my case, on all occasions this has occurred, the box controls have frozen and will not respond to the front panel or remote. The web i/f is still working, but the only way to stop the recording if it is still going is to switch off mains power.