Colossus 2 and nextpvr

[mvallevand]

The extra looks ok, but there is no point testing the extra in NextPVR until the script works from bash.

To start your script is not going to send anything to NextPVR, NextPVR will just wait and fail

- you have incorrectly added sudo which will not work since you are running as nextpvr which isn't a sudo user and it probably is waiting for a password to be entered.
- you also need to use ffmpeg ffprobe was used see if you were getting data from command line testing.

Also I didn't give you the whole script, just the command line I used to help testing, I would try either removing the & or adding a wait after line in the script. This is all based on having my patch too.

So fix those errors in the script the run (keep ffmpeg in the script)

colossus2.sh | ffprope -i pipe:

until you are getting audio and video streams.

Here is what my output looks like

Code:

2024-04-21T12:27:16.632207 CRIT <main> Logger.cpp:83 (setLogLevelFilter) Changing loglevel to NOTC
2024-04-21T12:27:16.632818 CRIT <main> hauppauge2.cpp:355 (main) Starting up
2024-04-21T12:27:16.651952 CRIT <main> hauppauge2.cpp:368 (main) Initializing [Bus: 1, Port: 1] E515-00-00AE3EB8
2024-04-21T12:27:23.700810 CRIT <main> hauppauge2.cpp:69 (evtWait) waiting
Input #0, mpegts, from 'pipe:':
  Duration: N/A, start: 1.433367, 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), 1920x1080 [SAR 1:1 DAR 16:9], 29.97 fps, 29.97 tbr, 90k tbn
  Stream #0:1[0x101]: Audio: ac3 (AC-3 / 0x332D4341), 48000 Hz, 5.1(side), fltp, 640 kb/s

Martin

[Iriman]

ive tried and tried again with the updates to the .sh and trying to ffprobe. for some reason i cannot enable/initialize the device unless the script is run as sudo. def not what i want. as long as sudo is passed, the device initializes and at least throws an error that it cant read the info.

[mvallevand]

Is it executable for everyone? Do you see that with

ls -la /opt/Hauppauge/bin/hauppauge2

-rwxr-xr-x 1 root root 31927024 Mar 24 12:39 /opt/Hauppauge/bin/hauppauge2

and when you read about /etc/udev/rules.d/99-Hauppauge.rules did you add yourself to the video group (or whatever group you assigned)

Martin

[Iriman]

yes I am a member of the video group, and my file looks to have the same ownership and permissions as yours does. it needs the elevation to access the usb bus for some reason.

[mvallevand]

Check the rules for typos since you shouldn't need sudo after the reboot.

Martin

[Iriman]

got it working by re-adding myself to video group. now it runs without sudo.
[mpegts @ 0x63928f9d0e00] Could not find codec parameters for stream 1 (Audio: aac ([15][0][0][0] / 0x000F), 0 channels): unspecified sample format
Consider increasing the value for the 'analyzeduration' (0) and 'probesize' (5000000) options
Input #0, mpegts, from 'pipe:':
Duration: N/A, start: 2.961344, bitrate: N/A
Program 1
Stream #0:0[0x1011]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p(tv, bt709, progressive), 1920x1080 [SAR 1:1 DAR 16:9], 29.97 fps, 59.94 tbr, 90k tbn
Stream #0:1[0x1100]: Audio: aac ([15][0][0][0] / 0x000F), 0 channels
pipe:: Invalid data found when processing input

[mvallevand]

That's a step forward and I can't help think it is your HDMI output source or splitter not setting proper audio. If you have a another HDMI source you could try it.

Martin

[Iriman]

yeah. all sources are throwing the same audio error. tried a dvd player, (hdmi), an older cable box and my tablet.

[mvallevand]

Maybe try this https://github.com/jpoet/HauppaugeUSB/issues/30 I only have an HDVPR2 and I can record AC-3 or AAC so I can't help much here.

Martin

[Iriman]

ended up buying a HDMI>component adapter thats working well. AC3 audio is only available as passthrough on the colossus 2. i spent a week looking into it and there was no way it was going to work. Now that i can see both audio and video streams, i wonder why nextpvr/kodi isnt playing the content. it errors out and the device locks up. How'd you end up fixing that?