<div class="gmail_quote"><div>
> 1. How long should I expect commflagging to take? I have "all methods"<br>
> enabled. Comskip (used by GB-PVR and others) consistently took about 4<br>
> minutes on a 1 hours show, same hardware (generally pegging 1 core), and<br>
> uses more detection methods. Detection was at least as good. Commflag took<br>
> about 30 minutes for a 1-hours show last night, though it seemed to run at<br>
> about 20-25% (guessing half of one core due to nice?). I saw at least one<br>
> post that indicated it should be a bit faster than that, but I don't know on<br>
> what hardware. hdparm shows good speed. If others are getting much better<br>
> times, then I'll look for something external to Myth. (I realize it can run<br>
> real-time, but for now I want to resolve this question.)<br>
><br><br>Wow, i didnt realize GB was that fast, i wonder how the other PVR software rate in speed/accuracy.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">
> recording and loading the breaks as a cutlist (Z)? (Did I characterize that<br>
> right?) Doing so seems to change the behavior, notably it seems to autoskip<br>
> even with autoskip off. My search for an OSD with commercial breaks turned<br>
> up "yeah, that'd be cool". Yup. Mostly I am interested in this because of<br>
> #3:<br>
><br>
</div>> 2. Is there any way to see the commercial breaks without editing the<br>Coorect. Not implemented to show commflags in the OSD. You're right - it<br>
would be cool. :)<br></blockquote></div><br><br>I have always thought the OSD and entire Myth interface leaves a lot to be desired. It pretty feature-less but it works. I wish the OSD had a view like TiVo (Where if timeshifting you see what portion of the program you have). But there are limited devs and if I had to choose between a nicer OSD/"Prettyness" or a useful feature (ie Storage Groups or Input Groups) i would choose the later.<br>
<br>Mitchell<br>