Just upgrade from 3.2.9 to 3.3.8 on both the client and the server and it has not gone very well. The client now stutters and shows blocking with no audio, as if the client is struggling to receive the signal. I made no changes other than installing (same decoders etc, etc, etc).

Under 3.2.9, the client has never worked properly (freeze after a while, 50% freeze on channel changes, 50% freeze on "Previous Channel"), but other than that, the client worked acceptably.

Here are the logs after the install of 3.3.8.

Any chance I can get the schedule direct fix without installing the entire 3.3.8 because I'm having a dog of a time getting an EPG update with 3.2.9.

With my current configuration (which I've been using since Schedules Direct was created--before GBPVR had built-in support for SD), I use xmltv.exe to download the guide data from SD and then use UltraXMLTV to "enhance" the data before NPVR imports and processes it. The enhancements I use are:

1. Mark new episodes with an "*" so that my recurring recording rules could pick just the new episodes (I pretty sure that NextPVR now has support for this type of functionality when scheduling recurring recordings, but it doesn't have any visible display in the guide to indicate new or not)
   
2. Update the description field to include the original air date
   
3. Add the guests and actors to the end of the description field
   

1. Am I correct that the built-in Guide does not have any visible indication of "new" episodes?
   
2. Are the additional SD fields containing the original air date and guests and actors stored in the EPG table when the built-in SD mechanism is used?
   
3. And, if that data is stored, is there any way to have it displayed in the guide and recordings screens?
   

This one would be more of a minor convenience than anything else. If it would be too much work on your end, then I understand. I just don't know if a command line switch to UpdateEPG exists in the programming or not. Whenever I try to look for command line switches, NPVR just starts the GUI.

When I use XMLTV in conjunction with the UpdateEPG script, the NPVR GUI application can time out, especially with a full channel load. So to be safe I now consider this a two-step process, instead of a one-step process (I run XMLTV independently before UpdateEPG, rather than from the NPVR Scripts).

So I was wondering if I might be able to do it the other way around, start the XMLTV batch file by hand, let it run and complete first, and then let it trigger UpdateEPG via command line. I haven't seen any indication that I might be able to do this. Is this even possible?

Thanks
Chris

The web page appears to not be working.

Edit: I got it working by deleting on old WEB folder and re-installing NEXTPVR.

Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>

You can download 3.3.8 from http://www.gbpvr.com/NPVRSetup_3_3_8.exe

If you're upgrading from a previous release, remember to make sure you stop NextPVR before running the upgrade.

Please post any support issues in the support forum.

Changes:

Quote:- fixed problem with new multi file screen in Recordings screen when a failed recording was present
- major changes to schedules direct support. Schedules Direct have moved to a new API. To support this, there is new screens in NextPVR for managing lineups, entering zip codes etc.
- added support for ATSC major.minor numbers. You can now have channel numbers like "12.2".
- fixed a problem with sort order of new multi file screen in Recordings
- fixed a couple of bugs with the new Freesat EPG option introduced in the last release.
- fixed an unhandled exception that could happen on the Recordings screen
- the multi-record feature is now possible on analog/HDPVR/HDPVR2/Colossus/IPTV/Prime devices. For these types of devices it's not as useful as digital tuners, but still gives some advantages like the ability to get overlapping recordings on back-to-back recordings on the same channel (with padding in both).
- changed app to make it compatible with Microsoft DTV-DVD Audio Decoder for AAC audio.
- colored red/yellow/green/blue flags now included in export/import of recordings
- fixed a problem where re-entering a directory in icon mode could cause the start of the list to become offset, appearing like one or more blank spaces at the start of the list.
- fixed bug with webclient that cause server to try running a music file locally aswell as client.
- adds support for detecting changes to the desktop resolution when running in fullscreen mode (to avoid problem where user was ending up with a fullscreen app not filling the screen after machine had been asleep)
- fixed a problem where trailing slash was not added to new media directories added until the user revisited the settings screen for a second time.
- added support Hauppauge Colossus2.
- slight change to the way the devices tab loads, so that the entire screen is drawn before it goes off looking for devices.
- changed "don't record duplicates" logic to fix a scenario that could occur with multiple recurring recordings picking the same future episodes to record.
- fixed a scenario that could cause Recurring not to be created in the case of a conflict.
- fixed a problem where EPGEvent's would lose all but first genre/cast/crew when stored as cached copy in recording
- install process attempts to create firewall exceptions for NextPVR.exe, NRecord.exe and NDigitalHost.exe. Hopefully this will get rid of some of the HDHR new user problems.
- improvements to duplicate detection logic to better cater for users that switch from mc2xml to schedules direct.
- now forcing a reload of the channel list when a device is deleted, so that the Settings->Channels tab always reflects the correct list of channels
- RECENTLY_DELETED entries now use the current time, rather than the original recording time.
- improved duplicate detection logic to better handle movies.
- fixed a problem where escape key wouldn't back out of select audio/subtitle popup
- fixed a problem with API for updating recurring recording advanced rules.
- PromptForDeleteAfterPlayback no longer prompts for delete if you were watching an in-progress recording
- added a popup to control the DVB Subtitle delay. This popup is accessed via Ctrl-D
- added a work around for channel ids changing in mc2xml generated xmltv files
- added cast/crew support for xmltv
- fixed a crash with DVB scanning on transponder with huge number of channels
- added support for LCN v2 channel numbers, which are starting to be used in some DVB countries (like Singapore etc).
- changes to metadata API to better support multiple metadata plugins.
- added metadata plugin for TheMovieDB
- fixed problem where it would go to the new details screens even when the show didnt have any description, leaving you a very blank screen.
- recurring recordings no longer limit potential recordings to those after the start date of the original show used to create the recording.
- slight change to the way config.xml is saved to resolve issue where user could end up with a corrupt config.xml when their disk was full and it attempted to save the config
- updated NEWA

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.

Thanks

Snag

[ATTACH=CONFIG]39096[/ATTACH]

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.

For the most up-to-date news, look for links on the SD website
http://schedulesdirect.org

Robert Eden
President, Schedules Direct

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?

Many thanks,

B