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 78

post #2311 of 2753
9/16/09 at 1:25pm
Ohhh... you know what.. that probably explains why I see these R5000HD Interfaces popup in front of me on my desktop unexpectedly when a recording starts sometimes (even though I have the option set for hiding it in "iconic" mode in the taskbar.

Another unusual behavior is when flipping through the different tabs on the interface, it has this weird focus issue where I'll lose focus of the interface and it will hide behind another window (if there is one).

I tried contacting their support recently about this with respective screenshots, but, never received a reply back. I'm not sure if I should attempt to try again; or, thats their way of saying I dont get support anymore from them (even though I've spend more than 2 grand and refered over 8 grand <-edit worth of customers) in the last couple of years.

Quote:
Originally Posted by boiler11 View Post

I know there's a separate process for each instance. When you run the r5000hd.exe, it spawns more processes for each instance. I believe the way in which they spawn the process is the reason why it's difficult to kill, not that it's "tied" to the driver. But then again, I didn't write the code ...



It was really hung, sage was correct. I neglected to mention, but when I logged into the server, I had a windows dialog indicating that the process had terminated improperly, or something along those lines. I don't remember exactly how they word it. However, when that happened with the older versions of the app, the process would really go away. With 3.1c, it does not.

Note that I'm NOT using the new 3.1c options to load at startup and auto recovery, they are disabled. I'm pretty sure the statup option loads at user login, not at boot. I don't usually log onto my server, so load at login doesn't work.

I could probably get the proxy working with 3.1c to avoid the crashes, but there's no real benefit. My wife was tired of me messing with it, so I'm back to 3.0c ...

Sean
Reply
Reply

AVS Top Picks

post #2312 of 2753
9/19/09 at 6:57am
Anyone else experience this, I'm using the multi (2x r5000) sagetv xp version of 3.1c and it worked fine for about a day or two and then it came up with the error "port already in use" and asking me to change it and that tuner quite communicating with sagetv. It has done this several times now and I have to restart the r5000 app and restart the sagetv service to get it working again with the assigned port. So I have gone back to using the proxy to bridge the gap with sagetv and this issue hasn't happened yet. Although 3.1c fixed the handles/memory issue with sagetv did it introduce another bug? I had a rock solid setup with 3.0e (although the proxy was needed).
Reply
Reply
post #2313 of 2753
9/19/09 at 9:20am
Yes, of course. It happens to me alot; usually when restarting sageTV. Can you please send the R5000 support telling them this is a reproducible bug? I think they are tired of my reporting bugs to them. I didnt tell them about this one.

Quote:
Originally Posted by pilotguy7ca View Post

Anyone else experience this, I'm using the multi (2x r5000) sagetv xp version of 3.1c and it worked fine for about a day or two and then it came up with the error "port already in use" and asking me to change it and that tuner quite communicating with sagetv. It has done this several times now and I have to restart the r5000 app and restart the sagetv service to get it working again with the assigned port. So I have gone back to using the proxy to bridge the gap with sagetv and this issue hasn't happened yet. Although 3.1c fixed the handles/memory issue with sagetv did it introduce another bug? I had a rock solid setup with 3.0e (although the proxy was needed).
Reply
Reply
post #2314 of 2753
9/20/09 at 5:16pm
Quote:
Originally Posted by pilotguy7ca View Post

Anyone else experience this, I'm using the multi (2x r5000) sagetv xp version of 3.1c and it worked fine for about a day or two and then it came up with the error "port already in use" and asking me to change it and that tuner quite communicating with sagetv. It has done this several times now and I have to restart the r5000 app and restart the sagetv service to get it working again with the assigned port. So I have gone back to using the proxy to bridge the gap with sagetv and this issue hasn't happened yet. Although 3.1c fixed the handles/memory issue with sagetv did it introduce another bug? I had a rock solid setup with 3.0e (although the proxy was needed).

Yep. That's exaclty what I was talking about several posts ago. That's why I'm back to 3.0c with the proxy.
Reply
Reply
post #2315 of 2753
9/20/09 at 5:46pm
Have anyone informed Nextcom about this specific issue?

Quote:
Originally Posted by boiler11 View Post

Yep. That's exaclty what I was talking about several posts ago. That's why I'm back to 3.0c with the proxy.
Reply
Reply
post #2316 of 2753
9/20/09 at 6:58pm
Yeah I did...I got a response explaining I need to make sure each tuner/instance needs a different port, which of course I do and explained that further to them...
Reply
Reply
post #2317 of 2753
9/22/09 at 9:38am
Anyone else noticed that they actually RAISED the prices of the mod? This seems odd.. I mean, are they really selling THAT well? what's the story on that? I was thinking about getting a couple more DiY kits, but can't believe they raised the price...
Reply
Reply
post #2318 of 2753
9/22/09 at 10:08am
Quote:
Originally Posted by CraziFuzzy View Post

