Odd sounds/graphical glitches in all recordings.

[pilgrim2223]

So on Tuesday I reset my switch that sits between my HDHR and my NPVR server... All Tuesday recordings clear as a bell, perfect in every pixel.

I think I may have a hint as to where I'm dropping packets (which would explain the sound and pictures glitches) may go get a new switch (or dig in the bin, pretty sure I've got a spare here somewhere) and see what I get. I really don't think it's NPVR or a setting therein, positive it's something else!

[pilgrim2223]

So doesn't seem to be the switch after all... Grrrr...

So here's a question. My NPVR is running on an old I5 with 4 gigs of RAM with Windows 7 Home Premium as the OS. Spec wise is that enough?

I get some recording that are crystal clear (all my nerd stuff last week came through great) but live TV/recordings off most channels get artifacts/sound drops. It's not a deal breaker but it is annoying. Should I move all of this to a bigger better, meaner computer?

[BrettB]

So doesn't seem to be the switch after all... Grrrr...

So here's a question. My NPVR is running on an old I5 with 4 gigs of RAM with Windows 7 Home Premium as the OS. Spec wise is that enough?

I get some recording that are crystal clear (all my nerd stuff last week came through great) but live TV/recordings off most channels get artifacts/sound drops. It's not a deal breaker but it is annoying. Should I move all of this to a bigger better, meaner computer?

Is your temp buffer file location (used for the live TV) on the same drive as your default recording directory? Normally, NPVR is just taking a digital stream and recording it to disk, so it does not need much power (CPU and RAM).

Most of my recordings are great. But I have found that when several (6+) simultaneous recordings are all going to the same drive, I tend to have artifact issues like you describe.

Just a thought...

[scJohn]

You had mentioned in a prior post that you watched Live TV for an hour on the server using VLC without any problems. Correct? VLC uses their own codecs, not anybody else. So the tearing is happening on playback from the client. What codec(s) are you using on the client? What is the client?

[pilgrim2223]

Is your temp buffer file location (used for the live TV) on the same drive as your default recording directory? Normally, NPVR is just taking a digital stream and recording it to disk, so it does not need much power (CPU and RAM).

Most of my recordings are great. But I have found that when several (6+) simultaneous recordings are all going to the same drive, I tend to have artifact issues like you describe.

Just a thought...

Live tV is one thing... nice to see it happening on their as well, but this also shows up in Recordings. The Temp Buffer directory is on the server itself. Also I never do more than 2 at once... Makes me wonder, what is the speed on your HDD? I wonder if I tossed a 5200 in there and that's causing issues? MAy be worth exploring... And while it does the tearing on all recordings it's worst on the one night I'm doing two at once.

You had mentioned in a prior post that you watched Live TV for an hour on the server using VLC without any problems. Correct? VLC uses their own codecs, not anybody else. So the tearing is happening on playback from the client. What codec(s) are you using on the client? What is the client?

Yes and no. As mentioned above it happens in recordings as well. Watch the stream in VLC was direct UDP into the HDHR.

Live TV via NPVR or Recording from NPVR where I've seen issues is:
VLC
KODI
And NPVR Client all on an I3 8 gig Windows 10 machine that is CAT 6 to the NPVR server with a single Gigabyte Switch between them. (The NPVR client is using FFDshow) the server doesn't use the client for any playback but has the MS-DVD DT or whatever they're called configured for the giggles.

Also because I'm "That guy" I've tried used one of my other servers as a client and saw the same on live, and for the fun of it hooked my phone in over EMBY and saw the same.

So now I'm wondering if the local server codecs matter? I had it set to all disabled and had no problem getting recordings off it. I figured the record service wasn't using any.

[scJohn]

Just throwing thing at the wall to see what may stick. I would make sure that your server has valid video/audio codec settings. Can't hurt. Maybe the power supply for the SD is going bad. Strange things will start to happen when the power supply starts to go bad: device will drop of the network, the green LED on the front will look dim, the signal becomes weak ( reports are that the second tuner is effected first). I think that SD can test your device and tell you if the power supply is going bad.

[sub]

In the HDHomeRun Setup app, try temporarily setting the 'application' to "NextPVR" to see if it helps. Anything else sends a lot more data across the network, and I wonder if you network just isn't keeping up.

VLC going direct to the HDHomeRun doesn't use their BDA drivers, so doesn't use this application setting, but only sends the single channel rather than full transport stream. When you use the "NextPVR" setting it'll also only send a single channel. Any other selection will send the full transport stream.

[pilgrim2223]

This one is an off one from the start.

I don't have an "Application setting" there is a BDA Compatibility Mode, which I've always had set to NextPVR. I figured this was a classic Silicon Dust not updating instructions (something I've run into for years now)
So when I first setup I used:
http://my.hdhomerun.com/instructions/sof...extpvr.php

As my guide.
but step 3: On the Applications tab, set the Main Application to Other:ATSC/QAM.
I don't have an application tab, and Other:ATSC/QAM isn't an option under BDA compatibility mode

Now as to behavior... Using BDA Compatibility set to NextPVR and I set 8.1 and 8.2 to record at the same time it only uses one tuner, telling me that the entire transport stream is there and not just the current channel. (this is HDHomeRun Setup Version 20161119) Wonder if there's a better BDA Compatibility to use... I also wonder what BDA is.

options in BDA comp is:
Default
NextPVR
WMC
MediaPortal
JRiver
For the Record
Easy HDTV DVR


And while it could be bad network... certainly possible, I think It's more likely that the computer I re-purposed for this job is cursed (Lenovo Thinkstation M91p which doesn't support Anything past Win 7 or Ubuntu 11.1... seriously I think it's cursed!) The network is Tested CAT6 into a Gigabyte Switch (which is also possibly cursed) The HDHR and the Server are on the same switch.

so now I've set up a completely separate Windows 10 I7 with 32 gig or RAM (it was on Sale) and a Long history of not being cursed. Tonight I will record 24 legacy on both the existing and my new hot version (different tuners for each) So 2 computers direct connected to the same switch, using the same HDHR... Let the Battle BEGIN!!!!

[pilgrim2223]

think this kinda answers it...

But first fun fact. Two full streams running full out on a single switch slows that switch down something fierce!

So old cursed computer:
[ATTACHMENT NOT FOUND]

Bigger meaner computer that I didn't want doing this job:
[ATTACHMENT NOT FOUND]

As close to same frame... And I swapped ports on the Switch today just to be sure... so I think I can say that it's the stupid old cursed computer. I really think the built in NIC has trouble interacting with my HDHR... I'll possibly get a new NIC for it, or storage the silly thing and just use my bigger rig for the job.

So with any luck this is the end of this particular saga with me using a different computer (I'll toss a secondary drive in it to hold recording and call it good) Thanks for all the input and help! Still curious about BDA compatibility and the difference it makes!