I can control the OSD playback text elements a little better after some Jarvis changes, and I was wondering what you prefer, highlighting the show name or episode name (Kodi style)?
So after upgrading to Windows 10 I noticed that the font in NextPVR (DroidSans) would render in bold everywhere. I much prefer how it renders in Windows 7, which is as the skin is designed to, with bold for titles and normal weight for descriptions. Normal weight fits more on screen, and looks very elegant and readable. It also bugged me that there was a bug.
The fix is:
1) Install the DroidSans and DroidSans-Bold fonts as system fonts. To do so, right click the font files, select "Install".
2) Edit Global.xml in the skin folder, changing all instances of font="DroidSans" to font="Droid Sans". Note the space that is added.
I've attached an updated Global.xml, and example pictures.
Perhaps this could be added to the next installer?
For information: It appears that the error arises from a change in the way Windows handles font families. It is now particular in how it looks for font weights/styles. When using a non-system font, it seems to default to the first approximate match it finds in the folder. It is looking for the Droid Sans font name, and will find it no matter the font's filename. However, if the bold weight font is first in the file order, it uses that for everything. For example, if A.ttf is Bold, and B.ttf is Normal, it will render everything in bold. Swap the file names, and everything renders in Normal. It appears that DroidSans-Bold.ttf is considered to come before DroidSans.ttf. However, it doesn't appear to proceed to find the bold weight after finding the normal weight. The only solution I have found is installing as system fonts. Note then it is important that Global.xml uses the correct font name for the font family, i.e. Droid Sans with a space.
I am running the latest NextPVR on Win7 Pro(x86) using the Hauppague WinTV Dual HD USB.
I have solved this issue, but I decided to post it just for the record in case anyone else experiences this.
A couple of months ago I began to investigate why my computer was mysteriously hanging (total lockup, no access to keyboard, mouse, etc.) and not going back to sleep on occasion. After examining all logs and ruling out the usual suspects, including running memtest for hours on end, I finally decided to rule out the antivirus I had been running.
While auditioning replacements, I decided to tryout other free AV's.
I use Avira on my other computers without any issue, so I thought I would give it a shot here. I have high confidence in this AV. But then, this is where things got weird ...
After I installed Avira and rebooted, everything looked good. The NextPVR services started as expected. Launched the NextPVR GUI, and looked in settings. The WinTV tuners were there and ready to go.
Tried launching live TV, and got an on-screen error something like "failed to start Hauppauge WinTV-dualHD ATSC Tuner 2". Tried several more times, same error. I tried excluding all of the NextPVR services and folders in Avira, without improvement. Nothing in Windows Event Viewer could be found related to this event.
Uninstalled Avira and the problem went away. I eventually found another AV solution that worked.
This event occurred back on May 24th, so my main NextPVR logs don't go back that far. However I did find a file in npvr\logs "ndigitalhost-26.log.3.txt" that captured this event:
Just tried NextPVR and found out that not all my tuners can scan channels.
I attached logs of unsuccessful scanning by MyGica T230.
Where can be the problem?
In MediaPortal the tuner works perfectly.
Wondering if anyone can help. I've searched around and did see a very old post about people having recordings stop short if they were back to back, but I'd imagine that would be fixed by now. The problem I'm having is that some of the recordings i have stop short. I have attached my log files if someone has some cycles to take a look.
here is a sample of the recording in question...(found in NRecord.log)
any ideas?
16-06-12 21:58:00.348 [DEBUG][10] Preferred filename is 'The Odd Couple.S05E07.The Odd Candidate'
2016-06-12 21:58:00.358 [DEBUG][10] allocating recording target filename: \\NAS-SRV\common\shared\recorded\The Odd Couple\The Odd Couple.S05E07.The Odd Candidate.ts
2016-06-12 21:58:00.358 [DEBUG][10] About to start recording (19946 on 22): \\NAS-SRV\common\shared\recorded\The Odd Couple\The Odd Couple.S05E07.The Odd Candidate.ts...
2016-06-12 21:58:00.358 [DEBUG][10] Asking NDigitalHost to start: \\NAS-SRV\common\shared\recorded\The Odd Couple\The Odd Couple.S05E07.The Odd Candidate.ts
2016-06-12 21:58:01.358 [DEBUG][10] Temp at 6/12/2016 9:58:11 PM
2016-06-12 21:58:01.358 [DEBUG][10] Started recording (19946:13:\\NAS-SRV\common\shared\recorded\The Odd Couple\The Odd Couple.S05E07.The Odd Candidate.ts)
2016-06-12 21:58:01.388 [DEBUG][10] No C:\Users\Public\NPVR\Scripts\ParallelProcessing.bat
2016-06-12 21:58:01.398 [DEBUG][52] catalog says:
<Catalog><Version>1</Version></Catalog>
2016-06-12 21:58:01.588 [DEBUG][42] Done fanart.tv lookup
2016-06-12 21:58:02.138 [DEBUG][78] Using URL: https://json.schedulesdirect.org/20141201
2016-06-12 21:58:02.288 [DEBUG][78]
{"account":{"expires":"2017-04-25T04:29:20Z","messages":[],"maxLineups":4},"lineups":[{"lineup":"USA-OTA-91104","modified":"2016-06-11T16:09:43Z","uri":"\/20141201\/lineups\/USA-OTA-91104"}],"lastDataUpdate":"2016-06-13T02:13:51Z","notifications":[],"systemStatus":[{"date":"2015-09-08T00:00:00Z","status":"Online","message":"No known issues."}],"serverID":"20141201.web.2","code":0}
2016-06-12 21:58:02.508 [DEBUG][52] Downloading metadata and artwork took + 1109.9878ms
2016-06-12 22:02:00.051 [DEBUG][10] Stopping recording (19543 on 20). Past end time of recording. 64
2016-06-12 22:02:00.081 [DEBUG][10] StopStream(40)
2016-06-12 22:02:00.631 [DEBUG][10] StoreMetaData@1
I have combed through the NRecord logs and I'm pretty sure the blaster never gets called unless it is a new channel number. This would make sense if the set top box was never used manually but that is not the case here. If I change my Directv box to another channel directly then the next recording will be of the wrong channel unless the new recording channel happens to be different from the last recording.
Why conserve blaster calls? This almost has to be intentional. Is there a setting?
Thanks
Dennis in Minneapolis
NPVR 3.6.6 Win7 AMD system. Hardwired serial/usb control of directv box via custom code and "DirecTV Control.exe" utility
I use NEXT-PVR since years, since it was known as GBPVR. I always use it with internal or USB tuner/receiver. Now i have a DD Octopus NET DVB-C/C2/T2 Box and i use it with DVB-C. My Cable Provider is Untimedia in Germany.
The tuner/receiver is shown in the device list (TYP SAT>IP) but since now i am not able to find some channels. In the Device Dialog i can't find any Configuration for DVB-C only DVB-S, i think.
Is it possible to get this device work with NEXTPVR?