Anyone else noticed that they actually RAISED the prices of the mod? This seems odd.. I mean, are they really selling THAT well? what's the story on that? I was thinking about getting a couple more DiY kits, but can't believe they raised the price...

I did. I've been waiting for a price drop so that I can get one and add support to GBPVR for it. It looks like I won't be anytime soon.
Reply
Reply
post #2319 of 2753
9/22/09 at 10:25am
Has anyone noticed that they took off the DIY Motorola cable mods? I'm not exactly sure the reason for this. But, whatever the reason is, I wish they would consider putting it back.
Reply
Reply
post #2320 of 2753
9/24/09 at 10:02am
What were the prices before?

I just discovered this product and was considering it, but the prices did seem a bit high to me. I was looking specifically for the motorola mod, and I could have sworn I saw a DIY for that one. Now I know I'm not crazy, and they removed it just as I was looking into it.
Reply
Reply
post #2321 of 2753
10/2/09 at 4:10pm
Quote:
Originally Posted by DVBLogic View Post

Hello again!

After the launch of DVBLink for R5000HD Alpha1, which turned to be almost a disaster, we have worked with NextCom to improve our software. As a result we have released today DVBLink for R5000HD Alpha2. This product only works with recently released 3.1c version of original R5000HD software (all flavors - basic, multi and sagetv).
Please feel free to try and report your experiences. The software is available for download from our forum:
http://dvblogic.com/phpBB3/viewforum.php?f=41

Thanks!

