Trying to record only nz dvb-t on underpowered 2.6 celeron
xp sp3. playback on apacer al460. Tuner is a wand usb stick,
chip is Afateck IT9135.
Installed all software as per wiki.
On first run multiple errors occurred,kept going,set to record
total tvnz mux,at this point npvr crashed. however recording
service started and recorded successfully. All channels on mux
played back glitch free on AL460.
After reboot all errors in UI of npvr disapeared, program appeared
to be working ok. However all further recordings are unplayable.
apacer reports audio data error. picture is large blocks of color,
audio is loud pops and whistles which locks up the apacer.
Have tried multiple reinstalls with out success.
I know what I`m trying to do is achievable as first run proved.
Questions: On a straight TS record,does any processing take place,
I would have thought not.If so what minimum codecs are required?.
Do I need to write a bda capture file, if so were does it go.
Do I just copy and past to bda.inf.
Remembering none of these were present in my first succesful capture.
Thanks for any help or ideas offered.
So, my cable company (Comcast) hasn't been able to figure out how to properly pair/activate their CableCard with my DCR-2650 yet. Hence, I can currently only use it to record/watch ClearQAM channels. Perfect time to test how NextPVR handles non-subscribed/unauthorized channels, right? That's what I thought, so this morning (8:54 in the logs) I gave it a simple test.
I was using the NMT client and tried to watch channel 831 (AMC HD). If I try to watch it in Windows Media Center with the DCR-2650, I get a message saying the channel is not subscribed. When I tried it with NextPVR, the recording service appears to have begun recording it. And it generates a .ts file. In the nrecord.log file I see multiple "Renew lease ok (0x5FC0004)" messages. I think that those are new for the DCR-2650 device. I'm not sure if they are good, bad, or indifferent...
On the NMT client, the screen just went black and then it hung. The logs.zip file contains a putty.log from the NMT client for Martin to look at.
I also made a similar "unsubscribed" recording earlier, and I tried playing it on the server pc with NextPVR.exe. It shows the black screen for a few seconds, but then goes back to the recordings list and marks the show as watched. I attached a separate .zip file with the NextPVR.log for that for comparison.
At the end of my test (9:07 in the logs), I shutdown the npvr recording service. There are DigitalRecorder.StopAllStreams() messages in the log file. However, it doesn't appear that npvr actually told the DCR-2650 to stop. When I looked at it, it still showed the tuner as in-use and was still transmitting data. I ended up manually stopping it with the HDHR Config utility.
Does NextPVR require additional software for the Hauppauge DCR-2650 besides the device drivers to install in Windows 7? The CD that was shipped in the box with it also has a hdhomerun beta software installation .exe file, but the instructions don't tell the user to run/install that. And the software on the Hauppauge website for the DCR-2650 is just the driver files.
However, when I looked at the nrecord.log from NextPVR, it has lines like:
Code:
2011-08-30 08:54:28.918 [DEBUG][13] checking: HDHomeRun Device 20100465
2011-08-30 08:54:28.918 [DEBUG][13] enabled and present
2011-08-30 08:54:28.918 [DEBUG][13] has channel
2011-08-30 08:54:28.918 [DEBUG][13] live tv is possible
2011-08-30 08:54:28.980 [DEBUG][13] SetTarget@2
2011-08-30 08:54:28.980 [DEBUG][13] Executing: C:\Program Files\Silicondust\HDHomeRun\hdhomerun_config.exe 20100465 set /tuner0/vchannel 831
2011-08-30 08:54:29.816 [DEBUG][13] NIC: Realtek PCIe GBE Family Controller
2011-08-30 08:54:29.816 [DEBUG][13] NIC: Hauppauge OpenCable Receiver (MOCUR-SD)
2011-08-30 08:54:29.817 [DEBUG][13] Executing: C:\Program Files\Silicondust\HDHomeRun\hdhomerun_config.exe 20100465 set /tuner0/target rtp://192.168.140.210:5001
2011-08-30 08:54:29.877 [DEBUG][13] SetTarget@2
2011-08-30 08:54:29.877 [DEBUG][13] Live TV handle: 0x5FC0004
Now, I do have that C:\Program Files\Silicondust\HDHomeRun\hdhomerun_config.exe on my system, but I think that is just because I already have a "classic" HD-HomeRun. If this was a fresh install, I don't think that it would be there.
And, if NextPVR is using/needs the Silicondust software, should I install the beta version that is on the CD I got from Hauppauge? I'm guessing it might have some additional support for the newer devices (the DCR-2650 & the HDHR Prime).
When I added the DCR-2650 to my system last night, I came up with a few questions about exactly how it is working and how it should (ideally) be configured. When I went into the device configuration for the 1st tuner, I did a Scan. The scan resulted in a channel listing which appears to be every channel on my cable company's lineup (plus a few extras which appear to be test, diagnostic, etc. from their names). NPVR gave them channel numbers which match the channel numbers published by the cable company. That seems good. And it gave them channel names which I will call "short descriptions." Sometimes these "short descriptions" are just a broadcast channel's call sign (i.e. "WCCO"), other times it is supposed to be a "friendly version" of a call sign (i.e. "WCCO HD" whose call sign in Schedules Direct is "WCCODT"), and other times it is a longer description (i.e. "National Geographic HD" whose call sign in Schedules Direct is "NGCHD").
So, now the questions:
1. When NPVR gets the channel listing from the cable company, does it just have the logical channel number and this "short description" or does it also have a "call sign" which would/should match the Schedules Direct "call sign"?
2. Since I was adding new channels to an already setup channel listing with channels already configured for XMLTV EPG source, I couldn't use the bulk map feature. However, even if I could have, I don't think that it would have been very successful since (I believe) that it would be trying to match the "short descriptions" from the DCR-2650 to the "call signs" from the Schedules Direct XMLTV file, correct? In these CableCard cases where the logical channels are coming from the cable company and directly match the Schedules Direct cable lineup channel numbers, I think that the matching should be done on the channel numbers. How do you do it with something like the HD-PVR?
3. In NPVR, the channel names tend to be expected (by skins in TV Guide, recordings info, etc.) to be shorter like the "call sign" (i.e. "NGCHD") rather than medium-length like the "short descriptions" (i.e. "National Geographic HD") coming from my cable company. So, my initial thought was to go and change all of the channel names in NPVR to be the "call sign" from the Schedules Direct XMLTV file. But then I got worried about what would happen when (not IF--WHEN) the cable company makes changes to the lineup. I'm presuming that NPVR won't just automatically detect and adjust for it like set-top boxes do. Instead, I expect I'll have to go into the device and do another scan. But then how will NPVR match up the old channels currently used in the database (for recurring recordings, existing recordings, etc.) to the new channels now coming from the cable company lineup? You couldn't use the channel numbers since they might have changed. So I'm thinking that you will have to use the "short description" which is coming from the cable company/DCR-2650. Now, if I have changed the channel names in NPVR from the "short description" to the "call sign" from the Schedules Direct XMLTV file, they won't match up, and it will look like there are all of these new channels, right? Argh!
I "think" the answer may be yes, but confirmation would be handy as this would be for a friends setup who is not too pc literate and some distance away.
Can both NPVR and GBPVR recording services run at the same time on the same machine if they are configured for different tuners.
Only one (npvr?) will be used for an NMT, the other (gbpvr?) would be used on the local machine.
Don't ask the obvious question I asked, otherwise you may get the long winded and confusing explanation I got
Hopefully the above should only run for a couple of weeks.
I've been testing mvallevand's new Network Recorder quite successfully using firewire from my Motorola cable box prior to it being released into the "wild". Now that it's out (in the wiki under plug-ins) and I've installed the production version, here's a report.
Martin helped me clear out some debris from the previous test version. Also, he provided an updated version of Network Recorder that requires a slight work around to install and configure. Here are his instructions:
Stop the NPVR recording service
Delete npvr.db3 to start with a clean database
Start NPVR and add and configure Network Recorder
Start the recording service
This worked OK for me as I was setting up a new NPVR install; if you don't want to delete your database, submit a post for advice.
I use Schedules Direct and it imported my lineup with no problems (I only have the channels of interest enabled in the SD lineup, a total of 27). I didn't even have to map the channels as I kept the same channel numbers as the cable box.
For firewire, one uses SageGraphRecorder (SGR) to interface between the firewire drivers and the Network Recorder plug-in. The firewire drivers are from TimMMoore and are quite old, but work fine in Win7 as long as it is 32 bit; there are no 64 bit firewire drivers. Also, the Win7 firewire driver has to be rolled back to the legacy version in Device Manager before installing the timmmoore drivers. You can google on exdeus to get an updated installer of the drivers and good instructions, or just go to this link: http://home.comcast.net/~exdeus/stbfirewire/
You also need to create a graph using Graphedit on your machine for SGR to use. It needs only two filters: the firewire tuner and the NPVR file writer.
The firewire drivers package also includes a firewire channel changer that works great, at least for me. However, you need to call it from SGR using a batch file as it requires more arguments than SGR wants to provide. My install pops up the command window for a few seconds when it runs, but there are ways to hide it, I understand.
So, how does it work? In a word, great! Solid recordings and live TV. In particular, live TV is very good with no audio-video sync or choppy issues for me. It pauses and rewinds just fine. This is probably due to Sub's work on the NPVR file writer and TS reader.
This removes the final holdup for me moving to NPVR, so I'm happy. Note that my cableco has all the channels of interest in the clear, no 5C or copy protections. YMMV.
Hi there. I'm having difficulty connecting to mvpmcx2 or npvr from my egreat m34a nmt. I can connect successfully to the ihome sw and stream from my media pc. Here is the syntax checker info and attached are my log files. Hope I have all the logs needed.
Thanks!
Checking for mvpmc share on MEDIA-PC
mvpmc C:\mvpmc
Checking GB-PVR.html links
C:\mvpmc \GB-PVR.html not found
NMT IP Address: 10.14.1.5 MAC 0006DC447A9C
GB-PVR Installed
GB-PVR previously uninstalled
N-PVR Installed C:\Users\Public\NPVR
<a href="http://localhost.drives:8883/NETWORK_SHARE/MEDIA-PC:mvpmc/npvr.cgi">N-PVR</a>
<a href="http://localhost.drives:8883/NETWORK_SHARE/NETWORK_BROWSER/browser.cgi">N-PVR via Network Browser</a>
<a href="http://localhost.drives:8883/USB_DRIVE_A-1/mvpmc/usb_a.cgi">N-PVR via USB</a>
config.xml entry found Client Type PCH2
MVPSendIncrementalUpdates true
MVPClientType PCH2
MVPWidth 1920
MVPHeight 1080
MVPOffsetX 0
MVPOffsetY 0
Enabled true
Port 8866
The remote server returned an error: (404) Not Found.
The basic hardware installation went fairly smoothly. I followed the directions on the included quick start sheet for the installation and configuration with Windows Media Center. I had already run the digital cable tv advisor (or something like that) in Windows Media Center back before I ordered the DCR-2650, so that part was already done. When I connected the usb cable to the server, Windows 7 (64-bit) detected the new hardware and automatically installed the drivers for it. It already knew about a Hauppauge OpenCable Receiver (MCOUR-SD), so I didn't even need the CD included in the package. (Note, that in device manager, the device shows up as a network adapter.)
Next, I launched Windows Media Center to do the CableCard pairing/activation. (Again, following the steps on the installation sheet.) I got to the step where it displays the HostID, Data ID, and CableCARD Serial Number. Then I called my cable provider (Comcast) to pair/activate. This is where my problems began... The front-line person took the information and put me on hold to make the changes. After a few minutes, he came back on the line and asked me to give him the HostID again--which I did. He then put me on hold again. And after a few more minutes, he came back on the line and said the he was unable to activate the card. He was going to have to escalate to technical support. After about 45 minutes, the front-line rep called me back and said he had gotten a technical support person who was working on it. Unfortunately, they still weren't able to activate the card. So, Comcast is going to have to send a technician out to my house to do the activation (supposedly at no cost to me). And, unfortunately, the first available time slot is not until Thursday morning. So, it looks like I won't be able to activate the card to really test with cable channels until Thursday.
I went ahead and completed the setup in Windows Media Center. And just for grins, I tried watching one of the "expanded" cable channels (not a premium channel). After a few seconds, it came up and displayed a message saying that a "Subscription is required for this channel. Contact your service provider." Then I tried one of the "basic" cable channels (i.e. one that I already get in clear QAM). That channel does work. So I was able to verify that the DCR-2650 was tuning and sending data to the application.
Next, I decided to try NextPVR. First, I made a backup copy of my npvr.db3 file. Then launched nextpvr and went into the settings. Under devices, the DCR-2650 was listed with 2 tuners. I went into the configuration for the 1st tuner and did a scan. It came up with a list of a couple hundred channels. I then went through the list and unselected the channels which are not included in my cable package (based upon the channel lineup provided by Comcast). Then I went into the configuration for the 2nd tuner. NPVR offered to copy the configuration from the 1st to the 2nd, and I said yes. Then the same channel list (with my package channels selected) came up. So far, so good. The next step was to set the EPG source for the 150 or so new channels from the channel configuration screen. Unfortunately, I could not figure out a way to use the Bulk Map screen to assist with this task. (I'm going to post about it in the support forum.) So, I ended up having to go through and select each individual channel, change the EPG source to XMLTV, and then pick its channel listing from the XMLTV file. That process took a while... :mad: And then I did an EPG update. That process seemed to go fine.
I then went into the TV Guide and selected a couple of shows to do test recordings. I specifically selected one of the "basic cable" ones and one of the "expanded" ones. The basic one seemed to work just fine. The "expanded" channel one appeared to record OK (i.e. the DCR-2650 showed that it was tuned to the channel, was transmitting data, etc.) and NPVR did create a .ts file for the recording. No errors or anything. However, when I tried to play the file it did not work. On the NMT, it would hang mvpmcx2. On the pc, it displays a black screen for a few seconds, then goes back to the recordings list. Interestingly, it marks the recording as being watched. :confused:
That's about it for the first day's report. I'm going to post some specific problems/issues/questions in the support fourms, so look there, too.
I left NPVR paused for a while and when I came back there was an error on the screen saying NRecord.exe had died.
When I try to start the recording service I get the following message:
Unable to start service: System.ServiceProcess.TimeoutException: Time out has expired and the operation has not been completed.
at System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus desiredStatus, TimeSpan timeout)
at NCtrl.Program.Main(String[]args)
I deleted the program files/NPVR folder and re-installed, still the same. I tried starting it from Services and I get the error on the screen saying NRecord.exe had died.
