<div dir="ltr"><div><div><div>Hi JYA,<br><br></div>Thanks for your work on this. It seems to have solved all my issues with watching an in-progress recording exiting when fast-forwarded to real time. Haven't had any other problems with the change. Its greatly appreciated :-)<br>
</div><br></div>Lincoln.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Mar 3, 2014 at 6:22 PM, Jean-Yves Avenard <span dir="ltr"><<a href="mailto:jyavenard@gmail.com" target="_blank">jyavenard@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On 3 March 2014 15:26, Bill Meek <<a href="mailto:keemllib@gmail.com">keemllib@gmail.com</a>> wrote:<br>
> Is this message supposed to be loglevel debug?<br>
><br>
> 2014-03-02 22:08:02.032226 I [4857/4891] MythSocketThread(-1)<br>
> mythcorecontext.cpp:1151 (readyRead) - MythCoreContext: Received remote<br>
> 'FILE_WRITTEN /srv/mythtv-0/recordings/2615_20140303040000.mpg' request<br>
> 2014-03-02 22:08:02.239430 I [4857/4891] MythSocketThread(-1)<br>
> mythcorecontext.cpp:1151 (readyRead) - MythCoreContext: Received remote<br>
> 'FILE_WRITTEN /srv/mythtv-1/recordings/1021_20140303030000.mpg' request<br>
><br>
> I've had over 5300 (with various channels) in the last 10 hours. None<br>
> were from LiveTV, they were scheduled recordings.<br>
><br>
> They were all on a FE which is running: v0.28-pre-931-g2c71895.<br>
><br>
> The message appears in: commit fafc658.<br>
<br>
</div>Yes, those messages appear with loglevel=debug like all messages sent<br>
by the backend.<br>
FILE_WRITTEN is sent by the backend whenever a new file is created in<br>
write mode, and following that, no more than every 10s whenever a file<br>
is being written to.<br>
<br>
Those messages are needed in order to resolve one particular problem:<br>
when watching an in-progress recording, if you were to fast forward<br>
very close to the end, playback would exit.<br>
<br>
The reason was that the frontend had no way to differentiate during<br>
playback between reading a completed recording and reading an<br>
in-progress recording. So if it ever encountered an EOF (End Of File),<br>
it would simply exit, regardless of the backend still writing to the<br>
file or not.<br>
<br>
With those messages, every frontends can keep a record of while file<br>
are currently being written to and those that aren't.<br>
<br>
If during playback it encounters and EOF, if the file is still being<br>
written to by the backend (e.g. an in-progress recording) then it<br>
won't exit when encountering EOF, instead it will retry.<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
mythtv-dev mailing list<br>
<a href="mailto:mythtv-dev@mythtv.org">mythtv-dev@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-dev" target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-dev</a><br>
<a href="http://wiki.mythtv.org/Mailing_List_etiquette" target="_blank">http://wiki.mythtv.org/Mailing_List_etiquette</a><br>
MythTV Forums: <a href="https://forum.mythtv.org" target="_blank">https://forum.mythtv.org</a><br>
</div></div></blockquote></div><br></div>