Although the instructions are a bit convoluted (screen captures don't match the current software configuration for example), I installed the R5000-HD 3.1c app, made sure it worked and then installed DVBLink. I setup the channels, media center sees DVBLink, I can do the channel configuration, the channels show up in the guide but I get no picture.

Any ideas what is wrong?

BTW, I have both installed on my HTPC running Windows 7 RC
Reply
Reply
post #2322 of 2753
10/3/09 at 8:42am
Anybody who installed the DIY R5000HD kit, what is the chip/device on it? The driver suggests it is a Cypress Semiconductor USB device. Thx.
Reply
Reply
post #2323 of 2753
10/3/09 at 2:56pm
Well I just uninstalled version 3.1. It ended up doing the same thing that 3.0e did without the proxy code. 3.0e was losing about 90% of my recordings without the proxy code and was losing 0% (recording perfectly) with the proxy code.

I decided I would upgrade to 3.1 to give it a try and shortly after that it started losing 25% of the recordings. I just reverted back to 3.0e with the proxy and we will see how it goes. The first recording worked flawlessly.

This is on XP sp2 with a single recorder.

Greg
Reply
Reply
post #2324 of 2753
10/5/09 at 2:37am
Quote:
Originally Posted by guppyman View Post

Although the instructions are a bit convoluted (screen captures don't match the current software configuration for example), I installed the R5000-HD 3.1c app, made sure it worked and then installed DVBLink. I setup the channels, media center sees DVBLink, I can do the channel configuration, the channels show up in the guide but I get no picture.

Any ideas what is wrong?

BTW, I have both installed on my HTPC running Windows 7 RC

Our excuses for discrepancies between the instruction and the current version.
1. Remove log file ..\\DVBLogic\\DVBLink\\DVBLinkServer.log.
2. Set in Source Configuration->Server->Configuration->Log Level in Info.
3. Start DVBLink server.
4. Choose 2-3 channels in MCE.
Attach zipped log on our forum http://dvblogic.com/phpBB3/viewtopic...p=13664#p13664.
Reply
Reply
post #2325 of 2753
10/5/09 at 3:38am
Quote:
Originally Posted by Realman_DVBLogic View Post

Our excuses for discrepancies between the instruction and the current version.
1. Remove log file ..\\DVBLogic\\DVBLink\\DVBLinkServer.log.
2. Set in Source Configuration->Server->Configuration->Log Level in Info.
3. Start DVBLink server.
4. Choose 2-3 channels in MCE.
Attach zipped log on our forum http://dvblogic.com/phpBB3/viewtopic...p=13664#p13664.

I'll get to this as soon as I can. Unfortunately, I don't have the time to devote to this that I would like. Too many unfinished projects on the house.
Reply
Reply
post #2326 of 2753
10/13/09 at 7:48am
OK, I concede, I give up on trying to move to 64-bit single system running everything, and have plunked down $109 on an MSI Atom based nettop to run my R5000's...

So I looked at the proxy, but I've got two problems...one is hmmm I thought %1 %2 etc were wild cards that were filled by how you write the command line that calls the bat file...can someone provide an actual example of the BAT they use to run the Proxy, and if I'm right about the %x's in the file, an example of the cmd line they run to execute the bat?

Also, with the new 3.1, my old bat for launching the 3.0 app now hangs as the 3.0 app knows there is a 3.1, and stalls with a new interface asking me if I want to upgrade...err. How are you guys dealing with that issue / adjusting your startup commands.

Since I want to use the Nettop headless and robust (XP with a startup bat)...can someone walk me through how to address these items?

thanks,

and I apologize in advance for not recognizing MKANET's wisdom on both holding out for 64-bit, and trying to get everything to run on just one 24x7 system

jmv
Reply
Reply
post #2327 of 2753
10/17/09 at 12:48pm
Well, I've got my system setup, but I can not get the Proxy to work. The system works ok w/o the proxy using 6967 and 6969 as the ports for the two R5000's I have. However, when I start up the R5000 App, and tell it to use 6966 and 6968 respectively, and then set up the Proxy using the command line

R5000HDProxy 6966 6967 >out6966.txt 2>err6966.txt
and...
R5000HDProxy 6968 6969 >out6966.txt 2>err6966.txt

SageTV just doesn't see them. I also tried reversing the port order in the Proxy eg. 6967 6966...but that had no effect. I know SageTV and the R5000's are talking because everything is fine if I just leave the R5000 SW set to 6967 and 6969...any help on what I'm doing wrong?

thanks,

mv
Reply
Reply
post #2328 of 2753
10/18/09 at 9:34am
Try changing the address of the encoder in the sage.properties file to point to the name of the server, or the ip, instead of 127.0.0.1. If I remember right, there's a problem with the proxy app not tying itself to localhost (127.0.0.1) so it doesn't listen there.
Reply
Reply
post #2329 of 2753
10/18/09 at 10:09am
Crazyfuzzy,

Thanks for the response. I am running the R5000 on a separate PC and I did change the Sage.properties file to look at the IP of that separate computer. I never could get Sage to talk to the proxy app...I could get sage to talk to the R5000App on the separate computer, although the playback was very poor and choppy it did "see it".

I've since moved the R5000's back to the server PC where it runs reliably w/o the Proxy app...although handles to "grow" so I would prefer to have a working Proxy app.

thanks,

mv
Reply
Reply
post #2330 of 2753
10/19/09 at 8:41pm
Quote:
Originally Posted by MKANET View Post

Boiler, what you are seeing is normal behavior. Your supposed to see multiple instances of R5000HD.exe; one for each R5000 that's used on your machine. I dont think you can kill the process even if you tried as it's tied into the driver. SageTV will falsely report devices that are hung; when they are perfectly fine, not just the R5000, but many other types of devices (ie USB Hauppauge products like the 950q, etc). I think you can turn this new sageTV error reporting off.

I would be very surprised if you missed a recording (or part of a recording) with this version; and didnt with the older version. If anything, its supposed to fix the remaining stability issues.

The only thing I see that's odd about the R5000 interface is it sometimes gets confused and doesnt properly hide things the user should not see. It seems to only happen with 4 devices though.

-Michael

did anyone get this port issue resolved? I have emailed them a few times, but they only responded once,hopefully that means a fix is imminent.
Reply
Reply
post #2331 of 2753
10/21/09 at 8:45am
Nextcom wireless will not fix reproducable software/driver bugs just because several paying customers report the same issues over and over again. It seems there are other factors preventing them from addressing these issues within a reasonable time frame; at which they feel they are at liberty not to not say why.

My guess is they arent using the money they receive from R5000 sales, repairs, instalations, to pay for the developer's time; and the developer himself doesnt actually use the software he developes for personal use. They should at least make their software/drivers available to the opensource community if they are unable to support their own products anymore.

I'd love to know what it is exactly that "Nextcom Wireless" is so busy doing that they dont have time to address significant reproducible software bugs on a major new software release.

EDIT: I remember they used to provide frequent bug fixes in beta releases on their webpage a couple years back. Then... all of a sudden, they just stopped.

Quote:
Originally Posted by btrcp2000 View Post

did anyone get this port issue resolved? I have emailed them a few times, but they only responded once,hopefully that means a fix is imminent.
Reply
Reply
post #2332 of 2753
10/21/09 at 7:58pm
Who wants to help me hook up my proxy so it talks directly to the driver? The driver is the generic Cypress EZ-USB driver. I know how to stream the raw video data. I've got a lot of the pieces in place but one thing I need help with is a function to extract a single program's transport stream from the raw data.

Quote:
Originally Posted by MKANET View Post

Nextcom wireless will not fix reproducable software/driver bugs just because several paying customers report the same issues over and over again.
Reply
Reply
post #2333 of 2753
10/21/09 at 8:17pm
Guho,

I can't help you I have 0 programming skills...but I do have a request...would it be possible to make your Proxy intercept an incoming sage request from a separate machine (ie different IP address) and have the R5000 and Proxy running on a different IP address. I exchanged e-mail with MKANET, and he thought that because I was running R5000App+Proxy on one physical machine and SageTV on a separate machine, that was why I am having issues getting SageTV and the Proxy app to talk...

mv
Reply
Reply
post #2334 of 2753
10/21/09 at 8:18pm
Hugo, you know I am always here to do testing for you. I used your proxy program for a long time until the new driver was released. If they were to fix these trivial bugs with their new software it would be great. But I cant wait another year for them to try to fix their broken software.

Quote:
Originally Posted by guho View Post

Who wants to help me hook up my proxy so it talks directly to the driver? The driver is the generic Cypress EZ-USB driver. I know how to stream the raw video data. I've got a lot of the pieces in place but one thing I need help with is a function to extract a single program's transport stream from the raw data.
Reply
Reply
post #2335 of 2753
10/21/09 at 10:18pm
Quote:
Originally Posted by guho View Post

Who wants to help me hook up my proxy so it talks directly to the driver? The driver is the generic Cypress EZ-USB driver. I know how to stream the raw video data. I've got a lot of the pieces in place but one thing I need help with is a function to extract a single program's transport stream from the raw data.

It's been a LONG time sense i spent any time digging through the internals of an MPEG transport stream, but I'm pretty sure grabbing a single program from it should be relatively easy. You have to read the Program Map Table (PMT), determine what program you want, and, from the table, get which Packet Identifiers (PID's) are included in that table, then, each packet is either written, or ignored, based on the PID.
Reply
Reply
post #2336 of 2753
10/21/09 at 10:36pm
Quote:
Originally Posted by guho View Post

Who wants to help me hook up my proxy so it talks directly to the driver? The driver is the generic Cypress EZ-USB driver. I know how to stream the raw video data. I've got a lot of the pieces in place but one thing I need help with is a function to extract a single program's transport stream from the raw data.

How are you streaming it and when you say "raw video data" I assume you are talking about a transport stream and not actually raw video? If you could port your code into a DirectShow BDA filter, you wouldn't need to worry about splitting the stream. Any DirectShow application would then handle all the demuxing (splitting off each program). I can help you somewhat with the DirectShow filter but I don't have an R-5000 so someone else would have to do the testing and be willing to do lots of it.
Reply
Reply
post #2337 of 2753
10/21/09 at 10:45pm
yeah, BDA would be the way to go (really, the way nextcom SHOULD have gone to begin with).
Reply
Reply
post #2338 of 2753
10/30/09 at 11:20am
Does anybody know what affects the "pushing it" bar in the recorder?

I just moved the recorder to a brand new quad core i5 with 4 GB of ram running on 500 GB sata drives and I am getting the bar closer to pushing it than I did when I was running a dual core Pentium D820 with 3GB of ram and the exact same disk drives. (I moved the disk drives to the new machine).

Any suggestions would be good. Even with the latest version of their driver / program I am still getting recordings that get interrupted. it doesn't happen as often as before, but it happens about a couple times a week.

With the new system I have started to see overflows happening as well. I don't remember them ever happening on the Pentium system.

Thanks
Greg
Reply
Reply
post #2339 of 2753
10/30/09 at 11:25am
Quote:
Originally Posted by gregveres View Post

Does anybody know what affects the "pushing it" bar in the recorder?

I just moved the recorder to a brand new quad core i5 with 4 GB of ram running on 500 GB sata drives and I am getting the bar closer to pushing it than I did when I was running a dual core Pentium D820 with 3GB of ram and the exact same disk drives. (I moved the disk drives to the new machine).

Any suggestions would be good. Even with the latest version of their driver / program I am still getting recordings that get interrupted. it doesn't happen as often as before, but it happens about a couple times a week.

With the new system I have started to see overflows happening as well. I don't remember them ever happening on the Pentium system.

Thanks
Greg

Did you use 64K clusters on the storage volumes that are being used for recordings? Depending on how the code handles writes, default windows configs sometimes have issues with write performance.
Reply
Reply
post #2340 of 2753
10/30/09 at 11:53am
Greg,

More about the configuration...are you using the Proxy app?, What OS are you using? Is SageTV your front end? Although the drives are "local" are they seen as local, or are you using a network address?

FYI, I have a Q9450, and use the old app w/o the proxy, have the sometimes miss the first 5 min issue, but never loose a recording once started, but some recordings have playback issues (skip randomly).

I have a very fast RAID array (500MB/s) and the indicator always sits below the mid-point on the "pushing it" scale.

mv
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