I noticed that a few pending recordings suddenly disappeared (granted, I was doing some "upgrades" to the computer so imagine this has a tie in somehow). Anyway, I went to perform a manual EPG update and NextPVR crashed. After the sixth time, I decided that I certainly need some help. Can anyone give me a tip? Logs attached. Thanks in advance.
I see there are function keys for most of the home-screen menu items, but I didn't see any for the Search menu.
If none exists, has anyone come up with their own method? (not using NEWA or any other plugin, etc.)
Thanx.
I thought I would give the "Newbies" and some not so "Newbies" a helping hand with VideoRedo.
I nearly hung myself trying to get VRD to work. So I pieced this together so others wouldn't suffer as I did :o
I use VideoReDoTVSuite (VideoReDo3) but this "should" apply to later versions as well.
2. Move PsExec.exe to some location on your Path, I used "C:\Windows\System32"
3. Open a Command Prompt as Administrator
4. Enter the following (or cut and paste it) ..... psexec -accepteula -s -i cmd.exe ....
(the -accepteula seems to be needed or you will end up with a non 0 return code and VideoRedo will not run, in Windows 10 anyway )
5. Enter the following (or cut and paste it) ..... "C:\Program Files\VideoReDoTVSuite\VideoReDo3.exe"
(change this to suite your installation)
6. The VideoRedo Config Screen should appear, answer the prompts and close down VideoRedo.
7. Enter "EXIT" in the Command Windows (no don't enter the Quotes)
8. Cut and paste the following into a text file (Notepad is Good) and save as "vidredo.reg" ....
The important bit is the "QuietUsesSilentVideo"=dword:00000001
You may have to change "[HKEY_USERS\.DEFAULT\Software\DRD Systems\VideoReDo-TVSuite\Special]" to match your version
This is good for VideoReDo-TVSuite (look in the registry)
9. Double Click on the "vidredo.reg" file created in step 8 to add the entries to the registry
That's it you are finished
Attached is a .BAT file that can be scheduled to run by "Task Scheduler" or run from PostProcessing.bat
It will only process completed recordings, (it looks for the corresponding .xml for the recording)
generated by .... <StoreSeparateMetadataXml>true</StoreSeparateMetadataXml>
NOTE:- All recordings and their related xml files are stored in a single folder ...... NOT SUBFOLDERS
(I can not remember the config file setting for this ....... someone please help :o )
Got it ..... <AutoCreateFolders>false</AutoCreateFolders>
like
RECORDINGS (folder)
Rec1.ts
Rec1.xml
Rec2.ts
Rec2.xml
etc...
I have the location set so the time shows up correctly to me when I post something. Minutes ago I posted a message and it stated I did so at 10:03 am today. This was really done at 1803 on Friday the 13th. Is this a Friday the 13th joke?
I have a scanning issue that I do not know how to solve. I am missing at least one channel that I know should be found because I can view it on my other TV with a cable box. It should be channel 125 (SD) or 625 (HD). There are channels around it so I assume the scanning is set up right.
I went to check C:\Users\Public\NPVR\Tuning\QAM\ to see if that channel was being skipped but I am not sure which .ini it is using.
Recently, after obtaining a cableCARD from Comcast, I bit the proverbial bullet and downgraded my system from Windows 10 Pro to Windows 7 Ultimate. The drivers for my Ceton infinitv 4 USB installed without any difficulty, since I now have Windows Media Center installed. The problem arose when I installed the current version of nextPVR, and began the process of configuration When I entered the details for the first channel, including selecting the appropriate lineup from Schedules Direct, to my display, the Bulk Mapping dialog I had been expecting failed to appear! I have been totally unable to get the bulk mapping feature to work, even after uninstalling the program and manually the nextPVR directory which contained the nextpvr.db3 database! Unless this can be corrected, much as I hate to say this, I'm just about ready to give up on nextPVR, and stick with WMC. HELP!!
Desktop computer has a dual core processor. There are two recordings ongoing at this time and when attempting to watch a live channel, I receive the notice the capture device cannot be found. After recordings finish, that channel is found without any problem. Is this something that would be normal for this computer or should I attempt it again and submit the logs? Comskip would be operating at the same time. Overload?
I am using windows 10 with an Avermedia 7231 analog capture/tv tuner card. I used to have it running on windows 7 with Windows Media Center. However, there was no WMC in Windows 10.
I have looked just about all over the internet trying to find a solution to be able to watch tv again on my Avermedia 7231 card.
This search brought me here and I have the latest version of NextPVR installed. Under settings/devices I see an Avermedia 7231 DVB-T Tuner. From readings the forums I was to install SoftPVR to get the analog version of my Avermedia card. I downloaded WinTV7 and 8 from the Hauppauge website. Next I ran the SoftPVR batchfile softpvr.bat as administrator to get the correct settings. It extracted several .ax and .dll files from the archive.
Unfortunately the settings/devices still only shows the DVB-T version of my card and not the analog version that was supposed to be added to the list.
Honestly, I am real tired after hours of reading, installing, reinstalling, uninstalling, etc. I am living in The Netherlands and get my analog tv from cable. Can someone tell me what I am doing wrong?
I'm currently running NextPVR 3.5.7 and Kodi 15.2 for live tv... Can I use X-NEWA to watch live tv on my iphone/ipad? Currently it seems the iNEWA doesnt work, I get an 'Error processing your request' when i try to go to the tv guide page
My setup is quite solid, but sometimes I get 0 bytes recordings with the "No data deliverd" message. Restarting the recording service seems to fix it. In my logs I see the following line:
Code:
2015-11-11 13:39:00.176 [DEBUG][103] Unexpected error on DVB-C put_TunerRequest: 0x8000FFFF
Recordings that are OK do not have this line in the logs. The logs are attached.