<div dir="ltr"><div>t<font size="2">hanks. I got this when I enabled extra logging (verbose logging for record and mysql I think) :</font></div><div><font size="2"><br></font></div><div><font size="2">
</font><p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;font-family:"Calibri",sans-serif"><font size="2"><span lang="EN-US">MPEGRec[3](/dev/video1): Got Resolution 1280x720....<span></span></span></font></p><font size="2">
</font><p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;font-family:"Calibri",sans-serif"><font size="2"><span lang="EN-US">(HandleResolutionChanges)
MPEGRec[3](/dev/video1): Old bitrate 13500/20200 VBR<span></span></span><span lang="EN-US"> .....<br></span></font></p><p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Calibri",sans-serif"><span lang="EN-US"><font size="2">RecThread
recorders/mpegrecorder.cpp:1512 (SetBitrate) MPEGRec[3](/dev/video1): New
bitrate 9000/13500 kbps VBR</font></span></p><p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Calibri",sans-serif"><br></p><p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Calibri",sans-serif"><font size="2">This is the weird part: neither the 'old bitrate' nor the 'New bitrate' settings match my actual settings, which is 13500/6500, so I cannot figure out where these numbers are coming from! </font><br></p><p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;font-size:12pt;font-family:"Calibri",sans-serif"><span lang="EN-US"><font size="2"></font><span></span></span>
</p></div></div><br><div class="gmail_quote"><div dir="ltr">On Mon, Oct 8, 2018 at 9:11 AM Dan Wilga <<a href="mailto:mythtv-users2@dwilga-linux1.amherst.edu">mythtv-users2@dwilga-linux1.amherst.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 10/5/18 4:11 PM, john wrote:<br>
> On 2018-10-04 9:49 a.m., mythtv-users2 at <a href="http://dwilga-linux1.amherst.edu" rel="noreferrer" target="_blank">dwilga-linux1.amherst.edu</a> <br>
> (Dan Wilga) wrote:<br>
>> I recently noticed that my free disk space was creeping downward, and<br>
>> decided to investigate. I discovered that many recordings made since I<br>
>> switched from 0.28.2 to 29.1 are consistently larger--sometimes double<br>
>> or triple in size.<br>
>><br>
>> Looking further, I noticed that the bitrate of the HD-PVR (not HD-PVR2)<br>
>> recordings seems to be much higher than it should be. SoI checked the<br>
>> recording profiles in mythtv-setup. I have confirmed that the recordings<br>
>> rules in question are using my Low Quality profile, which has this for<br>
>> all three (low, med, high) resolutions:<br>
>><br>
>> Avg. Bitrate: 4500 Max. Bitrate: 6200<br>
>><br>
>> What is clear is that recordingsdon't seem to be using this value.<br>
>> Taking the output of mediainfo from a 0.28.1 recording and comparing it<br>
>> to that of a 29.1 recording of the same program on another night gives<br>
>> this diff:<br>
>><br>
>> # diff /tmp/1 /tmp/2<br>
>> 5,6c5,6<br>
>> < File size : 835 MiB<br>
>> < Duration : 33 min 25 s<br>
>> ---<br>
>> > File size : 2.52 GiB<br>
>> > Duration : 33 min 24 s<br>
>> 8c8<br>
>> < Overall bit rate???????????????????????? : 3 490 kb/s<br>
>> ---<br>
>> > Overall bit rate???????????????????????? : 10.8 Mb/s<br>
>> 21c21<br>
>> < Duration : 33 min 25 s<br>
>> ---<br>
>> > Duration : 33 min 23 s<br>
>> 23c23<br>
>> < Bit rate : 2 929 kb/s<br>
>> ---<br>
>> > Bit rate : 9 891 kb/s<br>
>> 35,36c35,36<br>
>> < Bits/(Pixel*Frame) : 0.047<br>
>> < Stream size : 700 MiB (84%)<br>
>> ---<br>
>> > Bits/(Pixel*Frame) : 0.159<br>
>> > Stream size : 2.31 GiB (91%)<br>
>> 48c48<br>
>> < Duration : 33 min 26 s<br>
>> ---<br>
>> > Duration : 33 min 24 s<br>
>> 58c58<br>
>> < Stream size : 91.8 MiB (11%)<br>
>> ---<br>
>> > Stream size : 91.8 MiB (4%)<br>
>><br>
>> At the same time, while a recording is ongoing, the output of "v4l2-ctl<br>
>> -l" gives these values:<br>
>><br>
>> video_encoding (menu)?? : min=0 max=2 default=2 value=2<br>
>> video_bitrate_mode (menu)?? : min=0 max=1 default=1 value=0 flags=update<br>
>> video_bitrate (int)??? : min=1000000 max=13500000 step=100000<br>
>> default=6500000 value=13500000<br>
>> video_peak_bitrate (int)??? : min=1100000 max=20200000 step=100000<br>
>> default=9000000 value=20200000<br>
>><br>
>> The recording bitrates are maxed. It's as though the values in the<br>
>> profile aren't being used, even though they are in the range of<br>
>> acceptable values (once you multiply by 1000). Can Anyone else with an<br>
>> HD-PVR confirm this?<br>
>><br>
>> -------------- next part --------------<br>
>> An HTML attachment was scrubbed...<br>
>> URL: <br>
>> <<a href="http://lists.mythtv.org/pipermail/mythtv-users/attachments/20181004/3a7bbf8b/attachment.html" rel="noreferrer" target="_blank">http://lists.mythtv.org/pipermail/mythtv-users/attachments/20181004/3a7bbf8b/attachment.html</a>><br>
>><br>
> I'm seeing the same thing on 29. Opened a bug report (13317) with more <br>
> information a little while ago, but don't know if anyone's looking at <br>
> it or whether this also occurs in 30/testing.<br>
><br>
> It happens to me with my HD-PVR recordings immediately on upgrade from <br>
> .28 to 29-fixes (using Mythbuntu PPA). Bitrate settings from Recording <br>
> Profiles in Mythtv-Setup are applied just fine to recordings in .28, <br>
> but on upgrade to 29 they are ignored, and some sort of <br>
> what-looks-like generic settings are applied to all HD-PVR recordings <br>
> instead: 720p records with VBR at 9000/13500 kbps, regardless of <br>
> settings in Mythtv-Setup being set to 13500 average bitrate and 6500 <br>
> for max bitrate which should, I believe, result in CBR at 13500.<br>
><br>
> I verified by checking the recordings from .28 and 29fixes both with <br>
> mediainfo, and also by checking in-progress recordings by running the <br>
> v4l2-ctl command to display bitrate info (sorry at work and don't <br>
> remember exact command).<br>
><br>
> As you would expect, I also see smaller file sizes and a decrease in <br>
> video quality with the lower bitrate recordings on 29, despite the <br>
> fact that the Recording Profile settings for the HD-PVR are unchanged.<br>
><br>
> I tried swapping in a new hdpvr power supply and a replacement hdpvr <br>
> board to eliminate hardware issues but got the same results. Tried it <br>
> out on a test machine with a fresh install to eliminate corrupted <br>
> database possibility, got same results: bitrate settings work in 28 <br>
> but are no longer applied once I upgrade to 29.<br>
Over the weekend I enabled extra logging (-v record:info) on my backend. <br>
In my case, I can see "Checking Resolution" and "Got Resolution" log <br>
messages when it enters MpegRecorder::HandleResolutionChanges, but it <br>
doesn't alter the bitrate. It thinks the rate is already correct.<br>
<br>
I think I need to add some more logging, to see what values are present <br>
when it first enters this method. This will take some time, as I don't <br>
want to adversely affect WAF.<br>
</blockquote></div>