<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 6 March 2013 21:45, Anthony Giggins <span dir="ltr"><<a href="mailto:seven@seven.dorksville.net" target="_blank">seven@seven.dorksville.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><div class="h5">On 6 March 2013 02:50, Roger Siddons <span dir="ltr"><<a href="mailto:dizygotheca@ntlworld.com" target="_blank">dizygotheca@ntlworld.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>On Tue, 05 Mar 2013 10:20:38 -0000, <<a href="mailto:phipps-hutton@sky.com" target="_blank">phipps-hutton@sky.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I get a segfualt at the end that is fixed with this patch:<br>
<br>
</blockquote>
<br></div>
Good spot. What logging are you using? Have you tweaked it further? And how did you detect this ?<br>
It occurs on the last line and doesn't affect functionality but I'm concerned that I don't see any indication of this on my system, even though it must be segfaulting every time.<div><br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
I've not used this very long but is it waiting for the next set of silences before recording the last advert break? It just seems to take longer to record a break than I was expecting.<br>
<br>
</blockquote>
<br></div>
It does. On a typical programme, this design will only flag the 1st advert when it reaches the 2nd. It seemed elegant when only comflagging completed recordings, which is what I did until a couple of days ago.<br>
I rarely watch in-progress recordings and only tacked this on as a result of our recent discussions. So it is currently rubbish at flagging in-progress recordings!<br>
I'm currently re-designing it to work effectively - v2 ETA ~1 week.<br>
<br>
Moreover, I noticed yesterday that a comflagging job still doesn't flag a programme that you're watching (for my shoddy testing I only ran the script manually). I was hoping to get v2 out before anyone noticed, but the fix for that is to change silence.py #156 to:<br>
<br>
# player update message needs prog id (with time in Qt::ISODate format)<br>
progId = str(chanid) + '_' + str(starttime).replace(' ','T')<div><div><br>
<br></div></div></blockquote></div></div><div>Hi Roger,<br><br></div><div>how did you determin your silence.presets?<br><br></div><div>trial and error or do you have some script you can run over recordings?<br><br></div>
<div>I find this works fine with the defaults on most Australian channels but there are a few which it detects no ad's. ie.Nine Digital<br>
<br></div><div>Cheers,<br><br></div><div>Anthony <br></div></div><br></div></div></blockquote><div>ignore me just saw the line just below it in the wiki<br><br>"Once you understand the logging information you can easily tune your
own channels/programmes by experimenting with the --preset option
directly from a command line until you get decent results. For example;
<pre> silence.py --chanid 1004 --starttime 20130117220000 --loglevel debug --preset "-80,,3,,180"<br>"<br><br></pre><pre>Cheers,<br><br></pre><pre>Anthony <br></pre> </div></div><br></div></div>