Colossus 2 and nextpvr

[mvallevand]

Maybe you can. I am using LIRC with my Rogers STB in Canada and Rogers actually licenses the Comcast Xfinity system here. My boxes are both Comcast devices. I have XiOne but the Xi6 also works here. Both boxes do have both RF and IR active simultaneously.

I use one box in my media room I use for watching TV directly or with NextPVR, it gives me a backup recording device since I don't watch TV there all the time. I tune remotely with LIRC on an RPi and a network HDMI capture device. In fact the XiOne, is controlled by two IR transmitters, one from the RPi and one from my Harmony Hub. I can even connect to it from my test server so I don't have to do all my testing in production.

Rogers hasn't turned on web browser tuning yet that might be interesting. Turns out these device do have internal IP tuning I just haven't found out how to control it but there is a Control4 app for Comcast tuning that works too.. Unfortunately I joined the Comcast developer program and couldn't find anything on how to access IP tuning, that would be ideal.

Martin

[Iriman]

The web remote is very nice. It's worked from everywhere so far and no issues yet. can even program custom buttons and commands. voice controls are there and available but i haven't had the time to mess with it to get it working correctly yet. I use an XiD X1 Cisco box for space saving.

[Iriman]

just wanted to say i was able to get ac3 5.1 working perfectly. one of my addons was throwing an error so i renamed ~/.kodi to ~/.kodi.old and started from scratch. As soon as i did, SPDIF started working correctly and all is good.
Thanks for the help!

[ehfortin]

Hello,

I'm up to this point:


colossus2.sh | ffprope -i pipe:

And I seems to have audio (AAC) and video. I tried to generate .ts file by doing colossus2.sh > file.ts which produce a playable file but without any audio using VLC. A .ts coming from NextPVR on Windows is playing normally with the same VLC. Any idea what could be the issue? I have a HD-PVR2.

Thank you.

Code:

Input #0, mpegts, from 'pipe:':
  Duration: N/A, start: 1.413544, bitrate: N/A
  Program 1
    Metadata:
      service_name    : Service01
      service_provider: FFmpeg
  Stream #0:0[0x100]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p(tv, bt709, progressive), 1280x720 [SAR 1:1 DAR 16:9], 60 fps, 60 tbr, 90k tbn, 120 tbc
  Stream #0:1[0x101]: Audio: aac (LC) ([15][0][0][0] / 0x000F), 48000 Hz, stereo, fltp, 384 kb/s

ehfortin

[mvallevand]

Before getting to to script you have to make sure that /opt/Hauppauge/bin/hauppauge2 files generates a playable mpeg ts file with audio.

Martin

[ehfortin]

Hi,

hauppauge2 and the script are now working with AAC. It's not with AC3. I guess it means the Bell TV receiver is not pushing this, is that correct?

I'm now installing NextPVR and will put the extra file in the directory you suggested. Will see how it goes.

Thank you.

ehfortin

[mvallevand]

Ir could be your hdcp stripper, your box settings or.hauppauge2 parameters. I have it with Rogers

Martin

[ehfortin]

I have nothing between the Bell (Motorola VIP1232) receiver and the HDPVR2. It's a SPDIF connection and that's it. hauppauge2 parameter either 3 (AAC) or 2 (AC3). When using "-d 3", I have sound. Nothing with "-d 2" so, except if you tell me I missed something, I will assume for now that the receiver is not sending AC3. Will see if I have something I can configure on the receiver itself.

The problem I got just after that, which is now fixed is that I've created an extras and put it in /opt/nextpvr/system/data which seems to be the ideal place for it. But looking at the log, it doesn't seems to be read. So I moved it to /var/opt/nextpvr and it's not recognized. I think it is related to the fact that I've use the nextpvr-helper.deb to do the installation on ubuntu. Wanted to leave a trace here for anybody having a similar issue or for when I'll reinstall in the future and will have forgot about this.

Here is my current extras-hdpvr2.xml file: 

Code:

<extras>
  <channel name="{channel-name}">
    <command>bash</command>
    <args>-c "/opt/nextpvr/system/data/scripts/pvr2.sh {channel}"</args>
  </channel>
</extras>

Martin, I have a question. In one of the post, you said you used {2.2} instead of {channel}. However, I didn't understand the reasoning behind it. Can you explain what it change compared to {channel}?

My next challenge is for the ir blaster. I have a usb-uirt which is recognized by lirc. I was using usbuirtsend.exe on Windows. Is there a way to use/convert the USB-UIRT IR file? I've not found anything yet so I guess not but while I start looking more into lirc, if somebody has a magic trick, it would be great.

Thank you.

ehfortin

[mvallevand]

Extras go in /var/opt/nextpvr That is a permanent data folder with configuration information, database etc. The program folder is static,

I use these -a 1 -d 2 and get AC-3, I guess you need to hook your box up to a TV and see. I get the SPDIF from my splitter though.

I used 2.2. hardcoded for an extra that needed major and minors since NextPVR's channel option doesn't send the minor number (typically ATSC)

I don't know anything about usb-uirt and how it works with LIRC sorry.

Martin

[ehfortin]

That's fine. I'm able to send half of the number through irsend. The rest are not working correctly but it's a matter of having those recorded correctly by irrecord or translated from HEX to LIRC RAW which I don't know how to do yet. But as I have at least a few digit working, I would like to integrate the blaster script into the equation. I seems to remember that you have a subscript in your script that is called from the extras. Can you share it? I know you are not using usb-uirt but I seems to remember you are using LIRC so this part should be similar. I'm curious to see if you are using irsend and how you deal with the KEY_#.

Thank you.

ehfortin