home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
MediaPortal 1 Talk
Multiple Hauppauge Colossus cards -- pre- and post-recording behavior?
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="mm1352000" data-source="post: 1050539" data-attributes="member: 82144"><p>Happy new year to you as well! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p></p><p>The hardware side of this makes perfect sense to me and I can see what you're wanting to do. I think where you need more clarity is on the boundaries/purposes of MediaPortal, TV Server and IRSS. In other words, the "TV Server box" and "MediaPortal 1.5+" sections.</p><p></p><p></p><p>Maybe so. This in itself is no problem. However I think it is important to start pointing out here that if you're wanting to use "MediaPortal" to receive from or control Colossae then the primary component that you need to configure is <strong>TV Server, not MediaPortal</strong>. Maybe it would help your understanding if I said to think of MediaPortal as a client like XBMC. TV Server is effectively independent back end software.</p><p></p><p></p><p>That's fine. No problem. There is a SchedulesDirect plugin <strong>for TV Server</strong>. Confusingly, it is installed using the MediaPortal Extension Installer which itself is only installed if you install MediaPortal (ie. the front end client).</p><p></p><p></p><p>I agree with your statement regarding the hardware. However, I want to be absolutely crystal clear about the software too. MediaPortal does <strong>not</strong> contain any implementation of tuning, scheduling, EPG storage... etc. So, when you say "the correct software implementation in MP" what I think you really mean is "the correct software implementation in TV Server and IRSS".</p><p></p><p></p><p>Understood. This is something that <strong>IRSS </strong>will need to understand and be configured to handle.</p><p></p><p></p><p>Okay.</p><p>As I've tried to explain previously: that configuration is only to allow you to navigate through MediaPortal (the front end). In other words, it is configuration for the receiver part of the USB-UIRT... <strong>not</strong> for the two blaster ports.</p><p></p><p></p><p>Absolutely. That is way more flexible and complicated than what you need. For your purposes all you need is for IRSS to send "1" to the correct STB when the channel that you want to view/record has a "1" in the channel number.</p><p></p><p>Note that I did <strong>not</strong> say "when you press a "1" on your remote". That is because channel selection in the front end could be done with up/down/left/right arrows + enter/OK. Let me explain in more detail... because it is <strong>really crucial</strong> that you understand this.</p><p></p><p>When you select a channel in MediaPortal, MediaPortal interprets the combination of button presses (presumably on a remote control in your case) to mean "okay, he wants to tune channel ABC". You might have selected the channel with numbers or arrows or even the green button for all MP knows or cares. The point is that the end result is that MediaPortal tells TV Server: "please tune channel <strong>ABC</strong>". I can't over-emphasize enough: MP is <strong>not</strong> saying "tune channel 123". Aside from the fact that MediaPortal doesn't have any concept of channels, tuners, EPG, recordings etc. without TV Server... this is the fundamental reason why you cannot solve this problem using MediaPortal alone.</p><p></p><p>Continuing the explanation...</p><p>In your case, when TV Server gets that "please tune channel ABC" request, all TV Server will know to do is select the HDMI input on one of the two Colossae. That by itself doesn't change any channels unless you had different STBs connected via HDMI, component, composite etc.</p><p></p><p>So how does the STB actually get told to change channels?</p><p>The "magic" is that the IRSS TVE 3 Blaster plugin is always watching what TV Server does. When TV Server gets that "please tune channel ABC", TV Server sends out a general message to all TV Server plugins saying "I'm about to tune channel ABC". When the TVE 3 Blaster plugin gets that message, it looks up the channel number associated with channel ABC (let's say it is channel 100), figures out which blaster port needs to be blasted, and then tells IRSS: "please blast 1 + 0 + 0 + OK on USB UIRT blaster port 2".</p><p></p><p>Hopefully things are starting to click for you now.</p><p></p><p></p><p>No. As I've tried to explain above, you simply can't have a proper working solution with only MediaPortal, or with only MediaPortal and IRSS. The way I see it you're thinking about this totally the wrong way. The components you really need are TV Server and IRSS. MediaPortal is the expendable part that can be swapped out for XBMC or some other front end.</p><p></p><p></p><p>For this you need MediaPortal, TV Server and the TV Server SchedulesDirect plugin.</p><p></p><p></p><p>For this you only need TV Server. MediaPortal and IRSS will never know what a Colossus is.</p><p></p><p></p><p>No - not MP and/or TV Server. You need to make <strong>IRSS </strong>and its <strong>TVE 3 Blaster plugin</strong> aware of this. Also, you need to make the TVE 3 blaster plugin aware that when TV Server tunes with Colossus 1 then IRSS should blast with port 1; similarly, when TV Server tunes with Colossus 2 then IRSS should blast with port 2. This is how IRSS fits in.</p><p></p><p></p><p>You schedule the recordings in MediaPortal.</p><p>TV Server stores the schedules and deals with the timing stuff.</p><p>IRSS and the TVE 3 blaster plugin take care of the blasting.</p><p></p><p></p><p>Again, this has absolutely nothing to do with MediaPortal.</p><p>As above, TV Server controls the timing and selects the HDMI input on the Colossae.</p><p>IRSS has to do the blasting... and on that note, I thought you'd already confirmed that the TVE 3 blaster plugin blasts for the second recording?</p><p></p><p></p><p>Honestly, I'm leaning towards the nuts side. I don't mean to be rude in any way. If you had said "unrealistic" instead of "nuts" I would have been able to agree more wholeheartedly.</p><p>The thing is, from my perspective MP, TV Server and IRSS are robust. When I say that, I mean they're generally reliable and do what the label says they'll do. Same with generic. Each component has its place and can be swapped out if not suitable. For example, MP can be swapped out for XBMC; TV Server's scheduler can be swapped out for Argus; IRSS and the TVE 3 blaster plugin can be swapped out for an alternative blaster plugin/system. I'm not sure what more you could ask for on that front.</p><p>Your confusion seems to be one of the consequences of the generic design. I mean, somebody could have built the USB-UIRT blaster support directly into TV Server... but they didn't because they wanted a more generic solution which supports a whole range of STBs and blasters... which is IRSS.</p><p>Another consequence is that I don't think people are ever going to be able to smoothly configure such a setup like an off-the-shelf PVR. Configuration has to be done in separate applications and places; there is no way to automate it or improve the flow.</p><p>On the other hand, there is much more flexibility and power to do crazy things... and that is completely in line with the design philosophy of MediaPortal. </p><p></p><p>mm</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1050539, member: 82144"] Happy new year to you as well! :) The hardware side of this makes perfect sense to me and I can see what you're wanting to do. I think where you need more clarity is on the boundaries/purposes of MediaPortal, TV Server and IRSS. In other words, the "TV Server box" and "MediaPortal 1.5+" sections. Maybe so. This in itself is no problem. However I think it is important to start pointing out here that if you're wanting to use "MediaPortal" to receive from or control Colossae then the primary component that you need to configure is [B]TV Server, not MediaPortal[/B]. Maybe it would help your understanding if I said to think of MediaPortal as a client like XBMC. TV Server is effectively independent back end software. That's fine. No problem. There is a SchedulesDirect plugin [B]for TV Server[/B]. Confusingly, it is installed using the MediaPortal Extension Installer which itself is only installed if you install MediaPortal (ie. the front end client). I agree with your statement regarding the hardware. However, I want to be absolutely crystal clear about the software too. MediaPortal does [B]not[/B] contain any implementation of tuning, scheduling, EPG storage... etc. So, when you say "the correct software implementation in MP" what I think you really mean is "the correct software implementation in TV Server and IRSS". Understood. This is something that [B]IRSS [/B]will need to understand and be configured to handle. Okay. As I've tried to explain previously: that configuration is only to allow you to navigate through MediaPortal (the front end). In other words, it is configuration for the receiver part of the USB-UIRT... [B]not[/B] for the two blaster ports. Absolutely. That is way more flexible and complicated than what you need. For your purposes all you need is for IRSS to send "1" to the correct STB when the channel that you want to view/record has a "1" in the channel number. Note that I did [B]not[/B] say "when you press a "1" on your remote". That is because channel selection in the front end could be done with up/down/left/right arrows + enter/OK. Let me explain in more detail... because it is [B]really crucial[/B] that you understand this. When you select a channel in MediaPortal, MediaPortal interprets the combination of button presses (presumably on a remote control in your case) to mean "okay, he wants to tune channel ABC". You might have selected the channel with numbers or arrows or even the green button for all MP knows or cares. The point is that the end result is that MediaPortal tells TV Server: "please tune channel [B]ABC[/B]". I can't over-emphasize enough: MP is [B]not[/B] saying "tune channel 123". Aside from the fact that MediaPortal doesn't have any concept of channels, tuners, EPG, recordings etc. without TV Server... this is the fundamental reason why you cannot solve this problem using MediaPortal alone. Continuing the explanation... In your case, when TV Server gets that "please tune channel ABC" request, all TV Server will know to do is select the HDMI input on one of the two Colossae. That by itself doesn't change any channels unless you had different STBs connected via HDMI, component, composite etc. So how does the STB actually get told to change channels? The "magic" is that the IRSS TVE 3 Blaster plugin is always watching what TV Server does. When TV Server gets that "please tune channel ABC", TV Server sends out a general message to all TV Server plugins saying "I'm about to tune channel ABC". When the TVE 3 Blaster plugin gets that message, it looks up the channel number associated with channel ABC (let's say it is channel 100), figures out which blaster port needs to be blasted, and then tells IRSS: "please blast 1 + 0 + 0 + OK on USB UIRT blaster port 2". Hopefully things are starting to click for you now. No. As I've tried to explain above, you simply can't have a proper working solution with only MediaPortal, or with only MediaPortal and IRSS. The way I see it you're thinking about this totally the wrong way. The components you really need are TV Server and IRSS. MediaPortal is the expendable part that can be swapped out for XBMC or some other front end. For this you need MediaPortal, TV Server and the TV Server SchedulesDirect plugin. For this you only need TV Server. MediaPortal and IRSS will never know what a Colossus is. No - not MP and/or TV Server. You need to make [B]IRSS [/B]and its [B]TVE 3 Blaster plugin[/B] aware of this. Also, you need to make the TVE 3 blaster plugin aware that when TV Server tunes with Colossus 1 then IRSS should blast with port 1; similarly, when TV Server tunes with Colossus 2 then IRSS should blast with port 2. This is how IRSS fits in. You schedule the recordings in MediaPortal. TV Server stores the schedules and deals with the timing stuff. IRSS and the TVE 3 blaster plugin take care of the blasting. Again, this has absolutely nothing to do with MediaPortal. As above, TV Server controls the timing and selects the HDMI input on the Colossae. IRSS has to do the blasting... and on that note, I thought you'd already confirmed that the TVE 3 blaster plugin blasts for the second recording? Honestly, I'm leaning towards the nuts side. I don't mean to be rude in any way. If you had said "unrealistic" instead of "nuts" I would have been able to agree more wholeheartedly. The thing is, from my perspective MP, TV Server and IRSS are robust. When I say that, I mean they're generally reliable and do what the label says they'll do. Same with generic. Each component has its place and can be swapped out if not suitable. For example, MP can be swapped out for XBMC; TV Server's scheduler can be swapped out for Argus; IRSS and the TVE 3 blaster plugin can be swapped out for an alternative blaster plugin/system. I'm not sure what more you could ask for on that front. Your confusion seems to be one of the consequences of the generic design. I mean, somebody could have built the USB-UIRT blaster support directly into TV Server... but they didn't because they wanted a more generic solution which supports a whole range of STBs and blasters... which is IRSS. Another consequence is that I don't think people are ever going to be able to smoothly configure such a setup like an off-the-shelf PVR. Configuration has to be done in separate applications and places; there is no way to automate it or improve the flow. On the other hand, there is much more flexibility and power to do crazy things... and that is completely in line with the design philosophy of MediaPortal. mm [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Talk
Multiple Hauppauge Colossus cards -- pre- and post-recording behavior?
Contact us
RSS
Top
Bottom