After installing 1.5.36 I'm having a problem with TVListings, as reported here. When watching any video through TVListings (live, in process, or completed recording) I get bad stutter and high CPU (SD ~60%, HD ~70%). When watching the same files with TV Guide or Recordings, video plays smooth and CPU is low (SD ~15, HD ~40). I don't see anything in the new logs attached, which at the end show watching the same program live with TVListings first then with TV Guide.

What other causes can I look for?

Thanks

I want to put together a new HTPC, I'd like it to be capable of playing HD content (blu-ray disks, and H.264 encoded videos), and also be able to record two channels simultaneously. If possible I would like for the tuners to support HD viewing and recording (for which I guess I'd need a DVB-T2 tuner).

I currently have a Hauppauge WinTV Nova-T PCI, if a DVB-T2 tuner is not an option for now, then would re-use my Nova-T, would it be better to purchase an additional WinTV Nova-T PCI to have two tuners, or would a single dual tuner card (such as the Nova-TD-500) be a better option? Are dual tuner cards as good as getting individual tuner cards (any advantages/dis-advantages)? Would anyone recommend a different DVB-T card instead of the Nova-T or Nova-TD-500? Does anyone also have any opinions on the USB tuners over internal cards, do they perform as well?

For the other components I was looking at something along the lines of an Intel Core i3 540 3.06GHz with 4GB (2x2GB) of RAM. Still undecided about the motherboard, but will depend on whether I end up going for a dual tuner or two single tuners, and whether the tuners are PCI or PCI-E, depending on those points will need to look at a relevant board that has enough PCI or PCI-E slots.

I considered an Atom based system, but wasn't sure whether that would be able to handle a situation such as playing a HD movie while recording two channels, or would it? Also looked at the Athlon II range, they seem well priced and a little more energy efficient than the i3's, but

Is the integrated GPU on the i3s good enough for H.264 content decoding or would I need to look at a purchasing a dedicated graphics card?

Would appreciate any ideas or suggestions, thanks.

Alibert,

Is there any chance that similar to "create link" from theTVDB.com could be implemented for Amazon? What I am really looking for is an easy way to get the movie poster for recorded movies and maybe some rating info as well?

The theTVDB.com linking works fine now with one exception (found so far). The show "Christine" (the new adventures of old Christine) refuses to link. All other shows found links fine. Logs attached.

Finally, If a show cannot be found due to the translated name in the XMLTV is there any way to manually fix the link? For example the show "two and a half men" is in my EPG Guide translated to "2 1/2 män" which does not return anything.

Thanks,

\\Anders

Sub,

Quote:1.5.36
- added ability to bring up OSD TV Guide during playback of video files. Previously it was only available during live tv.

Hi.
Firstly thanks for new nPVR release!
There is a problem with AR if VMR7/9 is in use, look on picture (problem was there in older nPVR too):

This one it "fast shot" from LiveTV.
It happend on all videos undepended on used decoder.

It can be "fixed" by using EVR, but that will kill DxVA on WinXP, so it is useless.
There is no such issue in GB-PVR or if i play video in Graphstudio.

BTW, "capture screenshot" will be usefull feature

EDIT:
LOG

*suspect*

Oh hi Alibert, long time not written. *buck*

After upgrading to TV Listings 3.2.1 i have a small problem while idle within the TV Listing menu: NPVR.exe just crashes after a few minutes (around 7 minutes) (nothing pressed, nothing moved, nothing opened, just idle).

This thread will contain the current version of Universe Plugin, a UPnP client for NPVR 1.5.36+

Current version 1.02 2010-12-30

To install uncompress and run the executable. It comes with only the default skin, but the skin from WebRadio will be used if found in other skins.

Martin

I am developing a linux npvr client. For playback I use mplayer using streaming from http://server:8866/stream?f=... , but I have problem with seeking the media. The source of the problem seems to be that the server does not report Accept-Ranges: bytes unless a range is specified in the http request. As a result mplayer does not recognize the stream as seekable.

For example:

wget -S .... would give you:

HTTP request sent, awaiting response...
HTTP/1.1 200 OK
Server: N-PVR
Connection: Close
Content-Length: 1410023424
Content-Type: application/octet-stream

while wget -c -S .... on a partially downloaded file would give you.

HTTP/1.1 206 Partial Content
Server: N-PVR
Accept-Ranges: bytes
Content-Range: bytes 14557832-1410023424/1410023424
Content-Length: 1395465593
Content-Type: application/octet-stream
Connection: close

I do not know whether this is the proper behavior and mplayer is buggy or there is a bug in the NPVR server?

At the moment I solved the issue by hacking mplayer, but this does not seem a viable solution if the bug is indeed in the NPVR server.

I have just installed TV Listings 3.2 on the server in the following order:

- Disabling NRecord.exe, closing NTray.exe
- Install TV Listings 3.2
- Enabling NRecord.exe, starting NTray.exe
- Startup NPVR and go to settingsscreen
- Activate TV Listings and TV Recordings Plugin
- Shutdown NPVR.exe
- Startup NPVR and go to settingsscreen
- Configuring TV Listings 3.2 Plugin (2 Guides, 1 for analog TV, 1 for digital TV)
- Shutdown NPVR.exe
- Startup NPVR and go TV Listings 3.2

Getting this one:
"Unbehandelte Ausnahme - Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt"

Hi,

I've just uploaded a new version of the TVListings plugin at the wiki.

Changelog:

Quote:- fixed a bug where the what's new list was based on universal time
- fixed a potential threading problem in recordings lists
- added combined skin parameters for recording list items representing 'selected' and 'preview image' state
- included new default skin
- added option to define the channel header type