USBUIRTSEND not sending newly learnt codes to USB-UIRT?

[sub]

Hmmm? There are still many subscriber plans in Asia (HK, Singapore etc., I assume this is IPTV) with both HD and 4K content delivery over the internet that go through a STB; I'm not sure what it is called, but surely that's not analog? The box is the decoder if you like but the content is all digital? So why then are there not more Channel Changer options (Hardware and Software to blast them)?

I assumed you were talking about an old school analog card for capture (composite/svideo etc), but looking at your signature I see you're actually using a Hauppauge Colossus - didn't that come with a blaster? If so, does it work with your set top box? Alternatively you could look at other blasters.

The HDPVR/Colossus style boxes are kind of digital, in that they have a digital transfer from the set top box, but behind the scenes they're kind of like a HD analog device in that they receive raw video frames that have to encoded. (unlike digital capture devices that receive already encoded streams from the broadcaster).

1. The NPVR Not Responding thing; which you have explained is normal but with a brand new PC and in this day and age I would have thought would be instantaneous.

NextPVR isn't doing anything other than waiting for USBUIRTSend.exe to finish doing it's thing. Unfortunately IR blasting is fairly slow business, with USBUIRTSend.exe needing to pretend to be a user pressing the buttons on the remote (behind the scenes it does a few repeats of digit, with short delay between each, and then with another delay between each digits). ie, regardless of how fast your PC is, it's doing practically nothing, spending all the time waiting. At the end of the day, regardless of blaster, it's never going to be any faster than you pointing your remote at your TV, typing three digits, then waiting for the new channel to appear. (ie probably 5 seconds+).

Some people in the US have been lucky, and can control their set top box over the network, effectively sending a command to ask their set top box to change to channel x, taking away the requirement to wait for blasting (they still have a short delay while the set top box changes channels).

Also did you see the USBUirtSend Windows error?

Yeah, unfortunately I don't know what that is. Does it do this every time, or just some times? Does it actually successfully do the IR blast before crashing?

[jksmurf]

I assumed you were talking about an old school analog card for capture (composite/svideo etc), but looking at your signature I see you're actually using a Hauppauge Colossus - didn't that come with a blaster? If so, does it work with your set top box? Alternatively you could look at other blasters.

Yeah it did, but it was too snug and cosy in its little unopened packet to take out. :o Actually I just dug out teh box and WTF, it has a blaster...I've had that thing for years but as the USBUIRT was working well I thought it's all good, leave it. Are they better than the USBUIRT, less overhead? If so I can try it fort sure, but if not then I will leave it.

The HDPVR/Colossus style boxes are kind of digital, in that they have a digital transfer from the set top box, but behind the scenes they're kind of like a HD analog device in that they receive raw video frames that have to encoded. (unlike digital capture devices that receive already encoded streams from the broadcaster).

I am not sure what this all means ... or what OTHER capture card would be a replacement and if it would be better?

NextPVR isn't doing anything other than waiting for USBUIRTSend.exe to finish doing it's thing. Unfortunately IR blasting is fairly slow business, with USBUIRTSend.exe needing to pretend to be a user pressing the buttons on the remote (behind the scenes it does a few repeats of digit, with short delay between each, and then with another delay between each digits). ie, regardless of how fast your PC is, it's doing practically nothing, spending all the time waiting. At the end of the day, regardless of blaster, it's never going to be any faster than you pointing your remote at your TV, typing three digits, then waiting for the new channel to appear. (ie probably 5 seconds+).

Yeah I sort of got that after millions of attempts with various delays repearts blaster software / hardware permutations. All like wading through Golden Syrup (treacle to our American friends..)

Some people in the US have been lucky, and can control their set top box over the network, effectively sending a command to ask their set top box to change to channel x, taking away the requirement to wait for blasting (they still have a short delay while the set top box changes channels).

THAT is what I thought should happen (by now / thos day and age) but this thing ain't one of those.

Yeah, unfortunately I don't know what that is. Does it do this every time, or just some times? Does it actually successfully do the IR blast before crashing?

Every time. But to be fair Windows Logs it as Information so lets say we just leave it for now while it works, your explanation of the whole process being slow is good enough (albeit surprising in this day and age). If it goes TU I might try the Colossus thingy if you reckon its better (above).

Thanks again sub.

[sub]

your explanation of the whole process being slow is good enough (albeit surprising in this day and age). If it goes TU I might try the Colossus thingy if you reckon its better (above).

I don't know if it'll be any better or not - it's just another blaster you already own, so another option you could possibly try some time. You can probably try it's blaster without actually switching to use the Colossus for capture. (by running Haupblast.exe instead of USBUIRTSent.exe). I think the Hauppauge blaster has a predefined set of set top boxes though, rather than learning capability, so it may not know about your set top box.

Regardless, there is unlikely to be any speed difference - IR blasting is a slow activity. Nothing has changed about that technology since you first used an IR blaster.

[jksmurf]

I don't know if it'll be any better or not - it's just another blaster you already own, so another option you could possibly try some time. You can probably try it's blaster without actually switching to use the Colossus for capture. (by running Haupblast.exe instead of USBUIRTSent.exe). I think the Hauppauge blaster has a predefined set of set top boxes though, rather than learning capability, so it may not know about your set top box.

