AVS › AVS Forum › HDTV › HDTV Recorders › The Official R5000-HD Technical Status Discussion
New Posts  All Forums:Forum Nav:

The Official R5000-HD Technical Status Discussion - Page 75

post #2221 of 2753
8/22/09 at 4:55am
Well, yesterday I tracked down the post with the R5000HDProxy in it.
http://www.avsforum.com/avs-vb/showp...postcount=2082

This solved the problems I was having with the R5000 software stopping part way through.

If anybody is having any problems with the R5000 recording, you really should check out the proxy program. It works very well.

Greg
Reply
Reply

AVS Top Picks

post #2222 of 2753
8/22/09 at 11:33am
Yeah, I dont think people realize that this utility is required to use in many cases (forcing the R5000 software to work correctly). I, sure as heck, couldnt use my R5000 boxes without it. I wrote a script to hide the command line windows for the proxy too and quietly putting the R5000 apps in the Windows system tray. Glad you got it working.

The funny thing is Hugo gave his code to the R5000 people to integrate into their app. Instead of fixing the problem immediately; they decided to just not relaase software anymore despite all the complaints and multiple email request.. They actually wouldnt even admit there was a problem until Hugo cornered them into admiting the problem. You should email R5000 support and ask them why they havent fixed this problem in the past year.

Quote:
Originally Posted by gregveres View Post

Well, yesterday I tracked down the post with the R5000HDProxy in it.
http://www.avsforum.com/avs-vb/showp...postcount=2082

This solved the problems I was having with the R5000 software stopping part way through.

If anybody is having any problems with the R5000 recording, you really should check out the proxy program. It works very well.

Greg
Reply
Reply
post #2223 of 2753
8/22/09 at 1:08pm
Their support was responsive at first, then they went silent when I kept feeding them information. I asked them a couple days in a row if they had any updates.

Once I get through the weekend with all recordings working perfectly (half way through and batting 1000 right now), I will email them telling them that the problem seems to be a race condition in their code because if it responding to all the GET_FILESIZE and point them at the proxy code (yet again, but the sounds of it). I think I saw somebody mention that they probably have a resource leak because the handle leak keeps going up. If that is the case, it might be prudent to restart it once a month or so.

Greg
Reply
Reply
post #2224 of 2753
8/22/09 at 1:31pm
The resource leak issue is fixed with the proxy. I dont like rebooting my server unless absolutely necessary (for security patches, etc); especially on stable machine. However, the resource leak for me (if not fixed by the proxy app) would flood my memory within a day or two of aggressive recordings on all 4 R5000 boxes.

Quote:
Originally Posted by gregveres View Post

Their support was responsive at first, then they went silent when I kept feeding them information. I asked them a couple days in a row if they had any updates.

Once I get through the weekend with all recordings working perfectly (half way through and batting 1000 right now), I will email them telling them that the problem seems to be a race condition in their code because if it responding to all the GET_FILESIZE and point them at the proxy code (yet again, but the sounds of it). I think I saw somebody mention that they probably have a resource leak because the handle leak keeps going up. If that is the case, it might be prudent to restart it once a month or so.

Greg
Reply
Reply
post #2225 of 2753
8/25/09 at 1:26am
We are starting today the alpha testing of our product - DVBLink for R5000HD. This product connects R5000HD-equipped settopboxes to MediaCenter.
Reply
Reply
post #2226 of 2753
8/25/09 at 1:26am
Who are interested in this http://dvblogic.com/phpBB3/viewtopic.php?f=41&t=3879
Reply
Reply
post #2227 of 2753
8/25/09 at 8:49am
Any chance of you guys over there at DVBLogic creating a proper service based driver for all r5000 usage?
Reply
Reply
post #2228 of 2753
8/25/09 at 1:04pm
Quote:
Originally Posted by Realman_DVBLogic View Post

Who are interested in this http://dvblogic.com/phpBB3/viewtopic.php?f=41&t=3879

Maybe you discussed this before, but what does it mean when you say, "The r5000hd.exe has a limitation of 15 minutes working time. It is enough for the first alpha, but we are currently working together with Nextcom to create a fully functional trial version with prolonged working time."

Does this refer to a recording time limit?
Reply
Reply
post #2229 of 2753
8/25/09 at 11:53pm
R5000HD.exe to our site specially designed version for DVBLink. For alpha1 Nextcom made version R5000HD.exe with limited time work. This will be enough for debug DVBLink. For beta or release will be made fully functional version R5000HD.exe.
Reply
Reply
post #2230 of 2753
8/27/09 at 1:15am
Hi everybody,

I am taking over the discussion here from my colleague "realman_dvblogic".

