Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: MythTV: Dev
Re: Ticket #10414: HDHomeRun: Bad Recordings (was: Bad, Recordings - Choppy Playback)
 

Index | Next | Previous | View Flat


billstuff2001 at sbcglobal

Mar 11, 2012, 8:52 AM


Views: 302
Permalink
Re: Ticket #10414: HDHomeRun: Bad Recordings (was: Bad, Recordings - Choppy Playback)

If you'd like to see statistics about the recording quality - in
particular, anything bad that was noticed by the HDHomerun library
during the recording - then check out this thread:
http://www.gossamer-threads.com/lists/mythtv/dev/388751#388751

The patch in it logs network, sequence, transport, and buffer overflow
errors from the HDHomerun.

Like this: "HDHRRec(31): HDHR Stats: pkts=1061797 hwm=23 KB Errors:
net=0 trnsprt=0 seq=8 ovflow=0"

I've been using this for years to diagnose screwy recordings.

-Bill

On 03/11/2012 07:00 AM, mythtv-dev-request [at] mythtv wrote:
> Send mythtv-dev mailing list submissions to
> mythtv-dev [at] mythtv
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://www.mythtv.org/mailman/listinfo/mythtv-dev
> or, via email, send a message with subject or body 'help' to
> mythtv-dev-request [at] mythtv
>
> You can reach the person managing the list at
> mythtv-dev-owner [at] mythtv
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of mythtv-dev digest..."
>
>
> Today's Topics:
>
> 1. Re: Ticket #10414: HDHomeRun: Bad Recordings (was: Bad
> Recordings - Choppy Playback) (Daniel Kristjansson)
> 2. Profile builds and debug code (Lawrence Rust)
> 3. Re: Ticket #10414: HDHomeRun: Bad Recordings (was: Bad
> Recordings - Choppy Playback) (Tom Lichti)
> 4. Re: Profile builds and debug code (Jean-Yves Avenard)
> 5. Re: Ticket #10414: HDHomeRun: Bad Recordings (was: Bad
> Recordings - Choppy Playback) (Marc Randolph)
> 6. Re: Ticket #10414: HDHomeRun: Bad Recordings (was: Bad
> Recordings - Choppy Playback) (Daniel Kristjansson)
> 7. Re: Ticket #10414: HDHomeRun: Bad Recordings (was: Bad
> Recordings - Choppy Playback) (Gary Buhrmaster)
> 8. Re: Profile builds and debug code (Lawrence Rust)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 10 Mar 2012 11:41:03 -0500
> From: Daniel Kristjansson<danielk [at] cuymedia>
> Subject: Re: [mythtv] Ticket #10414: HDHomeRun: Bad Recordings (was:
> Bad Recordings - Choppy Playback)
> To: Development of MythTV<mythtv-dev [at] mythtv>
> Message-ID:<1331397663.8739.16.camel [at] t6>
> Content-Type: text/plain; charset="ISO-8859-1"
>
> On Fri, 2012-03-09 at 13:17 -0500, Tom Lichti wrote:
>> On Fri, Mar 9, 2012 at 12:44 PM, Derek Atkins<warlord [at] mit> wrote:
>>> Tom Lichti<tom [at] redpepperracing> writes:
>> I'm trying to rule that out. I don't think it's network or interrupts,
>> I have all Gig-E networking, and the backend is actually a server,
>> Dell Poweredge SC1435, so the only thing I can see is it being the
>> disk. I'll try putting a storage group on another disk and test that
>> and report back.
> I doubt it is the disk. 0.25 dynamically resizes it's buffer up to
> about 128 MB per recording vs the user specified buffer that defaulted
> to 9.6MB in 0.24.
>
> I was able to reproduce a problem with old firmware using udp
> streaming, but with newer firmware employing rtp streaming I
> can not reproduce the issue. I'm also not seeing the high CPU
> usage reported. I see about 15% CPU usage with two recordings.
>
> Can you take a look at this:
> http://www.cyberciti.biz/faq/linux-tcp-tuning/
> And tell me if increasing the rmem_max helps?
> libmythhdhomerun tries to increase the socket buffer
> on startup, but perhaps the rmem_max is set low on
> your system? Mine is set to 131071000.
>
> -- Daniel
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 10 Mar 2012 18:57:19 +0100
> From: Lawrence Rust<lvr [at] softsystem>
> Subject: [mythtv] Profile builds and debug code
> To: mythtv-dev [at] mythtv
> Message-ID:<1331402240.1723.27.camel [at] gagari>
> Content-Type: text/plain; charset="UTF-8"
>
> I've been profiling some Myth functions using the --compile-type=profile
> configure option and noticed that doing so results in Myth linking
> against debug builds of Qt libs. This is selected in settings.pro:
>
> profile:CONFIG += debug
>
> I was wondering what the reason for this was?
>
> I'm of the opinion that profiling should be performed on a release build
> that's instrumented to record time spent etc. If there's debugging code
> left in then the profiling won't be representative or useful to
> optimisers. There's some existing support for removing debug code in
> that configure currently defines NDEBUG for profiled builds.
>
> What do you think? Should debug be removed or left in?
>

_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-dev

Subject User Time
Re: Ticket #10414: HDHomeRun: Bad Recordings (was: Bad, Recordings - Choppy Playback) billstuff2001 at sbcglobal Mar 11, 2012, 8:52 AM

  Index | Next | Previous | View Flat
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.