Regardless, there is unlikely to be any speed difference - IR blasting is a slow activity. Nothing has changed about that technology since you first used an IR blaster.

OK good to know (and for others to know too hopefully).

While I have you on the subject, you mentioned blasting is a slow progress; I had the cable guy (always wanted to say that) over and he was so confused about going through the PC, that I ended up connecting the STB direct to the Computer Monitor (HDMI Cable) for him, so he could test the channel change speed. Not sure if it was a placebo effect or not but I was wondering if the STB (HDMI) -> Splitter Box (HDMI) -> PC cable connections could be partly at fault here? PC to Screen should be as fast as STB to screen I guess.

I use the splitter box so a signal actually arrives at the Colossus and I can record it (without it I get a black screen...).
The cables are pretty cheapo and the splitter as well - so my question is would better cables help here (or as long as it's not HDMI 2.2 it doesn't matter, HDMI is HDMI)?

Would those "digital capture devices" to which you refer obviate the need for the splitter? e.g. this device blurb says "Record HDMI signal source directly, No HDMI splitter needed anymore" ?

Another Avermedia site says.... don't use splitters (which suggest you still need them)...

k.

[sub]

While I have you on the subject, you mentioned blasting is a slow progress; I had the cable guy (always wanted to say that) over and he was so confused about going through the PC, that I ended up connecting the STB direct to the Computer Monitor (HDMI Cable) for him, so he could test the channel change speed. Not sure if it was a placebo effect or not but I was wondering if the STB (HDMI) -> Splitter Box (HDMI) -> PC cable connections could be partly at fault here? PC to Screen should be as fast as STB to screen I guess.

When you use a splitter, with one split going to a TV, and one split going to an HDMI capture device (like Colossus etc), they both receive the video frames at the same time. On the TV, it can just display the frames instantly. On the HDMI capture device, it then has to put the video frames into a buffer for H.264 encoding - that process typically takes a second or two, before the H.264 stream is delivered out the other side of the capture device to the PC.

So, going through an HDMI capture box does typically add couple of seconds delay.

You also have the hit up front, of the IR blaster doing it's thing.

I use the splitter box so a signal actually arrives at the Colossus and I can record it (without it I get a black screen...).
The cables are pretty cheapo and the splitter as well - so my question is would better cables help here (or as long as it's not HDMI 2.2 it doesn't matter, HDMI is HDMI)?

Help with what exactly? Regardless of how good your cables are, the video will still take a couple of seconds to go through the HDMI capture device, and IR blasting will still take a few seconds.

Would those "digital capture devices" to which you refer obviate the need for the splitter? e.g. this device blurb says "Record HDMI signal source directly, No HDMI splitter needed anymore" ?

Anotehr Avermedia site says.... don't use splitters (which suggest you still need them)...

That Avermedia website is saying "don't use HDMI splitters to bypass copy protection" as simply a way to let people know they can use an HDMI splitter to remove the copy protection (ie, they're kind of recommending you need to use a splitter in this scenario without saying it explicitly).

So... there is a slightly different type of HDMI capture device (and Hauppauge also have one they're about to release), which relies on the high bandwidth of USB 3, to send raw video frames from the HDMI device to the PC, removing that 1-2 seconds delay you get when going through the H.264 encoder (on Colossus and similar devices). This arrives at the PC as raw video frames, rather than H.264 encoded transport stream. The problem with this is that to able to record that video, you really need to encode it to something smaller (either H.264 or MPEG-2), so you end up having to do that on the PC end (using your CPU), in effect adding that 1-2 second delay back in (and using more of your CPU). This type of capture device is better suited to gamers that only need to be able to see a live preview on their monitor, and need as little delay as possible.

[jksmurf]

Thanks for the detailed explanation of what it’s doing sub, that’s useful to know; I guess I’m just looking for a way to get a reliable channel blasted to my STB. It seems from what you’re saying there is a lag from selecting the channel in NPVR, to NPVR telling the USBUIRTsend.exe to send 325, to the PC telling the USBUIRT to send those IR signals to the STB, to the STB changing it then going down the HDMI cable through a splitter to the capture card and having that thing process the signal to tell you in NextPVR it’s done it. I’m not worried about getting an instant preview or feed, most of my viewing is record shows, but I do need the channel change to be reliable for the correct show to be recorded.

If the first part is fast enough (my new pc is quick) then it should always change reliably, but it doesn’t. The cable guy had a little gloat about how slow it was vs when I plugged it directly into the monitor.

I will try the HD PVR one today as I had a couple of total freezes and when I looked at Event Viewer on restart it mentioned USBUIRTSEND.exe. Will post logs later.

[jksmurf]

When I woke the PC this morning I saw this.... NextPVR isn't even running. I'm getting literally hundreds of them?

k.

[sub]

Maybe just go back to your old version of USBUIRTSend.exe. I'm not sure what would be causing that, and I have no idea where my USB-UIRT is to look into it.

[jksmurf]

Maybe just go back to your old version of USBUIRTSend.exe. I'm not sure what would be causing that, and I have no idea where my USB-UIRT is to look into it.

Did that; same error (even after a Windows restart - also removed all the Channels it applies to and imported them back in). It really hates me. Will try the HD-PVR Blaster in the hope it kills it.

[sub]

Do you get the crash when you run USBUIRTSend.exe from the command line, or does it only happen when NextPVR runs it?