We at DVBLogic work together with nextcom to create DVBlink compatible product for r5000hd-equipped settopboxes.
For those who might not know - DVBLink is a digital streaming connectivity platform for Windows MediaCenter. It takes digital stream from a custom source - dreambox, Hauppauge HDPVR, IPTV, satTV card etc. - and presents it to MediaCenter as a virtual tuner. As such user gets full MediaCenter functionality for this source - liveTV, time-shifting, timer recordings, guide listings etc.
DVBLink for R5000HD will feature the same functionality for r5000hd stbs. Our software should be better comparing to NextCom's own MediaCenter integration in the following points:
- switching between channels with different resolution (SD and HD) is seamless and does not require restarting MediaCenter
- Better timer recording robustness because of the previous point
- less audio/video artifacts
- Additional DVBLink goodies - upnp server, guide a la carte and - soon - signal transcoding and network server

We have released lately the first Alpha of our product. The goal of this alpha is to test the basics of product functionality - channel changes and streaming. We need some statistics to say that it works and we can move further. This is exactly where we need your help.

Please feel free to try the alpha and report your findings. I will be happy to answer all your questions here or on our forum at dvblogic.com.
Reply
Reply
post #2231 of 2753
8/27/09 at 1:41am
You might consider also posting on the AVS - HTPC forum; explaining what it does; if you need more alpha testers. Glad to see finally taking on Windows Media Center for the R5000; as there are probably a lot of people interested in this who are used to WMC. I am curious, will you product still require the R5000 DVR helper app and 32bit Windows driver?

Quote:
Originally Posted by DVBLogic View Post

Hi everybody,

I am taking over the discussion here from my colleague "realman_dvblogic".

We at DVBLogic work together with nextcom to create DVBlink compatible product for r5000hd-equipped settopboxes.
For those who might not know - DVBLink is a digital streaming connectivity platform for Windows MediaCenter. It takes digital stream from a custom source - dreambox, Hauppauge HDPVR, IPTV, satTV card etc. - and presents it to MediaCenter as a virtual tuner. As such user gets full MediaCenter functionality for this source - liveTV, time-shifting, timer recordings, guide listings etc.
DVBLink for R5000HD will feature the same functionality for r5000hd stbs. Our software should be better comparing to NextCom's own MediaCenter integration in the following points:
- switching between channels with different resolution (SD and HD) is seamless and does not require restarting MediaCenter
- Better timer recording robustness because of the previous point
- less audio/video artifacts
- Additional DVBLink goodies - upnp server, guide a la carte and - soon - signal transcoding and network server

We have released lately the first Alpha of our product. The goal of this alpha is to test the basics of product functionality - channel changes and streaming. We need some statistics to say that it works and we can move further. This is exactly where we need your help.

Please feel free to try the alpha and report your findings. I will be happy to answer all your questions here or on our forum at dvblogic.com.
Reply
Reply
post #2232 of 2753
8/27/09 at 1:55am
Quote:
I am curious, will you product still require the R5000 DVR helper app and 32bit Windows driver?

The DVBLink solution still requires r5000hd helper application. However this application is specifically updated for our purpose so that we can use in the same way as SageTV does - with faster channel changes and transferring th stream via shared memory interface.
We may consider running this application as a service at the later stages of the product.
Reply
Reply
post #2233 of 2753
8/27/09 at 4:13am
Quote:
Originally Posted by DVBLogic View Post

We may consider running this application as a service at the later stages of the product.

Really, for what the R5000HD.EXE app does, it should definitely already BE a service from nextcom. It should be started at boot-up, and if it loses the box for some reason, reinitialize itself. This should be considered a standard feature.

Of course, the REAL end-game for this would be a BDA driver wrapper for the R5000. THAT would finally fix almost all teh issues with the R5000, and probably get me on the hook for 2 more DiY kits...
Reply
Reply
post #2234 of 2753
8/27/09 at 9:10am
I approached Nextcom about adding support for GBPVR. Basically, I was going to write my own BDA driver which wrapped the helper application and it would work with any TV application that used BDA drivers. Unfortunately, since I don't have Dish/DTV yet, the startup cost was going to be way too high for me. It probably would have been worth it in the end but Nextcom did not seem interested at all.
Reply
Reply
post #2235 of 2753
8/27/09 at 11:34am
Quote:


I approached Nextcom about adding support for GBPVR. Basically, I was going to write my own BDA driver which wrapped the helper application and it would work with any TV application that used BDA drivers.

This is exactly what DVBLink does. As such it works with any application that understands BDA drivers - MediaCenter, GBPVR, DVBViewer, SageTV etc.
Reply
Reply
post #2236 of 2753
8/27/09 at 12:20pm
Quote:
Originally Posted by DVBLogic View Post

This is exactly what DVBLink does. As such it works with any application that understands BDA drivers - MediaCenter, GBPVR, DVBViewer, SageTV etc.

