2021-08-21, 10:12 AM
Hello, just wondering if it is possible to change the channel inputs of my saved Colossus card configuration in the NextPVR web app?.
I currently use HDMI video input and HDMI audio input for my colossus card.
Have been using the Dolby Digital 5.1 audio from my STB, and it works really well with Kodi Matrix on my Windows PC, and also with my NVidia Shields running Kodi Matrix. For whatever reason, I don't require delays or anything when blasting on the above clients, and it works really well.
However, using Dolby Digital causes other clients such as native NextPVR client on the Windows PC, and AppleTV client MrMC to lose audio when channel changing.
Finally, I decided to change my STB's audio output to PCM/Mpeg and try things out.
It certainly fixes the audio issue for those affected clients, that is good.
Whilst messing around, I discovered my STB can have both HDMI and Toslink (Optical Digital) simultaneously, and has options to select type of audio for each output.
ie. Can select PCM/Mpeg for HDMI audio output, and Dolby Digital for Toslink audio output.
So, I wondered if I could have the best of both worlds?.
I wondered for the STB channels in my NextPVR HDPVR device channel list, if I could alter the inputs for the channels that support Dolby Digital, to use the optical digital input for audio, and the HDMI for video.
I changed some of the channels to use HDMI/SPDIF instead of HDMI/HDMI.
I had to re-enter the blast configs, as updating a channel forces this.
When I select a channel, the IR codes seem to flash, and can see my STB indicating it is receiving change channel command, but it is not sending the correct channel command, and my STB just changes to the last working channel.
I manually changed channels with my STB remote, and can confirm that it was indeed getting HDMI video, and Toslink Audio.
However, it messes up IR Blasting.
If I change the channel inputs back to HDMI/HDMI, then it changes channels properly again, and blasts normally.
I just wondered if there is some trick to overcome this?
I am editing an existing channel to change inputs, and wonder if nuking all the channels and configuring one at a time as new channels would make any difference?
I thought that was quite interesting, and wonder if the blasting weirdness was due to editing inputs as opposed to creating a brand new channel?
I currently use HDMI video input and HDMI audio input for my colossus card.
Have been using the Dolby Digital 5.1 audio from my STB, and it works really well with Kodi Matrix on my Windows PC, and also with my NVidia Shields running Kodi Matrix. For whatever reason, I don't require delays or anything when blasting on the above clients, and it works really well.
However, using Dolby Digital causes other clients such as native NextPVR client on the Windows PC, and AppleTV client MrMC to lose audio when channel changing.
Finally, I decided to change my STB's audio output to PCM/Mpeg and try things out.
It certainly fixes the audio issue for those affected clients, that is good.
Whilst messing around, I discovered my STB can have both HDMI and Toslink (Optical Digital) simultaneously, and has options to select type of audio for each output.
ie. Can select PCM/Mpeg for HDMI audio output, and Dolby Digital for Toslink audio output.
So, I wondered if I could have the best of both worlds?.
I wondered for the STB channels in my NextPVR HDPVR device channel list, if I could alter the inputs for the channels that support Dolby Digital, to use the optical digital input for audio, and the HDMI for video.
I changed some of the channels to use HDMI/SPDIF instead of HDMI/HDMI.
I had to re-enter the blast configs, as updating a channel forces this.
When I select a channel, the IR codes seem to flash, and can see my STB indicating it is receiving change channel command, but it is not sending the correct channel command, and my STB just changes to the last working channel.
I manually changed channels with my STB remote, and can confirm that it was indeed getting HDMI video, and Toslink Audio.
However, it messes up IR Blasting.
If I change the channel inputs back to HDMI/HDMI, then it changes channels properly again, and blasts normally.
I just wondered if there is some trick to overcome this?
I am editing an existing channel to change inputs, and wonder if nuking all the channels and configuring one at a time as new channels would make any difference?
I thought that was quite interesting, and wonder if the blasting weirdness was due to editing inputs as opposed to creating a brand new channel?