Hauppauge HD-PVR & Colossus Support (3 Viewers)
- Thread starter WileECoyote
- Start date
- September 1, 2008
- 21,577
- 8,224
- Home Country
-
New Zealand
I can tell that you're using the DLL that is attached to the first post. What I'm saying is *don't* use the one attached to the first post. Use the one that came out of the All_Colossus_HDPVR_Patch(v2).zip.
Duh, let me go do that. I apparently got confused. I'll get back to you.
Went back and copied over the All_Colossus files and no change. I downloaded All_Colossus again and copied over the TVLibrary.dll from the All_Colossus folder once more, but same problem. Just to clarify, the All_Colossus file I'm using was in post 367, as referenced in post 1. I'm asking, because it say in post 367 not to reference it yet. Thought I might go back and reinstall MP, and maybe try another skin, unless you have any other suggestions. I've been fiddling with things so much that maybe I've corrupted something. Thanks again for your help.
Went back and copied over the All_Colossus files and no change. I downloaded All_Colossus again and copied over the TVLibrary.dll from the All_Colossus folder once more, but same problem. Just to clarify, the All_Colossus file I'm using was in post 367, as referenced in post 1. I'm asking, because it say in post 367 not to reference it yet. Thought I might go back and reinstall MP, and maybe try another skin, unless you have any other suggestions. I've been fiddling with things so much that maybe I've corrupted something. Thanks again for your help.
- September 1, 2008
- 21,577
- 8,224
- Home Country
-
New Zealand
Hi again
You haven't corrupted anything. Well, at least it doesn't look that way from the logs you posted earlier. What they're saying is that TV Server is not detecting audio or video from the HDPVR. Are you sure you have the right inputs configured in all your channels? SvhsInput1 is what your logs say. That would be an s-video input. You're not using component or composite?
mm
You haven't corrupted anything. Well, at least it doesn't look that way from the logs you posted earlier. What they're saying is that TV Server is not detecting audio or video from the HDPVR. Are you sure you have the right inputs configured in all your channels? SvhsInput1 is what your logs say. That would be an s-video input. You're not using component or composite?
mm
- September 1, 2008
- 21,577
- 8,224
- Home Country
-
New Zealand
Oh no - you're going to hate me for this. 
You know all those channels in the TV Server "TV Channels" section? What you're going to have to do is for each one, click edit, select the tuning detail (that is the row), click edit, and then change the video source field to YRYBY#1. At least I think it would be YRYBY#1. It would definitely pay to get one channel working before you change all of them. I might be wrong, but the SchedulesDirect plugin might also allow you to set that field when you create the channels, so that would be the alternative - delete all the channels and reimport them using the correct settings.
mm
You know all those channels in the TV Server "TV Channels" section? What you're going to have to do is for each one, click edit, select the tuning detail (that is the row), click edit, and then change the video source field to YRYBY#1. At least I think it would be YRYBY#1. It would definitely pay to get one channel working before you change all of them. I might be wrong, but the SchedulesDirect plugin might also allow you to set that field when you create the channels, so that would be the alternative - delete all the channels and reimport them using the correct settings.
mm
Some good clues. Now that I think about it, I seem to remember some option somewhere to choose a component source. It might have been in Schedules Direct, but I overlooked it at the time, not realizing how important it was. I'll let you know. I not only DON'T hate you, you have my undying gratitude for the progress you've helped me make. I've spent a day and a half on this and would have spent a lot more without your help.
The choice is in the "Advanced" tab of the SD downloader in the TVserver. The default choice is SvhsInput1, but who knew that was S-video? Couldn't the programmers just say S-video? In each of the selections in the drop down menu, there is a 1, 2, and 3 choice (YRYBYInput1, 2 and 3). I'm not sure what that means either. I'm going to assume it relates to the number assigned to the device in the server and will try to download the channel guide again with this clicked. THANK YOU AGAIN!
The choice is in the "Advanced" tab of the SD downloader in the TVserver. The default choice is SvhsInput1, but who knew that was S-video? Couldn't the programmers just say S-video? In each of the selections in the drop down menu, there is a 1, 2, and 3 choice (YRYBYInput1, 2 and 3). I'm not sure what that means either. I'm going to assume it relates to the number assigned to the device in the server and will try to download the channel guide again with this clicked. THANK YOU AGAIN!
- September 1, 2008
- 21,577
- 8,224
- Home Country
-
New Zealand
Hi again srr037
From what you've said and what I know about our code, the field obviously lists the complete set of video inputs in our code. We support up to 3 of each kind of input on a single device, hence the 1's, 2's and 3's. S-video would make more sense to me too, as would component instead of YRYBY or RGB etc., but these relate to the inputs on crossbar devices which are labelled in the same way (as per the Microsoft BDA standard). Device manufacturers choose how they associate those labels with physical inputs like s-video, and unfortunately I don't think they all use the same associations. I'm going to blame Microsoft for this one, but I will keep it in the back of my mind for the future...
mm
From what you've said and what I know about our code, the field obviously lists the complete set of video inputs in our code. We support up to 3 of each kind of input on a single device, hence the 1's, 2's and 3's. S-video would make more sense to me too, as would component instead of YRYBY or RGB etc., but these relate to the inputs on crossbar devices which are labelled in the same way (as per the Microsoft BDA standard). Device manufacturers choose how they associate those labels with physical inputs like s-video, and unfortunately I don't think they all use the same associations. I'm going to blame Microsoft for this one, but I will keep it in the back of my mind for the future...
mm