Great. I may have missed it but is there any idea on the cost for the DVBLink driver yet? I know a lot of GBPVR users who may be interested.
Reply
Reply
post #2237 of 2753
8/27/09 at 1:05pm
If it can just keep the R5000HD program from crashing, I'd be intersted (sage user).
Reply
Reply
post #2238 of 2753
8/27/09 at 1:24pm
Quote:
Originally Posted by DVBLogic View Post

This is exactly what DVBLink does. As such it works with any application that understands BDA drivers - MediaCenter, GBPVR, DVBViewer, SageTV etc.

Have you thought about doing this for cablecard as well?
Reply
Reply
post #2239 of 2753
8/27/09 at 7:58pm
Ok - I've done a fresh install of Windows 7 RC and have now attempted to install the DVBLink product. Step one of the installation documentation says to "Install R5000HD". I use the R5000hd.exe that came with DVBLink software and it doesn't seem to install anything - it just runs the r5000hd.exe dvr app and gives me a USB Error indicating that the USB device driver for the R5000 isn't installed. It also doesn't install any software to they system.

Should I install Nextcom's software first and then replace the R5000hd.exe file with DVBLink version? I attempted that with Nextcom's generic version and got the same USB Error after I replaced the Nextcom file with the DVBLink one. Should I use the MCE version of Nextcom's software instead? Please clarify - thanks.
Reply
Reply
post #2240 of 2753
8/27/09 at 8:22pm
I think you need to modify the driver .inf file for it to work for Windows 7 (the hack needed for the driver to work on Vista). Try the attached inf (should replace the inf file paired up with the driver file NxtcmUSB.sys). This should take care of the USB error message you see when you start the R500HD.exe app; as your driver installation isn't complete yet. You definitely need the DVBLink's version of the R5000HD.exe app for it to know to talk to the DVBLink software.

Quote:
Originally Posted by guppyman View Post
Ok - I've done a fresh install of Windows 7 RC and have now attempted to install the DVBLink product. Step one of the installation documentation says to "Install R5000HD". I use the R5000hd.exe that came with DVBLink software and it doesn't seem to install anything - it just runs the r5000hd.exe dvr app and gives me a USB Error indicating that the USB device driver for the R5000 isn't installed. It also doesn't install any software to they system.

Should I install Nextcom's software first and then replace the R5000hd.exe file with DVBLink version? I attempted that with Nextcom's generic version and got the same USB Error after I replaced the Nextcom file with the DVBLink one. Should I use the MCE version of Nextcom's software instead? Please clarify - thanks.

 

NextcomHDTV.zip 16.9482421875k . file
Reply
Reply
post #2241 of 2753
8/27/09 at 10:04pm
Quote:
Originally Posted by MKANET View Post

I think you need to modify the driver .inf file for it to work for Windows 7 (the hack needed for the driver to work on Vista). Try the attached inf (should replace the inf file paired up with the driver file NxtcmUSB.sys). This should take care of the USB error message you see when you start the R500HD.exe app; as your driver installation isn't complete yet. You definitely need the DVBLink's version of the R5000HD.exe app for it to know to talk to the DVBLink software.

I'll have to give that a try. I've been using the R5000-HD since last November and never had that error message before. I only get the USB error with DVBLink's R5000HD.exe file. I've used the three flavors from Nextcom - generic, Sage, MCE and none have given me the usb error. I've never hung in there long enough to make them work with Sage or MCE - I've just done my recording manually or through TitanTV. I recently wanted to fight through it again because I'd really prefer a more integrated solution. When I saw DVBLink's post, I jumped on it - it's got to be better than Nextcom's solutions.
Reply
Reply
post #2242 of 2753
8/27/09 at 10:30pm
Once you get it working, it doesnt matter how it works.. so long as it's reliable and as quick as possible.

For me, I have mine put together with gum and shoestring using hugo's proxy app (opening 4 command line windows (one for each device) and automatically hiding the windows using CMDOW.exe). Nobody would ever know looking at the windows desktop that there's all that junk running in the background since everything is hidden.

Quote:
Originally Posted by guppyman View Post

I'll have to give that a try. I've been using the R5000-HD since last November and never had that error message before. I only get the USB error with DVBLink's R5000HD.exe file. I've used the three flavors from Nextcom - generic, Sage, MCE and none have given me the usb error. I've never hung in there long enough to make them work with Sage or MCE - I've just done my recording manually or through TitanTV. I recently wanted to fight through it again because I'd really prefer a more integrated solution. When I saw DVBLink's post, I jumped on it - it's got to be better than Nextcom's solutions.
Reply
Reply
post #2243 of 2753
8/28/09 at 12:48am
There is a typo in the installation and configuration manual indeed. Sorry about that.
r5000hd.exe from dvblink zip is the application itself - e.g. not the installation executable. So you need to install NextCom own software first (does not really matter which flavor it is) and then copy DVBLink's r5000hd.exe over. This should do the trick. You may not be able to use it in a usual way, but it should work with DVBLink for r5000hd.
Run DVBLink's channel configuration dialog, insert several channels (2-3 will do for a start), synchronize them in MediaCenter and try changing them to see whether you can see picture.

