OK, maybe I'm misunderstanding some things... but I purchased an HDHR Plus to replace my ancient (original) HDHR because it had "H.264 support".
So, I dropped it in as a straight replacement, configured everything, and did a test recording... the file is definitely much smaller (< 1 GB for ~20 mins of video, would have been > 2 GB previously), but this is what mediaanalyzer tells me is in the ts file (see attachment).
**Edit - I was wrong about the file duration, it's 5 mins & change, not 20
I thought it'd be recording H.264/x264 natively (?).
I've come across a problem and I can't seem to figure it out. I've set a reoccurring recording for "the flash" on channel 1007 which should have recorded tonight from 8pm-9pm. It shows up in the web interface as a "reoccurring recording" but it doesn't show it as pending on 10/28/2014 from 8pm-9pm which is the next scheduled showing. In the NPVR interface it doesn't show up in the "reoccurring recording" list either. Strange... anyone have any ideas what's going on? I've included logs and a few other files I thought might help those smarter than me figure it out or at least point me in the right direction.
Since Schedules Direct has sent out an email letting people know about changes to the service on Nov 1, I thought it'd be worth letting you know what's happening from a NextPVR perspective.
NextPVR has been updated to support the new interface they've provided. This new 3.3.x release of NextPVR will be available in the next day or two. From a user's perspective, it'll look just like any other upgrade, and things will keep working. This release is largely ready, we're just working through a last minute thing that popped up in testing.
If you don't update to the new version, things should continue to work to. The Schedules Direct guys have created a service that looks like the old service, for old apps that haven't been updated for the new service. The new version of NextPVR does not use this legacy-look-a-like service, and instead moves to their new native json service, which offers some advantages like quicker update times etc.
Will this effect NPVR in any way (mail i received below as i use them)....
Schedules Direct has been operating since 2007 to provide a stable
environment for non-commercial media applications to receive TV listings
data, but that does not mean things never change! This may be our
first email-blast since 2007!
We have been informed that Gracenote (formerly Tribune Media Services)
will be ending the guide data service currently used by most members of
Schedules Direct. Their plan is to end support for this service on
November 1, 2014. Schedules Direct was already hard at work
implementing replacement services.
Please check with your application's support page for your best
solution. Some applications have chosen to use a new SD-JSON service
that offers a richer data set, while others have chosen to use the
SD-DD service, which is meant to be a drop-in replacement for
Gracenote/Tribune's service.
If your application is no longer supported, there's no reason to worry.
Most apps can continue to function with a change to your system's hosts
file. (details in the SD forum).
Last week I asked Tribune to update their DNS to force half of the
traffic to the SD-DD servers. The concept was for people with problems
to fail half the time now, rather than 100% come Nov 1. If you're one
of the folks having problems, check with your application team or us to
help resolve it.
Got email this morning from SD announcing their major service change away from Tribune/Gracenote. Did some forum searching and it seems that NPVR testers and sub are busy with this.
What do we normal users need to do to switch to the new SD-DD interface?
I've just bought myself an Intel NUC (D54250WYKH) to try out as a prototype NPVR client. It's very nice and with NPVR 3.2.9 and Windows 8.1 runs HDTV very happily at about 20% CPU usage. I'm using ffdshow for the video decoding and lav for the audio (both courtesy of SAF). I'm quite happy with that, but I did notice that by default, ffdshow wasn't taking advantage of the Intel Quicksync hardware decoding on the HD5000 video chipset. The odd thing is that when I reconfigured the ffdshow decoders to use the hardware decoding instead of libavcodec, the cpu usage went up noticeably, lipsync went out and the video developed a distinct stutter.
I'm not concerned, because the i5 CPU is more than up to the job of the software decode, but it struck me as odd, so I thought I'd put it out here to see if wiser heads could suggest why. I did think of buying the cheaper Celeron version to give it a try, but without the hardware decode working, it might struggle.
I'm trying to figure out the best options for playing back a recording in progress. In all cases, when I've tried, it stops playback once it reaches the amount of time i started the recording from -- i.e., I i started at 10 minutes into a 1 hour recording, after ten minutes playback ends even though there is another 10 minutes of video.
I've tried both Direct and Timeshift modes. I increased the Pre-buffer to the max. None of these had any effect.
I saw on another post about sharing the time shift folder on the NextPVR server, but I didn't see where I set this in the configuration options for X-NEWA.
This may be our