Thanks!
Reply
Reply
post #2244 of 2753
8/28/09 at 1:05am
So, this brings up some questions from me.. is ANYONE using the R5000 with Vista or Win7 successfully? I get BSOD's whenever I try it, even on a completely clean install. DVBLink, I saw your comment about modified .inf files, and tried that, but it does the same thing. Is anyone else having this problem?

Thanks
Reply
Reply
post #2245 of 2753
8/28/09 at 2:03am
Quote:
Originally Posted by DVBLogic View Post

There is a typo in the installation and configuration manual indeed. Sorry about that.
r5000hd.exe from dvblink zip is the application itself - e.g. not the installation executable. So you need to install NextCom own software first (does not really matter which flavor it is) and then copy DVBLink's r5000hd.exe over. This should do the trick. You may not be able to use it in a usual way, but it should work with DVBLink for r5000hd.
Run DVBLink's channel configuration dialog, insert several channels (2-3 will do for a start), synchronize them in MediaCenter and try changing them to see whether you can see picture.

Thanks!

Okay I will try a different version to see if that will work better.

Any help with the USB error? See my previous post.
Reply
Reply
post #2246 of 2753
8/28/09 at 6:30am
Quote:
Originally Posted by CraziFuzzy View Post

So, this brings up some questions from me.. is ANYONE using the R5000 with Vista or Win7 successfully? I get BSOD's whenever I try it, even on a completely clean install. DVBLink, I saw your comment about modified .inf files, and tried that, but it does the same thing. Is anyone else having this problem?

Thanks

I use it on Vista with my 2 Dish Vip211s with SageTV mostly successfully. Just the occasional stopped recording, but no bluescreens.
Reply
Reply
post #2247 of 2753
8/28/09 at 7:30am
You should be more descriptive with the scenarios you get BLOD's if you want help. I can't speak for everyone; for me, using Vista with the proxy app, is rock solid. In fact, its so solid that I use that machine as full time workstation as well; running all 10 tuners (4 of them R5000s) invisibly in the background. I can even play 1080p 3D games in the foreground while all 10 tuners are active in the background at the same time. I even have FTP, HTTP (with asp.NET apps) servers on that same machine.

As far as troubleshooting goes, general rule is remove all USB and PCI peripherals except the device causing the bug check from the driver. If youre still getting BSOD's without anything connected, except for the R5000 on a clean Vista machine... its an incompatibility between your motherboard with respective drivers and your R5000. If it doesnt BSOD without anything connected, then you can start adding your devices back one by one until you see which one conflicts with the R5000; causing the BSOD.

Quote:
Originally Posted by CraziFuzzy View Post

So, this brings up some questions from me.. is ANYONE using the R5000 with Vista or Win7 successfully? I get BSOD's whenever I try it, even on a completely clean install. DVBLink, I saw your comment about modified .inf files, and tried that, but it does the same thing. Is anyone else having this problem?

Thanks
Reply
Reply
post #2248 of 2753
8/28/09 at 9:17am
well, I've definately narrowed it down to the R5000 causing the crash, though I hadn't thought about USB incompatability... This is Win7, but from the driver standpoint, it's pretty much equivalent to vista. I can run the system fine and stable, even WITH the r5000 hooked up, but if it's hooked up AND the app is running, it'll crash pretty reliably.
Reply
Reply
post #2249 of 2753
8/28/09 at 9:22am
Does that mean you already tried running the R5000 without any other peripheral connected or not?

Quote:
Originally Posted by CraziFuzzy View Post

well, I've definately narrowed it down to the R5000 causing the crash, though I hadn't thought about USB incompatability... This is Win7, but from the driver standpoint, it's pretty much equivalent to vista. I can run the system fine and stable, even WITH the r5000 hooked up, but if it's hooked up AND the app is running, it'll crash pretty reliably.
Reply
Reply
post #2250 of 2753
8/30/09 at 9:40am
Seems as though Nextcom is in the process of putting up a new version of software. Some release notes are posted on their site in the downloads section, but I didn't see the software:

Quote:


8/29/09: ver 3.1c New version supports 64-bit systems. Requires new driver package and is incompatable with previous versions. Changes and additions: Startup options added. All configuration options managed via UI, configuration files no longer used. Record logging files eliminated. This data is retreived via the "Recordings Log" utility menu. Media Player no longer integrated with DVR app. Dish 211/622/722 periodic wake-up command added. Fast channel switch for SageTV modes.
Reply
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: HDTV Recorders

AVS Top Picks

AVS › AVS Forum › HDTV › HDTV Recorders › The Official R5000-HD Technical Status Discussion